Few tips to follow in case of issues with Informatica debugger. Seeing Informatica developer fussy is very common scenario we all developers face. At times, these kinds of issues end up putting us in trouble.
This post is for beginners. Please avoid reading it, if you have good experience on tool. Estimated time to read this post is 5 Minutes. 🙂
Tried to write post on Informatica debugger after consulting with Peer bloggers to cover almost all the aspect of fix. Informatica debugger doesn’t not work after this as well. I would apologies and request you to look for others help.
Your client installed on your machine should have the same version as on server . So one always first check with the informatica administrator or team members regarding client version need to be used. If he can give you right version of client. Please don’t take me wrong. I understand that repository itself will not install in case of version difference. Provided Informatica architecture is different. In most of l case this is one the biggest problem I have seen.
Ensure Mapping and sessions are valid without any failure, do a dry run.
I should not have included it. I know it is so obvious, just including it for beginners. One need to ensure that workflow is getting completed successfully once. If there are any errors then please fix them.
Ensure that records are qualifying.
Your debugger doesn’t get initiated if you have no records to qualify. So ensure, that you have some 2-3 records at least which can qualify from source qualifier. Moreover, what I have noticed that if run debugger with fewer records (like 1 or 2 records) chances of getting it initialized more. Later we can increase number of records which needs to be tested.
Ensure records are qualifying for look-up as well.
Above three steps are enough for Informatica debugger to run. Steps below are precautionary steps. You are advised to ensure these steps one by one if no luck. If possible fill up your look-up as well with few records. If not with few records then try to fill it up matching records which you have set up for source data. This might be required only in case your mapping is very complex. This generally happens in transactional processing mapping or with those kind of mappings which does the job of transaction validation.
If you have flat file look-up then please ensure that flat file has data in it. At least for the corresponding records you have setup to test in source Custom.
Custom transformation / Parameter file.
We have generally observed that Debugger doesn’t work good with custom transformation Alternative to this, Try to skip custom transformation step by marking look-up for next transformation. If you want to see the data output after custom transformation then try to see it by placing a expression after custom transformation or flat file target which you can delete later.
Last but not least
If nothing works. Really if nothing works. I understand it will be painful at the same time we have to do something to get it going. Place a dummy Flat file target after transformation. It will help to understand that till which transformation data is moving. With this you can isolate transformation which is creating problem.
Though this solution is very tedious one. It can only help who has good understanding for data and it’s transformation. One need to understand source data setup and able to imagine how particular records should have changed after.