Read DIReleaseNotes.book text version

Data Integrator Release Notes

Data Integrator Release Notes Release Notes

Data Integrator 11.5.3.0 January 29, 2007 for Windows and UNIX

Patents

Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty

Trademarks

Third-party contributors

Copyright

Copyright © 2007 Business Objects. All rights reserved.

Data Integrator Release Notes

Introduction

Introduction

BusinessObjects Data Integrator XI Release 2 (XI R2) version 11.5.3.0 is a release update for version 11.5.2.0. This document contains important information about this product release, including installation notes, details regarding the latest resolved and known issues, and important information for existing customers. Please read this entire document before installing your Business Objects software.

Data Integrator information resources

Consult the Data Integrator Getting Started Guide for:

· · ·

An overview of Data Integrator products and architecture Data Integrator installation and configuration information A list of product documentation and a suggested reading path

After you install Data Integrator (with associated documentation), you can view the technical documentation from several locations. To view documentation in PDF format:

·

Select Start > Programs > Data Integrator version > Data Integrator Documentation and select:

· · · · · · · · ·

Release Notes--Opens this document, which includes known and fixed bugs, migration considerations, and last-minute documentation corrections Release Summary--Opens the Release Summary PDF, which describes the latest Data Integrator features Technical Manuals--Opens a "master" PDF document that has been compiled so you can search across the Data Integrator documentation suite Tutorial--Opens the Data Integrator Tutorial PDF, which you can use for basic stand-alone training purposes Release Notes Release Summary Technical Manuals Tutorial

Select one of the following from the Designer's Help menu:

Data Integrator Release Notes

1

2007 Daylight Savings Time

Other links from the Designer's Help menu include:

· ·

Knowledge Base--Opens a browser window to Business Objects' Technical Support Knowledge Exchange forum (access requires registration) Select Help from the Data Integrator Administrator to open the Technical Manuals.

To obtain additional information following the release of this document, or to find documentation for previous releases (including Release Summaries and Release Notes), visit the Business Objects Customer Support Web site at http://support.businessobjects.com/documentation/.

In this document

These release notes contain the following sections:

· · · · · · · ·

2007 Daylight Saving Time patch Compatibility and limitations update Software requirements for UNIX Migration considerations Resolved issues Known issues Business Objects information resources Copyright information

2007 Daylight Savings Time

Data Integrator XI Release 2 (XI R2) version 11.5.3.0 includes a Daylight Saving Time (DST) patch that allows Data Integrator to perform correctly after the new Daylight Saving Time period takes effect in 2007. Under the new law, Daylight Saving Time begins three weeks earlier than previously, on the second Sunday in March and is extended by one week to the first Sunday in November. The new start and stop period begins March 2007. This change affects the United States, Canada and Bermuda. The change affects Data Integrator jobs that are using the History Preserving transform with the option, "Preserve delete rows(s) as update rows(s)" enabled. Without the DST patch the Data Integrator engine will generate the wrong time for the to_date column. In versions of Data Integrator prior to 11.5.3.0, the included Java Virtual Machine does not compensate for the 2007 changes in Daylight Saving Time.

2

Data Integrator Release Notes

Compatibility and limitations update

The Daylight Saving Time (DST) patch included Data Integrator 11.5.3.0 corrects these errors. In general, a DST patch for the operating system is also required in conjunction with the Data Integrator patch. For the web application components, Data Integrator now bundles a new version of the JVM that contains the DST patch on the Windows platform. On the UNIX platforms, the minimum JDK version required is now 1.4.2 patch13. See your Operating System's vendor for current documentation on documentation on upgrading your OS for daylight savings's time. For complete details about how each version of Data Integrator is impacted, as well as specific technical details about the DST patch, see article 6637591 in the Data Integrator Knowledge Base, accessed from the Designer's Help menu. This link opens a browser window to Business Objects' Technical Support Knowledge Exchange forum (access requires registration).

Compatibility and limitations update

This section describes changes in compatibility between Data Integrator and other applications. It also summarizes limitations associated with this version of Data Integrator. For the latest information on compatibility, availability, and limitations, see the Supported Platforms documentation on the Business Objects Customer Support Web site at: http://support.businessobjects.com/documentation

Data Integrator Release Notes

3

Compatibility and limitations update

Compatibility update

This section describes:

· · ·

Supported products Unsupported products

Supported products

Support is now available for the following platforms and configurations:

· · · · ·

HP-UX for Itanium® 2 64-bit, version11.23 IBM DB2/UDB iSeries V5R3 via DB2 Connect. Please check the Supported Platforms documentation on the Business Objects Customer Support Web site for updates on iSeries client support. HTTPS support for Web services adapters Microsoft SQL Server 2005 MySQL 5.0 via ODBC driver version 3.51.12 for Windows only. Please check the Supported Platforms documentation on the Business Objects Customer Support Web site for updates on UNIX availability. Netezza NPS 2.5 and 3.0 via ODBC driver version 3.0.1 Red Hat Linux Advanced Server 4.0 SUSE Version 9 SP1 SAP BW 3.5 SAP ECC 6.0 Siebel 7.7 Solaris 10 operating system on Solaris SPARC Sybase Adaptive Server Enterprise 15.0 (Windows and UNIX support source, target, and repository)

· · · · · · · · ·

Data Integrator version 11.5.3 is compatible with versions 11.5 or 11.5 SP1 of the following BusinessObjects Data Integrator interfaces:

· · · · · · · ·

4

IBM Message Queue (MQ) Series Java Message Service (JMS) Salesforce.com (available in version 11.5 SP1 and above) BusinessObjects versions 6.5.1, XI, and XI R2. BusinessObjects universes 6.5.1, XI, and XI R2 Web Intelligence documents versions 6.5.1, XI, and XI R2 Desktop Intelligence documents version XI R2

Impact analysis will interoperate with:

Data Integrator Release Notes

Compatibility and limitations update

· ·

Business Views XI and XI R2

This release of Data Integrator is compatible with the Universe Builder version bundled with BusinessObjects Enterprise XI R2 SP1 with patch CHF-13. Find Universe Builder documentation in the "Building Universes from Data Integrator Metadata Sources" chapter of the Universe Designer Guide, which you can download from the Business Objects Customer Support Web site at http://support.businessobjects.com/ documentation/. Select BusinessObjects Enterprise as the product and Universe Designer Guide as the document. Data Mart Accelerator for Crystal Reports will interoperate with BusinessObjects version XI and XI R2. ODBC to generic database support has been validated with the following database servers and ODBC drivers. For complete compatibility details, see the Business Objects Supported Platforms documentation on the Business Objects Customer Support Web site: http:// support.businessobjects.com/documentation/

· ·

·

Microsoft SQL Server 2000 via DataDirect Connect for ODBC 5.0 or 5.1. Note: Version 5.1 is required on Linux and version 5.0 is required for Solaris Opteron.

· · · · ·

MySQL version 5.0 via ODBC driver version 3.51.12 on Windows and MySQL version 4.1 via ODBC driver version 3.51.10 on UNIX and Windows Red Brick version 6.3 via ODBC driver version IBM 6.3 SQLAnywhere version 9.0.1 via ODBC driver version Adaptive Server Anywhere 9.0

Sybase IQ version 12.6 requires ESD 4. Log-based changed-data capture (CDC) works with the following database versions

· · · ·

Oracle version 9.2 and above compatible versions for synchronous CDC and Oracle version 10G and above compatible version for asynchronous CDC Microsoft SQL Server 2000 and 2005 IBM DB2 UDB for Windows version 8.2 using DB2 Information Integrator for Replication Edition version 8.2 (DB2 II Replication) and IBM WebSphere Message Queue version 5.3. IBM DB2 UDB for z/OS using DB2 Information Integrator Event Publisher for DB2 UDB for z/OS and IBM WebSphere Message Queue version 5.3.1

Data Integrator Release Notes

5

Compatibility and limitations update

· · · ·

IBM IMS/DB using DB2 Information Integrator Classic Event Publisher for IMS and IBM WebSphere Message Queue version 5.3.1 IBM VSAM under CICS using DB2 Information Integrator Classic Event Publisher for VSAM and IBM WebSphere Message Queue version 5.3.1 Attunity for mainframe sources using Attunity Connect version 4.6.1

NCR Teradata V2R6 with TTU 8.0 and NCR Teradata ODBC 3.0.4 and V2R6.1 with TTU 8.1 and NCR Teradata ODBC 03.05.00 This support requires the following TTU patches:

·

On Windows platforms:

· · · · · · · · · · ·

cliv2.04.08.00.01.exe tbld5000.05.00.00.01.exe psel5000.05.00.00.01.exe pdtc5000.05.00.00.01.exe npaxsmod.01.03.01.00.exe npaxsmod.01.03.00.02.exe npaxsmod.01.03.00.01.exe cliv2.04.08.00.01.exe tbld5000.05.00.00.01.exe

On all UNIX platforms:

On AIX: 03.04.00.02

NCR Teradata V2R5 and V2R6 continue to be supported. Supported versions of TTU client include: Teradata server version V2R6.1 V2R6 V2R5.1 V2R5 Client version TTU 8.1 TTU 8.0 TTU 7.1 TTU 7.0

With Teradata V2R6, the named pipes mechanism for Teradata bulk loader is now supported. Note: Teradata does not recommend using Teradata Parallel Transporter in TTU 7.0 and 7.1, and there are some issues with Data Integrator on the AIX platform with multiple pipes.

·

Data Integrator Firstlogic data cleansing using:

·

International ACE version 7.70c

6

Data Integrator Release Notes

Compatibility and limitations update

· · ·

DataRight IQ version 7.60c

BusinessObjects Mainframe Bulk Interface using IBM WebSphere Information Integrator Classic Federation for z/OS version 8.2. BusinessObjects Mainframe Live Interface using the following:

· · · ·

WebSphere Information Integrator Classic Event Publisher version 8.2. WebSphere MQ for z/OS version 5.3.1

Data Integrator uses Apache Axis version 1.1 for its Web Services support. Axis version 1.1 provides support for WSDL version 1.1 and SOAP version 1.1 with the exception of the Axis servlet engine. Data Integrator connectivity to Informix servers is now only supported via the native Informix ODBC driver. The following Informix client SDK versions are required:

· · · · ·

Windows: version 2.81.TC3 or higher compatible version HP-UX for PA-RISC 32 bit: version 2.81.HC3X7 or higher compatible version AIX or SOLARIS SPARC: version 2.81.UC3X7 or higher compatible version Linux version 2.90.UC1 or higher compatible version HP-UX for Itanium 64-bit version 2.90.FC1 or higher compatible version

Unsupported products

· · · · · ·

Netezza NPS 2.5.x Netezza ODBC driver 2.2.1.5234 Netscape Navigator Red Brick 5.6.2 Trillium Interface Firstlogic data cleansing using:

· · · ·

International ACE versions 7.25c, 7.50c, or 7.60 DataRight IQ versions 7.10c or 7.50c

Informix repository and datastore connectivity via DataDirect Technologies ODBC. The migration path is to use native Informix connectivity. Data Integrator mainframe interface using DETAIL. The migration path is through the IBM Connector and Attunity Connector mainframe interfaces. For migration information and guidance, contact your Business Objects sales person.

Data Integrator Release Notes

7

Compatibility and limitations update

· · · ·

Data Integrator LiveLoad Context-sensitive Help for Data Integrator AIX version 5.1 Sybase IQ 12.5

Limitations update

These limitations apply to Data Integrator version 11.5.3.0:

·

The following products are not currently supported on the HP-UX for PARISC platform. (Please check the Supported Platforms documentation on the Business Objects Customer Support Web site for updates on support availability.)

· · ·

BusinessObjects Mainframe Bulk Interface BusinessObjects Mainframe Live Interface

The following products are not currently supported on the LINUX platform. (Please check the Supported Platforms documentation on the Business Objects Customer Support web site for updates on support availability.)

· · · · · ·

BusinessObjects Application Interface for JD Edwards One World or World BusinessObjects Application Interface for Siebel BusinessObjects Technology Interface IBM MQSeries Interface BusinessObjects Mainframe Bulk Interface BusinessObjects Technology Interface JMS

The following products are not currently supported on the HP-UX Itanium (64-bit) platform. (Please check the Supported Platforms documentation on the Business Objects Customer Support web site for updates on support availability.)

· · · · · · · ·

BusinessObjects Application Interface for J.D. Edwards One World or World BusinessObjects Interface for Siebel BusinessObjects Database Interface for NCR Teradata BusinessObjects Technology Interface for IBM MQSeries BusinessObjects Interface for JMS BusinessObjects Mainframe Bulk Interface BusinessObjects Mainframe Live Interface Data Cleansing

8

Data Integrator Release Notes

Compatibility and limitations update

· ·

Files read by an adapter must be encoded in either UTF-8 or the default encoding of the default locale of the JVM running the adapter. All Data Integrator features are available when you use an Attunity Connector datastore except:

· · · · · ·

Bulk loading Imported functions (imports metadata for tables only) Template tables (creating tables) The datetime data type supports up to 2 sub-seconds only Data Integrator cannot load timestamp data into a timestamp column in a table because Attunity truncates varchar data to 8 characters, which is not enough to correctly represent a timestamp value.

All Data Integrator features are available when you use an IBM Connector datastore except:

· · · · · · · ·

Datetime and timestamp data types are recognized as varchar, because IBM's DB2 II Classic Federation for z/OS product does not natively support these types Bulk loading Imported functions (imports metadata for tables only) Importing primary and foreign keys Template tables View Data's Column Profile feature

The Adapter SDK no longer supports Native SQL or Partial SQL. Unsupported data type:

· ·

Only implemented for SQL Server, Oracle, Teradata, ODBC, DB2, Informix and Sybase ASE, Sybase IQ, Oracle Applications, PeopleSoft, and Siebel. Data Integrator can read, load, and invoke stored procedures involving unknown data types for SQL Server, Oracle, Teradata, ODBC, DB2, Informix, Sybase ASE, and Sybase IQ assuming these database servers can convert from VARCHAR to the native (unsupported) data type and from the native (unsupported) data type to VARCHAR. Data Integrator might have a problem loading VARCHAR to a physical CLOB column (for example, bulk loading or auto-correct load could fail). Note: Use the VARCHAR column in the physical schema for loading. Unsupported data type is not supported in the SQL transform.

·

· ·

PeopleSoft 8 support is implemented for Oracle only.

Data Integrator Release Notes

9

Compatibility and limitations update

Data Integrator jobs that ran against previous versions of PeopleSoft are not guaranteed to work with PeopleSoft 8. You must update the jobs to reflect metadata or schema differences between PeopleSoft 8 and previous versions.

· ·

Stored procedure support is implemented for DB2, Oracle, MS SQL Server, Sybase ASE, Sybase IQ, and ODBC only. Teradata support is implemented for Windows, Solaris SPARC, and AIX. HP-UX for PA-RISC 32 bit is not supported due to limitations in Teradata's HP-UX for PA-RISC 32 bit product. HP-UX for Itanium and Solaris for AMD Opteron are not supported. On Teradata, the named pipe implementation for Teradata Parallel Transporter is supported with Teradata Tools and Utilities version 8 or later compatible version. Teradata Tools and Utilities version 7.0 and 7.1 are not supported with named pipes.

· · ·

Bulk loading data to DB2 databases running on AS/400 or MVS systems is not supported. Data Integrator Administrator can be used on Microsoft Internet Explorer version 6.0 SP1 or 6.0 SP2. Earlier browser versions may not support all of the Administrator functionality. Data Integrator's View Data feature is not supported for SAP R/3 IDocs. For SAP R/3 and PeopleSoft, the Table Profile tab and Column Profile tab options are not supported for hierarchies.

10

Data Integrator Release Notes

Compatibility and limitations update

·

Support for the Data Profiler is provided for sources as follows: Supported Not supported IDOC JDE SAP BW XML Memory Datastore COBOL copybooks

Attunity Connector for mainframe databases DB2 Flat file IBM connector for mainframe databases Informix Netezza ODBC (includes MySQL) Oracle Oracle Applications PeopleSoft SAP R/3 Siebel SQL Server Sybase ASE Sybase IQ Teradata

Data Integrator Release Notes

11

Compatibility and limitations update

·

Support for the LOOKUP_EXT function is provided for sources as follows: Supported DB2 Flat file Informix JDE Memory Datastore Netezza ODBC Oracle Oracle Applications PeopleSoft Siebel SQL Server Sybase ASE Sybase IQ Teradata Not supported IDOC SAP BW SAP R/3 XML

·

DB2 Java Library limitations The Web Administrator will not work with a DB2 repository under any of the following conditions:

· · · ·

db2java library is incompatible with DB2 client. For example, DB2 Client is version 8.1 and db2java library is version 8.2, or db2java library is not generated for JDBC 2 driver, or the java class path variable is not properly set to the corresponding java library, or the DB2 JDBC shared library (e.g. libdb2jdbc.so on AIX) is not compatible with the Java JDBC 2 driver The Administrator stops working or crashes after you configure the DB2 repository. Find any error and warning messages related to the DB2 repository configuration in the log file. When testing your DB2 connection from Administration > Repository > Specify DB2 database type and clicking "Test", the following errors appear in the Administrator log:

Under these conditions, you might see the following behavior:

· ·

·

BODI-3016409: fail to connect to repository.

12

Data Integrator Release Notes

Compatibility and limitations update

·

BODI-3013014: didn't load DB2 database driver.

In this release, the db2java JDBC 2 driver version of DB2 8.1 and DB2 8.2 are provided. On Windows, find the different version of these libraries $LINK_DIR/ext/lib

· ·

db2java.zip (by default) DB2 8.2 version db2java_8.1.zip DB2 8.1 version

By default, the db2java.zip of version 8.2 will be used. If you run with a DB2 8.1 Client, you must:

· · ·

replace with version 8.1 of db2java.zip make sure the compatible DB2 JDBC shared library is in the shared library path restart the web server service on Windows or restart the job service on UNIX

If you run with other DB2 Client versions, you must obtain the corresponding java library with the JDBC 2 driver. Please refer to IBM DB2 documentation for how to obtain the correct java library.

·

Informix native-driver support on UNIX requires a fix in the Informix Client SDK for IBM bug number 167964. Please contact IBM for a patch that includes this bug fix. Note: IBM is targeting inclusion of this bug fix in Client SDK version 2.90. Data Integrator supports files greater than 2 GB only in the following cases:

·

· · · ·

Reading and loading large data files of type delimited and positional. Generating large files for bulk loader staging files for subsequent bulk loading by a native bulk loader utility (such as SQL Loader). Previewing data files from the file format page in Designer when the large files are on a UNIX Job Server. Reading COBOL copybook data files.

All other files generated by Data Integrator, such as log files and configuration files, are limited to 2 GB.

·

The MySQL 64-bit library for HP-UX Itanium 64-bit only supports LazyLoading. When using MySQL on this platform, you must set LazyLoading=TRUE in $LINK_DIR/odbc.ini.

Data Integrator Release Notes

13

Software requirements for UNIX

Software requirements for UNIX

Please observe the following requirements for UNIX systems.

· ·

Use JDK version 1.4.2 patch 13 or higher as recommended by the vendor. The AIX maintenance level must be at least 5200-05. For all versions of AIX, the following file sets must be installed: Level 6.0.0.0 State Description

File set xlC.aix50.rte xlC.rte

6.0.0.13 COMMITTED C Set ++ Runtime for AIX 5.0 COMMITTED C Set ++ Run-time COMMITTED C Set ++ Run-time Messages, U.S.English

xlC.msg.en_US.rte 6.0.0.0

To find these xlC file sets and their levels on your AIX system, use the command lslpp -l xlC*

·

If you are installing the Administrator on HP-UX for PA-RISC 32 bit, add the following patches:

· ·

PHSS_26577 PHSS_26638

Refer to the $LINK_DIR/log/DITC.log file for browser-related errors.

14

Data Integrator Release Notes

Migration considerations

·

For Red Hat Linux 4, install the following patches:

· · · · · · · · · · · · ·

glibc-2.3.4-2 libgcc-3.4.3-9.EL4 compat-libstdc++-296-2.96-132.7.2 compat-libstdc++-33-3.2.3-47.3 Install 111721-04 (for both 32-bit and 64-bit SPARC) The patch 112874-22 causes a core dump error coming from the date function calls to the C lib. Apply the latest patch instead. 108434-13 (for 32-bit SPARC) 108435-13 (for 64-bit SPARC) 111722-04 (for both 32-bit and 64-bit SPARC) 120470-01

For Solaris 8:

For Solaris 9, install the appropriate patch:

For Solaris 10 SPARC, install the following patch:

Migration considerations

This section describes information for:

· ·

Repository upgrades Behavior changes

Repository upgrades

There are no repository changes in this release. The latest repository version in the 11.5 family is 11.5.2.0. If your current Data Integrator repository is version 11.0 or earlier, you must upgrade it to use this release. If your current repository is version 11.5.0 or later, you can use this release without upgrading the repository. However, you must upgrade your repository to take advantage of the following new features:

· · · · · ·

Data Quality Dashboards Preserving database case Salesforce.com Adapter Interface (delivered with version 11.5 SP1 Adapter Interfaces) Netezza bulk loading Teradata MultiLoad, TPump, and FastLoad

Data Integrator Release Notes

15

Migration considerations

Behavior changes

The following sections describe changes in the behavior of Data Integrator since the release of version 11.0.0. In most cases, the new version avoids changes that would cause existing applications to modify their results. However, under some circumstances a change has been deemed worthwhile or unavoidable. This section includes:

· · · · · · · · · · · ·

Brief installation instructions Netezza bulk loading Conversion between different data types Varchar behavior Central Repository Crystal Enterprise adapters Data cleansing Changes to Designer licensing Web Services support Sybase ASE version 12.5 bulk loader library on UNIX Informix native client support Statistics repository tables

Brief installation instructions

Complete installation instructions are in the Data IntegratorGetting Started Guide (for the stand-alone version, open the DIGettingStartedGuide.pdf in the Doc\Books folder on the installation CD). To install without a previous version of Data Integrator Follow the instructions in the Data Integrator Getting Started Guide to create a database location for a Data Integrator repository, run the installation program, and register the repository in the Data Integrator Administrator. To install with an existing version of Data Integrator Using your existing Data Integrator or ActaWorks version, export the existing repository to a file as a backup. Create a new repository and import the ATL file created in step 1. To use configuration settings from the previous version of Data Integrator or ActaWorks, create the new installation directory structure and copy the following files from your Data Integrator or ActaWorks installation into it. The default Windows installation structure is:

1. 2. 3.

16

Data Integrator Release Notes

Migration considerations

drive\Program Files\Business Objects\Data Integrator version

To use Administrator settings Repository, Job Server, and Designer settings 4.

Copy \conf directory \bin\dsconfig.txt

Uninstall your previous version of Data Integrator or ActaWorks. Business Objects recommends uninstalling, particularly when you are upgrading from ActaWorks to Data Integrator.

5. 6.

Install Data Integrator in the default location given by the install program. If you set up an installation path in step 3, use that path. During the installation, you can choose to upgrade the repository to the latest repository version in the 11.5 family (see "Repository upgrades" on page 12). If you used the configuration settings from the previous version, validate that the existing Job Server and Access Server configuration appears when you reach the server configuration section of the installer. After the installation is complete, open the Administrator at the browser location

http://<hostname>:28080

7.

8.

9.

Re-register (add) the repository.

Netezza bulk loading

If you are upgrading to 11.5.2.0 or later, to take advantage of the new Netezza bulk-loading functionality, follow these procedures. To enable Netezza bulk loading Upgrade your repository to version 11.5.2.0. In the Designer, for each ODBC datastore that uses a Netezza data source: a. b. Right-click the datastore and click Edit to open the datastore editor. Click OK.

1. 2.

This procedure verifies the connection to the database. If you receive a connection error: a. b. c. Open the ODBC Administrator. Select the data source name. Click Configure.

Data Integrator Release Notes

17

Migration considerations

d. e. f. g. 3. a. b.

Click Test Connection. Correct any connection errors. Right-click the datastore and click Edit to open the datastore editor. Click OK. Open the job so it appears in the workspace. Click the Save All button.

In the Designer, for each Netezza job:

This procedure causes Data Integrator to set the default options in the jobs. If you only upgrade the repository and do not perform the other steps, then the Bulk Loader Options tab for Netezza targets and the new options in the datastore editor won't be visible. However, Data Integrator still automatically employs bulk loading unless one or more of the following options have values set on the Netezza target table editor Options tab:

· · · ·

Ignore columns with value Ignore columns with null Any Error handling options Any Transaction control options

Conversion between different data types

For this release, there is a change in behavior for data conversion between different data types. Previously, if there was an error during data conversion (for example converting a varchar string to integer and the varchar string contains non-digits), the result was random. Now, the return value will be NULL for any unsuccessful conversion. Similarly, previously Data Integrator returned random data for the result of varchar to datetime conversion when the varchar string contains an illegal date format. Now, the return value will be NULL.

Varchar behavior

Data Integrator 11.5.0 (and above) conforms to the ANSI SQL-92 varchar behavior. When you upgrade Data Integrator and save your previous configurations, the default is to use the previous varchar behavior. However, Business Objects recommends that you use the ANSI varchar behavior because the previous varchar behavior will not be supported in a future Data Integrator version.

18

Data Integrator Release Notes

Migration considerations

To change from the previous varchar behavior to the ANSI varchar behavior 1. In the Data Integrator Designer, click Tools > Options > Job Server > General. 2. 3. 4. Enter al_engine for Section, ANSI_VARCHAR_BEHAVIOR for Key, and TRUE for Value. Click OK. If you want your jobs and work flows from a previous version of Data Integrator to use the ANSI varchar behavior, you must make changes in the following areas:

· · ·

NULLs and empty strings in scripts and script functions Trailing blanks in sources and functions NULLs, empty strings, and trailing blanks in transforms

For details about the changes in these areas and a comparison of the prior behavior and the varchar ANSI behavior, please contact Business Objects Technical Support at Business Objects Customer Support at http://support.businessobjects.com/.

Central Repository

Business Objects recommends the following guidelines to upgrade your central repository from one Data Integrator release to another.

·

Maintain a separate central repository for each Data Integrator version to preserve object history. An upgrade of the central repository might override the versions of any object whose internal representation (ATL) has changed in the new release.

1.

To preserve the current ATL of objects and their history Create a new central repository on the current Data Integrator release and export the latest version of all objects and their dependents from the existing central repository to the new central repository. Install the new Data Integrator release and upgrade the new central repository to the new Data Integrator release. Keep the existing central repository to maintain the history of the objects in the current release. Use the new central repository for objects that you create in the new release. Upgrade the central repository and local repositories at the same time, if possible.

2. 3. 4.

·

Data Integrator Release Notes

19

Migration considerations

A central repository might not work with a local repository that is on a different Data Integrator release. You might not be able to perform multiuser operations between a central repository and a local repository that are on different Data Integrator versions. Therefore, upgrade the central repository and local repositories to the same Data Integrator version at the same time.

·

If it is not convenient to upgrade the central and local repositories at the same time, check in all objects before you upgrade the central repository. Check in all objects (or undo the check-outs if objects have not been modified after check-out), especially those objects that were checked out to the local repositories that will not be upgraded at the same time. After you upgrade the central repository the new Data Integrator version, you will not be able to check in any objects from the local repository of an older Data Integrator version.

Crystal Enterprise adapters

After installing a new version of Business Objects, you might receive a class not found error when trying to start Crystal Enterprise adapter. You must update the Crystal Enterprise adapter configuration by updating the BusinessObjects directory name in the classpath for both the Crystal Enterprise adapter and the DMAC command file. To update classpaths Locate the new jar files. The default locations are: BusinessObjects XI: C:\Program Files\Common Files\ Business Objects\3.0\java\lib BusinessObjects XI R2: C:\Program Files\ Business Objects\common\3.5\java\lib 2. For the Crystal Enterprise Adapter: a. To ensure any new adapter instances have the correct classpath, modify LINK_DIR\adapters\install\CrystalAdaper.xml with the new jar file location. Modify the element <adapter3PartyJarFiles> by globally changing the path to the new jar files for Crystal Enterprise 10 (see the default location noted in the previous step) to that of the BusinessObjects XI path. Save the file. Any future adapter instances created will now have the correct jar file path. Change any configured adapter instances by deleting the configured adapter instance and creating a new one using the same adapter instance name, which keeps all adapter usage valid.

1.

b. c.

20

Data Integrator Release Notes

Migration considerations

3.

For the DMAC command file launched by the DMAC wizard: a. b. Edit LINK_DIR\ext\dmac\wizard.com. Change the entry set CE_JARS_DIR= to point to the new path. For example, if you installed BusinessObjects XI, the line should read:

set CE_JARS_DIR=C:\Program Files\Common Files\Business Objects\3.0\java\lib

Data cleansing

The new Data Integrator installation will overwrite all template job files shipped with Data Integrator with the upgraded job files compatible with Firstlogic DataRight IQ 7.60c, Match Consolidate 7.60c, and International ACE 7.7c. If you had manually modified the template job files and want to preserve the changes, Business Objects recommends you make a copy of the job file or rename it prior to installing Data Integrator version 11.5.3.0. If you will be using International ACE 7.7c with Firstlogic 7.6c products, install the Firstlogic 7.6c products and upgrade the modified template job files for the 7.6c products before installing International ACE 7.7c. After installing Data Integrator version 11.5 and the Firstlogic 7.6c software, do the following: 1. From the Data Integrator CD, copy pwdiqjob.upd from the following directory:

· ·

2.

Windows: \Utilities UNIX: /unix/PLATFORM

to the dtr_iq directory. Click Yes to overwrite the existing file. For your customized job templates for DataRight IQ 7.6c and Match Consolidate 7.6c, run Firstlogic's edjob 7.6c utility to upgrade your Firstlogic job files from the previous version to 7.6c. Find the edjob utility in the Firstlogic installation directory. Run the utility to upgrade all jobs of the same extension by specifying *.extension in the utility. Extension names are .diq and .mpg. For instructions on how to use the edjob utility, refer to the Firstlogic documentation. Note: If the jobs have already been updated to 7.60c (using the .upd file that came with the master installation using edjob), you will receive the following error when trying to open a 7.60 job:

Error: The "Report Defaults" block, occurrence 1, has an incorrect number of lines and the job cannot be loaded.

You will need to manually edit these jobs to change the version string in the General block from the previous version to 7.60c. Then rerun edjob with the correct .upd file.

Data Integrator Release Notes

21

Migration considerations

3.

If you are using International ACE, install the 7.7c version of the software (and the edjob utility) and run edjob to upgrade the International ACE job templates to 7.7c. For all International ACE template job files, manually edit the job templates using an editor such as Notepad, and comment out the Create Output File block by adding the * character at the beginning of the line. For example:

*BEGIN Create Output File

4.

Changes to Designer licensing

Data Integrator Designer versions 6.5 and above do not support floating licenses. If you are currently using floating Designer licenses, obtain a new license key before upgrading. Send your request to [email protected] with Data Integrator License Keys as the subject line. The new key will be added to your existing License Authorization Code. For more information, contact Business Objects Customer Support at http:// support.businessobjects.com.

Web Services support

When using Data Integrator with Web Services, the following limitations exist:

· · ·

SAP R/3 IDoc message sources in real-time jobs are not supported The Data Integrator Web Services server uses the first Job Server in the list of those available for a batch job. The first Job Server might be a server group. If you are using Web Services and upgrading to versions 6.5.0.1 or above, Web Services server (call-in) functionality that you created with previous versions of Data Integrator is not supported. Perform the following changes to manually upgrade the Web Services server:

·

Regenerate a WSDL file Prior to release 6.5.0.1, every batch job and real-time service configured in Data Integrator was published in the WSDL file. In release 6.5.0.1 and above, Data Integrator only publishes batch jobs and real-time services that you select. Clients that call Data Integrator using Web Services will fail until you authorize the jobs and services being invoked.

22

Data Integrator Release Notes

Migration considerations

·

Change SOAP calls to match those in the 6.5.0.1 and above versions. A session ID is not included in SOAP messages unless you enable security for the Web Services server. Prior to release 6.5.0.1, the sessionID message part was published in every SOAP message. To fix this problem, change SOAP calls to match those in the 6.5.0.1 or above version of the WSDL file.

· ·

If security is off, remove the sessionID line from the SOAP input message. If security is on, copy the sessionID from the SOAP body to the SOAP header as a session ID now appears in the SOAP header instead of the body.

Note: When you install 6.5.0.1 or above, the installer automatically upgrades the Web Services Adapter and your existing Web Services clients will function properly.

Sybase ASE version 12.5 bulk loader library on UNIX

With Sybase ASE version 12.5, the installed Sybase ASE client on UNIX platforms does not include the Sybase bulk loader dynamic shared library that Data Integrator requires. Please refer to the README in either the CDROM Location/unix/PLATFORM/AWSybase directory or the $LINK_DIR/AWSybase directory for instructions about how to:

· ·

Confirm that the library is available in the Sybase client installation Build the library

Informix native client support

If you created an Informix repository and datastores with a previous Data Integrator release using DataDirect Technologies Connect ODBC driver, they are not compatible with Data Integrator 6.5.1 and above. You must recreate your repository, datastores, and jobs if you want to use the Informix native driver.

Statistics repository tables

The repository tables AL_FLOW_STAT and AL_JOB_STAT are no longer populated for job, work flow, or data flow statistics. These two tables no longer exist in the newly created Data Integrator version 11.0.1 and above repositories. They could still exist in the repositories that are upgraded to version 11.0.1 and above.

Data Integrator Release Notes

23

Migration considerations

Beginning with Data Integrator version 11.0.1, all job, work flow, and data flow statistics are stored in the AL_HISTORY, AL_HISTORY_INFO, and AL_STATISTICS tables. In particular, the job statistics, previously stored in AL_JOB_STAT, are now stored in the AL_HISTORY and AL_HISTORY_INFO tables. The work flow and data flow statistics, previously stored in AL_FLOW_STAT are now stored in the AL_STATISTICS table. Use the metadata reporting tool to retrieve all job, work flow and data flow statistics.

24

Data Integrator Release Notes

Resolved issues

Resolved issues

Please refer to http://support.businessobjects.com/documentation for the latest version of these release notes, which includes resolved issues specific to version 11.5.3.0. ADAPT00700221 You can now use a lookup_ext function as part of the input schema to the pivot transform as a non-pivot column. ADAPT00691549 Outer joins are now evaluated properly if Data Integrator functions are used in the WHERE clause in the Query transform. ADAPT00687101 When working with Teradata environments, you may run into the following error message when using Teradata bulk loader in named pipe mode: Named pipe error occurred: <The system cannot find the file specified> This problem is resolved in this release by eliminating the maximum named pipe connection wait time restriction. You can now set the flag NamedPipeWaitTime to any number of seconds. ADAPT00675249 In LINUX, where completed execed() processes in a job are instructed not to wait, these completed processes do not linger. ADAPT00673927 Connections to the Job Server are now released when done. The connections do not accumulate to a point where system resources are depleted. ADAPT00672346 When using smtp_to function to send email messages, the send time and the receive time are now synchronized. ADAPT00619969 Data Integrator jobs now exit normally on the LINUX when a lookup_ext function call to Oracle database has a datetime column in the condition list. This applies to all UNIX platforms as well. ADAPT00696434 When using the Validation transform on the Solaris platform the job may exit abnormally. This problem has been fixed. ADAPT00695837 When running a real-time job that contains a XML message format as a source as well as a XML format in the transform, you may encounter an error with WSDL generation if the real-time job is published via Web Administrator. This problem has been addressed in this release. If you have seen this issue with your real-time job, after applying this Hot Fix, you will need to open the job in the Designer and re-save the job for this fix to take effect.

Data Integrator Release Notes

25

Resolved issues

ADAPT00693918 In the Data Integrator Release Notes, the Solaris patch requirement information for Solaris versions 8 & 9 is incorrect. The correct patch requirement is: Solaris 8: Install 111721-04 (for both 32-bit and 64-bit SPARC) · 108434-13 (for 32 bit SPARC)

·

108435-13 (for 64 bit SPARC)

Solaris 9: The patch 112874-22 causes a core dump error coming from the date function calls to the C library. Apply the latest patch instead: 111722-04 (for both 32-bit and 64-bit SPARC) ADAPT00692414 When viewing complex jobs in Auto Documentation, the print functionality may fail with the following error: An application internal error occured: Array index out of range: 2 java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 2 at java.util.Vector.get(Vector.java:709) This issue has been resolved. ADAPT00691896 When calling a SQLServer 2000 stored procedure from Data Integrator, the varchar parameter value is not passed in correctly. This issue has been resolved. ADAPT00688040 In the Web Administrator, there is a memory leak when viewing job execution logs. If the user views many monitor logs from the Web Administrator, the memory usage of the job server process will increase. This issue has been fixed. ADAPT00687185 Java error is encountered when using the print functionality in Auto Documentation. This is similar to bug ADAPT00692414. The user may experience the following error: An application internal error occured: -1 java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.Vector.get(Vector.java:711) at com.acta.webapp.mdreport.selfdoc.DIObjects.DIWorkspace$VectorWorksp aceSteps.get(DIWorkspace.java:284) at com.acta.webapp.mdreport.selfdoc.DIObjects.ObjectCalls.DIIFStep.parse( DIIFStep.java:82) This issue has been resolved. ADAPT00685406 When exporting Data Integrator data flows, incorrect ATLs were generated when the data flow contains lookup_ext function call which contains global variables. This issue has been resolved. ADAPT00683909 When calling a function in a loop inside a Data Integrator script, an access violation error may occur. This problem has been fixed.

