Skip to Main Content
  • Questions
  • ORA-32004: obsolete and/or deprecated parameter(s) specified

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Kamal.

Asked: December 26, 2005 - 1:36 pm UTC

Last updated: October 17, 2018 - 4:45 am UTC

Version: 10.2.0.1

Viewed 100K+ times! This question is

You Asked

Hi Tom,
When starting the database, I get the error ORA-32004:
---------------------------------
SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 75498852 bytes
Database Buffers 88080384 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
SQL> disconnect
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
-------------------------------
Is there a way to find out which deprecated parameter(s) are causing the above message when using spfile?
Thank You.


and Tom said...

In your alert log, you will find messages to the effect:

.....
Deprecated system parameters with specified values:
parallel_automatic_tuning
End of deprecated system parameter listing
PMON started with pid=2, OS id=26188


Rating

  (15 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Another way to find obsolete parameters

Michel Cadot, December 26, 2005 - 3:01 pm UTC

Hi,

You can also find your obsolete parameters with:

select name from v$obsolete_parameter where isspecified='TRUE';

Regards
Michel


log_archive_start ?

Kamal Kishore, December 28, 2005 - 7:59 pm UTC

Thanks Tom. I fould the entry in the alert file.
The select from v$obsolete_parameter does not indicate any such obsolete parameter, yet alert file has the entry for the obsolete parameter.

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

Total System Global Area  167772160 bytes
Fixed Size                  1247900 bytes
Variable Size              83887460 bytes
Database Buffers           79691776 bytes
Redo Buffers                2945024 bytes
Database mounted.
Database opened.
SQL> select name from v$obsolete_parameter where isspecified='TRUE';

no rows selected

SQL>

Whereas the alert.log contains the following:
------------
Deprecated system parameters with specified values:
  log_archive_start        
End of deprecated system parameter listing
------------

In order to remove this, should I create pfile from spfile and back to spfile? Is that the only way?
 

Tom Kyte
December 28, 2005 - 8:17 pm UTC

you can try this first:

<quote src=Expert Oracle: Database Architecture>

Unsetting Values in SPFILEs

The next question that arises is, “OK, so we set a value, but we would now like to ‘unset’ it—in other words, we don’t want that parameter setting in our SPFILE at all, and we would like it removed. Since we cannot edit the file using a text editor, how do we accomplish that?” This, too, is done via the ALTER SYSTEM command, but using the RESET clause:

Alter system reset parameter <scope=memory|spfile|both> sid='sid|*'

Here the SCOPE/SID settings have the same meaning as before, but the SID= component is not optional. The documentation in the Oracle SQL Reference manual is a bit misleading on this particular command, as it seems to indicate that it is only valid for RAC (clustered) databases. In fact, it states the following:

The alter_system_reset_clause is for use in a Real Application Clusters environment.

Later, it does go on to state

In a non-RAC environment, you can specify SID='*' for this clause.

But this is a bit confusing. Nonetheless, this is the command we would use to “remove” a parameter setting from the SPFILE, allowing it to default. So, for example, if we wanted to remove the sort_area_size, to allow it to assume the default value we specified previously, we could do so as follows:

sys@ORA10G> alter system reset sort_area_size scope=spfile sid='*';
System altered.

The sort_area_size is removed from the SPFILE, a fact you can verify by issuing the following:

sys@ORA10G> create pfile='/tmp/pfile.tst' from spfile;
File created.

You can then review the contents of /tmp/pfile.tst, which will be generated on the database server. You will find the sort_area_size parameter does not exist in the parameter files anymore.
</quote>

Thanks

Kamal Kishore, December 29, 2005 - 8:01 pm UTC

Thanks Tom.
That did the trick. I missed the reset option with the alter system command. I guess I should be reading the documentation even more closely now.

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

Total System Global Area  167772160 bytes
Fixed Size                  1247900 bytes
Variable Size              88081764 bytes
Database Buffers           75497472 bytes
Redo Buffers                2945024 bytes
Database mounted.
Database opened.
SQL>
SQL> alter system reset log_archive_start scope=spfile sid='*' ;

System altered.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> startup
ORACLE instance started.

Total System Global Area  167772160 bytes
Fixed Size                  1247900 bytes
Variable Size              88081764 bytes
Database Buffers           75497472 bytes
Redo Buffers                2945024 bytes
Database mounted.
Database opened.
SQL> disconnect
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
 

ORA-32004 obsolete and/or deprecated parameter

Dennis, January 31, 2006 - 4:39 pm UTC

The description of the error was exactly what I had. The corrective procedure worked perfectly. Thank you.

Reset an obsolete parameter in 9i

A reader, March 13, 2006 - 10:34 am UTC

Tom,

is it possible to reset an obsolete parameter in 9i
without creating pfile from spfile/editing it and creating spfile again?

SQL> alter system reset parameter dblink_encrypt_login scope=spfile;
alter system reset parameter dblink_encrypt_login scope=spfile
*
ERROR at line 1:
ORA-00922: missing or invalid option 

Tom Kyte
March 13, 2006 - 9:27 pm UTC

sys@ORA9IR2> alter system reset dblink_encrypt_login scope=spfile sid='*';

System altered.



"parameter" was a placeholder in the text for the parameter name itself.

A reader, March 14, 2006 - 5:33 am UTC

Thanks - it is exactly I was looking for.

Need the SID

Steven E, April 28, 2006 - 6:04 pm UTC

Hi All,

  I'm running a non-RAC 10.2.0.2 DB and I found that I needed the SID parameter to get a reset command to run:

SQL> alter system reset log_archive_start scope=spfile;
alter system reset log_archive_start scope=spfile
                                                *
ERROR at line 1:
ORA-00905: missing keyword


SQL> alter system reset log_archive_start scope=spfile sid='*';

System altered.

Thanks Tom, I would NEVER have figured that out on my own. 

pls help me

mohammed, August 23, 2006 - 3:54 am UTC

------------------------------ Wed Aug 23 03:12:12 EDT 2006
LOGFILE FOR STARTING ORACLE

Trying to start T03 database ...

------------------------------ Wed Aug 23 03:12:12 EDT 2006
checking required environment variables

ORACLE_HOME is >/oracle/T03/920_64<
ORACLE_SID is >T03<

------------------------------ Wed Aug 23 03:12:12 EDT 2006
check initora


------------------------------ Wed Aug 23 03:12:12 EDT 2006
check initora


------------------------------ Wed Aug 23 03:12:12 EDT 2006
checking V2 connect


TNS Ping Utility for HPUX: Version 9.2.0.5.0 - Production on 23-AUG-2006 03:12:1
2

Copyright (c) 1997 Oracle Corporation. All rights reserved.

Used parameter files:
/oracle/T03/920_64/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = sap
.world) (PROTOCOL = TCP) (Host = njscmdev) (Port = 1574))) (CONNECT_DATA = (SID
= T03) (GLOBAL_NAME = T03.world)))
OK (10 msec)
tnsping: V2 connect to T03

------------------------------ Wed Aug 23 03:12:12 EDT 2006
Connect to the database to check the database state:

R3trans: connect check finished with return code: 12
Database not available

------------------------------ Wed Aug 23 03:12:12 EDT 2006
Shutdown database

First trying to shutdown the database - May be,
the database is in the nomount or mount state

------------------------------ Wed Aug 23 03:12:22 EDT 2006
starting database


SQL*Plus: Release 9.2.0.5.0 - Production on Wed Aug 23 03:12:22 2006

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to an idle instance.
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Total System Global Area 4204492936 bytes
Fixed Size 739464 bytes
Variable Size 1744830464 bytes
Database Buffers 2457600000 bytes
Redo Buffers 1323008 bytes
Database mounted.
Database opened.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Producti
on
With the Partitioning option
JServer Release 9.2.0.5.0 - Production

------------------------------ Wed Aug 23 03:12:39 EDT 2006
Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12
*** ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/T03/SYS/exe/run/startdb: Terminating with error code 12
njscmdev:t03adm 65>

Tom Kyte
August 27, 2006 - 3:20 pm UTC

well, umm, guess I'd look at "R3trans" - whatever the heck that is - and find out why it is getting "return code: 12" - whatever that is.


(eg: might be time to log a tar with SAP since the database is obviously up and runnnig here...)



Depricated Paramaters

Rohit Dogra, December 11, 2010 - 1:53 am UTC

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

Total System Global Area  603979776 bytes
Fixed Size                  1220796 bytes
Variable Size             188747588 bytes
Database Buffers          406847488 bytes
Redo Buffers                7163904 bytes
Database mounted.
Database opened.
SQL> 
SQL> 
SQL> select name from v$obsolete_parameter where isspecified='TRUE';

no rows selected






SQL> alter system reset sort_area_size scope=spfile sid='orcl';
alter system reset sort_area_size scope=spfile sid='orcl'
*
ERROR at line 1:
ORA-32010: cannot find entry to delete in SPFILE





SQL> alter system reset log_archive_start scope=spfile sid='orcl';
alter system reset log_archive_start scope=spfile sid='orcl'
*
ERROR at line 1:
ORA-32010: cannot find entry to delete in SPFILE


Now what to do sir pls tell me?


And there is no such entry in the alert log file


Alert Log File





Mon Nov 22 19:41:11 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 150
  sga_target               = 603979776
  control_files            = /opt/oracle/oradata/orcl/control01.ctl, /opt/oracle/oradata/orcl/control02.ctl, /opt/oracle/oradata/orcl/control03.ctl
  db_block_size            = 8192
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /opt/oracle/flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  job_queue_processes      = 10
  background_dump_dest     = /opt/oracle/admin/orcl/bdump
  user_dump_dest           = /opt/oracle/admin/orcl/udump
  core_dump_dest           = /opt/oracle/admin/orcl/cdump
  audit_file_dest          = /opt/oracle/admin/orcl/adump
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 200278016
PMON started with pid=2, OS id=9162
PSP0 started with pid=3, OS id=9164
MMAN started with pid=4, OS id=9166
DBW0 started with pid=5, OS id=9168
LGWR started with pid=6, OS id=9170
CKPT started with pid=7, OS id=9172
SMON started with pid=8, OS id=9174
RECO started with pid=9, OS id=9176
CJQ0 started with pid=10, OS id=9178
MMON started with pid=11, OS id=9180
Mon Nov 22 19:41:12 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=9182
Mon Nov 22 19:41:12 2010
starting up 1 shared server(s) ...
Mon Nov 22 19:41:12 2010
The input backup piece /opt/oracle/102/assistants/dbca/templates/Seed_Database.dfb is in compressed format.
Full restore complete of datafile 4 to datafile copy /opt/oracle/oradata/orcl/users01.dbf.  Elapsed time: 0:00:00 
  checkpoint is 446074
Full restore complete of datafile 2 to datafile copy /opt/oracle/oradata/orcl/undotbs01.dbf.  Elapsed time: 0:00:01 
  checkpoint is 446074
Mon Nov 22 19:41:27 2010
Full restore complete of datafile 3 to datafile copy /opt/oracle/oradata/orcl/sysaux01.dbf.  Elapsed time: 0:00:11 
  checkpoint is 446074
Mon Nov 22 19:41:38 2010
Full restore complete of datafile 1 to datafile copy /opt/oracle/oradata/orcl/system01.dbf.  Elapsed time: 0:00:25 
  checkpoint is 446074
Mon Nov 22 19:41:39 2010
Create controlfile reuse set database "orcl"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/opt/oracle/oradata/orcl/system01.dbf',
'/opt/oracle/oradata/orcl/undotbs01.dbf',
'/opt/oracle/oradata/orcl/sysaux01.dbf',
'/opt/oracle/oradata/orcl/users01.dbf'
LOGFILE GROUP 1 ('/opt/oracle/oradata/orcl/redo01.log') SIZE 51200K,
GROUP 2 ('/opt/oracle/oradata/orcl/redo02.log') SIZE 51200K,
GROUP 3 ('/opt/oracle/oradata/orcl/redo03.log') SIZE 51200K RESETLOGS
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in future release
Setting recovery target incarnation to 1
Mon Nov 22 19:41:39 2010
Successful mount of redo thread 1, with mount id 1263515123
Mon Nov 22 19:41:39 2010
Completed: Create controlfile reuse set database "orcl"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/opt/oracle/oradata/orcl/system01.dbf',
'/opt/oracle/oradata/orcl/undotbs01.dbf',
'/opt/oracle/oradata/orcl/sysaux01.dbf',
'/opt/oracle/oradata/orcl/users01.dbf'
LOGFILE GROUP 1 ('/opt/oracle/oradata/orcl/redo01.log') SIZE 51200K,
GROUP 2 ('/opt/oracle/oradata/orcl/redo02.log') SIZE 51200K,
GROUP 3 ('/opt/oracle/oradata/orcl/redo03.log') SIZE 51200K RESETLOGS
Shutting down instance: further logons disabled
Mon Nov 22 19:41:39 2010
Stopping background process MMNL
Mon Nov 22 19:41:40 2010
Stopping background process CJQ0
Mon Nov 22 19:41:40 2010
Stopping background process MMON
Mon Nov 22 19:41:41 2010
Shutting down instance (immediate)
License high water mark = 1
Mon Nov 22 19:41:41 2010
Stopping Job queue slave processes
Mon Nov 22 19:41:41 2010
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Mon Nov 22 19:41:44 2010
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Mon Nov 22 19:41:44 2010
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Nov 22 19:41:46 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 150
  sga_target               = 603979776
  control_files            = /opt/oracle/oradata/orcl/control01.ctl, /opt/oracle/oradata/orcl/control02.ctl, /opt/oracle/oradata/orcl/control03.ctl
  db_block_size            = 8192
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /opt/oracle/flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  _no_recovery_through_resetlogs= TRUE
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  background_dump_dest     = /opt/oracle/admin/orcl/bdump
  user_dump_dest           = /opt/oracle/admin/orcl/udump
  core_dump_dest           = /opt/oracle/admin/orcl/cdump
  audit_file_dest          = /opt/oracle/admin/orcl/adump
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 200278016
PMON started with pid=2, OS id=9199
PSP0 started with pid=3, OS id=9201
MMAN started with pid=4, OS id=9203
DBW0 started with pid=5, OS id=9205
LGWR started with pid=6, OS id=9207
CKPT started with pid=7, OS id=9209
SMON started with pid=8, OS id=9211
RECO started with pid=9, OS id=9213
MMON started with pid=10, OS id=9215
Mon Nov 22 19:41:46 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=11, OS id=9217
Mon Nov 22 19:41:46 2010
starting up 1 shared server(s) ...
Mon Nov 22 19:41:46 2010
Create controlfile reuse set database "orcl"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/opt/oracle/oradata/orcl/system01.dbf',
'/opt/oracle/oradata/orcl/undotbs01.dbf',
'/opt/oracle/oradata/orcl/sysaux01.dbf',
'/opt/oracle/oradata/orcl/users01.dbf'
LOGFILE GROUP 1 ('/opt/oracle/oradata/orcl/redo01.log') SIZE 51200K,
GROUP 2 ('/opt/oracle/oradata/orcl/redo02.log') SIZE 51200K,
GROUP 3 ('/opt/oracle/oradata/orcl/redo03.log') SIZE 51200K RESETLOGS
Mon Nov 22 19:41:46 2010
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in future release
Setting recovery target incarnation to 1
Mon Nov 22 19:41:47 2010
Successful mount of redo thread 1, with mount id 1263521274
Mon Nov 22 19:41:47 2010
Completed: Create controlfile reuse set database "orcl"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/opt/oracle/oradata/orcl/system01.dbf',
'/opt/oracle/oradata/orcl/undotbs01.dbf',
'/opt/oracle/oradata/orcl/sysaux01.dbf',
'/opt/oracle/oradata/orcl/users01.dbf'
LOGFILE GROUP 1 ('/opt/oracle/oradata/orcl/redo01.log') SIZE 51200K,
GROUP 2 ('/opt/oracle/oradata/orcl/redo02.log') SIZE 51200K,
GROUP 3 ('/opt/oracle/oradata/orcl/redo03.log') SIZE 51200K RESETLOGS
Mon Nov 22 19:41:47 2010
Stopping background process MMNL
Mon Nov 22 19:41:48 2010
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
MMON started with pid=10, OS id=9224
Mon Nov 22 19:41:49 2010
ALTER SYSTEM enable restricted session;
MMNL started with pid=11, OS id=9226
Mon Nov 22 19:41:49 2010
alter database "orcl" open resetlogs
Mon Nov 22 19:41:49 2010
RESETLOGS after incomplete recovery UNTIL CHANGE 446074
Mon Nov 22 19:41:49 2010
Errors in file /opt/oracle/admin/orcl/udump/orcl_ora_9222.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/opt/oracle/oradata/orcl/redo01.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon Nov 22 19:41:50 2010
Errors in file /opt/oracle/admin/orcl/udump/orcl_ora_9222.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/opt/oracle/oradata/orcl/redo02.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon Nov 22 19:41:51 2010
Errors in file /opt/oracle/admin/orcl/udump/orcl_ora_9222.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/opt/oracle/oradata/orcl/redo03.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon Nov 22 19:41:52 2010
Setting recovery target incarnation to 2
Mon Nov 22 19:41:52 2010
Assigning activation ID 1263521274 (0x4b4fcdfa)
Thread 1 opened at log sequence 1
  Current log# 3 seq# 1 mem# 0: /opt/oracle/oradata/orcl/redo03.log
Successful open of redo thread 1
Mon Nov 22 19:41:52 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Nov 22 19:41:52 2010
SMON: enabling cache recovery
Mon Nov 22 19:41:53 2010
Successfully onlined Undo Tablespace 1.
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Dictionary check complete
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
         This condition can occur when a backup controlfile has
         been restored.  It may be necessary to add files to these
         tablespaces.  That can be done using the SQL statement:
 
         ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
 
         Alternatively, if these temporary tablespaces are no longer
         needed, then they can be dropped.
           Empty temporary tablespace: TEMP
*********************************************************************
Mon Nov 22 19:41:53 2010
SMON: enabling tx recovery
Mon Nov 22 19:41:53 2010
Database Characterset is US7ASCII
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
   then disabled.
**********************************************************
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=15, OS id=9228
Mon Nov 22 19:41:55 2010
LOGSTDBY: Validating controlfile with logical metadata
Mon Nov 22 19:41:55 2010
LOGSTDBY: Validation complete
Global Name changed to ORCL
Completed: alter database "orcl" open resetlogs
Mon Nov 22 19:41:55 2010
alter database rename global_name to "orcl"
Completed: alter database rename global_name to "orcl"
Mon Nov 22 19:41:55 2010
ALTER TABLESPACE TEMP ADD TEMPFILE '/opt/oracle/oradata/orcl/temp01.dbf' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
Completed: ALTER TABLESPACE TEMP ADD TEMPFILE '/opt/oracle/oradata/orcl/temp01.dbf' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
Mon Nov 22 19:41:56 2010
ALTER DATABASE DEFAULT TABLESPACE "USERS"
Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
Mon Nov 22 19:41:57 2010
ALTER SYSTEM disable restricted session;
Mon Nov 22 19:41:57 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Nov 22 19:41:58 2010
Starting background process CJQ0
CJQ0 started with pid=18, OS id=9236
Mon Nov 22 19:41:59 2010
The input backup piece /opt/oracle/102/assistants/dbca/templates/example01.dfb is in compressed format.
Full restore complete of datafile 5 to datafile copy /opt/oracle/oradata/orcl/example01.dbf.  Elapsed time: 0:00:02 
  checkpoint is 460200
Mon Nov 22 19:42:04 2010
Plug in tablespace EXAMPLE with datafile
  '/opt/oracle/oradata/orcl/example01.dbf'
Mon Nov 22 19:42:16 2010
ALTER TABLESPACE example READ WRITE
Mon Nov 22 19:42:16 2010
Completed: ALTER TABLESPACE example READ WRITE
Mon Nov 22 19:42:19 2010
Memory Notification: Library Cache Object loaded into SGA
Heap size 2239K exceeds notification threshold (2048K)
KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw== 
Mon Nov 22 19:42:30 2010
Starting background process EMN0
EMN0 started with pid=19, OS id=9262
Mon Nov 22 19:42:30 2010
Shutting down instance: further logons disabled
Mon Nov 22 19:42:32 2010
Stopping background process CJQ0
Mon Nov 22 19:42:32 2010
Stopping background process QMNC
Mon Nov 22 19:42:33 2010
Stopping background process MMNL
Mon Nov 22 19:42:34 2010
Stopping background process MMON
Mon Nov 22 19:42:35 2010
Shutting down instance (immediate)
License high water mark = 4
All dispatchers and shared servers shutdown
Mon Nov 22 19:42:37 2010
ALTER DATABASE CLOSE NORMAL
Mon Nov 22 19:42:37 2010
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Nov 22 19:42:38 2010
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 1
Successful close of redo thread 1
Mon Nov 22 19:42:38 2010
Completed: ALTER DATABASE CLOSE NORMAL
Mon Nov 22 19:42:38 2010
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Nov 22 19:42:39 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 150
  sga_target               = 603979776
  control_files            = /opt/oracle/oradata/orcl/control01.ctl, /opt/oracle/oradata/orcl/control02.ctl, /opt/oracle/oradata/orcl/control03.ctl
  db_block_size            = 8192
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /opt/oracle/flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  _no_recovery_through_resetlogs= TRUE
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  background_dump_dest     = /opt/oracle/admin/orcl/bdump
  user_dump_dest           = /opt/oracle/admin/orcl/udump
  core_dump_dest           = /opt/oracle/admin/orcl/cdump
  audit_file_dest          = /opt/oracle/admin/orcl/adump
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 200278016
PMON started with pid=2, OS id=9265
PSP0 started with pid=3, OS id=9267
MMAN started with pid=4, OS id=9269
DBW0 started with pid=5, OS id=9271
LGWR started with pid=6, OS id=9273
CKPT started with pid=7, OS id=9275
SMON started with pid=8, OS id=9277
RECO started with pid=9, OS id=9279
MMON started with pid=10, OS id=9281
Mon Nov 22 19:42:39 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=11, OS id=9283
Mon Nov 22 19:42:39 2010
starting up 1 shared server(s) ...
Mon Nov 22 19:42:39 2010
ALTER DATABASE   MOUNT
Mon Nov 22 19:42:43 2010
Setting recovery target incarnation to 2
Mon Nov 22 19:42:43 2010
Successful mount of redo thread 1, with mount id 1263539503
Mon Nov 22 19:42:43 2010
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Mon Nov 22 19:42:43 2010
ALTER DATABASE OPEN
Mon Nov 22 19:42:43 2010
Thread 1 opened at log sequence 1
  Current log# 3 seq# 1 mem# 0: /opt/oracle/oradata/orcl/redo03.log
Successful open of redo thread 1
Mon Nov 22 19:42:43 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Nov 22 19:42:43 2010
SMON: enabling cache recovery
Mon Nov 22 19:42:43 2010
Successfully onlined Undo Tablespace 1.
Mon Nov 22 19:42:43 2010
SMON: enabling tx recovery
Mon Nov 22 19:42:43 2010
Database Characterset is US7ASCII
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=15, OS id=9291
Mon Nov 22 19:42:44 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Nov 22 19:42:44 2010
Completed: ALTER DATABASE OPEN
Mon Nov 22 19:42:44 2010
Stopping background process MMNL
Mon Nov 22 19:42:44 2010
Starting background process CJQ0
CJQ0 started with pid=16, OS id=9297
Mon Nov 22 19:42:46 2010
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
MMON started with pid=10, OS id=9299
Mon Nov 22 19:42:47 2010
ALTER SYSTEM enable restricted session;
MMNL started with pid=11, OS id=9301
Mon Nov 22 19:42:47 2010
alter database character set INTERNAL_CONVERT WE8ISO8859P1
Mon Nov 22 19:42:51 2010
Updating character set in controlfile to WE8ISO8859P1
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
Mon Nov 22 19:42:52 2010
Thread 1 advanced to log sequence 2
  Current log# 1 seq# 2 mem# 0: /opt/oracle/oradata/orcl/redo01.log
