Dirty Read dbschema?

Hello All, I have a question regarding dbschema. I have a script that copies data on a nightly basis to a reporting database. I wrote the script to capture the schema each night so that any schema changes are automatically incorporated. Occasionally, I cannot capture the schema because of locks in the source database. For this reason, my script retries 40 times before it gives up and pages our primary pager. On rare occasions, even 40 retries is not enough. Is there any way to have dbschema operate on a dirty read basis? The locks preventing dbschema from completing are not due to schema changes but rather from normal day end processing. One other bit of information, this script runs a one box and is capturing schema and copying data from 16 databases in 16 different instances spread across 6 other boxes. The users have become more dependent on these reporting databases and they have begun requiring increasingly fresh data; therefore, some time before the end of the year we will be replacing this process with CDR (aka ER). I hope I don't have to re-engineer this script or put too much effort into rewriting it as its life span is growing short. Here is some pertinent background information: HP-UX 11.00 64-bit IDS 9.21.FC4Xq Thanks Rob Schmitz 913-315-4183 Rob.B.Schmitz@mail.sprint.com

Get my dbschema replacement utility, myschema. It is a full replacement for dbschema with MANY extensions (ex: ability to output dbimport compatible schema files, ability to output update statistics commands to replicate the current level of stats, ability to separate CREATE TABLE and CREATE INDEX other DDL into different files) and bug fixes. Myschema does not use any locks on the database, tables, or system catalogs. Myschema is included in the package utils2_ak available for download from the IIUG Software Repository. Art S. Kagel ----- Original Message ----- From: Ro.... Schmitz <Rob.B.Schmitz@mail.sprint.com> At: 5/28 13:16 > Hello All, > > I have a question regarding dbschema. I have a script that copies data on a > nightly basis to a reporting database. I wrote the script to capture the schema > each night so that any schema changes are automatically incorporated. > Occasionally, I cannot capture the schema because of locks in the source > database. For this reason, my script retries 40 times before it gives up and > pages our primary pager. On rare occasions, even 40 retries is not enough. > > Is there any way to have dbschema operate on a dirty read basis? The locks > preventing dbschema from completing are not due to schema changes but rather > from normal day end processing. > > One other bit of information, this script runs a one box and is capturing schema > and copying data from 16 databases in 16 different instances spread across 6 > other boxes. > > The users have become more dependent on these reporting databases and they have > begun requiring increasingly fresh data; therefore, some time before the end of > the year we will be replacing this process with CDR (aka ER). I hope I don't > have to re-engineer this script or put too much effort into rewriting it as its > life span is growing short. > > Here is some pertinent background information: > > HP-UX 11.00 64-bit > IDS 9.21.FC4Xq > > Thanks > > Rob Schmitz > 913-315-4183 > Rob.B.Schmitz@mail.sprint.com