xi31211 ds release notes en

Data Services Release Notes

BusinessObjects Data Services XI 3.1 (12.1.1.0)

© 2008 Business Objects, an SAP company. All rights reserved. Business Objectsowns the following U.S. patents, which may cover products that are offered and

Copyright

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 andits logos, BusinessObjects, Business Objects Crystal Vision, Business ProcessOn Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications,Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, CrystalVision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, TableLens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts,RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius aretrademarks or registered trademarks in the United States and/or other countriesof Business Objects and/or affiliated companies. SAP is the trademark or registeredtrademark of SAP AG in Germany and in several other countries. All other namesmentioned herein may be trademarks of their respective owners.

Business Objects products in this release may contain redistributions of softwarelicensed from third-party contributors. Some of these individual components may

Third-partyContributors

also be available under alternative licenses. A partial listing of third-partycontributors that have requested or permitted acknowledgments, as well as requirednotices, can be found at: http://www.businessobjects.com/thirdparty

2008-11-28

ContentsAbout Data Services XI 3.1 5Chapter 1

Documentation set for Data Services..........................................................7Business Objects information resources.....................................................9

Compatibility and limitations update 13Chapter 2

Compatibility update..................................................................................14Limitations update......................................................................................17

Migration considerations 25Chapter 3

Resolved issues 27Chapter 4

Known issues 31Chapter 5

Data Services Release Notes 3

4 Data Services Release Notes

Contents

About Data Services XI 3.1

1

Welcome to BusinessObjects Data Services XI 3.1, version 12.1.1. DataServices combines industry-leading data quality and integration into oneplatform. With Data Services, your organization can transform and improvedata 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 onUNIX and Linux in addition to Windows and also includes new features inthe 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 includinginstallation 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 themost up-to-date version of these Release Notes, visit the SAP BusinessObjects Help Portal at (http://help.sap.com/) and follow the appropriateproduct guide links.

Maintenance Installation

This version may be installed as a new instance of Data Services or may beused as an update over an existing Data Services or Data Integrator instancein the same installation directory. For a full installation, please follow theinstructions in your Data Services Installation Guide for Windows.

Note that for an installation over an existing version, Data Services will replacethe binaries of installed components and reuse the configurations that youselected in the prior installation.

Related Topics• Compatibility update on page 14• Limitations update on page 17• Migration considerations on page 25


About Data Services XI 3.11 Documentation set for Data Services

http://help.sap.com/

• Resolved issues on page 27• Known issues on page 31

Documentation set for Data ServicesYou should become familiar with all the pieces of documentation that relateto your Data Services product.

What this document providesDocument

Information about available Data Services books,languages, and locationsDocumentation Map

Highlights of key features in this Data Services re-leaseRelease Summary

Important information you need before installing anddeploying this version of Data ServicesRelease Notes

An introduction to Data ServicesGetting Started Guide

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

Information about and procedures for installing DataServices in a UNIX environment.Installation Guide for UNIX

Guidelines and options for migrating applications in-cluding information on multi-user functionality andthe use of the central repository for version control

Advanced Development Guide

Information about how to use Data Services DesignerDesigner Guide

Information for third-party developers to access DataServices functionality. Also provides information abouthow to install, configure, and use the Data ServicesAdapter for JMS.

Integrator's Guide

Information about how to use Data Services Adminis-trator

Management Console: AdministratorGuide


1About Data Services XI 3.1Documentation set for Data Services


Information about how to use Data ServicesMetadataReports

Management Console: Metadata Re-ports Guide

Information about:• Release-specific product behavior changes from

earlier versions of Data Services to the latest re-lease

• How tomigrate fromData Quality to Data Services

Migration Considerations Guide

Information about how to improve the performanceof Data ServicesPerformance Optimization Guide

Detailed reference material for Data Services Design-erReference Guide

A compiled “master” PDF of core Data Services bookscontaining a searchable master table of contents andindex:• Getting Started Guide• Installation Guide for Windows• Installation Guide for UNIX• 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

Technical Manuals

A step-by-step introduction to using Data ServicesTutorial

In addition, you may need to refer to several Adapter Guides andSupplemental Guides.


About Data Services XI 3.11 Documentation set for Data Services


Information about how to install, configure, and use the DataServices Salesforce.com Adapter Interface

Salesforce.com AdapterInterface

Information about license-controlled interfaces between DataServices and J.D. Edwards World and J.D. Edwards OneWorld

Supplement for J.D. Ed-wards

Information about the license-controlled interface between DataServices and Oracle Applications

Supplement for Oracle Ap-plications

Information about license-controlled interfaces between DataServices and PeopleSoftSupplement for PeopleSoft

Information about license-controlled interfaces between DataServices, SAP ERP, and SAP BI/BWSupplement for SAP

Information about the license-controlled interface between DataServices and SiebelSupplement for Siebel

Business Objects information resourcesA global network of Business Objects technology experts provides customersupport, education, and consulting to ensure maximum business intelligencebenefit to your business.

Useful addresses at a glance:

ContentAddress


1About Data Services XI 3.1Business Objects information resources

ContentAddress

Information about Customer Support programs,as well as links to technical articles, downloads,and online forums. Consulting services canprovide you with information about how Busi-ness Objects can help maximize your businessintelligence investment. Education services canprovide information about training options andmodules. From traditional classroom learningto targeted e-learning seminars, Business Ob-jects can offer a training package to suit yourlearning needs and preferred learning style.

Customer Support, Consulting, and Educationservices

http://service.sap.com/

Get online and timely information about DataServices, including tips and tricks, additionaldownloads, samples, and much more. All con-tent is to and from the community, so feel freeto join in and contact us if you have a submis-sion.

Data Services Community

https://www.sdn.sap.com/irj/sdn/businessobjects-ds

Search the Business Objects forums on theSAP Community Network to learn from otherData Services users and start posting questionsor share your knowledge with the community.

Forums on SCN (SAP Community Network)

https://www.sdn.sap.com/irj/sdn/businessobjects-forums

Blueprints for you to download and modify to fityour needs. Each blueprint contains the neces-sary Data Services project, jobs, data flows, fileformats, sample data, template tables, andcustom functions to run the data flows in yourenvironment with only a few modifications.

Blueprints

http://www.sdn.sap.com/irj/boc/blueprints


About Data Services XI 3.11 Business Objects information resources

http://www.service.sap.com/





http://www.sdn.sap.com/irj/boc/blueprints

ContentAddress

Business Objects product documentation.Product documentation


Send us feedback or questions about yourBusiness Objects documentation. Do you havea 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 yoursuggestion is considered for the next releaseof our documentation.

Note:If your issue concerns a Business Objectsproduct and not the documentation, pleasecontact our Customer Support experts.

Documentation mailbox

[email protected]

Get information about supported platforms forData Services.

In the left panel of the window, navigate toDocumentation > Supported Platforms >BusinessObjects XI 3.1. Click the Busines-sObjects Data Services link in the main win-dow.

Supported platforms documentation

https://service.sap.com/bosap-support


1About Data Services XI 3.1Business Objects information resources


mailto:[email protected]

https://service.sap.com/bosap-support


About Data Services XI 3.11 Business Objects information resources

Compatibility and limitationsupdate

2

For the latest detailed compatibility, availability, and limitations information,see the Supported Platforms document at http://service.sap.com/.

Compatibility updateThis 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 thelatest 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 validextended support agreement.

• The Data Services scheduling functionality is supported withBusinessObjects Enterprise version XI R2 or later versions of theBusinessObjects 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 DataServices 12.1.1. This stand-alone version of Universe Builder willinteroperate with BusinessObjects version 6.5.1 and XI. Find UniverseBuilder documentation in the "Building Universes from Data IntegratorMetadata Sources" chapter of the Universe Designer's Guide, whichyou can download from the SAP Business Objects Help Portal at


Compatibility and limitations update2 Compatibility update



http://help.sap.com/. Select BusinessObjects Enterprise as the productand Universe Designer's Guide as the document.

• The Universe Builder version bundled with BusinessObjects EnterpriseXI R2, XI 3.0, and XI 3.1 supported versions.

Note:Support for BusinessObjects Enterprise 6.5.1 is dependent on a validextended support agreement.

• Data Services and Data Federator support Java Virtual Machine forversion compatibility.

To access Data Federator data sources with Data Services, you mustmodify your OpenAccess environment to use the Java Virtual Machinethat ships with Data Services. Data Federator installs a component calledOpenAccess ODBC to JDBC Bridge that requires these modifications.

As an example, make the following modifications (where Data Federatoris installed in D:\Program Files\Business Objects\BusinessObjects DataFederator 12, Data Services is installed in D:\ProgramFiles\BusinessObjects XI 3.0\BusinessObjects Data Services, andOpenAccess is installed in D:\Program Files\OaJdbcBridge):

1. In the OpenAccess configuration file (LINK_DIR\OaJdbcBridge\bin\iwinnt\openrda.ini), the path for the JVM must bechanged from JVM_DLL_NAME=D:\Program Files\BusinessObjects\BusinessObjects Data Federator12\jre\bin\client\jvm.dll to JVM_DLL_NAME=D:\ProgramFiles\BusinessObjects XI 3.0\BusinessObjects DataServices\ext\Jre\Bin\client\jvm.dll.

2. Add the following OpenAccess jar files to the CLASSPATHenvironment variable:• D:\ProgramFiles\OaJdbcBridge\jdbc\thindriver.jar

• D:\ProgramFiles\OaJdbcBridge\oajava\oasql.jar

• Data Services supports DataDirect ODBC Drivers to access sources andtargets. If you want to connect from a UNIX or Linux job server to MicrosoftSQL Server for source and target access, you can download a DataDirectConnect driver for this purpose from the Diamond technical communityat https://boc.sdn.sap.com/EIM. Check theSupported Platforms documentfor versions of Data Direct ODBC drivers that are supported with thisrelease.


2Compatibility and limitations updateCompatibility update


https://boc.sdn.sap.com/EIM

Included utilities

The following utilities are included with Data Services XI 3.1 to support DataQuality address correction functionality.

DescriptionUtility

Looks up address line information in the US address direc-tories

ShowA

Looks up lastline information in the US address directoriesShowL

Looks up address line information in the Canadian addressdirectories

CaShowL

Unsupported (deprecated) Business Objects functionality

The following functionality, which was available with Data Quality XI R2, isno 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 XIR2 Accelerated, is no longer available:• Log-based changed-data capture (CDC) with IBMDB2 UDB forWindows,

z/OS, IMS/DB, and IBM VSAM.


Compatibility and limitations update2 Compatibility update

Related Topics• Limitations update on page 17

Limitations updateThe 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.1SP 1 (version 12.1.1) or above.

• When upgrading from Data Services XI 3.0 or XI 3.1 (version 12.0.0 or12.1.0) to Data Services XI 3.1 SP 1 (version 12.1.1), you must firstuninstall Data Services and reboot the machine before installing DataServices XI 3.1 SP1 (version 12.1.1) or above. If you haveBusinessObjects Enterprise on the same machine as Data Services,please also refer to the known issues section before you uninstall DataServices.

• When installing Data Services XI 3.1 SP1 (version 12.1.1) or above onthe same machine as BusinessObjects Enterprise XI 3.0, the option toreuse the same Tomcat or MySQL instance as BusinessObjects Enterpriseis not available.

• When you install Data Services on the samemachine as BusinessObjectsEnterprise and reuse the BusinessObjects Enterprise installed version ofMySQL or Tomcat, refer to the known issues section of these releasenotes for important information before uninstalling Data Services orBusinessObjects Enterprise.

• Data Services XI 3.1 cannot be installed in the same folder asBusinessObjects Enterprise XI 3.0. During installation, select a differentinstallation location.

• If you have Data Services XI 3.0 version 12.0.0 installed, you must firstuninstall Data Services XI 3.0 version 12.0.0 prior to installing DataServices XI 3.1 version 12.1.0 or later. After you uninstall 12.0.0, restartyour computer. If you are using a version of MySQL that is installed witha previous version of Data Services, you must back up your databasebefore you uninstall Data Services. For details, see the Data ServicesInstallation Guide.

• If you have Data Services XI 3.0 on your system and that system alsohas BusinessObjects Enterprise-installed version of MySQL, you must


2Compatibility and limitations updateLimitations update

complete the following backup and restore procedure for MySQL whenyou 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:\ProgramFiles\Business Objects\MySql5.

3. Uninstall Data Services XI 3.0.

Note:Do not reboot your machine at the conclusion of the Data Servicesuninstall because the MySql5 folder will be corrupted as a result ofthe Data Services uninstall.

4. Delete the corrupted MySql5 folder and replace it with the backupcopy of the MySql5 folder in the installation location.

5. Start the service from theWindows Component Services window. Theservice 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 inthe 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 aWeb service if the real-time job uses a DTD (DocumentType 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 convertthe DTDs to XSDs (XML Schemas) using whatever available tool,import the XSD as message formats, modify the data flows to use thenew XSDmessage formats, publish the real-time job as aWeb service,and reimport the service as a function in the Web Service datastore.

• Due to a vendor limitation with Oracle 10G, while running Data Serviceson UNIX using Oracle Client on UNIX and Oracle Server on Windows,the Oracle version must be 10.2.0.1 or higher.


Compatibility and limitations update2 Limitations update

• The Data Services log-based changed-data capture (CDC) works withthe following database versions:• Oracle version 9.2 and above compatible versions for synchronous

CDC and Oracle version 10G and above compatible version forasynchronous 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 featuresare 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 convertfrom 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 physicalCLOB column if the native database does not support thatconversion.(for example, bulk loading or auto-correct load could fail).

Note:Use varchar_to_long function to convert a VARCHAR datatype to aLONG datatype before loading physical CLOB. If from a priorinstallation, you are using a VARCHAR column in the physical schemafor loading, this will still work.

• Stored procedure support is implemented for DB2, Oracle, Microsoft SQLServer, Sybase ASE, Sybase IQ, and ODBC only.

• Bulk loading data to DB2 databases running on z/OS or iSeries systemsis 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 supportedfor hierarchies.

• Metadata values with multi-byte data are not supported by the DataCleanse rule file. Because of this restriction, the Designer and underlying



Universal Data Cleanse transform code does not support multi-byte valuesfor custom output categories, output fields, and classifications.

• Data Services supports multi-byte metadata for table names, columnnames, file names, and file paths. The following table lists which sourcessupport multi-byte and single-byte metadata and which support single-byteonly:

Single-byte metadata supportedMulti-byte and single-bytemetada-ta supported

• Attunity connector for mainframedatabases

• JD Edwards• Netezza• Oracle Applications• PeopleTools• SAP ERP databases• SAP BI/BW server

• BusinessObjects Enterprise• Data Federator• DB2• HP Neoview• Informix• MySQL• ODBC• Oracle• Siebel• Microsoft SQL Server• Sybase ASE• Sybase IQ• Teradata• XML

Note:Support for multi-byte metadata depends on comparable support in theapplications, databases, and technologies with which Data Servicesinteroperates.

• Support for Data Profiler is provided for sources as follows.



Data Profiler not supportedData Profiler supported

• COBOL copybooks• Excel• IDOC• JD Edwards• Memory Datastore• SAP BI/BW• XML

• Attunity Connector for mainframedatabases

• DB2• Data Federator• Flat file• HP Neoview• Informix• Microsoft SQL Server• 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.



LOOKUP_EXT not supportedLOOKUP_EXT supported

• COBOL copybook• Excel• IDOC• SAP BI/BW• SAP ERP• XML

• DB2• Data Federator• Flat file• JD Edwards• HP Neoview• Memory Datastore• Microsoft SQL Server• 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 configurationfiles, are limited to 2 GB. Data Services supports files greater than 2 GBonly 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 differentmachine 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 datatype 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 theMySQL ODBC library.

• The Data Services Salesforce.com adapter can connect to theSalesforce.com version 12 API; however, the new functionality added inAPI version 7 and above is not supported. The custom lookup field is theonly exception (new in API version 7) and is supported in theSalesforce.com adapter. To ensure that your existing Salesforce.comadapter works properly, you must update the URL in the datastore topoint 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 beused.

• 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 UCS2column (default). The data can be in any code page.

Related Topics• Compatibility update on page 14



https://www.salesforce.com/services/Soap/u/12

Migration considerations

3

See theData Services Migration Considerations document, which is availableat Start > Programs > BusinessObjects XI 3.1 > BusinessObjects DataServices > Documentation > Migration Considerations. You can alsocheck http://help.sap.com/ for documentation updates.

The Data Services Migration Considerations document includes two guides.

• Migration Considerations Guide:Describes behavior changes associatedwith all supported versions of Data Integrator and Data Services.

• Data Quality to Data Services Migration Guide: Contains new featuresand explains how to upgrade from previous Data Quality releases priorto 12.0.0.

Installation and migration

Before you migrate, be sure you refer to the Limitations update section ofthese Release Notes for important installation information about upgradingfrom previous versions of Data Services (XI 3.0 or XI 3.1).

Related Topics• Limitations update on page 17• Resolved issues on page 27• Known issues on page 31


Migration considerations3


Resolved issues

4

For the latest version of these release notes, see http://help.sap.com/, whichincludes resolved issues specific to version 12.1.1. For details on issuesfixed in Data Integrator 11.7.3, 12.0.0, and 12.1.0, see the BusinessObjectsData 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 trackingnumber and are listed in descending order. We also use these numbers inthe release notes that accompany our fix packs and patches. You canreference the tracking number when searching for the issue on our knowledgebase or when speaking to Customer Assurance.

DescriptionIssue ID

A Data Services installation is not successful if OpenGL is not first installedon your system. The installer displayed an error "invalid keycode". This issuehas been resolved by displaying the correct message in the case that OpenGLis not installed.

ADAPT01146336

When you attempt to upgrade an older Data Integrator version's repositoryto Data Services 12.0.0.0 or later, and one of the dataflows in the repositorycontains a query whose output schema is empty, the upgrade will fail and amessage saying that the upgrading was cancelled will show up in therepository manager console log. This issue has been resolved.

ADAPT01146259

Mismatch in JDK version causes broken Impact and Lineage links in DataServices and Metadata Management. This issue has been resolved.

ADAPT01145123

When using a query with a WHERE clause longer than 200 characters in asingle line, the WHERE clause may not evaluate properly. This issue hasbeen resolved.

ADAPT01144091

Columns that have and empty string as data are loaded as NULL in theNetezza target table, if the bulk load option is used. This issue has been re-solved.

ADAPT01143492

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.

ADAPT01136670

A WSDL file could not be imported in the Designer. This WSDL file importsanother WSDL file. The WSDL parser in the Designer was unable to handlethis construction. This issue has been resolved.

ADAPT01135530

Match and UDT transforms do not save input field mappings if their inputpipe is from a Merge or Case transform. This issue has been resolved.

ADAPT01135427


Resolved issues4


DescriptionIssue ID

Data Services uses a two-level naming convention (for example, database-name.Object-name) to reference Netezza tables. This results in an error ifthe tables in a single Netezza datastore are imported from multiple Netezzadatabases. This issue has been resolved.

ADAPT01135026

When you attempt to import a file format from a .fmt file and the file namecontains a hyphen, period, or other special character, the import operationfails. This issue has been resolved.

ADAPT01133226

Data Services does not transcode a flat file in ISO-8859-5 to CP1251 correct-ly. This issue has been resolved.

ADAPT01132882

When running a job with an XML reader with a DTD in which the root elementis defined as multiple occurences of its children, an Access violation erroroccurs. This issue has been resolved.

ADAPT01130616

XML suggestion list data from Address Cleanse containing special XMLcharacters was not encoded correctly. This issue has been resolved.

ADAPT01133100

When a data flow has a DOP of more than 1 and contains a gen_row_numfunction, the data flow generates incorrect output. This is caused by thefunctions running in parallel because of the DOP setting. This issue has beenresolved.

ADAPT01123546

The engine did not generate the correct size for columns with varchar typewhen 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 "Dataitem too large for field C1_ in vartext record number 1" when doing bulkloading using mload. This issue has been resolved.

ADAPT01123231

The custom range option in the Data Services Excel worksheet feature maynot work properly if the cell has a two-character index, such as AB. Thisproblem has been resolved.

ADAPT01123144

Data Services Metadata Integrator for CMS fails for Universes or Reportsthat have a description of more than 1000 characters. This issue has beenresolved.

ADAPT01122729

Loading data to an Oracle table using the CDC Map transform failed withthe error "ORA-01460: Unimplemented or unreasonable conversion request-ed" when the loader option "Include in Transaction" was set to true. This issuehas been resolved.

ADAPT01122631


4Resolved issues

DescriptionIssue ID

The job server would hang occasionally when reading connection requestmessages via the socket. This issue has been resolved.

ADAPT01122625

the check-in operation for Data Quality Project to central repository failedwith the following error: "BODI - 1260169 Could not find the object <ob-ject_name> in the local repository." This issue has been resolved.

ADAPT01122265

When the Map_CDC_Operation transform was used with a DB2 loader withthe overflow option enabled, the loader did not commit the data loaded afterfailed rows were written to the overflow file. This issue has been resolved.

ADAPT01119152

Whenmigrating from Data Quality XI to Data Services, Data Quality XI binarydata types are not supported for fixed-width files. This issue has been re-solved.

ADAPT01116234

Address Cleanse Sample Reports - Records with extended ASCII charactersare not being displayed for Oracle repositories. This issue has been resolved.

ADAPT01114793

When you delete a primary key column(s) of a table in the Designer, theDesigner might exit abnormally. This issue has been resolved.

ADAPT01112785

If the Expend occurs option is not selected when configuring a COBOLCopybook, and if the Copybook has an Occurs field, Data Services extractsdata incorrectly. This issue has been resolved.

ADAPT01112206

When running a job that contains script functions, you might receive the fol-lowing error: "Stack overflow has occurred". This issue has been resolved.

ADAPT01100158

When performing check-out or check-in operations with very large jobs toan Oracle central repository, you might have encountered the Oracle error"ORA-01795: maximum number of expressions in the list is 1000". This issuehas been resolved.

ADAPT01100152

On Linux, when running the Address Server with more than three threads,there is a problem with handling all reference data (post native + UPUcountries). This issue has been resolved.

ADAPT01085674

If a Sybase IQ server is installed on an HP-UX Itanium machine and the jobserver is on an HP-UX Itanium machine, and if the job was using Sybase IQas a reader or loader, temporary files created in /tmp/.SQLAnywhere werenot getting deleted after the completion of the job. This issue has been re-solved.

ADAPT01040190

In HP-UX Itanium 64, jobs connecting to Sybase IQ would not releasesemaphores even after disconnecting. This issue has been resolved.

ADAPT00980364


Resolved issues4

Known issues

5

This section lists known issues in descending order by Business ObjectsProblem Report tracking number. We also use these numbers in the releasenotes that accompany our fix packs and patches. You can reference thetracking number when searching for the issue on our knowledge base orwhen speaking to Customer Assurance.


Known issues5

Known installation issues

DescriptionIssue ID

ADAPT01155032


5Known issues

DescriptionIssue ID

During Data Services installation, an SAP BusinessObjects Edge productactivation keycode may be incorrectly identified as an invalid keycode. Thecause is typically related to upgrading from one tier of the product to another(for example, advancing from a Edge Professional level product to a EdgeData Services level product) or reaching the processor or user account limitsimplied by the keycode.

The problem will typically be encountered during a version upgradescenario or some other form of reinstallation, and can be seen in bothWindows and UNIX installations. You will receive an invalid keycode errormessage.

Solution

If you believe that your keycodes are fully valid and continue to encounterthis problem, we suggest launching the License Manager product directlyfrom the installation media. From the License Manager, you should beable to remove the keycodes that are creating the problem and proceedwith installation.

Windows1. Exit out of the installation. Navigate within the installation media to

package\Utilities\KeyDecoder and launch the LicenseManager.exeapplication within that directory.

2. From the Registered Keycodes section of the application, navigate toSAPBusinessObjects Edge > XI 3.x and record all keycodes displayedin 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.

Unix1. On UNIX, the environment variable BOE_REGISTRYHOME must first

be set. This should be set to a path including the installation directoryand the subdirectory dataservices/registry.

2. If using Bourne shell and the installation directory chosen is /usr/local/businessobjects, execute the following command:

BOE_REGISTRYHOME=/usr/local/businessobjects/dataser


Known issues5

DescriptionIssue ID

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 XWindows 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 SAPBusinessObjects 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 theBusinessObjects Edge area. Once these steps are completed,installation can be resumed.

In both cases, after installation is complete, you should be able to usethe License Manager to add back in any keycodes that would be neededto enable further functionality.


5Known issues

DescriptionIssue ID

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 ofMySQL, when you uninstall BusinessObjects Enterprise, MySQL will be re-moved and the Data Services operations related to the MySQL repositorywill not function. Examples of Data Services operations which will not workare those associated with the Data Services Designer and Data ServicesManagement Console.

Youmust backup of the Data Services configuration files and the MySQLrepository 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 MySQLrepository before you uninstalled BusinessObjects, you can still back themup and then start from Step 3 above.

For the latest update on backup and restore procedures, refer to SAPnote 1274989 in the SAPServiceMarketplace. The note can be accessedat https://service.sap.com/sap/support/notes/1274989.

ADAPT01153442

ADAPT01153440


Known issues5

https://service.sap.com/sap/support/notes/1274989

DescriptionIssue ID

When you uninstall Data Services, the MySqlAdmin5 folder that containsthe MySQL administration utilities will also be uninstalled. This can causeproblems 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 atthe 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 ServiceMarketplace. The note can be accessed at https://service.sap.com/sap/support/notes/1274995.

Multiple Data Services installations on the same Linux or UNIX machinescannot run the Address Server at the same time. To resolve this, youneed 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

ADAPT01142551


5Known issues



DescriptionIssue ID

When installing the Swiss cleansing package through Repository Managerwith DB2, the unzip process crashes. If you want to use the Swiss cleansingpackage, use a different database.

ADAPT01136144

When you install BusinessObjects Enterprise XI 3.1 on the same machineas an existing Data Services XI 3.1 SP1 (version 12.1.1) instance and reusethe Data Services-installed version of Tomcat, uninstalling Data Serviceswill prevent BusinessObjects Enterprise Tomcat web applications fromstarting.

To fix the issue, you must perform a "modify install" to reinstall Busines-sObjects Enterprise. For detailed information on the BusinessObjectsEnterprise modify install option, refer to SAP note 1274978 in the SAPService Marketplace. The note can be accessed at https://service.sap.com/sap/support/notes/1274978.

ADAPT01123319

When installing cleansing packages through Repository Manager, the unziputility cannot unzip compressed files larger than 2 GB on Solaris, AIX, andLinux. This issue only affects Universal Data Cleanse dictionaries for DB2.To work around this, use the Repository Manager on Windows.

ADAPT01113280

Other known issues

DescriptionIssue ID

When using the Metadata Exchange functionality or creating a new Busi-ness Objects Universe using a source datastore that defines an alias, anychanges to the alias value may be lost in the resulting CWM, ERWin, orBusiness Objects Universe. To workaround this issue, export the sourcedatastore to an ATL file, import the ATL to a new Data Services 12.1.0repository, then perform the Metadata Exchange or Business ObjectsUniverse creation operation from the new repository.

ADAPT01151623

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 isdue a bug in MySQL ODBC driver with ODBC Outer left join syntax.

ADAPT01149810

Match - UniqueID - Error issued when using the GUID option on Linux. Tocorrect this problem, deselect this option and use one of the other UniqueIDoptions .

ADAPT01145535


Known issues5



DescriptionIssue ID

USA Regulatory Address Cleanse transform - 100 unique record minimumerror is inconsistently incorrectly generated for jobs where Degree of par-allelism is greater than one. To correct this problem, reduce the Degree ofparallelism value.

ADAPT01144373

When using domain/userid as login for DB2, the existing Data Cleanserepository is not detected. In this scenario, remove your Data Cleanserepository before updating.

ADAPT01113239

The Address Server does not support Locality2 aliases. This affects NewZealand, Hong Kong, Mexico, Ukraine, and South Africa.

ADAPT01112105

Inconsistent LACSLink/DPV Directory initialization errors when Degree ofparallelism is greater than four. To correct this problem, reduce the Degreeof parallelism value.

ADAPT01109755

MySQL case-insensitive collation causes some false matches with Dictio-nary Encryption Algorithm for Universal Data Cleanse.

ADAPT01103044

USA Regulatory Address Cleanse PSForm 3553 report has formatting is-sues when generating the report on AIX. Two workarounds are to purchasethe Arial font and copy the files into the JRE (Java Runtime Environment)path of the Data Services installation (located at <installation_directory>/bobje/jdk/jre/lib/fonts), or to remove the Thonburi andCourier fonts from the Data Services JRE path. This forces Data Servicesto use the Lucida family fonts, which display correctly. After eitherworkaround, you must restart your application server.

ADAPT01099928

The Compare To Object functionality does not always work correctly forData Quality transform configurations.

ADAPT00994274

Sybase ASE is not a supported database for Universal Data Cleansecleansing packages.

ADAPT00959986

When running the Data Quality Migration utility, an error occurs indicatingthat Crypto.dll was not found. To run the Data Quality migration utilitysuccessfully, add %LINK_DIR%\bin to your PATH environment variable.

ADAPT00893920

The option names that you see in Match error messages may not matchthe actual option name.

ADAPT00857445


5Known issues

DescriptionIssue ID

When comparison tables are on Microsoft SQL Server, the Table Compar-ison transform's Sorted input option generates incorrect results. The DataServices engine runs in binary collation while the Microsoft SQL Serverdatabase runs in a Latin1 collation sequence. As a result, Microsoft SQLServer 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.

ADAPT00620063

English cleansing package

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


Known issues5

xi31211 ds release notes en

Documents