TSM Server (service not starting)

[Mtorres81]

Hi I have a Tivoli Storage Manager for Windows Version 5, Release 3, Level 1.0 installed on a Windows 2003 Server, the service when i boot looks good (started) but when i try to open the Administrative Command Line i put the password and it close by himself, and when i try to start form the DOS mode i recieve this message:



C:\Program Files\Tivoli\TSM\server>dsmserv

ANR0900I Processing options file C:\Program Files\Tivoli\TSM\server1\dsmserv.o-

pt.

ANR7800I DSMSERV generated at 04:04:18 on Mar 29 2005.



Tivoli Storage Manager for Windows

Version 5, Release 3, Level 1.0



Licensed Materials - Property of IBM



(C) Copyright IBM Corporation 1990, 2004.

All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure

restricted by GSA ADP Schedule Contract with IBM Corporation.



ANR4726I The ICC support module has been loaded.

ANR0990I Server restart-recovery in progress.

ANR0200I Recovery log assigned capacity is 6500 megabytes.

ANR0201I Database assigned capacity is 16384 megabytes.

ANR0306I Recovery log volume mount in progress.

ANR0287W Contents of the page shadow file dbpgshdw.bdt are not valid.

ANR0285I Database page shadowing started using file dbpgshdw.bdt.

ANR0353I Recovery log analysis pass in progress.

ANR0354I Recovery log redo pass in progress.

ANR0355I Recovery log undo pass in progress.

ANR9999D pkthread.c(838): ThreadId<0> Run-time assertion failed: "CmpLsn(

*pageLsnP, hdrP->updtLsn ) != LESSTHAN", Thread 0, File dblog.c, Line 1118.

ANR9999D ThreadId<0> issued message 9999 from: <-10578598 outDiagf()+168

<-10007209 pkLogicAbort()+39 <-101BD39E DbWriteLogRecordV()+2ee <-101BD50D

dbLogWriteV()+ad <-101BD56B dbLogWrite()+1b <-101F53C0 TbCompExternal()+280

<-101F6179 TbDirectInsert()+219 <-1020153B TbUndoExternal()+12b <-101EF2D4

dbInRecovery()+cc4 <-101EF4BB DbRestartRecovery()+3b <-101C97ED dbInit()+42d

<-10017700 admStartServer()+330 <-10004EF4 adsmMain()+764 <-1000105F

enterAdsmMain()+f <-004010AF main()+5f <-0040267F mainCRTStartup()+143

<-77E523E5 IsProcessorFeaturePresent()+9e

Entering exception handler

Leaving exception handler.







I'm really losted with this error. Thanks for you help.

 

[Harry_Redl]

Hi,





seems your TSM DB is corrupted and you need to restore it .... What happened? Server crashed? Unsuccessfull upgrade/migration attempt?

Do you have DB backup?

Are all disks (TSM DB and RLog volumes) present, visible and writable?



Asking more questions than you



We may help then



Harry

 

[Mtorres81]

Hi Thanks for your response, here is the answers for you question...



The last time when i works with the TSM i have I/O errors with one drive, i change the drive and update the path, but the server still sending I/O errors with one of the drive, so i call dell to askfor change the Drive and i change the drive but when i try to update i write the command on the command line and then close the window, i check the service and it's was down, so i try to restart and then open the Administrative command line, but when i type my user is ok but when i type my password and give enter close the window.



I think some migrations was unsucessfull because the Drive1 was on hung state.

Yes i Have a Backup of the DB but i don't know if the Tapes are on the Library.

The TSM Db are visibles

The logs files are visibles and locked by TSM when i try to open..



<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>Hi,





seems your TSM DB is corrupted and you need to restore it .... What happened? Server crashed? Unsuccessfull upgrade/migration attempt?

Do you have DB backup?

Are all disks (TSM DB and RLog volumes) present, visible and writable?



Asking more questions than you



We may help then



Harry</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>

 

[Harry_Redl]

Hi,



log volumes are locked? So it seems something is running on the background and locking that files ...

I would try to disable the TSM service, reboot and then try to start the server on the foreground - if the error is the same or not.



If it does not help then the DB restore may be the only option - check the volhist.out file for the last DBBackup or DBSnapshot volumes and prepare them



Let me know, then we may proceed



Hope it helps



Harry

 

[Mtorres81]

Thaks for your help and works fine i restore the DB and now everyting is good.