In for Matic a Logs Explanation

7/24/2019 In for Matic a Logs Explanation

1/15

Informatica Training

16/02/2016

Log Files

The PowerCenter Server can create log files for each workflow it runs These files containinformation a!out the tasks the PowerCenter Server "erforms# "lus statistics a!out the workflowan$ all sessions in the workflow If the writer or target $ata!ase re%ects $ata $uring a session run#the PowerCenter Server creates a file that contains the re%ecte$ rowsThe PowerCenter Server can create the following t&"es of log files'

(Workflow log. Contains information a!out the workflow run such as workflow name# taskse)ecute$# an$ workflow errors *& $efault# the PowerCenter Server writes this informationto the server log or +in$ows ,vent Log# $e"en$ing on how &ou configure the PowerCenterServer If &ou wish to create a workflow log# enter a workflow file name in the workflow"ro"erties

(Session log. Contains information a!out the tasks that the PowerCenter Server "erforms$uring a session# "lus loa$ summar& an$ transformation statistics *& $efault# thePowerCenter Server creates one session log for each session it runs If a workflow containsmulti"le sessions# the PowerCenter Server creates a se"arate session log for each sessionin the workflow

(Reject file. Contains rows re%ecte$ !& the writer or target file $uring a session run If thewriter or target $oes not re%ect an& $ata $uring a session# the PowerCenter Server $oes notgenerate a re%ect file for that session *& $efault# the PowerCenter Server saves each t&"eof log file in its own $irector& The PowerCenter Server re"resents these $irectories usingserver varia!les

-ou can change the $efault $irectories at the server level !& e$iting the server connection in the+orkflow .anager -ou can also overri$e these values for in$ivi$ual workflows or sessions !&u"$ating the workflow or session "ro"erties

Log File Type Default Directory Value

+orkflow logs P.+orkflowLogir P.ootir/+orkflowLogs

Session logs P.SessionLogir P.ootir/SessLogse%ect files P.*a$Fileir P.ootir/*a$Files

+orkflow Logs

-ou can configure a workflow to create a workflow log +hen &ou $o this# the PowerCenter Serverwrites information such as "rocess initialiation# workflow task run information# errors encountere$#an$ workflow run summar& to the workflow logIn general# a workflow log contains the following information a!out the workflow'

(+orkflow name

(+orkflow status

(Status of tasks an$ worklets in the workflow

(Start an$ en$ times for tasks an$ worklets

(esults of link con$itions

(Some session messages an$ errors

(,rrors encountere$ $uring the workflow

The PowerCenter Server categories workflow log error messages into severit& levels ThePowerCenter Server either writes or $oes not write an error message to the log file !ase$ on the

1


2/15


16/02/2016

error severit& level -ou can set the ,rror Severit& Level for Log Files in the PowerCenter Serversetu" "rogram-ou can also configure the PowerCenter Server to su""ress writing messages to the workflow logfile com"letel& 3s with PowerCenter Server logs an$ session logs# the PowerCenter Server entersa co$e num!er into the workflow log file message along with message te)t-ou configure a workflow to create a workflow log !& entering a workflow log file name in theworkflow "ro"erties If &ou choose to create a workflow log# the PowerCenter Server saves theworkflow log in a $irector& entere$ for the server varia!le P.+orkflowLogir in the PowerCenterServer registration -ou can overri$e the workflow log $irector& at the server level or at the workflowlevel*& $efault# the PowerCenter Server saves one workflow log for each workflow If &ou want to savemulti"le logs for $ifferent workflow runs# &ou can configure the workflow to save a workflow log file!& timestam"# which "ermits an unlimite$ num!er of workflow logs# or !& run# which saves as"ecifie$ num!er of logs To view "revious workflow logs# save log files !& timestam"If &ou choose not to create workflow logs# the PowerCenter Server writes the workflow logmessages to the server log or +in$ows ,vent Log# $e"en$ing on how &ou configure thePowerCenter Server

+orkflow Log .essages

The PowerCenter Server "rece$es each message in the log file with a co$e an$ num!er It also"rece$es some messages with a timestam" The co$e $efines a grou" of messages for a s"ecific"rocess The num!er $efines a s"ecific message The message can "rovi$e general information orit can !e an error message-ou can configure the PowerCenter Server to a""en$ a time stam" to ever& message it writes tothe workflow log To $o this# ena!le the Time Stam" +orkflow Log o"tion in the PowerCenter Serversetu" "rogram

+orkflow Log Co$es

-ou can use the workflow log to $etermine the cause of workflow "ro!lems To resolve workflow"ro!lems# locate the relevant log file co$es an$ te)t "refi)es in the workflow log# then see theTroubleshooting Guide for $etails -ou can fin$ workflow4relate$ server messages in the 5I7server log 8$efault name' "mserverlog9 or in the +in$ows ,vent Log 8viewe$ with the ,vent:iewer9

+orkflow Log Sam"le

The following sam"le is a workflow log from a sim"le workflow that shows log file co$es'

INFO : LM_36315 [Tue Nov 18 11:16:38 2003] : (270|305) Start!" e#e$uto! o% &or'o&[&%_*o!eL+t],INFO : LM_36330 [Tue Nov 18 11:16:38 2003] : (270|305) Start!" e#e$uto! o% +tart !+ta!$e[Start-or'o&],INFO : LM_36333 [Tue Nov 18 11:16:38 2003] : (270|305) .#e$uto! o% +tart !+ta!$e

[Start-or'o&] +u$$ee/e/,INFO : LM_36505 : (270|305) L!' [Start-or'o& +_*o!eL+t]: et4 e#re++o! +tr!"evauate/ to T.,INFO : LM_36330 [Tue Nov 18 11:16:38 2003] : (270|305) Start!" e#e$uto! o% +e++o! !+ta!$e[+_*o!eL+t],INFO : LM_36522 : (270|305) Starte/ 9TM ro$e++ [/ 273] %or +e++o! !+ta!$e [+_*o!eL+t],INFO : ;MN_1760 : (273|255) Me++a"e %ro +e++o!: LM_36033 [;o!!e$te/ to reo+tor4 [S$+erver>Se++Lo"+>+_*o!eL+t,o"],],

2


3/15


16/02/2016

INFO : LM_36333 [Tue Nov 18 11:16:?3 2003] : (270|306) .#e$uto! o% +e++o! !+ta!$e[+_*o!eL+t] +u$$ee/e/,INFO : LM_36318 [Tue Nov 18 11:16:?3 2003] : (270|306) .#e$uto! o% &or'o& [&%_*o!eL+t]+u$$ee/e/,

Configuring +orkflow Logs-ou can configure workflow log o"tions in the workflow "ro"erties -ou can configure the followinginformation for a workflow log'

(Location. -ou can configure the $irector& where &ou want the workflow log create$ *&$efault# the PowerCenter Server creates the workflow log in the $irector& configure$ for theP.+orkflowLogir server varia!le -ou can enter a $ifferent $irector !ut if the $irector&$oes not e)ist or is not local to the PowerCenter Server that runs the workflow# the workflowfails

(Name. If &ou wish to create a workflow log# &ou can enter a name for the workflow log file If&ou $o not enter a filename# the PowerCenter Server $oes not create a workflow logInstea$# the PowerCenter Server writes workflow log messages to the +in$ows ,vent Log

or 5I7 server log (Arci!e. -ou can configure the num!er of workflow logs &ou want the PowerCenter Server

to archive for each workflow *& $efault# the PowerCenter Server $oes not archive workflowlogs

3rchiving +orkflow Logs

*& $efault# the PowerCenter Server $oes not save multi"le logs for a single workflow It creates oneworkflow log for each workflow an$ overwrites the e)isting log with the latest workflow logIf &ou wish to save multi"le logs for a workflow# &ou can configure the PowerCenter Server to $othis The PowerCenter Server can save workflow logs in two wa&s'

(Save a selecte$ num!er of logs

(Save all logs !& timestam"

If &ou configure the workflow to save a s"ecific num!er of workflow logs# it names the most recentlog filenamelog It then c&cles through a close$ naming se;uence for historical logs as follows'filenamelog0# filenamelog1# filenamelog2#


4/15


16/02/2016

(mi = minute# ranging from 04?@

To "revent filling the workflow log $irector "erio$icall& $elete or !acku" log files when using thetimestam" o"tion

Ste"s for Configuring +orkflow Logs

-ou can configure workflow log information on the Pro"erties ta! of the workflow "ro"erties

1 In the +orkflow .anager# o"en the workflow "ro"erties2 Select the Pro"erties ta!

> ,nter the following workflow log o"tions'

A


5/15


16/02/2016

A Click B to save the workflow

:iewing +orkflow Logs

+orkflow logs are te)t files that &ou can o"en with an& te)t e$itor The PowerCenter Server savesworkflow logs in the $irector& &ou s"ecif& in the +orkflow Log File irector& fiel$ in the workflow"ro"erties -ou can also view workflow logs through the +orkflow .onitor +hen &ou $o this# the+orkflow .anager creates a tem"orar& file that stores the workflow log -ou can view thetem"orar& file through the +orkflow .onitor

The PowerCenter Server generates the workflow log !ase$ on the PowerCenter Server co$e "age-ou can s"ecif& the language in which &ou want to view the workflow log !ase$ on the locale of themachine hosting the PowerCenter Server

To use the +orkflow .onitor to view the most recent workflow log'

1 In the avigator win$ow# connect to the server on which the workflow runs2 B"en the fol$er that contains the workflow> ight4click the workflow an$ choose Det +orkflow Log

?


6/15


16/02/2016

If &ou save workflow logs !& timestam"# &ou can also use the +orkflow .onitor to view "astworkflow logs To $o this# right click the workflow in the Dantt chart view an$ choose Det +orkflowLog

Session Logs

The session log file contains information a!out all tasks the PowerCenter Server "erforms# "lus theloa$ summar& an$ transformation statistics The amount of $etail in the session log $e"en$s on thetracing level that &ou set -ou can $efine the tracing level for each transformation or for the entiresession The session4level tracing overri$es an& transformation4level tracing levelsIn general# the session log contains the following information a!out the session'

(3llocation of s&stem share$ memor&

(,)ecution of "re4session comman$s

(Creation of SEL comman$s for rea$er an$ writer threa$s

(Start an$ en$ times for target loa$ing

(,rrors encountere$ $uring session

(,)ecution of "ost4session comman$s (Loa$ summar& of rea$er# writer# an$ ata Transformation .anager 8T.9 statistics

*& $efault# the PowerCenter Server saves session logs in the $irector& for the PowerCenter Servervaria!le P.SessionLogir# which &ou $efine in the +orkflow .anager The $efault name for thesession log is s_mapping namelog -ou can overri$e the session log name an$ location in thesession "ro"ertiesThe PowerCenter Server $oes not archive session logs !& $efault Instea$# it creates one log foreach session an$ overwrites the e)isting log with the latest session log owever# &ou can configurethe session to archive session logs*& $efault# the PowerCenter Server generates session log files !ase$ on the PowerCenter Serverco$e "age owever# if &ou ena!le the But"ut Session Log in 5TF4G o"tion on the Configuration ta!of the PowerCenter Server setu" "rogram# the PowerCenter Server writes to the session log usingthe 5TF4G character set

Session Log .essages

The PowerCenter Server "rece$es each message in the log file with a threa$ i$entification an$ thena co$e an$ num!er The co$e $efines a grou" of messages for a s"ecific "rocess The num!er$efines a s"ecific message The message can "rovi$e general information or it can !e an errormessage-ou can configure the PowerCenter Server to write session log messages to an e)ternal li!rar& aswell as to the session log To $o this# &ou can set the ,)"ort Session Log Li! ame in thePowerCenter Server setu" "rogram

Session Log Co$es

-ou can use the session log to $etermine the cause of session "ro!lems To resolve session"ro!lems# locate the relevant log file co$es an$ te)t "refi)es in the session log# then see theTroubleshooting Guide for $etails -ou can fin$ session4relate$ server messages in the 5I7 serverlog 8$efault name' "mserverlog9 or in the +in$ows ,vent Log 8viewe$ with the ,vent :iewer9

"essage co#e Description

*L.essages relate$ to rea$er "rocess# inclu$ing

3""lication# relational# or flat file

6


7/15


16/02/2016

C7.essages relate$ to the e"ositor& 3gentconnections

C..essages relate$ to $ata!ases# memor&allocation# Looku" an$ Hoiner transformations# an$internal errors

*D .essages relate$ to PowerCenter Server loa$ingan$ $e!ugging

*D .essages relate$ to the e!ugger

,P .essages relate$ to e)ternal "roce$ures

,S .essages relate$ to the e"ositor& Server

F .essages relate$ to file sources

FTP.essages relate$ to File Transfer Protocolo"erations

I, .essages relate$ to rea$ing 7.L sources

L. .essages relate$ to the Loa$ .anager

TS,: .essages relate$ to +in$ows server o"erations

B*H. .essages relate$ to the e"ositor& 3gent

BL .essages relate$ to $ata!ase functions

P,TL .essages relate$ to "i"eline "artitioning

P.F.essages relate$ to caching 3ggregator# ank#Hoiner# or Looku" transformations

3PP .essages relate$ to the e"ositor& 3gent

,P .essages relate$ to re"ositor& functions

.essages relate$ to relational sources

SF.essages relate$ to server framework# use$ !&Loa$ .anager an$ e"ositor& Server

SBT .essages relate$ to the Sorter transformation

T, .essages relate$ to transformations

T..essages relate$ to ata Transformation.anager 8T.9

TT .essages relate$ to transformations

:3 .essages relate$ to ma""ing varia!les

+T .essages relate$ to the +riter

7.L .essages relate$ to the 7.L ea$er

7.L+ .essages relate$ to the 7.L +riter

Threa$ I$entification

The threa$ i$entification consists of the threa$ t&"e an$ a series of num!ers se"arate$ !&un$erscores The num!ers following a threa$ name in$icate the following information'

(Target loa$ or$er grou" num!er

(Partition "oint num!er

(Partition num!er


8/15


16/02/2016

The PowerCenter Server "rints the threa$ i$entification !efore the log file co$e an$ the messagete)t in the session log The following e)am"le illustrates a rea$er threa$ from target loa$ or$ergrou" one# concurrent source set one# source "i"eline one# an$ "artition one'

.


9/15


16/02/2016

Loa$ Summar&

The session log inclu$es a loa$ summar& that re"orts the num!er of rows inserte$# u"$ate$#$elete$# an$ re%ecte$ for each target as of the last commit "oint The PowerCenter Server re"ortsthe loa$ summar& for each session !& $efault owever# &ou can set tracing level to :er!ose

Initialiation or :er!ose ata to re"ort the loa$ summar& for each transformationThe following sam"le is an e)cer"t from a loa$ summar&'

GGGGGST# 2# an$ 2 -ou mark rows for u"$ate where S3L,SJI is 2 The writeraffects three rows# even though there was onl& one u"$ate request Br# if &ou mark rows foru"$ate where S3L,SJI is A# the writer affects 0 rows

(Delete#. Shows the num!er of rows the PowerCenter Server marke$ to remove from thetarget The num!er of affected rows can !e $ifferent from the num!er of requested rows

(Rejecte#. Shows the num!er of rows the PowerCenter Server re%ecte$ $uring the writing"rocess These rows cannot !e a""lie$ to the target For the e%ecte$ rows categor thenum!er of affected an$ applied rows is alwa&s ero since these rows are not written to thetarget

The loa$ summar& "rovi$es the following statistics'

(Re&ueste# rows. Shows the num!er of rows the writer actuall& receive$ for the s"ecifie$o"eration

(Applie# rows. Shows the num!er of rows the writer successfull& a""lie$ to the target 8thatis# the target returne$ no errors9

(Affecte# rows. Shows the num!er of rows affecte$ !& the s"ecifie$ o"eration e"en$ingon the o"eration# the num!er of affected rows can !e $ifferent from the num!er ofrequested rows For e)am"le# &ou have a ta!le with one column calle$ S3L,SJI an$ fiverows containing the values' 1# 2# ># 2# an$ 2 -ou mark rows for u"$ate where S3L,SJI is

@


10/15


16/02/2016

2 The writer affects three rows# even though there was onl& one u"$ate request Br# if &oumark rows for u"$ate where S3L,SJI is A# the writer affects 0 rows

(Rejecte# rows. Shows the num!er of rows the writer coul$ not a""l& to the target Fore)am"le# the target $ata!ase re%ects a row if the PowerCenter Server attem"ts to insert5LL into a not4null fiel$ The PowerCenter Server writes all re%ecte$ rows to the sessionre%ect file# or to the row error log# $e"en$ing on how &ou configure the session

("utate# from up#ate. Shows the num!er of rows originall& flagge$ for update that areinstea$ inserted into the target when the session is configure$ 5"$ate ,lse Insert

If the num!er of rows re;ueste$# a""lie$# re%ecte$# an$ affecte$ are all ero for an& of thesefour o"erations# the o"eration $oes not a""ear as a line in the loa$ summar& If no $ata is"asse$ to the target# the writer re"orts the following message'

No /ata oa/e/ %or t*+ tar"et,

etaile$ Transformation Statistics

The T. ena!les transformation statistics in the session log for two levels of tracing# :er!oseInitialiation an$ :er!ose ata Transformation statistics a""ear after the loa$ summar& in the log

file The PowerCenter Server re"orts the following $etails for each transformation in the ma""ing'

(The name of the transformation

(The num!er of in"ut rows an$ the name of the in"ut source

(The num!er of out"ut rows an$ the name of the out"ut transformation or target

(The num!er of rows $ro""e$

The following sam"le is an e)cer"t from the transformation statistics in a session log file'

9.T


11/15


16/02/2016

Configuring Session Logs

Configure session log o"tions in the session "ro"erties -ou can configure the following informationfor a session log'

(Location. -ou can configure the $irector& where &ou want the session log create$ *&$efault# the PowerCenter Server creates the session log in the $irector& configure$ for theP.SessionLogir server varia!le -ou can enter a $ifferent $irector !ut if the $irector&$oes not e)ist or is not local to the PowerCenter Server that runs the session# the sessionfails

(Name. -ou can name the session log or acce"t the $efault name The $efault name for thesession log is s_mapping namelog

(Arci!e. -ou can configure the num!er of session logs &ou want the PowerCenter Serverto archive for each session *& $efault# the PowerCenter Server $oes not archive sessionlogs

(Tracing le!els. -ou can control the t&"e of information the PowerCenter Server inclu$es inthe session log !& setting a tracing level for the session *& $efault# the PowerCenterServer uses tracing levels configure$ in the ma""ing

Configuring Session Log Locations an$ Filenames

-ou can configure the name an$ location of the session log on the Pro"erties ta! of the session"ro"ertiesTo configure session log information'

1 In the +orkflow .anager# o"en the session "ro"erties2 Select the Deneral B"tions settings on the Pro"erties ta!> ,nter the following session log o"tions'A Click B to save the session

3rchiving Session Logs

-ou can archive session logs on a session4!&4session !asis The PowerCenter Server can savesession logs in the following wa&s'

(Save a selecte$ num!er of logs

(Save all logs !& timestam"

*& $efault# the PowerCenter Server $oes not archive session logs It creates one session log foreach session an$ overwrites the e)isting log with the latest session logIf &ou configure the session to save a s"ecific num!er of session logs# it names the most recent logs_mapping namelog It then c&cles through a close$ naming se;uence for historical logs asfollows' s_mapping name.log0# s_mapping namelog1# s_mapping namelog2#


12/15


16/02/2016

-ou can also save all session logs !& configuring a session to save logs !& timestam" +hentimestam"ing session logs# the PowerCenter Server a""en$s the month# $a hour# an$ minute ofthe session com"letion to the log file The resulting log file name is s_mappingname.logyyyymmddhhmi# where'

(yyyy = &ear

(mm = month# ranging from 1412 (dd = $a ranging from 14>1

(hh = hour# ranging from 042>

(mi = minute# ranging from 04?@

To "revent filling the session log $irector "erio$icall& $elete or !acku" log files when using thetimestam" o"tionTo s"ecif& archiving information'

1 In the +orkflow .anager# o"en the session "ro"erties2 Select the Log B"tions settings on the Config B!%ect ta!> ,nter the following session log o"tions'A Click B to save the session

Setting Tracing Levels

The amount of $etail in the session log $e"en$s on the tracing level that &ou set -ou can $efinetracing levels for each transformation or for the entire session *& $efault# the PowerCenter Serveruses tracing levels configure$ in the ma""ingSetting a tracing level for the session overri$es the tracing levels configure$ for each transformationin the ma""ing If &ou select a normal tracing level or higher# the PowerCenter Server writes rowerrors into the session log# inclu$ing the transformation in which the error occurre$ an$ com"leterow $ata If &ou configure the session for row error logging# the PowerCenter Server writes rowerrors to the error log instea$ of the session log If &ou want the PowerCenter Server to write$ro""e$ rows to the session log as well# configure the session with :er!ose ata tracing level

-ou can also enter tracing levels for in$ivi$ual transformations in the ma""ing +hen &ou enter atracing level in the session "ro"erties# &ou overri$e tracing levels configure$ for transformations inthe ma""ingTo set the tracing level'

1 Select the ,rror an$ling settings on the Config B!%ect ta!2 Select a tracing level from the Bverri$e Tracing list> Click B to save the session

:iewing Session Logs

Session logs are te)t files that &ou can o"en with an& te)t e$itor The PowerCenter Server saves

session logs in the $irector& &ou s"ecif& in the Session Log File irector& fiel$ in the session"ro"erties-ou can also view session logs through the +orkflow .onitor +hen &ou $o this# the +orkflow.onitor creates a tem"orar& file that stores the session log -ou can view the tem"orar& file throughthe +orkflow .onitor If a session fails# &ou can still view the session log fileThe PowerCenter Server generates the session log !ase$ on the PowerCenter Server co$e "age-ou can s"ecif& the language in which &ou want to view the session log !ase$ on the locale of themachine hosting the PowerCenter Server

12


13/15


16/02/2016

To use the +orkflow .onitor to view the most recent session log'

1 In the avigator win$ow# connect to the server on which the workflow runs2 B"en the fol$er that contains the workflow> B"en the workflow that contains the session whose log &ou wish to viewA ight4click the session an$ choose Det Session Log

If &ou save session logs !& timestam"# &ou can also use the +orkflow .onitor to view "ast sessionlogs To $o this# right4click the session in the Dantt chart view an$ choose Det Session Log

5n$erstan$ing the ,rror Log File

-ou can create an error log file to collect all errors that occur in a session This error log file is acolumn $elimite$ line se;uential file *& s"ecif&ing a uni;ue error log file name# &ou can create ase"arate log file for each session in a workflow +hen &ou want to anal&e the row errors for onl&one session# use an error log fileIn an error log file# $ou!le "i"es KM $elimit error logging columns *& $efault# "i"e KM $elimits row

$ata -ou can change this row $ata $elimiter !& setting the ata Column elimiter error log o"tionThe co$e "age for the error file is the same as the co$e "age for the session log file If the sessionlog uses a 5TF4G co$e "age# the error file also uses a 5TF4G co$e "age,rror log files have the following structure'

[Se++o! ea/er][;ou! ea/er][;ou! 9ata]

(Session ea#er. Contains session run information Information in the session hea$er is likethe information store$ in the P.,JS,SS ta!le

('olumn ea#er. Contains $ata column names

('olumn #ata. Contains actual row $ata an$ error message information

The following sam"le error log file contains a session hea$er# column hea$er# an$ column $ata'

GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGeo+tor4 AI9: %e?817aC7/87?65%11035?222?2?/%0eo+tor4: ;u+toerI!%oFo/er: o&_.rror_Lo""!"-or'o&: &%_Ca+$_.L_error+_


14/15


16/02/2016

.O(.#re++o! .rror [.O]: [!,,,!:.O(+:[


15/15


16/02/2016

The following ta!le $escri!es the columns in an error log file'

1?

Date post:	24-Feb-2018
Category:	Documents
Upload:	mithun
View:	218 times
Download:	0 times

In for Matic a Logs Explanation

Documents