Informatica Corporation Informatica Powercenter 6 Informatica Powermart 6 Release Notes

Informatica Corporation
Informatica® PowerCenter® 6
Informatica® PowerMart® 6
Version 6.1
Release Notes
December 2002
Copyright 2002 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-2002 Yaletown Technology Group Inc.
All Rights Reserved.
Contents
CD Contents.....................................................................................................................................................2
Informatica Developer Network.......................................................................................................................3
Webzine............................................................................................................................................................3
Web Support.....................................................................................................................................................3
6.1 New Features and Enhancements...............................................................................................................3
Designer........................................................................................................................................................3
Informatica Server Enhancements................................................................................................................4
Metadata Reporter........................................................................................................................................4
pmrep............................................................................................................................................................4
Repository Manager.....................................................................................................................................4
Repository Server.........................................................................................................................................4
Transformation Language.............................................................................................................................4
Workflow Manager.......................................................................................................................................5
Workflow Monitor........................................................................................................................................5
6.0 New Features and Enhancements...............................................................................................................5
Designer........................................................................................................................................................5
Informatica Server........................................................................................................................................7
Metadata Reporter........................................................................................................................................7
Repository Manager.....................................................................................................................................7
Repository Server.........................................................................................................................................8
Transformation Language.............................................................................................................................8
Workflow Manager.......................................................................................................................................8
Compilers for External Procedures and Advanced External Procedures.........................................................9
6.1 Bug Fixes....................................................................................................................................................9
Bulk Loading................................................................................................................................................9
Client..........................................................................................................................................................10
Informatica Server......................................................................................................................................10
Repository Agent and Repository Server...................................................................................................11
6.0 Bug Fixes..................................................................................................................................................12
Client..........................................................................................................................................................12
Database Connectivity................................................................................................................................12
Flat Files and COBOL................................................................................................................................12
Third Party Limitations..................................................................................................................................13
IBM DB2....................................................................................................................................................13
HP-UX........................................................................................................................................................14
Informix......................................................................................................................................................14
Microsoft SQL Server................................................................................................................................14
Oracle.........................................................................................................................................................15
Sybase.........................................................................................................................................................17
Teradata......................................................................................................................................................18
Microsoft Windows....................................................................................................................................19
PowerCenter/PowerMart Known Limitations................................................................................................19
Bulk Loading..............................................................................................................................................19
Client..........................................................................................................................................................20
Database and Connectivity.........................................................................................................................21
Date Handling.............................................................................................................................................23
External Loader..........................................................................................................................................23
External Procedures and Stored Procedures...............................................................................................24
Flat Files and COBOL................................................................................................................................24
Installation..................................................................................................................................................27
Metadata Reporter......................................................................................................................................27
Partitioning.................................................................................................................................................29
Repository...................................................................................................................................................30
Repository Agent and Repository Server...................................................................................................30
XML...........................................................................................................................................................30
Installation......................................................................................................................................................31
PowerCenter/PowerMart Platform Components........................................................................................31
Client..........................................................................................................................................................31
Repository Server.......................................................................................................................................32
Database Connectivity....................................................................................................................................33
Upgrading.......................................................................................................................................................33
6.1 Documentation Addenda..........................................................................................................................34
Installation and Configuration Guide.........................................................................................................34
Supplemental Guide...................................................................................................................................35
Troubleshooting Guide...............................................................................................................................36
Transformation Language Reference.........................................................................................................36
Workflow Administration Guide................................................................................................................37
6.0 Documentation Addenda..........................................................................................................................37
All Manuals................................................................................................................................................37
Installation and Configuration Guide.........................................................................................................37
Metadata Reporter Guide...........................................................................................................................38
Repository Guide........................................................................................................................................39
Workflow Administration Guide................................................................................................................39
Contacting Informatica...................................................................................................................................40
Note: This document summarizes revisions to PowerCenterRTTM 6.1, PowerCenter® 6.1, and PowerMart®
6.1 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.1/PowerCenter 6.1/PowerMart 6.1 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
<mailto: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:
<http://my.Informatica.com>
If you have any questions, please email web@informatica.com <mailto:web@informatica.com>.
6.1 New Features and Enhancements

This section describes new features and enhancements to PowerCenter 6.1 and PowerMart 6.1.
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 database. You can use
Teradata as source, target, or repository database. You can also create Lookup and Stored Procedure
transformations for Teradata sources and targets.
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.
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.
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. You use a tool called the Repository Administration Console
to issue repository administration commands through the Repository Server. Use the Administration
Console to perform repository functions, such as creating, copying, backing up, and restoring repositories.
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 will automatically
close repository connections lost due to network or system problems, and will automatically release locks
held by lost connections.
Teradata repositories. PowerCenter and PowerMart support Teradata as a repository database.
Transformation Language
Transformation language updates. Informatica has 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 programs from within the Workflow Manager that you frequently use.
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.
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 when you need 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.
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.
6.0 New Features and Enhancements

This section describes new features and enhancements to PowerCenter 6.0 and PowerMart 6.0.
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.
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. 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 the View Dependencies option.
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.
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.
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.
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 any prior version, you must upgrade the external procedure and recompile it.
6.1 Bug Fixes

The following issues are corrected in PowerCenter 6.1 /PowerMart 6.1. 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.
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.
•You set the session for bulk mode.
This no longer occurs.
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 by 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 value of the 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, Informatica Server produces numeric
overflow.
For example, you have the following expression:
(2,147,483,647 - 2) + 3
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 always 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 to 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, when you edit a flat file source instance or target instance, and when you edit 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 you may have received 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. For example, in
normal mode Microsoft SQL Server rounded 0.215 up to 0.22. In bulk mode, it rounded 0.215 down to
0.21.
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.
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

The following issues are corrected in PowerCenter 6.0 /PowerMart 6.0. 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 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 now 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.
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.1 and PowerMart 6.1. 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 38440: IBM DB2 EE db2load utility fails to load last numeric column to DB2 EE
database on UNIX
If you use the DB2 EE db2load utility to load data in which the last column is numeric to a DB2 EE
database on UNIX, db2load does not convert the numeric value. The db2load utility loads a null value to
the database.
CR 36093: The Informatica Server fails to promote a local DB2 repository after creating the
repository
When you use the Repository Server to create a DB2 repository, the Informatica Server 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 12140: Informatica Server on AIX cannot connect to DB2 UDB EEE sources/targets
through Merant 3.7 ODBC
When you run a session with DB2 UDB EEE 6.1 (or above) sources or targets, the session fails if the
following conditions are true:
•The Informatica Server is running on AIX.
•The Informatica Server is using both the Merant 3.7 ODBC manager and the DB2 UDB EEE 6.1 (or
above) CAE ODBC driver.
The session fails with the following error message:
CMN_1046 ODBC Error

CMN_1046 []
This problem occurs because the Merant 3.7 ODBC manager and the DB2 UDB EEE 6.1 (or above) CAE
ODBC driver are not compatible.
Workaround: Do not use an ODBC connection. Be sure to only use a native DB2 CAE connection to a DB2
database.
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 ( _ ).
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: Integer limitation 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: You must manually change these datatypes to Nchar and Nvarchar.
Microsoft SQL Server

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 constraint on a foreign key 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 11967: Using the wrong short date format in Windows might cause the Microsoft SQL
Server bulk loader to load incorrect dates
When loading data into a Microsoft SQL Server table using the bulk load option, the Microsoft SQL Server
bulk loader sometimes loads incorrect dates. For example:
01/01/1800 in the source becomes 01/01/2000 in the target

Workaround: To ensure that Microsoft SQL Server loads the correct date, you must set the short date format
to MM/DD/YYYY on Windows. Select Start-Settings-Control Panel. For NT, double-click the Regional
Settings icon. For Windows 2000, double-click the Regional Options icon. For both Windows NT and
2000, click the Date tab and set the short date to MM/DD/YYYY.
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: Re-install 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.
•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 that fixes Oracle bug 2281980 from Oracle patch set 8.1.7.3 to the
database client application on the UNIX system.
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 that fixes Oracle bug 2281980 from Oracle patch set 8.1.7.3 to the
Oracle client library used by the Repository Agent.
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 always 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.
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 8k 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 33115: The Sybase IQ external loader fails when loading to a view for a table
The Sybase IQ external loader cannot load data to a view for a table. It can only load data to an a database
table.
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 constraint on a foreign key 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.
Teradata
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: 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.
PowerCenter/PowerMart Known Limitations

Please be aware of the following limitations that may occur when using PowerCenter 6.1 and PowerMart
6.1. If you encounter difficulties or have further questions regarding one of these limitations, contact
Informatica Technical Support and reference the CR number.
Bulk Loading
CR 39673: Sybase bulk load session fails when using a 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 table name prefix in the target instance Table Name Prefix
property. Use the following format:
dbname.tablenameprefix
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.
CR 34329: When running the 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 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 extension default value. For example, you create a reusable metadata extension for
targets in the Repository Manager and supply a default value for the extension. You then create and save a
new 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.
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 re-import 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: Re-import all tables affected by the primary/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.
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. However, when you specify a hard
coded Varchar value, the Informatica Server finds a match and performs updates.
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 35867: Informatica Server on HP-UX fails session accessing DB2 and ODBC
When the Informatica Server installed on HP-UX runs a session, the session fails with database errors
under the following circumstances:
•The session reads from the source through ODBC and writes to a DB2 target.
•The session reads from a DB2 source and writes to the target through ODBC.
•The repository resides on an IBM DB2 UDB database and the session reads from the source through
ODBC writes to the target through ODBC.
The Informatica Server may write a message similar to the following message in the session log:
READER_5_1_1 RR_4036 Error connecting to database [ [IBM][CLI Driver]

SQL1001N "QACCM_COMNTDB_UNIX" is not a valid database name.
SQLSTATE=2E000 Database driver error... Function Name : Connect
Database driver error... Function Name : Connect]. READER_5_1_1 Tue
Mar 05 09:25:44 2002 READER_5_1_1 BLKR_16001 Error connecting to
database... MASTER PETL_24020
Workaround:
•Install the HP patch PHSS_24303. To obtain the necessary HP patch, visit the HP support web site at:
http://ussupport2.external.hp.com/wpsl/bin/doc.pl/sid=7267d6001260250024/screen=wpslPatchList
<http://us-
support2.external.hp.com/wpsl/bin/doc.pl/sid=7267d6001260250024/screen=wpslPatchList>
•Add the following configuration option to the Informatica Server pmserver.cfg file:
LoadDB2BeforeODBCOnHP=Yes
CR 29118: Error statistics are reported incorrectly in the log file for rows written to DB2
targets on AS400 or OS390
When rows are written to a DB2 target database on AS400 or OS390 and the array write option is enabled,
error statistics are reported incorrectly in the log file due to a limitation in DB2.
Workaround: Add the following entry to the file pmserver.cfg on the Informatica Server:
DB2ArrayStatusPtrWorkAround=Yes
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:
[MERANT][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 to Integer)
If a mapping converts data from a Double to an Integer, and the session writes 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 Integers 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 Integer values.
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.
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.
Informatica Server
CR 46365: 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 41486: Informatica Server cannot access Informix 9.x databases on AIX 5.1
The Informatica Server cannot access Informix 9.x databases on AIX 5.1.
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 PowerCenter Server does
not read the source rows. In PowerCenter, 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.
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.
Work around: 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 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 Microsoft SQL Server and Sybase targets do not exist
When you run a session that writes to a target table on Microsoft SQL Server or Sybase, the Informatica
Server completes the session even if the session 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, problems may
occur.
In addition, the Flat File Wizard does not display non-printable ASCII characters.
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>
<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\
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: Problems displaying reports in Metadata Reporter for Informix

repositories
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.
Repository
CR 9642: Unable to create or restore repositories or display non-ASCII characters in
Informatica Client tools (Oracle 8 and 8i databases only)
When you try to create or restore a repository on an Oracle 8 or 8i database, the following error displays:
ORA 01026 Multiple Buffers of size > 4 K in the bind list.
In addition, the Informatica Client does not accurately display non-ASCII characters.
Workaround: For Oracle databases, set the language parameter NLS_LANG to the database character set.
For example, an Oracle 8i database has UTF-8 as the character set.
On UNIX, set the following language parameter:
setenv NLS_LANG = japanese_japan.UTF8
On Windows NT/2000: In the Control Panel, double-click System. In the Environment tab, set the System
Variable to NLS_LANG and the value to japanese_japan.UTF8.
Repository Agent and Repository Server
CR 45128: The Informatica Server fails to load an external procedure when a shared library
is not in the runtime location or system path
The Informatica Server fails to load an external procedure when the DLL shared library, or a reference file,
is not in the runtime location specified in the External Procedure or Advanced External Procedure
transformation.
Workaround: Copy all DLLs and shared libraries referenced by the external procedure to the runtime
location specified in the External Procedure or Advanced External Procedure transformation, or copy them
to a location specified in the system path.
CR 41325: 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.
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.1 and
PowerMart 6.1 components
When you install Informatica PowerCenter 6.1/PowerMart 6.1 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.
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 98 or Windows NT/2000 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.

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.
Enabling Data Code Page Validation

