修改了spfile***.ora的 processes后，oracle启动不了！

估计processes不是数据库启动不了的原因.贴alert_$SID.log文件最后部分,查看具体原因.

下面是alert_$SID.log文件最后部分，
Sat Mar 21 18:38:33 2009
Thread 1 advanced to log sequence 1076
  Current log# 1 seq# 1076 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO01.LOG
Sun Mar 22 09:26:01 2009
Thread 1 advanced to log sequence 1077
  Current log# 2 seq# 1077 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO02.LOG
Sun Mar 22 21:00:45 2009
Thread 1 advanced to log sequence 1078
  Current log# 3 seq# 1078 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO03.LOG
Mon Mar 23 09:26:45 2009
Thread 1 advanced to log sequence 1079
  Current log# 1 seq# 1079 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO01.LOG
Dump file f:\oracle\product\10.2.0/admin/newnad/bdump\alert_newnad.log
Mon Mar 23 10:49:16 2009
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows Server 2003 Version V5.2
CPU                 : 2 - type 586, 1 Physical Cores
Process Affinity    : 0x00000000
Memory (Avail/Total): Ph:1425M/1919M, Ph+PgF:2903M/3820M, VA:1940M/2047M
Mon Mar 23 10:49:16 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Mon Mar 23 10:49:27 2009
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 150
  __shared_pool_size       = 75497472
  __large_pool_size        = 4194304
  __java_pool_size         = 4194304
  __streams_pool_size      = 0
  spfile                   = F:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILENEWNAD.ORA
  sga_target               = 574619648
  control_files            = F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\CONTROL01.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\CONTROL02.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\CONTROL03.CTL
  db_block_size            = 8192
  __db_cache_size          = 482344960
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = F:\oracle\product\10.2.0/flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=newnadXDB)
  job_queue_processes      = 10
  audit_file_dest          = F:\ORACLE\PRODUCT\10.2.0\ADMIN\NEWNAD\ADUMP
  background_dump_dest     = F:\ORACLE\PRODUCT\10.2.0\ADMIN\NEWNAD\BDUMP
  user_dump_dest           = F:\ORACLE\PRODUCT\10.2.0\ADMIN\NEWNAD\UDUMP
  core_dump_dest           = F:\ORACLE\PRODUCT\10.2.0\ADMIN\NEWNAD\CDUMP
  db_name                  = newnad
  open_cursors             = 300
  pga_aggregate_target     = 189792256
PSP0 started with pid=3, OS id=3488
PMON started with pid=2, OS id=3484
MMAN started with pid=4, OS id=3492
DBW0 started with pid=5, OS id=3496
LGWR started with pid=6, OS id=3500
CKPT started with pid=7, OS id=3504
SMON started with pid=8, OS id=3508
RECO started with pid=9, OS id=3512
CJQ0 started with pid=10, OS id=3516
MMON started with pid=11, OS id=3520
Mon Mar 23 10:49:36 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=3524
Mon Mar 23 10:49:36 2009
starting up 1 shared server(s) ...
Mon Mar 23 10:49:41 2009
alter database mount exclusive
Mon Mar 23 10:49:47 2009
Setting recovery target incarnation to 2
Mon Mar 23 10:49:49 2009
Successful mount of redo thread 1, with mount id 2605521605
Mon Mar 23 10:49:49 2009
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Mon Mar 23 10:49:50 2009
alter database open
Mon Mar 23 10:49:54 2009
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Mon Mar 23 10:49:57 2009
Started redo scan
Mon Mar 23 10:49:59 2009
Completed redo scan
312 redo blocks read, 114 data blocks need recovery
Mon Mar 23 10:50:00 2009
Started redo application at
Thread 1: logseq 1079, block 21690
Mon Mar 23 10:50:01 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1079 Reading mem 0
  Mem# 0 errs 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO01.LOG
Mon Mar 23 10:50:02 2009
Completed redo application
Mon Mar 23 10:50:03 2009
Completed crash recovery at
Thread 1: logseq 1079, block 22002, scn 49403247
114 data blocks read, 110 data blocks written, 312 redo blocks read
Mon Mar 23 10:50:22 2009
Thread 1 advanced to log sequence 1080
Thread 1 opened at log sequence 1080
  Current log# 2 seq# 1080 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO02.LOG
Successful open of redo thread 1
Mon Mar 23 10:50:23 2009
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Mar 23 10:50:24 2009
SMON: enabling cache recovery
Mon Mar 23 10:50:41 2009
Successfully onlined Undo Tablespace 1.
Mon Mar 23 10:50:41 2009
SMON: enabling tx recovery
Mon Mar 23 10:50:44 2009
Database Characterset is JA16SJIS
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Mar 23 10:50:56 2009
Starting background process QMNC
QMNC started with pid=18, OS id=3456
Mon Mar 23 10:51:46 2009
Completed: alter database open
Mon Mar 23 10:51:53 2009
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Mar 23 16:18:35 2009
Thread 1 advanced to log sequence 1081
  Current log# 3 seq# 1081 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO03.LOG
Mon Mar 23 22:00:30 2009
Thread 1 advanced to log sequence 1082
  Current log# 1 seq# 1082 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO01.LOG
Tue Mar 24 06:06:53 2009
Thread 1 advanced to log sequence 1083
  Current log# 2 seq# 1083 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO02.LOG
Tue Mar 24 09:18:24 2009
Thread 1 advanced to log sequence 1084
  Current log# 3 seq# 1084 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO03.LOG
Tue Mar 24 15:00:44 2009
Thread 1 advanced to log sequence 1085
  Current log# 1 seq# 1085 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO01.LOG
Tue Mar 24 20:16:00 2009
Thread 1 advanced to log sequence 1086
  Current log# 2 seq# 1086 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\NEWNAD\REDO02.LOG

请问你是怎样改那个spfile的？

数据库正常启动了啊,没有问题.
连不上数据库,估计是listener或者tns没有整对.

spfile是不能手工改的。你没有备份吗？

你如果有一个正常的init.ora的话还可以用pfile启动DB。
STARTUP PFILE=/u01/oracle/dbs/init.ora
然后用
create spfile from pfile;
来创建一个新的spfile了

processes = 150 没改阿，就是默认150啊Completed: alter database open

数据库已经打开了，没问题阿

spfile 不能手工修改，你能用 alter system 命令修改。
或者 create pfile 命令导出为 pfile，修改 pfile 后，用 create spfile 导成 spfile。

SQL>Conn sys/password as sysdba
后，
提示：tns错误，适配器错误。可能是因为监听起不来吧。。

控制面板里面的管理工具->服务里
启动tnsListener服务启动不起来。SQL>Conn sys/password as sysdba
后，
提示：tns错误，适配器错误。

手动启一下
lsnrctl start
看看什么错误信息

重建一下SPFILE吧，网上随便搜了一个帖，你可以参考一下。
http://www.lurenjia.net/article.asp?id=327

诚聘DBA！！！！有意者请联系[email protected]
本科以上学历，计算机或相关专业
-至少2年的Oracle数据库管理的相关经验
-熟悉Oracle的备份恢复，数据迁移，RAC，数据库调优和PL/SQL编写
-熟悉Red Hat和Solaris操作系统及Shell脚本编写
-熟练的英语听说读写能力
-良好的沟通和表达能力
-在高强度和富有挑战的工作环境下，进行有效工作的能力
-富有创造力，工作积极主动，能主动地与项目组其他成员进行合作
-高度认同公司的企业文化：尊重员工，诚实和正直，追求品质和卓越，以客户为中心，恪守个人职责和倡导团队精神，求变创新，专注于技术，社会责任。

谢谢，不过看了参考。只是网页里是说如何创建一个新的spfile。
而我现在是直接连不上SQL>Conn sys/password as sysdba
后，
提示：tns错误，适配器错误。另外控制面板里面的管理工具->服务里
启动tnsListener服务启动不起来。难道要重新安装oracle了吗，郁闷

lsnrctl start ==>看看启动是什么信息

lsnrctl start ==>看看启动是什么信息
没有错误，提示成功。控制面板里面的管理工具->服务里
tnsListener服务可以启动了。
不过：
SQL>Conn sys/password as sysdba
后，
提示：tns错误，适配器错误。

诚聘DBA，地点大连。本科以上学历，计算机或相关专业
-至少2年的Oracle数据库管理的相关经验
-熟悉Oracle的备份恢复，数据迁移，RAC，数据库调优和PL/SQL编写
-熟悉Red Hat和Solaris操作系统及Shell脚本编写
-熟练的英语听说读写能力
-良好的沟通和表达能力
-在高强度和富有挑战的工作环境下，进行有效工作的能力
-富有创造力，工作积极主动，能主动地与项目组其他成员进行合作
-高度认同公司的企业文化：尊重员工，诚实和正直，追求品质和卓越，以客户为中心，恪守个人职责和倡导团队精神，求变创新，专注于技术，社会责任。有意者请联系[email protected]

lsnrctl status 把内容贴出来

谢谢各位，刚才用二进制工具把spfile重新编辑了一下，ok了。多谢各位。加分。

另一种方法：
修改：oracle\product\10.2.0\db_1\database中的int[sid].ora文件。将里面的内容注释掉，替换成ifile = 'c:\oracle\admin\[数据库名]\pfile\init.ora'

调试易

修改了spfile***.ora的 processes后，oracle启动不了！

解决方案 »