Xi31211 Ds Release Notes en

Data Services Release Notes
BusinessObjects Data Services XI 3.1 (12.1.1.0)

Copyright © 2008 Business Objects, an SAP company. All rights reserved. Business Objects
owns the following U.S. patents, which may cover products that are offered and
licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250;
5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698;
6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068;
6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189;
6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440;
7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and
its logos, BusinessObjects, Business Objects Crystal Vision, Business Process
On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications,
Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal
Vision, Desktop Intelligence, Inxight and its logos , 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. SAP is the trademark or registered
trademark of SAP AG in Germany and in several other countries. All other names
mentioned herein may be trademarks of their respective owners.
Third-party Business Objects products in this release may contain redistributions of software
Contributors 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-11-28
Contents
Chapter 1 About Data Services XI 3.1 5
Documentation set for Data Services..........................................................7
Business Objects information resources.....................................................9
Chapter 2 Compatibility and limitations update 13

Compatibility update..................................................................................14
Limitations update......................................................................................17
Chapter 3 Migration considerations 25
Chapter 4 Resolved issues 27
Chapter 5 Known issues 31
Data Services Release Notes 3

Contents
4 Data Services Release Notes

About Data Services XI 3.1
1
1 About Data Services XI 3.1
Documentation set for Data Services
Welcome to BusinessObjects Data Services XI 3.1, version 12.1.1. 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.
This version is a functional release that makes Data Services available on

UNIX and Linux in addition to Windows and also includes new features in
the following areas:
• Enterprise agility (ease of use)

• Trusted information
• Operational excellence
• Enterprise class
See the Data Services Release Summary for details about these key features.
Before installing your Business Objects software, read this entire document.
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 SAP Business
Objects Help Portal at (http://help.sap.com/) and follow the appropriate
product guide links.
Maintenance Installation
This version may be installed as a new instance of Data Services or may be
used as an update over an existing Data Services or Data Integrator instance
in the same installation directory. For a full installation, please follow the
instructions in your Data Services Installation Guide for Windows.
Note that for an installation over an existing version, Data Services will replace
the binaries of installed components and reuse the configurations that you
selected in the prior installation.
Related Topics
• Compatibility update on page 14
• Limitations update on page 17
• Migration considerations on page 25

Documentation set for Data Services 1
• Resolved issues on page 27
• Known issues on page 31

You should become familiar with all the pieces of documentation that relate
to your Data Services product.
Document What this document provides
Information about available Data Services books,

Documentation Map
languages, and locations
Highlights of key features in this Data Services re-

Release Summary
lease
Important information you need before installing and

Release Notes
deploying this version of Data Services
Getting Started Guide An introduction to Data Services
Information about and procedures for installing Data

Installation Guide for Windows
Services in a Windows environment.
Information about and procedures for installing Data

Installation Guide for UNIX
Services in a UNIX environment.
Guidelines and options for migrating applications in-

Advanced Development Guide cluding information on multi-user functionality and
the use of the central repository for version control
Designer Guide Information about how to use Data Services Designer
Information for third-party developers to access Data

Services functionality. Also provides information about
Integrator's Guide
how to install, configure, and use the Data Services
Adapter for JMS.
Management Console: Administrator Information about how to use Data Services Adminis-
Guide trator

Management Console: Metadata Re- Information about how to use Data Services Metadata
ports Guide Reports
Information about:
• Release-specific product behavior changes from
Migration Considerations Guide earlier versions of Data Services to the latest re-
lease
• How to migrate from Data Quality to Data Services
Information about how to improve the performance

Performance Optimization Guide
of Data Services
Detailed reference material for Data Services Design-

Reference Guide
er
A compiled “master” PDF of core Data Services books

containing a searchable master table of contents and
index:
• Getting Started Guide
• Installation Guide for Windows
• Installation Guide for UNIX
• Designer Guide
• Reference Guide
Technical Manuals • 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 A step-by-step introduction to using Data Services
In addition, you may need to refer to several Adapter Guides and

Supplemental Guides.

Business Objects information resources 1
Salesforce.com Adapter Information about how to install, configure, and use the Data
Interface Services Salesforce.com Adapter Interface
Supplement for J.D. Ed- Information about license-controlled interfaces between Data
wards Services and J.D. Edwards World and J.D. Edwards OneWorld
Supplement for Oracle Ap- Information about the license-controlled interface between Data
plications Services and Oracle Applications
Information about license-controlled interfaces between Data

Supplement for PeopleSoft
Services and PeopleSoft
Information about license-controlled interfaces between Data

Supplement for SAP
Services, SAP ERP, and SAP BI/BW
Information about the license-controlled interface between Data

Supplement for Siebel
Services and Siebel
Business Objects information resources

A global network of Business Objects technology experts provides customer
support, education, and consulting to ensure maximum business intelligence
benefit to your business.
Useful addresses at a glance:
Address Content

Address Content
Customer Support, Consulting, and Education Information about Customer Support programs,
services as well as links to technical articles, downloads,
and online forums. Consulting services can
http://service.sap.com/ provide you with information about how Busi-
ness Objects can help maximize your business
intelligence investment. Education services can
provide information about training options and
modules. From traditional classroom learning
to targeted e-learning seminars, Business Ob-
jects can offer a training package to suit your
learning needs and preferred learning style.
Data Services Community Get online and timely information about Data
Services, including tips and tricks, additional
https://www.sdn.sap.com/irj/sdn/businessob downloads, samples, and much more. All con-
jects-ds tent is to and from the community, so feel free
to join in and contact us if you have a submis-
sion.
Forums on SCN (SAP Community Network) Search the Business Objects forums on the
SAP Community Network to learn from other
https://www.sdn.sap.com/irj/sdn/businessob Data Services users and start posting questions
jects-forums or share your knowledge with the community.
Blueprints Blueprints for you to download and modify to fit
your needs. Each blueprint contains the neces-
http://www.sdn.sap.com/irj/boc/blueprints sary Data Services project, jobs, data flows, file
formats, sample data, template tables, and
custom functions to run the data flows in your
environment with only a few modifications.

Business Objects information resources 1
Address Content
Product documentation Business Objects product documentation.
http://help.sap.com/
Documentation mailbox Send us feedback or questions about your

Business Objects documentation. Do you have
documentation@businessobjects.com a suggestion on how we can improve our docu-
mentation? Is there something that you particu-
larly like or have found useful? Let us know,
and we will do our best to ensure that your
suggestion is considered for the next release
of our documentation.
Note:
If your issue concerns a Business Objects
product and not the documentation, please
contact our Customer Support experts.
Supported platforms documentation Get information about supported platforms for

Data Services.
https://service.sap.com/bosap-support
In the left panel of the window, navigate to
Documentation > Supported Platforms >
BusinessObjects XI 3.1. Click the Busines-
sObjects Data Services link in the main win-
dow.


Compatibility and limitations
update
2
2 Compatibility and limitations update
Compatibility update
For the latest detailed compatibility, availability, and limitations information,

see the Supported Platforms document at http://service.sap.com/.
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

Check the Supported Platforms document at http://service.sap.com/ for the
latest updates in compatibility.
• Data Services impact analysis interoperates with:
• BusinessObjects universes 6.5.1, XI, XI R2 SP2 or above, XI 3.0, XI
3.1
• Web Intelligence documents versions 6.5.1, XI, XI R2 SP2 or above,
XI 3.0, XI 3.1
• Desktop Intelligence documents versions 6.5.1, XI R2 SP2 or above,
XI 3.0, XI 3.1
• Business Views XI, XI R2 SP2 or above, XI 3.0, XI 3.1
Note:
Support for BusinessObjects Enterprise 6.5.1 is dependent on a valid
extended support agreement.
• The Data Services scheduling functionality is supported with
BusinessObjects Enterprise version XI R2 or later versions of the
BusinessObjects Enterprise scheduler.
• Data Services supports Data Insight 12.0 and 12.1.
• Data Services is compatible with the following Universe Builder versions:
• The stand-alone Universe Builder version 11.5 bundled with Data
Services 12.1.1. 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's Guide, which
you can download from the SAP Business Objects Help Portal at

Compatibility and limitations update
Compatibility update 2
http://help.sap.com/. Select BusinessObjects Enterprise as the product
and Universe Designer's Guide as the document.
• The Universe Builder version bundled with BusinessObjects Enterprise
XI R2, XI 3.0, and XI 3.1 supported versions.
Note:
Support for BusinessObjects Enterprise 6.5.1 is dependent on a valid
extended support agreement.
• 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.
As an example, 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):
1. In the OpenAccess configuration file (LINK_DIR\OaJd

bcBridge\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
Services\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
• Data Services supports DataDirect ODBC Drivers to access sources and

targets. If you want to connect from a UNIX or Linux job server to Microsoft
SQL Server for source and target access, you can download a DataDirect
Connect driver for this purpose from the Diamond technical community
at https://boc.sdn.sap.com/EIM. Check the Supported Platforms document
for versions of Data Direct ODBC drivers that are supported with this
release.

Included utilities
The following utilities are included with Data Services XI 3.1 to support Data
Quality address correction functionality.
Utility Description
ShowA Looks up address line information in the US address direc-
tories
ShowL Looks up lastline information in the US address directories
CaShowL Looks up address line information in the Canadian address
directories
Unsupported (deprecated) Business Objects functionality

The following functionality, which was available with Data Quality XI R2, is
no longer available in Data Services:
• Web Services: .Net Deployment
• Compound Transforms
• Shared options
• Unique ID Record Stem support in Candidate Selector
• Pre/Post SQL Operations in Reader transform
• Per Dataflow Mode in User-Defined transform (use workflow and scripts
instead)
• Enabling and disabling transforms in a dataflow
• Thread and watermark settings on a per-transform basis
• Observer transform
• Progress Service Transform
• Integrated batch API
• Admin methods in Message Client API
• JIS_Encoding, UTF-32 for flat files
• Python methods for User-Defined transform
• Generic Per Collection Mode Sort in Sorter transform
• DBASE3 file formats
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.

Limitations update 2
Related Topics
Limitations update
The following limitations apply to Data Services version 12.1.1.
Installation limitations
• If you are installing Data Services on the same machine as
BusinessObjects Enterprise XI 3.1, you must use Data Services XI 3.1
SP 1 (version 12.1.1) or above.
• When upgrading from Data Services XI 3.0 or XI 3.1 (version 12.0.0 or
12.1.0) to Data Services XI 3.1 SP 1 (version 12.1.1), you must first
uninstall Data Services and reboot the machine before installing Data
Services XI 3.1 SP1 (version 12.1.1) or above. If you have
BusinessObjects Enterprise on the same machine as Data Services,
please also refer to the known issues section before you uninstall Data
Services.
• When installing Data Services XI 3.1 SP1 (version 12.1.1) or above on
the same machine as BusinessObjects Enterprise XI 3.0, the option to
reuse the same Tomcat or MySQL instance as BusinessObjects Enterprise
is not available.
• When you install Data Services on the same machine as BusinessObjects
Enterprise and reuse the BusinessObjects Enterprise installed version of
MySQL or Tomcat, refer to the known issues section of these release
notes for important information before uninstalling Data Services or
BusinessObjects Enterprise.
• Data Services XI 3.1 cannot be installed in the same folder as
BusinessObjects Enterprise XI 3.0. During installation, select a different
installation location.
• If you have Data Services XI 3.0 version 12.0.0 installed, you must first
uninstall Data Services XI 3.0 version 12.0.0 prior to installing Data
Services XI 3.1 version 12.1.0 or later. After you uninstall 12.0.0, restart
your computer. If you are using a version of MySQL that is installed with
a previous version of Data Services, you must back up your database
before you uninstall Data Services. For details, see the Data Services
Installation Guide.
• If you have Data Services XI 3.0 on your system and that system also
has BusinessObjects Enterprise-installed version of MySQL, you must

Limitations update
complete the following backup and restore procedure for MySQL when
you upgrade from Data Services XI 3.0 to Data Services XI 3.1 or later.
1. Stop the BusinessObjects MySQL service (for example,
BOE120MySQL) from the Windows Component Services window.
2. Back up the MySql5 folder at the BusinessObjects Enterprise or
BusinessObjects Edge installation location, such as C:\Program
Files\Business Objects\MySql5.
3. Uninstall Data Services XI 3.0.
Note:
Do not reboot your machine at the conclusion of the Data Services
uninstall because the MySql5 folder will be corrupted as a result of
the Data Services uninstall.
4. Delete the corrupted MySql5 folder and replace it with the backup
copy of the MySql5 folder in the installation location.
5. Start the service from the Windows Component Services window. The
service should start successfully.
6. Reboot your system.
7. Install Data Services XI 3.1 or above.
8. Reboot your system.
• On UNIX and Linux, Data Services XI 3.1 or later cannot be installed in
the same folder as BusinessObjects Enterprise XI 3.0. During installation,
select a different installation location.
Other limitations
• As of version 12.1.0, Data Services no longer supports publishing a
real-time job as a Web service if the real-time job uses a DTD (Document
Type Definition) to define the input and output message.
• If you upgrade from version 12.0.0 to version 12.1.1, you do not need
to do anything unless you change the DTD, reimport it to the repository,
and publish the Web service.
• If you upgrade from Data Integrator 11.7 or earlier, you need to convert
the DTDs to XSDs (XML Schemas) using whatever available tool,
import the XSD as message formats, modify the data flows to use the
new XSD message formats, publish the real-time job as a Web service,
and reimport the service as a function in the Web Service datastore.
• Due to a vendor limitation with Oracle 10G, while running Data Services
on UNIX using Oracle Client on UNIX and Oracle Server on Windows,
the Oracle version must be 10.2.0.1 or higher.

• The 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 5.1
• When you use an Attunity Connector datastore, all Data Services features
are available except:
• Bulk loading
• Imported functions (imports metadata for tables only)
• Template tables (creating tables)
• 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:
• Data Services can read, load, and invoke stored procedures involving
unknown data types provided that your 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 if the native database does not support that
conversion.(for example, bulk loading or auto-correct load could fail).
Note:
Use varchar_to_long function to convert a VARCHAR datatype to a
LONG datatype before loading physical CLOB. If from a prior
installation, you are using a VARCHAR column in the physical schema
for loading, this will still work.
• Stored procedure support is implemented for DB2, Oracle, Microsoft SQL

Server, Sybase ASE, Sybase IQ, and ODBC only.
• Bulk loading data to DB2 databases running on z/OS or iSeries systems
is not supported.
• View Data is not supported for SAP ERP. For SAP ERP and PeopleSoft,
the Table Profile tab and Column Profile tab options are not supported
for hierarchies.
• Metadata values with multi-byte data are not supported by the Data
Cleanse rule file. Because of this restriction, the Designer and underlying

Limitations update
Universal Data Cleanse transform code does not support multi-byte values
for custom output categories, output fields, and classifications.
• Data Services supports multi-byte metadata for table names, column
names, file names, and file paths. The following table lists which sources
support multi-byte and single-byte metadata and which support single-byte
only:
Multi-byte and single-byte metada- Single-byte metadata supported

ta supported
• BusinessObjects Enterprise • Attunity connector for mainframe

• Data Federator databases
• DB2 • JD Edwards
• HP Neoview • Netezza
• Informix • Oracle Applications
• MySQL • PeopleTools
• ODBC • SAP ERP databases
• Oracle • SAP BI/BW server
• Siebel
• Microsoft SQL Server
• Sybase ASE
• Sybase IQ
• Teradata
• XML
Note:
Support for multi-byte metadata depends on comparable support in the
applications, databases, and technologies with which Data Services
interoperates.
• Support for Data Profiler is provided for sources as follows.

Data Profiler supported Data Profiler not supported
• Attunity Connector for mainframe • COBOL copybooks

databases • Excel
• DB2 • IDOC
• Data Federator • JD Edwards
• Flat file • Memory Datastore
• HP Neoview • SAP BI/BW
• Informix • XML
• MySQL
• Netezza
• ODBC
• Oracle
• Oracle Applications
• PeopleSoft
• SAP ERP
• Siebel
• Sybase ASE
• Sybase IQ
• Teradata
• Support for the LOOKUP_EXT function is provided for sources as follows.

Limitations update
LOOKUP_EXT supported LOOKUP_EXT not supported
• DB2 • COBOL copybook

• Data Federator • Excel
• Flat file • IDOC
• JD Edwards • SAP BI/BW
• HP Neoview • SAP ERP
• Memory Datastore • XML
• MySQL
• Netezza
• ODBC
• Oracle
• Oracle Applications
• PeopleSoft
• Persistent Cache
• Siebel
• Sybase ASE
• Sybase IQ
• Teradata
• 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
and XML files larger than 2 GB.
• 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 editor in Designer when the
large files are on a UNIX or Windows Job Server (on a different
machine than the Designer).
• 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.
• 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 12 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 to
point to Salesforce.com 12.0 API. The new URL should be:
https://www.salesforce.com/services/Soap/u/12.
• HP Neoview 2.3 support:
• ISO configuration: HP recommends that you use only the ISO column
(default). For data consistency, only one client code page should be
used.
• SJIS configuration: HP recommends that you use only the ISO column
(default). The data should be in SJIS.
• Unicode configuration: HP recommends that you use only the UCS2
column (default). The data can be in any code page.
Related Topics
• Compatibility update on page 14

Limitations update

Migration considerations
3
3 Migration considerations
See the Data Services Migration Considerations document, which is available

at Start > Programs > BusinessObjects XI 3.1 > BusinessObjects Data
Services > Documentation > Migration Considerations. You can also
check http://help.sap.com/ for documentation updates.
The Data Services Migration Considerations document includes two guides.

• Migration Considerations Guide: Describes behavior changes associated
with all supported versions of Data Integrator and Data Services.
• Data Quality to Data Services Migration Guide: Contains new features
and explains how to upgrade from previous Data Quality releases prior
to 12.0.0.
Installation and migration

Before you migrate, be sure you refer to the Limitations update section of
these Release Notes for important installation information about upgrading
from previous versions of Data Services (XI 3.0 or XI 3.1).
Related Topics
• Resolved issues on page 27
• Known issues on page 31

Resolved issues
4
4 Resolved issues
For the latest version of these release notes, see http://help.sap.com/, which
includes resolved issues specific to version 12.1.1. For details on issues
fixed in Data Integrator 11.7.3, 12.0.0, and 12.1.0, see the BusinessObjects
Data Integrator (11.7.3) and Data Services Release Notes (12.0.0 and 12.1.0).
The Issue ID numbers refer to the Business Objects Problem Report tracking
number and are listed in descending 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.
Issue ID Description
ADAPT01146336 A Data Services installation is not successful if OpenGL is not first installed
on your system. The installer displayed an error "invalid keycode". This issue
has been resolved by displaying the correct message in the case that OpenGL
is not installed.
ADAPT01146259 When you attempt to upgrade an older Data Integrator version's repository
to Data Services 12.0.0.0 or later, and one of the dataflows in the repository
contains a query whose output schema is empty, the upgrade will fail and a
message saying that the upgrading was cancelled will show up in the
repository manager console log. This issue has been resolved.
ADAPT01145123 Mismatch in JDK version causes broken Impact and Lineage links in Data
Services and Metadata Management. This issue has been resolved.
ADAPT01144091 When using a query with a WHERE clause longer than 200 characters in a
single line, the WHERE clause may not evaluate properly. This issue has
been resolved.
ADAPT01143492 Columns that have and empty string as data are loaded as NULL in the
Netezza target table, if the bulk load option is used. This issue has been re-
solved.
ADAPT01136670 The JRE was not installed as a part of the Designer component. As a result,
the profiler could not run properly. This issue has been resolved.
ADAPT01135530 A WSDL file could not be imported in the Designer. This WSDL file imports
another WSDL file. The WSDL parser in the Designer was unable to handle
this construction. This issue has been resolved.
ADAPT01135427 Match and UDT transforms do not save input field mappings if their input
pipe is from a Merge or Case transform. This issue has been resolved.

Resolved issues
4
ADAPT01135026 Data Services uses a two-level naming convention (for example, database-
name.Object-name) to reference Netezza tables. This results in an error if
the tables in a single Netezza datastore are imported from multiple Netezza
databases. This issue has been resolved.
ADAPT01133226 When you attempt to import a file format from a .fmt file and the file name
contains a hyphen, period, or other special character, the import operation
fails. This issue has been resolved.
ADAPT01132882 Data Services does not transcode a flat file in ISO-8859-5 to CP1251 correct-
ly. This issue has been resolved.
ADAPT01130616 When running a job with an XML reader with a DTD in which the root element
is defined as multiple occurences of its children, an Access violation error
occurs. This issue has been resolved.
ADAPT01133100 XML suggestion list data from Address Cleanse containing special XML
characters was not encoded correctly. This issue has been resolved.
ADAPT01123546 When a data flow has a DOP of more than 1 and contains a gen_row_num
function, the data flow generates incorrect output. This is caused by the
functions running in parallel because of the DOP setting. This issue has been
resolved.
ADAPT01123231 The engine did not generate the correct size for columns with varchar type
when using bulk loader with Teradata. Instead of the actual size of the col-
umn, the default value of 20 was used. This problem resulted in error "Data
item too large for field C1_ in vartext record number 1" when doing bulk
loading using mload. This issue has been resolved.
ADAPT01123144 The custom range option in the Data Services Excel worksheet feature may
not work properly if the cell has a two-character index, such as AB. This
problem has been resolved.
ADAPT01122729 Data Services Metadata Integrator for CMS fails for Universes or Reports
that have a description of more than 1000 characters. This issue has been
resolved.
ADAPT01122631 Loading data to an Oracle table using the CDC Map transform failed with
the error "ORA-01460: Unimplemented or unreasonable conversion request-
ed" when the loader option "Include in Transaction" was set to true. This issue
has been resolved.

4 Resolved issues
ADAPT01122625 The job server would hang occasionally when reading connection request
messages via the socket. This issue has been resolved.
ADAPT01122265 the check-in operation for Data Quality Project to central repository failed
with the following error: "BODI - 1260169 Could not find the object <ob-
ject_name> in the local repository." This issue has been resolved.
ADAPT01119152 When the Map_CDC_Operation transform was used with a DB2 loader with
the overflow option enabled, the loader did not commit the data loaded after
failed rows were written to the overflow file. This issue has been resolved.
ADAPT01116234 When migrating from Data Quality XI to Data Services, Data Quality XI binary
data types are not supported for fixed-width files. This issue has been re-
solved.
ADAPT01114793 Address Cleanse Sample Reports - Records with extended ASCII characters
are not being displayed for Oracle repositories. This issue has been resolved.
ADAPT01112785 When you delete a primary key column(s) of a table in the Designer, the
Designer might exit abnormally. This issue has been resolved.
ADAPT01112206 If the Expend occurs option is not selected when configuring a COBOL
Copybook, and if the Copybook has an Occurs field, Data Services extracts
data incorrectly. This issue has been resolved.
ADAPT01100158 When running a job that contains script functions, you might receive the fol-
lowing error: "Stack overflow has occurred". This issue has been resolved.
ADAPT01100152 When performing check-out or check-in operations with very large jobs to
an Oracle central repository, you might have encountered the Oracle error
"ORA-01795: maximum number of expressions in the list is 1000". This issue
has been resolved.
ADAPT01085674 On Linux, when running the Address Server with more than three threads,
there is a problem with handling all reference data (post native + UPU
countries). This issue has been resolved.
ADAPT01040190 If a Sybase IQ server is installed on an HP-UX Itanium machine and the job
server is on an HP-UX Itanium machine, and if the job was using Sybase IQ
as a reader or loader, temporary files created in /tmp/.SQLAnywhere were
not getting deleted after the completion of the job. This issue has been re-
solved.
ADAPT00980364 In HP-UX Itanium 64, jobs connecting to Sybase IQ would not release
semaphores even after disconnecting. This issue has been resolved.

Known issues
5
5 Known issues
This section lists known issues in descending order by Business Objects

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.

Known issues
5
Known installation issues
ADAPT01155032

5 Known issues
During Data Services installation, an SAP BusinessObjects Edge product
activation keycode may be incorrectly identified as an invalid keycode. The
cause is typically related to upgrading from one tier of the product to another
(for example, advancing from a Edge Professional level product to a Edge
Data Services level product) or reaching the processor or user account limits
implied by the keycode.
The problem will typically be encountered during a version upgrade
scenario or some other form of reinstallation, and can be seen in both
Windows and UNIX installations. You will receive an invalid keycode error
message.
Solution
If you believe that your keycodes are fully valid and continue to encounter
this problem, we suggest launching the License Manager product directly
from the installation media. From the License Manager, you should be
able to remove the keycodes that are creating the problem and proceed
with installation.
Windows
1. Exit out of the installation. Navigate within the installation media to
package\Utilities\KeyDecoder and launch the LicenseManager.exe
application within that directory.
2. From the Registered Keycodes section of the application, navigate to
SAP BusinessObjects Edge > XI 3.x and record all keycodes displayed
in this section.
3. Saving the keycodes and remove each keycode in this area.
4. Save and Close the application.
Now you can restart the installation and provide your valid product acti-
vation keycode.
Unix
1. On UNIX, the environment variable BOE_REGISTRYHOME must first
be set. This should be set to a path including the installation directory
and the subdirectory dataservices/registry.
2. If using Bourne shell and the installation directory chosen is /usr/lo
cal/businessobjects, execute the following command:
BOE_REGISTRYHOME=/usr/local/businessobjects/dataser

Known issues
5
vices/registry ; export BOE_REGISTRYHOME
3. Navigate within the installation media to setup/utilities/license/.

In this directory, you will find the LicenseManager executable.
• If X Windows is available, simply launch the executable and follow
the instructions laid out above for Windows users.
• If X Windows is not available, you will be required to remove each
keycode within the SAP BusinessObjects Edge > XI 3.x section.
To do so, run LicenseManager -r <keycode> for each 26-char-
acter product activation keycode listed by the application in the
BusinessObjects Edge area. Once these steps are completed,
installation can be resumed.
In both cases, after installation is complete, you should be able to use

the License Manager to add back in any keycodes that would be needed
to enable further functionality.

5 Known issues
ADAPT01153442 If you install Data Services XI 3.0, 3.1 or 3.1 SP1 (versions 12.0.0, 12.1.0,
or 12.1.1) and share the BusinessObjects Enterprise-installed version of
MySQL, when you uninstall BusinessObjects Enterprise, MySQL will be re-
moved and the Data Services operations related to the MySQL repository
will not function. Examples of Data Services operations which will not work
are those associated with the Data Services Designer and Data Services
Management Console.
You must backup of the Data Services configuration files and the MySQL
repository and then you must restore Data Services. We highly recom-
mended that these steps are followed before you uninstall BusinessOb-
jects Enterprise. The backup and restore steps are:
1. Back up the Data Services configuration file %LINK_DIR%/bin/DSCon-
fig.txt.
2. Back up the MySql5\data folder at the BusinessObjects Enterprise instal-
lation location, such as C:\ProgramFiles\Business Objects\MySql5.
3. Uninstall the existing Data Services version. Reboot the machine.
4. Do the clean install of Data Services with the new MySQL instance (use
the same port number and Data Services database name as before).
5. After installation, stop the Data Services service and BusinessObjects
MySQL service (for example, BOE120MySQL) from the Windows Com-
ponent Services window.
6. Replace the MySQL folder with the backed-up MySQL folder.
7. Replace the DSConfig.txt file with the backed-up DSConfig.txt file.
8. Start the Data Services service and the BusinessObjects MySQL instance.
Note:
If you did not backup the Data Services configuration files and the MySQL
repository before you uninstalled BusinessObjects, you can still back them
up and then start from Step 3 above.
For the latest update on backup and restore procedures, refer to SAP
note 1274989 in the SAP Service Marketplace. The note can be accessed
at https://service.sap.com/sap/support/notes/1274989.
ADAPT01153440

Known issues
5
When you uninstall Data Services, the MySqlAdmin5 folder that contains
the MySQL administration utilities will also be uninstalled. This can cause
problems for a particular scenario where you have an instance of Busi-
nessObjects Enterprise that reuses the instance of MySQL that was in-
stalled by Data Services.
To work around this issue:

• Before uninstalling Data Services, back up the MySqlAdmin5 folder at
the BusinessObjects Enterprise installation location, such as C:\Program-
Files\Business Objects\MySqlAdmin5.
• Restore the MySQLAdmin5 folder to it's prior location.
For the latest update, refer to SAP note 1274995 in the SAP Service
Marketplace. The note can be accessed at https://ser
vice.sap.com/sap/support/notes/1274995.
ADAPT01142551
Multiple Data Services installations on the same Linux or UNIX machines
cannot run the Address Server at the same time. To resolve this, you
need to edit the AddressserverConfig.txt file in the $LINK_DIR/bin/ad-
dress_server directory to change the port numbers. For example:
ADDRESS_SERVER_CNT_PORT = 40010
ADDRESS_SERVER_APP_PORT = 40011

5 Known issues
ADAPT01136144 When installing the Swiss cleansing package through Repository Manager
with DB2, the unzip process crashes. If you want to use the Swiss cleansing
package, use a different database.
ADAPT01123319 When you install BusinessObjects Enterprise XI 3.1 on the same machine
as an existing Data Services XI 3.1 SP1 (version 12.1.1) instance and reuse
the Data Services-installed version of Tomcat, uninstalling Data Services
will prevent BusinessObjects Enterprise Tomcat web applications from
starting.
To fix the issue, you must perform a "modify install" to reinstall Busines-
sObjects Enterprise. For detailed information on the BusinessObjects
Enterprise modify install option, refer to SAP note 1274978 in the SAP
Service Marketplace. The note can be accessed at https://ser
vice.sap.com/sap/support/notes/1274978.
ADAPT01113280 When installing cleansing packages through Repository Manager, the unzip
utility cannot unzip compressed files larger than 2 GB on Solaris, AIX, and
Linux. This issue only affects Universal Data Cleanse dictionaries for DB2.
To work around this, use the Repository Manager on Windows.
Other known issues
ADAPT01151623 When using the Metadata Exchange functionality or creating a new Busi-
ness Objects Universe using a source datastore that defines an alias, any
changes to the alias value may be lost in the resulting CWM, ERWin, or
Business Objects Universe. To workaround this issue, export the source
datastore to an ATL file, import the ATL to a new Data Services 12.1.0
repository, then perform the Metadata Exchange or Business Objects
Universe creation operation from the new repository.
ADAPT01149810 When you use multiple outer joins in the same query to a MySQL source,
you will get a MySQL syntax error on LEFT OUTER JOIN. This issue is
due a bug in MySQL ODBC driver with ODBC Outer left join syntax.
ADAPT01145535 Match - UniqueID - Error issued when using the GUID option on Linux. To
correct this problem, deselect this option and use one of the other UniqueID
options .

Known issues
5
ADAPT01144373 USA Regulatory Address Cleanse transform - 100 unique record minimum
error is inconsistently incorrectly generated for jobs where Degree of par-
allelism is greater than one. To correct this problem, reduce the Degree of
parallelism value.
ADAPT01113239 When using domain/userid as login for DB2, the existing Data Cleanse
repository is not detected. In this scenario, remove your Data Cleanse
repository before updating.
ADAPT01112105 The Address Server does not support Locality2 aliases. This affects New
Zealand, Hong Kong, Mexico, Ukraine, and South Africa.
ADAPT01109755 Inconsistent LACSLink/DPV Directory initialization errors when Degree of
parallelism is greater than four. To correct this problem, reduce the Degree
of parallelism value.
ADAPT01103044 MySQL case-insensitive collation causes some false matches with Dictio-
nary Encryption Algorithm for Universal Data Cleanse.
ADAPT01099928 USA Regulatory Address Cleanse PSForm 3553 report has formatting is-
sues when generating the report on AIX. Two workarounds are to purchase
the Arial font and copy the files into the JRE (Java Runtime Environment)
path of the Data Services installation (located at <installation_direc
tory>/bobje/jdk/jre/lib/fonts), or to remove the Thonburi and
Courier fonts from the Data Services JRE path. This forces Data Services
to use the Lucida family fonts, which display correctly. After either
workaround, you must restart your application server.
ADAPT00994274 The Compare To Object functionality does not always work correctly for
Data Quality transform configurations.
ADAPT00959986 Sybase ASE is not a supported database for Universal Data Cleanse
cleansing packages.
ADAPT00893920 When running the Data Quality Migration utility, an error occurs indicating
that Crypto.dll was not found. To run the Data Quality migration utility
successfully, add %LINK_DIR%\bin to your PATH environment variable.
ADAPT00857445 The option names that you see in Match error messages may not match
the actual option name.

5 Known issues
ADAPT00620063 When comparison tables are on Microsoft SQL Server, the Table Compar-
ison transform's Sorted input option generates incorrect results. The Data
Services 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 ad-
dressed in a later release. Use the Row-by-row select or Cached compar-
ison table option in the Table Comparison transform.
English cleansing package

Due to the discovery of discrepancies such as conflicting regionalisms in the
English 2.2 Cleansing Package that shipped with Data Services XI 3.1, we
highly recommend using the English 2.2.1 Cleansing Package, which ships
with this Data Services 3.1 Service Pack 1 (12.1.1) release.

Xi31211 Ds Release Notes en

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Xi31211 Ds Release Notes en

Hochgeladen von

Copyright:

Verfügbare Formate

Data Services Release Notes

BusinessObjects Data Services XI 3.1 (12.1.1.0)

Chapter 2 Compatibility and limitations update 13

Chapter 3 Migration considerations 25

Chapter 4 Resolved issues 27

Chapter 5 Known issues 31

Data Services Release Notes 3

4 Data Services Release Notes

Welcome to BusinessObjects Data Services XI 3.1, version 12.1.1. Data

This version is a functional release that makes Data Services available on

• Enterprise agility (ease of use)

To obtain the latest version of Data Services documentation including the

6 Data Services Release Notes

Documentation set for Data Services

Document What this document provides

Information about available Data Services books,

Highlights of key features in this Data Services re-

Important information you need before installing and

Getting Started Guide An introduction to Data Services

Information about and procedures for installing Data

Information about and procedures for installing Data

Guidelines and options for migrating applications in-

Designer Guide Information about how to use Data Services Designer

Information for third-party developers to access Data

Data Services Release Notes 7

Document What this document provides

Information about how to improve the performance

Detailed reference material for Data Services Design-

A compiled “master” PDF of core Data Services books

Tutorial A step-by-step introduction to using Data Services

In addition, you may need to refer to several Adapter Guides and

8 Data Services Release Notes

Information about license-controlled interfaces between Data

Information about license-controlled interfaces between Data

Information about the license-controlled interface between Data

Business Objects information resources

Useful addresses at a glance:

Data Services Release Notes 9

10 Data Services Release Notes

Documentation mailbox Send us feedback or questions about your

Supported platforms documentation Get information about supported platforms for

Data Services Release Notes 11

12 Data Services Release Notes

For the latest detailed compatibility, availability, and limitations information,

Interoperability with other Business Objects products

14 Data Services Release Notes

As an example, make the following modifications (where Data Federator

1. In the OpenAccess configuration file (LINK_DIR\OaJd

• Data Services supports DataDirect ODBC Drivers to access sources and

Data Services Release Notes 15

Unsupported (deprecated) Business Objects functionality

16 Data Services Release Notes

Data Services Release Notes 17

18 Data Services Release Notes

• Stored procedure support is implemented for DB2, Oracle, Microsoft SQL

Data Services Release Notes 19

Multi-byte and single-byte metada- Single-byte metadata supported

• BusinessObjects Enterprise • Attunity connector for mainframe

20 Data Services Release Notes

• Attunity Connector for mainframe • COBOL copybooks

• Support for the LOOKUP_EXT function is provided for sources as follows.

Data Services Release Notes 21