These OPM-related update scripts were *not* intended to be included in the 12.2 upgrade driver.   These OPM table modifications are included in OPM Post-Upgrade steps.

In the u_merged.drv patch driver file, delete all references to the following files, and restart the adpatch session.

 GMFG5ITM.sql 

 GMFG5MCP.sql 

 GMFG6MEL.sql 

 GMFG6P00.sql 

 GMFG6P01.sql

 GMFG6P02.sql 

 GMFG6P03.sql 

 GMFG6P04.sql 

 GMFG6P05.sql 

 GMFG6P06.sql 

 GMFG6P07.sql 

 GMFG6P08.sql 

 GMFG6P09.sql 

 GMFG6P10.sql 

 GMFG6P11.sql 

 GMFG6P12.sql 

 GMFG6P14.sql 

 GMFG6P15.sql 

 GMFG6P16.sql 

 GMFG6P17.sql 

 GMFG6P18.sql 

 GMFG6P19.sql

uHalt all worker processes

uupdate $ORACLE_BASE/fs1/EBSapps/appl/au/12.0.0/patch/115/driver/u_merged.drv

uConfirm all adworker sessions are gone at the DB level

uRestart adpatch process

uPermanent Solution for 12.2 OPM Customers , oracle support released the pre-install patch "18688087"

uBug 18688087 - POOR PERFORMANCE ON GMFG6P03.SQL TASKS DURING 12.2 UPGRADE DRIVER

Manual method to add context file of FS1/FS2 File systems

FS_Clone or ADOP issues – basic check/Solution:

1) Before running fs_clone or any ADOP phases, we should make sure that there are three context files exists in FND_OAM_CONTEXT_FILES table. If not we have to run autoconfig on DB and Application nodes .

a. EXEC FND_CONC_CLONE.SETUP_CLEAN;

b. Run autoconfig on DB

c. Run autoconfig on App

Manual method to add context file of FS1/FS2 File systems :

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer action=upload contextfile=/u01/oracle/appl/fs2/inst/apps/DEV_testdev/appl/admin/DEV_testdev.xml logfile=/tmp/patchctxupload.log

De-register a custom schema from the e-business suite

De-register a custom schema from the e-business suite

•Log on the Alert Manager responsibility and go to menu System/Installations , then delete the line     related to your custom schema.

•Log on the System Administrator responsibility , menu Security/Oracle/Register then delete the line

•related to your custom schema.

•Remove the relevant entry from the FND_OAM_CONTEXT_CUSTOM table and run AutoConfig on

• all nodes.

Custom top Impact with Online patching in E-Biz 12.2

Online Patching Issues : Custom Products registration in 12.2 

If you are an upgrade customer with a custom product top in the context file, but have not run AD Splice, you must:

1.Remove the relevant entry from the FND_OAM_CONTEXT_CUSTOM table.

2.Run AutoConfig on all nodes.

3.Apply the latest AD-TXK release update pack as needed.

4.Run AD Splice to add/register the custom product.

Points to be noted before creating a new custom product:

1) Custom production abbreviation should be less than 8 Characters.

2) Custom product should not have any "_" ( Underscore) in the name

3) Custom product should not start with Numeric value

4) Custom products should be registered with ad<name> 

5) Custom Products should not be registered using OAM, we should use adsplice.

         Eg:  Product name : Flex Interface 

                 We should create the name as FLEXINT

Note : With E-Business Suite 12.2.4 the possibility to use OAM for a Custom Product TOP has been removed. You need to use the adsplice Utility from the Command line to add your Custom Product TOP starting with EBS 12.2.4 and higher.


Related Oracle Note :1577707.1