After you complete the PowerCenter or PowerMart installation, you can choose to enable data code page
validation. If you want to enable code page validation, you must also configure the Informatica Server for
Unicode data movement mode.
Installing the Informatica Server on HP-UX

If you want to run the Informatica Server on HP-UX, you must install HP patch PHSS_24303 on the HP-
UX system.
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 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
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.
Installing the Repository Server on HP-UX

If you want to run the Repository Server on HP-UX, you must install HP patch PHSS_24303 on the HP-
UX system.
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 nulls 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 nulls.
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>
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 on each client, server, and repository machine. If you do not install
SQL Server Service Pack 1, you can cause repository inconsistencies.
Upgrading
Unlock all Repository Objects
Before upgrading to PowerCenter 6.0 or PowerMart 6.0, make sure no sessions or batches are running on
the Informatica Server and no users are connected to the repository, then unlock all repository objects.
Repository Upgrade Duration

In order to make existing expressions compatible with updates to the transformation language, the
PowerCenter 6.1/PowerMart 6.1 upgrade process must fetch, examine, and modify a large number of
objects in the repository. If you are upgrading from PowerCenter 1.7/5.0/5.1 or PowerMart 4.7/5.0/5.1, the
upgrade process must also fetch each session and batch and upgrade it to the workflow model. Depending
on the size of your repository, this process 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.
DTM Buffer Size and Buffer Block Size Requirements

In PowerCenter 6.1/PowerMart 6.1, the DTM buffer size must be at least ten times the size of the DTM
buffer block size. If you have any PowerCenter 6.0/PowerMart 6.0 sessions that do not meet this
requirement, they will fail in PowerCenter 6.1/PowerMart 6.1 with the following message:
TM_6279 Session instance <session name> runtime validation error: [The DTM Buffer Size
should be at least 10 times the Buffer Block Size (defined in the session
configuration object)].
When you get this message, you should edit the session properties to ensure that the DTM buffer size is at
least ten times the size of the DTM buffer block size.
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.
For more information about upgrading the repository, “Upgrading a Repository” in the Supplemental Guide
in the manuals directory of the install CD or the installation directory of the Informatica Client.
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.
6.1 Documentation Addenda

The following section contains additional information not included in the printed version of the
PowerCenter 6.1 and PowerMart 6.1 manuals. This section also contains information about new features or
changes in functionality introduced in PowerCenter 6.1/PowerMart 6.1 that is not included in the printed
version of the PowerCenter 6.0/PowerMart 6.0 manuals.
Installation and Configuration Guide

Chapter 8: Installing and Configuring the Informatica Windows Server (Step 2. Configuring
the Informatica Windows Server)
The following text adds to Informatica Server configuration information in Table 8-6, “Miscellaneous
Configuration for Informatica Server on Windows.”
Setting Required/Optional Description

Output Metadata for Flat Optional If you enable this option, the Informatica Server writes
File Target column headers to flat file targets. It writes the target
definition port names to the flat file target in the first
line, starting with the # symbol. By default, this option is
disabled.
Treat Null In Required Determines how the Informatica Server evaluates null
Comparison Operators values in comparison operations. Specify one of the
As following: Null. The Informatica Server evaluates null
values as null values in comparison expressions. If either
operand is a null value, the result is a null value. This is
the default behavior. High. The Informatica Server
evaluates null values as greater than non-null values in
comparison expressions. If both operands are null
values, the Informatica Server evaluates them as equal.
When you choose High, comparison expressions never
result in a null value. Low. The Informatica Server
evaluates null values as less than non-null values in
values, the Informatica Server treats them as equal.
When you choose Low, comparison expressions never
result in a null value.
Chapter 9: Installing and Configuring the Informatica UNIX Server (Step 2. Configuring the
Informatica Server on UNIX)
The following text adds to Informatica Server configuration information in Table 9-2, “Configuration
Parameters for Informatica Server on UNIX.”
Option Required/Optional Description
OutputMetaDataForFF Optional If set to Yes, the Informatica Server writes column
headers to flat file targets. It writes the target definition
port names to the flat file target in the first line, starting
with the # symbol. By default, this option is set to No.
TreatNullInComparison Required Determines how the Informatica Server evaluates null
OperatorsAs values in comparison operations. Specify one of the
following: Null. The Informatica Server evaluates null
values as null values in comparison expressions. If
either operand is a null value, the result is a null value.
This is the default behavior. High. The Informatica
Server evaluates null values as greater than non-null
values in comparison expressions. If both operands are
null values, the Informatica Server treats them as equal.
When you choose High, comparison expressions never
result in a null value. Low. The Informatica Server
evaluates null values as less than non-null values in
values, the Informatica Server evaluates them as equal.
When you choose Low, comparison expressions never
result in a null value.
Supplemental Guide
Chapter 2: Managing the Repository (Deleting a Repository)
The following text adds to the information about deleting a repository in the Repository Server
Administration Console.
If the repository you want to delete is a global repository, you must choose to unregister all local
repositories. If you do not choose to unregister all local repositories, and the global repository has
registered local repositories, the Repository Server does not delete the global repository.
Chapter 10: Upgrading Repository Metadata (Upgrading TPump Date Format)

