----------------------------------------------------------------------

ELOQUENCE B.07.00 - patch PE70-0607142

----------------------------------------------------------------------

This patch adds enhancements or fixes defects of the dbrecover utility
as released with Eloquence B.07.00. This patch will be integrated in 
the Eloquence B.07.00 release.

Eloquence B.07.00 must be installed before applying this patch.

Severity:
 PE70-0607142: ENHANCEMENT, BUG FIX

Superseded patches:
 PE70-0602282: ENHANCEMENT, BUG FIX
 PE70-0408312: BUG FIX
 PE70-0401162: BUG FIX
 PE70-0307162: CRITICAL (panic during recovery)
 PE70-0305091: CRITICAL (panic during recovery)


Patch PE71-0607142
------------------

Platforms: All

* The dbrecover utility was modified support for the modified
  forward-log file format added with eloqdb6 patch PE70-0607140.


Notes / Related patches:

- The following related patches (or superseding) should be installed 
  with this patch:
  - PE70-0607140 - eloqdb6 server
  - PE70-0607141 - dblogreset utility


Patch PE71-0602282
------------------

Platforms: All

* A rare defect with forward-recovery was fixed that could result in 
  a corrupted volume set (#2999). This causes an internal consistency 
  check to fail and eloqdb6 to abort on startup with an error message
  like below:
  
    Assertion failed: page == new_vol->flist_tail
    server panic: Aborting on internal failure, file volume.c, line 3988

  This problem could happen if the data volume was extended and the
  volume list of available blocks had to be extended as well (this
  is required around every 500 MB). The recovery then missed to update
  the flist_tail field in the volume header, causing a panic the next 
  time the server was restarted.

  The dbrecover utility was fixed to correctly update the flist_tail
  field. In addition the eloqdb6 behavior was modified to detect 
  and correct this problem on startup. A notice is written to the 
  server event log file in this case.

* The dbrecover utility was modified to add support for the modified
  forward-log file format added with eloqdb6 patch PE70-0602280.
 
  The eloqdb6 server process was enhanced to use a more efficient 
  format to record index and meta data changes. 
  This enhancement results in a substantial reduction in disk space
  for the forward-log file when index entries are changed frequently.
 
  This change required a modification of the forward-log file format.
  While older forward-log files are still supported, related utility
  programs need to be updated to handle the new format.


Notes / Related patches:

- The following related patches (or superseding) should be installed 
  with this patch:
  - PE70-0602280 - eloqdb6 server
  - PE70-0602281 - dblogreset utility


Patch PE70-0408312
------------------

Platforms: All

* The commit operations performed by dbrecover have been aligned with
  the changes in eloqdb6 patch PE70-0408310.

* dbrecover now verifies that the data volume files have the expected 
  size (#2468).

This patch (or newer) should be installed when using the corresponding 
eloqdb6 patch PE70-0408310.


Patch PE70-0401162
------------------

Platforms: All

* The commit operations performed by dbrecover have been aligned with
  the changes in eloqdb6 patch PE70-0401160.

This patch (or newer) should be installed when using the corresponding 
eloqdb6 patch PE70-0401160.


Patch PE70-0307162
------------------

Platforms: All

* dbrecover was enhanced to improve recovery performance (#1988)
  dbrecover uses temporary files to collect all changes which belong
  to a single transaction. This handling was optimized, resulting in
  a dramatic performance increase on HP-UX (and to some lesser extent
  on other platforms).

* dbrecover was fixed to handle a situation where the database server
  crashed and wrote incomplete information to the forward log (#1966).
  While dbrecover makes sure only complete transactions are applied a
  rare corner case could lead to (unused) data blocks linked to a table
  but not marked in use. This could lead to subsequent data corruption.

* dbrecover could abort with an internal error when schema is executed
  immediately after a dbpurge (#2053)

  panic: Fatal problem detected in bf_link_cluster
  Assertion failed: f_bhp->id.node_id == node_id
  Aborting on internal failure, file mpool.c, line 408


Patch PE70-0305091
------------------

Platforms: All

* dbrecover could abort with an internal error (#1948).

  panic: Fatal problem detected in FixRec_FinalCommitDelete
  Assertion failed: data_addr
  Aborting on internal failure, file volfrec.c, line 3126

  NOTE: In case dbrecover aborts the forward recovery needs to
  be restarted from the beginning by restoring the backup and
  running dbrecover again.


Installation:
-------------

UNIX:

In order to install this patch, you need to unpack it with gzip.
Gzip is included with HP-UX and Linux.
Installation requires root privileges.

cd /opt/eloquence6
gzip -dc /path/to/PE70-0607142-hpux.tar.gz | tar xf -

Files:

   bin/dbrecover
   share/doc/PE70-0607142-README


Windows XP/2000/NT:

This patch should *only* be installed if you previously installed
the Eloquence server components on your system.

Download the PE70-0607142-win32.zip file and unpack its contents
with WinZip or PKUNZIP.
Installation requires administrative capabilities.

Please copy the dbrecover.exe file into the bin subdirectory of your
Eloquence installation (for example C:\Programs\Eloquence\bin).

Please copy the PE70-0607142-README.txt file into the share\doc
subdirectory of your Eloquence installation (for example
C:\Programs\Eloquence\share\doc).

Files:

   dbrecover.exe
   PE70-0607142-README.txt