一次由于arch参数导致oracle11g2 rac 无法启动解决过程
2011-06-27 21:49
609 查看
晚上接到用户电话由于ups停电检修,需关闭rac。shutdown immediate 时hang住,abort关闭,但startup时报错:
SQL> startup
ORACLE instance started.
Total System Global Area 1.3629E+10 bytes
Fixed Size 2194168 bytes
Variable Size 6912214280 bytes
Database Buffers 6677331968 bytes
Redo Buffers 37339136 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 4982
Session ID: 35 Serial number: 3
检查alertlog发现:
Mon Jun 27 20:53:49 2011
ARC1 started with pid=37, OS id=5167
SUCCESS: diskgroup ARCH was mounted
Errors in file /u01/app/oracle/diag/rdbms/zlsora9/zlsora92/trace/zlsora92_ora_5150.trc:
ORA-16038: log 3 sequence# 3 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 3 thread 2: '+DATA/zlsora9/redo03.log'
ORA-15173: entry 'zlsora9' does not exist in directory '/'
Mon Jun 27 20:53:49 2011
System state dump requested by (instance=2, osid=5150), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/zlsora9/zlsora92/trace/zlsora92_diag_5089.trc
Mon Jun 27 20:53:49 2011
ARC2 started with pid=38, OS id=5169
USER (ospid: 5150): terminating the instance due to error 16038
Dumping diagnostic data in directory=[cdmp_20110627205349], requested by (instance=2, osid=5150), summary=[abnormal instance termination].
Instance terminated by USER, pid = 5150
突然想起来前段时间打开arch时,设置log_archive_dest='+arch/zlsora9',但+arch下并没有zlsora9这个目录,问题找到了,下面解决就很容易了.
解决:
QL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH/zlsora9
Oldest online log sequence 10
Next log sequence to archive 10
Current log sequence 11
SQL>
SQL> alter system set log_archive_dest='+arch';
System altered.
SQL>
SQL>
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 10
Next log sequence to archive 10
Current log sequence 11
SQL>
SQL>
SQL> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1.3629E+10 bytes
Fixed Size 2194168 bytes
Variable Size 6912214280 bytes
Database Buffers 6677331968 bytes
Redo Buffers 37339136 bytes
Database mounted.
Database opened.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 13
Next log sequence to archive 14
Current log sequence 14
同理在2号机修改log_archive_dest='+arch';startup正常.
修改参数时要小心呀!
SQL> startup
ORACLE instance started.
Total System Global Area 1.3629E+10 bytes
Fixed Size 2194168 bytes
Variable Size 6912214280 bytes
Database Buffers 6677331968 bytes
Redo Buffers 37339136 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 4982
Session ID: 35 Serial number: 3
检查alertlog发现:
Mon Jun 27 20:53:49 2011
ARC1 started with pid=37, OS id=5167
SUCCESS: diskgroup ARCH was mounted
Errors in file /u01/app/oracle/diag/rdbms/zlsora9/zlsora92/trace/zlsora92_ora_5150.trc:
ORA-16038: log 3 sequence# 3 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 3 thread 2: '+DATA/zlsora9/redo03.log'
ORA-15173: entry 'zlsora9' does not exist in directory '/'
Mon Jun 27 20:53:49 2011
System state dump requested by (instance=2, osid=5150), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/zlsora9/zlsora92/trace/zlsora92_diag_5089.trc
Mon Jun 27 20:53:49 2011
ARC2 started with pid=38, OS id=5169
USER (ospid: 5150): terminating the instance due to error 16038
Dumping diagnostic data in directory=[cdmp_20110627205349], requested by (instance=2, osid=5150), summary=[abnormal instance termination].
Instance terminated by USER, pid = 5150
突然想起来前段时间打开arch时,设置log_archive_dest='+arch/zlsora9',但+arch下并没有zlsora9这个目录,问题找到了,下面解决就很容易了.
解决:
QL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH/zlsora9
Oldest online log sequence 10
Next log sequence to archive 10
Current log sequence 11
SQL>
SQL> alter system set log_archive_dest='+arch';
System altered.
SQL>
SQL>
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 10
Next log sequence to archive 10
Current log sequence 11
SQL>
SQL>
SQL> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1.3629E+10 bytes
Fixed Size 2194168 bytes
Variable Size 6912214280 bytes
Database Buffers 6677331968 bytes
Redo Buffers 37339136 bytes
Database mounted.
Database opened.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 13
Next log sequence to archive 14
Current log sequence 14
同理在2号机修改log_archive_dest='+arch';startup正常.
修改参数时要小心呀!
相关文章推荐
- 一次权限修改导致的RAC无法正常启动的问题的解决
- 记录由于一次强制断电导致的服务器无法启动的恢复过程
- 由于回滚段参数设置存在问题导致数据库无法启动
- 解决由于启动用户实例的进程时出错,导致无法生成 SQL Server 的用户实例
- 错误初始化参数导致无法启动的解决办法
- 一次误修改sga_max_size值过大后导致数据库无法启动的解决方法
- 由于计算机磁盘硬件配置出现问题,导致 Windows 无法启动的解决方法 由于计算机磁盘硬件配置出现问题,导致 Windows 无法启动
- 修改oracle系统参数spfile导致数据库无法启动解决
- 一次安全狗参数配置导致断网的解决过程
- 一次由于设置错误,导致无法进入gnome的解决。
- 由于启动用户实例的进程时出错,导致无法生成 SQL Server 的用户实例 解决办法
- 由于回滚段参数设置存在问题导致无法启动
- 由于文件夹目录结构导致MyEclipse无法启动问题解决办法
- RAC由于归档表空间满而无法启动实例的解决
- 由于启动用户实例的进程时出错,导致无法生成 SQL Server 的用户实例,该连接将关闭的解决办法
- 一次简单的AIX磁盘未正常激活导致RAC无法启动的故障排除
- 解决hadoop启动时由于hostname不一致导致DataNode无法正常启动
- 11g rac 修改参数文件导致数据库无法启动 解决方案!
- Rabbitmq由于queen数据持久化错误,导致无法启动的解决办法
- 如何解决由于启动用户实例的进程时出错,导致无法生成 SQL Server 的用户实例。该连接将关闭。