Hello everyone,

we have ran into trouble because our Tivoli database has reached 100% and we can't add new volumes.

Diving into TSM documentation, we have seen we could reorganize the database, as estimating process reports we could free about 40 GB of space.

The first step (dsmserv unloaddb) finished without problems, but when we run the next step, which is the dsmserv loadformat command:

./dsmserv loadformat 12 '/dev/rdsk/c1t6d0s3' '/dev/rdsk/c1t4d0s0' '/dev/rdsk/c1t6d0s4' '/dev/rdsk/c1t7d0s4' '/dev/rdsk/c1t6d0s5' '/dev/rdsk/c1t7d0s5' '/dev/rdsk/c1t6d0s0' '/dev/rdsk/c1t7d0s0' '/dev/rdsk/c1t6d0s1' '/dev/rdsk/c1t7d0s1' '/dev/rdsk/c1t6d0s6' '/dev/rdsk/c1t7d0s6' 28 '/dev/rdsk/c1t2d0s0' '/dev/rdsk/c1t4d0s0' '/dev/rdsk/c1t2d0s1' '/dev/rdsk/c1t4d0s1' '/dev/rdsk/c1t2d0s3' '/dev/rdsk/c1t4d0s3' '/dev/rdsk/c1t2d0s4' '/dev/rdsk/c1t4d0s4' '/dev/rdsk/c1t2d0s5' '/dev/rdsk/c1t4d0s5' '/dev/rdsk/c1t2d0s6' '/dev/rdsk/c1t4d0s6' '/dev/rdsk/c1t2d0s7' '/dev/rdsk/c1t4d0s7' '/dev/rdsk/c1t3d0s0' '/dev/rdsk/c1t5d0s0' '/dev/rdsk/c1t3d0s1' '/dev/rdsk/c1t5d0s1' '/dev/rdsk/c1t3d0s3' '/dev/rdsk/c1t5d0s3' '/dev/rdsk/c1t3d0s4' '/dev/rdsk/c1t5d0s4' '/dev/rdsk/c1t3d0s5' '/dev/rdsk/c1t5d0s5' '/dev/rdsk/c1t3d0s6' '/dev/rdsk/c1t5d0s6' '/dev/rdsk/c1t3d0s7' '/dev/rdsk/c1t5d0s7'

(devices are those reported running 'q dbvol' and 'q logvol')

we get the following error:

ANR7800I DSMSERV generated at 12:26:18 on Nov 18 2009.
ANR7801I Subsystem process ID is 29761.
ANR4726I The ICC support module has been loaded.
ANR9999D_3321915101 lvmInstall(lvminst.c:332) Thread<1>: Error creating Logical Partition Table for LOG volume /dev/rdsk/c1t7d0s4.
ANR9999D Thread<1> issued message 9999 from:
ANR9999D Thread<1> 0x00000001017E15B0 OutDiagToCons
ANR9999D Thread<1> 0x00000001017F735C outDiagfExt
ANR9999D Thread<1> 0x0000000100D52EBC lvmInstall
ANR9999D Thread<1> 0x00000001002D5578 admInstallServer
ANR9999D Thread<1> 0x000000010006F940 InstallServer
ANR9999D Thread<1> 0x000000010006B130 main
ANR9999D Thread<1> 0x0000000100067C9C _start

If we try just to remove this disk from the list, we get the same error with the next one, and the same if we remove it again.

Could anyone give a hint about what's going on?

Thanks in advance!


-- Jordi