Make a whole database backup.

Invoke SQL*Plus and connect as a user with SYSDBA privileges.

Issue the following query to determine the current DBID:

SELECT dbid, name
FROM v$database;

Shut down the instance using the NORMAL, IMMEDIATE, or TRANSACTIONAL options:

SHUTDOWN IMMEDIATE

Start the instance and mount the database, specifying the parameter file if you are not using a server parameter file or the text initialization parameter file is not in the default location:

STARTUP MOUNT

Invoke the DBNEWID utility on the command line, specifying a valid user with the SYSDBA privilege. The DBNEWID utility performs validations of the headers of the data files 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, changes the DBID for each data file (including offline normal and read-only data files), and then exits. The database is left mounted but is not yet usable.

nid TARGET=SYS/secure@<service_name>

After DBNEWID successfully changes the DBID, shut down the instance:

SHUTDOWN IMMEDIATE

Create a new password file using the ORAPWD utility:

orapwd file=orapw<SID> password=<your password> entries=

Start the instance and mount the database:

STARTUP MOUNT;

Open the database with the RESETLOGS option:

ALTER DATABASE OPEN RESETLOGS;

Verify the change to the DBID by issuing the following query:

SELECT dbid, name
FROM v$database;

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.

Make a whole database backup.

Invoke SQL*Plus and connect as a user with SYSDBA privileges.

Issue the following query to determine the current database name:

SELECT name
FROM v$database;

Shut down the instance using the NORMAL, IMMEDIATE, or TRANSACTIONAL options:

SHUTDOWN IMMEDIATE

Start the instance and mount the database, specifying the parameter file if you are not using a server parameter file or the text initialization parameter file is not in the default location:

STARTUP MOUNT

Invoke the DBNEWID utility on the command line, specifying a valid user with the SYSDBA privilege. You must specify the DBNAME parameter and supply your new database name. You must also specify the YES value for the SETNAME parameter to indicate that only the DBNAME is to be changed. DBNEWID performs validations of the headers of the control files, but not the data files, before attempting I/O to the files. If validation is successful, then DBNEWID prompts for confirmation, changes the database name in the control files, and exits. After DBNEWID completes successfully, the database is left mounted but is not yet usable.

nid TARGET=<username>/<password>@<servicename> DBNAME=<newname> SETNAME=YES

After DBNEWID successfully changes the database name, shut down the instance:

SHUTDOWN IMMEDIATE

Change the DB_NAME initialization parameter to your new database name.

Create a new password file using the ORAPWD utility:

orapwd file=orapw<SID> password=<your password> entries=

Start the instance and open the database:

STARTUP

Verify the change to the database name by issuing the following query:

SELECT name
FROM v$database;

Make a whole database backup.

Invoke SQL*Plus and connect as a user with SYSDBA privileges.

Issue the following query to determine the current database identifier and database name:

SELECT dbid, name
FROM v$database;

Shut down the instance using the NORMAL, IMMEDIATE, or TRANSACTIONAL options:

SHUTDOWN IMMEDIATE

Start the instance and mount the database, specifying the parameter file if you are not using a server parameter file or the text initialization parameter file is not in the default location:

STARTUP MOUNT

Invoke the DBNEWID utility on the command line, specifying a valid user with the SYSDBA privilege. You must specify the DBNAME parameter and supply your new database name. DBNEWID performs validations of the headers of the control files and the data 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, changes the DBID for each data file (including offline normal and read only files), changes the database name in the control file, and exits. After DBNEWID completes successfully, the database is left mounted but is not yet usable.

nid TARGET=<username>/<password>@<service name> DBNAME=<new name>

After DBNEWID successfully changes the database identifier and database name, shut down the instance:

SHUTDOWN IMMEDIATE

Change the DB_NAME initialization parameter to your new database name.

Create a new password file using the ORAPWD utility:

orapwd file=orapw<SID> password=<your password> entries=

Start the instance and mount the database:

STARTUP MOUNT

Open the database with the RESETLOGS option:

ALTER DATABASE OPEN RESETLOGS;

Verify the change to the database name and database identifier by issuing the following query:

SELECT name, dbid
FROM v$database;

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.

Invoke SQL*Plus and connect as a user with SYSDBA privilege.

Issue the following query to determine the current database name:

SELECT name
FROM v$database;

Issue the following command to force a checkpoint:

ALTER SYSTEM CHECKPOINT;

Issue the following command to create a trace file containing the statements to re-create the control file:

ALTER DATABASE BACKUP CONTROLFILE TO TRACE RESETLOGS;

Locate the trace file created in step 4. The trace file will be in the location specified by the USER_DUMP_DEST initialization parameter. The file will be named ora_NNNN.trc. You can find the value of USER_DUMP_DEST by issuing the following command:

SHOW PARAMETER USER_DUMP_DEST

Change the value of the DB_NAME initialization parameter to your new database name.

Shut down the instance using the NORMAL, IMMEDIATE, or TRANSACTIONAL options:

SHUTDOWN IMMEDIATE

Copy the contents of the trace file beginning with the STARTUP NOMOUNT command to a new file. For the purposes of this example, assume you have named the new file ccf.sql.

Edit your ccf.sql file and make the following changes:

Remove all of the comment lines. Your script should begin with the CREATE CONTROLFILE statement.

Change:
CREATE CONTROLFILE REUSE DATABASE "olddbname" RESETLOGS
To:
CREATE CONTROLFILE SET DATABASE "newdbname" RESETLOGS

Remove the RECOVER DATABASE USING BACKUP CONTROLFILE statement:

Rename your existing control files to provide a backup.

Invoke SQL*Plus and connect as a user with SYSDBA privileges.

Execute your ccf.sql script to re-create the control file. The script starts the instance in NOMOUNT mode and re-creates the control file. The script opens the database.

@ccf

Change your global database name if required by issuing the following command.

ALTER DATABASE 
RENAME GLOBAL_NAME to <newdbname>.<domain>;

Verify your changes by issuing the following query to find the current value of DB_NAME:

SELECT name FROM v$database;

Make a whole consistent (full or complete) database backup using Recovery Manager (RMAN) or operating system commands.