---------------------------------------------------------------------- ELOQUENCE B.08.20 - patch PE82-2206091 ---------------------------------------------------------------------- This patch adds enhancements or fixes defects of the dblogreset utility as released with Eloquence B.08.20. This patch will be integrated in the Eloquence B.08.20 release. Eloquence B.08.20 must be installed before applying this patch. Severity: PE82-2206091: BUG FIX Superseded patches: PE82-2204051: BUG FIX PE82-1808230: BUG FIX PE82-1501301: BUG FIX Patch PE82-2206091 ------------------ Platforms: All * Fixed a problem which in rare cases could cause a recovery or replication to fail after database restructuring (#4345). When a data set has been restructured, its meta data was not updated immediately. Under certain conditions this could cause a subsequent panic during recovery or on a slave server: D0: server panic: Fatal problem detected in FixRec_FinalCommitUpdateRange D0: Assertion failed: range_offset + range_size < (int)meta->rec_size Notes / Related patches: * Patches PE82-2206090 or superseding (eloqdb database server) and PE82-2206092 or superseding (dbrecover utility) fix a related problem and should be installed with this patch. Patch PE82-2204051 ------------------ Platforms: All * Fixed two potential problems related to creating or resuming on the forward-log "bridge" segment during startup recovery or using the dblogreset utility (#4341). After an abnormal termination, the database server (or the dblogreset utility) performs a startup recovery. During this process, a special forward-log "bridge" segment is created that allows a dbrecover, dbrepl or fwutil process to continue across the previous abnormal termination. If more than one forward-log segment is created during a checkpoint interval, and if the eloqdb then terminates abnormally, a following startup recovery (or the dblogreset utility) could choose a wrong forward-log segment number for the "bridge" segment. As a consequence, the recovery could fail with a log message like: failed to restart forward-log file '...': Fwr_SERIAL record expected If multiple forward-log "bridge" segment files are created during the startup recovery (or by the dblogreset utility) and the recovery is interrupted and then repeated it would be unable to handle already existing "bridge" segment files. In this case, forward-logging could be disabled unexpectedly with a log message like: unable to create forward-log '...': File exists (errno 17) Note: forward-logging has been disabled due to failure Notes / Related patches: * Patch PE82-2204050 or superseding (eloqdb database server) fixes a related problem and should be installed with this patch. Patch PE82-1808230 ------------------ Platforms: All * This patch updates the dblogreset utility to incorporate the changes as of eloqdb database server patch PE82-1710200. Fixed a problem where repeating an interrupted startup recovery could result in an empty forward-log "bridge" segment (#4255). After an abnormal termination, the database server (or the dblogreset utility) perform a startup recovery. During this process, a special forward-log "bridge" segment is created that allows a dbrecover, dbrepl or fwutil process to continue across the previous abnormal termination. Interrupting and then repeating the startup recovery should resume on an existing "bridge" segment. However, because an internal state was not correctly initialized, the resulting "bridge" segment could be empty. Patch PE82-1501301 ------------------ Platforms: All * This patch updates the dblogreset utility to incorporate the changes as of eloqdb database server patch PE82-1501300. Fixed potentially wrong volume generation count after a recovery from on-line backup mode was interrupted and then repeated (#4186). Improved the interoperability of the dbrecover utility with database replication (#4201). This patch ensures identical behavior of the dblogreset utility and the PE82-1501300 eloqdb after dbrecover was used. Installation: ------------- Please download the patch archive that corresponds with the installed release. The patch files follow the conventions below: PE82-2206091-hpux-ia64.tar.gz ^ ^ ^ | | Architecture / OS specific build | Operating system Patch ID HP-UX: In order to install this patch, you need to unpack it with gzip and tar. Gzip is included with HP-UX. Installation requires root privileges. cd /opt/eloquence/8.2 gzip -dc /path/to/PE82-2206091-hpux.tar.gz | tar xf - Files: bin/dblogreset share/doc/PE82-2206091-README Linux: In order to install this patch, you need to unpack it with tar. Installation requires root privileges. cd /opt/eloquence/8.2 tar xzf /path/to/PE82-2206091-linux.tar.gz Files: bin/dblogreset share/doc/PE82-2206091-README Windows: Two options are available for patch installation. The patch is available as self extracting archive for automatic installation and as a zip archive for manual installation. Both patches are equivalent. Installation requires administrative capabilities. For automatic installation of this patch, please download the patch file PE82-2206091-win32.exe. Before installation, please consider closing all applications, then execute the patch installation program. Installation does not require a reboot unless the patched files were active. For a manual installation of the patch, please download the patch file PE82-2206091-win32.zip and unpack its contents. Then perform the following steps: * Please copy the dblogreset.exe file into the Eloquence bin directory. (Default location: C:\Program Files\Eloquence\8.2\bin) * Please copy the PE82-2206091-README.txt file into the Eloquence share\doc directory. (Default location: C:\Program Files\Eloquence\8.2\share\doc) Files: dblogreset.exe PE82-2206091-README.txt