| |
Eloquence A.06.20 has been released in Febrary 1999.
Please refer to the release notes
for more information.
Changes
- 2001-04-02 - Patch PE62-0009080 has been replaced with
PE62-0101240 (eloqdb6 for all platforms)
- 2001-01-02 - Patch PE62-9909230 has been replaced with
PE62-0101020 (eloqsd server for Windows NT)
- 2000-10-26 - Patch PE62-9912210 has been replaced with
PE62-0010250 (new dlgsrv GUI drivers for the
Windows platform)
- 2000-07-28 - New eloqcore patch PE62-0007280
has been added for all platforms
The following patches against A.06.20 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 PE62-0101240
- This patch fixes defects of the eloqdb6, dbvolcreate and dblogreset
programs as released with A.06.20.
Replaces patches PE62-9902110, PE62-9902170, PE62-9902221,
PE62-9902222, PE62-9903080, PE62-9903290, PE62-9903311, PE62-9904060,
PE62-9904120, PE62-9905250, PE62-0006020 and PE62-0009080.
Summary of fixed problems:
-
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.
-
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.
-
eloqdb6 could panic during volume recovery if transaction log meta
information is damaged.
-
Under rare conditions 16 bit integer key values were incorrectly
inserted into an index. This could result in a subsequent database
status -96 (bad link to master set).
-
The HTTP status display could show garbaged server configuration.
-
A deadlock condition could occur during DBPUT and DBUPDATE in rare
cases causing the affected tasks to hang infinitely.
-
A zero record number in the free record list causes a panic in
Node_RemoveFirstItem() during DBPUT. This patch takes care of
a possible side effect when encountering the zero record
number.
-
The buffer allocation strategy in the buffer cache has been slightly
modified to handle cases of committing large transactions with
a small buffer cache configurtion more gracefully.
-
Due to a race condition, simultaneous DBOPEN and DBCLOSE operations
could cause a server panic in rare situations.
-
A zero record number in the free record list causes a panic in
Node_RemoveFirstItem() during DBPUT. This patch adds a workaround
to handle this particular case more gracefully and ignore the
offending list entry. The cause why the record number 0 was present
in the record free list in the fist place is still investigated.
-
Transaction isolation in the fixrec subsystem did not work correctly.
This could cause a server panic if a commit operation was executed
concurrently to a read operation.
-
dbctl dbstore could cause a buffer leak when running out of disk space.
This caused a subsequent server panic.
-
dbctl dbrestore may cause a server panic when using dbutil
subsequently to modify the database catalog.
-
dbctl backup stop could cause a eloqdb6 panic.
-
A eloqdb6 crash during on-line backup could cause a subsequent
failure to open the volume files: "Vol_Open() failed with VOLE018"
-
Crash recovery could fail with an internal error.
-
A corner case with disabling on-line backup mode could cause
data corruption if a checkpoint operation was executed concurrently.
-
Disabling on-line backup mode could cause a server hang.
-
A server crash while in backup on-line mode could cause an internal
failure the next time on-line backup mode was enabled.
Due to a related reason, dbfsck or dbvolextend could refuse to
modify a volume, complaining that the volume is still in on-line
backup mode.
-
dblogreset shares the same recovery routines as the eloqdb6 server.
So a new version is included in this patch.
-
eloqdb6 could abort with an internal failure.
-
When a client was disconnected (killed) eloqdb6 could cause a high
load when the associated internal thread was blocked internally.
For example, when eloqcore is blocking on a DBLOCK and is killed
the eloqdb6 process could busy waiting until the lock becomes
available, consuming almost all CPU resources.
-
Crash recovery could leave unassigned index and system catalog data
pages. In rare situations, this could lead to data corruption.
-
Crash recovery could cause fixrec meta data corruption.
-
dbctl dbrestore could cause a deadlock.
-
DBUPDATE mode 1 on a standalone detail set returned status 41.
-
DBFIND/DBGET on index item or QFIND on index item could fail.
-
A race condition in cache management could cause a eloqdb6 panic.
-
A race condition in Node_Open() could cause a eloqdb6 panic.
-
On the HP-UX and Linux platform a server shutdown could cause
errorneous messages.
-
dbvolcreate utility could output errorneous warnings about
a possible PIN LEAK.
-
The eloqdb6 server process could output errorneous warnings about
a possible PIN LEAK.
-
The dbstore operation failed to release a node lock which could cause
a subsequent eloqdb6 server panic.
-
After opening more than 32767 databases in succession in a single
session eloqdb6 could provide a possibly wrong or duplicate dbid.
Please refer to the PE62-0101240
patch description for more information.
- Patch PE62-0101020 (Windows)
- This patch fixes a defect of the eloqsd server for Windows NT
as released with A.06.20.
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.
-
The eloqsd server did not correctly setup all permissions for the
user who had logged-on. This could cause subsequent failures e.g.
when accessing a network resource from an Eloquence program.
-
The eloqsd server sometimes failed to read its configuration files
eloqsd.share and eloqsd.user correctly. This could cause the eloqsd
server to hang when reading its share or user configuration.
The problem was related to a bug in the Microsoft runtime library.
Please refer to the PE62-0101020
patch description for more information.
- Patch PE62-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.20.
Additionally, this patch provides preliminary support for Eastern
Europe Windows for the dlgsrv GUI driver and eloqcore.
Replaces patches PE62-9909240 and PE62-9912210.
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.
-
The EDITTEXT.ins and EDITTEXT.delln attributes caused the 16bit and
32bit dlgsrv(32) driver to crash if the cursor was positioned at the
end of the current content.
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.
-
The dlgsrv now supports the iso 8859/2 character encoding which is
used in Eastern European Windows versions.
Please refer to the PE62-0010250
patch description for more information.
- Patch PE62-0007280
- This patch fixes defects of the eloqcore program as released
with A.06.20.
Replaces patches PE62-9902190 (linux, libc6) and PE62-9902171 (win32),
PE62-9903081, PE62-9906290, PE62-9908311 and PE62-9911290.
Summary of fixed problems:
-
Matrix operations could fail with an internal error if the
destination matrix had more elements than the source matrix.
-
HP-UX:
A bug with the HP-UX C-Compiler could cause an error 1000 when
calling a subroutine and passing a file.
-
HP-UX:
A problem with the build procedure caused a abort by dld.sl (SIGABRT)
due to missing symbols during a SORT BY statement on HP-UX.
-
The -quiet or -nb arguments to eloqcore suppress the copyright
banner message.
-
Windows:
DLG SET ".driver" will use localhost as requester instead of
the hostname. This will fix a failure to startup DLGSRV in a
un-docked laptop.
-
Windows:
Code page cp852 map file is included. This is required to use
Eloquence on Eastern European Windows because the code page
850 used normally is not available.
-
Windows:
If the PC-850 Multilingual code page on Windows NT is not available
eloqcore refused to start.
-
A beep could either be not output instantly or cause abort of
eloqcore if curses was not active (eg. cron job or output redicrected).
-
Windows:
DLG SET failed with error 654 on string values with zero length.
This affected DLG LOAD, too.
-
Fixed possible ERROR 133/143 on printer close. When printer was closed
without having printed anything an internal variable referred to the
previous used printer (which could have been closed already) and the
close operation could fail with status 133 or 143.
-
MAT A=B could copy excessive elements if the target array had
more elements than source array. This could lead to subsequent
failure due to garbaged contents if the target array was
REDIMmed afterwards.
-
Linux and Windows:
DUMP SEGMENTS statement causes a segment violation or GPF if
the main segment is empty.
-
Linux (libc6):
ERRMSG$(n) causes a segmentation violation.
-
Windows:
When used with the Eloquence IDE or eqstart utility, eloqcore was
unable to redirect its error output into the IDE's output window if
a character mode program was executed.
Please refer to the PE62-0007280
patch description for more information.
- New setup.exe (Windows NT)
- This fixes a defect with the generation of temporary license
keys during installation on the Windows NT server.
Temporary license keys generated during installation after
Dec 1, 1999 will not work correctly.
The new setup.exe should be used as a replacement for the setup.exe
delivered with Eloquence. Please note, that the setup.exe and the *.z
package files need to be present in the same directory.
- Patch PE62-9905190 (Windows)
- This patch fixes defects of the Eloquence IDE and eloqstart
utility as released with A.06.20.
Replaces patch PE62-9902172.
Note: This patch requires installation of patch PE62-9908311
or a more recent eloqcore patch. Eloqcore as released with A.06.20
may crash (GPF) when used with this version of the Eloquence IDE
or eqstart.
Summary of fixed problems:
-
An internal overflow condition caused a GPF in the Eloquence IDE
when a directory was displayed in the Explore window which
contained a file with an invalid modification date.
-
In rare situations, a GPF was caused when the Explore window was
opened. An assumption was made concerning the network hierarchy
which was not always true. This has been fixed by re-implementing
the enumeration algorithm more defensively.
-
Although eloqcore supports character mode programs with A.06.20,
the Eloquence IDE and the eqstart utility did not support this
mode (the eloqcore window was always hidden).
Please refer to the PE62-9905190
patch description for more information.
- Patch PE62-9904092
- This patch fixes a defect of the dbfsck program as released
with A.06.20.
Summary of fixed problems:
-
dbfsck could report a errorneous fixrec meta data inconsistency.
When using in write mode (-w commandline argument) this could
cause bad fixrec meta information written back to the data
volume which could cause a subsequent eloqdb6 panic due to
inconsistent fixrec meta information.
Please refer to the PE62-9904092
patch description for more information.
- Patch PE62-9904010 (Windows)
- This patch delivers the dbctl utility for Windows which is missing
in the A.06.20 release.
Summary of fixed problems:
-
The dbctl utility is missing in the A.06.20 release for Windows.
Please refer to the PE62-9904010
patch description for more information.
- Patch PE62-9903230 (Windows)
- This patch fixes a defect of the Run Server GUI drivers for Windows
as released with A.06.20.
Summary of fixed problems:
-
The Run Server could hang after accepting a network connection
Please refer to the PE62-9903230
patch description for more information.
- Patch PE62-9902230 (linux, libc6)
- This patch fixes a defect of the Eloquence distribution
for the Linux libc6 platform.
This patch is required in order to use Eloquence A.06.20
on Linux libc6 based systems besides SuSE 6.0.
In addition patch PE62-9908311 or a later eloqcore patch must
be installed.
Summary of fixed problems:
-
Executables fail with __register_frame_info undefined.
Please refer to the PE62-9902230
patch description for more information.
- Patch PE62-9902220 (HP-UX)
- This patch fixes a defect of the Eloquence schema processor
utility as released with A.06.20.
Summary of fixed problems:
-
The schema procesor did not handle 8 bit characters ("Umlaute")
correctly on the HP-UX platform. This could result to syntax error
messages in schema definitions when 8 bit characters are used in
comments.
Please refer to the PE62-9902220
patch description for more information.
- Patch PE62-9902173
- This patch fixes a defects of the dbimport program as released
with A.06.20.
Summary of fixed problems:
-
dbimport failed to recognize import files which include structural
information (created by dbexport -r).
Please refer to the PE62-9902173
patch description for more information.
The Patches are available for download by ftp from the
/eloq/A0620/patch/
directory.
Patches currently in beta test are available for download by ftp
at /eloq/A0620/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).
|
|
