Oracle eBusiness 12.2 clone : OHS config fails for UpdateOhsT2PMovePlan.java:1063

While running clone we faced this issue. Multiple runs but every-time it failed at OHS config.
Under txkSetOHSConfig directory provison_<timestamp>.log has following error.

Updating /YMS-UI-context-root and setting WeblogicCluster to : u060supcw801.kroger.com:6801Inside run context 
StackTrace: java.lang.NullPointerException at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSDirectives(UpdateOhsT2PMovePlan.java:812) at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:721) at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:698) at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:698) at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.processMoveplan(UpdateOhsT2PMovePlan.java:631) at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.main(UpdateOhsT2PMovePlan.java:1063)

Solution:

It was not a recommended way but we had to solve it asap. So I looked for start of the error (just prior to that) in the log.
It was completing until the point /YMS-UI-context-root.

Now searched same string in the comn/clone/FMW/OHS/moveplan.xml.
Took a backup of it and removed the section which was just next to /YMS-UI-context-root. For us this was /console with further details host,port etc. so removed it totally.
p.s. Stick to the indentation and identifiers to remove the section exactly point to point. If not done correctly this may say invalid moveplan.xml in next execution.

So post removing the particular part from moveplan.xml I executed the clone again, and it completed with some warnings. Some services did not come up correctly but we were able to solve those small issues and bring application up.

Reason:
Later found that we had some customization on console URL which was causing the issue. Customization should be removed, or this is supposed to throw error.

[ERROR] Unable to continue as an existing adop session was found.

Using ADOP on 12.2.5 environment. Last session had some issues so we aborted the same. the adop -status was clearly showing aborted.

Node Name       Node Type  Phase           Status          Started              Finished             Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
xxxxxxxxx101    master     PREPARE         SESSION ABORTED 2017/02/06 15:52:37      6:55:14 
                                            APPLY           SESSION ABORTED
                                           FINALIZE        SESSION ABORTED
                                           CUTOVER         SESSION ABORTED
                                           CLEANUP         NOT STARTED

So now cleanup should be run and I tried the same. It gave me following messages.

Validating system setup.
    Node registry is valid.

Checking for existing adop sessions.
    [ERROR]     Unable to continue as an existing adop session was found.

[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"


Surprisingly the cleanup was not proceeding and checking logs with above command and the directories was giving nothing


Even checked from database side. The status was already "C" so nothing could be done here.

SQL> select ADOP_SESSION_ID , abort_status, prepare_status,apply_status , status, edition_name from ad_adop_sessions where ADOP_SESSION_ID=13;

ADOP_SESSION_ID A P A S EDITION_NAME
--------------- - - - - ------------------------------
             13 Y R N C


Digging more found following processing in execution. Looks like were started to abandon the patch but have still been there.

applmgr 18809034 20381948  58 22:57:32      -  0:00 /..../bin/adzdoptl.pl phase=prepare,apply patches=24390794,23708596 abandon=yes restart=no
applmgr 20381948        1 120 15:49:28      - 71:52 /..../bin/adzdoptl.pl phase=prepare,apply patches=24390794,23708596 abandon=yes restart=no


So killed these processes and tried cleanup phase again and it completed successfully.

Oracle eBusiness 12.1.3 to 12.2.5 upgrade - Part 3 (Upgrade to 12.2 - B)

Finishing 12.2 Upgrade


1. Back up the binaries and database.

2. Cleanup Nodes info (Optional).

SQL>exec fnd_conc_clone.setup_clean ;

3. Verify env variables on DB

LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
ORACLE_SID = <instance name for current database node>
TNS_ADMIN=$ORACLE_HOME/network/admin/<CONTEXT_NAME>
PATH=$ORACLE_HOME/bin:$ORACLE_HOME/appsutil/jre/bin:$PATH
PERL5LIB=$ORACLE_HOME/perl/lib/5.14.1:$ORACLE_HOME/perl/lib/site_perl/5.14.1:$ORACLE_HOME/appsutil/perl

4. Run autoconfig on database

Make appsutil again from apps using
perl <AD_TOP>/bin/admkappsutil.pl

Unzip on Databzse
unzip -o appsutil.zip

or copy database context file
cd <RDBMS ORACLE_HOME>/appsutil/bin
perl adbldxml.pl

Run Autoconfig
<RDBMS ORACLE_HOME>/appsutil/bin/adconfig.sh contextfile=<context file>


5. Run autoconfig on App.

Drop table ADX_PRE_AUTOCONFIG from APPS schema, will be recreated during autoconfig.
cd <AD_TOP>/patch/115/sql
sqlplus APPS/$APPS_PASS @txkDropAdxPreAutoConfig.sql

Run AutoConfig on all the Application Tier nodes using the following Commands

$ADMIN_SCRIPTS_HOME/adautocfg.sh

6. Start Rapidwiz and run Configuration.

Provide Context File, then in further screens provide inputs as asked.

This will start configuration post confirmation. At the end you will get following screen for validation. 

Here we are done with 12.2 Upgrade. But there is a major step due is ADOP enablement.
ADOP is the new feature introduced with 12.2 making it too much different for earlier version. It is AD Online Patching, and so it needs specific versions of Database to support Edition Based Redefinition.

Following are the steps to enable Adop, which is also a part of Upgrade activity.

Enable ADOP


1. Apply E-Business Suite:Online Patching Readiness and GSCC Report patch 22071026:R12.AD.C.

2. Consider Localization if Any.

3. Run Readiness Scripts. (Doc ID 1531121.1)

sqlplus system @$AD_TOP/sql/ADZDPSUM.sql
sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql

Resolve all the issues reported by scripts.

4. Fix Data Dictionary or Time Stamp mismatch.
$AD_TOP/patch/115/sql/adzddtsfix.sql (Following the usage instructions provided in it).

Run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether the data dictionary corruption is still present.

In case yes, follow the doc 1531121.1.

5. Verify the tablespace Freespace.

Set the fs1 env.
Set HOSTNAME env variable without domain name.
Run adzdreport.pl.

Recommended for system to have 25 GB free space and APPS_TS_SEED to have 5 GB

6. Run the Online Patching Enablement - Status Report

sqlplus apps @$AD_TOP/sql/ADZDEXRPT.sql

7. Make sure Application Services are down.

8. Apply ADOP enablement patch. 13543062:R12.AD.C.

adpatch options=hotpatch,forceapply

Monitor the progress using sqlplus apps @$AD_TOP/sql/ADZDSHOWDDLS.sql

9. Check for invalids and compile.

exec sys.utl_recomp.recomp_parallel(n);

10. Re Run the online patching enablement report.

sqlplus <Apps Username> @$AD_TOP/sql/ADZDEXRPT.sql

Re run readiness reports for errors.

sqlplus system @$AD_TOP/sql/ADZDPSUM.sql
sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql

Run Compliance Checker again.

sqlplus <Apps Username> @$AD_TOP/sql/ADZDDBCC.sql


11. Resplice Localizations and perform additional activities.

12. Check following DB parameters.

service_names=%s_dbSid%,ebs_patch
recyclebin=off
_SYSTEM_TRIG_ENABLED=true

With this we are done with 12.2 Upgrade. This point onward whatever patches will go to the system will go using adop utility. So will be the 12.2.5 related patches and upgrade driver.

For 12.2.5 Upgrade please click on below link.