ILCattivo
ADSM.ORG Senior Member
So, for my sins I have been tasked with attempting to reduce the size of a TSM DB. Here's the problematic situation though.. <GULP>
Platform = AIX
TSM Ver - 6.3.3 <- EOS I know..!!
DB2 Ver = 9.7
TSM has been handling the DB Re-organization daily and has been completing successfully.
Tables excluded from TSM based Re-org are :-
ARCHIVE_OBJECTS
BACKUP_OBJECTS
BF_AGGREGATED_BITFILES
BF_BITFILE_EXTENTS
Now, here's where it starts to get a bit ugly...
So, what are my options here?
I was thinking along the lines of Backing up the database (To another disk).. and going down the dsmserv cmd route of removing it and blowing it away to make the available space back to 100%, but would the restore of the DB still place back all of the unwanted rubbish and not restore it clean? What would be the procedure for doing this if it were to work?
Thoughts please if I may?
Thanks
Platform = AIX
TSM Ver - 6.3.3 <- EOS I know..!!
DB2 Ver = 9.7
TSM has been handling the DB Re-organization daily and has been completing successfully.
Tables excluded from TSM based Re-org are :-
ARCHIVE_OBJECTS
BACKUP_OBJECTS
BF_AGGREGATED_BITFILES
BF_BITFILE_EXTENTS
Now, here's where it starts to get a bit ugly...
- TSM DB Size is at 96-97% capacity
- No further physical storage available to increase the capacity.
- Not enough available free capacity to run Offline re-org. Its fails stating as such...
- Removal of large file spaces (18+ TB) makes no difference to TSM DB size or shrinkage.
So, what are my options here?
I was thinking along the lines of Backing up the database (To another disk).. and going down the dsmserv cmd route of removing it and blowing it away to make the available space back to 100%, but would the restore of the DB still place back all of the unwanted rubbish and not restore it clean? What would be the procedure for doing this if it were to work?
Thoughts please if I may?
Thanks