Changing the DBID and Database Name   Leave a comment

Changing the DBID and Database Name
The following steps describe how to change the DBID of a database. Optionally, you can change the database name as well.
  1. Ensure that you have a recoverable whole database backup.
  1. Ensure that the target database is mounted but not open, and that it was shut down consistently prior to mounting. For example:
  1. Invoke the DBNEWID utility on the command line, specifying a valid user with the SYSDBA privilege. For example:
To change the database name in addition to the DBID, specify the DBNAME parameter. This example changes the name to ORCL2
The DBNEWID utility performs validations in the headers of the datafiles and control files before attempting I/O to the files. If validation is successful, then DBNEWID prompts you to confirm the operation (unless you specify a log file, in which case it does not prompt), changes the DBID for each datafile (including offline normal and read-only datafiles), and then exits. The database is left mounted but is not yet usable. For example:
DBNEWID: Release
(c) Copyright 2002 Oracle Corporation.  All rights reserved.
Connected to database ORCL1 (DBID=5463293245)
Control Files in database:
Change database id of database to ORCL2? (Y/[N]) => y
Proceeding with operation
    Datafile /oracle/dbs/tbs_01.f – changed
    Datafile /oracle/dbs/tbs_02.f – changed
    Datafile /oracle/dbs/tbs_11.f – changed
    Datafile /oracle/dbs/tbs_12.f – changed
    Datafile /oracle/dbs/tbs_21.f – changed
New DBID for database ORCL2 is 534256732.
All previous backups and archived redo logs for this database are unusable
Proceed to shutdown database and open with RESETLOGS option.
DBNEWID – Database changed.
If validation is not successful, then DBNEWID terminates and leaves the target database intact. You can open the database, fix the error, and then either resume the DBNEWID operation or continue using the database without changing its DBID.
4. After DBNEWID successfully changes the DBID, shut down the database:
7.   Open the database in RESETLOGS mode and resume normal use. For example:
8.   Make a new database backup. Because you reset the online redo logs, the old backups and archived logs are no longer usable in the current incarnation of the database.

Posted October 3, 2013 by in Oracle10g/11g

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: