Ошибка ora 32004

I am getting ORA-32004 error while starting the database but all the parameters in spfile are fine. This issue came after upgrade the database from 10g to 11.2.0.4.0

SQL> startup

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

How to fix the ORA-32004 error?

Cause: ORA-32004 causes because one or more obsolete parameters were specified in the SPFILE. These depreciated parameters are still in use by spfile.

Action: See alert log for a list of parameters that are obsolete or deprecated. Remove it from the SPFILE.

You must check alert log to see the names of the parameters that are obsolete.

You can also find the obsolete parameters with this SQL*Plus query:

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

                                           OR

select p.name,p.value
from v$parameter p, v$spparameter s
where s.name=p.name
and p.isdeprecated='TRUE'
and s.isspecified='TRUE';

Once found, you must remove it from the spfile or pfile.  You can use alter system command to remove it from spfile.

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: www.linkedin.com/in/SirDBaaSJoelPerez

Anuradha’s LinkedIn: https://www.linkedin.com/in/dbaanuradhamudgal/

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

Symptoms:

[oracle@vmxdb01.dbaglobe.com ~]$ sqlplus '/ as sysdba'
SQL*Plus: Release 11.1.0.6.0 - Production on Fri Sep 18 14:30:15 2009
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size                  2151248 bytes
Variable Size             612371632 bytes
Database Buffers          448790528 bytes
Redo Buffers                5623808 bytes
Database mounted.



  


                       
  

Solutions:

Deprecated parameters can be found after non-default parameters, for example, in our case, the deprecated parameter is «sql_trace».

Fri Sep 18 14:30:21 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side pfile /opt/app/oracle/product/11.1.0/dbs/initorcl.ora
System parameters with non-default values:
  processes                = 1000
  sessions                 = 1105
  nls_territory            = "SINGAPORE"
  resource_manager_plan    = "DEFAULT_PLAN"
  memory_target            = 1G
  control_files            = "+DATA/orcl/controlfile/control01.ctl"
  control_files            = "+ARC/orcl/controlfile/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.1.0.0.0"
  log_archive_dest_1       = "LOCATION=+ARC/"
  log_archive_format       = "%t_%s_%r.dbf"
  db_create_file_dest      = "+DATA"
  db_recovery_file_dest    = "+ARC"
  db_recovery_file_dest_size= 45000M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
  audit_file_dest          = "/opt/app/oracle/admin/orcl/adump"
  audit_trail              = "DB"
  db_name                  = "orcl"
  open_cursors             = 300
  sql_trace                = FALSE
  diagnostic_dest          = "/opt/app/oracle"
Deprecated system parameters with specified values:
  sql_trace                
End of deprecated system parameter listing
Fri Sep 18 14:30:21 2009
PMON started with pid=2, OS id=29803 
Fri Sep 18 14:30:21 2009
VKTM started with pid=3, OS id=29805 at elevated priority
VKTM running at (20)ms precision

Skip to content