SAP Knowledge Base Article - Preview

1394280 - Data Services XI 3.2 SP1 (12.2.1.0) Release Notes

Symptom

This release resolves the following list of issues.  For full release note which contains migration considerations and known issues, please see the attached file.The issues listed here were fixed specifically in Data Services 12.2.1.0. The Issue ID numbers refer to the Problem Report tracking number and are listed in descending order. These numbers are also used in the release notes that accompany all maintenance releases. You can reference the tracking number when searching for the issue on our knowledge base or when speaking to Technical Customer Assurance.  

ADAPT01302966 When a job that contains a Match transform was run, the job intermittently failed with the error "Cannot open file <C:/Program Files/BusinessObjects Data Services/Log/PCache/.../xxxxxxPageableCollectionPassthruxxxxx">... Please check its path and permissions". This issue has been resolved.   

ADAPT01301387 When directly loading data from an Oracle CDC table and changing the DI_SEQUENCE_NUMBER data type to decimal, an access violation occurred. This issue has been resolved.  

ADAPT01297309  For 64-bit Linux environments, using the "Convert text to numbers" option within the Match transform caused a crash for certain "Locale" option settings when large scientific notation values (for example, 5602e402) is present in the data. This issue has been resolved.

ADAPT01291288 When migrating from Data Services 12.1.x.x to 12.2.0.x, incorrect results were generated for some Query transforms if there are two project members in the Query transform that use the same input column and one of the project member modifies the column and the other project member uses the modified column value instead of the original input column value. This was due to a bug in the Data Services engine. This problem has been fixed.  

ADAPT01289547 Output data was not being populated within the Global Address Cleanse transform's standard output fields when using suggestion list processing. This issue has been resolved. The suggestion list output fields and standard output fields should both be populated with data when using suggestion lists.  

ADAPT01287581 In the generated ABAP code for Datastore, code page 'utf-8' was incorrectly set to encoding = '1100'. This issue has been resolved.  

ADAPT01286201 Creating a Data Service repository on a non-US-English locale SQL Server 2008 database failed. This problem has been resolved in this release.  

ADAPT01286185 Embedded non-printable characters like carriage-return and line feed in the source data stream caused Data Services bulk loads to fail when sending data using Teradata bulkload utilities. This problem has been fixed in this release.  

ADAPT01286093 The Designer failed intermittently while performing "view data" on a table. This issue has been resolved.  

ADAPT01284390 When a local or global variable value was passed via a parameter to a COBOL copybook format to set the data file name, the value of the variable was truncated. This issue has been resolved.  

ADAPT01284300 Global Address Cleanse transform - EMEA Engine: If an address on input should contain secondary information, such as "flat" information, to be fully qualified, the engine was not outputting an info code to reflect this. This issue has been resolved.  

ADAPT01282793 If a global variable is used as the transport file name in an R/3 data flow, the job failed due to a misformed path name. The issue has been resolved.  

ADAPT01281139 The global variable(s) default value was lost after renaming the global variable(s). This problem is resolved in this release.  

ADAPT01279140 A new file format option "Row within text string" has been added. It has two values: • Character. A row delimiter within text string is treated as character. This is the default value. • Row Delimiter. A row delimiter within text string is treated as a row delimiter.  

ADAPT01278556 When restarting the Designer after it had been configured to use a secured central repository, the Designer sometimes appeared to hang. This happened when the Designer was configured to use the secured central repository and the "remember" password option for the central repository was not selected. This issue has been resolved.  

ADAPT01277891 Global Address Cleanse transform – EMEA Engine: If an address in the UK contains "UK" on other lines, the duplicate country code was not recognized. This issue has been resolved.  

ADAPT01277888 Global Address Cleanse transform – EMEA Engine: In some cases, the engine was unable to assign an address that is unique just by inputting the post code and the primary number. This issue has been resolved.  

ADAPT01277884 Global Address Cleanse transform – EMEA Engine: If there is a number in the same input line as the street name, this number was parsed as primary number and not tried as a flat number. This issue has been resolved.  

ADAPT01277750 Global Address Cleanse transform – EMEA Engine: The engine was not able to recognize abbreviations such as "hse" for "house". This issue has been resolved.  

ADAPT01277743 Global Address Cleanse transform – EMEA Engine: If an address has no primary number and the flat number is input directly in front of the primary name, the engine was not able to recognize the flat number as it was parsed as a primary number. This issue has been resolved.  

ADAPT01277733 Global Address Cleanse transform – EMEA Engine: If there is a building name and a street name on the same input line without a delimiter between them, the engine was not able to differentiate the two. This issue has been resolved.  

ADAPT01277727 Global Address Cleanse transform – EMEA Engine: If there is just a street name and a region name on input, the engine misparsed the region as a locality and mismatched the address if the address components could be fuzzy matched. This issue has been resolved.  

