4. Run perl adcfgclone.pl dbTechStack on Target DB.Any reason you are using dbTechStack option if you are cloning everything?
Warning: Unable to connect to Database.Are you only configuring the RDBMS ORACLE_HOME? If not and you want to create the database then you should use dbTier instead of dbTechStack option.
user4434301 wrote:What is the complete error message this time?
I am not following you now, I'm just trying to figure out why the adcfgclone.pl dbTechStack script replace the previously existing listener, tnsnames, and sqlnet files and replace them with newly generated ones which contain unknown values for ports, etc? As far as I can tell, the DB port is now set to 3001?
Subsequent attempts to run perl adcfgclone.pl dbTechStack end in the following:
- 4% completed RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack
ERROR while running Apply...
Fri Dec 14 16:32:31 2012
ERROR: Failed to execute /u01/oracle/WMSTST/db/tech_st/11.1.0/appsutil/clone/bin/adclone.pl
Please check logfile.
user4434301 wrote:Please see (On Release 12 adcfgclone is failing with AC-00423, RC-50014 adcrdb.sh missing from file system [ID 549872.1]).
I have since patched the source DB to the latest AD versions. The entire logfile from the latest attempt is linked above, but the error is here:
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
AutoConfig could not successfully instantiate the following files:
AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDBTechStack