Some days ago we noticed the above problem when trying to start our NT ADSM
server. We finally 'solved' the problem by restoring the database from a
backup without using the log files - so we lost the backups of the last
three days.

How can we prevent this problem ? Is it a bug which is fixed in 3.2 ?

Was there a better way of solving this problem ?

Any comments are more than welcome !

Regards,

Dirk Rober
FETEW
K.U.Leuven


ANR0900I Processing options file C:\ADSMSERV\server\dsmserv.opt.
ANR7800I DSMSERV generated at 13:08:53 on May 11 1998.

ADSTAR Distributed Storage Manager for Windows NT
Version 3, Release 1, Level 1.3
...
ANR0990I ADSM server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 196 megabytes.
ANR0201I Database assigned capacity is 1856 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR9999D pkthread.c(833): Run-time assertion failed: "Cmp64( scanLsn,
LOGV->headLsn ) != GREATERTHAN", Thread 0, File logread.c, Line 364.