ADAPT01277615 Global Address Cleanse transform – EMEA Engine: If the locality is missing on input when using multilines only, secondary information could be misparsed. This issue has been resolved.  

ADAPT01277474 AL_RWJobLauncher in Unix/Linux with parameter -t was not working correctly. This problem has been fixed in this release.  

ADAPT01276781 In a job with try/catch that has a flow with more than four levels of "nested if" conditions and the last level causes an error, the job hung on the AIX platform. This problem has been resolved in this release.  

ADAPT01275749 When a repository upgrade is not successfully done from 11.7.x to 12.x, executing a job in the Designer sometimes hit an access violation. This problem has been resolved in this release.  

ADAPT01273618 Calculating column mappings failed with error "VAL-030359: Error calculating column mappings for data flow <dataflow name>..." when the data flow contains the function call extract_from_xml. This issue has been resolved.  

ADAPT01271622 In this release, a new Data Services WSDL interface version is introduced: version 2.1. In this version, the input/output schema in the WSDL has been modified to add elementFormDefault="qualified" for a real-time service when the corresponding real time job is created using no namespace schemas. If you have web service client applications that use an earlier version of the WSDL, your applications will continue to work. However, Data Services will use WSDL version 2.1 as the default for generating new WSDL.  

ADAPT01271565 Using hex string 'x/000' as a search string in replace_substr_ext() was returning an unexpected result. This problem has been resolved in this release.  

ADAPT01268769 For the Data Services repository, if a user created a schema that did match the user name in Microsoft SQL Server 2005 or above, they would not be able to view Data Quality reports. This problem has been resolved.  

ADAPT01267493 A verification warning was received when Remove_Punctuation and Convert_Text_To_Numbers options are both enabled within the Match transform. This issue has been resolved.  

ADAPT01266434 Loading data to BW targets resulted in incorrect data. This issue has been resolved.  

ADAPT01264469  A job that has a hierarchy flattening transform where the child attributes list does not match the input schema columns ends with the error <Named Pipe ended>. This has been fixed to make sure the mismatch is validated and a proper error message is displayed.  

ADAPT01263001 HTTP Adapter failed to process the request for content type application/xwww-form-urlencoded. HTTP Adapter did not encode the input message before sending it to the URL. This issue has been resolved.  

ADAPT01262019 If you created a repository connection in Data Services Management Console using Oracle RAC, you were unable to view the Data Quality reports. This problem has been resolved.  

ADAPT01261376 When the same job was published in multiple local repositories and a schedule for the job was deactivated in one repository, then all entries for the job for all repositories were deleted in crontab. This issue has been resolved.  

ADAPT01261320 A job ran into an access violation error when writing to the overflow file after database insert/update statements failed. This issue has been resolved.  

ADAPT01260658 Loading NULL string as data to Netezza tables using bulk load would fail with error "ERROR: External Table : count of bad input rows reached maxerrors limit, see nzlog file". This issue has been resolved.  

ADAPT01258941 Recover from a failed execution could fail for a R3 Job if the first run failed after finishing FTP transfer. This issue has been resolved.  

ADAPT01258858 A job which contains a table comparison transform in the following situation sometimes got an access violation error causing the engine to core dump: The transform uses either the Row-by-row or Sorted-input option. The transform also uses Detect deleted rows and Detect row with largest generated key value options specified. The job also starts with the "Collect Statistics" option. This issue has been resolved.  

ADAPT01258732 An exported job with cross-field matching configured within the Match transform was not importing correctly, which then generated errors when running the imported job. This issue has been resolved.

ADAPT01258686 The BusinessObjects Address Server service would not start after performing a maintenance installation upgrade to Data Services 3.2 (12.2.0.0) due to a file not updated correctly. This issue has been resolved.  

ADAPT01257269 Calling a web service failed if no target namespace was provided in the published web service. This issue has been resolved.  

ADAPT01256645 If bad rows were written to the overflow file while running a job, the Management Console displayed the status as failed. Instead of failed, the status should have displayed as completed with warnings. This issue has been resolved.  

ADAPT01256631 When calling a web service via the web service datastore and the input data contains multi-byte characters, the data that the web service client sends out was corrupted. This issue has been resolved.  

ADAPT01254863 When using a Match transform configuration in a dataflow and one or more settings are removed, upon saving, exporting, and importing the dataflow, the settings that were previously removed reappeared. This issue has been resolved.  

ADAPT01252834 The error message was truncated when the web services function call failed. This issue has been resolved.  

ADAPT01251801 Data Services Web Service operation Get_Trace_Log failed with the error "The Trace log file does not exist" for the job executed using Job Server Group or Job Server running on different machine than web server. This issue has been resolved.  

