[Info-Ingres] incremental recovery failure -
01-13-2010
, 09:08 AM
Hi All,
I'm running two installations, both using II9.2.0+p13556. Call the two
installations A and B.
I'm using incremental recovery to keep a warm spare copy of database
A::ace_pack_live on B.
The hosts differ in the settings of paths for the database locations but
I generally solve that problem with a few symlinks.
I do an initial recovery of A::ace_pack_live on B by:
1. Create an empty database on B which looks like A::ace_pack_live.
2. Copying in all the journals, dumps, checkpoints and configuration
files from A to the correct locations on B.
3. rollforwarddb ace_pack_live +c -j -incremental -norollback
At the end of which the database is accessible and all appears to be OK.
I do subsequent journals by copying in the new journals from A to the
correct locations on B and doing:
rollforwarddb ace_pack_live -c +j -incremental -norollback
However, after a few of these, although I get no error on the
rollforwarddb command, I can no longer connect to the B::ace_pack_live.
Instead it fails at the front end with:
E_QE0086 Error beginning a transaction.
E_SC0206 An internal error prevents further processing of this query.
And in the errlog we see:
E_DM9004_BAD_FILE_OPEN Disk file open error on database:ace_pack_live
table:Not a table
pathname:/ace_vol_1/II/ingres/data/default/ace_pack_live
filename:aaaaaaaa.cnf
open() failed with operating system error 2 (No such file or directory)
E_DM012A_CONFIG_NOT_FOUND The database configuration file was not found.
E_DM9413_RCP_COUNT_OPENS Error tracking open/close database operations
in the recovery process.
E_CL0F0F_LG_DB_INCONSISTENT One of the databases has become
inconsistent. No new transactions may be begun against the inconsistent
database, and no new update operations against the inconsistent database
may be performed by transactions already underway.
But I can easily do an 'ls' on the config file path. Its there!
infodb on ace_pack_live shows a status of:
VALID,JOURNAL,DUMP,ROLL_FORWARD,CFG_BACKUP,INCR_RF P
infodb over the entire installation suggests there are no inconsistent
databases, yet logstat believes there are.
Am I doing something wrong or is this a bug of some kind?
Martin Bowes |