Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.1.1 HotFix 1 Fixed Limitations and Closed Enhancements
  4. 10.1.1 HotFix 1 Known Limitations
  5. 10.1.1 Update 2 Fixed Limitations and Closed Enhancements
  6. 10.1.1 Update 2 Known Limitations
  7. 10.1.1 Update 1 Fixed Limitations and Closed Enhancements
  8. 10.1.1 Update 1 Known Limitations
  9. 10.1.1 Fixed Limitations and Closed Enhancements
  10. 10.1.1 Known Limitations
  11. Informatica Global Customer Support

Data Type Known Limitations (10.1.1)

Data Type Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
PLAT-9589
You cannot preview or run a mapping that contains a Java transformation with an unconnected output port of the Timestamp with Time Zone data type. (442175)
PLAT-9580
Default value does not always appear for the Timestamp with Time Zone input port in the testing panel of the Expression Editor.
Workaround: Verify that the source data contains the following format for Timestamp with Time Zone:
MM/DD/YYYY HH24:MI:SS TZR
(439057)
PLAT-14753
The Web Services Consumer transformation and the REST Web Services Consumer transformation do not support the Timestamp with Time Zone data type. (443876)
PLAT-14737
When the number of input rows is greater than 100,000 and the mapping contains a Java transformation with a Timestamp with Time Zone port, the mapping sometimes fails unexpectedly. (440398)
PLAT-14656
Unable to read SAP HANA data for the columns of the Decimal data type with precision from 35 digits to 38 digits. (413806)
PLAT-13511
You cannot specify a Timestamp with Time Zone data type with a time zone region in Daylight Savings Time (TZD) format. (427263)
OCON-6523
You cannot preview data, run profiles or scorecards, or run a mapping for a Timestamp with Time Zone data type on Solaris.
OCON-364
On AIX 6.1, a mapping fails with an unexpected condition when the mapping contains a Timestamp with Time Zone data type. (439054)
OCON-1258
You cannot use a delimiter other than a colon when specifying the time zone offset with the Timestamp with Time Zone data type.
Workaround: Change the delimiter to a colon for the time zone offset for the Timestamp with Time Zone data type. (426892)
BDM-2725
When you do not specify the date format in the
Run Configurations
dialog box or when you do not specify the Timestamp with Time Zone formats in the target file, the Data Integration Service rejects the rows randomly during implicit conversion of a large data set.
Workaround: Verify that the data contains the date format specified at the
Run Configurations
and the Timestamp with Time Zone formats in the target file. You can use a data set with less than 100,000 rows. (440559)
BDM-2720
The Data Integration Service does not apply the cost-based optimization method to the mapping that contains a Timestamp with Time Zone data type even if the mapping is configured with the full optimizer level. (438661)
BDM-2718
Nanoseconds are ignored for Timestamp with Time Zone data in the expression result at the bottom of the testing panel in the Expression Editor. (438040)
BDM-2713
When you configure a mapping that contains a TO_BIGINT function and the function converts decimal values to bigint values for pushdown optimization, the mapping writes incorrect data to the target.
Workaround: Do not configure pushdown optimization for the mapping and run the mapping again. (437066)
BDM-2709
Expression format validation fails for the Timestamp with Time Zone functions: CREATE_TIMESTAMP_TZ, GET_TIMEZONE, GET_TIMESTAMP, and TO_TIMESTAMP_TZ. (432822)
BDM-2463
When you use Timestamp with Time Zone data type in the mapping, the data gets truncated if the precision exceeds seconds. The issue occurs when you enable data object caching on the logical data object mappings and the data object caching database is on IBM DB2 or Microsoft SQL Server. (438061)