URGEND!! ANR0259E, no TSM-start possible.

[dmdbt]

TSM-DB was full. system core-dumped.



we removed the corefile and defined an new db-datafile (dsmfmt -m -db ...)

Now we tried to extend the database and always get ANR0259E.



futher informations: during restore db we get



ANR9999D lvminit.c(1671): ThreadId<0> Unable to add disk /tsm1/log/logfile1 to

disk table.

Callchain of previous message: 0x0000000100017c74 outDiagf <- 0x0

0000001006129c4 ReadDiskTable <- 0x00000001006144a4 lvmInit <- 0x000000010040a

408 admRestoreDatabase <- 0x0000000100004cd0 RestoreDb <- 0x0000000100002b44 main <-

ANR0259E Unable to read complete restart/checkpoint information from any datab

ase or recovery log volume.





Is DB corrupt? Must we restore the DB with PIT?

Is there any way to bring up TSM without DB-restore?

Does a PIT-db-restore solve the problem?

 

[may]

have a look on your dsmserv.dsk file,



check if you have the right entries in it.....



if the dsmfmt -m -db ... command did not remove something

 

[chad_small]

TSM does not allow extension of the DB when it fills to bring it back up. Only the Log has that option. When the DB fills you have to create a new volume and reinitialize TSM so it updates the .dsk then restore the DB to the now larger DB. This is why Tivoli stresses never letting the DB fill by using the space trigger and always being aware of the DB's capacity.