{"id":16072,"date":"2021-04-02T06:49:33","date_gmt":"2021-04-02T04:49:33","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/rename-your-db-clone-completely\/"},"modified":"2021-04-02T06:49:33","modified_gmt":"2021-04-02T04:49:33","slug":"rename-your-db-clone-completely","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/rename-your-db-clone-completely\/","title":{"rendered":"Rename your DB clone completely"},"content":{"rendered":"

Introduction<\/strong><\/h3>\n

Have you ever renamed your database?
\nWhen you cloned a DB, you probably started it with a new name and cloning (duplicating) with RMAN provided a new DBID, right?
\nSo why should we need to rename a DB?<\/p>\n

There may be several reasons:
\ndue to changed company rules, you need to rename all your DBs
\nAfter a restore you need to run the DB with another name
\nAfter a snapshot clone, (see my recent blog) you want to run it with new name<\/p>\n

First, I want to mention that all I found in the Internet was incomplete \u2013 even the Oracle\u00ae Database Utilities<\/a> and MOS Doc Id 2258871.1. Incomplete regarding all<\/u> the items that should be changed together with the DB-name or simply not working. Therefore, I write this article with the word \u201ccompletely\u201d at the end.<\/p>\n

Starting point<\/strong><\/h3>\n

We did a snapshot clone with our fancy new PureStorage<\/a>.
\nThe Oracle release and edition must be the same as on the source server, of course.
\nThe oratab, spfile, etc are created and the $ORACLE_SID is set to T01A (the new SID will be changed to T01B)<\/em>.
\nJust to remember the commands \u2013 we did a snapshot and copied the volumes to the target server:<\/p>\n

   purepgroup snap --suffix $SUFFIX ${SrcPG} --apply-retention\n   purevol copy --force ${SrcPG}.$SUFFIX.$SrcVol1 $TgtVol1\n   purevol copy --force ${SrcPG}.$SUFFIX.$SrcVol1 $TgtVol2\n   purevol copy --force ${SrcPG}.$SUFFIX.$SrcVol1 $TgtVol3<\/pre>\n
Then we mounted the volumes and were already able to and start the DB \u2013 done 😊
\nBut here the story starts\u2026<\/p>\n
1. Clean shutdown<\/h3>\n
First, before a rename, the DB needs a \u201cclean\u201d shutdown.
\nSo simply startup and
\nwhile the DB is open, create a pfile<\/strong> and a script to rename<\/strong> all DB-files for later use
\nthen shutdown the DB \u201cimmediate\u201d (not \u201cabort\u201d).
\nSome blogs mention to backup the controlfile and\/or switch the logfile, but this is not required.<\/p>\n
2. The configuration files<\/h3>\n\n\n\n\n\n
The clone commands above \u201ccopied\u201d the<\/td>\n\/u02\/oradata<\/td>\ncontaining the tablespace files<\/td>\n<\/tr>\n
<\/td>\n\/u03\/oradata<\/td>\ncontaining redologs<\/td>\n<\/tr>\n
<\/td>\n\/u90\/fra<\/td>\ncontaining backups<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
In your environment you may have more volumes. Feel free to adapt \u2026<\/p>\n
For a fresh clone, we will need as well the spfile and orapw from either the ADMIN- or ORACLE_HOME-directory and the sqlnet configuration files.
\nWhen you are doing frequent clones, you probably have these files already on your target server.<\/p>\n
Note:<\/em><\/strong> From here on I will use \u201cSRC\u201d for the original, the source DB-name and
\n     \u201cTGT\u201d for the new, the target DB-name.<\/em><\/p>\n
 
\nHere in our example, we use:<\/p>\n
$ADMIN = \/u01\/app\/oracle\/admin\/$ORACLE_SID\/pfile<\/pre>\n
for spfile and orapwd and<\/p>\n
$TNS_ADMIN = \/u01\/app\/oracle\/network\/admin<\/pre>\n
So, we need links to the files for both old-SID and new-SID and set the variable:<\/p>\n
ln -fs<\/strong> $ADMDIR\/$ORACLE_SRC\/pfile\/orapw$ORACLE_SRC $ORACLE_HOME\/dbs\/orapw$ORACLE_SRC\nln -fs<\/strong> $ADMDIR\/$ORACLE_TGT\/pfile\/orapw$ORACLE_TGT $ORACLE_HOME\/dbs\/orapw$ORACLE_TGT\nln -fs<\/strong> $ADMDIR\/$ORACLE_SRC\/pfile\/spfile$ORACLE_SRC.ora $ORACLE_HOME\/dbs\/spfile$ORACLE_SRC.ora\nln -fs<\/strong> $ADMDIR\/$ORACLE_TGT\/pfile\/spfile$ORACLE_TGT.ora $ORACLE_HOME\/dbs\/spfile$ORACLE_TGT.ora\nexport TNS_ADMIN<\/strong>=\/u01\/app\/oracle\/network\/admin\n\/usr\/bin\/scp -pr<\/strong> oracle@$SRCHOST:$ADMDIR\/$ORACLE_SRC* $ADMDIR    (***)\n\/usr\/bin\/scp -pr<\/strong> oracle@$SRCHOST:$TNS_ADMIN\/*.ora $TNS_ADMIN<\/pre>\n
*** (if you do not want to copy a bulk load of *aud files, please modify the scp-command)<\/em><\/p>\n
For completeness I would like to mention directories containing the $DB_UNIQUE_NAME<\/strong> like
\n\/u01\/app\/oracle\/admin\/$DB_UNIQUE_NAME\/xdb_wallet or\u00a0<\/strong>
\n\/u01\/app\/oracle\/diag<\/strong>\/rdbms\/$DB_UNIQUE_NAME\/\u2026
\nwhich are handled in my script.<\/p>\n
3. DBNEWID<\/h3>\n
Now you can run the \u201cmain\u201d command.<\/p>\n
\u00a0nid target=\/ dbname=$ORACLE_TGT<\/strong><\/p>\n
The output will tell you something about changed file names:<\/p>\n
\u2026\nControl File \/u02\/oradata\/T01A\/control03T01A.dbf - modified\nDatafile \/u02\/oradata\/T01A\/system01T01A.db - dbid changed, wrote new name\n\u2026\nInstance shut down\nDatabase name changed to T01B.\nModify parameter file and generate a new password file before restarting.\nDatabase ID for database T01B changed to 2621333956.\nAll previous backups<\/strong> and archived redo logs<\/strong> for this database are unusable<\/strong>.\nDatabase is not aware of previous backups and archived logs in Recovery Area.\nDatabase has been shutdown, open database with RESETLOGS option.\nSuccesfully changed database name and ID.\nDBNEWID - Completed succesfully.<\/pre>\n
Be aware \u2013 the file names were NOT changed. They are just registered in the controlfile.
\nAnd it tells us that all the archives and backups are obsolete.<\/p>\n
4. Rename and adapt all and everything<\/h3>\n
Most blogs tell you ALTER SYSTEM SET DB_NAME=T01B; and start your DB\u00a0 \u21d2\u00a0 \ud83d\ude25<\/p>\n