Skip to main content

Some Tricks in Informatica

After a bit of gap, i am back here.So instead discussing about a specific topic, let me tell you about some tricks/tips that can be used while working in informatica

Worklet as we know is a set of reusable tasks.We cannot start a single task individually in worklet from workflow manager. we need to run the worklet in order the start the individual tasks assigned to it.Although after a run in completed from workflow monitor we can start tasks individually from monitor.

If a worklfow which has schedule assigned to it gets failed, then it gets unscheduled so we need to reschedule it again by doing right click in workflow manger and select schedule workflow.

If the following error appears while trying logging in informatica

 
Then try restarting services by doing the following steps go to run and type services.msc, there search
for informatica sever then right click select restart.
 
Joiner vs lookup - It is advisable to choose joiner transformation when there are large no of records in the source table as the performance will be better when compared to lookup.
 
Hope this article helps you in your informatica projects
 

 
 
 
 
 

Comments

  1. Hey Admin, we dont have these kind of privileges..

    ReplyDelete
  2. Hi Ravi, What privileges are you talking about>

    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

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.