Mon Nov 22 19:42:53 2010
Completed: alter database character set INTERNAL_CONVERT WE8ISO8859P1
Mon Nov 22 19:42:53 2010
ALTER SYSTEM disable restricted session;
Mon Nov 22 19:42:55 2010
Starting background process EMN0
EMN0 started with pid=19, OS id=9317
Mon Nov 22 19:42:55 2010
Shutting down instance: further logons disabled
Mon Nov 22 19:42:57 2010
Stopping background process QMNC
Mon Nov 22 19:42:57 2010
Stopping background process CJQ0
Mon Nov 22 19:42:59 2010
Stopping background process MMNL
Mon Nov 22 19:43:01 2010
Stopping background process MMON
Mon Nov 22 19:43:02 2010
Shutting down instance (immediate)
License high water mark = 1
All dispatchers and shared servers shutdown
Mon Nov 22 19:43:04 2010
ALTER DATABASE CLOSE NORMAL
Mon Nov 22 19:43:04 2010
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Nov 22 19:43:04 2010
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 2
Successful close of redo thread 1
Mon Nov 22 19:43:05 2010
Completed: ALTER DATABASE CLOSE NORMAL
Mon Nov 22 19:43:05 2010
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Nov 22 19:43:07 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 150
  sga_target               = 603979776
  control_files            = /opt/oracle/oradata/orcl/control01.ctl, /opt/oracle/oradata/orcl/control02.ctl, /opt/oracle/oradata/orcl/control03.ctl
  db_block_size            = 8192
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /opt/oracle/flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  job_queue_processes      = 10
  background_dump_dest     = /opt/oracle/admin/orcl/bdump
  user_dump_dest           = /opt/oracle/admin/orcl/udump
  core_dump_dest           = /opt/oracle/admin/orcl/cdump
  audit_file_dest          = /opt/oracle/admin/orcl/adump
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 200278016
PMON started with pid=2, OS id=9320
PSP0 started with pid=3, OS id=9322
MMAN started with pid=4, OS id=9324
DBW0 started with pid=5, OS id=9326
LGWR started with pid=6, OS id=9328
CKPT started with pid=7, OS id=9330
SMON started with pid=8, OS id=9332
RECO started with pid=9, OS id=9334
CJQ0 started with pid=10, OS id=9336
MMON started with pid=11, OS id=9338
Mon Nov 22 19:43:07 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=9340
Mon Nov 22 19:43:07 2010
starting up 1 shared server(s) ...
Mon Nov 22 19:43:07 2010
ALTER DATABASE   MOUNT
Mon Nov 22 19:43:11 2010
Setting recovery target incarnation to 2
Mon Nov 22 19:43:11 2010
Successful mount of redo thread 1, with mount id 1263548491
Mon Nov 22 19:43:11 2010
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Mon Nov 22 19:43:11 2010
ALTER DATABASE OPEN
Mon Nov 22 19:43:11 2010
Thread 1 opened at log sequence 2
  Current log# 1 seq# 2 mem# 0: /opt/oracle/oradata/orcl/redo01.log
Successful open of redo thread 1
Mon Nov 22 19:43:11 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Nov 22 19:43:11 2010
SMON: enabling cache recovery
Mon Nov 22 19:43:11 2010
Successfully onlined Undo Tablespace 1.
Mon Nov 22 19:43:11 2010
SMON: enabling tx recovery
Mon Nov 22 19:43:11 2010
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=16, OS id=9348
Mon Nov 22 19:43:12 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Nov 22 19:43:12 2010
Completed: ALTER DATABASE OPEN
Mon Nov 22 20:09:26 2010
Starting background process EMN0
EMN0 started with pid=19, OS id=16156
Mon Nov 22 20:09:26 2010
Shutting down instance: further logons disabled
Mon Nov 22 20:09:26 2010
Stopping background process QMNC
Mon Nov 22 20:09:26 2010
Stopping background process CJQ0
Mon Nov 22 20:09:28 2010
Stopping background process MMNL
Mon Nov 22 20:09:29 2010
Stopping background process MMON
Mon Nov 22 20:09:30 2010
Shutting down instance (immediate)
License high water mark = 10
Mon Nov 22 20:09:30 2010
Stopping Job queue slave processes
Mon Nov 22 20:09:35 2010
Process OS id : 16154 alive after kill
Errors in file 
Mon Nov 22 20:09:35 2010
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Mon Nov 22 20:09:48 2010
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Mon Nov 22 20:09:59 2010
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
Mon Nov 22 20:10:04 2010
ALTER DATABASE CLOSE NORMAL
Mon Nov 22 20:10:04 2010
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Nov 22 20:10:04 2010
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 2
Successful close of redo thread 1
Mon Nov 22 20:10:04 2010
Completed: ALTER DATABASE CLOSE NORMAL
Mon Nov 22 20:10:04 2010
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active

Tom Kyte
December 11, 2010 - 2:28 pm UTC

just show us the alert.log entry from TODAY - not last month.

show us only the part of the alert log generated by your startup command - not something that happened a long time ago

Depricated Paramaters

Rohit Dogra, December 13, 2010 - 8:35 am UTC

