R12.1.1 Invalid Objects After Patching - FRM-18108: Failed to load the following objects

R12.1.1 Invalid Objects After Patching - FRM-18108: Failed to load the following objects

When attempting to prepare a new instance on R12.1.1  for Order Management, receive invalid objects that will not regenerate.


ERROR
-----------------------
FRM-18108: Failed to load the following objects.

Source Module:OEXOEREL.fmb
Source Object: RELATED_ITEMS_PROMPT
Source Module:OEXOEREL.fmb
Source Object: RELATED_ITEMS
Source Module:OEXOEREL.fmb
Source Object: RELATED_ITEMS_CONTROL
Source Module:OEXOEREL.fmb
Source Object: RELATED_ITEMS_FOLDER
Source Module:OEXOEREL.fmb
Source Object: RELATED_ITEMS_FIXED
Source Module:OEXOEREL.fmb

In file aderrchk.lst
See the following error:
JAVA CLASS 0
oracle/apps/fnd/common/ias/JservA
dminHelper
ORA-29552: verification warning:
java.lang.UnsupportedClassVersionError:
oracle/apps/fnd/common/ias/JservAdminHelper (Unsupported
major.minor version 49.0)
(repeated for more JAVA messages)
...
PACKAGE BODY 0
BPEL_UPDATEORDEREBS11I10TOCOMS
PLS-00907: cannot load library unit APPS.OE_ACKNOWLEDGMENT_PUB
(referenced by APPS.OE_OUTBOUND_INT)

ran adadmin for ONT applications; below objects where not  compiled:
 au resource OESCHORG.pll
 au resource OEXOEFRM.pll
 au resource OEXOELIB.pll
 au resource OEXOELIN.pll
 ont forms/US OESCHORG.fmx
 ont forms/US OEXOEORD.fmx
 ont forms/US OEXOETEL.fmx
 ont forms/US OEXOERLI.fmx
 ont forms/US OEXOEVER.fmx

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Refresh from production ( 0 invalid objects)
2. Apply about 50 patches
3. Error in OM files

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access forms to complete setup and create sales orders.

Changes

Create a new R12.1.1 instance.
Cause

Many invalid OM objects after creating and patching a new instance.

The following bug was created for this issue:
OM Bug  9655621 - R12.1.1 - OE INVALID OBJECTS AFTER APPLING 51 PATCHES (NON OM)


Solution


To implement the solution, please execute the following steps:
1.
a) restart the database
b) run utlirp/utlrp as sys as instructed in the base bug.
    $ORACLE_HOME/rdbms/admin/utlirp.sql
    $ORACLE_HOME/rdbms/admin/utlrp.sql
c) if apps objects are still invalid after this then run the relevant
Apps script(s) to recompile.
d) once all objects in the database are valid run the following select
to ensure there are no timestamp mismatches remaining:

alter session set nls_date_format='dd-mon-yy hh24:mi:ss';

select do.name dname, po.name pname, d.p_timestamp, po.stime p_stime
from sys.obj$ do, sys.dependency$ d, sys.obj$ po
where d.P_OBJ#=po.obj#(+)
and d.D_OBJ#=do.obj#
and do.status=1 /*dependent is valid*/
and po.status=1 /*parent is valid*/
and po.stime!=d.p_timestamp /*parent timestamp not match*/
and do.type# not in (28,29,30) /*dependent type is not java*/
and po.type# not in (28,29,30) /*parent type is not java*/
order by 2,1;

If issues performing step 1, create a new service request with DataBase product,
component PL/SQL.

2. After following the above instruction, if all the Database packages are valid,
then try recompiling the pll and forms