![]() ![]() Modify the initEBSPROD.ora parameter file in $ORACLE_HOME/dbs, to reflect the name change of any mount points on the EBSTEST server. Sample bin]$ perl dbTechStack Step 2:Īs an oracle (or equivalent) OS user on the target server (EBSTEST), modify the controlfile $HOME/EBSTEST_bkp/create_control_yyyymmdd.sql as follows:Įverything before the CREATE CONTROLFILE statement can be removed from the file.Īny directory paths of files will have to be amended, to reflect the name change of mount points.įor example: from EBSPROD to EBSTEST Step3: This step will register your RDBMS Oracle home to central inventory and relink RDBMS oracle home. Ps –eaf|grep ora -> shouldn’t return any ORACLE processesĬonfigure the. Log on to the target system as the ORACLE userĪs an oracle (or equivalent) OS user on the target server (EBSTEST), ensure you have no Oracle environment variables set.Įnv | grep ORA shouldn’t return any ORACLE environment variables Database Tier Cloning do it one source system (DEVELOPMENT) Step 1: ![]() Should return NOT ACTIVE which means that all files associated with all tablespaces are no longer in hot backup mode. With some guidance, you can craft a data platform that is right for your organization’s needs and gets the most return from your data capital. Do the following on the source system (Production)Īs an oracle OS user on the server, the Production environment then needs to be taken out of hot backup mode and the log files archived: TEST Systems engineer then you will need to perform a Flex clone of the “EBSPROD” volumes located on the NetApp Filers in the server’s and. Select distinct status from v$backup The systems engineer does the flex clone #Appcloner archive.org archiveSql > create pfile=’/home/oracle/EBSTEST_bkp/pfile_bkp.ora’ from spfile Step 2Īs an oracle OS user on the server, archive all log files and put the database in hot backup mode: On Target Server as oracle OS user take a backup of PFILE: Sql > create pfile from spfile ($ORACLE_HOME/dbs/initEBSPROD.ora) On the Source Server as an oracle OS user on the server, create a parameter file for starting the database later on: Shutdown the current instance – APPS, Database and DB Listener Step 2Ĭreate a backup of necessary files like – pfile, tnsnames, context file etc and copy under a folder in oracle user $HOME Step 3Ĭreate a backup of the context file and keep into /tmp or winscp to your desktopĬloning steps on Source and Target EBS system On the source system (Production) do the following STEP 1 Log File to Check: scripts]$ perl appsTier Steps on the Target Instance (DEVELOPMENT) Step 1 Log File to Check: EBSPROD_ebsproddb01]$ perl dbTier Step 2 (approx 15 mins)Īs an oracle OS user on the server, APPS server:Ĭd $COMMON_TOP/admin/scripts/$CONTEXT_NAME Steps to Follow When Cloning Steps on the Source Instance (Production) Step 1 (approx 15 mins)Īs an oracle OS user on the server, RDBMS server:Ĭd $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME The biggest challenge is ensuring that we do not disturb the production or clone within the development system. There are regular requests from developers to clone the production system and prepare the development for the EBS System. ![]() CLONING IN ORACLE EBS R12 PRODUCTION SYSTEM:Ĭloning plays an important role in the Oracle EBS Production system. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |