I CHANGED ORACLE_SID: FROM DEVDB TO SIEBDEV

===================================================
- Shutdown the instance
- Backup all control, redo, and data files.
- Go through the .profile, .cshrc, .login, oratab, tnsnames.ora, (for SQL*Net
version 2), and redefine the ORACLE_SID environment variable to a new value.
- Change locations to the "dbs" directory
% cd $ORACLE_HOME/dbs
and rename the following files:
o
o

init<sid>.ora (or use pfile to point to the init file.)

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 paramete
r 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.
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 fil
e do not
reference old init<SID>.ora files that have been renamed. This file simplifies
the
"startup exclusive" process to start your database.
To rename the database files and redo log files, you would follow the instruct
ions
in <Note:9560.1>.
Change the ORACLE_SID environment variable to the new value.
Check in the "$ORACLE_HOME/dbs" directory to see if the password file has bee
n
enabled. If enabled, the file "orapw<OLD_SID>" will exist and a new password fi
le for
the new SID must be created (renaming the old file will not work). If "orapw<O
LD_SID>"
does not exist, skip to step 9. To create a new password file, issue the follow
ing
command as oracle owner:
orapwd file=orapw<NEWSID> password=?? entries=<number of users to be gran
ted

permission to start the database instance>

Start up the database and verify that it works. Once you have done this, shu
tdown
the database and take a final backup of all control, redo, and data files.
When the instance is started, the control file is updated with the current
ORACLE_SID.