Rman client migration queston

[jouell]

Hi

We have a database we currently backup via rman and use the catalog. We have vdumped the db and control files over the network and are readying the new database on new hardware.
We will shutdown the old copy of the db, and bring up the new one on new hardware.

How do I make sure rman is ok with backing up the "new" copy of the database, which will have the same DBID as the old?


Thanks!
-John

 

[LKBrwnDBA]

If theDBID is the same, take a full RMAN backup of new database and you may only need to "synchronize" the archive logs:

SQL "ALTER SYSTEM CHECKPOINT";

ALLOCATE CHANNEL FOR MAINTENANCE TYPE DISK;
CHANGE ARCHIVELOG ALL CROSSCHECK;

----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

 

[jouell]

Oracle Tech says no change is needed.

however, I do automatic channel allocation w/legato networker , so I will update NSR_CLIENT variables for my RAC databases, and not a bad idea for single instance,too.