ADSM-L

Re: TSM Server 5.2.3 (win 2003) service start problem

2006-04-28 07:36:29
Subject: Re: TSM Server 5.2.3 (win 2003) service start problem
From: Richard van Denzel <r.vandenzel AT BSU DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 28 Apr 2006 12:24:52 +0200
Have you created the recovery log the same size as before or did you
increase the size?

Met vriendelijke groet, with kind regards,
 
Richard van Denzel
-----Oorspronkelijk bericht-----
Van: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Namens Szymon
Kacprzak
Verzonden: vrijdag 28 april 2006 11:49
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: [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.
Hi

On start the TSM Server service I have information:

C:\Program Files\Tivoli\tsm\server>dsmserv
ANR0900I Processing options file C:\PROGRA
1\Tivoli\tsm\server\dsmserv.opt.
ANR7800I DSMSERV generated at 16:50:40 on Jun 21 2004.

Tivoli Storage Manager for Windows
Version 5, Release 2, Level 3.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990,2003. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 11368 megabytes.
ANR0201I Database assigned capacity is 44576 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0292W Database page shadow file dbpgshdw.bdt does not exist.
ANR0353I Recovery log analysis pass in progress.
ANR9999D pkthread.c(835): ThreadId<0> Run-time assertion failed: "Cmp64(
scanLsn, LOGV->headLsn ) != GREATERTHAN", Thread 0, File logread.c, Line
395.
Callchain: 104EAD79  outTextf()+1529 <- 10006649  pkLogicAbort()+39 <-
Entering exception handler.
Leaving exception handler.

My database is in roll-forward mode, so I try to restore db succesfully,
but server didn't started.
I've created new recovery log by dsmfmt, but problem didn't disapear.

What can I do more to fix my problem?

Thanks in advance for any help.

Szymon Kacprzak