Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
7.6.100.08 [01/20/2012] – Hot Fix | X | X | X | X | ||
7.6.100.06 [01/09/2012] – General | X | X | X | X | X | X |
7.6.000.17 [11/30/2010] – General | X | X | X | X | X | X |
7.6.000.08 [06/30/2010] – General | X | X | X | X | X | X |
This release note applies to all 7.6 releases of Data Mart.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that were introduced in this release of Data Mart.
Support for Oracle Real Application Clusters (RAC) 11g Releases 1 and 2. For the recommended configuration, see ER# 314049494.
This release includes the following corrections and modifications:
ETL Runtime now correctly recognizes when a process is stopped. Previously, ETL Runtime might fail to schedule processes that stopped, mistakenly recognizing them as running. (ER# 289715347)
ETL Runtime is now able to process ODS objects with CONFSERVER_OBJ_ID
with a maximum value of 1099511627775
on Oracle. Previously, the maximum value was 2147483647
.
(ER# 286858262)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Data Mart.
This release includes the following corrections and modifications:
ETL now uses shorter patterns for naming constraints on DB2. Previously, exceptions were raised when the constraint naming pattern exceeded the maximum allowed 18 characters on the DB2 database. (ER# 277447031)
Previously, ETL Runtime might incorrectly schedule processes which have a daily start time to begin on an hourly basis. This has been corrected. (ER# 270275781)
Previously, if the [jdbc]
section was not defined in the options of the Database Access Point,
then the ETL Starter was unable to read the database connection information. This has been corrected.
(ER# 264801648)
ETL runtime now correctly removes the set of invalid views (SYNONYMS
) from the database.
Previously, when the last layout was deleted, this set of invalid views were left in the database.
(ER# 249832748)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release of Data Mart does not contain new features or functionality.
This release includes the following corrections and modifications:
ETL_Service
now properly closes its connection with Local Control Agent (LCA) that is running on
the same box when a request to stop is issued from Solution Control Interface (SCI) or Alarm Reaction script.
When ETL_Service
is stopped, it is correctly indicated as having the Stopped
status.
Previously, because ETL_Service
did not close its connection, it would get stuck in the Stop
Pending
state. (ER# 261852181)
ETL_Tracking
(or DataMart) no longer fails when processing Agents with the rank of type
Genesys Administrator
assigned in the configuration environment. (ER# 258886692)
With this release, ETL now starts properly on AIX 6.1. Previously, the 64-bit version of Data Mart could not be started on AIX 64-bit platforms. (ER# 253285151)
The Data Mart application status is now always displayed correctly in Solution Control Interface (SCI). Previously, in some rare cases, the Data Mart application might be displayed in SCI as not running when it actually was running. (ER# 219160380)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This initial 7.6 release of Data Mart does not contain new features or functionality.
This release includes the following corrections and modifications that were made between Release 7.2 or earlier releases and the initial 7.6 release:
This version fixes an issue where ETL may have overwritten the DELETE_TIME
of all records of the
Object (for example Agent) in an object to object relationship (like Groups and Group members) when an object
was deleted from Configuration Manager, which effectively overwrote the history of the object to object
relationship for this Object. (ER# 254358498)
ETL Runtime now partially relieves aggregated data limitations because deleted statistics are now excluded from aggregation. Previously, ETL Runtime was unable to aggregate data for layouts with a very large number of statistics (deleted or active) due to limitations of the underlying RDBMS engine that holds the Data Mart database. (ER# 230573271)
Tenants Alias Tracking module now explicitly grants CREATE VIEW
and CREATE SYNONYM
privileges, in addition to RESOURCE
and CONNECT
roles on an Oracle database for new
Tenant DB Accounts. Previously, the absence of these privileges may have caused errors while executing the
Tenants Alias Tracking module on Oracle 10G. Prior to version 10G, Oracle included these privileges in the
CONNECT
role. (ER# 228970604).
ETL Runtime now keeps the last two OL_DATA
tables from being purged in scenarios where chunks
are written to a table that is not the last one. Previously, only one table was kept. (ER# 224323036)
ETL Runtime, when run against Microsoft SQL Server with a jTDS driver, now uses escape sequences during table and view existence checks. Previously, ETL Runtime may have failed to create tables of views in this situation because of erroneous (false positives) existence checks. (ER# 212170056)
This section provides the latest information on known issues and recommendations associated with this product.
Recommended Configuration for Oracle RAC 11g Releases 1 and 2—In order to support Oracle RAC in ETL, you must configure jdbcurl
in etl.properties
and any other properties files you use (for example, purge
, createdb
, and tenants_alias_update
)
as shown in the following examples:
Oracle RAC 11g Release 2:
jdbc:oracle:thin:@<scan-name>:<port>/<SERVICE NAME defined for your ETL>
For example:
jdbc:oracle:thin:@ora-scan.mydomain.com:1521/ORA_ETL
See Oracle RAC documentation for details on how to configure SCAN and cluster services.
Oracle RAC 11g Release 1:
jdbc:oracle:thin:@<Oracle Net connection descriptor format appropriate for RAC>
For example:
jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = rac1.mydomain.com)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = rac2.mydomain.com)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME = RAC.mydomain.com) ) )
See Oracle RAC documentation for details on how to configure the net connection descriptor.
Found In: 7.6.100.08 | Fixed In: |
If using Oracle Thin driver with Oracle RAC, and configuring ETL by using ETL Assistant, there may be a problem connecting to a Data Mart database. ETL Assistant generates the following URL to connect to the Data Mart database, and to configure the ODS Data Source:
jdbc:oracle:thin:@<Oracle Cluster IP address or Cluster Hostname>:<Oracle Listener Port>:<SID>
In the above, <SID>
can only point to one particular instance of the cluster, and
<SID>
is populated from the SID Name in the ETL Assistant
field. This is the only format that is supported when ETL Assistant connects to the Data Mart database. This same format is used in ETL Assistant for the ODS Data Source configuration if the ODS database is located on Oracle RAC. However, if you have an Oracle RAC cluster database, and want ETL runtime to be able to connect to the running instance during an instance failure, the Service Name must be used instead of the SID.
ETL Assistant cannot construct the URL with a Service Name. If this is desired, you need to create a new ODS
Data Source in ETL Assistant, and then update its URL to the following format (note that you must use
"/
" instead of ":
"):
jdbc:oracle:thin:@<Oracle Cluster IP address or Cluster Hostname>:<Oracle Listener Port>/<Service Name>
This can be done by issuing the following SQL statement against the Data Mart database:
update SOURCE set DB_URL = <DB URL in the format above> where SOURCE_ID = <ID of the
ODS source>
(ER# 255574621)
Found In: 7.6.000.08 | Fixed In: |
ETL Runtime might not start normally on the AIX 5.x and AIX 6.x 64-bit platforms.
To run ETL Runtime on these platforms, use the following as a workaround:
run.sh
file.
starter
to starter_32
.
run.sh
file.
(ER# 253285151)
Found In: 7.6.000.08 | Fixed In: 7.6.000.17 |
ETL Runtime may incorrectly write the time dimensions for the START_TIME
and
END_TIME
columns in scenarios where a data chunk is not aligned to the minute boundary. In such
situations, the duration (END_TIME-START_TIME
) will be preserved, and the START_TIME
and END_TIME
columns will both be shifted, so that START_TIME
is aligned with the
minute's beginning. (ER# 215929509)
Found In: 7.6.000.08 | Fixed In: |
In certain Japanese locales (for example, ja_JP.eucJP
and ja_JP.PCK
), Data Mart's
Configuration Tracking module may fail to unpack a localized string and return
java.lang.NullPointerException
. To avoid this problem, add the following option to the startup
command of the Configuration Tracking module:
-Dfile.encoding=SJIS
The Configuration Tracking module's startup command is specified in the Command
configuration
option of the ETL_Tracking
section. (ER# 73476983, 73789489)
Found In: 7.2.002.08 | Fixed In: |
On Solaris platforms, Data Sourcer may experience a time synchronization problem for some U.S. time zones during Daylight Savings Time, causing duplicate values to be recorded. (ER# 118869764)
Found In: 7.2.002.02 | Fixed In: |
Under certain circumstances, ETL Assistant will display the actual Data Mart table name instead of its synonym. (ER# 79928601)
Found In: 7.2.001.06 | Fixed In: |
On the Windows 2003 Japanese platform using the Japanese character set, the Data Mart Wizard does not successfully connect to a Data Mart built with Microsoft SQL RDBMS. (ER# 71735571)
Found In: 7.2.001.06 | Fixed In: |
For the Windows 64-bit platform, the Data Mart Installation may fail to detect the 64-bit JRE. To solve this problem, install the 32-bit JRE, install Data Mart, and then start Data Mart using the 64-bit JRE. (ER# 32384033)
Found In: 7.2.000.04 | Fixed In: |
In some situations, the jTDS driver used by ETL Runtime may not connect to the database on Microsoft SQL. The driver contains an incomplete set of charset conversion rules. The jTDS driver can be updated with the correct set of charset conversion rules, but for the 7.2 release, the driver that is shipped has already been updated for all charsets for which the issue was reported, including the MS949 charset. (ER# 35457267)
Found In: 7.1.000.09 | Fixed In: |
If you are configuring Data Mart and you select a custom driver, the installation process does not copy the driver to the ETL Runtime home directory. You must copy the custom JDBC driver files to your target ETL Runtime home directory manually. (ER# 99384)
Found In: 7.0.200.10 | Fixed In: |
Due to a problem in Unix installations of ETL Runtime, a newly installed instance of ETL Runtime may fail to start. To resolve this issue, employ the following steps:
run.sh
from the main Data Mart installation
directory to the etl_runtime
subdirectory.
starter_32
file in the
etl_runtime
subdirectory to starter
.
(ER# 95445)
Found In: 7.0.200.02 | Fixed In: |
Warning: Before upgrading your Data Mart manually, ensure
that you save copies of your .properties
files,
including: createdb.properties
,
etl.properties
, and purging.properties
, as these files will
be overwritten by this process. (ER# 93751)
Found In: 7.0.200.02 | Fixed In: |
To update your current Data Mart version during the installation process, remove the existing application and then create a new one. The offer to update your current Data Mart should be ignored. (ER# 97445)
Found In: 7.0.100.07 | Fixed In: |
If you delete layouts before creating a purge schedule, the layouts cannot later be purged. (ER# 80628)
Found In: 7.0.100.09 | Fixed In: |
The Historical Wizard configures the setFirstDayOfWeek
runtime parameter for the Starter process but does not set its
value in all .properties
files. If you elect to manually run ETL
Runtime processes, remember to set the value of this parameter in
the .properties
file that you use. (ER# 75995)
Found In: 7.0.100.04 | Fixed In: |
Object duplication in Brio Reports and incorrect statistical values can occur in certain situations after the following has occurred: a report layout is deleted, a report layout object name is modified, and the report layout is re-created. ETL Runtime unites these layouts automatically; however, ETL Runtime does not update object information for deleted layouts. (ER# 62573)
Found In: 6.5.001.12 | Fixed In: |
In some rare cases when Configuration Tracking module and Configuration Server are running on the same HP11 64-bit box, the Configuration Tracking module may freeze upon start. If you encounter this problem, contact Genesys Customer Care . (ER# 74238)
Found In: 6.5.001.09 | Fixed In: |
The length of integer fields in DB2 Data Marts may not be adequate in some Reporting environments. This may result in arithmetic overflow. Contact Genesys Customer Care if this problem occurs. (ER# 63994)
Found In: 6.5.001.09 | Fixed In: |
For each report view, ETL Assistant shows the RDBMS view name containing data for every report layout based on the same underlying layout template. ETL Assistant does not reveal table names; therefore, you should use views to build reports. (ER# 51714)
Found In: 6.5.001.06 | Fixed In: |
If you attempt to add a Configuration Server node using ETL Assistant
without first using the Data Mart Wizard to configure ETL Assistant,
ETL Assistant displays the following error message: Config
Server authentication error
. Click Ignore
in this
message box and the node will be saved in the Data Mart anyway.
(ER# 52929)
Found In: 6.5.001.05 | Fixed In: |
The Solution Reporting Wizard creates an ETL_Service application object and installation package; however, the installation package creates another ETL_Service application object and does not enable you to select any pre-existing ETL application object. (ER# 85379)
Found In: 6.5 | Fixed In: |
The Configuration Tracking module of ETL Runtime may
generate a java.lang.NullPointerException
error when checking agent skills if the ETL user has
inadequate permissions to view the corresponding tenants.
(ER# 75806)
Found In: 6.1.301.07 | Fixed In: |
You may see minor inconsistencies in the appearance of the mouse cursor while hovering it over various elements of the ETL Assistant interface. (ER# 48601)
Found In: 6.1.301.02 | Fixed In: |
ETL Assistant may display the following error message while trying to schedule a purge process when more than 20 report layouts are open:
Unable to generate NextID to table PURGING_RULES Exception Mess:ORA-00604 error occurred at recursive SQL level1 ORA_01000: maximum open cursors exceeded;
Click OK
to close this dialog box. (ER# 43366)
Found In: 6.1.301.02 | Fixed In: |
When you add a new Configuration Server to the Data Mart, verify
the information in the
New Source
dialog box displayed by ETL Assistant as ETL
Assistant does not always detect all available ODS sources.
Also, you must add JDBC information manually as this information is not available within Configuration Server. For further details on the scanning process of the ETL Assistant, refer to the "Auto-Detecting ODS Sources" topic in the Reporting 7.2 ETL Assistant Help file. (ER# 42298)
Found In: 6.1.301.02 | Fixed In: |
For some RDBMSs, such as DB2 or Sybase, having ETL Assistant open continuously can inhibit the purge process; therefore, do not keep ETL Assistant open for an extended period of time. (ER# 40021)
Found In: 6.1.301.01 | Fixed In: |
ETL Assistant does not support multi-byte characters. Entering a multi-byte user or application name causes login failure. (ER# 38535)
Found In: 6.1.007 | Fixed In: |
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.
Support for the following operating systems and RDBMS has been discontinued:
Discontinued As Of: 7.6.100.06 |
Oracle 8.1.7 is no longer supported.
Discontinued As Of: 7.6 |
DB2 8.1 is no longer supported.
Discontinued As Of: 7.6 |
Information in this section is included for international customers.
Internationalization is not supported for this release of Data Mart.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Reporting Deployment Guide first.
Reporting 8.0 Deployment Guide describes how to configure, install, start, and stop ETL Runtime.
Reporting 7.6 ETL Runtime User's Guide describes ETL Runtime modules, configuration options, and runtime parameters.
Reporting 7.6 ETL Assistant Help describes the user interface; how to specify new source connections; how to edit information about existing sources, report folders, and report views; and how to schedule database purges.
Reporting 8.0 Master Index directs you to the location of specific topics in the Reporting documentation set.
Reporting 8.0 Reference Manual includes component performance measurements.
Reporting 7.6 Physical Data Model for a Microsoft SQL Data Mart provides database schema with table and field descriptions for an Microsoft SQL Data Mart.
Reporting 7.6 Physical Data Model for an Oracle Data Mart provides database schema with table and field descriptions for an Oracle Data Mart.
Reporting 7.6 Physical Data Model for a DB2 Data Mart provides database schema with table and field descriptions for a DB2 Data Mart.
Reporting 7.6 Physical Data Model for a Sybase Data Mart provides database schema with table and field descriptions for a Sybase Data Mart.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.
Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.