PERFORMING RMAN CLONING ON DIFFERENT SERVERS

PERFORMING RMAN CLONING ON DIFFERENT SERVERS

In this article we will implement RMAN Cloning on different servers.

Server 1 :

Check instance information on server 1 

Check schema report by connecting RMAN 

Check archive-log  

Shutdown the database and keep database in mount state (consistent backup) 

Take the backup of primary using RMAN 

Server 2 :

Export  new SID 

Create new directory structure for CRD file and ARCHIVE LOG files

Create same directory as prod to store RMAN backup files

Server 1 :

Send all the backup files from primary to clone server using SCP

Create passwd and send to clone server 

Server 2 :

Rename pfile and passwd file

Edit pfile and change locations

Create the listener 

Start the listener

Startup the database in mount state 

Server 1 :

Create TNS entry in primary server

Check connectivity 

Connect to target using auxiliary instance using RMAN and issue duplicate command 

Execute the following duplicate target command to complete cloning 

Issue DUPLICATE COMMAND 

Cloning completed…….

Server 2:

Now in Server -2 check the instance information 

Here in above result the database is still mount state

Make clone database as read write

For clear understanding check below screenshot

 

Check controlfile_type in clone database 

Here it is clone controlfile ….. if we want to make it as current we need to recreate the controlfile.

 

Thanks for browsing ktexperts.com ….

 

 

Note: Please test scripts in Non Prod before trying in Production.
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading...

Add Comment