Informatica Logs Explanation

7/28/2019 Informatica Logs Explanation

1/16

Informatica Training Day 2

13/06/2013

Log Files

The PowerCenter Server can create log files for each workflow it runs. These files containinformation about the tasks the PowerCenter Server performs, plus statistics about the workflowand all sessions in the workflow. If the writer or target database rejects data during a session run,the PowerCenter Server creates a file that contains the rejected rows.The PowerCenter Server can create the following types of log files:

Workflow log. Contains information about the workflow run such as workflow name, tasks

executed, and workflow errors. By default, the PowerCenter Server writes this informationto the server log or Windows Event Log, depending on how you configure the PowerCenterServer. If you wish to create a workflow log, enter a workflow file name in the workflowproperties.

Session log. Contains information about the tasks that the PowerCenter Server performs

during a session, plus load summary and transformation statistics. By default, thePowerCenter Server creates one session log for each session it runs. If a workflow containsmultiple sessions, the PowerCenter Server creates a separate session log for each session

in the workflow. Reject file. Contains rows rejected by the writer or target file during a session run. If the

writer or target does not reject any data during a session, the PowerCenter Server does notgenerate a reject file for that session. By default, the PowerCenter Server saves each typeof log file in its own directory. The PowerCenter Server represents these directories usingserver variables.

You can change the default directories at the server level by editing the server connection in theWorkflow Manager. You can also override these values for individual workflows or sessions byupdating the workflow or session properties.

Log File Type Default Directory Value

Workflow logs $PMWorkflowLogDir $PMRootDir/WorkflowLogsSession logs $PMSessionLogDir $PMRootDir/SessLogsReject files $PMBadFileDir $PMRootDir/BadFiles

Workflow Logs

You can configure a workflow to create a workflow log. When you do this, the PowerCenter Serverwrites information such as process initialization, workflow task run information, errors encountered,and workflow run summary to the workflow log.In general, a workflow log contains the following information about the workflow:

Workflow name

Workflow status

Status of tasks and worklets in the workflow

Start and end times for tasks and worklets

Results of link conditions

Some session messages and errors

Errors encountered during the workflow

1


2/16


13/06/2013

The PowerCenter Server categorizes workflow log error messages into severity levels. ThePowerCenter Server either writes or does not write an error message to the log file based on theerror severity level. You can set the Error Severity Level for Log Files in the PowerCenter Serversetup program.You can also configure the PowerCenter Server to suppress writing messages to the workflow logfile completely. As with PowerCenter Server logs and session logs, the PowerCenter Server entersa code number into the workflow log file message along with message text.You configure a workflow to create a workflow log by entering a workflow log file name in theworkflow properties. If you choose to create a workflow log, the PowerCenter Server saves theworkflow log in a directory entered for the server variable $PMWorkflowLogDir in the PowerCenterServer registration. You can override the workflow log directory at the server level or at the workflowlevel.By default, the PowerCenter Server saves one workflow log for each workflow. If you want to savemultiple logs for different workflow runs, you can configure the workflow to save a workflow log fileby timestamp, which permits an unlimited number of workflow logs, or by run, which saves aspecified number of logs. To view previous workflow logs, save log files by timestamp.If you choose not to create workflow logs, the PowerCenter Server writes the workflow logmessages to the server log or Windows Event Log, depending on how you configure thePowerCenter Server.

Workflow Log Messages

The PowerCenter Server precedes each message in the log file with a code and number. It alsoprecedes some messages with a timestamp. The code defines a group of messages for a specificprocess. The number defines a specific message. The message can provide general information orit can be an error message.You can configure the PowerCenter Server to append a time stamp to every message it writes tothe workflow log. To do this, enable the Time Stamp Workflow Log option in the PowerCenterServer setup program.

Workflow Log Codes

You can use the workflow log to determine the cause of workflow problems. To resolve workflowproblems, locate the relevant log file codes and text prefixes in the workflow log, then see theTroubleshooting Guide for details. You can find workflow-related server messages in the UNIXserver log (default name: pmserver.log) or in the Windows Event Log (viewed with the EventViewer).

Workflow Log Sample

The following sample is a workflow log from a simple workflow that shows log file codes:

INFO : LM_36315 [Tue Nov 18 11:16:38 2003] : (270|305) Starting execution of workflow[wf_PhoneList].INFO : LM_36330 [Tue Nov 18 11:16:38 2003] : (270|305) Starting execution of start instance

[StartWorkflow].INFO : LM_36333 [Tue Nov 18 11:16:38 2003] : (270|305) Execution of start instance[StartWorkflow] succeeded.INFO : LM_36505 : (270|305) Link [StartWorkflow --> s_PhoneList]: empty expression string,evaluated to TRUE.INFO : LM_36330 [Tue Nov 18 11:16:38 2003] : (270|305) Starting execution of session instance[s_PhoneList].INFO : LM_36522 : (270|305) Started DTM process [pid = 273] for session instance [s_PhoneList].INFO : CMN_1760 : (273|255) Message from session: LM_36033 [Connected to repository [SALES]running on server:port [monster]:[5001] user [Administrator]].

2


3/16


13/06/2013

INFO : CMN_1760 : (273|255) Message from session: TM_6228 [Writing session output to log file[d:\pcserver\SessLogs\s_PhoneList.log].].INFO : LM_36333 [Tue Nov 18 11:16:43 2003] : (270|306) Execution of session instance[s_PhoneList] succeeded.INFO : LM_36318 [Tue Nov 18 11:16:43 2003] : (270|306) Execution of workflow [wf_PhoneList]succeeded.

Configuring Workflow Logs

You can configure workflow log options in the workflow properties. You can configure the followinginformation for a workflow log:

Location. You can configure the directory where you want the workflow log created. By

default, the PowerCenter Server creates the workflow log in the directory configured for the$PMWorkflowLogDir server variable. You can enter a different directory, but if the directorydoes not exist or is not local to the PowerCenter Server that runs the workflow, the workflowfails.

Name. If you wish to create a workflow log, you can enter a name for the workflow log file. If

you do not enter a filename, the PowerCenter Server does not create a workflow log.Instead, the PowerCenter Server writes workflow log messages to the Windows Event Logor UNIX server log.

Archive. You can configure the number of workflow logs you want the PowerCenter Server

to archive for each workflow. By default, the PowerCenter Server does not archive workflowlogs.

Archiving Workflow Logs

By default, the PowerCenter Server does not save multiple logs for a single workflow. It creates oneworkflow log for each workflow and overwrites the existing log with the latest workflow log.If you wish to save multiple logs for a workflow, you can configure the PowerCenter Server to do

this. The PowerCenter Server can save workflow logs in two ways:

Save a selected number of logs

Save all logs by timestamp

If you configure the workflow to save a specific number of workflow logs, it names the most recentlog filename.log. It then cycles through a closed naming sequence for historical logs as follows:filename.log.0, filename.log.1, filename.log.2, , filename.log.n-1, where n represents the numberof workflow logs. Because the PowerCenter Server cycles through the numeric naming sequence,check the workflow log file timestamp to determine the chronological order of those files.Instead of entering a specific number of workflow logs to save, you can use the server variable$PMWorkflowLogCount. When you use $PMWorkflowLogCount server variable, the PowerCenterServer archives the number of workflow logs configured for the server variable. If you use$PMWorkflowLogCount for all workflows, you can increase the number of archived workflow logsfor all workflows by changing the server variable.

You can also save all workflow logs by configuring a workflow to save logs by timestamp. Whentimestamping workflow logs, the PowerCenter Server appends the year, month, day, hour, andminute of the workflow completion to the log file. The resulting log file name isfilename.log.yyyymmddhhmi, where:

yyyy= year

3


4/16


13/06/2013

mm = month, ranging from 1-12

dd= day, ranging from 1-31

hh = hour, ranging from 0-23

mi= minute, ranging from 0-59

To prevent filling the workflow log directory, periodically delete or backup log files when using thetimestamp option.

Steps for Configuring Workflow Logs

You can configure workflow log information on the Properties tab of the workflow properties.

1. In the Workflow Manager, open the workflow properties.2. Select the Properties tab.

3. Enter the following workflow log options:

4


5/16


13/06/2013

4. Click OK to save the workflow.

Viewing Workflow Logs

Workflow logs are text files that you can open with any text editor. The PowerCenter Server savesworkflow logs in the directory you specify in the Workflow Log File Directory field in the workflowproperties. You can also view workflow logs through the Workflow Monitor. When you do this, theWorkflow Manager creates a temporary file that stores the workflow log. You can view thetemporary file through the Workflow Monitor.

The PowerCenter Server generates the workflow log based on the PowerCenter Server code page.You can specify the language in which you want to view the workflow log based on the locale of themachine hosting the PowerCenter Server.

To use the Workflow Monitor to view the most recent workflow log:

1. In the Navigator window, connect to the server on which the workflow runs.2. Open the folder that contains the workflow.3. Right-click the workflow and choose Get Workflow Log.

5


6/16


13/06/2013

If you save workflow logs by timestamp, you can also use the Workflow Monitor to view pastworkflow logs. To do this, right click the workflow in the Gantt chart view and choose Get WorkflowLog.

Session Logs

The session log file contains information about all tasks the PowerCenter Server performs, plus theload summary and transformation statistics. The amount of detail in the session log depends on thetracing level that you set. You can define the tracing level for each transformation or for the entiresession. The session-level tracing overrides any transformation-level tracing levels.In general, the session log contains the following information about the session:

Allocation of system shared memory

Execution of pre-session commands

Creation of SQL commands for reader and writer threads

Start and end times for target loading

Errors encountered during session

Execution of post-session commands

Load summary of reader, writer, and Data Transformation Manager (DTM) statistics

By default, the PowerCenter Server saves session logs in the directory for the PowerCenter Servervariable $PMSessionLogDir, which you define in the Workflow Manager. The default name for thesession log is s_mapping name.log. You can override the session log name and location in thesession properties.The PowerCenter Server does not archive session logs by default. Instead, it creates one log foreach session and overwrites the existing log with the latest session log. However, you can configurethe session to archive session logs.By default, the PowerCenter Server generates session log files based on the PowerCenter Servercode page. However, if you enable the Output Session Log in UTF-8 option on the Configurationtab of the PowerCenter Server setup program, the PowerCenter Server writes to the session log

using the UTF-8 character set.

Session Log Messages

The PowerCenter Server precedes each message in the log file with a thread identification and thena code and number. The code defines a group of messages for a specific process. The numberdefines a specific message. The message can provide general information or it can be an errormessage.You can configure the PowerCenter Server to write session log messages to an external library aswell as to the session log. To do this, you can set the Export Session Log Lib Name in thePowerCenter Server setup program.

Session Log Codes

You can use the session log to determine the cause of session problems. To resolve sessionproblems, locate the relevant log file codes and text prefixes in the session log, then see theTroubleshooting Guide for details. You can find session-related server messages in the UNIXserver log (default name: pmserver.log) or in the Windows Event Log (viewed with the EventViewer).

Message code Description

6


7/16


13/06/2013

BLKRMessages related to reader process, including

Application, relational, or flat file.

CNXMessages related to the Repository Agentconnections.

CMN Messages related to databases, memoryallocation, Lookup and Joiner transformations, andinternal errors.

DBGMessages related to PowerCenter Server loadingand debugging.

DBGR Messages related to the Debugger.

EP Messages related to external procedures.

ES Messages related to the Repository Server.

FR Messages related to file sources.

FTPMessages related to File Transfer Protocoloperations.

HIER Messages related to reading XML sources.

LM Messages related to the Load Manager.

NTSERV Messages related to Windows server operations.

OBJM Messages related to the Repository Agent.

ODL Messages related to database functions.

PETL Messages related to pipeline partitioning.

PMFMessages related to caching Aggregator, Rank,Joiner, or Lookup transformations.

RAPP Messages related to the Repository Agent.

REP Messages related to repository functions.

RR Messages related to relational sources.

SFMessages related to server framework, used byLoad Manager and Repository Server

SORT Messages related to the Sorter transformation.

TE Messages related to transformations.

TMMessages related to Data TransformationManager (DTM).

TT Messages related to transformations.

VAR Messages related to mapping variables.

WRT Messages related to the Writer.

XMLR Messages related to the XML Reader.

XMLW Messages related to the XML Writer.

Thread Identification

The thread identification consists of the thread type and a series of numbers separated byunderscores. The numbers following a thread name indicate the following information:

7


8/16


13/06/2013

Target load order group number

Partition point number

Partition number

The PowerCenter Server prints the thread identification before the log file code and the message

text in the session log. The following example illustrates a reader thread from target load ordergroup one, concurrent source set one, source pipeline one, and partition one:

READER_1_1_1> DBG_21438 Reader: Source is [p152636], user [jennie]

When you configure the PowerCenter Server to read Joiner transformation sources sequentially,the PowerCenter Server writes numbers with the following information after the thread name:

Target load order group number

Concurrent source set number

Partition point number

Partition number

A concurrent source set is the group of sources in a target load order group the PowerCenterServer reads concurrently. A target load order group might contain multiple concurrent source setsif it contains a Joiner transformation and you configure the PowerCenter Server to read Joinertransformation sources sequentially.Enable the PMServer 6.X Joiner source order compatibility PowerCenter Server option to configureit to read Joiner transformation sources sequentially.

Session Log Sample

The following sample is an excerpt from a session log file that illustrates log file codes and threadidentifications:

TM_6703 Session [s_m_SampleSessionLog] is run by PowerCenter Server [sarao].MASTER> CMN_1688 Allocated [12000000] bytes from process memory for [DTM Buffer Pool].MASTER> PETL_24000 Parallel Pipeline Engine initializing.MASTER> PETL_24001 Parallel Pipeline Engine running.MASTER> PETL_24003 Initializing session run.MAPPING> TM_6014 Initializing session [s_m_SampleSessionLog] at [Tue Aug 03 11:29:57 2004]...*****START LOAD SESSION*****Load Start Time: Tue Aug 03 11:30:00 2004

Target tables:Emp_targetREADER_1_1_1> BLKR_16019 Read [1] rows, read [0] error rows for source table [EMP_SRC] instance name[EMP_SRC]READER_1_1_1> BLKR_16008 Reader run completed.

TRANSF_1_1_1> DBG_21216 Finished transformations for Source Qualifier[SQ_EMP_SRC]. Total errors [0]WRITER_1_*_1> WRT_8167 Start loading table [Emp_target] at: Tue Aug 03 11:30:00 2004.MASTER> PETL_24002 Parallel Pipeline Engine finished.MASTER> PETL_24012 Session run completed successfully.

Some messages are embedded within other messages. For example, a code CMN_1039 containsinformational messages from the Microsoft SQL Server as it changes to the source database to beused in the session.

8


9/16


13/06/2013

If your PowerCenter Server is set to run in ASCII mode, the session log file reports the sort order asBinary, even if you select a different sort order in the session properties.

9


10/16


13/06/2013

Load Summary

The session log includes a load summary that reports the number of rows inserted, updated,deleted, and rejected for each target as of the last commit point. The PowerCenter Server reportsthe load summary for each session by default. However, you can set tracing level to Verbose

Initialization or Verbose Data to report the load summary for each transformation.The following sample is an excerpt from a load summary:

*****START LOAD SESSION*****Load Start Time: Tue Aug 03 11:30:00 2004

Target tables:Emp_targetCommit on end-of-data Aug 03 11:30:07 2004===================================================WRT_8036 Target: Emp_target (Instance Name: [Emp_target])WRT_8038 Inserted rows - Requested: 1 Applied: 1Rejected: 0 Affected: 1WRITER_1_*_1> WRT_8035 Load complete time: Tue Aug 03 11:30:07 2004LOAD SUMMARY============468 Chapter 16: Log Files

WRT_8036 Target: Emp_target (Instance Name: [Emp_target])WRT_8038 Inserted rows - Requested: 1 Applied: 1Rejected: 0 Affected: 1..,WRITER_1_*_1> WRT_8043 *****END LOAD SESSION*****

The PowerCenter Server reports statistics for each of the following operations performed on thetarget:

Inserted. Shows the number of rows the PowerCenter Server marked for insert into the

target. The number ofaffectedrows cannot be larger than requestedfor this operation.

Updated. Shows the number of rows the PowerCenter Server marked for update in the

target. The number ofaffectedrows can be different from the number ofrequested rows. For example, you have a table with one column called SALES_ID and five rows containing

the values: 1, 2, 3, 2, and 2. You mark rows for update where SALES_ID is 2. The writeraffects three rows, even though there was only one update request. Or, if you mark rows forupdate where SALES_ID is 4, the writeraffects 0 rows.

Deleted. Shows the number of rows the PowerCenter Server marked to remove from the

target. The number ofaffectedrows can be different from the number ofrequestedrows.

Rejected. Shows the number of rows the PowerCenter Server rejected during the writing

process. These rows cannot be applied to the target. For the Rejected rows category, thenumber ofaffectedand appliedrows is always zero since these rows are not written to thetarget.

The load summary provides the following statistics:

Requested rows. Shows the number of rows the writer actually received for the specified

operation.

Applied rows. Shows the number of rows the writer successfully applied to the target (that

is, the target returned no errors).

Affected rows. Shows the number of rows affected by the specified operation. Depending

on the operation, the number of affected rows can be different from the number ofrequestedrows. For example, you have a table with one column called SALES_ID and five

10


11/16


13/06/2013

rows containing the values: 1, 2, 3, 2, and 2. You mark rows for update where SALES_ID is2. The writeraffects three rows, even though there was only one update request. Or, if youmark rows for update where SALES_ID is 4, the writeraffects 0 rows.

Rejected rows. Shows the number of rows the writer could not apply to the target. For

example, the target database rejects a row if the PowerCenter Server attempts to insert

NULL into a not-null field. The PowerCenter Server writes all rejected rows to the sessionreject file, or to the row error log, depending on how you configure the session.

Mutated from update. Shows the number of rows originally flagged for update that are

instead insertedinto the target when the session is configured Update Else Insert. If the number of rows requested, applied, rejected, and affected are all zero for any of these

four operations, the operation does not appear as a line in the load summary. If no data ispassed to the target, the writer reports the following message:

No data loaded for this target.

Detailed Transformation Statistics

The DTM enables transformation statistics in the session log for two levels of tracing, VerboseInitialization and Verbose Data. Transformation statistics appear after the load summary in the logfile. The PowerCenter Server reports the following details for each transformation in the mapping:

The name of the transformation

The number of input rows and the name of the input source

The number of output rows and the name of the output transformation or target

The number of rows dropped

The following sample is an excerpt from the transformation statistics in a session log file:

DETAILED TRANSFORMATION ROW STATISTICSfor DSQ [SQ_EMPLOYEES], Partition[1]

---------------------------------MAPPING>MAPPING> TT_11031 Transformation [SQ_EMPLOYEES]:MAPPING> TT_11035 Input - 12 (__READER__)MAPPING> TT_11037 [T_EMPLOYEES]: Output - 12, Dropped - 0MAPPING>...

11


12/16


13/06/2013

Configuring Session Logs

Configure session log options in the session properties. You can configure the following informationfor a session log:

Location. You can configure the directory where you want the session log created. Bydefault, the PowerCenter Server creates the session log in the directory configured for the$PMSessionLogDir server variable. You can enter a different directory, but if the directorydoes not exist or is not local to the PowerCenter Server that runs the session, the sessionfails.

Name. You can name the session log or accept the default name. The default name for the

session log is s_mapping name.log.

Archive. You can configure the number of session logs you want the PowerCenter Server

to archive for each session. By default, the PowerCenter Server does not archive sessionlogs.

Tracing levels. You can control the type of information the PowerCenter Server includes in

the session log by setting a tracing level for the session. By default, the PowerCenter

Server uses tracing levels configured in the mapping.

Configuring Session Log Locations and Filenames

You can configure the name and location of the session log on the Properties tab of the sessionproperties.To configure session log information:

1. In the Workflow Manager, open the session properties.2. Select the General Options settings on the Properties tab.3. Enter the following session log options:4. Click OK to save the session.

Archiving Session Logs

You can archive session logs on a session-by-session basis. The PowerCenter Server can savesession logs in the following ways:

Save a selected number of logs

Save all logs by timestamp

By default, the PowerCenter Server does not archive session logs. It creates one session log foreach session and overwrites the existing log with the latest session log.If you configure the session to save a specific number of session logs, it names the most recent logs_mapping name.log. It then cycles through a closed naming sequence for historical logs asfollows: s_mapping name.log.0, s_mapping name.log.1, s_mapping name.log.2, , s_mapping

name.log.n-1, where n is the number of session logs. Because the PowerCenter Server cyclesthrough the numeric naming sequence, check the session log file timestamp to determine thechronological order of those files.Instead of entering a specific number of session logs to save, you can use the server variable$PMSessionLogCount. When you use $PMSessionLogCount server variable, the PowerCenterServer archives the number of session logs configured for the server variable. If you use$PMSessionLogCount for all sessions, you can increase the number of archived session logs for allsessions by changing the server variable.

12


13/16


13/06/2013

You can also save all session logs by configuring a session to save logs by timestamp. Whentimestamping session logs, the PowerCenter Server appends the month, day, hour, and minute ofthe session completion to the log file. The resulting log file name is s_mappingname.log.yyyymmddhhmi, where:

yyyy= year

mm = month, ranging from 1-12

dd= day, ranging from 1-31

hh = hour, ranging from 0-23

mi= minute, ranging from 0-59

To prevent filling the session log directory, periodically delete or backup log files when using thetimestamp option.To specify archiving information:

1. In the Workflow Manager, open the session properties.2. Select the Log Options settings on the Config Object tab.

3. Enter the following session log options:4. Click OK to save the session.

Setting Tracing Levels

The amount of detail in the session log depends on the tracing level that you set. You can definetracing levels for each transformation or for the entire session. By default, the PowerCenter Serveruses tracing levels configured in the mapping.Setting a tracing level for the session overrides the tracing levels configured for each transformationin the mapping. If you select a normal tracing level or higher, the PowerCenter Server writes rowerrors into the session log, including the transformation in which the error occurred and completerow data. If you configure the session for row error logging, the PowerCenter Server writes rowerrors to the error log instead of the session log. If you want the PowerCenter Server to write

dropped rows to the session log as well, configure the session with Verbose Data tracing level.

You can also enter tracing levels for individual transformations in the mapping. When you enter atracing level in the session properties, you override tracing levels configured for transformations inthe mapping.To set the tracing level:

1. Select the Error Handling settings on the Config Object tab.2. Select a tracing level from the Override Tracing list.3. Click OK to save the session.

Viewing Session Logs

Session logs are text files that you can open with any text editor. The PowerCenter Server savessession logs in the directory you specify in the Session Log File Directory field in the sessionproperties.You can also view session logs through the Workflow Monitor. When you do this, the WorkflowMonitor creates a temporary file that stores the session log. You can view the temporary file throughthe Workflow Monitor. If a session fails, you can still view the session log file.The PowerCenter Server generates the session log based on the PowerCenter Server code page.You can specify the language in which you want to view the session log based on the locale of themachine hosting the PowerCenter Server.

13


14/16


13/06/2013

To use the Workflow Monitor to view the most recent session log:

1. In the Navigator window, connect to the server on which the workflow runs.2. Open the folder that contains the workflow.3. Open the workflow that contains the session whose log you wish to view.4. Right-click the session and choose Get Session Log.

If you save session logs by timestamp, you can also use the Workflow Monitor to view past sessionlogs. To do this, right-click the session in the Gantt chart view and choose Get Session Log.

Understanding the Error Log File

You can create an error log file to collect all errors that occur in a session. This error log file is acolumn delimited line sequential file. By specifying a unique error log file name, you can create aseparate log file for each session in a workflow. When you want to analyze the row errors for onlyone session, use an error log file.In an error log file, double pipes || delimit error logging columns. By default, pipe | delimits row

data. You can change this row data delimiter by setting the Data Column Delimiter error log option.The code page for the error file is the same as the code page for the session log file. If the sessionlog uses a UTF-8 code page, the error file also uses a UTF-8 code page.Error log files have the following structure:

[Session Header][Column Header][Column Data]

Session header. Contains session run information. Information in the session header is

like the information stored in the PMERR_SESS table.

Column header. Contains data column names.

Column data. Contains actual row data and error message information.

The following sample error log file contains a session header, column header, and column data:

**********************************************************************Repository GID: fe4817ab-7d87-465f-9110-354222424df0Repository: CustomerInfoFolder: Row_Error_LoggingWorkflow: wf_basic_REL_errors_AGG_caseSession: s_m_basic_REL_errors_AGG_caseMapping: m_basic_REL_errors_AGG_caseWorkflow Run ID: 1310Worklet Run ID: 0Session Instance ID: 19Session Start Time: 08/03/2004 16:57:01Session Start Time (UTC): 1067126221**********************************************************************Transformation||Transformation Mapplet Name||TransformationGroup||Partition Index||Transformation Row ID||Error Sequence||ErrorTimestamp||Error UTC Time||Error Code||Error Message||ErrorType||Transformation Data||Source Mapplet Name||Source Name||Source RowID||Source Row Type||Source Dataagg_REL_basic||N/A||Input||1||1||1||08/03/200416:57:03||1067126223||11019||Port [CUST_ID_NULL]: Default value is:

14


15/16


13/06/2013

ERROR( [ERROR]: [AGG] CUST_ID - NULL detected on input.\n...nl:ERROR(s:'[AGG] CUST_ID - NULL detected on input.')).||3||D:1221|N:|N:|N:|D:KauaiDive Shoppe|D:4-976 Sugarloaf Hwy|D:Kapaa Kauai|D:HI|D:94766|D:[AGG] DEFAULTSID VALUE.|D:01/01/2001 00:00:00||mplt_add_NULLs_to_QACUST3||SQ_QACUST3||1||0||D:1221|D:Kauai Dive Shoppe|D:4-976 Sugarloaf Hwy|D:Kapaa Kauai|D:HI|D:94766agg_REL_basic||N/A||Input||1||4||1||08/03/200416:57:03||1067126223||11019||Port [CITY_IN]: Default value is: ERROR( [ERROR]: [AGG] Null detected for City_IN.\n... nl:ERROR(s:'[AGG] Null detectedfor City_IN.')).||3||D:1354|N:|N:|D:1354|T:Cayman Divers World|D:PO Box 541|N:|D:Gr|N:|D:[AGG] DEFAULT SID VALUE.|D:01/01/200100:00:00||mplt_add_NULLs_to_QACUST3||SQ_QACUST3||4||0||D:1354|D:Cayman DiversWorld Unlim|D:PO Box 541|N:|D:Gr|N: agg_REL_basic||N/A||Input||1||5||1||08/03/200416:57:03||1067126223||11131||Transformation [agg_REL_basic] had an errorevaluating variable column [Var_Divide_by_Price]. Error message is [ [/]: divisor is zero\n... f:(f:2 / f:(f:1 -f:TO_FLOAT(i:1)))].||3||D:1356|N:|N:|D:1356|T:Tom Sawyer Diving C|T:632-1Third Frydenh|D:Christiansted|D:St|D:00820|D:[AGG] DEFAULT SID VALUE.|D:01/01/200100:00:00||mplt_add_NULLs_to_QACUST3||SQ_QACUST3||5||0||D:1356|D:Tom Sawyer

Diving Centre|D:632-1 Third Frydenho|D:Christiansted|D:St|D:00820

15


16/16


13/06/2013

The following table describes the columns in an error log file:

16

Date post:	03-Apr-2018
Category:	Documents
Upload:	senthil-kumar
View:	217 times
Download:	0 times

Informatica Logs Explanation

Documents