Preface
If you prepare a context file ahead of time and sanitize it well, you can save time during 11i clones.Sometimes, though, editing context XML files can turn against you as well. For example, simple syntax issues (missing a > or a /) can cause a lot of grief and convert precious time into roundabout troubleshooting effort.
The wise thing to do...
The AD product has its own utility for running Autoconfig in test mode. This provides a great channel for proof-executing the autoconfig run, check elaborate value errors and saving precious time during the clone.A sample run..
Run autoconfig on check mode on all tiers (middle tiers, admin tier, configurator tier):sandbox:dev806> /ORACLE/apps/dev/ad/11.5.0/bin/adchkcfg.sh
Enter the full path to the Applications Context file:
/ORACLE/apps/dev/admin/dev_sandbox.xml
Enter the APPS user password:
abcdefg
AutoConfig is running in test mode and building diffs...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /ORACLE/apps/dev/
Classpath : :/usr/java14/jre/lib/charsets.jar:/usr/java14/jre/lib/core.jar:/usr/java14/jre/lib/graphics.jar:
/usr/java14/jre/lib/ibmcertpathprovider.jar:
/usr/java14/jre/lib/ibmjaaslm.jar:/usr/java14/jre/lib/ibmjcefw.jar:
/usr/java14/jre/lib/ibmjgssprovider.jar:
/usr/java14/jre/lib/ibmjssefips.jar:/usr/java14/jre/lib/ibmjsseprovider.jar:
/usr/java14/jre/lib/ibmorb.jar:
/usr/java14/jre/lib/ibmorbapi.jar:/usr/java14/jre/lib/ibmpkcs.jar:
/usr/java14/jre/lib/javaplugin.jar:
/usr/java14/jre/lib/security.jar:/usr/java14/jre/lib/server.jar:
/usr/java14/jre/lib/xml.jar:
/usr/java14/lib/dt.jar:/usr/java14/lib/tools.jar:
/ORACLE/apps/dev/common/java/appsborg2.zip:
/ORACLE/apps/dev/common/java
Using Context file : /ORACLE/apps/dev/admin/dev_sandbox/out/01021539/dev_sandbox.xml
Context Value Management will now update the test Context file
Updating test Context file...COMPLETED
[ Test mode ]
No uploading of Context File and its templates to database.
Testing templates from all of the product tops...
Testing AD_TOP........COMPLETED
Testing FND_TOP.......COMPLETED
Testing ICX_TOP.......COMPLETED
Testing IEO_TOP.......COMPLETED
Testing ECX_TOP.......COMPLETED
Testing BIS_TOP.......COMPLETED
Testing GL_TOP........COMPLETED
Testing AMS_TOP.......COMPLETED
Testing CCT_TOP.......COMPLETED
Testing WSH_TOP.......COMPLETED
Testing OKE_TOP.......COMPLETED
Testing OKL_TOP.......COMPLETED
Testing OKS_TOP.......COMPLETED
Testing CSF_TOP.......COMPLETED
Testing XNC_TOP.......COMPLETED
Testing IGS_TOP.......COMPLETED
Testing IBY_TOP.......COMPLETED
Testing PA_TOP........COMPLETED
Testing JTF_TOP.......COMPLETED
Testing MWA_TOP.......COMPLETED
Testing CN_TOP........COMPLETED
Testing CSI_TOP.......COMPLETED
Testing WIP_TOP.......COMPLETED
Testing CSE_TOP.......COMPLETED
Testing EAM_TOP.......COMPLETED
Testing FTE_TOP.......COMPLETED
Testing ONT_TOP.......COMPLETED
Testing AR_TOP........COMPLETED
Testing AHL_TOP.......COMPLETED
Testing IES_TOP.......COMPLETED
Testing CSD_TOP.......COMPLETED
Testing IGC_TOP.......COMPLETED
Differences text report is located at: /ORACLE/apps/dev/admin/dev_sandbox/out/01021539/cfgcheck.txt
Generating Profile Option differences
report...COMPLETED
Generating File System differences
report......COMPLETED --> This is very important --> Check the changes made by adchkcfg.sh
original context.xml file against the changes made to the source file.
Differences html
report is located at:
/ORACLE/apps/dev/admin/dev_sandbox/out/01021539/cfgcheck.html
AutoConfig
completed with errors.
The log file for
this session is located at: /ORACLE/apps/dev/admin/dev_sandbox/log/01021539/adconfig.log
Conclusion
There are many useful AD utilities that we can leverage, if we are aware of them; adchkcfg.sh is one of them. It can be especially useful for pre-staging context XML files for 11i/12i RapidClones.
