ADSM-L

Re: Emergency .. HELP

2004-07-15 20:30:58
Subject: Re: Emergency .. HELP
From: "Hashim, Shukrie BSP-IMI/211" <Shukrie.Hashim AT SHELL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 16 Jul 2004 08:29:07 +0800
Steve 

I did a restore db ... then ... some weird message came out .. what is it ? 
should I do an audit ? what is the command for an audit ? 

ANR9999D ssrecons.c(2398): ThreadId<67> Actual:   Magic=40EB4B01, 
SrvId=610717121,
SegGroupId=2931634798798438565, SeqNum=12592898, converted=T.
ANR9999D ssrecons.c(2412): ThreadId<67> Expected: Magic=53454652, SrvId=0, 
SegGroupId=296636929.
SeqNum=1.ANR9999D ssrecons.c(2398): ThreadId<67> Actual:   Magic=4F474943, 
SrvId=12717578,
SegGroupId=4187893577790063616, SeqNum=135201039, converted=T.
ANR9999D ssrecons.c(2412): ThreadId<67> Expected: Magic=53454652, SrvId=0, 
SegGroupId=296677584.
SeqNum=1.
ANR9999D ssrecons.c(2398): ThreadId<67> Actual:   Magic=4C630400, 
SrvId=828322399,
SegGroupId=6009320758017282134, SeqNum=234901590, converted=T.
ANR9999D ssrecons.c(2412): ThreadId<67> Expected: Magic=53454652, SrvId=0, 
SegGroupId=296677701.
SeqNum=1.


ANR8302E I/O error on drive DRIVE2 (/dev/rmt1) (OP=LOCATE, Error Number=5, 
CC=0, KEY=08, ASC=00,
ASCQ=05,
SENSE=70.00.08.00.00.00.00.58.00.00.00.00.00.05.FF.0A.3A.60.40.01.00.09.01.91.00.D5.50.14.00.00.2B.00.-
00.33.7E.00.00.33.35.00.88.33.3D.00.00.00.00.00.7C.77.00.41.F1.05.00.00.00.90.00.00.00.00.00.00.00.80.-
00.00.00.00.00.00.32.39.43.20.20.20.20.00.A0.00.4A.F0.F0.F2.F3.F2.F2.02.00.04.00.00.10.00,
Description=An undetermined error has occurred).  Refer to Appendix D in the 
'Messages' manual for
recommended action.
<< Message number 8944 not available for language EN_US >>
ANR8359E Media fault detected on 3590 volume 002322 in drive DRIVE2 (/dev/rmt1) 
of library 3494LIB.
am I suppose to do an audit ? 




-----Original Message-----
From: Steve Harris [mailto:Steve_Harris AT HEALTH.QLD.GOV DOT AU]
Sent: 14 July 2004 12:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Emergency .. HELP


Shukie,  

You probably don't want to hear this, but this is why you should always have 
that 500MB log file ready to be allocated, and immediatly deallocate it when 
the condition has beed cleared.

I believe that you are stuck with a database restore to point of time of your 
last DB backup.  This is an issue, but in most cases it is not too bad.  Once 
you get back up and running, just run your backups again, and in general they 
will pick up whatever they are missing.

Once you are back on level ground, have a look at the facilty to trigger DB 
backups automatically when the log gets above a given percentage full.

Regards and commisserations

Steve 

Steve Harris
Queensland Health
Brisbane Australia



>>> Shukrie.Hashim AT SHELL DOT COM 14/07/2004 11:01:09 >>>
Hi there

I have reached my maximum extention of recovery log of 13 gb ... now I can't 
even extend it so I can't log in and do a database back up ... can someone tell 
me how to delete some of the recovery log ... is there any other way ? 

Shukrie



***********************************************************************************
This email, including any attachments sent with it, is confidential and for the 
sole use of the intended recipient(s).  This confidentiality is not waived or 
lost, if you receive it and you are not the intended recipient(s), or if it is 
transmitted/received in error.

Any unauthorised use, alteration, disclosure, distribution or review of this 
email is prohibited.  It may be subject to a statutory duty of confidentiality 
if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this email in 
error, you are asked to immediately notify the sender by telephone or by return 
email.  You should also delete this email and destroy any hard copies produced.
***********************************************************************************

<Prev in Thread] Current Thread [Next in Thread>