Comments on: Oracle spfile and dbstart

By: bob

bob — Mon, 21 Aug 2006 05:48:50 +0000

Why do people constantly try to do something just a little bit better? IMHO, the article presents the best solution (period).

-Bob
8i/9i/10g OCM DBA

By: Jon

Jon — Sat, 12 Aug 2006 21:38:15 +0000

Nasseem,

I’m sure that works, but you’re running the same risks as Marius. The spfile and init file just aren’t the same. You also have the problem of having to reapply this change if an upgrade overwrites dbstart and dbshut.

By: Naseem Wagner

Naseem Wagner — Thu, 10 Aug 2006 10:56:32 +0000

Another possibility is to correct the ${ORACLE_HOME}/bin/dbstart and ${ORACLE_HOME}/bin/dbstart file.

simply change the line
PFILE=${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora

to
PFILE=${ORACLE_HOME}/dbs/spfile${ORACLE_SID}.ora

By: Jon

Jon — Tue, 11 Jul 2006 12:34:38 +0000

Marius,

While that method may work I would not recommend it. The pfile and spfile are in different formats and beyond Oracle screwing up your spfile, if another DBA sees initSID.ora they will think it’s a normal pfile and manually edit it. That means certian death for your spfile.

If you’re relaly lazy you could just create a blank one with the command:

$ touch spfile

but I would not recommend linking it to your spfile.

By: Marius

Marius — Tue, 11 Jul 2006 09:38:13 +0000

Easy guys – create a symbolic link as ORACLE to the spfile – and it works!

$ cd /u01/app/oracle/product/9.2.0/dbs
$ ln -s spfileSID.ora initSID.ora

As ROOT:
su – oracle -c /u01/app/oracle/product/9.2.0/bin/dbstart