javajockey
ADSM.ORG Senior Member
Hello all,
My TSM server is 6.1.4.2 on Aix 6.1
Storage pools reside on Sepaton VTL
NO TSM Dedup is used.
My current DB size is 921GB after adding 110G Sunday night
The DB,LOG and Archlog resides on VMAX.
My TSM server has started to become unstable. The DB grew 80GB in less than one hour on Sunday night. I presume this could be the DB2 Reorg process using temp space. The server Crashed at Sunday around 19:00 and I added 110GB after I brought the TSM server back up
I had to move some storage pools around and allocate /stgsysbk1 (stgsysbk1 is also on VMAX) to prevent the server from crashing again. I now have 170GB free for a total of 921G
This is what my current dpspace looks like
For some reason, even after I allocated the additional space, My server crashed again on Monday night (24 hours later). I have not received any alerts like I previously did about the DB running low on space. The system just crashed. I opened a PMR with IBM and was informed that DB space will not be available until TSM Server restarts. Can anybody else confirm this? I have requested a second option from IBM because I can't believe that DB2 must be restarted in order to allocate additional space.
Has anybody else experienced unusual Fast DB growth like this (100GB in one hour)
My TSM server is 6.1.4.2 on Aix 6.1
Storage pools reside on Sepaton VTL
NO TSM Dedup is used.
My current DB size is 921GB after adding 110G Sunday night
The DB,LOG and Archlog resides on VMAX.
My TSM server has started to become unstable. The DB grew 80GB in less than one hour on Sunday night. I presume this could be the DB2 Reorg process using temp space. The server Crashed at Sunday around 19:00 and I added 110GB after I brought the TSM server back up
I had to move some storage pools around and allocate /stgsysbk1 (stgsysbk1 is also on VMAX) to prevent the server from crashing again. I now have 170GB free for a total of 921G
This is what my current dpspace looks like
Code:
/stgsysbk1 102,400.00 16.00
/tsm/db/JGB/db9 102,400.00 102,399.84
/tsm/db/JGB/db7 204,800.00 204,799.96
/tsm/db/JGB/db5 20,480.00 20,479.77
/tsm/db/JGB/db4 20,480.00 20,479.80
/tsm/db/JGB/db3 20,480.00 20,479.79
/tsm/db/JGB/db2 20,480.00 20,479.77
/tsm/db/JGB/db1 20,480.00 20,479.95
/tsm/db/JGB/db6 102,400.00 102,399.92
/tsm/db/JGB/db8 102,400.00 102,399.86
/tsm/db/JGB/db10 102,400.00 65,329.14
/tsm/db/JGB/db11 102,400.00 65,329.18
For some reason, even after I allocated the additional space, My server crashed again on Monday night (24 hours later). I have not received any alerts like I previously did about the DB running low on space. The system just crashed. I opened a PMR with IBM and was informed that DB space will not be available until TSM Server restarts. Can anybody else confirm this? I have requested a second option from IBM because I can't believe that DB2 must be restarted in order to allocate additional space.
Has anybody else experienced unusual Fast DB growth like this (100GB in one hour)