On Fri, 10 Sep 2004 14:16:35 -0700, Emerson, Tom
<[log in to unmask]> wrote:

>worst thing that can happen on a friday -- "DBG IS DISABLED; ONLY DBCLOSE
ALLOWED"
>
>dbutil reports "database is logically inconsistent"
>
>adager reports "database was in a dynamic transaction, run dbdriver,diag
and follow the instructions"
>
>dbdriver, option 2 (report result in <base>00 file) aborts (!)
>
>and "transaction logging" is NOT enabled for this database.
>
>where should we look next?
>
>[only positive note: this is essentially a "scratchpad" database -- the
data gets fully recalculated every morning -- and is used to show to-the-
minute inventory levels; if push comes to shove, we simply won't have
reliable/usable data for the rest of the day]
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

Questions--

1) Was this data base restored from a partial backup?

2) Was the message -- "DBG IS DISABLED; ONLY DBCLOSE ALLOWED" from inside
a program updating the database?

3) If so, was it using the DBX procedures?


I think 1) is the most likeliest culprit....

Brian Donaldson.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *