Hi Erman,
Hope you are doing well. We are planning to upgrade our EBS database from 11g to 19c. So we have recently upgraded one of our EBS test instance database from 11g to 19c. The upgrade was successful. Now this is the first time we are trying to clone a 19c instance into a another new server . We are following doc id 2560690.1 .The preclone on both dbtier and appstier ran fine. But when we are trying to run adcfgclone dbtechstack on target its failing. Following are the steps we have done so far. in target server. after extracting the db binary. [ebsclonedb@ccuine105 bin]$ perl adclonectx.pl contextfile=/u01/ebsclone/db/tech_st/19.3.0/appsutil/EBS19C_ccuine102.xml template=/u01/ebsclone/db/tech_st/19.3.0/appsutil/template/adxdbctx.tmp ... ... ... The new database context file has been created : /u01/ebsclone/db/tech_st/19.3.0/appsutil/EBSCLONE_ccuine105.xml export ORACLE_BASE=/u01/ebsclone/db export ORACLE_HOME=/u01/ebsclone/db/tech_st/19.3.0 export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$ORACLE_HOME/OPatch:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=/u01/ebsclone/db/tech_st/19.3.0/perl/lib/5.28.1:/u01/ebsclone/db/tech_st/19.3.0/perl/lib/site_perl/5.28.1:/u01/ebsclone/db/tech_st/19.3.0/perl/lib export ORA_NLS10=/u01/ebsclone/db/tech_st/19.3.0/nls/data/9idata export ORACLE_SID=EBSCLONE export ORACLE_PDB_SID=EBSCDB cd /u01/ebsclone/db/tech_st/19.3.0/appsutil/clone/bin $perl adcfgclone.pl dbTechStack /u01/ebsclone/db/tech_st/19.3.0/appsutil/EBSCLONE_ccuine105.xml [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> [APPLY PHASE] AutoConfig could not successfully execute the following scripts: Directory: /u01/ebsclone/db/tech_st/19.3.0/perl/bin/perl -I /u01/ebsclone/db/tech_st/19.3.0/perl/lib/5.28.1 -I /u01/ebsclone/db/tech_st/19.3.0/perl/lib/site_perl/5.28.1 -I /u01/ebsclone/db/tech_st/19.3.0/appsutil/perl /u01/ebsclone/db/tech_st/19.3.0/appsutil/clone ouicli.pl INSTE8_APPLY 1 AutoConfig is exiting with status 1 RC-50013: Fatal: Instantiate driver did not complete successfully. /u01/ebsclone/db/tech_st/19.3.0/appsutil/driver/regclone.drv We have already raised SR for this. It has been a week and oracle has not been able to help in this regard. Looking for your assistance in this regard. Thanks. |
Administrator
|
It fails while executing the perl -> ouicli.pl
If it is Solaris, please see -> Clone 12.1.3 With Multitenant (19c) Fails running Adcfgclone.pl DbTechStack "RC-50013: Fatal: Instantiate driver did not complete successfully" (Doc ID 2637140.1) --pkg install pkg://solaris/system/kernel/oracka If it is not, check the OS-related things.. I mean packages, swap size and so on.. Ensure you have executed a proper preclone on source, as well. Ensure your inventory is okay.. Also verify file oraInst.loc is owned by the DB installer owner.. Ensure your /etc/hosts file is proper. So check these kinds of things.. Also check the installActions* log.. There may be a "make" or relink problem there, logged in that log so we need to see to be sure about the actual cause.. There are lots of documented issues on this.. So this can be fixed.. |
Hi erman,
Thanks for your reply. My environment is OEL 7 i have already chcecked all packages ,swap size , /etc/hosts entry etc are ok. Beside we have 3 other instance running on this server so i think from OS perspective it is ok. /etc/oraInstc.loc is owned by the db user . this is my host file entry [ebsclonedb@ccuine105 InstallActions2021-06-29_11-53-11AM]$ cat /etc/hosts 127.0.0.1 localhost.localdomain localhost #127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 #::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.10.5 ccuine105.eveready.co.in ccuine105 I didnt find any issue inside installActions*.log file as well. |
Hi Erman,
I have resolved the issue. Looks like the cloning was getting failed due to 8GB of its size. After increasing it to 16 gb it got resolved. Thanks for the pointer. Thanks once again for the help. Regards, Soumya |
Administrator
|
Perfect :) you see it is caused by some things below us (OS and below -- computational resources in this case).. Swap size might also cause this, but 8GB memory is the cause as you said. Glad that you solved it..
|
Free forum by Nabble | Edit this page |