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

HP ELOQUENCE A.06.01 - patch 980326

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

This patch fixes an issues with the A.06.01 database server.
It will be integrated in a subsequent HP Eloquence release.
You should have installed A.06.01 or A.06.00 and fixpack3 before
applying this patch.
This patch is a replacement for patch 971218,971211,980204,
980216,980305,980306


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

Platforms: HP-UX, Linux, Windows

* A non-fatal inconsistency check caused a server panic which also 
  prevented a server restart (Assertion failed: meta->first_recno == 0).
  This message incidates inconsistent meta information and should never
  happen. However the server should be able to recover from this situation.
  This condition still causes a server panic, however it the server will 
  be able to recover from this situation and fix the meta information 
  during crash recovery.

* A server crash might damage an index. When a new index page was
  allocated and the server crashed before the checkpoint operation, 
  the index page could be overwritten subsequently.


Included from previous patches
------------------------------

* Problem during index key comparison which caused a server panic.
  Assertion failed: size_a >= len && size_b >= len

* Possible data corruption. This could happen in a rare case
  when deleting the last record from a data set unless the
  data volume was set to sync mode.

  All access to the data base is performed through the internal
  cache system. When a cache page was marked ("pinned") as beeing
  used, the server did not write it back to the volume because it
  could contain inconsistent modifications. In this particular
  case it could happen that a cache page was not unmarked and thus
  modifications to this page were never written back to disk.
  As a result the database could become inconsistent when the
  server was shut down. This behaviour has been changed and a
  warning message is written to the log file in addition when a
  marked page is detected during a checkpoint operation.

* The Priority of the HTTP status thread has been increased.
  Previously the HTTP status thread had a priority which
  prevented it from becoming active on a busy server.

* DBERASE fixes. DBERASE could cause a data base server panic
  when erasing a single detail set. When the data base server
  erased path information from connected master sets it failed
  with "Assertion failed: lrec".

* DBCREATE/DBPURGE/DBERASE now check for a pending transaction.
  Data base utility statements can not be executed when a
  transaction is active. This will return a status 32 (transaction
  nesting exceeds maximum).

* HP-UX crash log. When detecting an internal problem, the HP-UX
  version omitted additional information about the location.

* The index order on little endian systems (Intel) was wrong for data
  types other then strings. This was caused by an issue in the index
  compare function which is not handling byte order properly. (#659)

  This affected DBGET mode 5/6/15/16 on index items which are not of
  type string on Intel based systems (Windows NT, Linux). Other than
  that the order seems to be random, the index worked correctly.

  Since installing a new index compare function establishes a
  different index order (which would break existing data bases), the
  new compare function is not active unless the index is rebuilt.
  The database should be exported, *purged* and imported again to
  activate this fix.
  Please note, that erasing the database is not sufficient, since
  only a dbcreate will create new BTREE metadata.

* On HP-UX and Linux, a new server configuration item is available.
  In the section [server], the configuration item "Title" provides
  a configurable title displayed by ps. This is helpful to identify
  a server instance if you run more than one on a machine. (#676)

  For example:  eloqdb6.cfg

   [Server]
   ...
   Title = test server

* DBFIND mode 3 / DBGET mode 16 sequence could cause eloqdb6
  server panic. DBGET mode 16 may return wrong record after
  DBFIND mode 3. (#605)

* Problem in eloqdb6 server can cause data corruption. (#620)

* A problem introduced as a side effect by patch 971211 is fixed.
  This could cause under some preconditions a cache page not to
  become unlocked. This will cause a eloqdb6 server panic when
  this page is modified subsequently. (#627)

  Assertion failed: bhp->refcount == 1
  server panic: Aborting on internal failure, file mpool.c, line 1059


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

UNIX:

In order to install the patch, you need to unpack it with gzip.
Gzip is included with Linux and HP-UX 10.x and can be obtained
for HP-UX 9.x from this ftp server in the /pub directory.
Installation requires root privileges.

cd /opt/eloquence6
gzip -dc hpux-980326.tar.gz | tar xf -

Files:

   bin/eloqdb6
   share/doc/README-980326

Windows:

The eloqdb6.exe file should *only* be installed, if you previously
installed the HP Eloquence server components on your system.

Download the win32-980326.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).

Files:

   eloqdb6.exe
   README-980326.txt