PMPC-62 - Release Notes For 6.2

Informatica Corporation
Informatica® PowerCenter® 6
Informatica® PowerMart® 6
Version 6.2
Release Notes
March 2003
Copyright 2003 Informatica Corporation
PowerCenter and PowerMart are registered
trademarks of Informatica Corporation. All other
trademarks and copyrights acknowledged.
Metadata Exchange for Data Models:

Underlying technology (c) 1997-2003 Yaletown Technology Group Inc.
All Rights Reserved.
Contents
CD Contents .............................................................................................................................................3
Informatica Developer Network ................................................................................................................3
Webzine....................................................................................................................................................3
Web Support.............................................................................................................................................3
6.2 New Features and Enhancements.........................................................................................................3
Backward Compatibility........................................................................................................................4
Informatica Server.................................................................................................................................4
Linux ....................................................................................................................................................4
Metadata Reporter.................................................................................................................................4
pmrep....................................................................................................................................................4
pmrepagent ...........................................................................................................................................4
Repository.............................................................................................................................................4
Usability ...............................................................................................................................................4
Designer................................................................................................................................................5
Informatica Server Enhancements..........................................................................................................5
pmrep....................................................................................................................................................5
pmrepagent ...........................................................................................................................................5
Repository Manager ..............................................................................................................................6
Repository Server..................................................................................................................................6
Transformation Language......................................................................................................................6
Workflow Manager ...............................................................................................................................6
Workflow Monitor ................................................................................................................................7
Designer................................................................................................................................................7
Informatica Server.................................................................................................................................8
Repository Manager ..............................................................................................................................9
Repository Server..................................................................................................................................9
Transformation Language......................................................................................................................9
Workflow Manager .............................................................................................................................10
Compilers for External Procedures and Advanced External Procedures ....................................................11
6.2 Bug Fixes..........................................................................................................................................11
Client..................................................................................................................................................11
1
Database and Connectivity ..................................................................................................................11
Informatica Server...............................................................................................................................12
6.1 Bug Fixes..........................................................................................................................................12
Bulk Loading ......................................................................................................................................12
Client..................................................................................................................................................13
Repository Agent and Repository Server..............................................................................................15
6.0 Bug Fixes..........................................................................................................................................15
Client..................................................................................................................................................15
Database Connectivity.........................................................................................................................15
Flat Files and COBOL.........................................................................................................................16
Third Party Limitations ...........................................................................................................................16
IBM DB2 ............................................................................................................................................16
HP-UX................................................................................................................................................18
Informix..............................................................................................................................................18
Linux ..................................................................................................................................................18
Microsoft SQL Server .........................................................................................................................18
Microsoft Windows.............................................................................................................................19
Oracle .................................................................................................................................................19
Sybase ................................................................................................................................................22
Teradata..............................................................................................................................................24
PowerCenter/PowerMart Known Limitations...........................................................................................24
Backward Compatibility......................................................................................................................24
Bulk Loading ......................................................................................................................................25
Client..................................................................................................................................................26
Database and Connectivity ..................................................................................................................29
Date Handling.....................................................................................................................................30
External Loader...................................................................................................................................30
External Procedures and Stored Procedures..........................................................................................31
Flat Files and COBOL.........................................................................................................................31
Installation ..........................................................................................................................................35
Metadata Reporter...............................................................................................................................35
Partitioning .........................................................................................................................................37
Repository Agent and Repository Server..............................................................................................38
Workflow Monitor ..............................................................................................................................39
XML...................................................................................................................................................39
Installation ..............................................................................................................................................39
PowerCenter/PowerMart Platform Components...................................................................................39
Client..................................................................................................................................................40
Repository Server................................................................................................................................40
Database Connectivity.............................................................................................................................41
Upgrading...............................................................................................................................................42
Documentation Addenda .........................................................................................................................42
All Manuals ........................................................................................................................................42
Designer Guide ...................................................................................................................................43
Installation and Configuration Guide ...................................................................................................43
Metadata Reporter Guide.....................................................................................................................44
Repository Guide ................................................................................................................................45
Supplemental Guide ............................................................................................................................46
Transformation Guide .........................................................................................................................49
Transformation Language Reference ...................................................................................................49
Troubleshooting Guide........................................................................................................................50
Workflow Administration Guide..........................................................................................................50
Contacting Informatica............................................................................................................................52
2
Note: This document summarizes revisions to PowerCenterRTTM 6.2, PowerCenter® 6.2, and PowerMart®
6.2 that do not appear in the documentation. Do not upgrade to this release from a previous version without
carefully reading the relevant sections on upgrading and bug fixes, since bug fixes may change the behavior
of existing sessions. For more complete information on the product, consult the manuals and online help.
For the final version of this document, please refer to the printed version of release notes included
with the product shipment. You can also download the final version of this document from Informatica
Corporation at http://my.Informatica.com/.
CD Contents
The PowerCenterRT 6.2/PowerCenter 6.2/PowerMart 6.2 installation CD includes the following programs
and files:
• PowerCenterRT/PowerCenter/PowerMart installation
• Metadata Reporter
• Sample Repository
• DataDirect 4.1 closed 32-bit ODBC drivers for Windows
• DataDirect 4.1 closed 32-bit ODBC drivers for UNIX
• Online versions of the manuals (Use Adobe Acrobat Reader included on the CD to view these files.)
• Release notes
Informatica Developer Network

The Informatica Developer Network is a web-based forum for third-party software developers. You can
access the Informatica Developer Network at http://devnet.informatica.com. The site contains information
on how to create, market, and support customer-oriented add-on solutions based on Informatica’s
interoperability interfaces.
Webzine
The Informatica Documentation Team delivers an online journal, the Informatica Webzine. This journal
provides solutions to common tasks, conceptual overviews of industry-standard technology, detailed
descriptions of specific features, and tips and tricks to help you develop data warehouses.
The Informatica Webzine is a password-protected site that you can access through the Customer Portal. The
Customer Portal has an online registration form for login accounts to its webzine and web support. To
register for an account, go to the following URL:
http://my.Informatica.com
If you have any questions, please email webzine@informatica.com.
To better serve your needs, the Informatica Documentation Team welcomes all comments and suggestions.
You can send comments and suggestions to: documentation@informatica.com.
Web Support
Informatica now has an online registration form for login accounts to webzine and websupport. To register
for a webzine or websupport account, go to the following URL:
If you have any questions, please email web@informatica.com.
6.2 New Features and Enhancements

This section describes new features and enhancements to PowerCenter 6.2 and PowerMart 6.2.
3
Backward Compatibility
Backward compatibility. PowerCenter 6.2/PowerMart 6.2 (version 6.2) provide backward compatibility
with PowerCenter 6.1/PowerMart 6.1 (version 6.1) client applications. You can use a version 6.1 client
application to connect to a version 6.2 repository.
Informatica Server
Partitioning enhancements. When you load to IBM DB2 tables stored on a multi-node tablespace, you
can optimize session performance by specifying the database partitioning partition type for IBM DB2
targets.
Use sorted input to optimize join performance. You can improve session performance by using sorted
data with the Joiner transformation. When you configure the Joiner transformation to use sorted data, the
Informatica Server improves performance by minimizing disk input and output.
Session recovery. You can recover failed sessions that write to relational targets. When you run a failed
session in recovery mode, the Informatica Server continues writing data to the target starting with the row
at which the previous session failed.
Linux
Linux support. The Informatica Server and Repository Server can run on Linux. On Linux, you can access
and connect to IBM DB2, Oracle, and Sybase sources, targets, and repositories using native drivers. Use
ODBC drivers to access other sources and targets.
Metadata Reporter
Custom Job Report. You can filter workflows by specifying start time and end time parameters in the
custom Job Report. The report displays workflows run between the specified start and end time. Access the
custom Job Report from the custom report menu.
pmrep
Addrepository. Use this command to add a repository configuration to the Repository Server.
Listobjects. Use this command to list objects in the repository.
Listtablesbysess. Use this command to list source and target names in a session.
Updateseqgenvals. Use this command to update some transformation properties for Sequence Generator
transformations.
pmrepagent
Bulkrestore. Use this command to restore Teradata repositories using FastLoad.
Repository
IBM DB2 EEE repositories. You can optimize repository performance when you store the repository
tables in a single-node tablespace. Specify the tablespace name when you create, copy, or restore the
repository.
Usability
Resizeable editors. You can resize the editor dialog boxes in the Workflow Manager and Designer.
4
Designer
Advanced External Procedure transformations. You can create non-reusable instances of reusable
Advanced External Procedure transformations.
Teradata database support. PowerCenter and PowerMart support Teradata as a source, target, or
repository database. You can also create Lookup and Stored Procedure transformations to access Teradata
databases.
Copy objects in the Designer workspace as an image. In the Designer workspace, you can capture an
image of objects such as mappings or source qualifiers.
Resizable edit dialog boxes. You can resize the edit dialog box when you use the Designer to modify an
object.
Informatica Server Enhancements

Cache partitioning. When you create a session with multiple partitions, the Informatica Server can
partition caches for the Aggregator, Joiner, Lookup, and Rank transformations. It creates a separate cache
for each partition, and each partition works with only the rows needed by that partition.
User-defined commits. PowerCenter and PowerMart allow you to control commit and rollback
transactions based on a row or set of rows that pass through a Transaction Control transformation. You
define transactions using an expression in the Transaction Control transformation. Based on the return
value of the expression, you can choose to commit, rollback, or continue without any transaction changes.
Write metadata to flat file targets. When you configure the Informatica Server, you can choose to write
flat file column metadata to flat file targets.
Metadata Reporter
Installation on IBM WebSphere Analytic Server. You can now install the Metadata Reporter on IBM
WebSphere Analytic Server and run it as a web application.
Installation on JRun Java Server Application. You can install the Metadata Reporter on JRun Java
Server Application and run it as a web application.
Installation on Apache Tomcat. You can install the Metadata Reporter on Apache Tomcat and run it as a
web application.
pmrep
Updatesrcprefix. Use this command to update the owner name for session source tables.
Updatetargprefix. Use this command to update the table name prefix for session target tables.
pmrepagent
Delete. Use this command to delete repository tables from the database.
Restore. Use this command to restore repositories from a repository backup file.
5
Repository Manager
File connection details. You can use the Repository Manager to view connection details for source and
target files. You can also use MX Views to view connection details for source and target files.
Repository Server Administration Console. The Repository Administration Console issues repository
administration commands through the Repository Server. Use the Administration Console to perform
repository functions, such as creating, copying, backing up, and restoring repositories.
Custom tools. The Repository Manager allows you to add custom tools to the Tools menu. This allows you
to start frequently used programs from within the Repository Manager.
Repository Server
Database connection pooling. You can specify the maximum number of connections the Repository
Server can make to the repository database.
Automatic connection closing and automatic lock release. The Repository Server automatically closes
repository connections lost due to network or system problems, and automatically releases locks held by
lost connections.
Teradata repositories. PowerCenter and PowerMart support Teradata as a repository database.
Transformation Language
Transformation language updates. Informatica updated the transformation language to increase the
precision of calculations in expressions and to improve session performance.
Workflow Manager
Copy and paste segments. You can copy segments of existing workflows or worklets into workflows and
worklets within the same folder, within another folder, or within a folder in a different repository.
Custom tools. The Workflow Manager allows you to add custom tools to the Tools menu. This allows you
to start frequently used programs from within the Workflow Manager.
Delete links in a workflow or worklet. When you edit a workflow or worklet, you can delete multiple
links at once without deleting the tasks they connect.
Highlight paths in a workflow or worklet. When you edit a workflow or worklet, you can view the
forward or backward link paths to other tasks.
Partitioned Joiner transformation. You can set a partition point at the Joiner transformation.
Partitioning enhancements. If you use PowerCenter, you can define up to 32 partitions at any partition
point in a pipeline that supports multiple partitions.
Teradata FastLoad external loader. You can use the Teradata FastLoad external loader to load data to a
Teradata database table. Use FastLoad to load data from a session with one partition to a single Teradata
database table.
Workflow Wizard. You can use the Workflow Wizard to create workflows quickly. When you use the
Workflow Wizard to create a workflow, you do not have to create sessions manually, drag sessions into the
workspace, or add links manually.
6
Workflow Monitor
Custom tools. The Workflow Monitor allows you to add custom tools to the Tools menu. This allows you
to start programs from within the Workflow Monitor that you frequently use.
Filter for Task view. The Workflow Monitor allows you to create filter settings for Task view. It stores the
filter settings, applies them each time you run the Workflow Monitor, and filters all other tasks from view.
Mark deleted workflows. The Workflow Monitor marks deleted workflows in Task and Gantt Chart
views.
Task release. You can release tasks from memory without switching to offline mode.

Designer
Compare objects. The Designer allows you to compare two repository objects of the same type to identify
differences between them. You can compare sources, targets, transformations, mapplets, mappings,
instances, or mapping/mapplet dependencies in detail. You can compare objects across open folders and
repositories.
Copying objects. In each Designer tool, you can use the copy and paste functions to copy objects from one
workspace to another. For example, you can select a group of transformations in a mapping and copy them
to a new mapping.
Custom tools. The Designer allows you to add custom tools to the Tools menu. This allows you to start
programs you use frequently from within the Designer.
Flat file targets. You can create flat file target definitions in the Designer to output data to flat files. You
can create both fixed-width and delimited flat file target definitions.
Heterogeneous targets. You can create a mapping that outputs data to multiple database types and target
types. When you run a session with heterogeneous targets, you can specify a database connection for each
relational target. You can also specify a file name for each flat file or XML target.
Link paths. When working with mappings and mapplets, you can view link paths. Link paths display the
flow of data from a column in a source, through ports in transformations, to a column in the target.
Linking ports. You can now specify a prefix or suffix when automatically linking ports between
transformations based on port names.
Lookup cache. You can use a dynamic lookup cache in a Lookup transformation to insert and update data
in the cache and target when you run a session.
Mapping parameter and variable support in lookup SQL override. You can use mapping parameters
and variables when you enter a lookup SQL override.
Mapplet enhancements. Several mapplet restrictions are removed. You can now include multiple Source
Qualifier transformations in a mapplet, as well as Joiner transformations and Application Source Qualifier
transformations for IBM MQSeries. You can also include both source definitions and Input transformations
in one mapplet. When you work with a mapplet in a mapping, you can expand the mapplet to view all
transformations in the mapplet.
7
Metadata extensions. You can extend the metadata stored in the repository by creating metadata
extensions for repository objects. The Designer allows you to create metadata extensions for source
definitions, target definitions, transformations, mappings, and mapplets.
Numeric and datetime formats. You can define formats for numeric and datetime values in flat file
sources and targets. When you define a format for a numeric or datetime value, the Informatica Server uses
the format to read from the file source or to write to the file target.
Pre- and post-session SQL. You can specify pre- and post-session SQL in a Source Qualifier
transformation and in a mapping target instance when you create a mapping in the Designer. The
Informatica Server issues pre-SQL commands to the database once before it runs the session. Use pre-
session SQL to issue commands to the database such as dropping indexes before extracting data. The
Informatica Server issues post-session SQL commands to the database once after it runs the session. Use
post-session SQL to issue commands to a database such as re-creating indexes.
Renaming ports. If you rename a port in a connected transformation, the Designer propagates the name
change to expressions in the transformation.
Sorter transformation. The Sorter transformation is an active transformation that allows you to sort data
from relational or file sources in ascending or descending order according to a sort key. You can increase
session performance when you use the Sorter transformation to pass data to an Aggregator transformation
configured for sorted input in a mapping.
Tips. When you start the Designer, it displays a tip of the day. These tips help you use the Designer more
efficiently. You can display or hide the tips by choosing Help-Tip of the Day.
Tool tips for port names. Tool tips now display for port names when you edit an object in the Designer.
To view the full contents of the column, position the mouse over the cell until the tool tip appears.
View dependencies. In each Designer tool, you can view a list of objects that depend on a source, source
qualifier, transformation, or target. Right-click an object and select View Dependencies.
Working with multiple ports or columns. In each Designer tool, you can move multiple ports or columns
at the same time.
Informatica Server
Add timestamp to workflow logs. You can configure the Informatica Server to add a timestamp to
messages written to the workflow log.
Expanded pmcmd capability. You can use pmcmd to issue a number of commands to the Informatica
Server. You can use pmcmd in either an interactive or command line mode. The interactive mode prompts
you to enter information when you omit parameters or enter invalid commands. In both modes, you can
enter a command followed by its command options in any order. In addition to commands for starting and
stopping workflows and tasks, pmcmd now has new commands for working in the interactive mode and
getting details on servers, sessions, and workflows.
Error handling. The Informatica Server handles the abort command like the stop command, except it has a
timeout period. You can specify when and how you want the Informatica Server to stop or abort a
workflow by using the Control task in the workflow. After you start a workflow, you can stop or abort it
through the Workflow Monitor or pmcmd.
Export session log to external library. You can configure the Informatica Server to write the session log
to an external library.
8
Flat files. You can specify the precision and field length for columns when the Informatica Server writes to
a flat file based on a flat file target definition, and when it reads from a flat file source. You can also
specify the format for datetime columns that the Informatica Server reads from flat file sources and writes
to flat file targets.
Write Informatica Windows Server log to a file. You can now configure the Informatica Server on
Windows to write the Informatica Server log to a file.
Metadata Reporter
List reports for jobs, sessions, workflows, and worklets. You can run a list report that lists all jobs,
sessions, workflows, or worklets in a selected repository.
Details reports for sessions, workflows, and worklets. You can run a details report to view details about
each session, workflow, or worklet in a selected repository.
Completed session, workflow, or worklet detail reports. You can run a completion details report, which
displays details about how and when a session, workflow, or worklet ran, and whether it ran successfully.
Installation on BEA WebLogic. You can now install the Metadata Reporter on BEA WebLogic and run it
as a web application.
Repository Manager
extensions for repository objects. The Repository Manager allows you to create metadata extensions for
source definitions, target definitions, transformations, mappings, mapplets, sessions, workflows, and
worklets.
pmrep security commands. You can use pmrep to create or delete repository users and groups. You can
also use pmrep to modify repository privileges assigned to users and groups.
Tips. When you start the Repository Manager, it displays a tip of the day. These tips help you use the
Repository Manager more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.
Repository Server
The Informatica Client tools and the Informatica Server now connect to the repository database over the
network through the Repository Server.
Repository Server. The Repository Server manages the metadata in the repository database. It accepts and
manages all repository client connections and ensures repository consistency by employing object locking.
The Repository Server can manage multiple repositories on different machines on the network.
Repository connectivity changes. When you connect to the repository, you must specify the host name of
the machine hosting the Repository Server and the port number the Repository Server uses to listen for
connections. You no longer have to create an ODBC data source to connect a repository client application
to the repository.
Transformation Language
New functions. The transformation language includes two new functions, ReplaceChr and ReplaceStr. You
can use these functions to replace or remove characters or strings in text data.
SETVARIABLE. The SETVARIABLE function now executes for rows marked as insert or update.
9
Workflow Manager
The Workflow Manager and Workflow Monitor replace the Server Manager. Instead of creating a session,
you now create a process called a workflow in the Workflow Manager. A workflow is a set of instructions
on how to execute tasks such as sessions, emails, and shell commands. A session is now one of the many
tasks you can execute in the Workflow Manager.
The Workflow Manager provides other tasks such as Assignment, Decision, and Event-Wait tasks. You can
also create branches with conditional links. In addition, you can batch workflows by creating worklets in
the Workflow Manager.
IBM DB2 external loader. You can use the DB2 EE external loader to load data to a DB2 EE database.
You can use the DB2 EEE external loader to load data to a DB2 EEE database. The DB2 external loaders
can insert data, replace data, restart load operations, or terminate load operations.
Environment SQL. For relational databases, you may need to execute some SQL commands in the
database environment when you connect to the database. For example, you might want to set isolation
levels on the source and target systems to avoid deadlocks. You configure environment SQL in the
database connection. You can use environment SQL for source, target, lookup, and stored procedure
connections.
Email. You can create Email tasks in the Workflow Manager to send emails when you run a workflow.
You can configure a workflow to send an email anywhere in the workflow logic, including after a session
completes or after a session fails. You can also configure a workflow to send an email when the workflow
suspends on error.
Flat file targets. In the Workflow Manager, you can output data to a flat file from either a flat file target
definition or a relational target definition.
Heterogeneous targets. You can output data to different database types and target types in the same
session. When you run a session with heterogeneous targets, you can specify a database connection for
each relational target. You can also specify a file name for each flat file or XML target.
extensions for repository objects. The Workflow Manager allows you to create metadata extensions for
sessions, workflows, and worklets.
Oracle 8 direct path load support. You can load data directly to Oracle 8i in bulk mode without using an
external loader. You can load data directly to an Oracle client database version 8.1.7.2 or higher.
Partitioning enhancements. To improve session performance, you can set partition points at multiple
transformations in a pipeline. You can also specify different partition types at each partition point.
Server variables. You can use new server variables to define the workflow log directory and workflow log
count.
Teradata TPump external loader. You can use the Teradata TPump external loader to load data to a
Teradata database. You can use TPump in sessions that contain multiple partitions.
Tips. When you start the Workflow Manager, it displays a tip of the day. These tips help you use the
Workflow Manager more efficiently. You can display or hide the tips by choosing Help-Tip of the Day.
Workflow log. In addition to session logs, you can configure the Informatica Server to create a workflow
log to record details about workflow runs.
10
Workflow Monitor. You use a tool called the Workflow Monitor to monitor workflows, worklets, and
tasks. The Workflow Monitor displays information about workflow runs in two views: Gantt Chart view or
Task view. You can run, stop, abort, and resume workflows from the Workflow Monitor.
Compilers for External Procedures and Advanced

External Procedures
You can use the following C compiler versions (or later) for both External Procedures and Advanced
External Procedures:
• HP: HP ANSI C++, bundle number B3910B, version A.03.10
• AIX: Visual Age C++ compiler, version 5.0

If you are upgrading from a version prior to PowerCenter 6.0/PowerMart 6.0, you must upgrade the
external procedure and recompile it.
• NT: VC++ 6.0, cl version 12.00.8168
• Solaris: Forte 6 Update 2, C++ patch 111685-07

If you are upgrading from a version prior to PowerCenter 6.1/PowerMart 6.1, you must upgrade the
external procedure and recompile it.
• Linux: g++ version 2.96 20000731
6.2 Bug Fixes

The following issues are corrected in PowerCenter 6.2 /PowerMart 6.2. Most of the listed corrections were
found through in-house testing and are unlikely to affect most users. They are listed here for your
information.
Client
Fixed CR 47089: Designer no longer shuts down unexpectedly when you export a mapplet
with a Router transformation or run a session with a mapplet containing a Router
transformation
In a previous release, the Designer shut down unexpectedly when you exported a mapplet with a Router
transformation to an XML file or when you ran a session with an exported mapplet containing a Router
transformation. This happened after you replaced the Router transformation in the mapplet with a Router
transformation with the same name, but different ports.
This no longer occurs.
Database and Connectivity

Fixed CR 44002: Repository no longer shuts down when copying a repository from
Teradata to DB2
In a previous release, if you copied a repository on an HP-UX or AIX Teradata database to DB2, the
Repository Agent managing the Teradata repository may have shut down.
Fixed CR 43387: Informatica Server on AIX no longer fails session accessing DB2 and
ODBC
In a previous release, the Informatica Server on AIX failed sessions with database errors under the
11
following conditions:
• The session read from the source through ODBC and wrote to a DB2 target.
• The session read from a DB2 source and wrote to the target through ODBC.
• The repository was on an IBM DB2 database and the session read from the source through ODBC and
wrote to the target through ODBC.
Fixed CR 35867: Informatica Server on HP-UX no longer fails session accessing DB2 and
ODBC
In a previous release, the Informatica Server on HP-UX failed sessions with database errors under the
following conditions:
• The session read from the source through ODBC and wrote to a DB2 target.
• The session read from a DB2 source and wrote to the target through ODBC.
• The repository was on an IBM DB2 UDB database and the session read from the source through
ODBC and wrote to the target through ODBC.
Informatica Server
Fixed CR 48354, 47248: Informatica Server Load Manager process no longer aborts
unexpectedly if you delete transformation used by a shortcut
In a previous release, if you deleted the transformation referenced by a shortcut in a mapping and then
saved the repository, the Informatica Server unexpectedly aborted the Load Manager process when you
tried to run a session using the mapping.
Fixed CR 47224: Informatica Server no longer generates a core file when performing full
outer join, detail outer join, or master outer join
In a previous release, the Informatica Server generated a core file when performing a full outer join or
detail outer join under the following conditions:
• The detail source contained no data.
• The join condition contained a String or Binary port.
• An Expression transformation immediately followed the Joiner transformation in the mapping.
The Informatica Server may have also generated a core file when performing a master outer join when the
master source contained no data.
6.1 Bug Fixes

information.
Bulk Loading
Fixed CR 5429: Errors no longer occur when bulk loading NULL dates to Microsoft SQL
Server targets with multiple date fields
In a previous release, if you ran a session for which all of the following were true, you might have found
inconsistent data in date fields:
• The session wrote to a Microsoft SQL Server target containing multiple date fields.
• You passed data with NULL date fields.
12
• You set the session for bulk mode.
Client
Fixed CR 41357: Designer can now import a target from an XML file that has both indexes
and metadata extensions
In a previous release, when you exported a target definition that contained both indexes and metadata
extensions to an XML file, and then imported the file, the Designer displayed an error message.
Fixed CR 5620: Precision no longer lost when you divide floating point numbers
In a previous release, if you wrote an expression that divided a floating point number by an integer, the
Informatica Server might have returned a result with incorrect precision. This occurred when the floating
point number in the numerator was of high precision. For example, if the numerator was a floating point
number with a precision of 19 and the divisor was an integer, the output was of precision 16 rather than the
expected 19.
Informatica Server
Fixed CR 46519: The Informatica Server no longer produces numeric overflow in some
decimal calculations
In a previous version, the Informatica Server produced numeric overflow in some decimal calculations.
For example, you have the following expression in a decimal port with precision 10 and scale 5:
(1.123456789 - 1234567890) * 0
In previous versions, the Informatica Server produced an overflow. Now, the Informatica Server returns the
correct value, 0.
Fixed CR 46517: The Informatica Server now detects numeric overflow when performing
integer calculations
In a previous version, the Informatica Server returned the maximum integer or minimum integer value in
some integer calculations instead of producing numeric overflow.
Integer calculations overflow when their results return values greater than the maximum or less than the
minimum integer values (2,147,483,647 and -2,147,483,648, respectively). If you created an expression
that produced integer overflow, the Informatica Server rounded the calculation result to the maximum or
minimum integer value.
This no longer occurs. If the expression result is out of range, the Informatica Server produces numeric
overflow.
For example, you have the following expression:
(2,147,483,647 - 2) + 3
13
Effective in version 6.1, this expression produces numeric overflow. In previous versions, this expression
returned 2,147,483,647.
Fixed CR 46336: The Informatica Server now evaluates ‘inf’, ‘-inf’, ‘NaN’, and ‘-NaN’ in test
and conversion functions as non-numeric strings
In a previous version, the Informatica Server evaluated the strings ‘inf’, ‘-inf’, ‘NaN’, and ‘-NaN’ in test
and conversion functions differently, depending on the function and platform.
This no longer occurs. Effective in version 6.1, the Informatica Server evaluates ‘inf’, ‘-inf’, ‘NaN’, and
‘-NaN’ in the following functions as non-numeric strings:
• IS_NUMBER
• TO_DECIMAL
• TO_FLOAT
• TO_INTEGER
Fixed CR 11256: No delay in scheduled sessions

In a previous release, as the Informatica Server ran scheduled sessions, it went into a wait mode before it
initialized and scheduled the next session. Each wait mode lasted from 2 to 30 seconds (or more, if the
Informatica Server was extremely busy) and could delay the start of the next session.
Fixed CR 10977: Informatica Server now correctly writes values to Time fields in flat file
targets
In a previous release, the Informatica Server did not correctly write datetime values to Time fields in flat
file targets.
This no longer occurs. You can now specify the format for datetime values when you edit a port in a flat
file source or target, a flat file source instance or target instance, or a flat file source definition or target
definition.
Fixed CR 8251: TRUNC function no longer loses precision when evaluating Double
datatypes
In a previous version, if you passed ports with Double datatypes to the TRUNC function, you may lose
precision. The following example shows possible results of the expression:
TRUNC(input_field, 4)
INPUT_FIELD RETURN VALUE

