difference between stop and abort

Answers were Sorted based on User's Feedback



difference between stop and abort..

Answer / malathi

Stopping a session task means the server stops reading data.

Abort has timeout of 60 sec , If the server is not finished
processing and committing data by the timeout ,the threads
and process assosiated with the sessions are killed.

Is This Answer Correct ?    10 Yes 1 No

difference between stop and abort..

Answer / neets

abort stops the session forcefully so in less time it stops
our task as compared to stop.

Is This Answer Correct ?    8 Yes 5 No

Post New Answer

More Informatica Interview Questions

Hi, This is Ranadheer. How to load fact tables using dimeension tables. Please anyone give me a answer with example. Thanks in Advance.

1 Answers  


Define error Threshold?

1 Answers  


What is DR strategy for Informatica project?

0 Answers  


3. Suppose Seq Gen is supplying a increamental value to a column of a table, suppose, table's column value reaches to maximum value, then what will happen, will the session fail? If it is the situation, then what should be done so that we can stop this kind of situation in advance?

7 Answers   Accenture,


How will you check the bottle necks in informatica? From where do you start checking?

3 Answers   HCL,






I have table with ID,PRD_DT,PRD_FLAG,CUST_DT,CUST_FLAG I need to get max date and its corresponding flag for both the date columns. Ex:- 1A,10/3/2015,AC,10/3/2015,XY 1A,10/4/2015,AB,10/2/2015,XZ Output needed 1A,10/4/2015,10/3/2015,XY I have 100 million + in the table so avoid self-join...

2 Answers   Amex,


How to join three sources using joiner? Explain though mapping flow.

0 Answers  


generate Unique sequence numbers for each partition in session with Unconnected Lookup ? Hi All, Please help me to resolve the below issue while Applying partitioning concept to my Session. This is a very simple mapping with Source, Lookup , router, and target. I need to Lookup on the target and compare with the source data, if any piece of data is new then Insert, and If any thing change in the existed data then Update. while Inserting the new records to the target table I'm generating sequence numbers with Unconnected lookup, by calling the maximum PK ID from the target table. The above flow is working fine from last one year. Now I wish to apply the Partitioning concept to the above floe(session) At source I used 4 pass through partitions.(For Each partition different filter conditions to pull the data from source) at Target I used 4 passthrough Partitions. it is working fine for some data, but for some rows for Insert Operation , it is throwing Unique key errors, because while Inserting the data it is generating the same sequence key twice. In detail : 1st row is coming from 1st partition and generated the sequence number 1 for that row. 2nd row is coming from 1st partition and generated the sequence number 2 for that row 3rd row is coming from the 2nd partition generated the sequence number 2 again for that row. (it must generate 3 for this row) the issue is becuase of generating the same sequence numbers twice for different partitions. Can any one Please help me to resolve this issue. While Applying partitions how can I generate a Unique Sequence numbers from Unconnected lookup for Each partitioned data. Regrads, N Kiran.

2 Answers   Tech Mahindra,


how to load rows into fact table in data warehouse

0 Answers   Informatica,


what is the main advantage of unconnected lookup

2 Answers   Cap Gemini,


why we r using presql&postsql in source qualifier?

1 Answers   HP,


How to load time dimension?

1 Answers   Ford,


Categories