|
|
|
Verastream Integration Broker 9.9 Patch 1: Fixes and Features
Technical Note 40036
Last Reviewed 14-Nov-2007
Applies To
Verastream Integration Broker version 9.9
Summary
Technical Note 40036
Last Reviewed 14-Nov-2007
Applies To
Verastream Integration Broker version 9.9
Summary
Verastream Integration Broker 9.9 Patch 1 contains product updates. This technical note lists the changes made to the product.
This document is organized into the following sections:
For more information about features introduced in the original VIB 9.9 release, see Technical Note 10071.
Fixes and Features in This Update
Issue No. 287060 -- Problem loading character-based objects in shared memory
The shared memory utility (introduced in version 9.8) did not correctly load the definition of character-based objects. This would lead to "cannot find text" errors.
Issue No. 287484 -- PostgreSQL: with LIMIT, be able to use a WHERE clause instead of OFFSET
With PostgreSQL, the use of OFFSET has some disadvantages:
- When it is used in a multi-user environment it is possible that one process ADD's or DEL's a record in a table the other process is traversing. With an OFFSET it is possible records are read again or skipped.
- Performance of OFFSET is quite slow. Each time the server needs to skip OFFSET records.
With this update, it is possible to use a WHERE clause for repositioning instead of OFFSET. The current record is taken to create a WHERE clause that selects the next LIMIT set of records. When a LIMIT is specified, not equal to 0, this is the default.
Added a new table option and database object option USE_OFFSET=[yes|no], default no. When set to yes, the original version 9.9 OFFSET behavior is used.
Refer to the documentation for details about using this option.
Issue No. 287521 -- A backslash at the end of a PostgreSQL string is not handled correctly
In the original version 9.9, errors could occur when writing backslash characters to a PostgreSQL database. This is due to the current PostgreSQL treatment of backslash characters as literal escape characters instead of ordinary string literals.
With this update, the backend detects whether to use a double backslash \\ to insert a backslash character.
Detection uses a PostgreSQL parameter standard_conforming_strings. It reports whether ordinary string literals treat backslashes literally, as specified in the SQL standard. The value is currently always off, indicating that backslashes are treated as escapes. It is planned that this will change to on in a future PostgreSQL release when string literal syntax changes to meet the standard. When this parameter value is on, backslashes will not be escaped anymore.
Issue No. 287843 -- The function DEL on VIEWBOX objects does not work correctly
The function DEL on VIEWBOX objects fails under certain conditions. In addition to causing failure, a subsequent NEXT will not find the real next record.
Issue No. 299079 -- All database backends needed to be updated
Because of the addition of a new database backend the internal code had to be changed. All existing database backends therefore needed to be changed.
Issue No. 300313 -- Error message EMFAILED when accessing a C-ISAM table.
When looping through a table and updating records, an ism.EMINTR error, which translated into EMFAILED, or EMRDONLY error could occur.
Added support for HP-UX 11i on HP Integrity Server (a.k.a. 'Itanium')
HP-UX 11i (V 11.23) support on HP Integrity Server added. (This system is also known as Itanium.)
- 32 bits support: C-Isam (V7.26.UC2), C-tree (6.7A), DB2 V9.1, Oracle 10g (10.2.0.1.0), Informix SQL/C (V2.81 and V2.90), PostgreSQL
- 64 bits support: C-Isam (V7.26.FC2), DB2 V9.1, Oracle 9i (9.2.0.2) and 10g (10.2.0.1.0), Informix SQL/C (V2.81 and V2.90), PostgreSQL
Note: This new platform support is available on the download site as new product release files (not patch files).
Issue No. 301752 -- Fixed missing support Informix 9.5 on Linux (Kernel 2.4.18 - Redhat 7.3)
In the original 9.9 release, the adapter for Informix version 9.5 (using ESQL/C 2.70) was incorrect (a copy of the adapter for Informix version 7.2). The correct adapter is provided in this update.
Issue No. 301578 -- Firebird ODBC: DEL and UPD sometimes fail
The Firebird ODBC Driver does not return an empty string correctly (terminated with null byte). As a result, a DEL or UPD could fail, because the current and previously fetched values differed.
In this update, a receive buffer is initialized with a null byte in case an empty string is received.
Obtaining This Update
This update is available in the Attachmate Download Library (https://download.attachmate.com/Upgrades/) to customers with current maintenance for Verastream Integration Broker. After logging in, click File Download under Verastream Integration Broker, and then scroll down to locate the appropriate new release (for HP Itanium) or patch file (for all other platforms).
For more information on using the Download Library, see Technical Note 0200.
Installation Instructions
After downloading the patch file, use the appropriate utility to unpack the contained files (such as uncompress, tar, and/or unzip). Refer to the unpacked .html file for a listing of files and installation instructions for the target platform.
Note: File names ending with uppercase .Z extension may change to lowercase .z in the downloading process. After downloading, you must rename the file to the original uppercase .Z extension before using the UNIX uncompress command.