26

Data Integrator Release Notes

Resolved issues

ADAPT00680744 Historical rows are not preserved properly if there are multiple entries of the same primary key and compare columns. The entry with the latest data is preserved instead of the entry with the earliest date. This issue was caused by incorrect logic when comparing sorted input data in the Table Comparison transform, and the problem has been fixed in this release. ADAPT00678466 When using Oracle char size semantic to define a column data type as char or varchar, Data Integrator may cause an Oracle error at runtime when performing the binding process for the column. This problem has been resolved. ADAPT00672004 Duplicate rows are not recognized properly in Table Comparison transform, and this problem caused the History Preserving transform to not function properly. This issue was caused by the Key Generation transform not setting up the internal cache properly. The problem appeared when Key Generation transform was used in conjunction with Table Comparison and History Preserving transforms. This problem has been fixed. ADAPT00670238 Starting in Data Integrator version 11.5.1.16, a bug in the outer join SQL generation has been corrected. Data Integrator now generates ANSIcompliant outer join syntax. This correction caused some customers' jobs to behave differently once the customers upgrade to 11.5.2.0. For 11.5 (starting from 11.5.2.4) releases only, a flag has been added so that customers can switch to the old outer join syntax. This flag will not be in the other releases that are not in the 11.5 version family, so customers should re-visit and adjust their jobs accordingly to accommodate for the new outer join syntax. From Data Integrator Designer, choose Tools->Options->Job Server>General. Enter al_engine in the section field, OldBehaviourFilter for the key, and 1 for the value if you wish to use the old outer join syntax. ADAPT00669473 When viewing Data Integrator jobs in Auto Documentation containing Cobol copybook sources, the documentation generated does not display the objects and connection lines properly. This problem has been fixed. ADAPT00660497 Running the executable smtp_mailer.exe causes MS C++ Runtime Error when zone contains spaces at the end. This issue has been addressed.

Data Integrator Release Notes

27

Resolved issues

ADAPT00660212 A new utility FixupDIMapText is introduced in this Hot Fix release to allow users to correct a repository that may have corrupted mappings in the data flows. If you have noticed that changes made to the column mappings are not reflected after the data flows are saved, you will need to run this utility. The corruption will only happen if you have a Multi-User environment, and there are users using Designers of version earlier than 11.5.1.18 and Designers of version 11.5.1.18 or later. The usage of the utility is as follows: fixupUIMapText.exe -U<user> -P<passwd> -S<server> -N<database_type> -Q<database_name> -g<Windows Authentication> Valid database types are: Informix, DB2, Oracle, Sybase, Microsoft_SQL_Server Note that the -g option applies to Microsoft SQLServer databases only. ADAPT00659815 When using the Auto Documentation feature, error message ObjectType Job is invalid is thrown when selecting some data flows from the left window pane. This issue has been addressed. ADAPT00659451 When using a while looping containing a data flow in the Auto Documentation feature, the while condition and the name of the data flow are not readable because they are superimposed on top of each other. This issue has been addressed. ADAPT00659440 Table descriptions are not displayed in the Auto Documentation feature. This issue has been addressed. ADAPT00658146 Case transforms are displayed incorrectly in Auto Documentation. This issue has been addressed. ADAPT00657456 Validation conditions are not displayed in Auto Documentation. This issue has been addressed. ADAPT00656102 When reading a Cobol copybook that contains REDEFINES clause, the data is not aligned properly when viewing the data from the Designer. This issue has been addressed. ADAPT00652478 Profiler tasks do not appear to be completed when the profiler repository database is Microsoft SQLServer. The tasks are displayed as 'Pending' in the Designer as well as the Web Administrator. This problem has been fixed. The tasks now return with the correct execution status. ADAPT00652463 An unknown exception occurs when viewing a XML file using the Designer. This problem has been fixed. ADAPT00648544 When reading varchar data using the Oracle 9i driver, if the length of the actual data read is less than the size of the varchar, memory leaks occur. This problem has been fixed. ADAPT00648523 Fixed-width file formats are not generated correctly if the data file is located on a remote server. This problem has been fixed.

28

Data Integrator Release Notes

Resolved issues

ADAPT00646862 For Microsoft SQLServer CDC readers, a new option in the source editor called Automatically delete rows after reading lets users delete rows after reading them from the replication server to manage server volume. For example, if many rows collect on the replication server during a given retention period, performance could suffer. If you select this option, Data Integrator deletes only the rows that have already been read by all Data Integrator CDC readers and other named subscriptions (and also observes the retention period setting). However, if there are additional anonymous subscribers, Data Integrator is unable to identify them and could delete rows regardless of whether or not they have been read by those subscribers. A CDC reader subscription is not established until the first time a job with such subscription is successfully executed. If in the CDC reader Automatically delete rows after reading option selected, and this reader with this subscription has not been executed before in any other data flow, Data Integrator will assume that there is only one subscription and the data will be purged after reading. This behavior will go away after the job has been executed at least once. If this is not the desired behavior, there are few workarounds: 1. Do not enable Automatically delete rows after reading option for the first runs of the Data Integrator jobs to establish all subscriptions. 2. If a CDC table has more than one subscription, check the Delete after reading in one CDC source only and execute the corresponding job last. ADAPT00644743 When defining a custom function in the Designer, the ordering of the input parameters are reversed inside the function. This problem has been fixed. ADAPT00644246 Data Integrator Designer aborts abnormally when function literal is used in a script and the script is validated. This issue has been addressed. ADAPT00642556 When a data flow or a work flow runs in an infinite loop, the Data Integrator engine process (al_engine) leaks memory. This problem has been fixed. Data Integrator also now submits a slightly different SQL statement to Microsoft SQL Server to improve performance when retrieving changed data from SQL Server replication server distribution database. ADAPT00642531 When the Cobol copybook contains REDEFINES sections, the data for those fields are not processed properly by Data Integrator. This issue has been resolved. ADAPT00642513 When importing a database link created in Microsoft SQLServer 2005, the Designer does not recognize the database link as a valid link. This issue has been addressed. ADAPT00641650 When using the Ignore Row Marker option in the flat file format, data truncation may occur. This problem has been fixed. ADAPT00641386 Sybase repository upgrade fails with syntax error when upgrading from Data Integrator version 6.1 to 11.5.2.0. This issue has been addressed.

Data Integrator Release Notes

29

Resolved issues

ADAPT00637736 Within a real-time job, using the same data flow more than once causes incorrect SQL insert statement to be generated. This issue has been addressed. ADAPT00635818 Reading multi-byte data from a flat file may get unexpected result. This problem has been solved. ADAPT00635475 Users can now specify a custom character to use as row delimiter in Sybase IQ bulk loader. A new flag called SybaseIQRowDelimiter can now be added to specify the row delimiter in the data file generated by Data Integrator. To add this flag, go to the Designer. From the menu, choose Tools->options>Job Server->General. Enter al_engine for the section field, and SybaseIQRowDelimiter for the key field, and the value of the delimiter. For non-printable characters, use the ASCII representation such as /125. ADAPT00633919 If a Cobol copybook contains REDEFINES clause and it is used together with the OCCURS clause, Data Integrator interprets the data incorrectly. This issue has been fixed. ADAPT00633872 The Data Integrator job fails when the job contains very large Cobol copybook schemas. This issue is addressed by modifying the internal language (ATL) generation to eliminate unnecessary ADAPT00621273 Data Integrator now provides support or SAP ECC 6.0 on Windows. ADAPT00619781 A Tomcat 500 error is encountered when starting Metadata Reports after the Data Integrator repository is upgraded from version 11.0 to version 11.5. This issue has been resolved. ADAPT00619421 When importing a Microsoft SQLServer table that has an index with a name of more than 64 characters, the import operation fails. This problem has been fixed. Data Integrator now imports correctly the index information along with the table. If the index name is longer than 64 characters, only the first 64 characters of the name will be saved in the repository. ADAPT00717659 Metadata Integrator fails with the following error when collecting Desktop Intelligence report information: repository(ies) not found This is an issue only if the user is using Metadata Integrator with Business Objects Enterprise XIR2 with patch MHF1 or above. This issue has been resolved. ADAPT00635925 The Metadata Integrator is enhanced in this release. More details of various Business Objects Enterprise objects are now captured. ADAPT00702353 Metadata Integrator fails when collecting Universes stored in a sub-folder. This is an issue only if the user is using Metadata Integrator with Business Objects Enterprise XIR2 with patch MHF1 or above. This issue has been resolved.

