Hi There,

I'm running II2.6/0305 (int.lnx/00) patch9892.

I have a database, which on a ckpdb - run by ingres, but which
specifies the -u<dbowner> flag gives the errors:
::[II_JSP , 0807c100]: Tue Mar 28 09:53:58 2006
E_DMA476_LGALTER_DBSTATE Unexpected database state. The
database with ID code 16,5455 was found to be in state 00000003,
which is erroneous. The LGalter() code was LG_A_RESUME.
::[II_JSP , 0807c100]: Tue Mar 28 09:53:58 2006
E_DM900B_BAD_LOG_ALTER Error altering the characteristics of
the logging system, characteristics: 00000030.

::[II_JSP , 0807c100]: Tue Mar 28 09:53:58 2006
E_CL1039_LK_RELEASE_BAD_PARAM LKrelease() failed due to
a lock id bad parameter; input lock id = 2; the system lock type = 0; the
system id = 2.
::[II_JSP , 0807c100]: ULE_FORMAT: Couldn't look up
message 3901b (reason: ER error 10903)
E_CL0903_ER_BADPARAM Bad parameter

::[II_JSP , 0807c100]: Tue Mar 28 09:53:58 2006
E_DM1128_CPP_RESUME Error occurred requesting LG to resume
stalled transactions.
::[II_JSP , 0807c100]: Tue Mar 28 09:53:58 2006
E_DM110B_CPP_FAILED Error occurred checkpointing the database.

However, when I run the checkpoint as ingres without the -u flag the
checkpoint succeeds.

Anyone got any ideas whats going on.

Martin Bowes
--
Random Duckman Quote #55:
Duckman: I am not an animal! Well, okay, I'm kind of an animal. I
mean, a
few of my features are animal- like and I don't wear clothes, and I
smell a little outdoorsy most of the time, but I have a job and I
talk and stuff, so when I say I'm not an animal...
I think, technically, I'm on solid ground.

Not sure if this is your problem, but I have seen errors on linux, with
R3, when checkpointing as a non-ingres user. The cause was that the C
compiler wasn't installed when ingres was. Installing this, then
running "iilink -noudts" OTOH fixed the problem. If I remember
incorrectly, try the manual. It's definitely there for R3 (possibly
"getting started for linux")

Hi Simon,

Don't think so in this case as after every install/patch install on
linux I run the iilink -noudts anyway.

The database in question was created by the user. But for
some bizarre reason, every now and then, the createdb will fail. The
user 'thinks' this database was one which had a bad create.

Once the create failure occurs then it fails for the every user - including
ingres. The only way to clear the problem is to shutdown and restart the
installation.

I've seen this happen twice now. After the last restart, I ran 700
consecutive createdbs with no error. I'm out of ideas...

Marty