Preparation of clone for Production eBusiness suite is a day to day work for Apps DBAs in any organization and also time consuming exercise. Sometime Functional/Development team will raise daily request to prepare fresh clone or even Oracle Support Analyst will release any solution through raised SR with the pre-set note that apply solution on fresh clone of Production. During the cloning process if error occurs due to any factor Apps DBA has to drill down to different locations to read out error logs and understand the reason for failure, it is quite time consuming and effort taking work.

Oracle Proactive Support Team has released new utility to consolidate error information from clone log files from various locations into an HTML report. A cloning activity may generate up to a dozen separate log files. This new Log Parser utility will allow you to view relevant snippets of each log at one time. Additionally the Log Parser will do some basic configuration and health checks of the environment and also may provide leads to solving problems. Major benefits of using this utility are:

• Save time and efforts: will reduce considerable time and efforts to validating clone logs during clone process- Consolidates over 12 cloning log file types in a single HTML report!
• Quick Fix of errors – Parses log file; exposes log snippets showing errors & warnings
• Links solutions to key error messages in My Oracle Support content, for instant error-fix recommendations

As of now Clone Log Parser utility is available for:

• 11i (11.5.9+)
• R12 (12.0.x, 12.1.x)

Log Parser will consolidate error logs on all cloning, oraInventory and relinking logs in the following sequence.

• StageDBTier.log
• StageAppsTier_.log
• ApplyDBTier.log
• ApplyDatabase.log
• ApplyDBTechStack.log
• ApplyAppsTechStack.log
• ApplyAppsTier.log
• CloneContext.log
• make_.log, make.log
• adconfig.log
• ohclone.log
• adcrdb_.txt
• NetServiceHandler.log
• setup_stubs.log
• Central/Global oraInventory/logs directory and all sub-directories,
  for any files with a .err, .log or .txt extension

Following are the main log files locations; DBAs usually refer to identify any error from these files:

Preclone (adpreclone.pl) log files in source instance

• Database Tier-$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_<time>.log)
• Apps Tier     – $INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_<time>.log)

Post-Clone (Adcfgclone.pl) log files in target instance

• Database Tier- $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<time>.logApps Tier
• $INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_<time>.log

Installation of Clone Parser utility is very simple, no specific configuration requires, will follow 3 steps….unzip, run, view report

Download from Oracle My Support note E-Business Suite Clone Log Parser Utility (Rapid Clone)[VIDEO] (Doc ID 1447553.1) and install separately on db tier and apps tier separately through unzip utility.

After download, you can install simply unzipping to specified directory as per note, it is very important installation must be done as per specified path.

Now you can unzip the file on the directory like  $ORACLE_HOME/appsutil/clone by creating $ORACLE_HOME/appsutil/clone/LogParser/

We need to install  separate Clone Log Parser utility for the dbTier and appsTier. for apps tier unzip LogParser.zip into <COMMON_TOP>/clone/

EndNote:

E-Business Suite Clone Log Parser Utility (Rapid Clone)[VIDEO] (Doc ID 1447553.1)