ADSM-L

Re: Server Crash!!

1998-05-27 06:26:54
Subject: Re: Server Crash!!
From: "Sanders, David" <DSanders AT INTERNAL.MASSMUTUAL DOT COM>
Date: Wed, 27 May 1998 06:26:54 -0400
Since I tend to be against mirroring, this could change my mind if what
Jason says is true!

There are 2 questions that I have:
1) Does the recovery log get written to after every activity, or does it
buffer activity for awhile before writing?
        *if every activity immediately writes to the primary log and
then to the mirrored-log, then I guess I'd have to rethink the
mirroring thing
        *if every activity DOESN't get written to the primary log
immediately, then mirroring accomplishes nothing since the content
of the buffer is broken and either neither log gets written to, or both
get written to badly.
2) If you have a busy system and a -write to a mirrored log- has to wait
for a write to finish on the primary log, does this negatively affect
performance?
        *I guess this would have to be accepted as a cost for having the
redundancy
        *Or, it's not detectable



Dave Sanders
Sr. Technical Consultant
DSanders AT massmutual DOT com
1295 State St, E060, Springfield, MA 01111
413-744-5095
!@#$%



> -----Original Message-----
> From: Jason Meaden [SMTP:jasonm AT AU1.IBM DOT COM]
> Sent: Wednesday, May 27, 1998 5:47 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Server Crash!!
>
> G'day Scott,
>
> You have a corrupt recovery log due to a partial write that was in
> progress
> when the system died.
>
> You should probably restore the DB from your last backup.  Don't
> bother with a
> rollforward, even if you had that enabled.  It will probably roll in
> the same
> error, and the server would still not start.
>
> You could also do a 'dump load audit' but this is very time consuming.
>
> To prevent the problem occuring again, you could mirror the recovery
> log and
> use:
>
> MIRRORWRITE LOG SEQUENTIAL
>
> ADSM will then ensure that one mirror copy has been properly written
> too before
> beginning to write to the next.
>
> Regards,
> --
>   Mr Jason E Meaden                                  IBM Australia Ltd
>   Software Service Specialist (Asia Pacific)         55 Coonara Avenue
>   IBM Certified Specialist - ADSM             West Pennant Hills  2125
>   Phone: 13 24 26 * Fax: 61 2 9354 7797 * Tie: 49427 * VM: RTP(MEADEN)
>
>
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 27/05/98 19:18:11
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Server Crash!!
>
>
> Help,
>
> We have an NT4 SP3 server running ADSM 3.1.0.2 server.
>
> It has been running fine for ages up until last weekend.
>
> The ADSM server crashed with a Dr Watson error relating to
> DSMSERV.exe.
>
> When we restart the server we get the following message
>
> ANR0990I ADSM server restart-recovery in progress.
> ANR0200I Recovery log assigned capacity is 500 megabytes.
> ANR0201I Database assigned capacity is 2004 megabytes.
> ANR0306I Recovery log volume mount in progress.
> ANR0353I Recovery log analysis pass in progress.
> ANR9999D pkthread.c (825) : Run-time assertion failed:  "Cmp64 (
> scanLsn, LOGV->headLsn )  != GREATERTHAN" , Thread 0, File logread.c,
> Line 364.
>
> Any help would be much appreciated
>
> Regards
>
> Scott
>
>
>
>
<Prev in Thread] Current Thread [Next in Thread>