You need to do the following:
- Run adpreclone on the database tier of the PROD system.
- Copy the appsutil from PROD to TEST.
- Run perl adcfgclone.pl database (to configure the new database)
So it is the appsutil from Db to Db and not the Apps to Db.
Wow! I learn new things everyday
I thought I am already expert in cloning.
So in case of disaster, how do you often update the appsutil of the Oracle_Home on the DR server?
What if, is case of disaster, I have RMAN backup only but the Oracle_Home was not backup
because we thought it was cloned already on the DR server?
Are there patches applied to PROD that are not in TEST. If that is the case, you need to clone the APPL_TOP/COMMON_TOP as well.
Normally, you can create the appsutil.zip form the appTier:
What were the exact errors from the DB autoconfig log, not the bottom, but where afdbprf.sh and adcrobj.sh actually failed?
Thanks Michael and Bashar
Actually I am not sure if I was able to clone the right way since it was long time ago.
I may not have run the adpreclone before and I lost track what are the patches applied.
I need to refresh again the cloning to be safe.
The appsutil is generated from the application tier as Michael mentioned.
However, if you have an Oracle database home that was cloned to another server (DR, for example) then you can copy the folder from the production server to the new one.
If you are cloning the database then you only need to copy the clone folder within the appsutil from production to the cloned environment.
If patches were applied on production database home then you need to clone the whole db tier.