Hi,
I upgraded my windows TSM Test server from V6.3.4.0 to V7.1.0.0 and it
didn't end well.
Software install went ok. Both DB2 and TSM where upgraded but the upgrade
db part ended with
SQL1762N Unable to connect to database because there is not enough space
to allocate active log files. SQLSTATE=08004
Bit strange because the active log drive had almost 20 GB of free space.
Also any other drive connected to this system had more than 5 GB of free
space.
Looking in the DB2diag log I see this message:
MESSAGE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG
"Not enough space to create primary logs"
DATA #1 : String, 59 bytes
Log path / Free space (bytes) / Log space required (bytes):
DATA #2 : String, 43 bytes
C:\tsm\actlog\vol12\NODE0000\LOGSTREAM0000\
DATA #3 : unsigned integer, 8 bytes
10466885632
DATA #4 : unsigned integer, 8 bytes
17180131328
If I calculate #3 its the amount of free space on C:, but not the amount on
c:\tsm\actlog (which is a mounted disk!).
Trying to relocate the log to another lun just end up with the same error.
Any ideas? If its because of free space calculation going wrong because of
mounted disk, we have a "challenge". All our TSM servers running on windows
use mounted disks instead of drive letters....
I also have a ticket open with IBM support about this, but until now the
support engineer is still thinking an upgrade is the same as a fresh
install and running the install wizzard a 2nd time is a good idea....
All in all, not a great start with TSM V7.1.
Kind regards,
Karel
