Error Log Tables

Centralized Error Logging and Reporting

To best describe this utility let’s discuss a scenario.


Scenario:
Need to load Employee flat file to two target instances 
1. Employees
2. Departments


Below is the sample mapping for loading Employees and Departments table (as shown in Fig)

                                        (Note: Click on image to see in Zoom)

Objective is to report the rejected records from this mapping for each target instance (Employees and Departments). To achieve this enable the marked property (as shown in fig below) in the config object in the session to collect the error records into the Informatica error tables.

The value for connection parameter ($DBConnection_SRC_ERR) should be given in parameter 
file or connection can be selected directly. This connection should point to database where 
Informatica PM Error tables are created. 
After  executing the mapping (m_Load_EMPLOYEE_DEPRT), 4 records got rejected from each 
target transformation (DEPARTMENTS & EMPLOYEES) (as shown)

Rejected records from this session are stored into four error logging tables.
1. PMERR_MSG
2. PMERR_SESS
3. PMERR_TRANS
4. PMERR_DATA