Last updated on DECEMBER 21, 2016
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
******* Checked for relevance 16-OCT-2016 ********
How to relocate a database to a new server
You may need to restore a database to a new server due to the following reasons:
1) confirming your disaster recovery strategy
2) cloning a database to a new server for UAT or or PRE-PRODUCTION
3) moving the database to a new server
This note will work for all file systems - ASM, OCFS, raw, cooked etc.
The steps can be summarised as:
1) take a backup of the database on the existing host
2) on the new host, restore the controlfiles, datafiles and tempfiles to the new location
3) on the new host, rename the online redo logs
4) use NID to change db_name and dbid
Important Note: During the restore and recovery process, do NOT connect to the production database's recovery catalog, even if you are using one to perform the backup. The production database's recovery catalog will get confused if there are multiple databases with the same DBID.
1) the existing and new hosts are running on the same operating system and RDBMS patchsets. Restoring to a different platform and/or RDBMS patchset is quite complex and will not be addressed in this note.
2) all datafiles and tablespaces are onlined and accessible
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms