ERROR Logging

7/28/2019 ERROR Logging

1/4

ERROR Logging

Informatica Inbuilt Error Logging feature can be leveraged to implement Row Error

logging in a central location. When a row error occurs, the Integration service logs errorinformation which can be used to determine the cause and source of the error.

These errors can be logged either in a relational table or in a flat file. When the error

logging is enabled, the Integration service creates the error table or error log file the first

time when it runs the session. If the error table or error log file exists already, then theerror data will be appended.

Following are the activities that need to be performed to implement the Informatica Row

Error Logging:

1. In the Config object tab of Error Handling option , set the Error Log type

attribute to Relational database or Flat File. By Default error logging is disabled.

2. SET Stop On Errors = 1

3. If the Error Log Type is set to Relational, specify the Database connection &

Table Name Prefix

Following are the tables which will be created by Integration service and which will be

populated as and when the error occurs.

PMERR_DATA

Stores data and metadata about a transformation row error and its corresponding sourcerow.

PMERR_MSG

Stores metadata about an error and the error message.

PMERR_SESS

Stores metadata about the session.

PMERR_TRANS

Stores metadata about the source and transformation ports, such as name and datatype,

when a transformation error occurs.

4. If the Error Log Type is set to Flatfile, specify the Error log file directory andError log file name


2/4

Database Error Messages and the Error messages that Integration service writes to Bad

File/ Reject file can also be captured and stored in the Error log tables / Flat files.

Following are the few database error messages which will be logged in the Error LogTables / Flat files.

Error Messages

Cannot Insert the value NULL into column , table

Violation of PRIMARY KEY constraint

Violation of UNIQUE KEY constraint

Cannot Insert Duplicate key in object

Row Error Logging Implementation

Advantages

Since the Informatica Inbuilt feature is leveraged, the Error log information would be

very accurate with very minimal development effort.

Pitfall

Enabling Error logging will have an impact to performance, since the integration service

processes one row at a time instead of block of rows.

Informatica File Transfer Protocol

Informatica File Transfer Protocol can be used to transfer/move files from differentenvironment into our pre-defined Landing Zone. It can also be used to transfer file to the

destination folder/directories. The Integration Service can use FTP to access any

machine it can connect to, including mainframes.

Configuring FTP in Informatica Workflow

To use FTP file sources and targets in a session,

Create an FTP connection object in the Workflow Manager and configure the

connection attributes

Configure the session to use the FTP connection object in the session properties.


3/4

Specify the Remote filename in the connection value of the Session properties.

Guidelines

Specify the source or target output directory in the session properties. If not

specified, the Integration Service stage the file in the directory where theIntegration Service runs on UNIX or in the Windows System directory.

Session cannot run concurrently if the same FTP source file or target file located

on a mainframe.

If a workflow containing a session that stages an FTP source or target from a

mainframe is aborted, then the same workflow cannot be run until its timed out.

Configure an FTP connection to use SSH File Transfer Protocol (SFTP) while

connecting to an SFTP server. SFTP enables file transfer over a secure data

stream. The Integration Service creates an SSH2 transport layer that enables asecure connection and access to the files on an SFTP server.

To run a session using an FTP connection for an SFTP server that requires public

key authentication, the public key and private key files must be accessible on

nodes where the session will run.

Configuring Remote Filename

Attribute Description

Remote

Filename

The remote file name for the source or target. Indirect source file name

to be entered, in case of indirect source file is sent.

Use 7-bit ASCII characters for the file name. The session fails if it

encounters a remote file name with Unicode characters.

If the path name is provided with the source file name, the IntegrationService ignores the path entered in the Default Remote Directory field.

The session will fail if the File name with path is provided with single or

double quotation marks.

Is Staged Stages the source or target file on the Integration Service. Default is Notstaged.

Is Transfer Mode ASCII

Changes the transfer mode.

When enabled, the Integration Service uses ASCII transfer mode.

- Use ASCII mode when transferring files on Windows machines

to ensure that the end of line character is translated properly in text files.


4/4

When disabled, the Integration Service uses Binary Transfer mode.

- Use Binary Transfer mode when transferring files on UNIXmachines. Default is disabled.

Documents

ERROR Logging