700 699.9999
8000 7999.9999
This no longer occurs. The TRUNC function does not lose precision when evaluating Double datatypes.
Fixed CR 3650: Microsoft SQL Server no longer rounds numeric data differently in bulk
and normal loads
In a previous release, the Informatica Server may have returned different results when you ran a session in
bulk or normal mode. In normal mode, Microsoft SQL Server rounded up; in bulk mode, it rounded down.
This no longer occurs. Results are now consistent between normal and bulk mode. Microsoft SQL Server
now truncates the result based on the precision specified for the column. For example, Microsoft SQL
Server truncates values 0.215, 0.214, and 0.216 to 0.21 when the column is configured for a numeric value
with a precision of 2.
14
Repository Agent and Repository Server
Fixed CR 43606, 41252: Repository Agent process no longer shuts down unexpectedly on
AIX system when system locale is set to en_US
In a previous release, the Repository Agent process running on an AIX system shut down unexpectedly if
you set the system locale to en_US.
6.0 Bug Fixes

information.
Client
Fixed CR 19933: The Designer no longer fails to preview data for flat file sources
In a previous release, when you manually created a flat file source definition and previewed the data, the
preview data dialog box was empty.
Fixed CR 17581: Designer now displays correct messages when you import a global
shortcut from an XML file
In a previous release, when you imported a global shortcut from an XML file into a folder that already
contained the same global shortcut, the Designer displayed the following messages:
The mapping <mapping_name> has been modified by another user. Mapping

will be saved as INVALID.
Shortcut_To_<mapping_name> already exists. Unable to save this

mapping. Continue with save?
Now, the Designer displays the following message:
A shortcut to Shortcut_To_<mapping_name> already exists. Creating

another shortcut to the same object is not allowed.
Fixed CR 17531: Designer no longer changes an imported shortcut to an object

In a previous release, when you imported a shortcut to an object from an XML file, the shortcut became an
object. For example, a local repository contained a shortcut to the source Items called Shortcut_To_Items.
If you exported Shortcut_To_Items to an XML file and imported Shortcut_To_Items to a global repository,
the Designer converted Shortcut_To_Items to Items and imported Items into the global repository.
Now, shortcuts are properly imported.
Database Connectivity
Fixed CR 11140: Teradata as ODBC source or target no longer needs an entry in
powrmart.ini
In a previous release, before you could import sources or targets from or create targets in a Teradata
database using ODBC, you were required to manually add an entry to the powrmart.ini file.
You no longer need to add an entry to the powrmart.ini file to use Teradata as an ODBC source or target.
15
Flat Files and COBOL
Fixed CR 11161: Informatica Server no longer returns parsing errors when session reads a
COBOL file that contains tabs
In a previous release when the Informatica Server read a COBOL file that contained tabs, it returned error
messages similar to the following:
05 FILLER Error at line 16: parse error

Error: FD FILE-ONE ignored - invalid or incomplete.
Third Party Limitations

Please be aware of the following limitations related to third party and platform products that you may use
with PowerCenter 6.2 and PowerMart 6.2. If you encounter difficulties or have further questions regarding
one of these limitations, contact Informatica Technical Support and reference the CR number.
IBM DB2
CR 50375, 49780: Sessions using database partitioning may hang when the Informatica
Server loads a large number of rows to IBM DB2 targets
When the Informatica Server loads a large number of rows to an IBM DB2 target, sessions may hang when
you use the database partitioning partition type.
Workaround: Reduce the buffer block size, such as 32 KB or less. If the session still hangs, configure the
Informatica Server to perform single row inserts by adding the following entry to the pmserver.cfg file:
OptimizeDB2Write=0
For information about configuring the Informatica Server on Windows, contact Informatica Technical
Support.
CR 49362: Informatica Server fails sessions using database partitioning when the IBM DB2
table uses a Decimal or Numeric datatype for the partitioning key
When the Informatica Server loads to an IBM DB2 table, it fails the session when you use the database
partitioning partition type and the IBM DB2 table partitioning key uses either a Decimal or Numeric
datatype. The Informatica Server writes the following message to the session log:
TT_11102 Database partition router failed due to the following error

[Decimal/Numeric partition key type is not supported.].
Workaround: Use pass-through partitioning. Or, do not use Decimal or Numeric datatypes for the
partitioning key.
CR 46763: Designer does not define correct port precision when importing DB2 for AS/400
stored procedures
When you import a DB2 for AS/400 stored procedure, the Designer creates a Stored Procedure
transformation with incorrect precision for some input and output ports compared to the precision specified
in the stored procedure.
Workaround: Open the Stored Procedure transformation in the Designer and correct the precision for input,
input/output, and output ports.
16
CR 39615: Sessions load data to a locked DB2 target table on AS/400
If you do not truncate the table, you can load data to a locked DB2 target table on AS/400 because the DB2
database on AS/400 does not detect the lock. You may get inconsistent data.
CR 39427: Constraint violations cause session failure when loading to DB2 on AS/400
When loading to DB2 on AS/400 violates key constraints, the session may fail with a communication error.
The following messages might appear in the session log:
WRITER_1_1_1> WRT_8229 Database errors occurred:

[IBM][CLI Driver][AS] SQL30081N A communication error has been
detected. Communication protocol being used: "TCP/IP". Communication
API being used: "SOCKETS". Location where the error was detected:
"10.1.72.203". Communication function detecting the error: "recv".
Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001
.
.
.
WRITER_1_1_1> CMN_1022 Database driver error...
CMN_1022 [
[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
Workaround: Verify that you load primary key tables before you load foreign key tables.
CR 39101, 29118: Informatica Server reports incorrect load statistics in the session log file
for DB2 targets on AS/400 or OS/390
The Informatica Server reports incorrect load statistics in the session log file when:
• The session loads to a DB2 database on AS/400 or OS/390.
• There are DB2 errors, such as violating not null constraints.
• You configure the Informatica Serve to perform array writes.
Workaround: Add the following entry to the file pmserver.cfg on the Informatica Server:
DB2ArrayStatusPtrWorkAround=Yes
CR 38440: IBM DB2 EE db2load utility fails to load last numeric column to DB2 EE
database on UNIX
If you use the DB2 EE load utility, db2load does not convert numeric values under the following
conditions:
• You load to a DB2 EE database on UNIX.
• The numeric data is in the last column.
The DB2 EE load utility loads a null value to the database.
CR 36093: The Repository Server fails to promote a local DB2 repository after creating the
repository
When you use the Repository Server to create a DB2 repository, it fails to promote the local repository to a
global repository.
Workaround: Catalog the DB2 database as a remote node instead of a local node. For more detailed
instructions, contact Informatica Technical Support and reference Knowledge Base ID 1347.
CR 10655: Column names do not appear in the source definition when importing DB2
table aliases containing underscores (_)
When you import a DB2 table alias in the Designer, no columns appear in the source definition if the alias
name contains an underscore ( _ ).
17
Workaround: Remove the underscore from the table or alias name.
or
In the DB2 CAE Client Configuration Assistant, clear the Underscore as Wildcard option:
1. Click the Properties button for the database alias.
2. Click Settings.
3. Click Advanced.
4. Click the Optimization tab.
5. Clear the Underscore as Wildcard option.
CR 6163: Session fails for non-cached lookups on DB2

When performing a non-cached lookup on an integer value, DB2 has an upper limit of 2147483583.
Workaround: Enable caching in the Lookup transformation.
HP-UX
CR 46161: Informatica Server on HP-UX may hang when writing to flat files
When you run a flat file session against an Informatica Server on HP-UX, the Informatica Server may
hang.
Workaround: Contact HP regarding bug #JAGad68396, and install HP patch PHSS_26560.
Informix
CR 9582: Sybase and Informix string datatypes display incorrectly in the Source Analyzer
When you import a Sybase source definition with Nchar and Nvchar datatypes, the Designer displays them
as Char and Varchar. When you import an Informix source definition with Nchar datatype, the Designer
displays it as Char.
Workaround: Manually change these datatypes to Nchar and Nvarchar.
Linux
CR 48674: When sessions fail on Linux due to insufficient memory allocation, the
Informatica Server does not write a message to the session log
When a session fails to allocate enough memory, the session might terminate unexpectedly without logging
an error message. Linux does not provide an error message for the Informatica Server to log.
Workaround: While a messaging workaround is unavailable, you can modify memory allocation. Verify
that you did not over allocate memory for DTM buffer pool size or cache sizes for Joiner, Aggregator,
Sorter, Lookup, and Rank transformations. You can also increase the amount of RAM and swap space
allocated on the Informatica Server machine.
Microsoft SQL Server

CR 42355: Sessions may fail when running multiple workflows against Microsoft SQL
Server repository
Deadlocks may occur when you run multiple workflows against a Microsoft SQL Server repository. This
causes the Repository Agent to stop and sessions to hang.
Workaround: Apply Microsoft SQL Server Service Pack 2. For more information on this limitation, see
Microsoft Knowledge Base Article # 300412.
18
CR 40506: Microsoft SQL Server may not commit smalldatetime values correctly
When you use OLE DB drivers to load data from a flat file into a Microsoft SQL Server smalldatetime
field, the Informatica Server does not commit rows if it encounters any invalid smalldatetime data.
Workaround: Use one of the following workarounds:

• Verify that you load only valid data.
• Add a Router transformation to filter rows containing invalid smalldatetime values.
• Use bulk mode.
• Use an ODBC driver.
CR 40190: Repository Server may take several minutes to complete repository operations
for folders with very large sources or targets
If your repository resides on a Microsoft SQL Server database on a Windows 2000 machine, the Repository
Server may take several minutes to complete operations on folders containing multiple sources or targets
with 4,000 columns or more. These operations include opening and deleting the folder.
CR 22991: Microsoft SQL Server ODBC driver does not report decimal truncation
The Microsoft SQL Server ODBC driver does not report decimal truncation when the following conditions
are true:
• Decimal column in the source has a precision less than the length of the field.
• The session uses a Microsoft SQL 2000 ODBC call.
The Informatica Server does not report the truncation. Instead, it reads truncated data and loads it to the
target.
Workaround: Use native drivers.
CR 16959: Loading data to Microsoft SQL Server or Sybase targets in bulk mode does not
preserve primary key and foreign key relations
When the Informatica Server loads a row with a foreign constraint to a Microsoft SQL Server or Sybase
target using bulk mode, Microsoft SQL Server and Sybase allow the foreign key table to be loaded before
the primary key table. Bulk load bypasses the foreign key restraint check in the database and does not
require that the primary key be loaded. Microsoft SQL Server and Sybase SQL Server preserve primary
key-foreign key relations for normal load only.
Microsoft Windows
CR 20777: Informatica Client and Server installation fails on some Windows 2000
machines with Internet Explorer prior to version 5.5
When you install the Informatica Client or Server on some Windows 2000 machines with Internet Explorer
prior to version 5.5, the installation might fail. During installation you might get an Ikernel error or an error
message that says “Class Not Registered. No Such Interface Supported.”
Workaround: Reinstall Internet Explorer 5.5 and then install the Informatica Client or Server.
Oracle
CR 41007: Designer does not properly import Oracle tables
When you connect the Informatica Client to an Oracle database, you may encounter the following
limitations:
• If you import a definition from an Oracle 8, 8i, or 9i table that you created from the Warehouse
Designer, the Oracle client doubles the precision of Nchar and Nvarchar columns. For example, you
create a definition in the Warehouse Designer that contains a column of datatype Nchar(2), and then
generate and execute the SQL to create the table in the Oracle database. When you import the table
from the database into the Source Analyzer or Warehouse Designer, the column has precision 4.
19
• If you install an Oracle 9i client on the Informatica Client machine, and you try to import source or
target tables from an Oracle 8 or 8i database, you can import the objects successfully on the first try. If
you try to import tables a second time however, the Designer displays the following error:
REP_12001: Failed to log onto Database Server.
Workaround: You can work around the second limitation by closing and reopening the Designer between
imports.
CR 40983: Repository Agent managing repository on Oracle does not start if Repository
Agent process port number is 32768
The Repository Agent process managing a repository database on Oracle does not start if the Repository
Agent process port number is 32768.
Workaround: Configure the Repository Agent process port number to a value other than 32768.
CR 40673, 36431: Repository Agent process on UNIX shuts down unexpectedly when
running repository on Oracle 8 database
The Repository Agent process on UNIX system shuts down unexpectedly when managing a repository on
an Oracle 8 database.
Workaround: Apply the Oracle patch for bug 2281980 from patch set 8.1.7.3 to the database client
application on the UNIX system.
CR 38932: Informatica Server fails to connect to Oracle 9i databases running on Windows

XP
The Informatica Server fails to connect to Oracle databases under the following conditions:
• The database server is Oracle 9i running on Windows XP.
• The Informatica Server machine or Repository Server machine run Oracle 8i client.
The Informatica Server writes an error message to the session log similar to the following message:
READER_1_1_1> RR_4036 Error connecting to database

ORA-12154: TNS:could not resolve service name
Workaround: Use Oracle 9i client on the Informatica Server or Repository Server machine.
CR 38672, 36211: Oracle bulk load session fails or runs in normal mode on some versions
of Oracle
When you configure a session for bulk loading and the target database is on Oracle, the session fails when
the Oracle client version is greater than or equal to 8.1.5 and less than 8.1.7.2. When the Oracle client
version is less than 8.1.5, the session runs in normal mode.
Workaround: Apply the Oracle Threaded Bulk Mode patch (Oracle bug number 1666360), use Oracle
client 8.1.7.2 or higher, or run the session in normal mode.
CR 37460: Repository Agent shuts down unexpectedly while making concurrent

connections to an Oracle 8.1.7 repository
If you make multiple, concurrent connections to an Oracle 8.1.7 repository, the Repository Agent process
may shutdown unexpectedly. This is because the Oracle 8.1.7 client library is not thread-safe. This problem
is most likely to happen while running multiple concurrent sessions.
Workaround: Apply the Oracle patch for bug 2281980 from patch set 8.1.7.3 to the Oracle client library
used by the Repository Agent.
20
CR 35268: The Informatica Server fails to bulk load to multiple instances of the same
Oracle target
The Informatica Server fails a session under the following conditions:
• You include multiple instances of the same Oracle target table.
• You specify bulk mode for at least one target instance.
• You specify the same database connection name for all target instances.
Workaround: Specify normal mode for all instances of the same Oracle target table. Or, use different
database connection names for each target instance, specifying the same user name, password, and connect
string.
CR 35240: Oracle external loader interprets new line characters as line breaks
When reading data from fixed-width or delimited flat file sources, the Oracle SQL*Loader always
interprets new line characters as row delimiters. Therefore, you cannot use a new line character as part of
any field that converts to the String or Nstring transformation datatype. This includes the following Oracle
datatypes: Char, Long, Nchar, Nvarchar2, Varchar, and Varchar2.
CR 34337: Oracle 8i sessions running in bulk mode may fail

When running an Oracle 8i session in bulk mode, the session may fail and return one of the following
errors:
WRITER_1_1_1> CMN_1022 Database driver error...

CMN_1022 [
ORA-00600: internal error code, arguments: [kpodpmop_01], [2], [], [],
[], [],[], []
-or-
MAPPING> TE_7022 TShmWriter: Initialized

MAPPING> Sat Jan 26 13:54:45 2002
MAPPING> TE_7001 Internal error: Failed to allocate a target slot.
MAPPING> Sat Jan 26 13:54:45 2002
MAPPING> TE_7017 Failed to Initialize Server Transformation
BLK_ALL_DATATYPES1
MAPPING> Sat Jan 26 13:54:45 2002
MAPPING> TM_6006 Error initializing DTM for session...
MAPPING> TM_6020 Session [s_BULK_LONG] completed at [Sat Jan 26
13:54:45 2002]
Workaround: Run the session in normal mode.
CR 32615: Repository Agent process on Windows NT stops when it loses connection to

Oracle repository database
When the Repository Agent process on a Windows NT system is running a repository on an Oracle
database, the Repository Agent stops if it loses connectivity to the repository database. The Oracle client
library generates a heap error.
CR 15904, 14573: Using Oracle external loader requires Oracle database version 8.0.5.2.1
or higher
If you use an Oracle external loader, the session might complete, even though the external loader
encounters errors. To detect Oracle external loader errors, you must have Oracle database version 8.0.5.2.1
or higher. Please refer to Oracle bug 711642 for details. Oracle database version 8.0.5.2.1 does not support
Windows 2000.
21
CR 12367: Default packet sizes on Oracle 8 client applications can slow session
performance
With Oracle 8, the default packet sizes for SQL*Net and Net8 can slow the performance of the Informatica
Server, especially when performing updates.
Workaround: Set the SDU and TDU parameters in listener.ora and tnsnames.ora to 8KB or greater.
For example, you can configure the listener.ora file as follows:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORCL )
(ENVS='EPC_DISABLED=TRUE')
(SDU=8192)
(TDU=8192)
(ORACLE_HOME = /usr1/oracle805/8.0.5)
)
)
You can configure the tnsnames.ora file as follows:
tsoracle.world =
(DESCRIPTION =
(SDU=8192)
(TDU=8192)
(ADDRESS_LIST =
(ADDRESS = (COMMUNITY = tcp.world) (PROTOCOL = TCP)
(Host = tsoracle) (Port = 1521) )
)
(CONNECT_DATA = (SID = orcl)
)
)
For details, see Oracle Doc ID 44694.1.
Sybase
CR 39673: Sybase bulk load session fails when you specify owner ID as table name prefix
When you configure a session for bulk loading and you specify a table name prefix for the target table on
Sybase, the session fails.
Workaround: Specify the database name and the owner ID in the target instance Table Name Prefix
property. Use the following format:
dbname.ownerID
CR 33115: Session fails when Sybase IQ external loader loads to a view for a table
The Informatica Server fails the session if the Sybase IQ external loader loads data to a view for a table.
The Sybase IQ external loader can only load data to a database table.
CR 25953: Sybase IQ sessions fail when using ODBC

When you use ODBC to perform array inserts to Sybase IQ 12.4.3 on an AIX or Windows Informatica
Server, the session fails and the Sybase database server shuts down. The following message might appear
in the session log:
ERROR: Unexpected condition at

file:[d:\k2\builder\powrmart\server\dwriter\wrtfile\rejfile.cpp]
22
line:[288]. Application terminating. Contact Informatica Technical
Support for assistance.
Workaround: Configure the Informatica Server to perform single row inserts. Add the following entry to
the pmserver.cfg file:
OptimizeODBCWrite = 0
For information about configuring the Informatica Server on Windows, contact Informatica Technical
Support.
CR 17761: Informatica Server loads null values to timestamp columns when bulk loading
to Sybase
The Informatica Servers loads null values (instead of hexadecimal values) to timestamp columns in Sybase
targets when you perform the following steps:
• Create a mapping with a Sybase target that includes a timestamp column.
• Do not link any transformation ports to the timestamp column.
• Create a session with this mapping and choose bulk load.
Workaround: To load hexadecimal values to unconnected timestamp columns, use a normal load.
CR 16959: Loading data to Microsoft SQL Server or Sybase targets in bulk mode does not
preserve primary key and foreign key relations
When the Informatica Server loads a row with a foreign constraint to a Microsoft SQL Server or Sybase
target using bulk mode, Microsoft SQL Server and Sybase allow the foreign key table to be loaded before
the primary key table. Bulk load bypasses the foreign key restraint check in the database and does not
require that the primary key be loaded. Microsoft SQL Server and Sybase SQL Server preserve primary
key-foreign key relations for normal load only.
CR 14799: Informatica Server hangs if session fails using Sybase IQ external loader on
Windows
If you run the Informatica Server with default service settings, and dbisql encounters a problem that
requires desktop interaction, the Informatica Server hangs.
Workaround: Allow desktop interaction from the Informatica service. In the Informatica service property
sheet, select Log On As System account and select Allow Service to Interact with Desktop. If dbisql sends
an error message to the desktop, you can close the message box, allowing dbisql and the Informatica Server
to exit properly.
CR 13256: Sybase IQ does not support Binary, Varbinary, or Image datatypes

If you try to write binary data to Sybase IQ, the external loader fails to run the generated script and issues
the following message:
"Unknown PowerMart datatype"
This is because Sybase IQ does not support Binary, Varbinary, or Image datatypes.
CR 9582: Sybase and Informix string datatypes display incorrectly in the Source Analyzer
When you import a Sybase source definition with Nchar and Nvchar datatypes, the Designer displays them
as Char and Varchar. When you import an Informix source definition with Nchar datatype, the Designer
displays it as Char.
Workaround: You must manually change these datatypes to Nchar and Nvarchar.
23
Teradata
CR 49499, 44886: pmrepagent or pmrep on AIX generates syntax errors when running
commands for a Teradata repository database
pmrepagent or pmrep on AIX generates syntax errors when you run a command for a Teradata repository
database, even though the command succeeds. You can ignore these errors.
CR 48794: Sessions may fail when loading XML data to a Teradata database
Sessions may fail when you load XML data to a Teradata database. This occurs when the Informatica
Server loads source XML data associated with a DTD file containing more than 2,000 characters. The
session log does not indicate the reason for failure.
CR 46224: Duplicate entries in REP_SESSION_FILES and REP_SESSION_INST_FILES

when using MX Views to access Teradata repository
If you configure a session to use multiple file writers to write to the same target file, you will find duplicate
entries when you use the REP_SESSION_FILES and REP_SESSION_INST_FILES MX Views to access
metadata in a Teradata repository.
CR 46211, 45602: Invalid date/time operation error when the Informatica Server runs
uncached lookup on Teradata database
When you run a session with a mapping that uses an uncached lookup on a Teradata database, the
Informatica Server fails the session if any transformation port in the lookup condition uses a Date/Time
datatype. The Informatica Server writes the following Teradata error message to the session log:
[NCR][ODBC Teradata Driver][Teradata RDBMS] Invalid operation on an

ANSI Datetime or Interval value.
Workaround: Configure the Lookup transformation to use a lookup cache, or remove the Date/Time port
from the lookup condition.
CR 43632: Informatica Server generates core file if invalid Teradata database specified in
odbc.ini
The Informatica Server on UNIX generates a core file if the DefaultDatabase entry for a Teradata ODBC
source in the odbc.ini file specifies an invalid database.
Workaround: Edit the DefaultDatabase entry and specify a valid database.
PowerCenter/PowerMart Known Limitations

Please be aware of the following limitations that may occur when using PowerCenter 6.2 and PowerMart
6.2. If you encounter difficulties or have further questions regarding one of these limitations, contact
Informatica Technical Support and reference the CR number.
Backward Compatibility
CR 50498: Version 6.1 Administration Console displays the tablespace name for version
6.2 repositories
When you connect to a version 6.2 Repository Server with a version 6.1 Administration Console and create
a repository configuration for an IBM DB2 repository, you can specify a tablespace name. However, when
you create the repository in the database, the Repository Server creates the repository tables in the default
tablespace, not the tablespace used in the repository configuration.
Workaround: Use a version 6.2 Administration Console to create IBM DB2 repositories in a specified
tablespace name.
24
CR 49110: A version 6.1 Informatica Client does not allow you to edit a copy of a version
6.2 read-only session after you save the copy
When you use a version 6.1 Informatica Client to create a copy of a version 6.2 session or a session
configuration object, you can modify the copy. However, once you save the copy, it becomes read-only. If
you try to edit the copy, the version 6.1 Informatica Client displays the following message:
The current user does not have write permission on the current folder.
You do not have sufficient privileges to obtain a write lock on the
object.
If you disconnect and then reconnect to the folder containing the copy, you can edit the copy again.
Workaround: Upgrade to the version 6.2 Informatica Client. A version 6.2 Informatica Client allows you to
make a copy of a version 6.2 read-only session or a session configuration object and edit the copy without
disconnecting and reconnecting to the folder.
CR 49101: A version 6.1 Informatica Client does not allow you to edit comments for a
shortcut once you save the comments and disconnect from the folder containing the
shortcut
When you use a version 6.1 Informatica Client to create a shortcut to a version 6.2 read-only Joiner
transformation or a 6.2 read-only mapping containing a Joiner transformation, the Designer allows you to
add comments to the shortcut. However, when you disconnect and reconnect to the folder containing the
shortcut, the version 6.1 Informatica Client does not allow you to edit the comments. It displays the
following message:
The current user does not have write permission on the current folder.
You do not have sufficient privileges to obtain a write lock on the
object.
Workaround: Upgrade to the version 6.2 Informatica Client. A version 6.2 Informatica Client allows you to
edit the comments after reconnecting to the folder.
Bulk Loading
CR 36404: Sessions configured for bulk load run in normal mode when the Informatica
Server running on AIX loads to an Oracle database
The Informatica Server on AIX runs sessions in normal load when you configure them for bulk mode. You
might see the following error message when this occurs:
WRT_8229 Database errors occurred:

ORA-26002: Table QASRVRK2.BULK_PRIMKEY_TGT has index defined upon it.
Workaround: Edit the $ORACLE_HOME/rdbms/admin/shrept.lst file and add the following lines of text:
rdbms : OCIDirPathDataSave
rdbms : OCIDirPathFinish
rdbms : OCIDirPathFlushRow
rdbms : OCIDirPathPrepare
rdbms : OCIDirPathLoadStream
rdbms : OCIDirPathColArrayEntrySet
rdbms : OCIDirPathColArrayReset
rdbms : OCIDirPathColArrayToStream
rdbms : OCIDirPathStreamReset
Then, run genclntsh.
25
CR 34329: When running a session in bulk mode, the Informatica Server loads null values
for the default value, SYSDATE, in the Oracle target
The Informatica Server loads null values into Oracle when the following conditions are true:
• You use the Warehouse Designer to create a target definition and generate a target table on Oracle with
two fields (F1 and F2).
• You use SQL*Plus to create a third field in the target table with a date datatype and the default value
of SYSDATE.
• You run the session in bulk mode.
Workaround: Run the session in normal mode or create a column on the relational target definition with
the date datatype and the default value of SYSDATE before you generate the target table in Oracle.
Client
CR 50911: Mapping Designer may not automatically update a mapping with changes to a
mapplet
When you have recently modified a port in a mapplet, you may get the following error message when you
open a mapping that uses the mapplet:
...mapping <mapping_name> contains a mapplet with a port mismatch.
Please edit mapplet <mapplet_name>.
Workaround: To resolve the port mismatch, open the mapplet in the Mapplet Designer. Edit and save the
mapplet. Then, return to the mapping in the Mapping Designer. Changes to the mapplet appear in the
Mapplet transformation.
CR 50706: Mapping Wizard cannot import sources that use SQL keywords as column
names
The Mapping Wizard cannot import a source when a column name uses an SQL keyword. When the
Mapping Wizard encounters an SQL keyword used as a column name, it prompts you to choose another
source.
Workaround: Create the mapping using the Mapping Designer.
CR 48237: Deploy folder performance is slow in an Oracle 8.1.7.2 and lower repository
database
Performance might be slow when you deploy folders in an Oracle 8.1.7.2 and lower repository database.
Workaround: Use a later version of Oracle or update your table and index statistics. For information on
updating the index statistics, see “Tuning Repository Performance” in the Supplemental Guide.
CR 45696: Designer does not correctly import foreign key on table created in Designer
When you create a target definition, you can use the Warehouse Designer to generate and execute the SQL
code to create the target in a relational database. If you then import the table with foreign keys into the
Source Analyzer or Warehouse Designer, the Designer does not import the foreign keys correctly.
Workaround: Edit the generated SQL query before you execute it on the database. For example, you
generate the following SQL query for tables AA2 and AA1:
CREATE TABLE AA2

(
byte_1 byte(10),
decimal_5 decimal(10) NOT NULL,
varbyte_10 varbyte(10),
varchar_11 varchar(10)
)
;
26
CREATE TABLE AA1
(
byte_1 byte(10),
)
UNIQUE PRIMARY KEY (decimal_5);
ALTER TABLE AA2 ADD

FOREIGN KEY (decimal_5) REFERENCES AA1 (decimal_5);
Modify the query as follows:
CREATE TABLE AA1

(
byte_1 byte(10),
decimal_5 decimal(10) NOT NULL primary key,
);
CREATE TABLE AA2

(
byte_1 byte(10),
varchar_11 varchar(10),
foreign key (decimal_5) references AA1
);
Execute the modified query. When you import the table in the Designer, foreign key columns appear
correctly.
CR 41733: Copy Folder Wizard does not copy reusable metadata extensions
When you use the Repository Manager to copy a folder that contains a mapping with reusable metadata
extensions, the Copy Folder Wizard might not copy the metadata extensions to the target repository.
Workaround: Save the source repository before you copy the folder to the target repository. If you added
the reusable metadata extension in the Repository Manager after the last time you saved the repository, you
must edit the object in the Designer or Workflow Manager and then save the repository.
CR 41232: Changes to reusable metadata extension default values do not get updated in
the Designer or Workflow Manager
When you create a reusable metadata extension for an object in the Repository Manager and specify a
default value for the extension, objects of that type in the Designer and Workflow Manager do not always
receive changes to the metadata extension default value. For example, in the Repository Manager you
create a reusable metadata extension for targets and supply a default value for the extension. You then
create and save a target in the Designer without changing the metadata extension default value. In the
Repository Manager, you edit and save the metadata extension default value. When you reopen the
Designer, the new target contains the original metadata extension default value.
Workaround: To update the metadata extension default value, edit the target and click the Revert button on
the Metadata Extension tab.
27
CR 39192: The Designer might shut down unexpectedly when you save a large mapping
If your system does not have enough memory, importing a large mapping with the “Save MX Data” option
selected might cause the Designer to shut down unexpectedly.
Workaround: Go to Tools-Options and clear the “Save MX Data” option. Then import your mapping.
CR 37527: Workflow Manager renames or deletes only some database connections

When you rename or delete a connection, the Workflow Manager renames or deletes the connection for
source and target connections in sessions. The Workflow Manager does not rename or delete the
connection for the following session properties:
• Location Information in Lookup transformations
• Connection Information in Stored Procedure transformations
• $Source Connection Value
• $Target Connection Value
Workaround: When you delete a connection, you must manually delete the residual connection names from
the other session properties in all sessions. Also, when you rename a non-relational database connection,
you must manually rename the old connection names from the other session properties in all sessions.
To rename a relational database connection, complete the following steps:

1. Create a new relational database connection with the same connection information as the connection you
want to rename. Give it a new name.
2. Open the Workflow and verify you close all folders in the repository.
3. Choose Connections-Replace to replace the connection you want to rename with the new connection you
created.
CR 32379: Designer incorrectly imports COBOL file with signed numeric fields
When you import a COBOL file with a signed numeric column, the Designer uses an extra space of
precision for the signed character. As a result, the Informatica Server may not correctly write signed
numeric data for the target. For example, the Designer imports a PIC S9 (2) V99 with a precision of 4 and a
scale of 2. The Informatica Server writes the source value -6789 to the target as –6.78 instead of –67.89.
Workaround: Increase the precision of the signed numeric field in the COBOL source definition to
accommodate the signed character. For the above example, increase the precision to 5.
CR 19266: Designer imports Informix table without columns when table name contains
slash character (/)
The Designer might import an Informix table without columns when the table name contains the slash
character (/).
CR 17277: Retain Primary/Foreign Key relationship option fails if you do not import all
tables affected in the relationship
When you import tables with a primary/foreign key relationship into the Source Analyzer or the Warehouse
Designer, and then reimport only some of the affected tables, the Designer does not import the key
relationships. The import tables option Retain user-defined primary/foreign key relationships fails if you do
not select all affected tables.
Workaround: Reimport all tables affected by the primary key-foreign key relationship.
CR 14760: Foreign keys lost after importing shortcut to source and shortcut to target
When you import a shortcut to any folder, you lose key type information.
Workaround: To maintain key type information after you import a shortcut, save the shortcut object, and
then disconnect and reconnect to the folder in which the shortcut resides.
28
CR 13591: Unable to correctly import Sybase 12.5 database source or target with
primary-foreign key
When you use the Source Analyzer or Warehouse Designer to import a source or target definition with a
primary-foreign key from Sybase 12.5, the Designer imports the source or target with a primary key only.
CR 12114: Designer cannot create a Long Varchar column in Teradata when target
database type is ODBC
If you are loading data to a Teradata table and you configured the target definition as an ODBC database
type, you cannot use the Long Varchar datatype in the Designer.
Workaround: Configure the target definition as a Teradata database type.
or
Workaround: To use the Designer to create a Teradata table with a Long Varchar column, complete the
following steps:
1. Create a target definition in the Warehouse Designer as an ODBC database type.
2. Define the column as any datatype, for example Text.
3. Manually edit the generated SQL file and change the datatype to Long Varchar.
4. Execute the SQL file.
The target definition still displays as the datatype you specify, for example Text, but it loads correctly to
the Long Varchar datatype in Teradata.
CR 8879: Target update override statements for Sybase target table with Varchar columns
do not find matches
When you use a Varchar column in the target update override statement for Sybase target tables, the
Informatica Server does not find matches and no update takes place.
Workaround: Specify Varchar column type in the update override statement.
CR 6250: Designer does not import unique keys and referential constraints
The Warehouse Designer does not import unique keys or referential constraints on a unique key.
Workarounds: Either change the unique key to a primary key in the database before importing the target
definition, or edit the target definition after importing it.
Database and Connectivity

CR 21801: ODBC drivers do not pass truncation message to Informatica Server
If the source column size in the database is larger than the source column size in the Designer, the
Informatica Server may truncate source data without writing messages to the session log. This occurs when
you use ODBC sources, and the ODBC drivers do not pass the messages to the Informatica Server.
Workaround: Ensure that the source definition in the Designer matches the source definition in the
database.
CR 17221: Precision in Varchar columns in Sybase targets limited to a maximum of 255

characters
If you import an Oracle target with Varchar or Varchar2 columns with a precision greater than 255, you
must reduce the precision before converting the target to Sybase. For example, if you convert an Oracle
target to a Sybase target in the Warehouse Designer with a column Varchar(2000), and then generate and
execute SQL, the Designer displays the following error message:
29
[DataDirect][ODBC Sybase driver][SQL Server] Length or precision
specification 2000 is not within the range of 1 to 255.
Workaround: Reduce precision to within Sybase specifications before generating and executing SQL, or
convert to another target type that supports a precision greater than 255 for Varchar columns.
CR 3581: Money data for Informix read as 0.00 when using high precision
To prevent fields with a money datatype as being read as 0.00 when using high precision, you must set the
following environment variable for that combination:
DBMONEY=' .' (that is, a single quote followed by space character followed by a period followed by
single quote). This DBMONEY variable tells Informix to not prefix the data with the dollar sign ($) for
money data types.
In ksh and sh:
DBMONEY=' .'
export DBMONEY
In csh:
setenv DBMONEY=' .'
On Windows: Set this environment variable in the profile of the person under whose name the Informatica
service is started.
Date Handling
CR 2947: Data conversion for flat file targets and error files (Double with scale 0)
If a mapping outputs Double data to flat file targets or a session reject file (target_name.bad), the following
data conversion rules apply:
• For UNIX, the Informatica Server converts Double values to their string representation based on the
IEEE math specification of rounding a 5 up if the previous digit is odd, and rounding down if the
previous digit is even. For example, the Informatica Server rounds 0.5 to 0, 1.5 to 2, 2.5 to 2, and so
on.
• For Windows, the Informatica Server always rounds up when it converts Double values to their string
representation. For example, .5 rounds to 1, 1.5 rounds to 2, 2.5 rounds to 3, and so on.
External Loader
CR 44703, 17032: Informatica Server prints external loader user name and password in the
control file
The Informatica Server does not encrypt the database user name and password in the external loader
control file.
Workaround: You can configure the Informatica Server to write the external loader control file to a
directory separate from the target flat file. You can then configure the permissions on the control file
directory to allow access by the user starting the Informatica Server only.
To configure the Informatica Server on UNIX to write the external loader control file to a separate
directory, add the following entry to pmserver.cfg:
LoaderControlFileDirectory=<directory_name>
If you want to configure the Informatica Server on Windows to write the external loader control file to a
separate directory, please contact Informatica Technical Support.
30
CR 38627: In sessions with multiple partitions, Oracle external loaders do not commit all
rows when run in replace mode
When you run a session with multiple partitions on a Windows system where you use an Oracle external
loader connection in replace mode, the loader does not commit all of the rows to the target table. This
occurs because replace mode truncates the target table and then inserts the rows. In sessions with multiple
partitions, the process for the last partition truncates rows that the previous processes inserted. This
problem occurs on Windows systems, but not on UNIX systems.
Workaround: Perform the truncate operation as a pre-session SQL command, and configure the Oracle
external loader connection in append mode instead of replace mode.
CR 5312: External loader does not maintain key relationships when loading
External loading does not recognize key constraints when loading target files to relational tables. If you run
an external loader session with target tables with key relationships, and the tables are loaded in the wrong
order, error messages appear in the external loader log, and rejected data appears in the external loader
reject file. Errors encountered by external loaders are not reported in the session log.
External Procedures and Stored Procedures

CR 24457, 23923: Sessions with DB2 stored procedures fail if the IN/OUT parameters are
defined with Date or Time datatypes
When you import DB2 stored procedures with IN/OUT parameters defined with Date or Time datatypes,
the Designer imports them as Date/Time datatype. The session fails due to datatype incompatibility. You
will see error messages similar to the following in the session log:
TRANSF_1_1_1_1> ODL_26027 DB2 Fatal Error

ODL_26027 [FnName: ExecuteSP -- SQLSTATE=42815 [IBM][CLI
Driver][DB2/NT] SQL0171N The data type, length or value of argument "
2" of function "GET_TIMESTAMP0" is incorrect. SQLSTATE=42815
Workaround: The DB2 datatype Timestamp is a superset of Date and Time datatypes. In DB2 stored
procedures, use the Timestamp datatype to declare Date or Time datatypes for IN/OUT parameters.
CR 7730: Advanced External Procedure project files cannot be created in source file
directory (Windows servers only)
When you use the Designer to generate source files for the External Procedure or Advanced External
Procedure transformations, two of the files created are readme.txt and stdafx.h. To build the DLL for use on
the Informatica Server on Windows, you need to use Visual Studio to create a project. However, as part of
creating a new project, Visual Studio tries to generate the same two files, readme.txt and stdafx.h. If you try
to create the project file in the same directory as the source files, Visual Studio displays an error message
stating that a project already exists in that directory.
Workaround: Create the project file in a different directory from the source files.
or
Rename the readme.txt file and delete the stdafx.h file before creating the project in Visual Studio. The
readme.txt file contains information you might require. The stdafx.h file is a stub file that can be deleted.
Visual Studio generates a replacement stdafx.h file when compiling the project.
Flat Files and COBOL

CR 7843, 3537: Concatenating data from a Normalizer transformation
If you concatenate data from a Normalizer transformation, the ports you concatenate cannot include
OCCURS.
31
Informatica Server
CR 50742: Informatica Server fails session with an unsorted Aggregator transformation
connected to a multigroup target, such as an XML target
The Informatica Server fails a session when the mapping contains an unsorted Aggregator transformation
connected to a multigroup target, such as an XML target. The Informatica Server writes the following
message to the session log:
TM_6203 [ERROR: Session or its instance is not Valid...Need to

revalidate in Workflow Manager. [Summary for Aggregator AGGTRANS]
Is no longer a repartition point.
Was moved across stages. This may effect its partitioning
information.
Partition type changed from Hash Auto Keys to None.
Workaround: Close the folder and then open it. Validate the session and save it. Run the session again.
CR 46365, 46146: The Informatica Server fails to match a lookup value using
ROUND(TO_DECIMAL(string)) in a string lookup port expression in low precision mode
The upgrade process to PowerCenter 6.1/PowerMart 6.1 replaces TO_INTEGER() with
ROUND(TO_DECIMAL()). When you have ROUND(TO_DECIMAL()) in a lookup port with a String
datatype, the Informatica Server does not match the port value with a string integer value in the lookup
cache or table in low precision mode.
For example, suppose you have the following expression in a previous version of PowerCenter or
PowerMart:
TO_INTEGER(‘5.18’)
The upgrade process changes this expression to:
ROUND(TO_DECIMAL(‘5.18’))
ROUND(TO_DECIMAL()) returns values as a Double with trailing zeros in low precision mode.
Workaround: Manually change expressions in string lookup ports of a Lookup transformations. Change
ROUND(TO_DECIMAL()) to TO_INTEGER().
CR 41184: Session hangs if Sybase repository database shuts down and restarts
If the Sybase repository database server shuts down unexpectedly during a session run, the session hangs
when you restart the Sybase database server. When this happens, abort the session and restart it.
CR 38542: Informatica Server does not read rows from Oracle sources when query
override contains a question mark (?)
When you use a question mark (?) in an SQL override query against Oracle, the Informatica Server does
not read the source rows. In PowerCenter/PowerMart, the question mark (?) is a reserved character.
Workaround: Create a query using characters other than question marks.
CR 28774: Informatica Server cannot read or write Blob datatype columns on IBM DB2
databases on AS/400
The Informatica Server cannot read from or write to Blob datatype columns for IBM DB2 databases
installed on AS/400 machines.
32
CR 20729: Informatica Server truncates data greater than 2,000 characters
When you import a column with more than 2,000 characters from relational source or target, the Designer
sets the column size to 2,000. When you run a session, the Informatica Server might load truncated data or
generate an overflow error.
This behavior occurs when you import Microsoft SQL Server Text, Sybase Text, Informix Text, Oracle
Long, or DB2 LongVarchar columns.
Workaround: To ensure that the Informatica Server loads all the data in columns with more than 2,000
characters, manually increase the column size for the source and target definitions in Designer.
CR 19751: Error occurs when you send post-session email notifications using Outlook
2000
When you configure a session to send an email notification, the Informatica Server encounters an Extended
Mapi Error and does not send the email. This occurs only when Informatica Server is installed on Windows
2000.
Workaround: Stop the Informatica Server. Copy the file mapi32.dll from winnt\system32 to the bin
directory where the Informatica Server is installed, overwriting the existing mapi32.dll in that directory.
Restart the Informatica Server so that the Informatica Server can use the new mapi32.dll.
CR 17128: Session may fail when sourcing very large indirect files
If you run a session using a very large indirect file list (greater than 500 MB), depending on the memory
size of the machine server, the session may fail.
CR 16601: Update Else Insert fails when source and target columns have different widths
If you run a session with the target option Update Else Insert selected, one or more source Char(n) columns
are compared to one or more target Varchar2(m) columns without blank padding, the session fails and the
Informatica Server issues a unique constraint violation to the session log. Since the source and target
columns are a different width, the columns do not match exactly and the update fails. When the update
fails, the Informatica Server attempts to insert into the target column. Since the record already exists in the
target column, the insert fails and the Informatica Server issues the constraint violation error.
Workaround: In the Designer, use the RPAD function in the WHERE clause of the target update override.
By including an RPAD function in the WHERE clause, the Informatica Server can allow for extra spaces to
the right when comparing the char source field to the varchar2 target field. For details on using the
WHERE clause or the target update override, see “Mappings” in the Designer Guide.
CR 12074: PowerCenter does not correctly detect newline or linefeed characters with
IBM930 codepage
Compared to previous versions of Global C, the IBM930 locale file in Global C versions 3.1 and later
reversed the byte values for newline and linefeed characters. Effective with PowerCenter 5.0 and
PowerMart 5.0, the Informatica Server uses the Global C 3.0 locale file with the IBM930 (Japanese
EBCDIC) code page. As a result, the Informatica Server may not detect newline characters properly if your
data is encoded according to the Global C 3.1 format. To determine the format of your data, refer to the
following table:
Global C 3.0 Global C 3.1

byte value byte value
newline (Unicode U+0085) 0x25 0x15

linefeed (Unicode U+000A) 0x15 0x25
Workaround: The Informatica Server includes three locale files for the IBM930 code page in the
33
Informatica Server \bin\locale directory:
• cp_0930.nls. The locale file currently in use. By default, the Informatica Server uses the Global C 3.0
version of this file.
• cp_0930.nls.1. The Global C 3.0 version of the IBM930 locale file.
• cp_0930.nls.2. The Global C 3.1 version of the IBM930 locale file.
If your data is encoded according to the Global C 3.1 format, rename cp_0930.nls.2 to cp_0930.nls.
CR 11196: Informatica Server generates a Dr. Watson error when you run a test load for a
session that has multiple Redefines in the Normalizer transformation
If you are working with multibyte data and run a test load session that has multiple Redefines in the
Normalizer transformation, the Informatica Server generates a Dr. Watson error.
CR 10584: On a Japanese operating system, a session hangs when the Informatica Server
code page and the database client code page are not identical
When you load data from a Shift-JIS source into an EUC or UTF8 relational target database, the session
hangs. This is because the database client code page used by the Informatica Server and the database
connection code page are not identical.
Workaround: Make sure the database client and database connection code pages are identical. Then run the
session again.
CR 10246: Server variables on Windows are not accessible when variable assignment
contains spaces
A server variable on Windows causes an error during pre-session or post-session shell command execution
if the variable is assigned to a directory name or path containing spaces. For example, when the server
variable $PMRootDir is assigned with the value c:\temp temp, the command referencing this variable fails.
Workaround: When assigning values to server variables, which are referenced in pre-session or post-
session shell commands, make sure the directory names or paths do not contain spaces.
CR 10151: Informatica Server always performs case-sensitive string comparisons in the

Joiner transformation
The Informatica Server always performs case-sensitive string comparisons in the Joiner transformation.
The Case Sensitive String Comparison Joiner transformation option is checked by default. If you clear this
option, the Informatica Server still performs case-sensitive string comparisons.
Workaround: If you want the Informatica Server to perform case-insensitive string comparisons in the
Joiner transformation, use an Expression transformation to convert data to the same case before passing
data to Joiner transformation.
CR 8864: Sessions complete when targets do not exist

When you run a session that writes to a target table on Microsoft SQL Server, Sybase, or Oracle the
Informatica Server may complete the session even if the target table does not exist. In this case, the
Informatica Server writes an error in the session log for each row of data that belongs to the non-existent
table and writes each row into the reject file.
CR 4649: Non-printable ASCII characters handling

If a fixed-width flat file contains non-printable ASCII characters, the Informatica Server can read and
propagate those characters through the session. However, if the file contains ASCII NULLs, you may get
unexpected results.
In addition, the Flat File Wizard does not display non-printable ASCII characters.
34
Installation
CR 34887: Repository Agent process on HP-UX does not start when connecting to
repository database through Oracle 9i client
The Repository Agent process on an HP-UX system does not start when it connects to an Oracle repository
database through Oracle 9i client connectivity software.
Workaround: Add $ORACLE_HOME/lib32 to the SHLIB_PATH shared library environment variable.
CR 9218: Access denied to start Informatica Service on Windows

If you install the Informatica Server in a directory with a long path, you may get the following message
from Microsoft in the Event Viewer:
Error 0005: Access is Denied
Workaround: Uninstall PowerCenter/PowerMart and reinstall in a shorter path.
Metadata Reporter
CR 35494: Metadata Reporter cannot connect to Sybase Repository using jConnect JDBC
drivers
The Metadata Reporter cannot connect to the repository using Sybase jConnect JDBC driver version 5.x.
The Metadata Reporter returns the following message when you run the test option from the
XMXConfigServlet:
Connecting to the repository Sybase_C63125

Repository Charset:ISO-8859-1
Status:Connection failed with the following error:
java.sql.SQLException: JZ0I5: An unrecognized CHARSET property was
specified: ISO-8859-1.
The Metadata reporter uses a Unicode CHARSET and Sybase jConnect JDBC drivers do not support
Unicode.
Workaround: Specify the following parameter on the JDBC URL:
CHARSET_CONVERTER_CLASS=com.sybase.jdbc2.utils.TruncationConverter
CR 29700: XMXProperties file created on the root directory

When you configure the Metadata Reporter by running XMXConfigServlet, the file containing properties
for the Metadata Reporter, XMXProperties, is created in the bin or root directory rather than within the imr
directory.
Workaround: Modify the web.xml file to use the configFile parameter. Modify the web.xml file located in
the WEB-INF directory of the Metadata Reporter installation. Add the following sections to the web.xml
file where imr_root represents the location of the imr directory:
<servlet>
<servlet-name>XMXConfigServlet</servlet-name>
<servlet-class>XMXConfigServlet</servlet-class>
<init-param>
<param-name>configFile</param-name>
<param-value>/home/imr_root/XMXProperties.xml</param-value>
</init-param>
</servlet>
<servlet>
35
<servlet-name>XMXServlet</servlet-name>
<servlet-class>XMXServlet</servlet-class>
<init-param>
<param-name>configFile</param-name>
<param-value>/home/imr_root/XMXProperties.xml</param-value>
</init-param>
</servlet>
If you are using IBM WebSphere Application Server with the Metadata Reporter, you must modify the imr
directory files and create an imr.ear file. IBM WebSphere Application Server requires an .ear format for
deployment. To create the imr.ear file, complete the following steps:
1. Install the Metadata Reporter directory files to a temporary location. For example, install the Metadata
Reporter in the following directory:
C:\temp\imr
2. Verify that you install the Metadata Reporter directory files rather than the imr.ear file. This allows you
access to the files you need to modify.
3. Verify that you installed Java Runtime Environment version 1.3.1 or higher.
4. Modify the web.xml file as described in the workaround above.
5. From the command line, switch to the temporary directory where you installed the Metadata Reporter,
and enter the following command to create an imr.war file:
jar cf imr.war –C imr
6. Create a temporary ear subdirectory and copy the imr.war file to this directory. For example, create the
following path:
C:\temp\ear\imr.war
7. Create a META-INF subdirectory under the ear directory. For example, create the following path:
C:\temp\ear\META-INF
8. Within the META-INF directory, create an application.xml files with the following contents:
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application 1.2//EN"
"http://java.sun.com/j2ee/dtds/application_1_2.dtd">
<application>
<display-name>Informatica Metadata Reporter</display-name>
<description>Informatica Metadata Reporter</description>
<module>
<web>
<web-uri>imr.war</web-uri>
<context-root>/imr</context-root>
</web>
</module>
</application>
9. From the command line, go to the parent directory of the war file you copied. For example, if you copied
the war file into the temp directory, enter the following path:
C:\temp\
36
10. Enter the following command:
jar cf imr.ear –C ear
An imr.ear file displays in the temporary directory:
11. Install the imr.ear file into the applications directory of the IBM WebSphere Application Server
following the Metadata Reporter installation instructions provided in the Supplemental Guide.
CR 24815, 17472: Reports in Metadata Reporter for Informix repositories do not display
properly
The Metadata Reporter displays some reports incorrectly for Informix repositories:
• In the Source Schema Report and the Target Schema Report, the Description column always displays
“N/A”.
• In the Transformation Report, the Comments column for the transformation always displays “N/A”.
The Comments column for each port in the transformation displays correctly.
• In the Mapping Report, the Comments column for the mapping and for each object in the mapping
always displays “N/A”.
• In the Mapplet Report, the Comments column for the mapplet always displays “N/A”. The Comments
column for each port in the mapplet displays correctly.
• The Source to Target Dependency Report does not display correctly for Informix repositories.
CR 12069: Global shortcuts not available for some reports in Metadata Reporter
The Metadata Reporter does not display global shortcuts for the following reports:
• Source to Target Dependency Report
• Lookup Table Dependency Report
Partitioning
CR 17163: Informatica Server fails partitioned sessions with a Microsoft SQL Server
source if the partition key is of datatype Smallint
If you use partition keys of Smallint or Money datatype with a Microsoft SQL Server source, the
Informatica Server fails the session.
Workaround: In the partition properties, instead of using a key range to select data, use an SQL query.
CR 13914: Additional disk space required to realign incremental aggregation files

If you change the partitioning after you run an incremental aggregation session, the Informatica Server
realigns the aggregate files the next time you run the session. The Informatica Server requires disk space at
least twice the size of the original cache files to realign the files.
CR 12581: Associated sources do not display with partitioning keys

When you partition a Source Qualifier with an associated source that is not connected to the Source
Qualifier, you cannot create partition keys on the associated source. The Keys for Partition dialog box does
not display the associated source.
Workaround: Connect the associated source to the Source Qualifier transformation, and you can create
partition keys on that source in the session properties. You do not need to connect the output ports in the
Source Qualifier transformation to another transformation.
37
Repository Agent and Repository Server
CR 50262: Repository database password exposed during Bulkrestore operation
When you restore a Teradata repository using pmrepagent Bulkrestore, the Repository Agent creates a
control file that contains the unencrypted repository database password.
Workaround: To maintain repository security, delete the fastload.ctl file after the Bulkrestore operation
completes. You can locate the fastload.ctl file in the directory where you install the Repository Server.
CR 49383: Repository Server will not start on UNIX

The Repository Server on UNIX does not start if the soft limit for the number of files a process can have
open simultaneously is greater than the hard limit.
Workaround: Configure the hard limit for the number of files a process can have open simultaneously to a
value greater than or equal to the soft limit. Informatica also recommends configuring the maximum
number of semaphores per ID to a value greater than both limits. Configure the following kernel parameters
with the specified values:
• Maxfiles. The soft limit for the number of files a process can have open simultaneously. Configure this
parameter for 1024 files.
• Maxfiles_lim. The hard limit for the number of files a process can have open simultaneously. The hard
limit should be greater than or equal to the value specified for maxfiles. Configure this parameter for
1024 files.
• Semmsl. The maximum number of semaphores per ID. You can configure this parameter in
/usr/include/sys/sem.h. Configure this parameter for 2048 semaphores.
CR 46331: Repository Agent process cannot restore lost connection to repository

database
If the repository database server stops unexpectedly while the Repository Agent process is running and
connected to it, the Repository Agent process may not restore the repository database connection after you
restart the database server.
Workaround: Shut down the Repository Agent process by stopping the repository, and then start the
repository to restart the Repository Agent process and reestablish the connection to the repository database.
CR 44575: Deadlocks may occur when using Teradata for repository database
You may experience deadlocks when running queries or updating metadata on a Teradata repository
database. Any database access, such as queries or updates, can cause deadlock. When deadlock occurs, the
Repository Agent posts an error message to the Repository Agent log similar to the following message:
ERROR : OBJM_54543 [Tue Sep 17 16:48:42 2002] : (11203|130) DataBase
error:
FnName: Execute -- [NCR][ODBC Teradata][Teradata RDBMS] Transaction
ABORTed due to deadlock.
When deadlocks occur, the client accessing the repository may hang. Typically, the Repository Agent
continues to serve other clients.
Workaround: Retry the operation. If your client hangs, stop and restart the client.
CR 44084: Repository Server may run slowly when performing restore or copy operations
on Teradata repository database
The Repository Server may run slowly when restoring a repository backup to a Teradata database or when
copying a repository to a Teradata database.
Workaround: Use the Repository Manager to truncate the workflow logs in the repository before backing
up or copying the repository.
38
CR 41325, 41047: Repository Agent process might stop responding during repository
startup or shutdown on slower databases
If you are running a repository on a slow database, the Repository Agent process might stop responding
when you start or shut down the repository. If you shut down the Repository Server, you may not be able to
restart it.
Workaround: To restart the Repository Server, you must restart the Repository Server system.
Workflow Monitor
CR 51913: Workflow Monitor hangs when it reads a session log greater than 1 GB
When you use the Workflow Monitor to open a session log greater than 1 GB, the Workflow Monitor
hangs.
Workaround: Open the session log from a text editor.
XML
CR 17278: Japanese XML targets cannot use user-defined code pages
For Japanese XML targets, you can use only the following code pages:
• JapanEUC (Japanese Extended UNIX Code, incl. JIS X 0212)
• MS932 (Microsoft Windows Japanese, superset of Shift JIS)
You cannot use user-defined code pages such as the following:

• JEF (Japanese EBCDIC Fujitsu)
• JIPSE (NEC ACOS JIPSE Japanese)
• KEIS (Hitachi KEIS Japanese)
• MELCOM (Mitsubishi MELCOM Japanese)
• UNISYS (UNISYS Japanese)
In a session, if you select a Japanese user-defined code page for an XML target, the Informatica Server
ignores the code page. It writes a blank character encoding tag in the XML target file, as in the following
example:
<?xml version=”1.0” encoding=””?>
Since the encoding tag is required in an XML file, the target file is an invalid XML file.
Installation
PowerCenter/PowerMart Platform Components
Use the Informatica Platform Products Setup program to install PowerCenter 6.2 and
PowerMart 6.2 components
When you install Informatica PowerCenter 6.2/PowerMart 6.2 components, Informatica recommends you
use the Informatica Platform Products setup.exe program located in the \pc directory on the
PowerCenter/PowerMart installation CD. You might get unexpected results if you install a platform
component using the setup program in the component subdirectory on the installation CD.
39
Client
Displaying Help Files
To properly display the online help files on a non-U.S. English operating system, change the system locale
settings to U.S. English before installing the Informatica Server. To change the system locale, set the
Locale setting on the General tab of the Windows Regional Options control panel to English (United
States). After installation, you can change the Locale to the previous setting.
Informatica Server
Working with Null Values in Boolean Expressions
In the Designer and Workflow Manager, you may pass a null value to an expression that contains logical
operators. Effective with version 6.1, in expressions that contain the logical AND operator, combining a
null value with a Boolean expression produces the following results:
• NULL AND TRUE = NULL. This expression no longer returns FALSE.

• NULL AND FALSE = FALSE. This expression no longer returns NULL.
Note: If you want to configure the Informatica Server to use PowerCenter 6.0 and PowerMart 6.0
functionality when it evaluates null values in comparison operations, contact Informatica Technical
Support.

Installing the Informatica Server on HP-UX

If you want to run the Informatica Server on HP-UX, install HP patch PHSS_24303.
Installing the Informatica Server on Solaris

If you want to run the Informatica Server on Solaris 2.6, install patches 107733 and 105591.
If you want to run the Informatica Server on Solaris 2.7, install patches 106950 and 106327.
Installing the Informatica Server on Windows

• The name of the server in the Windows Services dialog box is called Informatica.
• Before you install or upgrade the server, make sure you have a list of all the database platform keys the
Informatica Server needs to access each source, target, and repository database.
• You must set the short date format to MM/DD/YYYY on Windows. To verify this, select Start-Settings-
Control Panel, double-click the Regional Settings icon, and then click the Date tab.
Setting Windows to boot the database before the Informatica Server

For Informatica Servers installed on Windows, you can configure the system to start the database server
before the Informatica Server during system boot. To do so, create a value DependOnService in the registry
to define the services or groups of services on which the PowerMart service depends. The value should be
of datatype REG_MULTI_SZ. To change the registry setting on Windows, contact Informatica Technical
Support.
Repository Server
40
Installing the Repository Server on UNIX

To ensure the Repository Server correctly starts on UNIX, configure the following kernel parameters with
the specified values:
• Maxfiles. The soft limit for the number of files a process can have open simultaneously. Configure this
parameter for 1024 files.
• Maxfiles_lim. The hard limit for the number of files a process can have open simultaneously. This
hard limit should be greater than or equal to the value specified for maxfiles. Configure this parameter
for 1024 files.
• Semmsl. The maximum number of semaphores per ID. You can configure this parameter in
/usr/include/sys/sem.h. Configure this parameter for 2048 semaphores.
Installing the Repository Server on HP-UX

If you want to run the Repository Server on HP-UX, install HP patch PHSS_24303.
Installing the Repository Server on Solaris

If you want to run the Repository Server on Solaris 2.6, install patches 107733 and 105591.
If you want to run the Repository Server on Solaris 2.7, install patches 106950 and 106327.
Installing the Repository Server on Windows

• The name of the server in the Windows Services dialog box is called Informatica Repository Server.
• Before you install or upgrade the server, make sure you have a list of all the database platform keys the
Informatica Server needs to access each source, target, and repository database.
• You must set the short date format to MM/DD/YYYY on Windows. To verify this, select Start-Settings-
Control Panel, double-click the Regional Settings icon, and then click the Date tab.
Database Connectivity
Informatica Server guarantees 14 digits of precision when reading numeric values from
Microsoft SQL Server
To communicate with Microsoft SQL Server databases, the Informatica Server requires the Microsoft OLE
DB Provider for SQL Server instead of the older DBLIB driver. These two drivers round numeric values
differently. The DBLIB driver guaranteed 15 digits of precision for numeric values. The OLE DB driver
guarantees 14 digits of precision for numeric values and rounds the 15th digit based on the following
criteria:
• If the 16th digit is greater than or equal to five, the Informatica Server rounds the 15th digit up.
• If the 16th digit is less than five, the Informatica Server rounds the 15th digit down.
Empty strings are no longer treated as null values in Microsoft SQL Server
To communicate with Microsoft SQL Server databases, the Informatica Server requires the Microsoft OLE
DB Provider for SQL Server instead of the older DBLIB driver. These two drivers handle empty strings
differently. The DBLIB driver treated empty strings as null values in Microsoft SQL Server databases. The
OLE DB driver treats empty strings as empty strings, not as null values.
Native drivers recommended

When possible, use native drivers rather than ODBC drivers.
Informix transaction logging

If an Informix database is used for either a repository or a target, it is important that transaction logging is
enabled to avoid data inconsistencies. Enable transaction logging for each repository database. Perform a
level-0 archive using ontape. The syntax is:
ontape -s -B <dbname>
41
This command performs the archive and turns buffered logging on at the same time.
Microsoft SQL Server Service Pack

If you use Microsoft SQL Server 7.0, you must install the Microsoft SQL Server 7.0 client and the
Microsoft SQL Server Service Pack 1 or above on each client, server, and repository machine. If you do not
install SQL Server Service Pack 1 or above, you can cause repository inconsistencies.
Upgrading
Unlock all Repository Objects
Before upgrading to PowerCenter 6.2 or PowerMart 6.2, make sure no sessions, workflows, or batches are
running on the Informatica Server and no users are connected to the repository, then unlock all repository
objects.
Repository Upgrade Duration

If you are upgrading from PowerCenter 5.0/5.1/6.0 or PowerMart 5.0/5.1/6.0, the upgrade process must
fetch, examine, and modify a large number of objects in the repository in order to make existing
expressions compatible with updates to the transformation language. Also, if you are upgrading from
PowerCenter 5.0/5.1 or PowerMart 5.0/5.1, the upgrade process must fetch each session and batch and
upgrade it to the workflow model. Depending on the size of your repository, these processes can take
significant time to complete.
During the upgrade process, you can monitor the progression of incremental changes to the repository in
the Activity Log. The Activity Log window refreshes periodically during the upgrade process.
Beta Repositories
Repositories created with a Beta release should not be used after the completion of the program. You
should use the final release to create new repositories. Do not continue to use Beta repositories in either
production or development.
CR 39802: Upgrade process does not upgrade server names

When you upgrade from a version prior to PowerCenter 6.0/PowerMart 6.0, the upgrade process does not
upgrade the Informatica Server name if it contains one of the following characters:
! @ # $ % ^ & ( ) { } [ ] < > , ? | \ " ; : ~ ' * / - <space>
After you upgrade, you must edit the Informatica Server name in the Workflow Manager to remove the
special characters.
Documentation Addenda
The following section contains additional information not included in the printed version of the
PowerCenter and PowerMart manuals, versions 6.0, 6.1, and 6.2. This section also contains information
about new features or changes in functionality introduced in PowerCenter/PowerMart versions 6.1 and 6.2
that is not included in the printed version of the manuals.
All Manuals
Copyright Page
Additional information for the copyright page of each PowerCenter 6.0 and PowerMart 6.0 manual:
Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his
research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all
rights reserved.
42
Designer Guide
Chapter 4: Working with Flat Files (Defining Default Datetime and Numeric Formats)
The following text adds to the information for defining default datetime and numeric formats.
When you edit flat file source definitions in the Source Analyzer and flat file target definitions in the
Warehouse Designer, you can define formats for datetime values. Use the Datetime Format field on the
Properties tab to define formats for datetime values.
Chapter 5: XML Concepts (Metadata from XML, DTD, and XML Schema Files)
The following text adds to the information on creating metadata for source and target definitions from
XML, DTD, or XML schema files.
Note: If you have problems importing an .xsd file, you can create metadata for source or target definitions
by creating an XML file that fully represents and conforms to the .xsd file. After you create the sample
XML file, you can import it into the Designer.
Chapter 6: Working with XML Sources (Importing an XML Source Definition)

The following text adds to the information on importing an XML source definition.
Note: If you import circular references in an XML file, verify that you do not specify a circular reference
count lower than the number of circular references in the source file. If you specify a lower count, you may
lose data.
Appendix A: Datatype Reference (Comparing Native and Transformation Datatypes)

The following text replaces the information on XML binary datatype support:
Table A-15. XML and Transformation Datatypes

Datatype Transformation Range
binary Text 1 to 65,535 characters
Installation and Configuration Guide

Chapter 4: Installing and Configuring the Informatica Client (Step 1. Installing ODBC
Drivers)
The PowerCenter 6.2/PowerMart 6.2 ODBC installation program no longer installs Merant 3.7 closed
ODBC drivers. It now installs DataDirect 4.1 closed ODBC drivers.
Chapter 5: Installing and Configuring the Windows Repository Server (Installing the
Repository Server)
The following text provides additional information for the Repository Server installation instructions on
page 82:
If you want to reinstall the Repository Server, you must shut down the existing Repository Server service
before you run the Repository Server installation program.
Chapter 6: Installing and Configuring the UNIX Repository Server (Installing the
Repository Server)
The following text provides additional information for the Repository Server installation instructions on
page 101:
If you want to reinstall the Repository Server, you must shut down the existing Repository Server before
you run the Repository Server installation program.
43
Chapter 6: Installing and Configuring the UNIX Repository Server (Step 2. Configuring the
Repository Server on UNIX)
Repository Server configuration parameters are case insensitive.
Chapter 9: Installing and Configuring the Informatica UNIX Server (Step 2. Configuring the
Informatica Server on UNIX)
Informatica Server configuration parameters are case insensitive.
Metadata Reporter Guide

Chapter 3: Installing on WebLogic Under UNIX (Step 2. Configuring the WebLogic Server)
The following text replaces steps 4-7 for configuring the BEA WebLogic 6.1 installation to work with the
Metadata Reporter.
4. Copy the database drivers associated with your PowerCenter/PowerMart repository into the library
directory of the server hosting Metadata Reporter. The directory below shows the default location of the
WebLogic library directory.
/<WebLogic_installation_path>/wlserver6.1
5. Locate the startWebLogic.sh file, and open the file for editing. The following path shows the location of
the startWebLogic.sh file when you choose default settings during the WebLogic installation.
/<WebLogic_installation_path>/wlserver6.1/config/mydomain
6. Modify the classpath to include the .jar file and the JDBC drivers you copied into the WebLogic library
directory. Place the .jar file at the beginning of the classpath. The following classpath shows the .jar file
and the JDBC drivers:
CLASSPATH==.;./lib/CR064391_rel610sp2.jar;./lib/j2ee12.jar;./
lib/weblogic_sp.jar;./lib/weblogic.jar;./$WL_HOME:$WL_HOME/lib/weblogi
c_sp.jar:$WL_HOME/lib/weblogic.jar:$WL_HOME/lib/db2java.zip:$WL_HOME/l
ib/runtime.zip:$WL_HOME/lib/classes111.zip:$WL_HOME/lib/nls_charset11.
zip:$WL_HOME/lib/ifxjdbc.jar:$WL_HOME/lib/ifxjdbc-
g.jar:$WL_HOME/lib/jconn2.jar:
7. Save changes to the WebLogic.sh file.
Chapter 4: Configuring the Metadata Reporter (Configuring Locations Settings)

The following text adds to the information on specifying the URL for the Metadata Reporter document
directory:
1. To start the Metadata Reporter setup, open the following URL in your web browser:
http://<host_name>:<webserver_port>/imr/XMXConfigServlet
2. In the Locations section, specify the URL for the Metadata Reporter document directory.
You can enter the Metadata Reporter document directory URL either as a full URL that includes the
web server address or as a relative URL. Informatica recommends that you use the relative URL.
Make sure that the full or relative URL ends in a forward slash (…/).
• Full URL. Enter the web server address and the Metadata Reporter document directory using the
following syntax:
44
http://<host_name>:<webserver_port>/imr/
• Relative URL. Enter the Metadata Reporter document directory relative to the web server address:
/imr/
Chapter 6: Understanding the Report Details (Metadata Extensions Report)

The Metadata Extensions Report provides information about metadata extensions associated with the
objects in your repository. Informatica allows end users and partners to extend the metadata stored in the
repository by associating information with individual objects in the repository. The Metadata Extensions
Report contains the following sections:
• Metadata Extension Domains. Lists and describes the metadata extension domains in the repository.
You can drill down on any domain to see the extensions defined for the domain. You can also view the
extension’s values and where it is used in the repository.
• Target Extensions. Provides the metadata extension information associated with the target.
• Transformation Extensions. Provides the metadata extension information associated with
transformations and mapplets.
• Source Extensions. Provides the metadata extension information associated with the source.
• Mapping Extensions. Provides the metadata extension information associated with the mapping.
• Session/Workflow Extensions. Provides the metadata extension information associated with the
session, workflow, or worklet.
Chapter 6: Understanding the Report Details

The following text adds to the information on understanding report details in the Metadata Reporter:
Custom Job Report. You can filter workflows by specifying start time and end time parameters in the
custom Job Report. The report displays workflows run between the specified start and end time. Access the
custom Job Report from the custom report menu.
To run the custom Job Report, enter a start time and end time using the following format: YYYY-MM-DD
HH:MM:SS.
You must enter a start time that is prior to the start time for the workflows you want to display. For
example, if you want to display workflows that ran starting on 2002-09-18 15:33:47, enter the following
start time: 2002-09-18 15:33:46.
You must enter an end time that is after the end time for the workflows you want to display. For example, if
you want to display workflows that ran ending on 2002-09-18 15:33:47, enter the following end time:
2002-09-18 15:33:48.
Repository Guide
Chapter 9: Using Metadata Exchange (MX) Views (MX Views Field-Level Summary)
The following text adds to the field-level summaries of REP_SESS_LOG and REP_SESS_TBL_LOG.
The following field definitions modify the summary of REP_SESS_LOG:
Column Name Datatype Description

SUCCESSFUL_ROWS NUMBER Number of successfully loaded target rows.
FAILED_ROWS NUMBER Number of failed target rows.
SUCCESSFUL_SOURCE_ROWS NUMBER Number of successfully read source rows.
FAILED_SOURCE_ROWS NUMBER Number of failed source rows.
45
The following field definitions modify the summary of REP_SESS_TBL_LOG:
Column Name Datatype Description

SUCCESSFUL_ROWS NUMBER Number of successfully loaded target rows.
SUCCESSFUL_AFFECTED_ROWS NUMBER Number of affected target rows.
Chapter 10: Using pmrep (Specifying Options and Arguments)

The following text replaces information about enclosing pmrep arguments in quotes:
If any argument for an option or command contains more than one word, you must enclose the argument in
double quotes. pmrep does not recognize back quotes. pmrep ignores quotes that do not enclose an
argument.
Chapter 10: Using pmrep (pmrep Repository Commands)

The following text adds to the information about replacing connections using the Switchconnection
command:
To replace connections with pmrep, you must have Super User privilege.
When you use Switchconnection, the Repository Server replaces the relational database connections for all
sessions using the connection in one of the following locations:
• Source connection
• Target connection
• Location Information property in Lookup transformations
• Connection Information property in Stored Procedure transformations
• $Source Connection Value session property
• $Target Connection Value session property
If the repository contains both relational and application connections with the same name, the Repository
Server only replaces the relational connection when you specified the connection type as relational in all
locations in the repository.
For example, you have a relational and an application source, each called ITEMS. In a session, you
specified the name ITEMS for a relational source connection instead of Relational:ITEMS.
When you use Switchconnection to replace the relational connection ITEMS with another relational
connection, pmrep does not replace any relational connection in the repository because it cannot determine
the connection type for the source connection entered as ITEMS.
Supplemental Guide
Chapter 2: Installing and Configuring PowerCenter and PowerMart
The following text adds to information in Configuring the Informatica Server on UNIX:
If you run a session configured to connect to both an ODBC and a Teradata source or target, you must
specify the Teradata libraries after the ODBC libraries in the shared library environment variable.
Chapter 7: Working with Teradata (Configuring Teradata Connectivity)

The following text adds to information in Step 4 of the procedure for connecting the Informatica Server on
UNIX to Teradata databases:
If you also want to configure Informatica Server to read from ODBC sources or write to ODBC targets,
specify the Teradata libraries after the ODBC libraries in the shared library environment variable.
46
Chapter 20: Error Messages
The following text adds to error messages. Some of the following messages appear at the command line
when you use pmrep and some appear in the session log when you run a session:
Please specify folder version in the valid format (e.g. 1.2.3).
Cause: In the pmrep Updateseqgenvals command or Listobjects command, you entered an

invalid format for the folder version argument.
Action: Specify the folder version in the correct format. For example, you could specify version
1.0.0.
Failed to find sequence <Sequence Generator transformation name>.
Cause: The Sequence Generator transformation specified in the pmrep Updateseqgenvals

command does not exist. Or, you specified a shortcut to a Sequence Generator
transformation.
Action: When you use Updateseqgenvals, verify you specify a Sequence Generator
transformation that exists in the specified mapping, folder, and folder version. Also, do
not specify a shortcut to a Sequence Generator transformation.
Failed to find mapping <mapping name>.
Cause: The mapping specified in the pmrep Updateseqgenvals command does not exist. Or, you
specified a shortcut to a mapping.
Action: When you use Updateseqgenvals, verify you specify a mapping that exists in the
specified folder and folder version. Also, do not specify a shortcut to a mapping.
Failed to update sequence <Sequence Generator transformation name>.
Cause: pmrep failed to update the sequence values for the Sequence Generator transformation
specified in the Updateseqgenvals command.
Action: View the other error messages to find the cause of the error.
Please specify a reusable or non-reusable sequence. Do not specify an instance of a reusable

sequence.
Cause: In the pmrep Updateseqgenvals command, you entered an instance of a reusable

Sequence Generator transformation.
Action: Specify a reusable Sequence Generator transformation or a non-reusable Sequence

Generator transformation. You cannot update an instance of a reusable Sequence
Generator transformation.
47
The specified object type <object type> is not recognized by listobjects.
Cause: In the pmrep Listobjects command, you entered an invalid value for the object type
argument.
Action: Specify a valid object type in the Listobjects command. You can specify folder,
transformation, or session.
The specified transformation type <transformation type> is not recognized by listobjects.
Cause: In the pmrep Listobjects command, you entered an invalid value for the transformation
type argument.
Action: Specify a valid transformation type in the Listobjects command. For a list of
transformation types, see “Using pmrep and pmrepagent Commands” in the
Supplemental Guide.
The object type <object type> requires some options to be specified but they are missing.
Cause: In the pmrep Listobjects command, you did not specify some required arguments.
Action: Enter all required arguments for the specified object type in the Listobjects command.
For a list of required arguments, see “Using pmrep and pmrepagent Commands” in the
Supplemental Guide.
Failed to list the objects requested.
Cause: pmrep failed to list the objects specified in Listobjects.
Action: View the other error messages to find the cause of the error.
The specified table type <table type> is not recognized by listtablesbysess.
Cause: In the pmrep Listtablesbysess command, you entered an invalid value for the table type
argument.
Action: Specify source to list sources, or specify target to list targets.
CMN_1769 Inconsistent recovery cache.
Cause: The Informatica Server cannot run the session enabled for recovery because the recovery
cache file does not contain valid data.
Action: Delete all recovery cache files associated with the session and run the session normally to
create a new cache file. To determine which recovery cache file is associated with the
session, compare the time at which the file was last modified with the time the session
failed. If the times are the approximately the same, you can associate the cache file with
the session.
You can also refer to the cache file names to determine which files are associated with
the session. Recovery cache file names use the following format:
pmgmd_metadata_<repository ID>_<workflow ID>_<folder ID>_<session
ID>_<transformation ID>_<partition ID>_<group ID>_<checkpoint
ID>_<sequence number>.dat
48
For example, in the following file name, the session ID is 102:
pmgmd_metadata_7661f424_379f_11d7_947e_f63b53abfef7_103_2_102_0_0_
0_1_1.dat
Use the REP_LOAD_SESSIONS MX View on the repository database to determine the
name of the session associated with the session ID. You can use
REP_LOAD_SESSIONS to view information about reusable sessions.
ODL_26071 Graphic/vargraphic partition key types are supported only on servers with
UNICODE data movement enabled.
Cause: You ran a session using database partitioning on an Informatica Server running in ASCII
mode and the IBM DB2 target table uses a partitioning key with either a Graphic or
Vargraphic column.
Action: Run the session on an Informatica Server in Unicode mode.
TM_6326 Connection <connection name> is an invalid database partition connection type.
Cause: The Informatica Server failed the session because it cannot load to the target type using
database partitioning.
Action: Use pass-through partitioning for targets that do not support database partitioning.
Transformation Guide
Chapter 4: External Procedure Transformation (Developing Informatica External
Procedures)
The following text adds to information about the runtime location when developing Informatica-style
external procedures:
You must copy all DLLs or shared libraries to the runtime location or to the environment variable defined
on the Informatica Server machine. The Informatica Server fails to load the external procedure when it
cannot locate the DLL, shared library, or a reference file.
Transformation Language Reference

Chapter 6: Functions (SQRT, INSTR, and SUBSTR)
The following text replaces text in the SQRT(), INSTR() and SUBSTR() sections of the chapter:
SQRT()
The following text replaces the description of SQRT().
SQRT() returns the square root of a non-negative numeric value.
INSTR()
The following text replaces the example using nested INSTR() functions in SUBSTR().
The following expression strips out the character ‘#’ from a string:
SUBSTR( CUST_ID, 1, INSTR(CUST_ID, ’#’)-1 ) ||

SUBSTR( CUST_ID, INSTR(CUST_ID, ’#’)+1 )
SUBSTR()
The following text replaces the example using nested INSTR() functions in SUBSTR().
49
The following expression strips out the character ‘#’ from a string:
SUBSTR( CUST_ID, 1, INSTR(CUST_ID, ’#’)-1 ) ||

SUBSTR( CUST_ID, INSTR(CUST_ID, ’#’)+1 )
Troubleshooting Guide
For updated troubleshooting messages, please refer to “Error Messages” in the PowerCenter 6.2/PowerMart
6.2 Supplemental Guide.
Chapter 11: ES Messages

All ES code messages are now RS code messages.
Chapter 20: REP Messages

The following information replaces the text for REP_12328:
REP_12328 The repository at this location does not have the same name.
Cause: Either the database connection or the repository name entered is incorrect.
Action: The status bar displays the correct repository name. Correct the inaccurate information.
or
Cause: You tried to connect to a repository on the network, but there was a network failure
during the connect process.
Action: Verify that the Informatica Client and the repository are connected to the network. When
you connect to the repository again, enter the host name and port number of the
repository in the Connect to Repository dialog box.
Workflow Administration Guide

Chapter 2: Configuring the Workflow Manager (Replacing a Relational Database
Connection)
The following text adds to the information about replacing relational database connections in the Workflow
Manager:
To replace connections in the Workflow Manager, you must have Super User privilege.
When you replace database connections, the Workflow Manager replaces the relational database
connections in the following locations for all sessions using the connection:
• Source connection
• Target connection
• Location Information property in Lookup transformations
• Connection Information property in Stored Procedure transformations
• $Source Connection Value session property
• $Target Connection Value session property
If the repository contains both relational and application connections with the same name, the Workflow
Manager only replaces the relational connection when you specified the connection type as relational in all
locations in the repository.
50
For example, you have a relational and an application source, each called ITEMS. In one session, you
specified the name ITEMS for a source connection instead of Relational:ITEMS.
When you replace the relational connection ITEMS with another relational connection, the Workflow
Manager does not replace any relational connection in the repository because it cannot determine the
connection type for the source connection entered as ITEMS.
Chapter 4: Working with Workflows (Running the Workflow)

The following text adds to the information about assigning the Informatica Server to workflows in the
Workflow Manager.
To assign the Informatica Server to workflows, you must have Super User privilege.
Chapter 10: Pipeline Partitioning (Pipeline Partitioning Overview)

In previous releases of PowerCenter, you could create up to 16 partitions at any partition point in each
pipeline in a mapping. In PowerCenter 6.2, you can create up to 32 partitions. For more information on the
restrictions on the number of partitions, see “Pipeline Partitioning” in the Workflow Administration Guide.
Chapter 12: Monitoring Workflows (Using the Workflow Monitor)

The following text adds to the information on opening and closing folders in the Workflow Monitor.
To view folder contents in the Workflow Monitor, you must have one of the following sets of permissions
and privileges:
• Super User privilege
• Read permission
Chapter 14: Log Files

The following text replaces the text in the second and third rows of the workflow log options table on page
375 of the Workflow Administration Guide:
• Workflow Log File Name. Optionally enter a file name, or a file name and directory.
If you leave this field blank, the Informatica Server does not create a workflow log. Instead, the
Informatica Server writes workflow log messages to the server log or Windows Event Log, depending
on how you configure the Informatica Server.
If you fill in this field, the Informatica Server appends information in this field to that entered in the
Workflow Log File Directory field. For example, if you have “C:\workflow_logs\” in the Workflow
Log File Directory field, then enter “logname.txt” in the Workflow Log File Name field, the
Informatica Server writes logname.txt to the C:\workflow_logs\ directory.
• Workflow Log File Directory. Designates a location for the workflow log file. By default, the
Informatica Server writes the log file in the server variable directory, $PMWorkflowLogDir.
If you enter a full directory and file name in the Workflow Log File Name field, clear this field.
Chapter 17: External Loading (Loading to Teradata)

The following information applies to Teradata external loaders:
You cannot use Teradata external loaders to load binary data. You can use the Teradata external loaders to
load multibyte data.
Appendix B: Workflow Properties Reference

The following text replaces the text in the second and third rows of Table B-2 on pages 594-95 of the
Workflow Administration Guide:
51
• Workflow Log File Name. Optional. Enter a file name, or a file name and directory.
If you leave this field blank, the Informatica Server does not create a workflow log. Instead, the
Informatica Server writes workflow log messages to the server log or Windows Event Log, depending
on how you configure the Informatica Server.
If you fill in this field, the Informatica Server appends information in this field to that entered in the
Workflow Log File Directory field. For example, if you have “C:\workflow_logs\” in the Workflow
Log File Directory field, then enter “logname.txt” in the Workflow Log File Name field, the
Informatica Server writes logname.txt to the C:\workflow_logs\ directory.
• Workflow Log File Directory. Required. Designates a location for the workflow log file. By default,
the Informatica Server writes the log file in the server variable directory, $PMWorkflowLogDir.
If you enter a full directory and file name in the Workflow Log File Name field, clear this field.
Contacting Informatica
Mailing Address
Informatica Corporation
2100 Seaport Boulevard
Redwood City, California 94063
General Phone and Fax

800.653.3871
650.385.5000
650.385.5500 (fax)
Technical Support
North America / South America
support@informatica.com
866.563.6332
650.213.9489 (fax)
Africa / Asia / Australia / Europe

6 Waltham Park
Waltham Road, White Waltham
Maidenhead, Berkshire
SL6 3TN
Phone: 44 870 606 1525
Fax: +44 1628 511 411
Hours: 9 a.m. - 5:30 p.m. (GMT)
email: support_eu@informatica.com
Belgium
Phone: +32 15 281 702
Hours: 9 a.m. - 5:30 p.m. (local time)
France
Phone: +33 1 41 38 92 26
Germany
Phone: +49 1805 702 702
52
Netherlands
Phone: +31 306 082 089
Singapore
Phone: +65 322 8589
Hours: 9 a.m. - 5 p.m. (local time)
Switzerland
Phone: +41 800 81 80 70
Hours: 8 a.m. - 5 p.m. (local time)
UK +44 870 606 1525

support_uk@informatica.com
Germany +49 1805 702 702
Switzerland +41 800 81 80 70
Website Address
http://www.informatica.com
Informatica Webzine Address and Email

webzine@informatica.com (email)
53

PMPC-62 - Release Notes For 6.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PMPC-62 - Release Notes For 6.2

Uploaded by

Copyright:

Available Formats

Informatica Corporation

Metadata Exchange for Data Models:

Informatica Developer Network

If you have any questions, please email webzine@informatica.com.

If you have any questions, please email web@informatica.com.

6.2 New Features and Enhancements

Listobjects. Use this command to list objects in the repository.

Informatica Server Enhancements

Teradata repositories. PowerCenter and PowerMart support Teradata as a repository database.

6.0 New Features and Enhancements

Compilers for External Procedures and Advanced

• AIX: Visual Age C++ compiler, version 5.0

• NT: VC++ 6.0, cl version 12.00.8168

• Solaris: Forte 6 Update 2, C++ patch 111685-07

• Linux: g++ version 2.96 20000731

6.2 Bug Fixes

This no longer occurs.

Database and Connectivity

This no longer occurs.

This no longer occurs.

This no longer occurs.

This no longer occurs.

6.1 Bug Fixes

This no longer occurs.

This no longer occurs.

This no longer occurs.

This no longer occurs.

For example, you have the following expression:

Fixed CR 11256: No delay in scheduled sessions

This no longer occurs.

INPUT_FIELD RETURN VALUE

This no longer occurs.

6.0 Bug Fixes

This no longer occurs.

The mapping <mapping_name> has been modified by another user. Mapping

Shortcut_To_<mapping_name> already exists. Unable to save this

Now, the Designer displays the following message:

A shortcut to Shortcut_To_<mapping_name> already exists. Creating

Fixed CR 17531: Designer no longer changes an imported shortcut to an object

Now, shortcuts are properly imported.

05 FILLER Error at line 16: parse error

This no longer occurs.

Third Party Limitations

TT_11102 Database partition router failed due to the following error

WRITER_1_1_1> WRT_8229 Database errors occurred:

[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003

The DB2 EE load utility loads a null value to the database.

CR 6163: Session fails for non-cached lookups on DB2

Workaround: Enable caching in the Lookup transformation.

Workaround: Contact HP regarding bug #JAGad68396, and install HP patch PHSS_26560.

Workaround: Manually change these datatypes to Nchar and Nvarchar.

Microsoft SQL Server

Workaround: Use one of the following workarounds:

Workaround: Use native drivers.

REP_12001: Failed to log onto Database Server.

CR 38932: Informatica Server fails to connect to Oracle 9i databases running on Windows

READER_1_1_1> RR_4036 Error connecting to database

CR 37460: Repository Agent shuts down unexpectedly while making concurrent

CR 34337: Oracle 8i sessions running in bulk mode may fail

WRITER_1_1_1> CMN_1022 Database driver error...

MAPPING> TE_7022 TShmWriter: Initialized

Workaround: Run the session in normal mode.

CR 32615: Repository Agent process on Windows NT stops when it loses connection to