Scribd Logo
Upload

Welcome to Scribd!

  • 52 views

    ERROR Logging

    Uploaded by

    Dudi Kumar
    This document discusses using Informatica's inbuilt error logging feature to log row errors to a central relational table or flat file. It describes how to configure error logging by setting the error log type, enabling stop on errors, and specifying the database connection or flat file location. It also lists the tables that will be populated with error data and provides examples of database error messages that can be logged. Using the inbuilt error logging avoids custom development effort and provides accurate error information, though it can impact performance by processing rows one at a time.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    ERROR Logging

    Uploaded by

    Dudi Kumar
    52 views4 pages
    This document discusses using Informatica's inbuilt error logging feature to log row errors to a central relational table or flat file. It describes how to configure error logging by setting the error log type, enabling stop on errors, and specifying the database connection or flat file location. It also lists the tables that will be populated with error data and provides examples of database error messages that can be logged. Using the inbuilt error logging avoids custom development effort and provides accurate error information, though it can impact performance by processing rows one at a time.

    Original Description:

    err

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses using Informatica's inbuilt error logging feature to log row errors to a central relational table or flat file. It describes how to configure error logging by setting the error log type, enabling stop on errors, and specifying the database connection or flat file location. It also lists the tables that will be populated with error data and provides examples of database error messages that can be logged. Using the inbuilt error logging avoids custom development effort and provides accurate error information, though it can impact performance by processing rows one at a time.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    52 views4 pages

    ERROR Logging

    Uploaded by

    Dudi Kumar
    This document discusses using Informatica's inbuilt error logging feature to log row errors to a central relational table or flat file. It describes how to configure error logging by setting the error log type, enabling stop on errors, and specifying the database connection or flat file location. It also lists the tables that will be populated with error data and provides examples of database error messages that can be logged. Using the inbuilt error logging avoids custom development effort and provides accurate error information, though it can impact performance by processing rows one at a time.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 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 error information 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 the error 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 source row. 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 and Error log file name

    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 Log Tables / Flat files.

    Error Messages Cannot Insert the value NULL into column <<Column name>>, table <<Table_name>> Violation of PRIMARY KEY constraint <<Primary key constraint name>> Violation of UNIQUE KEY constraint <<Unique Key Constraint>> Cannot Insert Duplicate key in object <<Table_name>> 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 different environment 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.

    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 the Integration 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 a secure 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 Remote Filename Description 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 Integration Service 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 Not staged. Is TransferChanges the transfer mode. Mode ASCII 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.

    When disabled, the Integration Service uses Binary Transfer mode. Use Binary Transfer mode when transferring files on UNIX machines. Default is disabled.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy