Pages

Monday, July 25, 2016

High Level Clonning Steps

Preclonning Steps

1 Comment jobs
2 Blackout Target Instance in OEM
3 Take a backup of IMP files
4 Stop Application services on Target.
5 Unregister target database from RMAN catalog
6 Shutdown database services and  listener on all two RAC DB nodes on target using srvctl
7 Drop the target ( Cloning )  Database from node1
8 Remove Oracle homes registered in Global Inventory.
9 Remove target listener and database from cluster.


Database Cloning

1 Copy and Configure the RDBMS FS from Source to Target system
2 Remove the RDBMS Homes of Target database in all the nodes
3 Copy Oracle Home from source DB nodes to their respective target database nodes using rsync.
4 Register the RDBMS Homes in central Inventory on all RAC nodes.
5 Check inventory output on all DB nodes.
6 Make sure following TNS_ADMIN folder exists on all two DB nodes otherwise create them.
7 Create SPFILE & Recreate password file using system password in all DB nodes.
8 Enter the source DB , RMAN  TNS entries manually in Target tnsnames.ora on primary DB node.
9 Verify communication between the databases and RMAN catalog.
10 Starup Instance in no mount with rman restore pfile from db node1:
11 Start RMAN DB restoration.
12 Disable Archive log mode only for STAGE & DEV instances.
13 Ensure UNDO tablespace exists for each database instance.
14 Verify the redolog entries in the database
15 Ensure diskgroup for the target DB is online on all nodes
16 Register database and instances with Oracle Cluster Registry (OCR)
17 Verify database status using srvctl.
18 Create local and remote listener tnsnames.ora aliases using netca
19 Check the status of listener using srvctl

Configure the DB Tier

1 Run fnd_conc_clone.setup_clean as APPS user from node1
2 Generate  Context files on Database nodes. primary DB node
3 Generate Context file on primary DB node
4 Configure the RDBMS home.
5 Run the library update script against the RAC database.
6 Configure the primary target database 
7 Create softlink of of init.ora under $ORACLE_HOME/dbs
8 Generate Context file on secondary DB node.
9 Configure RDBMS homes on secondary DB nodes.
10 Update tnsnames/listener/sqlnet files under $ORACLE_HOME/network/admin on all DB nodes.
11 Update the listener/database environment in OCR
12 Run  autoconfig in all DB nodes.
13 Restart database and listeners

Application Clone

1 Verify nfs mount options of Application file system.
2 Remove Target Application Binaries and Copy EBSapps content from Source RUN edition
3 Configure the Target Primary application RUN edition.
4 Run adpreclone.pl on the run edition file system in the Target System.
5 Copy the run edition file system to the patch edition file system in the Target System.
6 Configure the Target Primary application PATCH edition.
7 Verify and Update the $CONTEXT_FILE in RUN edition on primary node.
8 Verify and Update the $CONTEXT_FILE in PATCH edition on primary node.
9 Run autoconfig in both RUN And PATCH edition on primary node.
 SCALE UP of application node
1 Prepare the Pairs File for configuring the RUN File System on 2nd node
2 Prepare the Pairs File for Configuring the Patch File System on 2nd node
3 Start ADMIN server in both RUN and patch edition on Primary application node
4 Configure the Run File System on the Secondary Node
5 Configure the Patch File System on the Secondary Node
6 Add new oacore managed servers ( Only on STAGE Instances )
7 Register the new topology from the newly added application tier node
8 Update/Verify the application context file only on secondary App. Node.
9 Run autoconfig in RUN and PATCH edition on both application nodes.
10 Synchronize the context files on both application nodes
11 Add new managed servers in OHS configuration files on primary application node
12 Add new managed servers in OHS configuration files on secondary node
13 Change APPS/APPLSYS  schema password
14 Change SYSADMIN Password.
15 Create DNS status check file in both app. Nodes.
16 Verify the target and source DBID should not be same.
17 Register the DB in Catalog
18 OAM Registration
19 OAM datasource timeout settings
20 Start the Application services.

2 comments:

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete