top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Performance tuning of session and workflow in Informatica?

+2 votes
556 views

How to tune the session, workflow for better performance, what are the things we consider for better performance?

posted Mar 2, 2016 by Amit Sharma

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

Partitioning, line sequential buffer length, tracing level as terse, collect performance data as enabled, commit interval are some of the pointers for session level performance tuning.

Make sure the Sorted Inputs enabled for Joiner, Lookup and Aggregate transformations in workflow. Use Dynamic cache for lookups whenever needed otherwise cache takes more spaces (instead of cache)

answer Mar 3, 2016 by Manikandan J
Similar Questions
0 votes

For cleaning up unused IPC-Sources I need a Repository Query for getting Workflow, Session, Mapping and Source/Target of Mapping.I have startet by joining REP_LOAD_SESSIONS and REP_TBL_MAPPING on mapping_id but only a fraction of mappings seem to be present in the joined output. I can't find the right tables to join to get the job done. Any help will be greatly appreciated!

+2 votes

I have two sessions I a workflow like below

workflow1->session1->session2

I have a join_date column in a table in Mapping1 , in session1. I want to pick this join_date value and pass to mpping2/session2

If join date value changes in the table in session1 then the same value should pick and pass to session2. I will use this date value in a query in session2 .

Please suggest how to achieve this?

0 votes

Can anyone tell me how to find the list of mapping and the workflow that are using a particular table say X either as a source or target table?

0 votes

When I look at many of the workflow last sessions runs in the workflow monitor I see the number of records that are picked by the transformation is different than the number of records that get updated or inserted in the target table.

For example my sql transformation picks 80,742 rows from the source table. but only 29,813 rows get loaded into the target table.

On further analyzing the workflow log file I can see it loaded both insertable records and updatable records:

WRT_8036 Target: W_SALES_ORDER_LINE_F (Instance Name: [W_SALES_ORDER_LINE_F]) WRT_8038 Inserted rows - Requested: 15284
 Applied: 15284 Rejected: 0 Affected: 15284 WRT_8041 Updated rows - Requested: 14529 Applied: 14529 Rejected: 0 Affected: 14529 

WRITER_1_*_1> WRT_8035 Load complete time: Wed Mar 19 04:41:24 2014

I am not able to figure out why would the workflows load lesser records than what source sql gives. and I would really appreciate some help in this matter.

Thanks

...