ADSM-L

Re: [ADSM-L] upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-11 18:40:45
Subject: Re: [ADSM-L] upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(
From: Saravanan <evergreen.sarav AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 12 Feb 2014 07:35:48 +0800
Hi Karel,

I think you need to keep your active log size as multiples of 8 so that it can 
create enough 512 mb files in the active log directory.

16384/512=32 active log files

In your case : 19000/512=37.10 active log files


By Sarav
+65-82284384


> On 11 Feb, 2014, at 10:34 pm, Karel Bos <tsm.wad AT GMAIL DOT COM> wrote:
> 
> Hi Zoltan,
> 
> activelogsize               19000
> 
> And there was abt 20GB free space in the active log disk.
> 
> Kind regards,
> 
> Karel
> 
> 
> 2014-02-11 14:52 GMT+01:00 Zoltan Forray <zforray AT vcu DOT edu>:
> 
>> What is your ACTIVELOGSIZE set to?  Maybe it is enforcing that limit, not
>> the available free space?
>> 
>> 
>>> On Tue, Feb 11, 2014 at 8:44 AM, Karel Bos <tsm.wad AT gmail DOT com> wrote:
>>> 
>>> 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
>> 
>> 
>> 
>> --
>> *Zoltan Forray*
>> TSM Software & Hardware Administrator
>> Virginia Commonwealth University
>> UCC/Office of Technology Services
>> zforray AT vcu DOT edu - 804-828-4807
>> Don't be a phishing victim - VCU and other reputable organizations will
>> never use email to request that you reply with your password, social
>> security number or confidential personal information. For more details
>> visit http://infosecurity.vcu.edu/phishing.html
>>