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

转载于：ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance - 清若止水 - 博客园

适用于：Oracle 11g for aix

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

Total System Global Area 1.6602E+10 bytes
Fixed Size                  2244872 bytes
Variable Size            1.3019E+10 bytes
Database Buffers         3556769792 bytes
Redo Buffers               23953408 bytes
Database mounted.
Database opened.，

出现错误提示信息"ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance"。查看background_dump_dest和user_dump_dest两个参数，发现没有变更成功。

删除参数文件中的background_dump_dest和user_dump_dest两个参数，并重启数据库。数据库正常运行。

阅读11g官方文档，发现background_dump_dest和user_dump_dest两个参数在11中废弃了，由新参数diagnostic_dest所取代。

以下是参数说明:

USER_DUMP_DEST

USER_DUMP_DEST specifies the pathname for a directory where the server will write debugging trace files on behalf of a user process.
NOTE
    This parameter is ignored by the new diagnosability infrastructure introduced in Oracle Database 11g Release 1, which places trace and core files in a location controlled by the DIAGNOSTIC_DEST initialization parameter.

BACKGROUND_DUMP_DEST

BACKGROUND_DUMP_DEST specifies the pathname (directory or disc) where debugging trace files for the background processes (LGWR, DBWn, and so on) are written during Oracle operations. An alert file in the directory specified by BACKGROUND_DUMP_DEST logs significant database events and messages. Anything that affects the database instance or global database is recorded here. The alert file is a normal text file. Its filename is operating system-dependent. For platforms that support multiple instances, it takes the form alert_sid.log, where sid is the system identifier. This file grows slowly, but without limit, so you might want to delete it periodically. You can delete the file even when the database is running. 
NOTE
    This parameter is ignored by the new diagnosability infrastructure introduced in Oracle Database 11g Release 1, which places trace and core files in a location controlled by the DIAGNOSTIC_DEST initialization parameter.

DIAGNOSTIC_DEST

As of Oracle Database 11g Release 1, the diagnostics for each database instance are located in a dedicated directory, which can be specified through the DIAGNOSTIC_DEST initialization parameter. The structure of the directory specified by DIAGNOSTIC_DEST is as follows:
<diagnostic_dest>/diag/rdbms/<dbname>/<instname>
This location is known as the Automatic Diagnostic Repository (ADR) Home.For example, if the database name is proddb and the instance name is proddb1, the ADR home directory would be diagnostic_dest>/diag/rdbms/proddb/proddb1.
The following files are located under the ADR home directory:
Trace files - located in subdirectory <adr-home>/trace
Alert logs - located in subdirectory <adr-home>/alert. In addition, the alert.log file is now in XML format, which conforms to the Oracle ARB logging standard.
Core files - located in the subdirectory <adr-home>/cdumd
Incident files - the occurrence of each serious error (for example, ORA-600, ORA-1578,ORA-7445) causes an incident to be created. Each incident is assigned an ID and dumping for each incident (error stack, call stack, block dumps, and so on) is stored in its own file, separated from process trace files. Incident dump files are located in <adr-home>/incident/<incdir#>. You can find the incident dump file location inside the process trace file.

转载：ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance - 清若止水 - 博客园