Possible in 8i to rename an instance ?

Question

I've got an instance that the suits say is a controversial
name.... say warrior.
They want it renamed to something 'business like' such as ;
lx101c or linux1 or something.
I couldn't find any cookbook on doing this, so I thought I'd ask
the crowd if anyone's had the pleasure.
By trying, failing, and falling back to square 1,
I know some of the things I need to keep in mind are :
1. /etc/oratab
2. initwarrior.ora vs. initlinux1.ora
3. tnsnames.ora
4. listener.ora
5. altering / changing the database name in the control files
somehow. This is the part that laughs at me.
If anybody can lend advice, I'd appreciate it.
- Freddy
[email protected]
null

Answer 1

Here is a copy of the notes that I've gleened off the web
in expectation of needing the info' myself. I've yet to
try them out (or tidy them up!) but they should get you
started,
colin.
>> Article on how to modify a database to run under a new
ORACLE_SID.
This entry describes how to change the ORACLE_SID for an
instance, without
recreating the database.
1. Shutdown the instance
2. Backup all control, redo, and data files.
3. Go through the .profile, .cshrc, .login, oratab,
tnsnames.ora,
(for net v2), and redefine the ORACLE_SID environment
variable
to a new value.
For example, search through disks and do a grep ORACLE_SID *
4. Change locations to the "dbs" directory
% cd $ORACLE_HOME/dbs
and rename the following files:
o init<sid>.ora (or use pfile to point to the init
file.)
o control file(s) This is optional if you do not rename
any
of the controlfiles, and the control_files parameter is
used.
The control_files parameter is set in the init<SID>.ora
file
or in a file it references with the ifile parameter.
Make
sure that the control_files parameter does not point to
old
file names, if you have renamed them.
o crdb<sid>.sql & crdb2<sid>.sql This is optional. These
are
only used at database creation.
5. Change locations to the "rdbms/admin" directory
% cd $ORACLE_HOME/rdbms/admin
and rename the file:
o startup<sid>.sql This is optional. On some
platforms,
this file may be in the "$ORACLE_HOME/rdbms/install"
directory.
Make sure that the contents of this file do not
reference old
init<SID>.ora files that have been renamed. This file
simplifies the "startup exclusive" process to start your
database.
6. To rename the database files and redo log files, you would
follow the
instructions in the RTSS bulletin 98863.723.
7. Change the ORACLE_SID environment variable to the new value.
8. Check in the "$ORACLE_HOME/dbs" directory to see if the
password
file has been enabled. If enabled, the file orapw<OLD_SID>
will
exist and a new password file for the new SID must be
created
(renaming the old file will not work). If orapw<OLD_SID>
does not
exist, skip to step 9. To create a new password file, issue
the following command as oracle owner:
orapwd file=orapw<NEWSID> password=?? entries=<number of
users to be
granted permission to start the database instance>
9. Start up the database and verify that it works. Once you
have done
this, shutdown the database and take a final backup of all
control,
redo, and data files.
10. When the instance is started, the control file is updated
with the
current ORACLE_SID.
>> Article on how to modify a database to run under a new
ORACLE_SID.
This entry describes how to change the "db_name" for a database
without
recreating the database.
1. Login to SQL*DBA or Server Manager
% sqldba
SQLDBA> connect internal
2. Type
SQLDBA> alter database backup controlfile to trace
resetlogs;
This will write in a trace file, the "CREATE CONTROLFILE"
command that
would recreate the controlfile as it currently exists.
3. Exit SQL*DBA
SQLDBA> exit
4. Change locations to the directory where your trace files are
located.
They are usually in the $ORACLE_HOME/rdbms/log directory. If
user_dump_dest is set in the init<SID>.ora file, then go to
the
directory listed in the user_dump_dest variable. The trace
file will
have the form "ora_NNNN.trc with NNNN being a number.
5. Get the "CREATE CONTROLFILE" command from the trace file and
put it in a
new file called something like "ccf.sql".
6. Edit the "ccf.sql" file
FROM: CREATE CONTROLFILE REUSE DATABASE "olddbname"
NORESETLOGS ...
TO: CREATE CONTROLFILE set DATABASE "newdbname" RESETLOGS
7. Save and exit the "ccf.sql" file
8. Rename the old control files for backup purposes and so they
are
not in the way of creating the new ones.
9. Edit the init<SID>.ora file so that db_name="newdb_name" .
10. Login to SQL*DBA or Server Manager
% sqldba
SQLDBA> connect internal Type:
11. Startup
SQLDBA> startup nomount
12. Run the "ccf.sql" script
SQLDBA> @ccf
13. Issue the alter database command
SQLDBA> alter database open;
14. Make sure the database is working.
15. Shutdown and backup the database.
Some said to this...
This doc is for v7, the problem that I am having is with v8. I
use basically
the same steps, except I do a reuse for the controlfile. The
problem that I
am having is not being able to reset the database id the new (in
v8) unique
identifier for each database. I don't know if taking the reuse
out of the
create controlfile script will be different because the reuse is
only
supposed to say reuse the file not any of the data within the
file, thereby
logically the dbid is stored in the data dictionary not the
control file.
>> Changing a D/B to run under a new ORACLE_SID
1. Shutdown instance
2. Backup all control, redo and data files.
3. Go thru the .profile, .cshrc, .login, oratab,
tnsnames.ora(for net v2),
and redefine the environment variable ORACLE_SID to a new
value.
ie search thru disks and do a grep ORACLE_SID *
4. Rename the following files in $ORACLE_HOME/dbs
. init<sid>.ora
(or use pfile to point to the init file.)
. control file(s)
This is optional if you don't rename any of the
controlfiles, and the
control_files parameter is used. control_files would be
set in the
init<sid>.ora file or in a file it references with the
ifile parameter.
Make sure control_files doesn't point to any old file
names, if you
renamed them.
. crdb<sid>.sql & crdb2<sid>.sql
This is optional. These are only used at database
creation.
5. Rename the following files in $ORACLE_HOME/rdbms/admin
. startup<sid>.sql
This is optional.
On some platforms, this file may be in
$ORACLE_HOME/rdbms/install
Make sure the contents of this file do not reference old
init<sid>.ora
files that have been renamed. This file simplifies the
process to
"startup exclusive" your database.
6. To rename the database files and redo log files, you would
follow the
instructions in the bulletin: 98863.723.
7. Change the ORACLE_SID environment variable to the new value.
8. start up database and verify it works. Once you have done
this, shutdown
the database and take a final backup of all control, redo
and data files.
9. When the instance is started, the control file gets updated
with the
current ORACLE_SID.
>> Changing the dbname for a database.
1. sqldba
2. connect internal
3. alter database backup controlfile to trace;
This will write in a trace file, the CREATE CONTROLFILE
command that
would recreate the controlfile as it currently exists.
4. Exit and go to the directory where your trace files are
located.
They are usually in the $ORACLE_HOME/rdbms/log directory.
If user_dump_dest is set in the initSID.ora, then go to the
directory
listed in the user_dump_dest variable.
The trace file will have the form "ora_NNNN.trc with NNNN
being a number.
5. Get the CREATE CONTROLFILE command from the trace file and
put it in a
new file called something like ccf.sql.
6. Edit the ccf.sql file and modify the CREATE CONTROLFILE
command.
Just change the word "REUSE" to "SET",and "NORESETLOGS" to
"RESETLOGS",
and modify the dbname.
Old line:
CREATE CONTROLFILE REUSE DATABASE "olddbname"
NORESETLOGS ...
New line:
CREATE CONTROLFILE set DATABASE "newdbname" RESETLOGS
Then save the ccf.sql file.
7. Rename the old control files for backup purposes and so they
are not in
the way of creating the new ones.
8. Edit initSID.ora so that db_name="newdbname".
9. sqldba
10. connect internal
11. startup nomount
12. @ccf
13. alter database open;
14. Make sure the database is working. Shutdown and backup the
database.
null