Skip to main content

CHANGING DBID FOR ORACLE DATABASE 11G




C:\Users\computer>sqlplus

SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:03:33 2013

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Enter user-name: sys as sysdba
Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select dbid from v$database;

      DBID
----------
2188161033

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

C:\Users\computer>nid

DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:04:44 2013

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Keyword     Description                    (Default)
----------------------------------------------------
TARGET      Username/Password              (NONE)
DBNAME      New database name              (NONE)
LOGFILE     Output Log                     (NONE)
REVERT      Revert failed change           NO
SETNAME     Set a new database name only   NO
APPEND      Append to output log           NO
HELP        Displays these messages        NO


C:\Users\computer>sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:05:26 2013

Copyright (c) 1982, 2008, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select dbid from v$database;

      DBID
----------
2188161033

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area  535662592 bytes
Fixed Size                  1348508 bytes
Variable Size             167775332 bytes
Database Buffers          360710144 bytes
Redo Buffers                5828608 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

C:\Users\computer>nid target=/

DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:07:26 2013

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Connected to database TEST (DBID=2188161033)

Connected to server version 11.1.0

Control Files in database:
    D:\TEST1\TEST\CONTROLFILE\O1_MF_BZ16OKZ4_.CTL

Change database ID of database TEST? (Y/[N]) => Y

Proceeding with operation
Changing database ID from 2188161033 to 2188213519
    Control File D:\TEST1\TEST\CONTROLFILE\O1_MF_BZ16OKZ4_.CTL - modified
    Datafile D:\TEST1\SYSTEM01.DB - dbid changed
    Datafile D:\TEST1\SYSAUX01.DB - dbid changed
    Datafile D:\TEST1\UNDOTBS01.DB - dbid changed
    Datafile D:\TEST1\USERS01.DB - dbid changed
    Datafile D:\TEST1\TEMP01.DB - dbid changed
    Control File D:\TEST1\TEST\CONTROLFILE\O1_MF_BZ16OKZ4_.CTL - dbid changed
    Instance shut down

Database ID for database TEST changed to 2188213519.
All previous backups and archived redo logs for this database are unusable.
Database is not aware of previous backups and archived logs in Recovery Area.
Database has been shutdown, open database with RESETLOGS option.
Succesfully changed database ID.
DBNEWID - Completed succesfully.


C:\Users\computer>sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:26:45 2013

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup mount
ORACLE instance started.

Total System Global Area  535662592 bytes
Fixed Size                  1348508 bytes
Variable Size             167775332 bytes
Database Buffers          360710144 bytes
Redo Buffers                5828608 bytes
Database mounted.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open


SQL> alter database open resetlogs;

Database altered.

SQL> select open_mode,log_mode from v$database;

OPEN_MODE  LOG_MODE
---------- ------------
READ WRITE ARCHIVELOG

SQL> select dbid from v$database;

      DBID
----------
2188213519

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

C:\Users\computer>

Comments

Post a Comment

Popular posts from this blog

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG
Post a Comment
Read more