| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 7.6.000.14 [09/02/09] – Hot Fix | X | X | X | X | ||
| 7.6.000.12 [05/22/09] – Hot Fix | X | |||||
| 7.6.000.11 [02/20/09] – Hot Fix | X | |||||
| 7.6.000.10 [01/16/09] – Hot Fix | X | |||||
| 7.6.000.09 [12/18/08] – General | X | X | X | X | X | X |
| 7.6.000.08 [02/14/08] – General | X | X | X | X | X | X |
| 7.6.000.07 [12/20/07] – Hot Fix | X | X | X | X | ||
| 7.6.000.06 [10/10/07] – General | X | X | X | X | X | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.
This release note applies to all 7.6 releases of DB Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
On an Oracle DBMS, the rate at which DB Server processes update requests for binary large object (BLOB) data has been improved. (ER# 232114857)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
When working with Oracle database clients, DB Server no longer returns the
error ORA‑01013 in response to client requests that are
made after the following scenario occurs:
SELECT request to DB Server.
This request specifies that only a limited number of rows should be returned
to the client, regardless of how many rows are actually returned by the
SELECT operation.SELECT operation are returned
to the client by DB Server because the number of rows that are selected
is more than the specified limit.Previously, DB Server occasionally did not execute subsequent client requests,
and returned the error ORA‑01013 instead.
(ER# 227171987)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
DB Server no longer truncates non-character type data if the size of that data type (in bytes) is less than the size of the string that represents a value of this type. Previously, the output data was sometimes truncated to fit the size of the type.
Example: Data of type DATE is 7 bytes. But 9 bytes is
required to represent a date in the format "dd-mmm-yy", a total of 9
characters. Before this release, the date was truncated to 7 characters, or
"dd-mmm-". Now, all 9 characters of the date is output, as "dd-mmm-yy".
(ER# 217736781)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
DB Server for Oracle no longer automatically commits all changes to the database when the connection between the client and DB Server is lost (because of a DB Server switchover or a client disconnection) before the transaction is completed. Previously in this scenario, the client did not explicitly commit the transaction, but DB Server did commit changes made up to the time that the connection was lost. (ER# 201161791)
An Oracle DB client now correctly proceeds to execute a stored procedure
that has input parameters of type NUMBER or FLOAT,
or output parameters of any type. Previously, the usage of such parameters
sometimes caused the DB client to terminate. (ER# 214841951)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications:
A 32-bit Oracle DB client now starts correctly with DB Server on the HP-UX
platform. Previously, the client did not consider the value of the environment
variable SHLIB_PATH, and was unable to load the shared library.
As a result, the client did not start. (ER# 200092607)
For MS SQL Server database engines, DB Server now correctly handles the
scenario where a stored procedure returns a NULL value through
the stored procedure's output parameter. Now, DB Server returns a
NULL value to the application, as required. Previously, DB
Server returned a meaningless value. (ER# 216102586)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications:
For MS SQL Server database engines, DB Server now correctly handles named parameters when calling stored procedures. Therefore, a procedure can be called with its parameters in any order, and parameters using default values can be omitted.
Previously, when a stored procedure was called with the order of the parameters different from the order specified during stored procedure creation, or with some parameters using default values omitted, the execution of the procedure would produce either an incorrect result or fail completely.
(ER# 173530495)
For MS SQL Server database engines, DB Server now correctly handles
values of float type parameters when calling stored procedures.
Previously, these values were not interpreted correctly, causing incorrect
data to be stored in the database. (ER# 165236888)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
DB Server now properly closes all dbclient processes after the
application disconnects from the database. Previously, the dbclient
processes were not closed properly and the number of running dbclient
processes accumulated until no further requests to open a connection to the
database could be accepted. This problem also caused CPU utilization to increase.
(ER# 164501770)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications that were made between release 7.5 or earlier releases and the initial 7.6 release:
DB Server MSQL client dbclient_msql.exe no longer causes a memory leak in
Datasourcer or Interaction Router scenarios. (ER# 146826041)
If you are using IMAGE data on Sybase for reading or writing, you can optimize the performance of DB Server if you limit the size of the IMAGE to 1 MB. Genesys also recommends that you set the following configuration options on your Sybase server:
abort tran on log full = true
trunc log on chkpt = true
(ER# 135505994)
DB Server now restores auto commit mode when a request to execute a binding command fails. Previously, DB Server did not restore auto commit mode thus leaving the connection in a manual commit state, which in some circumstances resulted in objects being locked in the database. (ER# 130324801)
DB Server no longer generates the BLOB data truncated error message when
the Universal Router Server retrieves routing strategies from the database.
DB Server truncates any BLOB data greater than 10 MB, as documented in the Framework
7.6 DB Server User's Guide. Therefore, when a SELECT describe operation
is applied to BLOB data that exceeds the maximum, DB Server generates the BLOB
data truncated warning message. This is often a wrong diagnosis, because the
length information returned by the SELECT describe operation is the value
used in the column length specification in the CREATE TABLE statement; no
data is actually truncated.
Note: It is the application's responsibility to ensure that the size of any BLOB data does not exceed the maximum limit of 10 MB.
(ER#s 107150387, 71733901)
This section provides the latest information on known issues and recommendations associated with this product.
For MS SQL databases, DB Server requires Microsoft Data Access Components (MDAC) version 2.8. (ER# 177187009)
For MS SQL users only. The execution of the stored procedure can fail when a stored procedure is called with the order of the arguments different from the order specified in the stored procedure during its creation. (ER# 173530495)
| Found In: 7.6.000.06 | Fixed In: 7.6.000.08 |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.
There are no discontinued features or functions in this release of DB Server 7.6.
Information in this section is included for international customers.
There are no limitations or restrictions associated with internationalization.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Framework Deployment Guide first.
Framework 7.6 Deployment Guide provides instructions for installing and configuring Framework 7.6 components, and for starting and stopping the Framework 7.6 components either using the Management Layer or manually.
Framework 7.6 Configuration Manager Help describes how to use Configuration Manager in either an enterprise or multi-tenant environment.
Framework 7.6 Configuration Layer Error Messages Help describes error messages that the Configuration Layer generates in either an enterprise or multi-tenant environment.
Framework 7.6 Configuration Options Reference Manual describes configuration options for Framework 7.6 components.
Framework 7.6 Combined Log Events Help describes log events that Genesys server applications generate and that Solution Control Interface displays.
Framework 7.6 DB Server User's Guide provides a high level overview of DB Server features and functions, together with architecture and configuration information.
Genesys 7.6 Security Deployment Guide describes Genesys security features and detailed instructions for deploying them. These features provide secure data transfer between Genesys components, protection against unauthorized access, and protection against data loss in case of component failure.