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

Developer Tool Known Limitations (10.1.1)

Developer Tool Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
PLAT-9719
When you use an SQL mapping and specify complex queries to generate a mapping, the Developer tool stops responding.
Workaround: You must increase the default value of -Xmx value to 1536M in the
developerCore.ini
file and relaunch the Developer tool. (458862)
PLAT-9400
Users with the IMFCryptographer file can access Model repository objects in the Developer tool that they do not have permissions on.
Workaround: Use Kerberos authentication to prevent transmission of passwords between client and server. (409289)
PLAT-14793
When you run data preview on an Oracle table with a native SSL connection or you run a mapping that has an Oracle data object with a native SSL connection, the Developer tool shuts down unexpectedly. (393023)
PLAT-14704
You cannot use the keyboard to add an HTTP web connection.
Workaround: Use the mouse to add an HTTP web connection.
(431728)
PLAT-14703
You cannot use the keyboard to add a web service connection.
Workaround: Use the mouse to add a web service connection.
(431726)
PLAT-14673
When you create an Oracle connection with a case-sensitive user name, the Developer tool does not display the default schema. (421946)
PLAT-14011
If you install the SQL Server JDBC driver on a virtual machine, you cannot use the driver to connect to Azure SQLServer. (457076)
PLAT-13743
When you import Teradata or Netezza objects from PowerCenter to the Developer tool, objects are converted as Teradata or Netezza objects by default. (457283)
OCON-990
The Developer tool imports the DECFLOAT data type of IBM DB2 for z/OS tables as Char(0). (455216)
OCON-6656
Mappings that contain columns of the Timestamp with Time Zone data type fail if you do not install the Microsoft Visual C++ 2010 Redistributable Package on the server machine.
OCON-609
When you import Teradata and Netezza mappings that contain stored procedures or SQL transformations from PowerCenter to the Developer tool, the import fails. (461184)
OCON-436
When you import Teradata and Netezza mappings that contain parameters from PowerCenter into the Developer tool, the mapping conversion framework does not bind the parameters between the object and the mapping automatically.
Workaround: When you import Teradata and Netezza mappings, mapping parameters
<param>
from PowerCenter are renamed as
<param_mappingname>
in the object level in the Developer tool.
To bind the parameters with the mapping parameters, perform one of the following tasks:
  • On the
    Parameter
    tab of the Netezza or Teradata source and target object, select the required parameters, and then select
    Expose as Mapping Parameter
    .
  • Select the required parameter in the Netezza or Teradata source or target object, click the
    Instance
    value, select
    Specify by Parameter
    from the list, browse, and then bind the object parameter with the required mapping parameters.
(455937)
OCON-353
If you choose to fetch columns from a Microsoft SQL Server source at run time, the data preview and mapping fail. (448786)
OCON-328
If a Teradata mapping contains an SQL query that reads decimal columns with precision less than 15, the mapping fails to run after you import the mapping from PowerCenter to the Developer tool. (459488)
IDQ-2741
Copy and paste operations on a reference table object might fail.
Workaround: Before you copy and past the object, press F5 to refresh the Model repository view. (459780)


Updated January 17, 2019