Rollforward error with 6.4/04

From: rjm@merkle.baaqmd.gov (Morey, Robert)
Subject: Re: Rollforward error
Date: 29 Jul 1996 19:26:43 -0400

        Hello,

        If this is the same error, it was fixed in 6.4/06; the following is from
the release notes for 6.4/06:

rollforward of an update to a btree secondary index would fail with 
E_DM93E4_BAD_INDEX_PUT (bug # 52462)

        Good luck--Robert

------------------------------------------------------------------------------
- Robert J. Morey, Systems Analyst, Bay Area Air Quality Management District -
-      San Francrisco, California, rmorey@baaqmd.gov, ideamen@well.com       -
-    Slay a sacred cow today         On a clear disk you can seek forever    -
-                      Dare to victualize whirled peas.                      -
------------------------------------------------------------------------------

______________________________ Reply Separator _________________________________
~Subject: Rollforward error
Author:  T.R.Screeton@leeds.ac.uk at Internet
~Date:    7/29/96 10:20 AM


Dear all,

We are using ingres version 6.4/04
A database is checkpointed and most (not all, but all critical) tables are 
journalled.
On trying to rollforward from the last checkpoint to a particular point in time
  rollforwarddb +c +j -e26-jul-1996:10:50:00 dbname
we get an error about half way through the process

Any ideas would be most welcome

The following is the excerpt from errlog.log

      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:48 1996 
      E_DM93E4_BAD_INDEX
_PUT   An error was encountered storing an index entry on a Btree index page. 
Tab le person_id               , owned by ecles                   , in database 
user_ admin              , was the failing table. Entry 86 on page 14 (type   
0x0000014 0, containing 86 entries) at offset -1 was the erroneous entry.
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:48 1996 
      E_DM93B9_BXINSERT_
ERROR  Internal Btree error encountered in dm1bxinsert().
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:48 1996 E_DM9262_DM1B_PUT 
       Error occurred adding a record.
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:48 1996 E_DM960F_DMVE_REP 
       Error recovering REPLACE operation.
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:51 1996 
      E_DM1306_RFP_APPLY
_RECORD        Error occurred attempting to apply roll forward record.
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:51 1996 
      E_DM1306_RFP_APPLY
_RECORD        Error occurred attempting to apply roll forward record.
      ::[II_JSP          , 002F0040]: Fri Jul 26 17:14:51 1996 
      E_DM1301_RFP_ROLL_
FORWARD        An error occurred
that precludes further processing.




From: mdkale@aol.com (MDKale)
Subject: Re: Rollforward error
Date: 29 Jul 1996 11:14:18 -0400

You may be out of luck.  I had a similar problem with 6.4/04.  Was this an
online checkpoint?  Let me give you some options to try.

1), if an online checkpoint, after applying the dump records, run verifydb
against the corrupt indexc(s) to fix it, then try applying journals.

2) pick up rollforward again just after this record in the journal.  If
you have a corrupt index, then you probably are toast though.

3) Write you own recovery programs to process journal entries.  This is
what we had to do.  If nothing else works, let me know and I can tell you
how we did it.

Hopefully, option #1 will work for you.

Mark

Mark Kale                                       mdkale@aol.com
York & Associates, Inc.
(V)  612-831-0077
(F)  612-831-0887
Ingres Q & A
To William's Home Page
Email William