Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    Cloning a Database to Our Test Server Using RMAN

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 19.01

    Description:
    I was wanting to know if I can use the RMAN recovery procedure to clone our production database to our test server?

    This is the general procedure I'm suggesting:

    1. Shutdown oracle on test server.
    2. Wipe oracle database files and archivelogs.
    3. Restore oracle backup files and archivelogs from a tape backup of the production server to test.
    4. Restore backup files using typical RMAN procedure for database recovery.

    Would that work? In addition, here is the RMAN recovery process I've used in the past when recovering a database to its original server:

    RMAN> set DBID 845168234;
    RMAN> startup nomount;
    RMAN> set CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/wrkspc1/backup_files/aleph17_10_ora_hot_control_file_%F';
    RMAN> RESTORE CONTROLFILE FROM AUTOBACKUP;
    RMAN> alter database mount;
    RMAN> restore database;
    RMAN> recover database;
    RMAN> alter database open resetlogs;

    Are there any alternate or additional steps than need to be taken?

    We're planning on shutting off access to our production server over the Christmas weekend, and would like to have an updated version of the database on our test server to use during the downtime.

    Resolution:
    Eyal says about this: "Yes, as long as the location/path of the datafiles + the DB name is that same, this is the correct way."

    • Article last edited: 10/8/2013