Sunday, 16 February 2014
Concurrent Processing - All Concurrent Requests Fail With ORA-03113 and Database Error ORA-07445 (Doc ID 945107.1)
The concurrent managers are up and running, but all concurrent requests are failing with ORA-03113 and ORA-03114.
The request log file contains the following error:
ORACLE error 3114 in post_cp_metrics_event Cause: post_cp_metrics_event failed due to ORA-03114:not connected to ORACLE. The SQL statement being executed at the time of the error was: &SQLSTMTand was executed from the file &ERRFILE. ORACLE error 3114 in AFPRSR-Resubmit_Time Cause:AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE . The SQL statement being executed at the time of the error was: and was executed from the file. ORA-03114: not connected to ORACLE Routine AFPPRD has encountered a fatal error. ORA-03114: not connected to ORACLE
Contact your system administrator or support representative.
ORACLE error 3114 in AFPRSR-Resubmit_Time
Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE
The following error is reported in the database alert log.
ORA-07445: exception encountered: core dump [lfilic()+312] [SIGSEGV] [Address not mapped to object] [0x000000040] [] [] Thu Sep 24 07:59:56 2009
No errors are shown in the Internal Concurrent Manager log file.
Cause
Changes to symbolic links/paths or other environmental settings can cause ORA-07445 which in turn causes ORA-03114 . The cause of the issue is due to FND binaries/executables.
Solution
To implement the solution, please execute the below action plan:
1) Stop all the application services.
$ cd $ADMIN_SCRIPTS_HOME
$ adstpall.sh apps/apps
2) Relink the FND product binaries using adadmin.
3) Start all the application services.
$ cd $ADMIN_SCRIPTS_HOME
$ adstrall.sh apps/apps
4) Monitor the database alert log for any ORA-07445 errors.
5) Submit a Concurrent Request and check for its successful completion.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment