TonyB
ADSM.ORG Senior Member
H,
Bit of a race condition here...as some of you may have gathered from previous posts I'm in test for tsm6.1(.3.4)...
Situation:
The question is - can I update the db2 config, allowing N secondary logs to be dynamically created...without TSM chucking a huge wobbly? Is this even needed? Certainly the DB2 snap indicates that it has way less than 20 GiB of known space...but hey maybe it will dynamically allocate a primary/secondary log based on free filesystem space. Beats me.
I'd be pleased to hear if anyone has done this already...I'm bored of bouncing this TSM instance...rebuilding it will only take a few mins so breakage is no real issue.
Cheers,
T
Bit of a race condition here...as some of you may have gathered from previous posts I'm in test for tsm6.1(.3.4)...
Situation:
- db2 active log filesystem extended to 20 GiB
- TSM "activelogsize" is 7680 (7.5ish GiB) (ho ho, what was I finkin?)
- DB2 primary log count = 15
- DB2 secondary log count = 0
- 10 million object import node operation (delayed commit) is likely going to "fill" the active log in...ooh lets say 4 hours
The question is - can I update the db2 config, allowing N secondary logs to be dynamically created...without TSM chucking a huge wobbly? Is this even needed? Certainly the DB2 snap indicates that it has way less than 20 GiB of known space...but hey maybe it will dynamically allocate a primary/secondary log based on free filesystem space. Beats me.
I'd be pleased to hear if anyone has done this already...I'm bored of bouncing this TSM instance...rebuilding it will only take a few mins so breakage is no real issue.
Cheers,
T