Skip to main content

Database name change using NID (rename DB after cloning)

Database changed name using nid option.

1- Database should be in mount mode
2- issue nid command
3- change db name in init.ora file before starting db in mount stage
3- open with open resetlog option

SQL> startup mount pfile=/u01//11.2.0/dbhome_1//dbs/initTESTR121.ora.tmp
ORACLE instance started.
Total System Global Area 2137886720 bytes
Fixed Size                  2230072 bytes
Variable Size            1375733960 bytes
Database Buffers          754974720 bytes
Redo Buffers                4947968 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

New DB name will be TESTR12
-bash-3.2$ nid target=/ dbname=TESTR12 logfile=/tmp/nid.log

-bash-3.2$ tail /tmp/nid.log
    Instance shut down
Database name changed to TESTR12.
Modify parameter file and generate a new password file before restarting.
Database ID for database TESTR12 changed to 3227523612.
All previous backups and archived redo logs for this database are unusable.
Database has been shutdown, open database with RESETLOGS option.
Succesfully changed database name and ID.
DBNEWID - Completed successfully.
-bash-3.2$
Before restarting change db_name parameter in $ORACLE_HOME/dbs/init.ora file then mount the database

-bash-3.2$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Sun Feb 4 10:21:22 2018
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to an idle instance.

SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 8551575552 bytes
Fixed Size                  2245480 bytes
Variable Size            1325403288 bytes
Database Buffers         7197425664 bytes
Redo Buffers               26501120 bytes
Database mounted.
SQL> alter database open resetlogs;
Database altered.

SQL> select name from v$database;
NAME
---------
TESTR12
SQL>



 

Comments

Post a Comment

Popular posts from this blog

EBS R12 “Unable to Authenticate Session”

Oracle E-Business Suite environment with IE8 and higher, When  cloning the EBS envitorment or you are logging out from your DEV Instance and want to login to  PROD-Instance it happens “Unable to authenticate session” Go to all programs, Right click on your IE icon and add -noframemerging to the end of the link in the Target field e.g.”C:\Program Files\Internet Explorer\ iexplore.exe ” -noframemerging (shown below) 1)  Start -> Program Files 2)  Right click on the Internet Explorer icon and select Properties 3)  Add -nomerge to the end of the link in the Target field i.e. “C:\Program Files\Internet Explorer\ iexplore.exe ” -noframemerging 4)  Click the OK button to close the window 5) Stop all Browser sessions. 6) Start a new Browser session and logon to the Instance
Post a Comment
Read more

EBS Standby Role Tranistion using standby database and standby application Tier

 Role Transitions A database can operate in either a primary or standby role - these roles are mutually exclusive. Oracle Data Guard enables you to change these roles dynamically by issuing SQL commands, and supports the following transitions: Switchover Allows the primary database to switch roles with one of its standby databases. There is no data loss during a switchover. After a switchover, each database continues to participate in the Oracle Data Guard configuration with its new role. Failover Changes a standby database to the primary role in response to a primary database failure. The following role transitions are discussed: 6.1 Performing a Switchover 6.2 Performing a Failover 6.3 Performing a Switchback to the Primary Following A Switchover/Failover Each of these three transitions requires some application configuration to be performed. Most of the application configuration step...
1 comment
Read more

How To Create LVM Using vgcreate in Linux

Logical Volume Management (LVM) creates a layer of abstraction over physical storage, allowing you to create logical storage volumes. With LVM in place, you are not bothered with physical disk sizes because the hardware storage is hidden from the software so it can be resized and moved without stopping applications or unmounting file systems. You can think of LVM as dynamic partitions. For example, if you are running out of disk space on your server, you can just add another disk and extend the logical volume on the fly. Below are some advantages of using Logical volumes over using physical storage directly: •Resize storage pools: You can extend the logical space as well as reduce it without reformatting the disks. •Flexible storage capacity: You can add more space by adding more disks and adding them to the pool of physical storage, thus you have a flexible storage capacity. •Use of striped, mirrored and snapshot volumes: Striped logical volume that stripes data across two or ...
Post a Comment
Read more