Mon Dec 13 19:57:23 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
__shared_pool_size = 184549376
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
sga_target = 603979776
control_files = /opt/oracle/oradata/orcl/control01.ctl, /opt/oracle/oradata/orcl/control02.ctl, /opt/oracle/oradata/orcl/control03.ctl
db_block_size = 8192
__db_cache_size = 402653184
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = /opt/oracle/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
background_dump_dest = /opt/oracle/admin/orcl/bdump
user_dump_dest = /opt/oracle/admin/orcl/udump
core_dump_dest = /opt/oracle/admin/orcl/cdump
audit_file_dest = /opt/oracle/admin/orcl/adump
db_name = orcl
open_cursors = 300
sql_trace = TRUE
pga_aggregate_target = 200278016


Deprecated system parameters with specified values:
sql_trace
End of deprecated system parameter listing

PMON started with pid=2, OS id=5600

Tom Kyte
December 14, 2010 - 2:46 am UTC

so, umm, it sort of looks like by posting the alert log portion that goes along with when the message started coming out - you were able to figure it out by yourself - right? Just asking - because you didn't say anything.


Deprecated Parameters

Rohit Dogra, January 02, 2011 - 2:04 am UTC

Deprecated system parameters with specified values:
sql_trace
End of deprecated system parameter listing

PMON started with pid=2, OS id=5600


Showing in the alert log file whats the reason should i alter the sql_trace='false' at the session level or at instance level? pls hel me out what the reason for this error
Tom Kyte
January 03, 2011 - 8:55 am UTC

you or a program run against your database is using "alter session set sql_trace=<something>"

that particular parameter has been deprecated - as the message sort of indicates and a glance at the documentation supports:

http://docs.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams243.htm#REFRN10208

the preferred method is to use dbms_monitor to enable tracing - some day sql_trace may just go away.

But for now, totally harmless.


ORA-32004

MAXIMUS, August 30, 2011 - 2:48 pm UTC

dear friend you should easily delete all lines which contains dump in it. these lines are located in database folder in the file init.ora
delete 3 line which contains dump and restart and you will not get the error

Nice

mohib, December 18, 2012 - 4:41 am UTC

Ya u ve to del d lines.. v usefull my db is up without errors :):):)
Tom Kyte
December 18, 2012 - 1:16 pm UTC

how do you even work in real life? I have no clue what you were even trying to express.

I'm glad you are happy, but no one knows what you are trying to say.

Abiven, July 17, 2017 - 10:19 am UTC

In 12.2.0.1 When I use select:
name from v$obsolete_parameter where isspecified='TRUE';
I got nothing:
no rows selected

Neverthless using this query I got the obsolete parameter:
select NAME,VALUE,ISDEPRECATED,ISDEFAULT from v$parameter where ISDEPRECATED='TRUE' and ISDEFAULT='FALSE';

Result:
NAME VALUE ISDEP ISDEFAULT
------------ ----------------------- ----- ---------
utl_file_dir /base/EIS3/trace/utldir TRUE FALSE

Enjoy :-)
Jean Christophe Abiven
Connor McDonald
July 24, 2017 - 1:50 am UTC

deprecated != obsolete

[but please dont ask me to explain the difference]

:-)

Resetting hidden obsolete parameters

Burak, October 16, 2018 - 8:37 am UTC

Hello,

I get the following after 12c2 upgrade, and try to reset hidden variable but getting the following error. Is there a special syntax for hidden variables?

SQL> startup;
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
SQL>select name from v$obsolete_parameter where isspecified='TRUE';

NAME
------------------------------
_optimizer_adaptive_plans

SQL>alter system reset "_optimizer_adaptive_plans" scope=spfile;
alter system reset "_optimizer_adaptive_plans" scope=spfile
*
ERROR at line 1:
ORA-00922: missing or invalid option

SQL> alter system reset '_optimizer_adaptive_plans' ;
alter system reset '_optimizer_adaptive_plans'
*
ERROR at line 1:
ORA-00922: missing or invalid option





Connor McDonald
October 17, 2018 - 4:45 am UTC

It is not that is it hidden, but that the parameter is *gone* in 12.2, so it is similar to trying:

SQL> alter system reset "xx" scope=spfile;
alter system reset "xx" scope=spfile
*
ERROR at line 1:
ORA-00922: missing or invalid option


You can

- create a pfile from your spfile
- remove the values
- create the spfile from your fixed spfile.

More to Explore

VLDB

If you are new to partitioning, check out Connor McDonald's introduction series here.

VLDB

Documentation set on VLDB and Partitioning.