Skip to main content

Steps To Change The Oracle Database Name Using Nid Utility

Steps To Change The Oracle Database Name Using Nid Utility

We will change the database name from DEV to PROD.

1. Mount the database


SQL> STARTUP MOUNT

ORACLE instance started.

Total System Global Area 8754618368 bytes
Fixed Size 4646288 bytes
Variable Size 3556776560 bytes
Database Buffers 5033164800 bytes
Redo Buffers 160030720 bytes
Database mounted.

SQL> select name,open_mode from v$database;

NAME OPEN_MODE
--------- --------------------
DEV MOUNTED

2. Run the NID utility


SYNTAX – nid sys/password@CURRENT_DBNAME DBNAME=NEW_DBNAME

 

[oracle@funoracledb]$ nid target=sys/oracle@DEV DBNAME=PROD

DBNEWID: Release 12.1.0.1.0 - Production on Tue May 17 20:38:51 2016

Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved.

Connected to database DEV (DBID=738282423)

Connected to server version 12.1.0

Control Files in database:
/u02/oradata/PROD/control01.ctl
/u02/oradata/PROD/control02.ctl

Change database ID and database name DEV to PROD? (Y/[N]) => Y

Proceeding with operation
Changing database ID from 738282423 to 23523233232
Changing database name from DEV to PROD
Control File /u02/oradata/PROD/control01.ctl - modified
Control File /u02/oradata/PROD/control02.ctl - modified
Datafile /u02/oradata/PROD/system01.db - dbid changed, wrote new name
Datafile /u02/oradata/PROD/sysaux01.db - dbid changed, wrote new name
Datafile /u02/oradata/PROD/undotbs01.db - dbid changed, wrote new name
Datafile /u02/oradata/PROD/users01.db - dbid changed, wrote new name
Control File /u02/oradata/PROD/control01.ctl - dbid changed, wrote new name
Control File /u02/oradata/PROD/control02.ctl - dbid changed, wrote new name
Instance shut down

Database name changed to PROD.

Modify parameter file and generate a new password file before restarting.

Database ID for database PROD changed to 23523233232.
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.


3. Change DB name in pfile and startup with reset logs




If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...
Post a Comment
Read more