The following information applies to upgrading existing TPump target update overrides:
In previous versions of PowerCenter/PowerMart, the sessions using the TPump external loader wrote data
to the flat file target in the format MM/DD/YYYY. In PowerCenter 6.1/PowerMart 6.1, sessions that use
TPump to load data to a target write data to the target flat file in the format YYYYMMDD. If you use a
target update override that specifies date format, you must change the date format from MM/DD/YYYY to
YYYYMMDD in the target instance of the mapping.
Troubleshooting Guide
For updated troubleshooting messages, please refer to “Error Messages” in the PowerCenter 6.1/PowerMart
6.1 Supplemental Guide.
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.
Transformation Language Reference

Chapter 6: Functions
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().
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 )
Workflow Administration Guide

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

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.1, 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.
6.0 Documentation Addenda
The following section contains additional information not included in the printed version of the
PowerCenter 6.0 and PowerMart 6.0 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.
Installation and Configuration Guide

Chapter 2: Installation and Configuration Overview (Minimum system requirements)
The following text adds to operating system support information to Table 2-1, “Minimum System
Requirements,” on page 20 of the Installation and Configuration Guide:
You can install the Informatica Client on Windows NT/2000/XP. You can install the Repository Server and
Informatica Server on Windows NT/2000.
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.
Metadata Reporter Guide

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:
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.
Workflow Administration Guide

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.
Appendix B: Session Parameters

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:
•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
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

http://my.Informatica.com
webzine@informatica.com (email)

Informatica Corporation Informatica Powercenter 6 Informatica Powermart 6 Release Notes

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Informatica Corporation Informatica Powercenter 6 Informatica Powermart 6 Release Notes

Hochgeladen von

Copyright:

Verfügbare Formate

Informatica Corporation

Copyright 2002 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 <mailto:web@informatica.com>.

6.1 New Features and 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

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

Repository Agent and Repository Server

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 now displays the following message:

A shortcut to Shortcut_To_<mapping_name> already exists. Creating

Now, shortcuts are properly imported.

Flat Files and COBOL

05 FILLER Error at line 16: parse error

This no longer occurs.

Third Party Limitations

The session fails with the following error message:

CMN_1046 ODBC Error

Workaround: Remove the underscore from the table or alias name.

CR 6163: Integer limitation 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.

Microsoft SQL Server

Workaround: Use native drivers.

01/01/1800 in the source becomes 01/01/2000 in the target

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

You can configure the tnsnames.ora file as follows:

For details, see Oracle Doc ID 44694.1.

CR 13256: Sybase IQ does not support Binary, Varbinary, or Image datatypes

"Unknown PowerMart datatype"

PowerCenter/PowerMart Known Limitations

WRT_8229 Database errors occurred:

Then, run genclntsh.

Workaround: Re-import all tables affected by the primary/foreign key relationship.

Workaround: Configure the target definition as a Teradata database type.

READER_5_1_1 RR_4036 Error connecting to database [ [IBM][CLI Driver]

CR 21801: ODBC drivers do not pass truncation message to Informatica Server

CR 17221: Precision in Varchar columns in Sybase targets limited to a maximum of 255

[MERANT][ODBC Sybase driver][SQL Server] Length or precision