ORA-7445 in alert log when you open Project Quick Entry form

In one of the 11.5.10.2 instances which was upgraded to 10.2.0.3 Database, the following behavior was observed:

Whenever Project Quick Entry form was accessed, it gave the error:

FRM-40735: ON-ERROR trigger raised unhandled exception ORA-01001.

APP-FND-01564: error 1000 in audfrm

Cause: audfm failed due to ORA-01000 maximum open cursors exceeded
The SQL statement being executed at the time of the error was &SQLSTMT and was executed from the file &ERRFILE.

In alert log the following ORA-7445 was logged:

ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [drurnew()+184] [SIGSEGV] [Address not mapped to object] [0x000000040] [] []
Current SQL statement for this session:
INSERT INTO PA_PROJECT_CTX_SEARCH (PROJECT_ID, CTX_DESCRIPTION, PROGRAM_REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED
_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) VALUES
(:B2 , :B1 , NULL, NULL, NULL, NULL, FND_GLOBAL.USER_ID, SYSDATE, FND_GLOBAL.US
ER_ID, SYSDATE, FND_GLOBAL.LOGIN_ID)
----- PL/SQL Call Stack -----
object line object
handle number name
3ec258df8 5 CTXSYS.TEXTINDEXMETHODS
3ec258df8 625 CTXSYS.TEXTINDEXMETHODS
----- Call Stack Trace -----

We logged an SR for this issue and got this response:

CAUSE DETERMINATION
===================
This is unpublished Bug 5587976.

The error is due to a problem with the intermedia functionality.

CAUSE JUSTIFICATION
===================
BUG 5587976 : APPSST: ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [DRURNEW()+129] [SIGSEGV]

PROPOSED SOLUTION(S)
====================
Download and install Patch 5587976

Bug has been fixed in 10.2.0.4 patchset

PROPOSED SOLUTION JUSTIFICATION(S)
==================================
SURE 461767.1 : ORA-7445 [Drurnew()] Encountered During Applications Upgrade

SOLUTION / ACTION PLAN
======================
-- To implement the solution, please execute the following steps::
Download and install Patch 5587976

Even after applying this patch the issue was occuring. The DBA team ran gather schema statistics on PA schema from backend.

execute fnd_stats.gather_schema_stats('PA');

After this the issue was resolved. This issue was not occuring in dev/test instances which did not have this patch. It is possible that the error was coming solely due to the absence of statistics.