| |
Eloquence A.06.30 has been released in March 2000.
Please refer to the release notes
for more information.
Changes
- 2001-07-26 - Patch PE63-0101240 has been replaced with
PE63-0104230 (eloqdb6 for all platforms)
- 2001-04-18 - New patch
PE63-0104180 (SuSE Linux 7.1 support)
- 2001-04-18 - New patch
PE63-0012220 (RedHat 6.2 and 7.x support)
- 2001-04-02 - Patch PE63-0010300 has been replaced with
PE63-0103300 (eloqcore for all platforms)
- 2001-01-02 - Patch PE63-0101020 has been
added (new eloqsd server for Windows NT)
- 2000-10-26 - Patch PE63-0010250 has been
added (new dlgsrv GUI drivers for the Windows platform)
The following patches against A.06.30 are available:
- Patch PHCO_10947
- If you are on HP-UX 10.20 we recommend to install
the HP-UX patch PHCO_10947 (curses patch).
Please refer to the patch documentation
PHCO_10947.text
for more information.
The patch is available for download at
ftp://ftp.marxmeier.com/eloq/A0610/hpux/PHCO_10947
or
ftp://ffs-geneva.external.hp.com/hp-ux_patches/s700_800/10.X/PHCO_10947
- Patch PHCO_10950
- If you are on HP-UX 10.10 we recommend to install
the HP-UX patch PHCO_10950 (curses patch).
Please refer to the patch documentation
PHCO_10950.text
for more information.
The patch is available for download at
ftp://ftp.marxmeier.com/eloq/A0610/hpux/PHCO_10950
or
ftp://ffs-geneva.external.hp.com/hp-ux_patches/s700_800/10.X/PHCO_10950
- Patch PE63-0104230
- This patch fixes a defect of the eloqdb6 program as released
with A.06.30.
Replaces patches PE63-0006020, PE63-009080, PE63-0010180 and PE63-0101240.
Severity: CRITICAL (panic, data corruption)
New functionality:
-
Eloqdb6 includes improved support for deadlock detection and
recovery.
-
The new data base status -35 can be returned on a DBLOCK,
DBPUT, DBUPDATE or DBDELETE statement if the eloqdb6 server
has detected a deadlock condition.
-
A database session which blocks on a resource can now be signaled
or even killed.
-
The dbctl command line interface has been enhanced to support
restoring a database archive with a different database name.
Summary of fixed problems:
-
A dbrestore operation could corrupt the database volume.
-
A released lock could fail to update lock dependencies. In rare situations
this could result in a wrong -35 status.
-
A duplicate DBLOCK could cause a deadlock.
-
Database volume file could grow to 2GB during online backup.
-
Eloqdb6 could fail to recover from an unclean shutdown due to
inconsistencies in the log volume.
-
Due to a race condition eloqdb6 could fail on a Linux 2.4 kernel
during start with an internal error.
-
Decoding of DBLOCK status could be incomplete in the HTTP status
display and dbctl list lock output.
-
The eloqdb6 title was not included in the HTTP status display.
-
The list of opened databases was not available in the HTTP status
display.
-
Using transactions could result in a server deadlock.
-
A server crash during schema, dbcreate, dberase or dbpurge could
result in data corruption under rare circumstances.
-
Due to problems encountered on some HP-UX systems which could result
in an eloqdb6 panic due to a failed writev() system call, the IPC
communication method is now disabled by default.
-
On Linux SMP systems shutting down the eloqdb6 server could
sometimes cause a segment violation (SIGSEGV).
-
Using regular expressions with DBFIND could cause the server to
hang infinitely under rare circumstances.
-
A newline character was missing in the 'dbctl list lock' output.
-
On the HP-UX platform the file descriptor soft limit could cause
connection failures.
-
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.
-
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.
-
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.
-
Regardless of the panic= configuration, eloqdb6 will not restart
automatically anymore if a fatal problem during startup is encountered.
-
A problem related to rollback of subtransactions was solved.
Depending on database usage this could result in btree corruption
or an eloqdb6 server panic.
-
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.
Please refer to the PE63-0104230
patch description for more information.
- Patch PE63-0104180 (SuSE Linux 7.1)
- This patch fixes a compatibility problem with SuSE Linux 7.1.
this patch should be installed after installing Eloquence on
SuSE Linux 7.1 or upgrading to SuSE Linux 7.1.
Please review the README file for specific installation instructions.
Severity: NORMAL
Please refer to the PE63-0104180
patch description for more information.
- Patch PE63-0012220 (RedHat Linux 6.2 and 7.x)
- This patch solves a compatibility problem with RedHat Linux 6.2
and 7.0. RedHat Linux includes a binary incompatible ncurses
library that causes eloqcore to crash with a SIGSEGV on start.
This patch is compatible with the libc6 (glibc2.0.x) build of Eloquence.
Please review the README file for specific installation instructions.
Severity: NORMAL
Please refer to the PE63-0012220
patch description for more information.
- Patch PE63-0103300
- This patch fixes a defect of the eloqcore program as released
with A.06.30.
Replaces patch PE63-0010300.
Severity: BUG-FIX
Summary of fixed problems:
-
A rounding problem has been fixed which could affect string conversion.
For some values the result was truncated instead of rounded.
-
The number of databases which can be opened simultaneously from
Eloquence has been extended from 20 to 50.
-
Printing specific numeric values could cause a crash in eloqcore due
to a buffer overflow.
-
Pressing the HALT function key (system functions) did not trigger
ON HALT in a WAIT statement.
-
A failed DLG SET .driver could result in an unexpected termination
of Eloquence.
-
Matrix operations could fail with an internal error if the
destination matrix had more elements than the source matrix.
-
HP-UX 10.20 and 11.x:
-
An experimental version of this patch using the X/Open Curses library
has been released. Previous Eloquence versions used the old
HP Curses library.
-
Linux:
-
ON DELAY did not work correctly. Only the first timer interrupt was
processed. After that any ON DELAY timer interrupt would be ignored
and a timed WAIT would never expire.
-
HP-UX:
-
A DBLOCK on a remote database running on an x86 platform (Linux,
Windows) could crash eloqcore with a SIGBUS due to an alignment
violation.
-
Windows:
-
The PAUSE key can now be used as a HALT key.
-
ON DELAY did not interrupt an INPUT statement.
-
Under certain circumstances eloqcore did not start-up in background
mode.
-
Given an unknown hostname or IP address in DLG SET ".driver" could
cause eloqcore to hang infinitely.
Please refer to the PE63-0103300
patch description for more information.
- Patch PE63-0101020 (Windows)
- This patch fixes a defect of the eloqsd server for Windows NT
as released with A.06.30.
Severity: BUG-FIX
Summary of fixed problems:
-
The Windows NT error #1816 (ERROR_NOT_ENOUGH_QUOTA) occurred after
logging-on more than about 35 times. This was caused by global
access control entries which were not removed after a session was
terminated. A reboot was necessary to recover from this situation.
Please refer to the PE63-0101020
patch description for more information.
- Patch PE63-0010250 (Windows)
- This patch fixes a defect of the 16 and 32bit dlgsrv(32) GUI drivers for
the Windows platform as released with A.06.30.
Severity: NORMAL
Summary of fixed problems:
-
DLG SET ".focus" applied to a container object (dialog/window or
groupbox) now sets the focus to the first sensitive object inside the
container object.
-
If an object does not specify its own .help attribute the dlgsrv
did not always fallback to the parent object's one.
-
Several problems concerning on-line help DDE communications have been solved.
New Functionality:
-
The on-line help browser can now be configured. Therefore, it is now possible
to use the MS Internet Explorer instead of Netscape Navigator/Communicator.
Please refer to the PE63-0010250
patch description for more information.
- Patch PE63-0006021
- This patch fixes a defect of the QUERY program as released
with A.06.30.
Severity: BUG FIX
Summary of fixed problems:
-
The QUERY application fails with ERROR 18.
Please refer to the PE63-0006021
patch description for more information.
The Patches are available for download by ftp from the
/eloq/A0630/patch/
directory.
Patches currently in beta test are available for download by ftp
at /eloq/A0630/patch/beta/.
As the name suggests, these fixes are believed to be correct (and were
tested) but are currently not released. However it may just fix your problem.
Feedbacks are appreciated (feedback@marxmeier.com).
|
|