ADAPT01251106 With ANSI_Varchar_Behavior set to FALSE in the product configuration, leading and trailing blanks in the fixed-width file readers were not trimmed. This issue has been resolved.  

ADAPT01249976 Data Quality Address Cleanse Sample reports were not generated correctly when utilizing a Sybase repository. This issue has been resolved.   

ADAPT01249520 In the lookup_ext function, using persistent cache table as a lookup table is not allowed. In this release this is resolved by not showing persistent tables in the lookup table browser.  

ADAPT01248540 The BusinessObjects Address Server was experiencing a memory leak when processing records for a sustained amount of time. This issue has been resolved.  

ADAPT01248020 Netezza bulk load using Named Pipe failed with the error "The database client cannot connect to named pipe". This issue has been resolved.  

ADAPT01247993 Absolute time for processing rows for a transform displayed an incorrectvalue in the monitor log for jobs that run in recovery mode. This issue has been resolved.  

ADAPT01246778 Server configuration utility SVRCFG crashed on SuSe LINUX. This issue has been resolved.  

ADAPT01246486 A "%1" message was received instead of an error message when using the Export Data Quality Reports functionality if Session Security is enabled for that web operation. An appropriate error message is now issued.  

ADAPT01245991 When communication between the job server and its clients (that is, Designers and Management Consoles) was interrupted, the job server could exceed its thread pool limit on the AIX platform. When this happened, the job server started getting a "processing threads <100> are busy" message and stopped responding to client requests. This issue has been resolved.  

ADAPT01243846 In the Management Console, the Log Deleter produced errors when cleaning up items for DB2 repositories. This issue has been resolved.  

ADAPT01241280 If a job contains an inner join with no data from the outer table, the job sometimes hung. This issue has been resolved.  

ADAPT01233741 Inconsistent system exception errors sometimes occurred when the Degree of parallelism option is greater than four within a dataflow containing the Geocoder transform. This issue has been resolved.  

ADAPT01229901 If multiple USA Regulatory Address Cleanse transforms exist in the data and the Degree of Parallelism option is set to greater than 1, the job sometimes crashed if using a Linux platform. This was due to the product using more than the maximum number of file handles available on the system. This issue has been resolved.  

ADAPT01228385 When reading datetime2 and datetime data from SQL Server 2008, if the columns are converted to Varchar in a Query transform and subsequently written out to a flat file, the formats of the data were different. This problem has been resolved in this release.  

ADAPT01227274 When a data flow has more than four levels of nested "if" conditions and the last level causes an error, the job hung on the Solaris platform. This issue has been resolved.  

ADAPT01226059 If the date value separator in the input_expression field does not match the date value separator in the date_format field, the is_valid_date function returned TRUE. Starting with this release, the default behavior is that the function returns TRUE if the date value separator in input_expression and the date value separator in date_format match and FALSE if they do not match. However, if you have an existing installation and update to this release, the function will still work in the old behavior. The change will take effect only if you turn on a special flag. From the Designer menu choose Tools > Options > Job Server > General, with Section set to "AL_Engine", Key set to “Datetime_Backwards_Compatible" and Value set to "FALSE".  

ADAPT01225615 Creating recurring job schedules on BusinessObjects Enterprise from the Management Console failed with error "The value 259526 of property SI_GROUP_ID does not fall with in the expected range 0 and 32767". This issue has been resolved.  

ADAPT01220743 Importing a table or a function from the command line into a datastore with aliases did not import the object properly. Instead, a new instance of the object was created in the datastore. This issue has been resolved. If you have aliases defined in the datastore, you can import the table or function by specifying the actual owner name in the command line.  ADAPT01220645 A job with flat-file processing sometimes hung at the end of the run on HPUX Itanium 11.31. This problem has been fixed in this release.  

ADAPT01216278 A real data type constant mapping of '0.0' in a Query transform caused SQL statements to be generated incorrectly. The value was treated as blank. This issue has been resolved.  

ADAPT01214141 In Data Services 12.2.0.1, selecting to export Data Quality Reports or using the -xCR command generated an access violation, a dump file, and an invalid return code. This issue has been corrected.  

ADAPT01198013 Web Service Adapter failed with an error "Read Timeout" when the web server took a long time to process requests. This issue has been resolved in this release by providing a configurable option in Web Service adapter datastore with a timeout period specified in milliseconds.  

ADAPT01183452 While configuring a native web service datastore, if HTTP basic authentication is used, Web Services got two requests although it was only invoked once. This problem has been resolved in this release.  

ADAPT01173982 After importing an ATL file which contained a Key Generation transform in a valid data flow, the data flow did not pass validation in the Designer. This issue has been resolved.  


Read more...

Product

SAP Data Services XI 3.2

Keywords

Data Services Fix Release 12.2 SP1, Note, DS, 12.2.1 , KBA , EIM-DS , Data Services , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.