Re: upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-12 Thread Karel Bos
Hi, After expanding the C: drive to 20GB of free space the upgrade DB proces completed succesfully. Clearly the free space check is not working properly (when using mounted disks on windows). All in all, 7.1 is running now. Kind regards, Karel 2014-02-12 0:35 GMT+01:00 Saravanan

upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-11 Thread Karel Bos
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.

Re: upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-11 Thread Zoltan Forray
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@gmail.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.

Re: upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-11 Thread Karel Bos
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 zfor...@vcu.edu: What is your ACTIVELOGSIZE set to? Maybe it is enforcing that limit, not the available free space? On

Re: upgrade V6.3.4.0 to V7.1.0.0 on Windows ended not well :(

2014-02-11 Thread Saravanan
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