Commit Interval:

Commit interval is the interval at which informatica server commits data in to target
table based on commit points .

Different types of commits :

Source based commit
target based commit
user defined commit

Source based commit : Informatica server commits data in to target table based on
commit interval .

Target based commit : Informatica server commits data in to target table

irrespective of commit interval,
It try's to fill writer buffer and once writer buffer got filled then informatica server
commits data in to
target table .

Which commit performance will be good?

Target based commit performance will be good as there will be less number of
commits

Error Handling in session :

I want to stop session if i get one transformation error ?

By putting stop on errors =1 you can achieve this requirement

I want to store every session log file how can we achieve this ?

By keeping save session log by time stamp we achieve this .

I just need to load 5 log files of a session how can we achieve this ?

By keeping number of session runs =5 in session properties we can achieve this .

Normal load:

When we run mapping with normal load informatica server commits data in to
target table
as well as it commits row-id's in to opbserver recovery table(log table).
When when we run a session with normal load there is scope of recovery .
For an example you are extracting 100 records from source and given commit
interval as 10 and
assume if your session got failed at 81th recode and you have opened the log file
and fixed the issue
so when we restart the session instead of loading in to target table from scratch it
starts loading from
where it got failed(when you fix the issue and restart the session

informatica server connects to opb server recovery table and checks last row id
commited in to log table
and starts loading from max id+1 .

Bulk Load :

When we run a session with bulk load informatica server bypasses the data base log
it just commits data in to
target table so there is no scope of recovery .

In Bulk load performance will be good but we need to ensure the following things
when we run a session with bulk load .

There should by no indexes in target table and your load strategy should be only
insert .

I need indexes on target table and i need to laod with bulk load can't we achieve
this?

We can achive using target pre and post sql .

Presql: Drop index idx_name ;

Postsql: Create index idx_name on table_name(col_name);

What are the different tabs present in workflow monitor :

Grant chat and task view

in Grant chart you can view only the current status runs.

In task chart you can view 20 runs of a session .