Hi Sabine,

It does indeed appear that you recovery log is corrupt. If my memory serves me 
correctly, this problem is caused by the server option 'MIRRORWRITE LOG' being 
set to PARALLEL by default. This leaves you open to this sort of problem. I 
can't recommend strongly enough to set this value to SEQUENTIAL. There were 
also some improvements made to the server in version 3.1.2.? that should avoid 
this situation. I'd suggest upgrading ASAP (I assume that since you have this 
problem you are running an earlier version).

However, to get back to your current problem, I fear that you have no option 
other than to restore your ADSM database.


regards,

Trevor

> -----Original Message-----
> From: Sabine Rettenberger [SMTP:Sabine.Rettenberger AT WOLF-HEIZTECHNIK DOT 
> DE]
> Sent: Tuesday, 6 July 1999 7:24 pm
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Server-Error: PKTHREAD.C (849)
>
> Hi all,
>
> i have big problems with my ADSM-Server.
> I fear, that the recovery-log is corrupted; and i have no other available
> (because the automatic log-copy has already overwritten the older saves).
>
>
> ANR0990I ADSM Server restart-recovery in progress
> ANR0215W Recovery log volume D:\ADSM_MIRROR\LOG1.DSM is in the offline
> state - VARY ON required
> ANR0200I Recovery log assigned capacity is 548 MB
> ANR0201I Database assigned capacity is 3464 MB
> ANR0306I Recovery log volume mount in progress
> ANR0353I Recovery log analysis plass in progress
> ANR9999D PKTHREAD.C (849): Runt-time assertion failed: "CMP64 (scanLSN,
> LOGV -> headLsn) != GREATERTHAN", Thread 0, File logread.c, Line 376.
>
>
> --->  DR. Watson
> DSMSERV.EXE
> Ausnahme (0xe0000001), Adresse: 0x77f1cd91
>
>
> Thanks to all for help
>
> Sabine Rettenberger