30

Data Integrator Release Notes

Known issues

Known issues

This section lists known issues in descending order by Business Objects tracking number. 36002 On Windows XP operating systems, columns in the query editor might not appear to be highlighted under certain conditions because of the default Windows XP color settings (the background and menu color are the same). As a work-around, change the Menu color by right-clicking on the Windows XP desktop, select Properties, click the Appearance tab, click Advanced, and under the Item drop-down list, select Menu and change the color. Firstlogic is not supported on HP Itanium 64bit. See http://support.businessobjects.com/documentation/ for additional information that may have become available following the release of this document. 33510 Due to a known Informix issue, two phase commit (XA) transactions in IBM® Informix® Dynamic Server may cause Data Integrator to fail loading the data to IBM Informix Dynamic Server or profiling data with Informix. The typical Informix errors are:

Could not position within a table

34003

and

Could not do a physical-order read to fetch next row. The reference number from the IBM site is Reference# 1172548. <http://www-1.ibm.com/support/docview.wss?uid=swg21172548>

33324

For SQL Server datastores, if the table owner name is DBO and the CMS connection is also SQL Server with logon user name of SA, the update Universe will determine the new table schema to be new because DBO is compared to SA as owner name. Tip: Do not use SQL Server as CMS connection with SA as login name. The Data Profiler does not support SQL Server profiling repositories that use Windows Authentication. Data Integrator does not support any non-ASCII characters that use the eighth bit (such as an umlaut) in metadata (such as the owner name). When using Attunity CDC, import from browser and import by name behave differently. For example, when you type either CDC_DSNX4612:PUBLIC or CDC_DSNX4612 as the owner name, the same table will be imported into the repository. Tip: When you import a table by name, always use the full owner name such as CDC_DSNX4612:PUBLIC and also define the alias for this full name.

33028 31165 30925

Data Integrator Release Notes

31

Known issues

30506

Due to an issue in Attunity software, when using Attunity Connect to load into a DB2 table on MVS that contains varchar columns larger than 255, the data inserted into those columns is always an empty string regardless of what you actually insert. A datastore in a nonsecure central repository can be deleted even if it has a table that is checked out by other users. For HP-UX at certain patch levels, the installation might fail with the following error message due to an HP-UX issue:

Placing product files into LINK_DIR cp: cannot access /cdrom/unix/hpux1100/AWSybase: No such file or directory As a work-around, use the pfs_mount command to mount the installation CD.

30059 29987

For example: 1. 2. Log on as root. Start pfs_mountd and pfsd:

# /usr/sbin/pfs_mountd & # /usr/sbin/pfsd &

3. 4. 5.

Edit or create the file /etc/pfs_fstab with the following content:

/dev/dsk/cxtydz /ISO_CDROM pfs-iso9660 xlat=unix 0 0

Create the /ISO_CDROM directory if it doesn't exist. Mount the installation CD:

# pfs_mount /ISO_CDROM

29826

When adding a very large project to central repository, a large memory leak occurs. Tip: After adding large projects to central repository, restart the Designer. SQL Server bulk loader API truncates the decimal precision when multiplying 2 decimals. Tip: Use the round function before bulk loading in the column mapping.

29018

28959

Data Integrator always works in binary collation for Table Comparison transform. If the comparison table sort order is not binary, Data Integrator will generate inconsistent results between cached, row-by-row and sorted comparison methods. Access server crashes on Windows 2003 machines when hyperthreading is activated. When using the Data Mart Accelerator for Crystal Reports, numbers that appear in the Link field are rounded to six digits.

28654 28610

32

Data Integrator Release Notes

Known issues

28399

On UNIX when running a Data Integrator job with an Attunity datastore, the job fails with following error: [D000] Cannot open file /usr1/attun/navroot/def/sys

System error 13: The file access permissions do not allow the specified action.; (OPEN)

This error occurs because of insufficient file permissions to some of the files under the Attunity installation directory. To avoid this error, change file permissions for all files under the Attunity directory to 777. Run the following command from Attunity installation directory: chmod a+rw *. 28356 When you import a table by name and this table is the target table of a table comparison transform, the table comparison does not refresh the database changes. Tip: Open the table comparison transform to refresh the output schema. 28319 28161 Execution statistics are not available for all instances of a real-time job over the life of a long-running Data Integrator batch job. The SAP function RFC_READ_TABLE does not work correctly with SAP 4.70 when reading source data if one of the table fields is a floating-point field. Tip: Install the Data Integrator recommended transport file (preferred) or install the Z_AW_RFC_READ_TABLE function manually from the supplied text file. 27974 On Solaris, Informix's client driver does not support the ONSOCTCP communication protocol. Until Informix provides a fix, Business Objects recommends you use the ONTLITCP communication protocol. By default, Data Integrator uses the ONSOCTCP communication protocol. Therefore, on Solaris, you must change the communication protocol configuration found in the Informix SQLHOSTS and the ODBC.ini files to use either ONTLITCP or SETLITCP communication protocols. 27485 27390 Data Integrator does not monitor database connections given through the scripts. When using the Get by label option of the multi-user development interface with a non-existent label, Data Integrator returns the latest version of the objects. Column Profiling is not supported in the View Data feature on SAP R/3 cluster and pool tables. Tip: Use the Data Profiling feature introduced in DI XI R2. 27045 Multibyte strings are not handled correctly when passed as a function parameter. Tip: Put multibyte string parameters in quotes.

27048

Data Integrator Release Notes

33

Known issues

26445

When editing metadata from columns belonging to multiple tables, all metadata except for that in the last table is lost. This is caused by refresh problems in the Designer. Work Around: To ensure your metadata is saved to the repository, close the metadata window for each table before opening the next table for editing.

26355

When comparison tables are on Microsoft SQL Server, the Table Comparison transform's Sorted input option generates incorrect results. The Data Integrator engine runs in binary collation while the Microsoft SQL Server database runs in a Latin1 collation sequence. As a result, Microsoft SQL Server generates the data in a different sort order. This issue will be addressed in a later release. Tip: Use the Row-by-row select or Cached comparison table option in the Table Comparison transform.

25578 24746

When processing large MQ messages, you must use IBM's AMI repository. If you do not use the AMI repository, the PUT operation could fail. Data Integrator cannot import metadata through an adapter if it includes a DTD or XML Schema that begins with the header <?xml encoding="UTF-8"?>. Tip: Remove the header line. When bulk loading to Oracle using the API method, Data Integrator cannot load a case-sensitive partitioned target table name due to a problem in Oracle. The following error message displays:

ORA - 02149. The specified partition does not exist.

24223

