dbTalk Databases Forums  

Re: [Info-Ingres] createdb failed, OK now, thanks!

comp.databases.ingres comp.databases.ingres


Discuss Re: [Info-Ingres] createdb failed, OK now, thanks! in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jukka Hartikainen
 
Posts: n/a

Default Re: [Info-Ingres] createdb failed, OK now, thanks! - 06-10-2009 , 11:34 PM






Good morning all.

Thanks to everyone, everything is allright now.

So, in a (little bit long) nutshell...
1) createdb failed with error
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.

2) infodb says that iidbdb is inconsistent with OPEN_COUNT

3) errlog.log says that
....
]: Fri May 15 13:28:20 2009 E_SC0129_SERVER_UP Ingres Release II
9.3.0
(int.lnx/138)NPTL Server -- Normal Startup.
PALKO_CC_JYU_FI ::[40983 , 30088 , 00f6d020, dm2d.c:4776
]: Fri May 15 13:28:20 2009 E_DM9327_BAD_DB_OPEN_COUNT The
database ope
n count was greater than zero for the first opener of the database,
therefore th
e database must be considered inconsistent. This can happen when the log
file wa
s not readable; therefore, if any transactions were in progress, they
could not
be backed out. This database must be rolled forward from a checkpoint, or
destr
oyed and recreated.
....

"Consider inconsistent"... Before this I had a diskfull with journals:
]: Fri May 15 12:36:39 2009 E_DM9C00_JNL_FILE_INFO An error
was enc
ountered processing journal file j0000826.jnl in database suti. The
journal sequ
ence number is 826. The checkpoint sequence number is 125. Journal block
number
620 was the most recently used block.
diwrite.c:859 write() failed with operating system error 0 (Success)
palko.cc.jyu.fi ::[II_ACP , 27940 , 00a3a100, dm0j.c:1022
]: Fri May 15 12:36:39 2009 E_DM902E_BAD_JNL_WRITE Error
writing jo
urnal file for database suti file sequence 826 block 620.
diwrite.c:859 write() failed with operating system error 0 (Success)
palko.cc.jyu.fi ::[II_ACP , 27940 , 00a3a100, dm0j.c:1022
]: Fri May 15 12:36:39 2009 E_DM9284_DM0J_WRITE_ERROR Error
occurred w
riting a journal file.
palko.cc.jyu.fi ::[II_ACP , 27940 , 00a3a100, dm0j.c:1022
]: Fri May 15 12:36:39 2009 E_DM9843_ARCH_COPY Error occurred
during th
e Copy phase of the archiver.
palko.cc.jyu.fi ::[II_ACP , 27940 , 00a3a100, dmfacp.c:936
]: Fri May 15 12:36:39 2009 E_DM9815_ARCH_SHUTDOWN Archiver
was tol
d to shut down.

palko.cc.jyu.fi ::[II_ACP , 27940 , 00a3a100, dmfacp.c:1152
]: Fri May 15 12:36:39 2009 E_DM9852_ACP_JNL_WRITE_EXIT Archive
processi
ng cannot continue due to the inability to write journal records for
database suti to the database journal directory,
/var/lib/IngresII/ingres/jnl/default/suti. This is probably due to a lack
of available disk space on the journal device.
The error occurred during an attempt to write to the journal file.
Please chec
k for disk space and the ability to create/write files in the journal
directory.
The archiver log will have more detailed information about the problem,
includ
ing the operating system's return code from the requested operation. To
continu
e archive processing following resolution of the above problem, run the
'ingstar
t -dmfacp' command.
....


Nobody did not notice this because system seems to work allright after
that normal startup untill now, createdb...

But yes, thaks to everybody. I made 'rollforward -v iidbdb' and
that's it, OK.

-Jukka-



Quote:
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
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.