On Apr 28, 2006, at 5:48 AM, Szymon Kacprzak wrote:

...
ANR9999D pkthread.c(835): ThreadId<0> Run-time assertion failed:
"Cmp64(
scanLsn, LOGV->headLsn ) != GREATERTHAN", Thread 0, File logread.c,
Line
395. ...

Szymon -

It appears that you have Log Sequence Number inconsistencies in your
TSM Recovery Log which is thwarting the restart in roll-forward mode.
You don't say why you're in this situation, or if you have TSM
mirroring configured, but there may have been a TSM or OS crash which
created a mess. If it was a TSM crash, see if there is a dsmserv.err
file with info about the event.

I don't think that extending the Recovery Log would serve as a remedy
for this; and your log size is large already. I would recommend
contacting TSM Support for guidance on resolving this. You may have
to end up restarting without the Recovery Log data, and face losing
some updates.

   Richard Sims