Data Services Release Notes
BusinessObjects Data Services XI 3.0 (12.0.0)
Copyright
© 2008 Business Objects. All rights reserved. Business Objects owns the following
U.S. patents, which may cover products that are offered and licensed by Business
Objects: 5,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;
6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;
7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objects
logo, BusinessObjects, Business Objects Crystal Vision, Business Process On
Demand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,
Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,
the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let
there be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web
Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in
the United States and/or other countries of Business Objects and/or affiliated
companies. All other names mentioned herein may be trademarks of their respective
owners.
Third-party
Contributors
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
2008-03-27
Contents
Introduction to Data Services XI 3.0 5Chapter 1
Documentation set for Data Services..........................................................6
Business Objects information resources.....................................................9
Compatability and limitations update 13Chapter 2
Compatibility update..................................................................................14
Limitations update......................................................................................17
Migration considerations 23Chapter 3
Resolved issues 25Chapter 4
Known issues 31Chapter 5
Data Services Release Notes 3
Contents
4 Data Services Release Notes
Introduction to Data Services XI 3.0
1
Introduction to Data Services XI 3.0
1
Documentation set for Data Services
Welcome to BusinessObjects(TM) Data Services XI 3.0 version 12.0.0. This
version is a functional release that includes the following new features:
• Data Services combines industry-leading data quality and integration into
one platform. With Data Services, your organization can transform and
improve data anywhere. You can have a single environment for
development, runtime, management, security and data connectivity.
• Enterprise agility (ease of use)
• Trusted information
• Operational excellence
• Enterprise class
See the Data Services Release Summary for details about these key features.
Read this entire document before installing your Business Objects software.
It contains important information about this product release including
installation notes, details regarding the latest resolved and known issues,
and important information for existing customers.
To obtain the latest version of Data Services documentation including the
most up-to-date version of these Release Notes, visit the Customer Support
documentation download site
(http://support.businessobjects.com/documentation/) and follow the
appropriate product guide links.
Related Topics
• Compatibility update on page 14
• Limitations update on page 17
• Migration considerations on page 23
• Resolved issues on page 25
• Known issues on page 31
Documentation set for Data Services
You should become familiar with all the pieces of documentation that relate
to your Data Services product.
6 Data Services Release Notes
Introduction to Data Services XI 3.0
Documentation set for Data Services
What this document providesDocument
1
Documentation Map
Release Summary
Release Notes
Getting Started Guide
Installation Guide
Advanced Development Guide
Designer Guide
Integrator's Guide
Management Console: Administrator
Guide
Information about available Data Services books,
languages, and locations
Highlights of key features in this Data Services release
Important information you need before installing and
deploying this version of Data Services
An introduction to Data Services
Information about and procedures for installing Data
Services
Guidelines and options for migrating applications including information on multi-user functionality and
the use of the central repository for version control
Information about how to use Data Services Designer
Information for third-party developers to access Data
Services functionality
Information about how to use Data Services Administrator
Management Console: Metadata Reports Guide
Migration Considerations
Migration Guide
Performance Optimization Guide
Reference Guide
Information about how to use Data Services Metadata
Reports
Release-specific product behavior changes from
earlier versions of Data Services to the latest release
Information about how to migrate from Data Quality
to Data Services
Information about how to improve the performance
of Data Services
Detailed reference material for Data Services Designer
Data Services Release Notes 7
Introduction to Data Services XI 3.0
1
Documentation set for Data Services
Technical Manuals
What this document providesDocument
A compiled “master” PDF of core Data Services books
containing a searchable master table of contents and
index:
• Installation Guide
• Getting Started Guide
• Designer Guide
• Reference Guide
• Management Console: Metadata Reports Guide
• Management Console: Administrator Guide
• Performance Optimization Guide
• Advanced Development Guide
• Supplement for J.D. Edwards
• Supplement for Oracle Applications
• Supplement for PeopleSoft
• Supplement for Siebel
• Supplement for SAP
Tutorial
In addition, you may need to refer to several Adapter Guides and
Supplemental Guides.
JMS Adapter Interface
Salesforce.com Adapter
Interface
Supplement for J.D. Edwards
Supplement for Oracle Applications
A step-by-step introduction to using Data Services
What this document providesDocument
Information about how to install, configure, and use the Data
Services Adapter for JMS
Information about how to install, configure, and use the Data
Services Salesforce.com Adapter Interface
Information about license-controlled interfaces between Data
Services and J.D. Edwards World and J.D. Edwards OneWorld
Information about the license-controlled interface between Data
Services and Oracle Applications
8 Data Services Release Notes
Introduction to Data Services XI 3.0
Business Objects information resources
What this document providesDocument
1
Supplement for PeopleSoft
Supplement for SAP
Supplement for Siebel
Information about license-controlled interfaces between Data
Services and PeopleSoft
Information about license-controlled interfaces between Data
Services, SAP ERP and R/3, and SAP BI/BW
Information about the license-controlled interface between Data
Services and Siebel
Business Objects information resources
Customer support, consulting, and training
A global network of Business technology experts provides customer support,
education, and consulting to ensure maximum business intelligence benefit
to your business.
Useful addresses at a glance
ContentAddress
Product information
http://www.businessob
jects.com
Information about the full range of Business
Objects products.
Product documentation
http://www.businessob
jects.com/support
Documentation mailbox
documentation@businessobjects.com
Business Objects product documentation, including the Business Objects Documentation
Roadmap.
Send us feedback or questions about your
Business Objects documentation.
Data Services Release Notes 9
Introduction to Data Services XI 3.0
1
Business Objects information resources
ContentAddress
Online Customer Support
http://www.businessob
jects.com/support
Online Developer Community
http://diamond.businessob
jects.com/
Consulting services
http://www.businessob
jects.com/services/consulting/
Education services
http://www.businessob
jects.com/services/training
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://www.businessobjects.com/support
Information on Customer Support programs,
as well as links to technical articles, downloads, and online forums.
An online resource for sharing and learning
about Data Services with your developer colleagues.
Information about how Business Objects can
help maximize your business intelligence investment.
Information on Business Objects training options and modules.
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, Business
Objects 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
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is
there something that you particularly like or have found useful? Drop us a
line, and we will do our best to ensure that your suggestion is considered for
the next release of our documentation: documentation@businessobjects.com.
10 Data Services Release Notes
Introduction to Data Services XI 3.0
Business Objects information resources
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts.
1
Data Services Release Notes 11
Introduction to Data Services XI 3.0
Business Objects information resources
1
12 Data Services Release Notes
Compatability and limitations update
2
Compatability and limitations update
2
Compatibility update
For the latest and detailed compatibility, availability, and lmitations information,
see the Supported Platforms documentation on the Business Objects
Customer Support Web site at:
http//support.businessobjects.com/documentation
Compatibility update
This section describes:
• Interoperability with other Business Objects products
• List of utilities included in this release
• Unsupported (deprecated) Business Objects functionality
Interoperability with other Business Objects products
• Data Services' impact analysis interoperates with:
• BusinessObjects universes 6.5.1, XI, XI R2 SP2 or above, XI 3.0
• Web Intelligence documents versions 6.5.1, XI, XI R2 SP2 or above,
XI 3.0
• Desktop Intelligence documents versions 6.5.1, XI, XI R2 SP2 or
above, XI 3.0
• Business Views XI, XI R2 SP2 or above, XI 3.0
• Data Services' scheduling functionality is supported with BusinessObjects
version XI R2 or later versions of the BusinessObjects Enterprise
scheduler.
• Data Services supports Data Insight 12.0.0.
• Data Services is compatible with the following Universe Builder versions:
• The stand-alone Universe Builder version 11.5 bundled with Data
Services 12.0. This stand-alone version of Universe Builder will
interoperate with BusinessObjects version 6.5.1 and XI. 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 Assurance
Web site at http://support.businessobjects.com/documentation/. Select
BusinessObjects Enterprise as the product and Universe Designer
Guide as the document.
• The Universe Builder version bundled with BusinessObjects Enterprise
XI R2, XI R2 SP2 or above, and XI 3.0.
14 Data Services Release Notes
Compatability and limitations update
Compatibility update
• Data Services' 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
• Attunity for mainframe sources using Attunity Connect version 4.6.1
• Data Services and Data Federator support Java Virtual Machine for
version compatibility:
To access Data Federator data sources with Data Services, you must
modify your OpenAccess environment to use the Java Virtual Machine
that ships with Data Services. Data Federator installs a component called
OpenAccess ODBC to JDBC Bridge that requires these modifications.
Make the following modifications (where Data Federator is installed in
D:\Program Files\Business Objects\BusinessObjects Data Federator 12,
Data Services is installed in D:\Program Files\BusinessObjects XI
3.0\BusinessObjects Data Services, and OpenAccess is installed in
D:\Program Files\OaJdbcBridge):
2
1. In the OpenAccess configuration file
(LINK_DIR\OaJdbcBridge\bin\iwinnt\openrda.ini), the path for the JVM
must be changed from JVM_DLL_NAME=D:\Program Files\Business
Objects\BusinessObjects Data Federator
12\jre\bin\client\jvm.dll to JVM_DLL_NAME=D:\Program
Files\BusinessObjects XI 3.0\BusinessObjects Data Ser
vices\ext\Jre\Bin\client\jvm.dll
2. Add the following OpenAccess jar files to the CLASSPATH
environment variable:
• D:\ProgramFiles\OaJdbcBridge\jdbc\thindriver.jar
• D:\ProgramFiles\OaJdbcBridge\oajava\oasql.jar
Included utilities
The following utilities are included with Data Services XI 3.0 to support Data
Quality address correction functionality.
Data Services Release Notes 15
Compatability and limitations update
2
Compatibility update
DescriptionUtility
ShowA
CaShowL
Unsupported (deprecated) Data Quality functionality
The following functionality, which was available with Data Quality XI R2, is
no longer available in Data Services:
• Web Services: .Net Deployment and several function calls
• Compound Transforms
• Shared options
• Unique ID Record Stem support in Candidate Selector
• Pre/Post SQL Operations in Reader transform
• Per Dataflow Mode in UDT (use workflow and scripts instead)
• Disabled transforms
• Thread and watermark settings on a per-transform basis
• Observer transform
• Progress Service Transform
• Integrated batch API
• Admin methods in real-time API
• JIS_Encoding, UTF-32 for flat files
• Python methods for UDT
• Generic Per Collection Mode Sort in Sorter transform
• DBASE3 file formats
Looks up address line information in the US address directories
Looks up lastline information in the US address directoriesShowL
Looks up address line information in the Canadian address
directories
The following functionality, which had been available with Data Integrator XI
R2 Accelerated, is no longer available:
• Log-based changed-data capture (CDC) with IBM DB2 UDB for Windows,
z/OS, IMS/DB, and IBM VSAM.
Related Topics
• Limitations update on page 17
16 Data Services Release Notes
Limitations update
The following limitations apply to Data Services version 12.0.0:
• All Data Services 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 Services 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
• Unsupported data type:
• Unsupported data type is only implemented for SQL Server, Oracle,
Teradata, ODBC, DB2, Sybase ASE, Sybase IQ, Oracle Applications,
PeopleSoft, and Siebel.
• Data Services 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 (unknown) data
type and from the native (unknown) data type to VARCHAR.
• Data Services might have a problem loading VARCHAR to a physical
CLOB column (for example, bulk loading or auto-correct load could
fail).
Compatability and limitations update
Limitations update
2
Note: Use the VARCHAR column in the physical schema for loading.
• Stored procedure support is implemented for DB2, Oracle, Microsoft SQL
Server, Sybase ASE, Sybase IQ, and ODBC only.
• 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 z/OS or iSeries systems
is not supported.
• View Data is not supported for SAP ERP or R/3 IDocs. For SAP ERP or
R/3 and PeopleSoft, the Table Profile tab and Column Profile tab options
are not supported for hierarchies.
Data Services Release Notes 17
Compatability and limitations update
2
Limitations update
• Metadata values with multibyte data are not supported by the Data
Cleanse rule file. Because of this restriction, the Designer and underlying
UDC transform code does not support multibyte values for custom output
categories, output fields, and classifications.
• Data Services supports multibyte metadata for table names, column
names, file names, and file paths. The following table lists which sources
support multibyte and single-byte metadata and which support single-byte
only.
supported
Single-byte metadata supportedMultibyte and single-byte metadata
• BusinessObjects Enterprise
• Data Federator
• DB2
• Data Quality
• Informix
• MySQL
• ODBC
• Oracle
• Siebel
• Microsoft SQL Server
• Sybase ASE
• Sybase IQ
• Teradata
• XML
Note: Support for multibyte metadata is dependent on comparable support
• Attunity connector for mainframe
databases
• HP Neoview
• JD Edwards
• Netezza
• Oracle Applications
• PeopleTools
• SAP ERP and R/3 databases
• SAP BI/BW server
in the applications, databases, and technologies with which Data Services
interoperates.
• Support for the Data Profiler is provided for sources as follows.
18 Data Services Release Notes
Compatability and limitations update
Limitations update
Not supportedSupported
2
• Attunity Connector for mainframe
databases
• DB2
• Data Federator
• Flat file
• HP Neoview
• Informix
• Microsoft SQL Server
• MySQL
• Netezza
• ODBC
• Oracle
• Oracle Applications
• PeopleSoft
• SAP ERP and R/3
• Siebel
• Sybase ASE
• Sybase IQ
• Teradata
• COBOL copybooks
• Excel
• IDOC
• JD Edwards
• Memory Datastore
• SAP BI/BW
• XML
• Support for the LOOKUP_EXT function is provided for sources as follows.
Data Services Release Notes 19
Compatability and limitations update
2
Limitations update
Not supportedSupported
• DB2
• Data Federator
• Flat file
• JD Edwards
• HP Neoview
• Memory Datastore
• Microsoft SQL Server
• MySQL
• Netezza
• ODBC
• Oracle
• Oracle Applications
• PeopleSoft
• Siebel
• Sybase ASE
• Sybase IQ
• Teradata
• COBOL copybook
• Excel
• IDOC
• SAP BI/BW
• SAP ERP and R/3
• XML
• All files generated by Data Services, such as log files and configuration
files, are limited to 2 GB. Data Services 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.
• When using Microsoft Excel as a data source, the following limitations
apply:
• Concurrent access to the same Excel file might not work. For example,
View Data might not display if the file is currently open in Excel.
• Because an Excel column can contain mixed data types, some data
type conversions could produce unexpected results; for example,
dates might convert to integers.
• Boolean formulas are not supported.
20 Data Services Release Notes
Compatability and limitations update
Limitations update
• Workbooks with AutoFilter applied are not supported. Remove the
filter before importing the workbook.
• Workbooks with hidden rows and/or columns are not supported.
• Stored procedures for MySQL are not supported due to limitations in
the MySQL ODBC library.
• The Data Services Salesforce.com adapter can connect to the
Salesforce.com version 7 API; however, the new functionality added in
API version 7 and above is not supported. The custom lookup field is the
only exception (new in API version 7) and is supported in the
Salesforce.com adapter. To ensure that your existing Salesforce.com
adapter works properly, you must update the URL in the datastore so
that it points to Salesforce.com 7.0 API, the new URL should be:
https://www.salesforce.com/services/Soap/u/7.0.
Related Topics
• Compatibility update on page 14
2
Data Services Release Notes 21
Compatability and limitations update
Limitations update
2
22 Data Services Release Notes
Migration considerations
3
Migration considerations
3
The Migration Considerations Guide contains two pieces of technical
documentation related to migrating to Data Services XI 3.0.
•
Migration Considerations: Contains, tracks, and briefly describes all
behavior changes associated with all supported versions of Data
Integrator.
•
Data Quality to Data Services Migration Guide: Contains new features
and explains how to upgrade from previous Data Quality releases.
Related Topics
• Resolved issues on page 25
• Known issues on page 31
24 Data Services Release Notes
Resolved issues
4
Resolved issues
4
Refer to http://support.businessobjects.com/documentation for the latest
version of these release notes, which includes resolved issues specific to
version 12.0.0.. All issues that were corrected with the Data Integrator 11.7.3.0
Service Pack are included in this release. For details on issues fixed in Data
Integrator 11.7.3.0, please refer to the BusinessObjects Data Integrator
Release Notes for version 11.7.3, which are available for download at
http://www.businessobjects.com/support.
The numbers refer to the Business Objects ADAPT system Problem Report
tracking number and are listed in ascending order. We also use these
numbers in the release notes that accompany our fix packs and patches.
You can reference the tracking number when searching for the issue on our
knowledge base or when speaking to Customer Assurance.
DescriptionIssue ID
ADAPT00620112
ADAPT00620821
ADAPT00621063
ADAPT00661876
ADAPT00671258
ADAPT00673438
ADAPT00688056
ADAPT00688210
When you import a table by name and this table is the targetable
of a Table Comparison transform, the table comparison does
not refresh the database changes. Open the Table Comparison
transform to refresh the output schema.
Windows NT authentication for Microsoft SQL Server doesn't
work for the Administrator and Metadata Reports. Use Microsoft
SQL Server authentication instead.
When using the Get by label option of the multiuser development interface with a non-existent label, Data Integrator returns
the latest version of the objects.
SQL Transform loses the Query if related datastore is missing.ADAPT00641710
A Data Quality project cannot be imported if the project path
name is longer than 230 characters.
Sysdate doesn't return correct format with iSeries on AS/400.
The problem is resolved by changing the sysdate function so
it now maps to a function of ODBC instead of curdate.
Data Quality Project descriptions are not imported into Data
Integrator Object Library.
Stopping a Data Integrator job will not stop the Data Quality
process.
Data Integrator should not import a project with more than one
socket writer.
26 Data Services Release Notes
Resolved issues
4
DescriptionIssue ID
ADAPT00733805
ADAPT00736500
ADAPT00738936
ADAPT00851830
ADAPT00879525
If the input to the Data Quality transform is not mapped and the
output of the transform is mapped, Data Integrator will hang
when the Job is executed.
Under the following circumstances, the Profiler may stay in the
pending state indefinitely:
• The repository is not connected to a job server.
• The associated job server is not running. Please check the
above before running the Profiler again.
Previously, there was a known issue with Data Quality projects
that contain periods (".") in the field names. Although the
projects can be imported from the Data Quality server, Data
Integrator cannot correctly map these fields. The project can
be used in a data flow as long as the fields containing periods
are not used. A workaround for this problem is to rename any
Data Quality project fields to use another character instead of
the period. Business Objects suggests using the underscore
character ("_").
This issue is not applicable in Data Services.
Data Services Management Console now disallows duplicate
repository connection entries.
When a table comparison transform was used, and if the compared table had a special character in the name, Data Integrator
did not handle the internal language generation properly. Multiple escape characters ( \) were added to the language.
ADAPT00880964
ADAPT00881112
ADAPT00882479
ADAPT00883226
It is now possible to import all the functions published by Siebel
Web Services WSDL into the Data Integrator Designer.
Data Integrator was not able to import ATLs that contained
object names that were exactly 64 characters in length. The
Data Integrator Designer occasionally exited abnormally if an
object name (such as table index name) was 64 characters
long.
When the file reader options adaptable schema and include
file name were set and the data file had extra columns defined,
Data Integrator did not read all of the rows.
Metadata Integrator can now properly work with two tables with
the same name but different owners in Data Integrator.
Data Services Release Notes 27
Resolved issues
4
DescriptionIssue ID
ADAPT00883284
ADAPT00885583
ADAPT00885589
ADAPT00890818
ADAPT00892929
ADAPT00896013
ADAPT00896020
When running a job via the Web Administrator, Data Integrator
now handles the global variables correctly.
For all CDC table readers, the cache option should always be
no. Prior to this release, Data Integrator Designer allowed the
user to set the reader option to yes, but did not honor the yes
value. This issue has been addressed by not allowing the user
to set the reader option to yes.
Data Integrator job produced incorrect result when two tables
were joined with a user-defined script function in the WHERE
clause, and the result data set was part of an outer-join.
Data Integrator job execution occasionally ended with the following error: SYS-170111: Cannot stop Memory monitor thread
: <RWThreadImp::terminate - No thread is active within the
runnable>.
Data Integrator job failed with the following error when reading
decimal data with scale of 9 or larger while the operating system
locale of the Job Server was using the comma character as the
decimal separator: cannot convert data<123456.123456789>
into type decimal .
The Salesforce.com adapter for Data Integrator now supports
the Salesforce.com data type anyType.
The Salesforce.com adapter for Data Integrator now correctly
queries the field LastModifiedDate on each CDC table, ensuring the data is properly copied.
ADAPT00904659
28 Data Services Release Notes
Calling the function <HTTP_ReqReply_Function> no longer
returns an error.
Resolved issues
4
DescriptionIssue ID
ADAPT00905796
ADAPT00906629
ADAPT00912163
ADAPT00913707
ADAPT00915902
ADAPT00918876
Between Data Integrator 11.7.1 and 11.7.3.0, when reading
CHAR data that contained all spaces from database tables,
one space was preserved while all the rest were stripped. This
behavior conflicted with the ANSI SQL-92 varchar standard
which Data Integrator has complied with since 11.5.0 release.
This behavior has been corrected in this release to not preserve
any spaces. With this release, when ANSI varchar behavior is
set and Data Integrator encounters character data of all spaces,
the spaces will be trimmed resulting in an empty string. If you
want to reserve the space, you can turn off ANSI varchar behavior by setting the ANSI_VARCHAR_BEHAVIOR to FALSE
(for more information, refer to varchar behavior section in the
MigrationBehaviorChanges document).
Comparing a local object with its version stored in the central
repository will no longer produce differences.
The Configuration tool will now appear after running the cmsCon
fig.cmd command.
Pushdown SQL functions included in jobs created in Data Integrator version 11.5 will now work properly when imported in
Data Integrator version 11.7 or later.
Data flows were not properly executing when the property
cache type was set to pageable. This issue has been resolved.
The value field of the al_statistics table now contains no decimal
separator, allowing queries on that field to complete successfully.
ADAPT00918879
ADAPT00919899
ADAPT00920638
ADAPT00931228
The count_distinct command now returns the same results
for decimal data types as for integer data types.
Using the Data Integrator passthrough functionality on Data
Quality fields will now pass these fields to the target datastore
without any modifications.
Using a hierarchy-flattening transform in a data flow with
pageable cache will no longer corrupt data.
It is now possible to process a very large XML source file
through the XML pipeline without encountering the 2-gigabyte
memory issue.
Data Services Release Notes 29
Resolved issues
4
DescriptionIssue ID
ADAPT00963405
ADAPT00963686
ADAPT00980366
Related Topics
• Migration considerations on page 23
• Known issues on page 31
Adding an alias in IBM DB2 Datastore will no longer cause
Data Integrator to return different optimized SQL statements
than without adding the alias.
From Data Services 12.0 release onwards, 'ntext' data type will
be treated as LONG data type. See the Migration Considera-
tions Guide: Large object data type enhancements for more
information.
Sometimes Data Integrator jobs would not run to completion
even though memory was available and database was idle.
30 Data Services Release Notes
Known issues
5
Known issues
5
This section lists known issues in ascending order by Business Objects
ADAPT system Problem Report tracking number. We also use these numbers
in the release notes that accompany our fix packs and patches. You can
reference the tracking number when searching for the issue on our knowledge
base or when speaking to Customer Assurance.
DescriptionIssue ID
ADAPT00619350
ADAPT00619427
ADAPT00619479
Duplicate of known issue ADAPT00620063. Data Services always works in binary collation for the 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. Use the Row-byrow select or Cached comparison table option in the Table
Comparison transform.
For Microsoft SQL Server datastores, if the table owner name
is DBO and the CMS connection is also Microsoft SQL Server
with a login user name of sa, the updated Universe will determine the new table schema to be new because DBO is compared to sa as owner name. Do not use Microsoft SQL Server
as CMS connection with sa as the login name.
Due to a known Informix issue, two phase commit (XA) transactions in IBM® Informix® Dynamic Server could cause Data
Integrator to fail when loading the data to an IBM Informix Dynamic Server or profiling data with Informix. The typical Informix
errors are:
• Could not position within a table 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
ADAPT00619744
ADAPT00620168
32 Data Services Release Notes
To correctly configure Data Integrator for a BusinessObjects
Enterprise XI Release 2 CMS instance that is not on the same
computer as Data Integrator, refer to the Business Objects
Customer Support Web site and see Knowledge Base article
c2019073.
When adding a very large project to a central repository, a large
memory leak occurs. After adding large projects to a central
repository, restart the Designer.
ADAPT00620227
Known issues
5
DescriptionIssue ID
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. 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.
ADAPT00620654
ADAPT00620815
ADAPT00644390
ADAPT00653478
ADAPT00655863
ADAPT00658811
ADAPT00688976
The import by name functionality for the Web Services adapter
is not working. The work-around is to use metadata Explorer
(browser) to import any metadata from the Web Services
adapter.
Changed-data capture for Oracle 10g R2 does not support
multibyte table or column names due to an Oracle limitation.
The problem is fixed in Oracle product patch 5693948. This
patch is available on MetaLink which you can download and
apply on top of Oracle 10.2.0.3.
Duplicate of ADAPT00867507. See the discription of that issue
for more information.
Table attribute function does not return correct value for processed and deleted rows in the case when there are multiple
records affected by the SQL statement at the target.
Data Integrator Web Services supports only the UTF8 code
page.
When creating a Data Integrator repository on IBM DB2, only
the UTF-8 code page is supported.
If the Web Service Adapter does not work due to an incorrect
keystore path, you must restart the Tomcat server after you
specify the correct keystore path.
Data Services Release Notes 33
Known issues
5
DescriptionIssue ID
ADAPT00695056
ADAPT00857453
ADAPT00867507
The Adapter SDK has the following syntax limitation for DTDs
that can be imported for use as an adapter source or target.
Conditional syntax cannot be included in the DTD file. Sample
syntax that fails: <!-- Common ebXML header--><!ENTITY %
INCLUDE_EBHEADER ""INCLUDE""><![ %INCLUDE_EBHEAD
ER;[<!ENTITY % eb:MessageHeader SYSTEM""ebHeader.dtd""> %eb:MessageHeader; ]] The following syntax is supported and produces the same result: <!ENTITY % eb:MessageHeader SYSTEM ""ebHeader.dtd""> %eb:MessageHeader;
This limitation only applies 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.
The option names you see in Match error messages may not
match the actual option name.
Duplicate of known issue ADAPT00644390.
Auto-correct loading might fail for Microsoft SQL Server,
ODBC, DB2, Informix, Sybase IQ, or Teradata databases if
the data contains NULL termination characters at the end
of varchar data. The auto-correct SQL does not generate
properly. To work around this issue, use the rtrim_blanks_ext
functions on columns that you know will contain NULL termination characters to trim the blanks. This issue also occurs
with Sybase and Sybase IQ targets in regular load mode.
Use the rtrim_blanks_ext to work around this issue for those
databases as well.
ADAPT00879554
ADAPT00879558
34 Data Services Release Notes
Duplicate for ADAPT00879558. See the description of that issue
for more information.
Duplicate of known issue ADAPT00879554.
When the UTF16 File contains data in the wrong encoding,
there is a possibility that column or row delimiter cannot be
detected and columns in the record may contain wrong data.
Data Services always expects that data in the UTF16 file
match character encoding specified in the codepage field
of File Format.
Known issues
5
DescriptionIssue ID
ADAPT00885748
ADAPT00893921
ADAPT00894516
ADAPT00901582
ADAPT00920349
ADAPT00946040
USA Regulatory Address Cleanse job with Degree of Parallelism
set to four or higher inconsistently locks directories and crashes.
When running the dqmigration utility, an error occurs indicating
that Crypto.dll was not found. To run the dqmigration utility
successfully, add %LINK_DIR%\bin to your PATH environment
variable.
When using Data Integrator with Netezza 4.0, the job may fail
with the following error message: SQL submitted to ODBC data
source <netezzadsn> resulted in error <ERROR: 0 : Invalid
datetime part value: 'quarter' >. This is due to a bug in the
Netezza driver not handling the "week" and "quarter" functions
properly. As a workaround to this problem, go to the "Advanced"
section in the Netezza 4.0 datastore and set the "week" and
"quarter" functions to "no" for pushdown.
Hierarchy flattening with a pageable cache does not work
properly for large amount of data. Hierarchy flattening might
run out of memory even when pageable cache is used.
Printed Editable RTFs result in borders around the graphic
objects and problems with report object placements. If you print
editable RTFs, graphic objects may be placed incorrectly and
will have borders around them.
The results you receive when performing a search with the
Data Cleanse Transform may not be in alphabetical order.
ADAPT00959994
ADAPT00961708
ADAPT00980373
ADAPT00981444
Sybase ASE is not a supported database for Global Parsing
Option installation.
If Global Parsing Option installation fails, the Data Cleanse
repository can be left in a state that causes the Data Services
Designer to crash. You can correct the problem by cleanly reinstalling the Global Parsing Option.
Unable to run EMEA job using al_engine from command line
except from the \bin directory.
On Windows 64-bit machine, Data Services Install generates
an Unknown Error while creating Repository when using a port
that is already listening. User is responsible to select unique
port for different application (for example, Tomcat, MySQL, and
so on.) when running Data Services on Windows 64-bit environment.
Data Services Release Notes 35
Known issues
5
DescriptionIssue ID
ADAPT00982063
ADAPT00988304
ADAPT00992900
USA Regulatory Address Cleanse Reports - The percentage
values for the LACSLink and DPV counts on the US Addressing
Report and Address Validation Summary utilize the total number
of records instead of the number of the total records submitted
for processing, causing the percentages to be slightly off when
Z4 change is enabled or Unicode characters are encountered.
When installing the Global Parsing Option for SQL Server 2000
and SQL Server 2005, we do not currently support database
names with dashes in them. For SQL Server 2000, the
workaround is for the user to put square brackets around the
database name. For SQL Server 2005, the workaround is for
the user to rename their database so that it does not have a
dash in it.
An error may occur if you have the output from the Validation
transform set to Pass or Fail, and the output only is used as an
inner source for a nested option in a Query transform.
The reason for this is that the Validation transform tries to
determine whether either PASS or FAIL is unused. It removes the unused output. If the output is used inside the
nesting, then validation transform cannot detect that the
output is being used and it prematurely deletes it.
Workaround: Insert a Merge transform between the Validation transform and the Query transform that does nesting.
ADAPT00994160
ADAPT00994274
ADAPT00995162
36 Data Services Release Notes
Any Match - Unique ID - Data flows will terminate with a memory error when processing extremely large collections.
Workaround: Go to Tools > Options > Job Server > General
and set the attributes accordingly: Section: AL_Engine, Key:
PAGEABLE_CACHE_BUFFER_POOL_SIZE_IN_MB, Value:
150. This will not completely fix the issue but it will allow for
larger collection sizes to be processed.
The Compare To Object functionality does not always work
correctly for Data Quality transform configurations.
Loading more than 32767 bytes to Sybase IQ CLOB, BLOB,
LONG VARCHAR and LONG BINARY columns is not supported
in this release.
Known issues
5
DescriptionIssue ID
ADAPT00996278
ADAPT00996491
ADAPT00997306
ADAPT00998517
ADAPT00999899
ADAPT0099982
ADAPT01001587
In the Global Parsing Option silent installer, the Record/Playback mode does not work with Windows authentication on SQL
2k/2k5.
Data Services Designer fails to parse a WSDL if a schema in
the WSDL types definition import/include schemas outside of
the WSDL. User will have to include all schemas in the WSDL
file.
You cannot use multi-level match sample transform configurations when you need to remove match criteria.
Data in Sample reports are not being displayed for ORACLE if
the source name is not populated.
Reports generated from Sybase calculate values in the report
incorrectly if the degree of parallelism is greater then 0.
URAC does not error out when producing a PS Form 3553 and
the Postcode2 is not output. The USPS requires that the updated ZIP+4 is posted after running US addresses through CASScertified software for the list to be considered valid for USPS
discounts. Ensure that the Postcode2 is posted when processing address records through the US Regulatory Address
Cleanse transform and a PS Form 3553 is required for mailing
purposes.
Adding a job schedule using BusinessObjects Enterprise XI
3.0 fails with error message "Server Input% not found or server
may be down".
Workaround:
Users attempting to access a BusinessObjects Enterprise
XI 3.0 system using BusinessObjects XI R2 SDK applications
may receive the following system message: "Err: "Server
Input% not found or server may be down".
This is caused by a change to the formatting of File Repository Server (FRS) names between the two versions. To resolve this issue, go to the Central Configuration Manager
and rename your Input FRS to Input.<host name>.fileserver
and Output FRS to Output.<hostname>.fileserver.
Data Services Release Notes 37
Known issues
5
Related Topics
• Migration considerations on page 23
• Resolved issues on page 25
38 Data Services Release Notes
Loading...