Skip to main content

Posts

Showing posts with the label Cloning

During adop phase=prepare get ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

This is one of those where I'm left scratching my head. During the clone I was getting issues with the LOCAL_LISTENER parameter. The clone would not complete with this value set. Now when I go and create a new adop session using adop phase=prepare I get the following error [ERROR]     Cannot connect to database [ERROR]     Error Message: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor (DBD ERROR: OCIServerAttach) I found a note to fix the issue and what does it say. I need to set the LOCAL_LISTENER. So I set the listener and now it runs. Again I'm lost for words with this new system of cloning and patching in R12.2 Reference adop phase=prepare fails with: Error Message : ORA-12514: TNS:listener does not currently know of service requested in connect descriptor (Doc ID 2007225.1)

R12.2 Rapid Clone using cold backup

Database Tier Because this is a cold backup of the database only need to run dbTier and it will do the rest for you. Thanks to Arty for this little jewel. cd $ORACLE_HOME/appsutil/clone/bin perl adcfgclone.pl dbTier Application Tier Run File System In R12.2 it has some check on the oraInst file. Make sure its there with the valid locations. vi /etc/oraInst.loc inventory_loc=/u03/APPLTEST/oraInventory inst_group=dba Remove the oracle inventory directory that you reference in oraInst. You could deregister or start messing around with the xml file but I found it easier to simply delete the directory. rm -rf /u03/APPLTEST/oraInventory Check which is the run file system grep s_file_edition_type /u03/APPLTEST/TEST/fs1/EBSapps/comn/clone/context/apps/TEST_erpapprod.xml grep s_file_edition_type /u03/APPLTEST/TEST/fs2/EBSapps/comn/clone/context/apps/TEST_erpapprod.xml Because this is a snapshot of PROD I have to remove some of the files that aren't required. Oracle...

Error during rapid clone on pasteBinary.sh, exit code 255

I needed to run a clone and was running into a really head scratcher. As is Oracle\'s way they sometimes enjoy giving us DBA's a bit of detective work to do. As usual I kept knocking my head into various brick walls instead of tracking back through the logs. Eventually I came up with the problem Start to configure the run filesystem. You can do a dualfs from AD-TXK Delta 7 but for now I just needed to get this up and running: perl adcfgclone.pl appsTier START: Creating FMW Home. Running /u03/APPLUAT/UAT/fs1/EBSapps/comn/clone/FMW/ pasteBinary.sh -javaHome /u03/APPLUAT/UAT/fs1/EBSapps/comn/util/jdk64 -al /u03/APPLUAT/UAT/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl /u03/APPLUAT/UAT/fs1/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl /u03/APPLUAT/UAT/fs1/inst/apps/UAT_erpapp05/admin/log/clone/fmwT2PApply -silent true -debug true -executeSysPrereqs false Script Executed in 21933 milliseconds, returning status 255 ERROR: Script failed, exit code 255 Oracle has left me a cryptic ...

Creating new WLS domain ends with exit code 255

Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file. START: Creating new WLS domain. Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt Script Executed in 1903 milliseconds, returning status 255 ERROR: Script failed, exit code 255 Dig a bit deeper into the log files cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply cat CLONE2016-01-10_04-37-...

Moving Concurrent Log files when cloning or changing servers

Mount old file system in new server so that you can copy the files over. Replace $[OLD_APPLCSF] ,$[NEW_APPLCSF] and [PROD] with your local settings rsync -a $[OLD_APPLCSF]/log/ $[NEW_APPLCSF]/log/ rsync -a $[OLD_APPLCSF]/out/ $[NEW_APPLCSF]/out/ Need to update the concurrent request table that stores the log file and out file locations update APPLSYS.FND_CONCURRENT_REQUESTS fcr set fcr.LOGFILE_NAME = replace  (FILE_NAME,'$[OLD_APPLCSF]','$[NEW_APPLCSF]') ,fcr.LOGFILE_NODE_NAME= '[PROD]' ,fcr.OUTFILE_NAME = replace  (OUTFILE_NAME,'$[OLD_APPLCSF]','$[NEW_APPLCSF]') ,fcr.outFILE_NODE_NAME= '[PROD]'; For Bi Publisher there is also the additional file that is created and this needs to be updated in FND_CONC_REQ_OUTPUTS. Sneaky one that I later found. update APPLSYS.FND_CONC_REQ_OUTPUTS set FILE_NAME = replace  (FILE_NAME,'$[OLD_APPLCSF]','$[NEW_APPLCSF]') ,FILE_NODE_NAME = '[PROD]';