Jazz DB2 regular maintenance
Hi all,
does Jazz DB2 reqiure any regular maintenance from DBA's point of view?
And please, don't say that maintaining Jazz DB2 is like maintaining any other DB2 instance, because DBA usually knows the database he is maintaning (physical model, etc.). Here he is asked to maintain a black-box.
So, an artical or any other documentation would be highly appreciated.
Regards,
Robert
does Jazz DB2 reqiure any regular maintenance from DBA's point of view?
And please, don't say that maintaining Jazz DB2 is like maintaining any other DB2 instance, because DBA usually knows the database he is maintaning (physical model, etc.). Here he is asked to maintain a black-box.
So, an artical or any other documentation would be highly appreciated.
Regards,
Robert
2 answers
Disclaimer: I'm not a DB2 expert, but I play one on TV....
Prior to migrating to Jazz 3 and DB2 9.7 I was able to configure automatic table/index maintenance using info here:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.ha.doc%2Fdoc%2Ft0051354.html
Fortunately, that has carried across to V9.7 and the table/index maintenance runs periodically.
I also struggled with backups as our repository DB grew and went to a full, incremental, delta scheme or just not backing up every day. Those backups were written to disk and later sent to TSM server.
If you're sending db2 backups to disk, try not using compression (if you are) as that can add a good deal of time/load to your machine.
After some money was spent to get keen new hardware (IBM Power7 570) all that that's less of a problem now. I also have luxury of backup direct to a TSM server for both the db2 logs and a full backup.
Prior to migrating to Jazz 3 and DB2 9.7 I was able to configure automatic table/index maintenance using info here:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.ha.doc%2Fdoc%2Ft0051354.html
Fortunately, that has carried across to V9.7 and the table/index maintenance runs periodically.
I also struggled with backups as our repository DB grew and went to a full, incremental, delta scheme or just not backing up every day. Those backups were written to disk and later sent to TSM server.
If you're sending db2 backups to disk, try not using compression (if you are) as that can add a good deal of time/load to your machine.
After some money was spent to get keen new hardware (IBM Power7 570) all that that's less of a problem now. I also have luxury of backup direct to a TSM server for both the db2 logs and a full backup.
I'm keen to know the answer too.
Currently I have nightly online backups configured with a 4hr offline automatic maintenance period configured on the weekend for each DB.
Even then, sometimes DB2 seems flaky and I don't get a backup per night.