Informatica® CorporationInformatica® Data Archive

Version 6.2 HotFix 1Release Notes

April 2014Copyright (c) 2003-2014 Informatica Corporation. All rights reserved.

ContentsVersion 6.2 HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Data Archive 6.2 HotFix 1 Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Data Archive 6.2 HotFix 1 Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Version 6.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Data Archive 6.2 Fixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Data Archive 6.2 Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

This document contains important information about installation, fixed limitations, and known limitations for ILM Data Archive.

Version 6.2 HotFix 1

Data Archive 6.2 HotFix 1 Fixes

Review the Release Notes of previous releases for information about previous fixed limitations.

The following table describes fixed limitations:

CR Description

387178 If you run parallel searches on many child tables, Search Data Vault fails with the error: Unknown column.

384958 Auto-entity creation fails if a table in the entity contains a space in the table name.

384423 An error appears when you add a role for an user after you sync an LDAP user.

383872 The archive to Data Vault job fails at the Generate Candidate step for Microsoft SQL Server tables that have SQL keywords.

IDA-ORC-62100-0001 1

CR Description

383473 The Collect Segmentation Group Statistics for Oracle E-Business standalone job fails with the error: ORA-00904: "PARTITION_NAME": invalid identifier.This occurs when you select the segment name parameter.

383031 Performance issues occur when you query data in the Data Vault from the Data Discovery portal.

382896 If the table name ends in error and the name of the last column ends in error, the Data Vault Loader job fails.

382773 When you create a report and use a table join, all the columns of both the tables are not visible in Data Visualization.

381418 The archive job fails for the JD Edwards Enterprise sales order entity at the Generate Candidate step. The following error appears: [SQL0104] Token (was not valid. Valid tokens: AS NO FOR NOT FILE WITH CCSID CHECK LOGGED UNIQUE COMPACT DEFAULT).

381412 The list of values do not appear when the application login name is different from the application schema name. This is because the ILM Engine uses the application login name to get the list of values.

381410 On IBM AS/400 source databases, the archive job fails for JD Enterprise entities at the Generate Candidate step. This is because of the TO_CHAR in the Where clause.

380939 If the entity contains tables with self-referential constraints, the archive job fails at the Copy to Destination step.

380938 If the SELECT query does not contain double quotes, the extraction job fails at the Copy to Destination step with the error: [informatica][SQLServer JDBC Driver][SQLServer]Incorrect syntax.

380936 If the tables in an entity contain composite keys, the export job fails with a parser error in Data Vault.

380018 Segment PO tables result in missing rows with tables PO_HEADERS_ALL and PO_REQUISITION_HEADERS_ALL.

379932 The CreateBigDataInterimIndexes indexes are created in the global tablespace instead of the interim tablespace.

379930 The function select tdi_perf_util.get_unique_ind_alternative('ont','OE_SALES_CREDITS','N') from dual is taking too long to complete for certain smart partitioning tables.

379927 The split segment creation process fails if the source user does not have privileges on the interim tablespace.

379766 The following issues occur when you retire data from an IBM DB2 database:- Non-ISO time stamp columns prevent the data from loading successfully.- Bulk mode does not extract data successfully.- The loader fails for exotic datatypes.

378619 The function "select tdi_perf_util.get_unique_ind_alternative('ont','OE_SALES_CREDITS','N') from dual" takes too long to complete on certain smart partitioning tables.

378210 Split default segment creation fails for the Account Receivables (AR) module in the pre-process business rules step (ProcessDateDimInterim) with a missing right parentheses error. This is because the Where clause is missing in the dimension rules defined in the AR entity accelerators.

2 IDA-ORC-62100-0001

CR Description

374820 Smart partitioning with interim table processing fails for standard Oracle applications due to a missing space at the Pre-process Business Rules insert statements.

374773 If a report published from Data Visualization Designer uses a non-standard name format, a user with the Report Viewer role can run the report the first time.

374687 The data visualization reports fail when the name of the Data Vault connection begins with a special character or space.

373869 After you import unique key constraints in the Enterprise Data Manager, the Enterprise Data Manager does not enable the unique keys for Informix source database.

373351 When you change the ILM repository password on the database, Data Archive updates and encrypts the password in the DataVisualization web.xml.

373055 If you base your search on reference table fields and enable the All Records option, then export, legal hold, retention, and tagging fail.

