Evan wrote:
> DA Morgan wrote:
>> Evan wrote:
>>
>>> I need a faster answer than I can get from Metalink, although I have
>>> opened a ticket there.
>>>
>>> I have messages that may be errors or may be acceptable notes. Can
>>> you tell me which? This is for a pre-production system one week from
>>> go-live.
>>>
>>> Environment:
>>> Red Hat 3 Enterprise 2.4.21-27.EL
>>> Oracle 10.2.0.2
>>> 3 node RAC (nodes=eps12,eps13,eps14)
>>>
>>> We had a total network failure (DSN, TCP, etc.), but the three raw
>>> shared disks should have still been available (ocr.dat, voting.dat,
>>> spfile+ASM.ora)
>>>
>>> Notes:
>>> = = $ASM_HOME/log/eps14/racg/mdb.log = =
>>> 2007-01-23 16:30:03.114: [ RACG][2548871008]
>>> [12283][2548871008][ora.eps14.ASM3.asm]: clsrdmstart:Fail to start
>>> Oracle in specified mode 5 [7]
>>> 2007-01-23 11:19:58.727: [ RACG][2548871008]
>>> [4470][2548871008][ora.KRONOSP.KRONOSP2.inst]: CLSR-0001: Oracle
>>> error -1034 encountered
>>>
>>> = = $CRS_HOME/log/eps13/racg/ora*vip*log
>>> 2007-01-23 02:50:44.435: [ RACG][2548871008]
>>> [11303][2548871008][ora.eps13.vip]: get_lock: Failed to get lock for
>>> eth0_1 (host=eps13)
>>> get_lock: Failed to get lock for eth0_2 (host=eps13)
>>> get_lock: Failed to get lock for eth0_3 (host=eps13)
>>> get_lock: Failed to get lock for eth0_4 (host=eps13)
>>> get_lock: Failed to get lock for eth0_5 (ho
>>> 2007-01-23 02:50:44.435: [ RACG][2548871008]
>>> [11303][2548871008][ora.eps13.vip]: st=eps13)
>>> get_lock: Failed to get lock for eth0_6 (host=eps13)
>>> get_lock: Failed to get lock for eth0_7 (host=eps13)
>>> get_lock: Failed to get lock for eth0_8 (host=eps13)
>>> get_lock: Failed to get lock for eth0_9 (host=eps13)
>>> get_lock: Failed to get lock for
>>> 2007-01-23 02:50:44.435: [ RACG][2548871008]
>>> [11303][2548871008][ora.eps13.vip]: eth0_10 (host=eps13)
>>
>>
>> Did you submit an RDA? Have you pursued SR escalation? That is the
>> appropriate route.
>
> I have opened the ticket and uploaded the RDA. I could escalate and
> plan on doing this tomorrow.
> However...
> I don't think this is a Sev one issue, so I posted here hoping someone
> had seen these messages and could say
> "Don't Worry" or "Panic and escalate".
>
> Oh Well.
Doesn't look sev 1 to me either but if it is a production system I'd
be sending them frequent emails making sure someone is paying attention
and asking for escalation.
If it isn't a production system ... kick back and find something else
to do for a day or two. Tom Kyte and Jonathan Lewis have great books and
this might be a good time to reread them. ;-)
--
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Received on Thu Jan 25 2007 - 11:54:15 CST
