ravi kumar guturi

• Mar 8th, 2006

 

Simple solution,

Nothing by using performance recovery option

satyam

• Mar 13th, 2006

 

firast find out the errors and rectify the errors and also use performance recovery method.

SSekar

 Profile Answers by SSekar 

• Mar 17th, 2006

 

Running the session in recovery mode will work, but the target load type should be normal. If its bulk then recovery wont work as expected

Vasan

• Apr 6th, 2006

 

Skip the number of initial rows to skip to 10001 in the source type option from session property

manju

• Jun 21st, 2006

 

Question

Running the session in recovery mode will work?

what is the meaning of running the session in recover mode and how to do that kindly provde me the steps

Regards

manju

suha

• Jan 2nd, 2007

 

    hi,

       useing performance recovery  to load the target

 they are  3  types of performance   recovery

1 ) we enable the  recovery option in session

2) we put a commite intervel point  in session

finally

3)  trancate the target and  loading newly

thanks

geetham

 Profile Answers by geetham Questions by geetham

• Jan 4th, 2007

 

Can anyone explain about running session in recovery mode?

kirangvr

 Profile Answers by kirangvr Questions by kirangvr

• Feb 1st, 2007

 

The session should be enable for recovery and you can do that by simply checking a box in the session. But one should remember that the data should be sorted from SQ, otherwise you will get inconsistent data. if the session failed/ suspended, you can right click on the session in the monitor and click on recover the task. Hope it helps you.

Maharishi

• May 7th, 2007

 

There are many ways to find out number of records loaded and rejected. One of the way is : You can find information in the repository table "PM_RECOVERY" that how many number of records are loaded out of the total number of records, if you are able to track such information in auditing tables, you can run the session with any number of records.


Thanks

uppala chary

• Aug 28th, 2011

 

In session properties use session recovery strategy.

srinivas

• Sep 14th, 2011

 

In Informatica 8.6, recovery feature is improved. Informatica server writes real time recovery info to a queue which helps maintain data integrity during recovery. So, no data is lost or duplicated. Recovery queue stores reader state, commit number and messageID informatica server committed to target. During recovery, informatica server uses recovery info to determine where it stopped processing.
The recovery ignore list stores message IDs that IS wrote to target for failed session. Informatica server writes recovery info to the list if there is a chance that source did not receive an acknowledgement. While recovering, informatica server uses recovery ignore list to prevent data duplication.

There are three options for recovery.
1. Fail task and continue work flow.
2. Resume from last checkpoint.
3. Restart task.

For the above question, resume from last checkpoint option will be best.