Clone E-Business Suite (EBS) database
From dbawiki
This will be a living document for a while as I change it with each successful clone I do!
Not all of these steps will be necessary in all cases. Some are specific to this particular installation.
Contents
- 1 Topology
- 2 Preparation
- 2.1 Backup the source db tier database(s)
- 2.2 Check disk space for clone is sufficient
- 2.3 Export dba_directories
- 2.4 Export dba_db_links
- 2.5 Verify the db links still work on the target (may need pointing somewhere else afterwards)
- 2.6 Save user passwords
- 2.7 Modify file location spfile parameters
- 2.8 Save SQL baselines
- 2.9 Save SQL profiles
- 2.10 Save context file on apps tier
- 2.11 Create a pfile from spfile
- 2.12 Add source database to target tnsnames.ora
- 2.13 Preclone the source db tier
- 2.14 Preclone the source apps tier
- 3 Perform clone
- 4 Post clone
- 4.1 Check datafile status
- 4.2 Restart database cleanly
- 4.3 Put back context file on apps tier
- 4.4 Register target database(s) with RMAN catalog
- 4.5 Stop target listener
- 4.6 link gcc
- 4.7 Check unzip version
- 4.8 Postclone the target db tier
- 4.9 Start target listener
- 4.10 Check spfile parameters
- 4.11 Clean up some directories on apps tier
- 4.12 Postclone the target apps tier
- 4.13 Change sysadmin password
- 4.14 Run Autoconfig on target database(s)
- 4.15 Check database is up
- 4.16 Restore dba_directories to target database(s)
- 4.17 Restore db links to target database(s)
- 4.18 Check utl_file_dir and APPLPTMP
- 4.19 Run Autoconfig on apps tier
- 4.20 Start apps tier services
- 4.21 Check Concurrent Manager status
- 4.22 Check Applications Dashboard
- 4.23 Execute Diagnostics tests
- 4.24 Run Concurrent Report "Activity Based Management (Obsolete)"
- 4.25 Change Site Name profile option value
- 4.26 Change Title header on portal login screen
- 4.27 Clear apps tier cache
- 4.28 Restart web server
- 4.29 Update other profile option values
- 4.30 Test concurrent program with known values to check consistency
- 4.31 Relink any .prog files to fndcpesr
- 4.32 Restore user passwords on target database(s)
- 4.33 Test db links
- 4.34 Set AWR parameters
- 4.35 Recreate nologging indexes
- 4.36 Fake stats on some tables
Topology
src_ebs_host
|
!-> SRC_AD_DB
!-> SRC_EBS_DB
src_apps_host
|
!-> SRC_APPS
tgt_ebs_host
|
!-> TGT_AD_DB
!-> TGT_EBS_DB
tgt_apps_host
|
!-> TGT_APPS
Preparation
Assuming there is already a target (clone) that will be destroyed in the process.
Backup the source db tier database(s)
The clone will be taken using RMAN as it is quicker than copying the datafiles if the database(s) are big.
Check if the last successful backup was not too long ago (to avoid rolling forward too much).
Check disk space for clone is sufficient
If we are refreshing an existing clone, the chances are that there is already enough space.
du -gs <source datafile filesystem> A
du -gs <destination datafile filesystem> B df -g <destination datafile filesystem> (find space remaining) C
Space remaining after clone on destination is : (B+C)-A
If this is positive, there will be enough space.
Export dba_directories
Do this on the destination to preserve any directories. They can be imported back in after the clone has overwritten them.
