oracle启动报错ORA-32004，查看alert日志，不知道怎么解决？

counter1219

ora-32004bsolete and/or deprecated parameter(s)specified
启动的alert日志里面的内容如下，怎么看出来是哪里的问题？
Mon Apr 28 10:04:20 2014
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 =218
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side pfile /oracle/app/product/11g/db/dbs/initora01.ora
System parameters with non-default values:
  processes                = 1800
  sessions                 = 1985
  sga_max_size             = 8G
  shared_pool_size         = 832M
  spfile                   = "/oratbs/lv_ora_spfile"
  nls_date_format          = "MM/DD/YYYY HH24:MI:SS"
  sga_target               = 4928M
  memory_target            = 8G
  memory_max_target        = 8G
  control_files            = "/oratbs/ora01/lv_ora_ctl01"
  control_files            = "/oratbs/ora01/lv_ora_ctl02"
  control_files            = "/oratbs/ora01/lv_ora_ctl03"
  db_block_size            = 8192
  compatible               = "11.1.0.0.0"
  log_archive_dest_1       = "LOCATION=/oratbs/ora_arch"
  log_archive_format       = "%t_%s_%r.dbf"
  log_buffer               = 3145728
  log_checkpoint_interval  = 0
  log_checkpoint_timeout   = 0
  archive_lag_target       = 7200
  db_recovery_file_dest    = ""
  fast_start_io_target     = 0
  fast_start_mttr_target   = 1800
  undo_tablespace          = "UNDOTBS1"
  undo_retention           = 1800
  remote_os_authent        = TRUE
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  remote_listener          = ""
  parallel_max_servers     = 0
  audit_file_dest          = "/oracle/app/admin/ora01/adump"
  audit_trail              = "NONE"
  db_name                  = "ora01"
  open_cursors             = 300
  pga_aggregate_target     = 819M
  diagnostic_dest          = "/oracle/app"
  max_dump_file_size       = "1024K"
Deprecated system parameters with specified values:
  fast_start_io_target     
  remote_os_authent        
End of deprecated system parameter listing
Mon Apr 28 10:04:23 2014
PMON started with pid=2, OS id=15776
Mon Apr 28 10:04:23 2014
VKTM started with pid=3, OS id=15780
VKTM running at (100ms) precision
Mon Apr 28 10:04:23 2014
DIAG started with pid=4, OS id=15786
Mon Apr 28 10:04:23 2014
DBRM started with pid=5, OS id=15790
Mon Apr 28 10:04:23 2014
PSP0 started with pid=6, OS id=15794
Mon Apr 28 10:04:23 2014
DIA0 started with pid=7, OS id=15798
Mon Apr 28 10:04:23 2014
MMAN started with pid=8, OS id=15802
Mon Apr 28 10:04:23 2014
DBW0 started with pid=9, OS id=15806
Mon Apr 28 10:04:23 2014
DBW1 started with pid=10, OS id=15810
Mon Apr 28 10:04:23 2014
LGWR started with pid=11, OS id=15814
Mon Apr 28 10:04:23 2014
CKPT started with pid=12, OS id=15818
Mon Apr 28 10:04:23 2014
SMON started with pid=13, OS id=15822
Mon Apr 28 10:04:23 2014
RECO started with pid=14, OS id=15826
Mon Apr 28 10:04:23 2014
MMON started with pid=15, OS id=15830
Mon Apr 28 10:04:23 2014
MMNL started with pid=16, OS id=15834
ORACLE_BASE from environment = /oracle/app
Mon Apr 28 10:04:23 2014
ALTER DATABASE   MOUNT
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 889439591
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Mon Apr 28 10:04:27 2014
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery setup failed: using serial mode
Started redo scan
Completed redo scan
1349 redo blocks read, 74 data blocks need recovery
Started redo application at
Thread 1: logseq 2481, block 26380
Recovery of Online Redo Log: Thread 1 Group 3 Seq 2481 Reading mem 0
  Mem# 0: /oratbs/ora01/lv_ora_redo3
Completed redo application of 0.23MB
Completed crash recovery at
Thread 1: logseq 2481, block 27729, scn 182130487
74 data blocks read, 74 data blocks written, 1349 redo blocks read
Thread 1 advanced to log sequence 2482 (thread open)
Thread 1 opened at log sequence 2482
  Current log# 4 seq# 2482 mem# 0: /oratbs/ora01/redo04.log
Successful open of redo thread 1
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
Opening with internal Resource Manager plan
Starting background process FBDA
Mon Apr 28 10:04:32 2014
FBDA started with pid=18, OS id=16004
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Apr 28 10:04:33 2014
QMNC started with pid=19, OS id=16016
Completed: ALTER DATABASE OPEN
Mon Apr 28 10:04:36 2014
Starting background process CJQ0
Mon Apr 28 10:04:36 2014
CJQ0 started with pid=24, OS id=16048
Mon Apr 28 10:14:34 2014
Starting background process SMCO
Mon Apr 28 10:14:34 2014
SMCO started with pid=25, OS id=19764

碉堡蔡

不太懂。不过顶你。

fflixiang

oracle不使用这两个参数了

fflixiang

应该是下面两个参数问题
Deprecated system parameters with specified values:
  fast_start_io_target     
  remote_os_authent        
End of deprecated system parameter listing

www_xylove

......
fast_start_io_target     = 0
remote_os_authent        = TRUE
......

这两个参数是默认参数吗？
为什么默认参数出现在告警日志文件里面？
正确的是，这个参数本来是默认参数，没有任何问题，然后，被修改之后，变成了非默认参数，而该参数在oracle 11.1版本被废弃了，故而报错了。
另外提一句：
告警日志里出现参数是非默认参数，并非你说的默认参数。

jackson198574

回复 14# counter1219

数据库启动的时候会按照pfile里面的参数初始化环境，如果如果写了就会按照参数的值去初始化环境，如果不写的话会按照默认值（比如0或者是false）进行初始化。如果你的数据库有spfile的话，最好先备份一下spfile，然后执行一下create spfile from pfile。确定spfile的存在的话使用命令：show parameter spfile;   
   

counter1219

回复 12# www_xylove
我把下面fast_start_io_targe，remote_os_authent两个参数删除之后，再用pfile重启，确实是没有问题了，这是什么原因呢？只是因为这两个设置为默认值，如果写在pfile文件中，就会报错吗？


   

jackson198574

建议楼主按照12楼www_xylove版主的建议操作一下，如果有条件，尽可能的选择一种备份方式对全库进行备份。

www_xylove

嫌疑：
archive_lag_target
fast_start_io_targe
fast_start_mttr_target
remote_os_authent
去掉这些参数看看。

jackson198574

回复 10# counter1219


    这个参数应该是没问题的，但是可能几个参数之间的设置会互相影响。根据我刚才取的10G和11G的默认设置值来看，FAST_START_MTTR_TARGET的值在10G以后默认为0。有可能有其他参数的修改导致的这个问题，你仔细看一下alert日志里最近有没有什么参数的改动，尤其是alter database或者alter system相关的语句。