My Oracle Support Banner

R12 Output Post Processing Fails After DB Upgrade with 'APP-FND-01564: ORACLE error 28 in publish' Error (Doc ID 2312154.1)

Last updated on JULY 01, 2024

Applies to:

Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

E-Business Suite R12 Concurrent Processing, Output Post Processing (OPP) related issues

 After a database upgrade from 11.2.0 to 12.1.0, Output Post Processor requests fail with the following errors in the Concurrent Request log file:

APP-FND-01564: ORACLE error 28 in publish

Cause: publish failed due to ORA-00028: your session has been killed.

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.
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 Output Post Processor log shows the following errors:

 [70:0] Output file was found but is zero sized - Deleted
[UNEXPECTED] [70:0] java.io.IOException: IO Error: Invalid Packet Length
at oracle.jdbc.driver.OracleBlobInputStream.needBytes(OracleBlobInputStream.java:204)
(...)
Caused by: oracle.net.ns.NetException: Invalid Packet Length
at oracle.net.ns.Packet.processHeader(Packet.java:361)
(...)

 [UNEXPECTED] [70:0] java.sql.SQLRecoverableException: Closed Connection
at oracle.jdbc.driver.PhysicalConnection.prepareCall(PhysicalConnection.java:3416)
(...)

 

Checking the database trace files the below error appears multiple times:

ORA-03137: TTC protocol internal error : [10000] [0] [100] [0] [] [] [] []

Changes

Upgraded the EBS database from 11.2.0 to 12c (12.1.0)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.