Thanks to all, Andy, thanks for the suggestions regarding the script and thanks to all the others for suggestions. Thanks Richard, I too am anxious to have the ability to recover my database, in fact it would be nice not to loose it in the first place. But it does happen and it will happen, I have had to restore 3 TSM databases in production due to multiple SAN-faults corrupting the log and logmirror (running"double mirrored" by OS - AND- TSM) and a RAID-Controller running astray and breaking the database. Maybe bad luck, but getting back to work was rather fast and straightforward and in hindsight a rather pleasing experience. I have the habit of splitting my TSM-servers at 30 GB database to make recovery easy and fast. Richard, I agree: don´t rely fully on DBBackups on file device class, as it all potentially has a single-point-of failure in the controllers: I do additional remote server-to-server DRM backups as dbsnapshots after client operations to be able to revert to points in time where no client data is lost and after creating my copypools to be able to revert to this point very quickly after a loss of the complete TSM-Server shipping the DRM-Server (identical Server/OS/TSM/HBA/microcode/...) with restored database. On these systems we can afford to revert back in time in case of desaster recovery.
On our critical sytems we have an site-failover using synchronous mirroring of anything that is disc-based (db,log,filepools) plus asynchronus standy-instances at the remote sites with dbbackups waiting to be restored. We use an additional product making site-disaster recovery a three-mouseclick-action by the operations crew, works like a charm. Regarding my initial question, I haven´t come up with an explanation yet, the workaround that we have is adding select * from db where backup_chg_pct>=100 if(rc_ok) goto ba_full works like a charm... Regards, Markus -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. ______________________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
