When doing database refresh for EBS databases, the following steps may save time on completing the clone faster…

Copy the code relevant to your environment to a file and run the script file prior to the clone to save the configuration information. Once database refresh completed, you may restore the values to the database and then run autoconfig to complete the clone.

Saving Information Before Clone

1. Define a directory path in wbackupdir variable, where the backup scripts are saved.

2. Save the $CONTEXT_FILE on database node

3. Save the database parameter file

Following items are saved, logged into the database.

Each item will be saved to separate files, thus can be run separately if needed after database refresh.

4. Save database read-only users, user accounts used in db links, etc whose password need to be preserved.

 

5. To preserve the database links, we use expdp. But need to drop the database links before doing the import. Following code will generate database link drop statements [only drop private DB Links under APPS user].

6. Save the profile values that need to be preserved. Second SQL capture site level profile values of interest. Add/remove as appropriate for your environment.

 

 

 

7. Save Oracle Directories created in the DB

 

8. Export the APPS owned DB Links

 

Perform the Database Refresh

After the information is saved from the database, you may do the following steps to complete the database copy process.

  1. Shutdown EBS and Database Sevices
  2. Startup database in mount status, restricted mode
  3. Drop database
  4. Restore the initialization parameter file saved in step 3
  5. Using RMAN or other methods, perform clone of the database [RMAN duplicate].

 

Post Database Refresh Configuration

Clear source node information from FND_NODES and other configuration tables.

Using the $CONTEXT_FILE, run autoconfig on the database node.

Now, you should see the database node name in the FND_NODES table.

Restore Saved Configuration Information

Restore DB Links under APPS

 

If you are not interested in the AWR and audit information in the clone instance, you may truncate those tables…

 

Complete the Clone on the EBS Nodes

Change APPS, ALLORACLE, any custom schema passwords using FNDCPASS to match the passwords before the database refresh.

Now execute autoconfig on all EBS nodes to complete the clone.

 

Hope this helps… Have fun!

PS: Please comment on the approach and method. If there is better, faster, easier method, would love to know. Here the assumption is all patch levels on the database side and EBS side are same, just need more recent data in the non-production instance for testing purposes.

 

%d bloggers like this: