在10G中如果设置了废弃的参数,那么在实例启动的时候会报ORA-32004错误。这个时候需要我们自己去查找设置了那些废弃参数。而在11G中,如果设置了废弃参数,那么在后台的alert日志文件中将会显示我们设置了那些废弃参数。
以下摘自11G的实例启动过程:
SQL> STARTUP
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 410112000 bytes
Fixed Size 1336876 bytes
Variable Size 230689236 bytes
Database Buffers 171966464 bytes
Redo Buffers 6119424 bytes
Database mounted.
Database opened.
ALERT文件内容:
Sun Sep 04 10:30:32 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Sun Sep 04 10:30:42 2011
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /u01/app/oracle/product/db11gr2/dbs/spfiletest11g.ora
System parameters with non-default values:
lock_name_space = "TEST11G"
processes = 150
shared_pool_size = 32M
java_pool_size = 4M
streams_pool_size = 4M
sga_target = 320M
memory_target = 0
memory_max_target = 392M
control_files = "/oradata/test11g/control01.ctl"
control_files = "/flashbackdata/test11g/control02.ctl"
db_block_size = 8192
db_cache_size = 100M
compatible = "11.2.0.0.0"
log_archive_dest_1 = "location=/tmp"
db_recovery_file_dest = "/flashbackdata"
db_recovery_file_dest_size= 3852M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=test11gXDB)"
local_listener = ""
result_cache_mode = "MANUAL"
result_cache_max_size = 1M
audit_file_dest = "/u01/app/oracle/admin/test11g/adump"
audit_trail = "NONE"
db_name = "test11g"
pga_aggregate_target = 64M
deferred_segment_creation= TRUE
diagnostic_dest = "/u01/app/oracle"
Deprecated system parameters with specified values:
lock_name_space
End of deprecated system parameter listing
Sun Sep 04 10:30:43 2011
PMON started with pid=2, OS id=3790
Sun Sep 04 10:30:43 2011
VKTM started with pid=3, OS id=3792 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Sun Sep 04 10:30:44 2011
GEN0 started with pid=4, OS id=3796
Sun Sep 04 10:30:44 2011
DIAG started with pid=5, OS id=3798
Sun Sep 04 10:30:44 2011
DBRM started with pid=6, OS id=3800
Sun Sep 04 10:30:44 2011
PSP0 started with pid=7, OS id=3802
Sun Sep 04 10:30:44 2011
DIA0 started with pid=8, OS id=3804
Sun Sep 04 10:30:44 2011
MMAN started with pid=9, OS id=3806
阅读(1493) | 评论(0) | 转发(0) |