Monday 6 July 2015

'Concurrent program returned no reason for failure' || 'ORA-03114: not connected to ORACLE' || 'Shutting down Concurrent Manager' ||'Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected' ||'Intermittently Login URL unable to Access' || 'COncurrent Programs and Reports are Erroring out' || 'Standard manager getting down automatically' || 'OPP aslo getting down automatically'

'Concurrent program returned no reason for failure' || 'ORA-03114: not connected to ORACLE' || 'Shutting down Concurrent Manager' ||'Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected' ||'Intermittently Login URL unable to Access' || 'Concurrent Programs and Reports are Erroring out' || 'Standard manager(FNDLIBR) getting down automatically' || 'OPP aslo getting down automatically' || after executing adcmctl.sh, FNDLIBR process won't go down

Errors :

=======================Error1=================================

Concurrent program returned no reason for failure.

===========================Error 2============================
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: select To_Char(To_Date(Decode(Resubmit_Time,null ,'00:

Shutting down Concurrent Manager : 05-JUL-2014 11:22:21
ORA-03114: not connected to ORACLE

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: select To_Char(To_Date(Decode(Resubmit_Time,null ,'00:

List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected
to ORACLE
.

Review your error messages for the cause of the error. (=<POINTER>)

_ 2 _
Routine AFPPRD has encountered a fatal error. ORA-03114: not connected
to ORACLE


Contact your system administrator or support representative.

_ 3 _
Routine AFPPRD has encountered a fatal error. ORA-03114: not connected
to ORACLE


Contact your system administrator or support representative.
.............................................................................


=========================Error 3====================
Program was terminated by signal 9
APP-FND-01564: ORACLE error 3114 in close_server_files

Cause: close_server_files failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 3213341.

Review your concurrent request log and/or report output file for more detailed information.
ORACLE error 3114 in AFPRSR-Resubmit_Time
=========================Error 4======================
+---------------------------------------------------------------------------+
Subledger Accounting: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

XLAACCUP module: Accounting Program
+---------------------------------------------------------------------------+

Current system time is 05-JUL-2014 05:40:44

+---------------------------------------------------------------------------+

**Starts**05-JUL-2014 05:40:44



like above log in concurrent request's log, all the reports and requests are going into Error


========================================================================

Solution

========================================================================

we were unable to resolve this issue for 4 days, create many SR with oracle and took Oracle ACS service and got the confirmation that database side everything fine.

and they said it could be because of network issue.

If anybody face above error check the following:

1) Check database and application server's hard status like RAM,CPU and Hard disk etc...

2) Check connectivity between database and application.

3) verify the database and application servers are same subnet like ( db server ip : 10.10.10.221 apps server ip : 10.10.10.223 )

4) verify firewall and switch bandwidth utilization between database and application server

5) If application and database's servers are in different subnet mask like connective between database and application happening through firewall,
   and firewall unable to process the connective between the these db and apps, cpu of firewall reaching 90 to 100%,
   Bring the db and apps server in same subnet so that connective would not happen by firewall, then it will communicate by switch.
 
   <<<<<<<<<< all the above errors happened in our Environment because of this >>>>>>>>>>
 

App server ip was : 10.10.9.221
DB server ip was  : 10.10.10.223

Then we changed ip address of application server ( 10.10.10.198 ) by the use of : Correct Method of Changing the IP Address in 11i & R12 (Doc ID 751328.1)

Then everything became fine...... :)

Thanks & Regards,
Chandrasekar S

No comments:

Post a Comment