oracle background_dump_dest,修改background_dump_dest等参数重启后报ORA-32004

这几天看日志看的有点累。想说规范整理一下，修改了如下2个参数：background_dump_dest  user_dump_dest。结果启动后报

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

吓我一跳。还好还是及时启动起来了。最后查了下 原来ORACLE 11G已经废弃了这2个参数了。

参数

1、 USER_DUMP_DEST  11g取消了

引用

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.

2、 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.

所以只要取消设定这2个参数就可以了。另外在检查的过程中 我使用create pfile from spfile 会报错。必须使用create pfile='/tmp/pfile.ora' from spfile。网上查了下说是权限的问题。没兴趣深究了。