373054 The Data Vault metadata database fails when you run reports and the migration job because the record page in the database was beyond record count.

373030 The technical view for the child table fails when the primary key has a timestamp data type.

372909 When you import metadata, the Enterprise Data Manager generates an exception if the database name is in mixed case but you enter the name in uppercase when you connect to the database.

372829 If you run the Detach Segments from Database job and then reattach them with the Reattach Segments to Database job, the read-only status of the table spaces is not retained.

372308 In Browse Data, if the number of characters in the display columns is greater than 4000 characters, the export job fails.

370641 Temporary selection tables are dropped even if you select the No option for dropping the temporary selection tables in both initial and period segment creation.

370457 If an entity you want to retire to the Data Vault has a large number of tables, the retirement job fails with the error: HY000

366816 Issue with table based object creation in Data Visualization.

366544 The default value for the Business Rule Order column should not be 0 (zero) in the Enterprise Data Manager.

362244 Query returns an invalid constant of type INTEGER error.

362060 The first business rule does not work correctly when the PURGEABLE_FLAG value is set to Y.

359322 For multi-level tables created with composite keys, Data Archive does not extract child tables or generate correct insert and delete statements.

357086 INV segmentation fails with the error: ORA-01461: can bind a LONG value only for insert into a LONG column.

354858 The Data Vault Service returns an error that the table was not found even though the table exists.

IDA-ORC-62100-0001 3

CR Description

336612 If you archive a table where the primary key is numeric and the precision and scale are defined, the interim table column is numeric with only precision defined, not scale.

334862 The Synch with LDAP Server job fails when it encounters special characters such as /.

310285 You cannot save a source connection with the application module name if the application module name contains OPS$.

309917 The Copy to Destination step does not follow the order defined in the entity.

295122 When thread tables are created as non-IOT tables, unexpected slow performance results.

294384 If the table is an index organized table, the archive job fails at the staging step with the error: SQLException ORA-01410: invalid ROWID.

292587 On IBM DB2 UDB 9.1, the Build Staging step fails for timestamp data types.

286400 Data Discovery fails for entities that do not contain interim tables.

282436 When you schedule an archive job to occur daily, the archive job runs even if the previous archive job has not finished.

279021 The technical view does not show the records correctly when the data type, length, and column name are different for the join key between the parent and child tables.

275884 On IBM DB2 databases, the import and export function does not support .del extension files when the database is partitioned.

270019 The Generate Candidates step fails when the primary key is a Varchar data type.

269064 The archive job fails for the HR entity with the error: Numeric overflow.

264031 The production and the history versions of IBM DB2 UDB tables are not archived to the same folder.

258330 The Seamless Access Script job fails for IBM DB2 z/OS when the ILM repository is on a Microsoft SQL Server.

254707 Multiple parameters against different child tables generate an invalid search query in Data Discovery.

251435 You cannot export metadata from a US-based ILM repository to a Japanese-based ILM repository.

249122 During an archive, the Microsoft SQL Server bit data type values 0, 1 are converted to true, false in Data Vault.

244095 Copy to Destination step for the MQS Application fails.

241898 Unable to archive FND (APPLSYS) products.

233410 The Import Entity Constraints option in the Enterprise Data Manager fails if the same table or constraint exists in multiple schemas within an application version.

232524 The Generate Candidate step fails when the interim column has a date field with a specified length.

4 IDA-ORC-62100-0001

CR Description

231166 Enterprise Data Manager does not create the delete order when you add tables.

229998 The Truncate Table command is not supported in IBM DB2 for z/OS version 8.

227456 The Create Tables job fails when the table has a user-defined data type.

227238 The Update Apps Table step does not append the JOB_ID to the interim table name.

223824 On Oracle E-Business Suite 11.5.10, the contract lines entity does not get archived when you run OKC - Service Contracts.

222828 When the source database is Oracle, the archive job fails when tables contain the Varchar (n char) columns.

Data Archive 6.2 HotFix 1 Known Limitations

The following table describes known limitations:

CR Description

388655 If the source database is IBM DB2 UDB, the archive job fails at the Generate Candidate step under the following conditions:- You import metadata offline.- A table contains a column with decimal values.

388188 On Windows 32-bit operating systems, the Data Vault Service cannot locate the EVP_md2 in the dynamic link library LIBEAY32.ddl.

387837 If the ILM repository is on IBM DB2, the Test JDBC Connectivity job list of values does not show the repository name.Workaround: Use Oracle for the ILM repository.

387753 If the source database is Microsoft SQL Server, the archive job fails at the Generate Candidate step if the column name contains the following value: <space>From.

387700 Constraints do not import correctly under the following conditions:- The source database is Microsoft SQL Server and the table name contains the characters [].- The source database is IBM DB2 and the table name contains the character \.

387527 If the data you want to archive or retire contains the Decfloat data type, the archive job fails at the Copy to Staging step.Workaround: When you define the source connection in the archive or retirement project, set the Insert Commit Interval to 1.

387286 If the source database is IBM DB2 AS/400, the transaction and cycle restore jobs fail at the Copy to Destination step.

386664 If the source database is Microsoft SQL Server 2012, the Data Growth Analyzer collection job fails with the error: Invalid parameter bindings.

IDA-ORC-62100-0001 5

CR Description

386657 The archive job fails at the Copy to Destination step when the following conditions apply:- The source database is Microsoft SQL Server.- The entity includes reference tables.- You enabled the Use Imported Schema Name check box when you set up the source connection.Workaround: Clear the Use Imported Schema Name check box and enter the imported schema name in the Application Schema Name field.

386614 If the target database is IBM DB2 UDB, import metadata through Enterprise Data Manager fails for related tables in different schemas.Workaround: Import metadata as a background job.

386558 The upgrade process creates a backup of existing start and stop application files. This might cause many start and stop application files in the installation folder.Workaround: Delete the older start and stop application files if not required.

386313 The Validate Destination step fails if both the following conditions apply:- You started ILM as a service.- You created a target connection for Data Vault using mapped network paths for the SCT and STAGE locations.Workaround: Create the target connection for Data Vault with SCT and STAGE locations as shared network (UNC) paths.

385725 On a Windows operating system, if a table contains a special character that is not supported by Windows OS, then the Update Retention policy and Apply Legal Hold fails.

385602 If the source database is Microsoft SQL Server, the Copy to Staging step fails if the name of a child table contains a space.

385077 The Data Vault loader job fails under the following conditions:- You installed the ILM Engine and Data Vault on different machines.- You created a target connection for Data Vault using mapped network paths for the SCT and STAGE locations.Workaround: Create the target connection for Data Vault with STAGE and DATA locations as shared network (UNC) paths.

384413 The allocate data files to mount points job does not update the table space size properly.

383332 If the source database is Microsoft SQL Server, and a table name exceeds 50 characters, the Data Growth Analyzer job fails with a string or binary truncated exception.

383294 You cannot import metadata through the JDBC-ODBC bridge. The following message appears: No data found and columns are not populating in EDM.

383177 If the source database is Informix, you can import metadata for only one set of relational tables even if you selected child tables for more than one relational set of tables.Workaround: Import metadata for one set of relational tables at a time or use the offline job to import metadata for all the tables.

383054 If the source database is IBM DB2 AS/400, you cannot create an entity based on the unique key because the unique key constraints do not get imported.

382988 If the source database is Microsoft SQL Server, the archive job fails if the entity contains tables from multiple schemas.

6 IDA-ORC-62100-0001

CR Description

382898 When a reference table has a child table, Enterprise Data Manager does not create the Where clause condition for the child table.Workaround: Add the Where clause statement for the child table.

382650 Tables with special characters in the table name do appear in the table list when you import metadata.

382473 If the source database is Microsoft SQL Server, then the name of the database appears instead of the name of the schema in the Select Schema(s) to Mine page of the Import metadata from Database wizard.

382332 If you have complicated CASE statements in the SQL query, you cannot use an SQL query to create a data visualization report in Data Archive.Workaround: Create the report with Data Visualization Designer and import it to Data Archive.

382314 If you have data with null values in the unique column, then Data Archive does not insert the records with the null value in to staging.

381969 If you skip the clean up after segmentation step in the initial smart partitioning process, you cannot split the default segment afterward.

381782 If the source database is IBM DB2, the Data Vault loader job fails when the table name, column name, or constraint name contains the following special characters: /;[]<>?:{}|

381282 If the source database is IBM DB2 UDB and if a column name in the driving table contains the special character =, then the archive job fails.Workaround: Create the table manually for target and interim. Remove the = from the column name in the interim table.

379895 If a child table in the entity has multiple references to the parent table, Enterprise Data Manager generates multiple INSERT and DELETE statements. This might lead to archiving duplicate records.Workaround: Delete the existing Entity. Verify the constraints and ensure that each child table has one path to the parent table. Disable the constraints that you do not require. Then, create a new entity.If you keep the multiple paths from the child to the parent table, select one of the following options when you archive the entity:- Select the archive and purge option if individual records do not overlap between the constraints.- Select the archive-only option if individual records overlap between the constraints. If you select this option, you must

delete source data. After you archive, you cannot restore data.

367844 The connection schema name is not sufficient to execute smart partitioning queries if the tables have multiple owners.

Version 6.2

Data Archive 6.2 Fixes

Review the Release Notes of previous releases for information about previous fixed limitations.

IDA-ORC-62100-0001 7

The following table describes fixed limitations:

CR Description

367665 The archive job fails with a duplicate domain name error when you archive data to the Data Vault.

367503 When you archive to an IBM DB2 database, the archive job converts null values from the source tables to empty strings in the target tables for columns that have Boolean, Character, Varchar, Vargraphic, and Long Vargraphic datatypes.

367502 When you archive to an IBM DB2 database, the archive job fails at the Copy to Destination step for table columns that have null values and Dbclob datatypes.

367497 When you export data to PDF or CSV files, you receive an error that the equal operation cannot be used with Timestamp and Date datatypes.

367495 The Data Vault Service shuts down during query processing if the projection list has duplicates and if more than two Data Vault Agents process the query concurrently.

367492 The Data Vault Service cannot start because the metadata check failed.

367489 When you use the Microsoft SQL Server Reporting Services tool to access data in the Data Vault, the Data Vault Service crashes for queries that involve joins from three or more tables.

367488 When you start the Data Vault Service, there is a metadata corruption issue.

367487 When you browse data, if a column name in the search contains a special character, Data Discovery generates a null pointer exception.

367485 When you run queries that involve joins on two tables in the Microsoft SQL Server Report Builder, the query execution fails with an invalid semantic attribute error.

367484 When you export data, you receive an index out of bound exception error.

367441 The Delete from Source step tries to close the target connection instead of the source connection.

366981 The INSERT AS SELECT routine does not support Time datatypes.

366980 Bulk mode fails for the Timestamp datatype on IBM DB2 z/OS.

366978 The Data Vault Loader job times out with a null tested server error.

366464 Cannot load external attachments to HCP.

365753 The Data Vault Loader job adds nulls values to timestamp columns when the BCP file contains a large number of rows.

362469 The Data Vault Loader job creates a DAT file in the staging directory for columns with Rowid datatypes and deletes the file after the job completes.

360714 The Data Vault Loader job fails when you run the job twice for the same entity for external storage.

360712 When you resume a retirement job, the log shows an error that the file was already registered.

359259 Split Segment job runs out of space in the global tablespaces.

8 IDA-ORC-62100-0001

CR Description

359251 When you run INV segmentation, you receive an error that the entity is copied from the original entity.

357479 The Data Vault repository includes inconsistent metadata due to incorrect SCT file registration.

356748 When you export data, you receive an error that the > operation cannot be used with the Timestamp and Date datatypes.

356141 The Data Vault Loader job log includes an error that BLOB file is not accessible when you archive from a Microsoft SQL Server database that has Binary(1) datatypes.

355683 Need default mappings for Varchar and Char datatypes to convert to Varchar with a length that is two times that of source.

355143 The Search Data Vault and the technical view show incorrect data even if there is valid data.

355103 Data Archive includes standalone jobs that are no longer valid.

351540 When you use stylesheets in the application view to open external attachment file types such as JPG, ZIP, TIF, and PPT, you receive an error.

351479 Browse Data and Data Discovery searches hang for large number of records when multiple parallel users run searches.

351474 Datatype mapping does not support multiple connections for the same datatype.

351438 Retention job fails because the Data Discovery session does not close the connection after the session fetches data from the Data Vault.

351437 Retention job fails if the column includes a Timestamp datatype.

351281 Parallel delete statements for Oracle E-Business Suite use the application owner instead of the schema owner.

350867 The Data Visualization Designer uses the wrong ini files.

350314 Datatype mapping does not support multiple connections for the same datatype.

343848 On Sybase databases, the extractor fails at the Generate Candidate step. The following message appears: CREATE TABLE command is not allowed within a multi-statement transaction in the STAGE database.

343470 When the ILM repository is on Microsoft SQL Server, the upgrade from 5.3.7 to 6.1.1 fails for Named Instance if the repository database name is different from user name.

341951 On Windows, the ODBC registry file does not automatically update to the correct database when you upgrade.

341893 When you create a data visualization report with a parameterized SQL statement, the data does not display on the report-creation wizard. However the data does display in the report.

341885 The compress segment job fails at the RebuildUnusableIndexes_Task step if the table has a read-only segment.

341762 Check constraints are dropped from the database after the segmentation.

IDA-ORC-62100-0001 9

CR Description

341361 When you use a Power Exchange adapter to connect to a source database, the double(15) datatype is treated as a float(15) datatype. This causes the loader to fail with a numeric truncation error.

341351 Transaction restore and cycle restore functions fail for the Microsoft SQL Server source nvarchar(max) datatype.

340999 If you select the dictionary option for extent management when you configure the segment tablespace properties, the tablespace creation fails.

340438 User actions related to data visualization are not recorded in the audit logs.

339468 The application log contains ILM repository details.

339462 In data visualization, if a column contains a large CLOB, the report field appears blank in the web report.

337645 The create indexes job fails for user-defined datatypes and displays the following error: ORA-02327: Cannot create index on expression with datatype NAMED TABLE TYPE.

333726 Retention policy errors with IncorrectResultSizeDataAccessException.

332781 The archive to database job fails for nested tables at the Copy to Destination step when there are inconsistent datatypes.

326884 The transaction restore job restores the selected rows displayed on the first page even if you select rows on other pages.

326582 Users can call JavaScript functions or commands.

326151 When the ILM repository is on IBM DB2, the Purge Expired Records job fails at the Generate Report step if you do not specify an entity.

324308 On Windows, the Data Vault Loader job fails if the name of an entity contains the $ character.

318578 Cannot create seamless access when a Microsoft SQL Server source contains more than 1000 tables.

316073 You cannot use the following special characters in table or column names for Data Vault archive: ' " / \ ; % * | < > ?You cannot use the following special characters in column names for database archive: ( ) . # "You cannot use the following special characters in table names for database archive: ( ) . , @ " & =You cannot use any special character in the primary key column name in Data Vault archive and database archive.

292846 Archive job fails when the total row count has more than 10 digits.

287703 The technical view does not show the data if the description in the search options contains special characters.

10 IDA-ORC-62100-0001

Data Archive 6.2 Known Limitations

The following table describes known limitations:

CR Description

381225 When you search across applications in Data Vault with a keyword, the search excludes columns with a BLOB or CLOB data type even if you selected these columns to be indexed.

378437 When you archive or retire data from a IBM DB2 source to Data Vault, search results do not appear correctly.Workaround: Use the code page ;CharsetFor65535=CP950 in the source connection to map the following data types to the Data Vault data types:- Map varchar() for bit data to varchar(2X)- Map long varchar for bit data to varchar(1X)

375405 The SAP Accelerator Installer status is set to SUCCESS even when the SAP Visualization Server is not running and data visualization reports are not published.

374348 Data Vault restore fails to restore data with the following datatypes:- XMLtype, bfile, urowid, timestamp with time zone, timestamp with local time zone, long, Oracle-supplied, and user-defined

datatypes on Oracle databases.- Clob, blob, dbclob, XML, and long vargraphic datatypes on IBM DB2 UDB and IBM DB2 zOS databases.- Char datatype on IBM DB2 zOS databases.- Nvarchar datatype on Microsoft SQL Server 2005 databases.

374056 Profiling on Data Vault fails when running from Enterprise Data Manager.Workaround: Perform the profiling from Informatica Data Explorer. Export the results from Informatica Data Explorer and import to Enterprise Data Manager.

373722 Profiling on Data Vault fails with DSN name not found error.

373633 When you search for records across applications, the search results take a long time to appear.Workaround: Clear the cache and search.

373409 If you run a segmentation policy with list type dimensions, access policies with the list scope type fail if you provide more than one list value when you create the access policy.

372982 The following row count limitations occur:- During an archive cycle, if the same table has different WHERE clauses in the entity, then the Copy to Destination report

shows a discrepancy in the row counts.- For Power Exchange Adapter source databases, the row count report does not work.

372848 The following limitations are specific to Sybase source databases:- Data Vault archive fails at the Delete from Source step.

Workaround: Remove the alias name from the Enterprise Data Manager delete statements.- Data Vault archive fails at the Copy to Staging step because the Build Staging step does not create staging tables.

Workaround: Precreate staging tables.

372801 If the reference tables to an entity are created with a join condition that has multiple character columns in the IN clause, then you cannot export the reference columns.

372175 When you search across applications in Data Vault, if you resume the Create Indexes for Data Vault job, duplicate records appear in the search results.Workaround: Update the search indexes. First run the job to delete the search indexes and then run the job to create the updated search indexes.

IDA-ORC-62100-0001 11

CR Description

371286 The following limitations are related to operating systems:- On a Solaris environment, you cannot create data visualization reports.- On a Windows environment, the Data Vault Service indicates that it has started even after an error occurs. Errors are

listed in the ssa_server logs.

368508 The following limitations relate to special, mixed-case, or multibyte characters:- On IBM DB2 databases, if the database link, schema, table, or column names contain special characters, the Create

Seamless Data Access job fails.- Records do not appear on the Modify Retention page if the column name in the search field contains multibyte

characters.- On Microsoft SQL Server and IBM DB2 source databases, constraints do not import correctly when table name contains

special characters / and [ ].- You cannot create data visualization reports and tables on the ILM repository when the ILM repository name and

password contains the @ character.

368505 On IBM DB2 UDB databases, if you specify the combined schema location or archive schema location as the target, the Create Seamless Data Access job fails.

365382 When the ILM repository is on Oracle, the restore job fails to restore Siebel file attachments from the Data Vault.Workaround: Remove the decode function from the attachment.properties in the restore section.

360049 The archive jobs fail for the following datatypes:- Archive to Data Vault fails at the Copy to Destination step for the bfile datatype when you archive from the history

database.- Archive to database fails at the Validate Destination step for the decfloat datatype on IBM DB2 UDB databases.- Archive to database fails at the Build Staging and Validate Destination steps for the graphic, vargraphic, long vargraphic,

XML, and dbclob datatypes on IBM DB2 zOS databases.- Archive to database fails at the Copy to Staging and Copy to Destination steps for the clob and blob datatypes on IBM

DB2 zOS databases. Workaround: Create the tables manually in the staging schema.

344961 When the ILM repository is on Microsoft SQL Server, child tables do not appear in the technical view, when physical constraints are imported as a scheduled job.Workaround: Go to the Enterprise Data Manager Constraints tab, select the parent table, add constraints, and save.

344918 Automated upgrade for SAP live archiving is not available.Workaround: Contact Informatica Global Customer Support to help with the upgrade for an SAP live archiving scenario.

343193 Data Archive for use with SAP works only with the 32-bit SAP Secure Libraries. The 64-bit SAP Secure Libraries are not supported.

342360 When the source schema name is different from the connection name in Informatica Data Explorer, you cannot view relations and keys under that schema.Workaround: View relationships and keys under a schema from the application version level.

341791 If you choose local for the index creation option and global regular for the bitmap option, the bitmap is created as local regular.Workaround: You must manually rebuild the bitmap indexes as global.

341513 On Netezza source databases, the archive job fails at the Generate Candidates step when you select a row count report in the project.

12 IDA-ORC-62100-0001

CR Description

340004 The view transaction object does not display multiple schema tables in the Enterprise Data Manager.

337897 The Data Archive job fails with error that the job cannot find the metadata.ddl file.

321769 The load external attachment job does not load the attachments if the file name contains multibyte characters.

313162 The following limitations occur for Teradata source databases:- Data Vault archive fails at the Build Staging step for the time zone and time interval datatypes.

Workaround: Clear the Use Copy to Staging check box on the Source Connection page.- On Teradata source databases using Teradata Parallel Transporter, cycle restore fails at the Copy to Destination step.

Workaround: Clear the Use Teradata Parallel Transporter checkbox on the Source Connection page.

310968 When a SAP job is cancelled with run-time errors, the ILM logs do not display the updated status of the SAP job.Workaround: Use the SM37 transaction code to monitor the status of the SAP job.

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support.

Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com.

The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.

IDA-ORC-62100-0001 13