Hi all,

ingres 2.6 /0305
HP 11.11

There are some error messages below in errlog.log when I start
ingres. ingres was not start successfully. I cannot use verifydb since
the DBMS server was not up.
Would you help me?
Thanks a lot.

Database iidbdb is inconsistent
[59922 , 40286140]: Wed Mar 2 18:52:17 2005 E_SC0121_DB_OPEN
Error opening database. Name: iidbdb Owner: $ingres Access
Mode: 00000002
Flags 40000000
LVGSBU01::[59922 , 40286140]: Wed Mar 2 18:52:17 2005
E_SC010D_DB_LOCA
TION Database Location Name: $default Physical Specification:
/opt/sdo/ingres/data/default/iidbdb Flags: 00000003
LVGSBU01::[59922 , 40286140]: Wed Mar 2 18:52:17 2005
W_SX1069_AUD_THREAD_NO_IIDBDB The Security Audit Thread could not open
IIDBDB because it does not exist or is currently unavailable.



Frank

Hi all,
The problem was resolved.
I recreate the transaction log and restart ingres. Then I run
verifydb to mark iidbdb as consistent.


Frank Fan wrote:

"Frank Fan" <jun_fan4 (AT) agilent (DOT) com> wrote

What you did will get Ingres running. It will not necessarily fix anything,
and it is easily capable of making things way worse. In the first place the
database was marked inconsisent because the server had no way to know
whether or not it was consistent. Verifydb just cleared the flag. Any
inconsistencies would remain. In the case of iidbdb you'd probably get away
with it, but for pretty well all other databases, doing that would probably
create quite a mess (or even a disaster).

Sometimes recreating the transaction log is unavoidable, but one should go
to extraordinary lengths to protect it because in general, once you lose it,
you DO lose COMMITTED data, with NO possibility of recovery. It is the
single most critical part of the Ingres installation.

Roy

Hi Roy,
Thanks a lot for your message. It's very helpful.

Roy Hann wrote: