RE: Oracle 9.2 spfile catch 22

> SPFILE concept is good and it is required for reaching the goal of 'no
dba
> required', but it is still far from being 'ready for prime time'.

I really don't think the DBA will ever be eliminated.

This kind of thing just gives us more time to spend on other aspects of the database.

Just consider how much database/computer savvy is needed to make runInstaller work. :)

Jared

"Deshpande, Kirti" <kirti.deshpande_at_verizon.com> Sent by: root_at_fatcity.com
07/11/2002 01:37 PM
Please respond to ORACLE-L  

        To:     Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
        cc: 
        Subject:        RE: Oracle 9.2 spfile catch 22

I would get the DB to function the way I want first using init.ora. Then switch to SPFILE from init.ora, while preserving a copy of working init.ora
file.

Also, when a parameter is changed dynamically with SCOPE=both or spfile, I recreate my init.ora file as the backup.

SPFILE concept is good and it is required for reaching the goal of 'no dba required', but it is still far from being 'ready for prime time'.

I stopped using SPFILE with a couple of my databases when I was able to add
db_cache_size to an spfile that already had db_block_buffers (two mutually exclusive parameters). The next restart of the DB failed. It was good that I
had kept the init.ora file. I have not installed 9.2 yet, so I do now know if such things are verified beforehand and prevented.

HTH,

• Kirti

> -----Original Message-----
> From: DENNIS WILLIAMS [SMTP:DWILLIAMS_at_LIFETOUCH.COM]
> Sent: Thursday, July 11, 2002 12:49 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Oracle 9.2 spfile catch 22
>
> Thanks to everyone for the ideas on the init.ora. You were correct that
> the
> answer is indeed with spfile. Now I have discovered a catch-22.
>
> Oracle 9.2, Solaris
>
> 1. If spfile is created with LOG_ARCHIVE_START = true,
> database will not start. Receive the error
> ORA-00439 feature not enabled: Managed Standby
> 2. Creating the spfile with LOG_ARCHIVE_START = false works and the
> database
> starts. Issuing
> ALTER SYSTEM ARCHIVE LOG START
> works, but it isn't changed in the spfile, so the next time Oracle is
> bounced, the archiver doesn't start.
>
> This is starting to smell like a bug, but I thought I'd run it past the
> list
> on the off-chance someone else has gotten archiving turned on for 9.2.
> Thanks.
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: Jared.Still_at_radisys.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).