Tip: Use the File method and select the Direct path option to handle casesensitive partition names. 24195 For the DB2 database, when the Data Integrator engine pushes down a SELECT statement and the SELECT statement has an upper/lower function for a graphic/vargraphic data type, then the describe column (ODBC library call) returns a char data type instead of a graphic data type. This is an ODBC bug. Tip: Set the datastore's code page to utf8 (or a similar superset code page). 24013 When you specify length (lpad(' ',41) for the varchar data type, it returns different lengths when it is pushed down to an Oracle database if the bind column is NCHAR or NVARCHAR2. The issue is with the Oracle OCI client. Tip: Do not use Data Integrator's Auto-correct load option (on the target table editor) for an Oracle table when you want to specify length (lpad(' ',41) for the varchar data type.

34

Data Integrator Release Notes

Known issues

23941

For Oracle, the load trigger for an NCHAR or NVARCHAR data type fails if the code page in the database does not support these characters in the pushdown SQL. Consequently, Oracle fails to execute the SQL properly. For example, the following situations are known to cause problems:

· · ·

The database code page is english, we8ISO88591 The code page of the NCHAR column in the database is ucs2 The submitted SQL has Japanese characters

Tip: Do not use Data Integrator's Auto-correct load option (on the target table editor) when processing NCHAR or NVARCHAR data types. 23938 If the code page used by the Oracle client is set to certain values (it works for utf8 and fails for we8winms1252), and the bind column size is greater than 1312, and Data Integrator uses the same Oracle connection more than twice during internal processing, then Oracle will throw the following error:

ORA-01460: unimplemented or unreasonable conversion requested

23852

For MS SQL Server, if a concatenation operator is used in a stored procedure and if the code page for the database is ucs2, then the ODBC library fails to concatenate the data properly. The issue is with the Microsoft ODBC driver. Tip: Do not allow Data Integrator to push down a concatenation expression to the database. One way to do this is to construct job so that data loads into a flat file and the concatenation operation occurs in another query. Thus, Data Integrator cannot push down the SELECT statement because the target does not have the operation it needs.

23811

For Oracle, nchar or nvarchar data types do not work for database procedures and database functions when one of the parameters has an nchar or nvarchar column and the datastore code page set in Data Integrator does not understand nchar or nvarchar encoding. In these cases, the Data Integrator engine handles nchar or nvarchars as if they were varchar data types. After you restart an adapter instance, the service that uses it fails to process the next message it receives. Tip: When you restart an adapter instance, also restart its associated services.

23687

23005

When reading XML schema data, you may encounter the following error message:

Type of attribute 'lang' must be validly derived from type of attribute in base...

Tip: Change your schema to avoid use="prohibited" for any attribute or element whose type is derived from xsd:language.

Data Integrator Release Notes

35

Known issues

22690

If you have a data flow that includes mapping a varchar column to a datetime column in a query transform, the job will give an access violation error if any of the date values are invalid. The Adapter SDK has some syntax limitations for DTDs that can be imported for use as an adapter source or target:

21659

·

Conditional syntax cannot be included in the DTD file. Sample syntax that fails:

<!-- Common ebXML header--> <!ENTITY % INCLUDE_EBHEADER "INCLUDE"> <![ %INCLUDE_EBHEADER; [<!ENTITY % eb:MessageHeader SYSTEM "ebHeader.dtd">%eb:MessageHeader;]]>

Tip: The following syntax is supported and produces the same result:

<!ENTITY % eb:MessageHeader SYSTEM "ebHeader.dtd"> %eb:MessageHeader;

·

XML version information cannot be included in the DTD file. Sample syntax that fails:

"<?xml version="1.0" encoding="UTF-8"?>"

Tip: Eliminate the line from the file. Note: These limitations only apply to DTD files read by an adapter, not those read by the Designer. It is important to note that the only file the adapter reads is the one configured in the adapter operation. Adapters do not read embedded DTD files.

36

Data Integrator Release Notes

Business Objects information resources

20647

View optimized SQL in the Designer does not capture the latest changes to the data flow. Instead, SQL for the previously-saved version of the object displays. Tip: To view Optimized SQL for the latest changes, save the object first. The mail_to function does not work on Windows 2000 after downloading a security patch for Microsoft Outlook. Tip: To send e-mail out from Data Integrator after installing a security patch, follow the instructions from the following web site:

http://support.microsoft.com/default.aspx?scid=kb;enus;Q263297&id=263297&SD=MSKB#OB

19893

The instructions on the web site show how to suppress prompting when sending e-mail from a particular computer. First a security policy file is created on the Exchange Server. Second, the registry key is added to a client machine that tries to send e-mail programmatically. This client machine is the machine on which you are running the Data Integrator Job Server. When a client machine tries to send an e-mail, the Outlook client first checks the registry key. If this key is set, Outlook looks at the security policy file on the exchange server. In the security policy file, turn off prompting and the Data Integrator mail_to function will work.

Business Objects information resources

Business Objects offers a full documentation set covering its products and their deployment. Additional support and services are also available to help maximize the return on your business intelligence investment. The following sections detail where to get Business Objects documentation and how to use the resources at Business Objects to meet your needs for technical support, education, and consulting.

Documentation

You can access electronic documentation at any time from the product interface, the web, or from your product CD.

Documentation on the web

The full electronic documentation set is available to customers on the web from the Customer Support web site at: http://support.businessobjects.com/ documentation/.

Data Integrator Release Notes

37

Business Objects information resources

Documentation on the product CD

Look in the Doc directory of your product CD or installation directory for guides in Adobe Acrobat PDF format.

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: [email protected] Note: If your issue concerns a Business Objects product and not the documentation, please contact our Customer Support experts at http:// support.businessobjects.com.

Customer support, consulting, and training

A global network of Business Objects technology experts provides customer support, education, and consulting to ensure maximum business intelligence benefit to your business.

Data Integrator Diamond

Business Objects Diamond provides technical information such as white papers, tips and tricks, and listings of training opportunities and other events. This site is available to all Data Integrator users. http://diamond.businessobjects.com/

Customer support centers

Business Objects offers customer support plans to best suit the size and requirements of your deployment. We operate customer support centers in the following countries:

· · · · ·

USA Australia Canada United Kingdom Japan

38

Data Integrator Release Notes

Business Objects information resources

Online Customer Support

The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including Knowledge Base articles, downloads, and support forums. http://support.businessobjects.com/

Consultation

Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/

Training

From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: http://www.businessobjects.com/services/training

Useful addresses at a glance

Address Business Objects product information http://www.businessobjects.com Product documentation http://support.businessobjects.com/ documentation Business Objects Documentation mailbox [email protected] Online Customer Support http://support.businessobjects.com Content Information about the full range of Business Objects products. Business Objects product documentation, including the Business Objects Product Document Map. Send us feedback or questions about documentation. Information on Customer Support programs, as well as links to technical articles, downloads, and online forums.

Data Integrator Release Notes

39

Copyright information

Address Business Objects Consulting Services http://www.businessobjects.com/ services/consulting/ Business Objects Education Services http://www.businessobjects.com/ services/training

Content Information on how Business Objects can help maximize your business intelligence investment. Information on Business Objects training options and modules.

Copyright information

SNMP copyright information

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University Portions Derivative Work - 1996, 1998-2000 Portions Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Portions Copyright (c) 2001, Networks Associates Technology, Inc All rights reserved.

40

Data Integrator Release Notes

Copyright information

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the NAI Labs nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Portions of this code are copyright (c) 2001, Cambridge Broadband Ltd. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND

Data Integrator Release Notes

41

Copyright information

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Specifications subject to change without notice. Not responsible for errors or admissions.

IBM ICU copyright information

Copyright (c) 1995-2003 International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

42

Data Integrator Release Notes

Copyright information

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

Data Integrator Release Notes

43

Copyright information

44

Data Integrator Release Notes

Information

DIReleaseNotes.book

46 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

835749