Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a problem with a SPFILE as shown below.How can I get rid of that problem?Any suggestions?

 SQL> startup
 ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
 ORACLE instance started.

 Total System Global Area 1068937216 bytes
 Fixed Size                  2182592 bytes
 Variable Size             784335424 bytes
 Database Buffers          276824064 bytes
 Redo Buffers                5595136 bytes
 Database mounted.
 Database opened.
 SQL> alter system reset log_archive_start scope=spfile sid='*';
 alter system reset log_archive_start scope=spfile sid='*'
 ERROR at line 1:
 ORA-32010: cannot find entry to delete in SPFILE
share|improve this question
how did you identify that that was the obsolete parameter? IIRC the obsolete and deprecated parameters are listed in the alert.log at startup. – Niall Litchfield Dec 20 '11 at 13:52
up vote 1 down vote accepted

Well, you can hack around with an SPFILE easily enough:

SQL> create pfile='/tmp/initSID.ora' from spfile;

Now edit that ordinary text file, then

SQL> create spfile from pfile='/tmp/initSID.ora';

And you can play with the temporary one with

SQL> startup pfile='/tmp/initSID.ora';

Note tho' there is no actual problem with specifying obsolete parameters other than the message; the only issue is if you were relying on them to set some desired behavior, and they were ignored.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.