Routine AFPPRD has encountered a fatal error. ORA-03114: not connected to ORACLE|| 'Shutting down Concurrent Manager' ||ORACLE error 3114 in AFPRSR-Resubmit_Time

Error:

+--------- 1) POST-PROCESSING  ---------+

Beginning post-processing of request 34508980 on node ACOD1RKA001 at 18-OCT-2017 11:04:50.

-- Publishing output

APP-FND-01564: ORACLE error 3113 in publish

Cause: publish failed due to ORA-03113: end-of-file on communication channel.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.

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

Finished executing request completion options.

APP-FND-01564: ORACLE error 3114 in afpprq

Cause: afpprq 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.

Shutting down Concurrent Manager : 18-OCT-2017 11:09:55

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.

.............................................................................

Solutions:

There are multiple scenarios that cause this error. Check the following list of solutions:

Lets devide it into two scenarios where we get this error.

1.DB Connection issue :-

                           

2. Verify there is no firewall or router setting which terminates connections which are active for longer than x minutes.

3. Verify there is no firewall or router setting which terminates connections which are idle for longer than x minutes.

3. Verify the Oracle configuration. Let the database send a packet every x minutes, so that the firewall, router, etc does not close the connection due to being 'idle'.

                                    The Oracle documentation lists the following details for the  sqlnet.ora parameter:   SQLNET.EXPIRE_TIME