TSM Server not Starting

winprod

ADSM.ORG Member
Joined
Sep 7, 2011
Messages
17
Reaction score
0
Points
0
Hi need some help.

The service is not starting (it starts en stops automatically)

After trying to start it in the foreground I get the following.


C:\Program Files\Tivoli\TSM\server>dsmserv.exe
ANR7800I DSMSERV generated at 15:32:07 on Aug 5 2014.

Tivoli Storage Manager for Windows

Version 6, Release 3, Level 5.000


Licensed Materials - Property of IBM


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


ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.opt.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR1380I The buffer pool monitor switch is enabled.
ANR1628I The database manager is using port 51500 for server connections.
ANR0171I dbicmd.c(240): Error detected on 1:1, database in evaluation mode.
ANR0175E dbicmd.c(240): Space exhausted for one or more of the following: DB, LOG, or instance directory.
ANR0162W Supplemental database diagnostic information: -1:57011:-968 ([IBM][CLI Driver][DB2/NT64] SQL0968C The file
system is full. SQLSTATE=57011
).

Transaction hash table contents (slots=256):
*** no transactions found ***

Lock hash table contents (slots=3002):
Note: Enabling trace class TMTIMER will provide additional timing info on the following locks
*** no locks found ***
ANR9999D_4205883037 pkLogicAbort(pkthread.c:942) Thread<0>: Run-time assertion "THRV->thread[ 0 ].nNtThreadId !=
tlsMyNtThreadId" at pkthread.c(1839) failed.
ANR7837S Internal error THR007 was detected.


Entering exception handler.
Leaving exception handler.

C:\Program Files\Tivoli\TSM\server>
 
Looks like there is not enough space for DB or Log file. Check your file system and make sure you got enough space. Best practice is to keep separate Log, DB and Archive log file to different file system.
 
Best practice is to keep separate Log, DB and Archive log file to different file system.
Yes, different and dedicated filesystems. And for the DB, 2 filesystems per 1TB of space allocated.
 
Always perform full database daily. That helps for archive logs. Once database is completely good, Archive logs cleared out.
 
Back
Top