Professional Documents
Culture Documents
Cloning EBS R12: A Step by Step Detailing by Orazer Technologies
Cloning EBS R12: A Step by Step Detailing by Orazer Technologies
Pre-Tasks:
• Bring down taget system’s services.
www.orazer.com 4
6. Once the backups are cataloged we can restore the database usig the
PROD’s backup. But the database files are pointing to PROD’s location so it
will try to restore the datafiles to PROD’s location which may not exist in
target.
Ex: /u01/oracle/PROD/data/system01.dbf
Note : Below script can be used to create the script for “SET NEWNAME”.
Change the path of target datafile location and run the script in source.
www.orazer.com 5
7. Restore and recover the database
Ex:
Rman>run {
set until time “to_date(’16/07/2015 23:20:00′,’dd/mm/yyyy hh24:mi:ss’)”;
set newname for datafile 1 to ‘/u01/oracle/TEST/system.dbf’;
set newname for datafile 44 to ‘/u01/oracle/TEST/apps_ts_tx_data_01.dbf’;
set newname for datafile 76 to ‘/u01/oracle/TEST/apps_ts_tx_idx01.dbf’;
set newname for datafile 35 to ‘/u01/oracle/TEST/sysaux_01.dbf’;
set newname for datafile 37 to ‘/u01/oracle/TEST/undotbs1_01.dbf’;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
restore database;
switch datafile all;
recover database;
release channel ch1;
release channel ch2;
}
After the database is restored and recovered then open the database using
resetlogs.
SQL> alter database open resetlogs;www.orazer.com 6
Post Steps:
1. Recreate ALL the temp tablespaces. If not done then DB will not be
opened after renaming.
Sql> select tablespace_name from dba_tablespaces where
tablespace_name like ‘%TEMP%’;
TEMP
TEMP1
Create a new temp tablespace
create TEMPORARY TABLESPACE temp2 tempfile
‘/u01/oracle/TEST/temp2.dbf’ size 2048M;
6. Drop TEMP2
6.1 Stop the database and startup in mount mode using same modified pfile
Sql> shutdown immediate;
Sql > startup mount pfile=’/backup/clone/initTEST.ora’
www.orazer.com 8
6.3 Once the database is renamed the nid command will bring down the
database. Start it using the old pfile in ORACLE_HOME/dbs. (which has
db_name as TEST)
Sql>startup mount
Sql>alter database open resetlogs;
Note : Disable archive log if needed.
6.4 After db is opened, cleanup the FND NODE details using below script.
Run it as apps user.
SQL> conn apps/<appspwd>
Connected.
SQL> show user
USER is “APPS”
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
commit;
6.4 Run auto-config on DB Tier after ensuring that the DB and listener are up
and running.
$ cd $ORACLE_HOME/appsutil/scripts/TEST_dmdev02/./ adautocfg.sh
www.orazer.com 9
Steps to Clone Application:
1. Ensure the file system copy completed successfully on the application tier.
Compare the size (du –sh) output with production for same content.
$ pwd
/u01/oracle/TEST/apps
$ du -sh apps_st tech_st
39303540 apps_st
9237724 tech_st
2. Set Primary and secondary nodes and set all Pending requests on hold.
update fnd_concurrent_queues set node_name=’DMDEV02′ where
node_name is not null;
3. Check the old $INST_TOP is removed completely before starting the next
step.
cd /u01/oracle/TEST/apps/apps_st/comn/clone/bin
perl adcfgclone.pl appsTier <Path of the context_file that was saved in Pre
Task B>
www.orazer.com 10
4. Stop the concurrent managers and workflow.
www.orazer.com 11
10. Run cmclean.sql
12. Start all the services except the concurrent managers. CM’s should not be
started until Security team complete their post clone activities.
13. Login to the application using login page and launch the forms.
14. Change the Site Name to the name of the current environment with
information of the Refreshed time
www.orazer.com 12
Issues
R12: “FRM-92101: There was a failure in the Forms Server during startup”
Error When Attempting to Launch Forms
(Doc ID 454427.1)
www.orazer.com 13