Hi all.

Anybody seen this before:
[ingsov@palko ~]$ createdb test
Creating database 'test' . . .

E_US0082 Error occurred updating the IIDATABASE table in the IIDBDB
database.
Check error log (errlog.log) for more information.
(Tue Jun 9 15:09:59 2009)

Creation of database 'test' abnormally terminated.

This is the only error, errlog.log does not tell anything, even not
that message above, other logs neither.

What is strange here is that I have successfully created databases
before in this same installation. Everything else (abf, reports, ...)
works well.

Any glues? What's going on?

Ingres version is
Ingres Linux Version II 9.3.0 (int.lnx/138)NPTL

-Jukka-

Hi,

IIDATABASE & IIDBDB in uppercase ... hum ... don't you have a SQL 92
compatibility issue ?

Hope this help,
--
Jean-Pierre Zuate
La Fage Conseil
+33(0)6 11 40 11 09
jean-pierre.zuate (AT) lafageconseil (DOT) fr
http://lafageconseil.fr/


2009/6/9 Jukka Hartikainen <jukka.p.hartikainen (AT) jyu (DOT) fi>

Strange; I would guess either a corrupt iidatabase table or there is an
outstanding lock on the table that is preventing the insertion of the
new record. Have you tried re-cycling the installation to clear out any
spurious locks? What happens when you try to "select * from iidatabase"?


--
stephenb

Select * from iidatabase works well, infodb iidbdb instead says that
iidbdb is inconsistent:
ingres@palko ~]$ infodb iidbdb
==================Wed Jun 10 07:31:36 2009 Database
Information=================

Database : (iidbdb,$ingres) ID : 0x00000001 Default collation : default
Unicode enabled : No
Extents : 5 Last Table Id : 279
Config File Version Id : 0x00060001 Database Version Id : 8
Mode : DDL ALLOWED, ONLINE CHECKPOINT ENABLED
Status : JOURNAL,CKP,CFG_BACKUP

The Database is Inconsistent.
Cause of Inconsistency: OPEN_COUNT
The Database has been Checkpointed.
The Database is Journaled.

Journals are valid from checkpoint sequence : 1
....

Cause is "OPEN_COUNT". What open count and why? Normally, if a
database is inconsistent you can't do anything, "database is
inconsistent". Now everything else works well...

Can I do "verifydb -mreport -sdbname "iidbdb" -oforce_consistent"
without any risks or is there any "tricks" to get rid of this
"open_count"

-Jukka-

O.K...that explains it. A database goes inconsistent with OPEN_COUNT
when you do a hard shutdown of the DBMS (e.g. kill -9 or "stop server"
in iimonitor) and someone is connected to the database. The CNF file
keeps a count of the number of active sessions in the database (the open
count), and a hard shutdown will exit the DBMS without re-setting it
properly. Normally the recovery server will fix this when doing a cold
start after the shutdown, maybe the error log or DBMS will explain why
it didn't.

In any case, for iidbdb, this is an easy fix. By default this database
is checkpointed and journalled, and it doesn't get many updates. All you
need to do is run rollforwarddb on it, which should take less than 10
minutes.

BTW: I would create another checkpoint afterwards.

Verifydb will fix the problem but don't use verifydb if you can help
it, it's unsupported and it may create some nasty inconsistencies in the
catalogs.


--
stephenb

Check the $II_SYSTEM/ingres/files/errlog.log for more information.
It may be that iidbdb is inconsistent. Try "sql iidbdb". That should
tell you if there is a problem connecting to iidbdb. If the iidbdb is
inconsistent you may need to use verifydb with -oforce_consistent. Use
with caution. Is this a production DB?


--
hanal04

Jukka,

As everyone has said, forcing the database consistent using the
verifydb command is the solution...

However, before you do that, you need to understand how it got
into this state.

grep -i the errlog.log for the word consistent to understand when
it was marked as bad then look in the logs around this time to
understand why...

If you haven't cycled the ingres installation, check what ingres
processes you have running (and the quantity)... for example there
should only be one DMFRCP etc in an installation...

If you're in a High Availability system - do you have ingres
running on both nodes at the same time ?

I'm sure there are many more scenarios for OPEN_COUNT to be
incorrect, but knowing why your installation has reached this
situation is an extremely important step that you must achieve before
issuing a verifydb command to resolve access.

Cheers - my 2p

Gary