An error occurs when you use the Teradata DataDirect 5.2 ODBC driver with the PowerCenter Client.
Workaround: Use the Teradata ODBC driver.
174593: Pmrepagent process for the Repository Service might leak memory when you use the Oracle 10.2.0.x client
The Repository Service process might leak memory when it runs on a 64-bit Linux machine, and you use Oracle 10.2.0.x client to connect to the repository.
PowerCenter Limitations
178363: The Integration Service shuts down unexpectedly on AIX 32-bit when you run a session that generates a Sorter cache larger than 2 GB
The Integration Service shuts down unexpectedly when you run a session that contains a Sorter transformation on AIX 32-bit and the size of the Sorter cache exceeds 2 GB.
177814: Session configured with resume recovery strategy fails in PowerCenter 8.5.1 because columns are missing from the recovery tables
After upgrading to PowerCenter 8.5.1, a session configured with the resume recovery strategy might fail because columns do not exist in the PM_RECOVERY and PM_REC_STATE tables.
The Integration Service attempts to dynamically add these columns the first time the session runs in 8.5.1.
The SQL statement to alter the tables might fail for the following reasons:
The user does not have the privileges to alter the tables.
The database returns an error before the Integration Service performs the ALTER statement and the session fails.
Workaround: Manually update each instance of the PM_RECOVERY and PM_REC_STATE tables. The scripts to alter the tables are in the following folder:
[PowerCenter Installation_dir]/server/bin/RecoverySQL
For more information see Informatica Knowledge Base article 22999.
177564: Sessions that contain a Java transformation fail on HP-UX 32-bit
When the Integration Service preloads the JVM library on HP-UX 32-bit, it cannot enable any service. Therefore, sessions that contain a Java transformation fail.
Workaround: Set the LD_PRELOAD environment variable for the Integration Service process to
177338, 177337, 177336: Web service workflow that contains a web service target definition created in the Target Designer can generate errors during execution
In the Target Designer, you can create a web service target definition by selecting Targets > Web Service Provider > Create Web Service Definition. When you run a web service workflow that contains a web service target definition created this way, the workflow can fail.
Workaround: Do not create a web service target definition from a relational or flat file source or target in the Target Designer. To create a web service target definition from a relational or flat file source or target, create it at the same time you create the source definition. In the Source Analyzer, select Sources > Web Service Provider > Create Web Service Definition. On the Create Web Service Definition window, select the Create Target option. Make sure that the Create Source and Create Target options are selected.
176736: Import Mapping Template Wizard fails when you import a slowly changing dimension Type 2 effective date mapping or Type 3 mapping
When you import a slowly changing dimension Type 2 effective date mapping or Type 3 mapping and you used the Create Target option, the Import Mapping Template Wizard fails.
Workaround: If you are using an Oracle source or target, change the ports with Timestamp datatype to date datatype.
176735: Import Mapping Template Wizard fails when you import a slowly changing dimension Type 3 mapping
When you import a slowly changing dimension Type 3 mapping with or without duplicate row handling and you use the Create Target option, the Import Mapping Template Wizard fails.
Workaround: If you are using an Oracle source or target, change the ports with Timestamp datatype to date datatype.
176733: Session with slowly changing dimension Type 2 mapping with version number with or without duplicate row handling fails
Session with slowly changing dimension Type 2 mapping with version number with or without duplicate row handling fails when you use a Microsoft SQL Server source or target.
176730: Session fails unexpectedly while running a dynamic Lookup transformation with an unprojected associated port
A PowerCenter session running a dynamic Lookup transformation fails unexpectedly if a lookup port with an associated port is not projected to another transformation or target.
176439: Moving a Reporting Service from one domain to another results in the user accounts being deleted
If you move a Reporting Service from one domain to another and use the Data Analyzer repository information that you specify in the old domain, the synchronization process deletes all the user accounts that do not exist in the new domain. The Reporting Service does not update the Data Analyzer repository with the information contained in the new domain.
Workaround: Add the users that exist in the original domain to the new domain before you move the Reporting Service. You can also move the users to the LDAP directory service and import them to the new domain, or import the users from the native domain.
176204: UTF-16 and UTF-32 encoding of line feed and carriage return is incorrect for big endian or little endian flat file targets
UTF-16 and UTF-32 encoding of line feed and carriage return for big endian or little endian flat file targets is incorrect.
176143: Importing a flat file source or target that contains a Shift-JIS character and scrolling the preview pane causes the Designer to freeze
If you import a flat file source or target that contains a Shift-JIS character using the Designer Flat File Import Wizard and scroll the preview pane horizontally, the Designer freezes.
176088: Source definitions created from an XML file with Japanese encoding that are then exported from the repository cannot be imported back into the repository
For example, you import a source definition from an XML file that has Shift-JIS (SJIS) encoding. After the source definition is created, export the source to a PowerCenter export file. If you import the file back to the repository, the import process fails.
175920: Load Manager API version 8.5 is not compatible with previous versions of the Load Manager API
The Load Manager API version 8.5 to is not backward compatible with previous versions. Some functions found in previous versions of the Load Manager API may not work in version 8.5.
175739: DTM process generates a core file when you run multiple sessions concurrently
When you run multiple sessions concurrently, the DTM process generates a core file. This does not affect the session results. You can ignore the core file.
175238: Reporting Service gets enabled before all the users and groups in the domain configuration database are synchronized with the Data Analyzer repository
If there are many Data Analyzers users and groups in the domain configuration database, synchronization takes time. The Reporting Service gets enabled on the Administration Console before synchronization completes. If you access the Data Analyzer instance, you might get the following error message: No Privileges.
Workaround: Before accessing the Data Analyzer instance, check the activity log to verify that all users and groups in the Data Analyzer repository have been synchronized with the domain configuration database.
175072: Session with decompress function hangs when you use a Microsoft SQL Server source
Session hangs when the mapping contains a decompress function and reads from a Microsoft SQL Server source.
174889: When you back up a newly upgraded domain configuration database, the backup process fails
If you back up the domain configuration database immediately after you upgrade PowerCenter, the backup process fails.
Workaround: After you upgrade PowerCenter, perform a task that updates the domain configuration, such as creating an application service or adding a user account. After you save the changes to the domain configuration, back up the domain.
173704: Users without adequate permissions cannot create a Reporting Service
If users without adequate permissions to a domain create a Reporting Service in that domain, PowerCenter returns the following error message: “An unexpected error occurred. Contact Informatica Technical Support for assistance.”
Workaround: Verify that users creating the Reporting Service have access permissions to the domain.
171814: Integration Service does not properly recover data for some CDC real-time sessions that write to SQL Server targets
If you recover or warm start a CDC real-time session that writes data to a Microsoft SQL Server target, the Integration Service does not properly retrieve data from the recovery table under the following conditions:
++PowerCenter creates the PM_REC_STATE recovery table in a Microsoft SQL Server database
++The Integration Service connects to an ODBC data source specifying AnsiNPW=no.
Incorrect restart occurs for CDC real-time sessions that use this recovery table.
Workaround: Create the PM_REC_STATE table manually.
170496: You might not be able to connect to the repository during Repository Service
synchronization
You might not be able to connect to the repository in the PowerCenter Client while the Repository Service is synchronizing repository users with LDAP security domain users.
136878: XSD definition contains incorrect code page
When you import an XSD definition with UTF-8 encoding into an ISO-8859-1 repository, and then save and edit it, the encoding changes to Latin 1.
136753: If you import a web service source or target from a WSDL with a large number of elements in hierarchical relationship import mode, the import process can fail
If you import a web service source or target from a WSDL in hierarchical relationship import mode and the Designer generates a large number of XML views in the source or target, the import process fails. The import process can succeed if you import the web service source or target in entity relationship mode.
135022: Links to a port in a target definition fail to import when column name is changed in the target definition
When you change a port name in a target definition and import the definition, mappings with the definition in the target repository do not include a link to the renamed port.
Workaround: Export and import the mapping that includes the target definition.
134614: Internet Explorer may shut down unexpectedly when you configure an LDAP security domain and then move the pointer over the Configure Security icon
Internet Explorer may shutdown unexpectedly when you configure an LDAP security domain and then move the pointer over the Configure Security icon.
Workaround: Apply the latest security updates for Internet Explorer 6.0 or use Firefox to access the Administration Console.
133615: Session fails unexpectedly while running a flat file Lookup transformation
A session fails unexpectedly while running several Lookup transformations. The Lookup transformation that fails is a flat file Lookup transformation that has more than one lookup condition.
The session fails with the following error:
** FATAL ERROR : Unexpected Condition in file [../server/cmnutils/svecmatrix.cpp] line [256]
Workaround: Enable case-sensitive string comparisons.
132253: Integration Service cannot read or write more than 8,000 characters in a text column when it uses an ODBC driver with a Microsoft SQL Server source or target
The Integration Service cannot read more than 8,000 characters from a text column or write more than 8,000 characters to a text column when it uses an ODBC driver to read from or write to Microsoft SQL Server. This problem occurs even if the precision of the source or target column is greater than 8,000.
Workaround: On Windows, use a native database driver instead of an ODBC driver.
131992: Designer shuts down with no errors when you try to use the XML Editor with a large XML schema
The Designer may shut down unexpectedly when you use the XML Editor to open a large XML schema in the Source Analyzer.
Workaround: Do not create XML views when importing the XML source file. Create the views manually in the XML Editor.
130903: Custom profile session fails with fatal error
The DTM process aborts unexpectedly when you run a custom profile session that contains a Custom transformation with 100 or more columns.
130856: Session sometimes fails with an out of virtual memory error when the Integration Service creates a new XML target for each commit
A session sometimes fails with an out of virtual memory error when an XML target is configured to create a new document on commit. When you create an XML document at each commit, the Integration Service allocates virtual memory for each XML root view row. As the Integration Service processes more XML root view rows, the virtual memory buffer requirements increase. The virtual memory allocated is reused across commit intervals. However, if the number of root view rows is large for a commit interval, the session fails and the following error displays:
ERROR: Failed to allocate memory (out of virtual memory). ***********
Workaround: Reduce the number of root view rows for each commit interval or change the mapping to increase the virtual memory available to the Integration Service.
127421: Advanced Purge does not work correctly for source, target, mapplet, and mapping objects
When you preview objects older than the latest version with Advanced Purge, the Designer does not return all of the objects. You cannot purge all of the versioned objects with Advanced Purge.
Workaround: Run a query to retrieve the deleted objects. Select View History. Purge the old object versions by choosing Tools > Purge Object Version.
108493: XML parser performance slows after upgrading to PowerCenter 8.5 on Solaris 32 bit
In PowerCenter 8.5, a session that parses an XML file runs up to 15% slower on Solaris 32bit than in previous versions.
106144: infacmd and infasetup commands hang on sun4v platform
infacmd and infasetup commands hang on machines running on sun4v platform.
105969: Session terminates unexpectedly when the Integration Service tries to set a code page
Session terminates with an unexpected condition when the Integration Service tries to set a code page for a Custom transformation.
104029: DTM process generates a core file when line sequential buffer length is greater than 27,750,000 bytes
When you set the line sequential buffer length great than 27,750,000 bytes, the DTM process generates a core file and the session terminates.
102638: Profile session logs do not appear in the Profile Manager when a persistent profile session fails
You cannot access session logs for failed persistent profile sessions through the Profile Manager.
Workaround: Use the Workflow Monitor to view the session logs.
Data Analyzer Limitations
176319: Data Analyzer displays groups and subgroups of parent or primary groups that are deleted from the User Management Console
Data Analyzer displays subgroups even after the parent or primary group has been deleted. Clicking the user icon associated with that group returns the following error:
Error details: java.lang.RuntimeException: com.informatica.pcsf.common.exception.PCSFConfigException: [UM_10010] The group [Level4-1] belonging to [Native] does not exist in the domain.”
175148: Upgrade does not work if you attempt to upgrade users and groups using the resolution ‘rename to’ with a supplied name that exists in the security domain
If a user or group name is resolved when upgrading users and groups with the resolution ‘rename to’ and the supplied name exists in the selected security domain, the upgrade does not occur.
Workaround: Provide a new name to resolve conflicts or choose to merge the users and groups.
Metadata Manager Limitations
178408: Relationships from packaged models to custom models are deleted during upgrade from 8.5 to 8.5.1
If you create a class-level relationship from a packaged class to a custom class on the Model page, the relationship is removed after upgrade.
178067: Metadata Manager Agent does not start when the installation directory path includes a space
If you install the Metadata Manager Agent and include a space in the installation directory path, the Metadata Manager Agent does not start.
Workaround: Comment out the following line in startup.bat in the
if not "%CATALINA_HOME%" == "" goto gotHome
175479: Permissions on child objects and default permissions on objects in the Metadata Manager catalog are removed during upgrade from 2.2 or 8.1.1 to 8.5.1
If you set permissions on metadata objects in the metadata catalog, the permissions inherited by the child objects are removed when you upgrade the repository. The default permissions set when you create objects are also removed. You must reset the permissions after you upgrade the repository.
174204: You cannot search for multiple tables when you configure an SAP resource on sapr347 and sapr346c machines
When you configure Application Components for SAP, you cannot search for multiple table names separated by commas.
Workaround: Search for single table names.
92040: Data lineage between IBM DB2 CubeViews and a relational database does not work
Data lineage between IBM DB2 CubeViews and a relational database does not work.
No comments:
Post a Comment