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

HP ELOQUENCE A.06.30 - patch 0010180

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

This patch fixes a defect of the eloqdb6 program as released
with A.06.30. This patch will be integrated in the A.06.30
release. A.06.30 must be installed before applying this patch.

This patch replaces patch PE63-0006020, PE63-0009080 and
PE63-0010160 (beta).

Severity:
 PE63-0010180: CRITICAL (incomplete results with SQL/R)
 PE63-0009080: CRITICAL (server panic, data corruption)
 PE63-0006020: CRITICAL (server panic)


Fixed problems:
---------------

Platforms: All

* A problem has been resolved which could cause SQL/R to return  
  incomplete results on a query on a busy database if the query was 
  optimized by an index.

  SQL/R uses an API to the data base server which allows it to optimize
  queries with indexes. A write access to the database could cause
  any index cursor to become invalid. In this case an EOF condition
  was wrongly assumed. The index cursor is now revalidated appropriately.


Patch PE63-0009080
------------------

Platforms: All

* A problem related to stopping online backup mode was solved.
  Depending on database usage during online backup this could result 
  in data corruption when stopping online backup mode.

  When the HP Eloquence database is in online backup mode committed 
  transactions are saved in the log volume not the data volume(s). 
  When the online backup mode is stopped (through dbctl backup stop) 
  committed transactions are transferred from the log volume to the 
  data volume(s). This could cause an extension of the data volume.
  
  A volume extension while transferring committed transactions from 
  the log volume to the data volume could cause corruption of 
  information in the log volume.

  Symptoms:
  - server panic after stopping online backup mode
  - dbfsck reports volume corruption

* Under rare circumstances a volume crash recovery could corrupt the
  data volumes. This can happen when the eloqdb6 server has crashed
  or was terminated with kill -9. In this case all committed 
  transactions since the last checkpoint operation are recovered 
  from the log volume during eloqdb6 startup.
  
  A problem was found if a data area affected by a transaction was
  deleted by a subsequent transaction and has been re-used since
  the last checkpoint operation. In some cases this could lead to 
  corruption of structural volume information. This has been fixed by 
  delaying page re-use until the next checkpoint operation.

  Symptoms:
  - server panic during volume crash recovery

* When an eloqdb6 server panic (internal error) is encountered the 
  eloqdb6 process restarts itself by default. This can be configured 
  in the eloqdb6.cfg configuration file with the panic= configuration 
  item.

  When eloqdb6 encounters a fatal problem during startup this will
  cause eloqdb6 to be started in an endless loop, possibly filling
  the log file and using system resources. Now eloqdb6 will not restart
  automatically if a problem during restart is encountered.


Patch PE63-0006020
------------------

Platforms: All

* A problem related to rollback of subtransactions was solved.
  Depending on database usage this could result in btree corruption
  or an eloqdb6 server panic.

  When a subtransaction was rolled back but the main transaction
  continued it could happen that invalidated btree information
  remained in memory and was used by subsequent btree operations.
  This problem could only happen when using transactions.

  Symptoms:
  - Assertion failed: f_bhp->id.node_id == node_id
    server panic: Aborting on internal failure, file mpool.c, line 392
  - DBPUT failed due to duplicate secondary index
  - dbfsck reports corrupted btree pages

  Impact:
  A database which shows the symptoms above must be reloaded (dbexport,
  dberase and dbimport).  Information besides internal btree is not
  affected.

* The eloqdb6 server could panic during processing volume recovery
  complaining about a buffer leak. This was caused by a bug
  processing defective recovery information from the log volume.

* Cache buffer management has been tuned to provide better performance
  for delete and update operations in a transaction. This should also
  improve the impact of transactions on concurrent read operations.


Installation
------------

UNIX:

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

cd /opt/eloquence6
gzip -dc /path/to/PE63-0010180-hpux.tar.gz | tar xf -

Files:

   bin/eloqdb6
   bin/dblogreset
   share/doc/PE63-0010180-README

Windows NT:

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

Download the PE63-0010180-win32.zip file and unpack with WINZIP or PKZIP.
Installation requires administrative capabilities.

PLEASE MAKE SURE THE EloqDB6 SERVICE has been STOPPED previously
(in the Service Control Manager). Please copy the eloqdb6.exe file
into the WINDOWS SYSTEM DIRECTORY (for example C:/WINNT/SYSTEM32)
and the dbvolcreate.exe and dblogreset.exe files to the bin subdirectory
of your HP Eloquence installation directory (for example
C:/Programs/Hewlett-Packard/HP Eloquence/bin).

Files:

   eloqdb6.exe
   dblogreset.exe
   PE63-0010180-README.txt