Not too long ago, I discovered:
dbca does hard coding
Now it gets even worse.
Create TEST environment.
SOURCE ORACLE_HOME:/u01/app/oracle/product/12.1.0/db_1
TARGET ORACLE_HOME:/u01/app/oracle/product/12.1.0/db
DB was cloned from Source to Target.
datapatch failed due to different OH and hard coding from dba_directories as shown below.
SOURCE:
OPATCH_LOG_DIR /u01/app/oracle/product/12.1.0/db_1/QOpatch
OPATCH_SCRIPT_DIR /u01/app/oracle/product/12.1.0/db_1/QOpatch
OPATCH_INST_DIR /u01/app/oracle/product/12.1.0/db_1/OPatch
TARGET:
OPATCH_LOG_DIR /u01/app/oracle/product/12.1.0/db/QOpatch
OPATCH_SCRIPT_DIR /u01/app/oracle/product/12.1.0/db/QOpatch
OPATCH_INST_DIR /u01/app/oracle/product/12.1.0/db/OPatch
I don’t get it! Why not use relative versus absolute path?
You might ask, “Why is the target different!”
To be honest, in this specific case, it should not have been.
BUT there may be scenarios where OH is already used and new location, i.e. db_2, is required.
Looking forward to Oracle AI – sarcasm.
