Szymon,
This is a regular hex file output, its written assembler language,
I ran it as far as I could, you are orking with libraries that I am
not familiar with.
basically, you need a good psychiatrist if you know what this stuff
all means.
You are having memory clashes with some other processes that TSM does
not do well with running, and sharing memory with. I dont think this is a
tsm problem, meaning you have something wrong in TSM, its crossing with
something else running.
Beyond that, GABBA GABBA HEY....
Friday, April 28, 2006 12:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
cc:
From: Szymon Kacprzak <Szymon.Kacprzak AT KRONOSPAN DOT PL>
Subject: Re: [ADSM-L] TSM Server 5.2.3 (win 2003) service start problem
Wiadomosc przeskanowana programem antywirusowym. Nie znaleziono wirusow /
This message was anti-virus scanned. No viruses were found.
I'm not sure about the reason of error. I think it's a TSM crash, because
OS is working without errors.
I extended my recovery log and create additional, but it didn't help.
This is a piece of dsmserv.err:
Exception generated: 04/27/2006 16:33:05
Module name: Unavailable
Current version: 5.2.3.0
Build date: Jun 21 2004 16:50:40
Build Type: 32Bit
Exception generated: 04/27/2006 17:47:54
Module name: Unavailable
Current version: 5.2.3.0
Build date: Jun 21 2004 16:50:40
Build Type: 32Bit
Crash dump file:
C:\Program Files\Tivoli\tsm\server\dsmserv.dmp
Exception code:
E0000001 (Unknown) at 001B:7C815DEA
Registers:
EAX=0012BFB4 EBX=00000001 ECX=001A7498 EDX=00000000 ESI=00000000
EDI=0000003B EBP=0012C004 ESP=0012BFB0 EIP=7C815DEA FLG=00000246
CS =0000001B DS =00000023 SS =00000023 ES =00000023 FS =0000003B
GS =00000000
Call stack:
Address Parameters
F()+Offset, File(Line#)
7C815DEA (0xE0000001 0xFFFFFFFF 0x00000000 0x00000000) RaiseException()+3C,
Unavailable
1000665D (0x00000000 0x00000000 0x00000000 0x00000000) pkLogicAbort()+4D,
Unavailable
Exception handler complete. RC: 487
Exception generated: 04/28/2006 10:42:14
Module name: Unavailable
Current version: 5
.2.3.0
Build date: Jun 21 2004 16:50:40
Build Type: 32Bit
Crash dump file:
C:\PROGRA~1\Tivoli\tsm\server\dsmserv.dmp
Exception code:
E0000001 (Unknown) at 001B:7C815DEA
Registers:
EAX=0012BFB4 EBX=00000001 ECX=001A7398 EDX=00000000 ESI=00000000
EDI=0000003B EBP=0012C004 ESP=0012BFB0 EIP=7C815DEA FLG=00000246
CS =0000001B DS =00000023 SS =00000023 ES =00000023 FS =0000003B
Regarding
Szymon Kacprzak
Richard Sims
<rbs AT BU DOT EDU>
Sent by: "ADSM: To
Dist Stor ADSM-L AT VM.MARIST DOT EDU
Manager" cc
<[email protected]
.EDU> Subject
Re: [ADSM-L] TSM Server 5.2.3 (win
2003) service start problem
2006-04-28 14:20
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
Wiadomosc przeskanowana programem antywirusowym. Nie znaleziono wirusow /
This message was anti-virus scanned. No viruses were found.
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
|
