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 Preparation
- 1.1 Backup db tier database(s)
- 1.2 Check disk space for clone is sufficient
- 1.3 Save important data on target database(s) before destroying
- 1.3.1 Export dba_directories
- 1.3.2 Export dba_db_links
- 1.3.3 Verify the db links still work on the target (may need pointing somewhere else afterwards)
- 1.3.4 Save user passwords
- 1.3.5 Modify file location spfile parameters
- 1.3.6 Save SQL baselines
- 1.3.7 Save SQL profiles
- 1.3.8 Save context file on apps tier
- 1.3.9 Create a pfile from spfile
- 1.3.10 Add source database to target tnsnames.ora
- 1.3.11 Preclone the source db tier
- 1.3.12 Preclone the source apps tier
- 2 Perform clone
- 3 Post clone
- 3.1 Check datafile status
- 3.2 Restart database cleanly
- 3.3 Put back context file on apps tier
- 3.4 Register target database(s) with RMAN catalog
- 3.5 Stop target listener
- 3.6 link gcc
- 3.7 Check unzip version
- 3.8 Postclone the target db tier
- 3.9 Start target listener
- 3.10 Check spfile parameters
- 3.11 Clean up some directories on apps tier
- 3.12 Postclone the target apps tier
- 3.13 Change sysadmin password
- 3.14 Run Autoconfig on target database(s)
- 3.15 Check database is up
- 3.16 Restore dba_directories to target database(s)
- 3.17 Restore db links to target database(s)
- 3.18 Check utl_file_dir and APPLPTMP
- 3.19 Run Autoconfig on apps tier
- 3.20 Start apps tier services
- 3.21 Check Concurrent Manager status
- 3.22 Check Applications Dashboard
- 3.23 Execute Diagnostics tests
- 3.24 Run Concurrent Report "Activity Based Management (Obsolete)"
- 3.25 Change Site Name profile option value
- 3.26 Change Title header on portal login screen
- 3.27 Clear apps tier cache
- 3.28 Restart web server
- 3.29 Update other profile option values
- 3.30 Test concurrent program with known values to check consistency
- 3.31 Relink any .prog files to fndcpesr
- 3.32 Restore user passwords on target database(s)
- 3.33 Test db links
- 3.34 Set AWR parameters
- 3.35 Recreate nologging indexes
- 3.36 Fake stats on some tables
Preparation
Assuming there is already a target (clone) that will be destroyed in the process.
