RE: Database name embedded in controlfile -- redundant?

From: <johnvue_at_gte.net>
Date: Tue, 26 May 1998 09:42:08 GMT
Message-ID: <6ke2re$80i$1@gte2.gte.net>

If that's true then what does Oracle do with the database name specified as part of the "CREATE DATABASE XYZ" command?

Here's where XYZ is specified:
ORACLE_SID=XYZ
DB_NAME = XYZ (in init.ora)
CREATE DATABASE XYZ ... Since Oracle is supposedly using the "XYZ" in init.ora to stamp the newly created control file, redo logs and SYSTEM datafile, what does it do with the "XYZ" in "CREATE DATABASE"?

Or put another way, if Oracle is using the "XYZ" in "CREATE DATABASE" to stamp the newly created control file, redo logs and SYSTEM datafile, what does it do with the "XYZ" in init.ora?

Everyone seems to agree that the "XYZ" in ORACLE_SID is only used to find the default initXYZ.ora upon startup when no "pfile=" is specified.

---

During the database creation, the DB_NAME parameter is used for recording the database name in redo logs ,datafiles and control files. If during the database startup the value of DB_NAME parameter and database name in control file are not name,the database won't start

-----Original Message-----
>What is the exact relationship between the database name in CREATE
>DATABASE and the DB_NAME parameter in init.ora?
>
>Is there ever a legitimate reason for not making them the same?
>
>It seems that ORACLE_SID environment variable tells Oracle about which
>init<SID>.ora to use. It doesn't use the environment variable to
>match up with the database name embedded within the controlfile.
>
>What is the purpose of having the database name inside the
>controlfile? Redundancy?
Received on Tue May 26 1998 - 04:42:08 CDT