RE: ASM instance will not open HELP!

  

Well, there are errors written to a trace file.  What did it say there?

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Johan Muller
Sent: Wednesday, July 26, 2006 6:13 PM
To: oracle-l-bounce@xxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: ASM instance will not open HELP!

 

From the alert log (rac 2 node cluster on solaris with shared raw
device):

Wed Jul 26 16:43:15 2006
Errors in file /u01/app/oracle/admin/rac1db/udump/rac1db1_ora_6522.trc:
ORA-19504: failed to create file "+ORA_DATA/rac1db/1_244_571764559.dbf"
ORA-17502: ksfdcre:4 Failed to create file
+ORA_DATA/rac1db/1_244_571764559.dbf

It seems to be at the point where the archiver is stuck; I need to add a
disk to the archive diskgroup but the instance will not open.

Wed Jul 26 16:43:15 2006
ARCH: Error 19504 Creating archive log file to
'+ORA_DATA/rac1db/1_244_571764559.dbf'
Reconfiguration complete
Wed Jul 26 16:43:15 2006
ARCH: Failed to archive thread 1 sequence 244 (19504)
Wed Jul 26 16:43:15 2006
Errors in file /u01/app/oracle/admin/rac1db/udump/rac1db1_ora_6522.trc:
ORA-16038: log 2 sequence# 244 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 2 thread 1:
'+ORA_DATA/rac1db/onlinelog/group_2.258.571764567'
USER: terminating instance due to error 16038
Wed Jul 26 16:43:15 2006
Errors in file /u01/app/oracle/admin/rac1db/bdump/rac1db1_lms0_6087.trc:
ORA-16038: log  sequence#  cannot be archived
Wed Jul 26 16:43:15 2006
Errors in file /u01/app/oracle/admin/rac1db/bdump/rac1db1_lmd0_6082.trc:
ORA-16038: log  sequence#  cannot be archived
Wed Jul 26 16:43:15 2006
Errors in file /u01/app/oracle/admin/rac1db/bdump/rac1db1_pmon_6063.trc:
ORA-16038: log  sequence#  cannot be archived
Wed Jul 26 16:43:15 2006
System state dump is made for local instance
System State dumped to trace file
/u01/app/oracle/admin/rac1db/bdump/rac1db1_diag_6065.trc
Wed Jul 26 16:43:16 2006
Trace dumping is performing id=[cdmp_20060726164315]
Wed Jul 26 16:43:21 2006
Instance terminated by USER, pid = 6522

I have searched high and low but no obvious answers - any ideas how to
work around/out of this mess


This electronic message transmission is a PRIVATE communication which contains
information which may be confidential or privileged. The information is 
intended 
to be for the use of the individual or entity named above. If you are not the 
intended recipient, please be aware that any disclosure, copying, distribution 
or use of the contents of this information is prohibited. Please notify the
sender  of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.

JPEG image

Other related posts: