Skip to main content

Debugger in Informatica


We usually go for Debugger in informatica when we want to check at which level (i.e. transformation) in a mapping the data is getting wrongly populated or missing functionality.

Suppose we are expecting a date field to be populated in YYYYMMDD format but it is populating in DDMMYYYY format.Then using debugger we can check in which expression or source qualifier the data is coming wrong.

While using the debugger it's better to restrict the data to lesser records(preferably single record)  i.e. we can restrict at SQ level by passing condition e.g where emp_id='1001' so as to get only 1001 record.

In designer under mappings tab we need to click debugger.Then start debugger (F9) after which we will be getting option to choose integration service and we will be having three options.

a) use an existing session instance
b) use an existing reusable session instance
c) create a debug session instance.




we can click the existing session instance. After which it will ask for select session and then ask for which all targets are needed. We can select all the Target's or any particular one of which we want to view data.

Then the debugger gets started. We need to press F10 to move from one transformation to another if we want to jump directly to a particular transformation then we need to press ctrl + F10 after selecting that particular transformation.

If we have multiple rows then we need to press multiple time ctrl+f10 to view all the records say we have 5 records and we want to see all the 5 records then we need to press 5 times to view all the 5 records.

Debugger will be looking like below



We can stop debugger by again going to mappings tab.

Note:once we stop debugger we can see in wf monitor that particular session would be in failed state.

Hope this article helps you in understanding debugger

Comments

  1. Really nice blog post. provided helpful information. I hope that you will post more updates like thisInformatica Training

    ReplyDelete

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Labelling and creating queries in informatica

Informatica components i.e. mappings,session,workflows,transformation are moved from one environment to another environment say from development to SIT can be done in various ways such as --Export the xml's and again import the xml's in the respective environment --Drag and Drop objects from one repository to another repository For the above process to be done you should have required access across environments. One other way is labelling the components and then creating queries in repository manager. Using these queries components are moved across environment's We need to go to the repository manager and select the version tab and select label Then click new label and give a name say "Wf Migration" and click OK. There we  have permissions tab where we can give access to other users to use the same label. Now we need to select the workflow which needs to be promoted to higher environment.  Right click on workflow and select "view dependencies...

Pre and Post Sql,Session properties at session level

Sometimes we may have a requirement where might need to drop indexes/truncate table and then load the data. So in here what we can we do is we can go for pre sql in session properties and there we can write the required the sql statements such as dropping indexes or truncating table and after the loads i.e. session gets completed we can recreate the indexes in post sql command. In mapping also we can do the same but it is advisable to do at session level. We even have option in session such as Presession, Postsession command and Postsession failure command. In session go to components tab to find out these options. Upon requirement we can use the following command to run unix scripts for specific purpose. We have email option option for on success/failure scenarios too. Hope this article helps you in understanding post/pre session commands