ORA-01155: the database is being opened, closed, mounted or dismounted

ora.scan1.vip  ora....ip.type ONLINE    ONLINE    m3          

[grid@m1 ~]$ crs_start ora.mes.db

Attempting to start `ora.FRA.dg` on member `m2`

Attempting to start `ora.mes.db` on member `m3`

Attempting to start `ora.mes.db` on member `m1`

Start of `ora.FRA.dg` on member `m2` succeeded.

Attempting to start `ora.mes.db` on member `m2`

CRS-5017: The resource action "ora.mes.db start" encountered the following error: 

ORA-03113: end-of-file on communication channel

Process ID: 14163

Session ID: 288 Serial number: 1

. For details refer to "(:CLSN00107:)" in "/u01/app/grid/11.2.0/log/m3/agent/crsd/oraagent_oracle/oraagent_oracle.log".

Start of `ora.mes.db` on member `m3` failed.

Attempting to stop `ora.mes.db` on member `m3`

Stop of `ora.mes.db` on member `m3` succeeded.

CRS-2632: There are no more servers to try to place resource 'ora.mes.db' on that would satisfy its placement policy

我的RAC报错：

alter.log-路径：

more /u01/oracle/diag/rdbms/mes/mes3/trace/alert_mes3.log 

现在在实例3上报错：

下面：

ARC0: STARTING ARCH PROCESSES COMPLETE

Errors in file /u01/oracle/diag/rdbms/mes/mes3/trace/mes3_ora_ 14163.trc:

ORA- 19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.

ORA- 17502: ksfdcre:4 Failed to create file +FRA

ORA- 15041: diskgroup "FRA" space exhausted

*************************************************************

WARNING: A file of type ARCHIVED LOG may exist in

db_recovery_file_dest that is not known to the database.

Use the RMAN command CATALOG RECOVERY AREA to re-catalog

any such files. If files cannot be cataloged, then manually

delete them using OS command. This is most likely the

result of a crash during file creation.

*************************************************************

ARCH: Error  19504 Creating archive log file to '+FRA'

Errors in file /u01/oracle/diag/rdbms/mes/mes3/trace/mes3_ora_ 14163.trc:

ORA- 16038: log 5 sequence# 13 cannot be archived

ORA- 19504: failed to create file ""

ORA- 00312: online log 5 thread 3: '+DATA/mes/onlinelog/group_5.266. 830189293'

ORA- 00312: online log 5 thread 3: '+FRA/mes/onlinelog/group_5.259. 830189299'

USER (ospid:  14163): terminating the instance due to error  16038

Mon Nov 11 22:45:05 2013

System state dump requested by (instance=3, osid= 14163), summary=[abnormal instance termination].

System State dumped to trace file /u01/oracle/diag/rdbms/mes/mes3/trace/mes3_diag_ 14090.trc

Dumping diagnostic data in directory=[cdmp_ 20131111224505], requested by (instance=3, osid= 14163), summary=[abnormal insta

nce termination].

解决： 数据库夯住了 mount状态

数据库夯在这里了 但是 打开另外一个窗口 显示：

ORA-01155: the database is being opened, closed, mounted or dismounted

startup 命令 

加载到 mount 状态 到 open状态 被卡住了！

在metalink上没有到解决办法。 看来这个错误很少见 ！

This is the text of the ORA-01155 error message from the alert log:

Errors in file /u02/app/oracle/diag/rdbms/drpdb/drpdb1/trace/drpdb1_m000_15160.trc:
ORA-01155: the database is being opened, closed, mounted or dismounted

Answer:    Here is what the oerr utility has to say about the ORA-01155 error:

ORA-01155: the database is being opened, closed, mounted or dismounted 

Cause: The requested operation needs the instance to be in a particular state but the state is being changed.

Action: Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work.

To diagnose the ORA-01155 error, you can run this query:

select switchover_status from v$database;

select 
   SID, 
   PROCESS, 
   PROGRAM 
from 
   v$session 
where 
   type = 'USER' 
and 
   SID (select DISTINCT SID from v$mystat);

If the second query returns data, then re-run the switchover command:

SQL>ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;