Escolar Documentos
Profissional Documentos
Cultura Documentos
DBNEWID Utility
Prior to the introduction of the DBNEWID utility alteration of the internal DBID of
an instance was impossible and alteration of the DBNAME required the creation
of a new control file. The DBNEWID utility allows the DBID to be altered for the
first time and makes changing the DBNAME simpler. Changing the DBID is
necessary when you want to use an RMAN catalog to backup a cloned instance.
RMAN identifies instances using the DBID, preventing the original and cloned
instance being managed by the same catalog. Alteration of the BID in the cloned
instance removes this restriction.
• Invoke the DBNEWID utility (nid) specifying the new DBNAME from the command line
using a user with SYSDBA privilege:
Assuming the validation is successful the utility prompts for confirmation before
performing the actions. Typical output may look something like:
SHUTDOWN IMMEDIATE
• Modify the DB_NAME parameter in the initialization parameter file. The startup will result
in an error but proceed anyway.
• STARTUP MOUNT
• ALTER SYSTEM SET DB_NAME=TSH2 SCOPE=SPFILE;
SHUTDOWN IMMEDIATE
If you are using UNIX/Linux simply reset the ORACLE_SID environment variable:
• Alter the listener.ora and tnsnames.ora setting to match the new database name and
restart the listener:
lsnrctl reload