Skip to main content

Cache in Informatica

What do you mean by Index cache and Data cache ?Explain it ?

1)Informatica server create Index and Data cache for Aggregator, Rank, Joiner, Look up Transformations.

2)Informatica server stores key values in Index cache,   and output values in data cache.

3)Informatica server  create cache files based on Informatica Server Code Page.

4)If Informatica server require more memory, it stores overflow values in cache files. If session completes server      releases cache memory and deletes cache files.

Transformation
Index Cache
Data Cache
Aggregator
Stores group values as configured in the Group-By ports.
Stores calculations based on the Group-By ports.
Rank
Stores group values as configured in the Group-By ports.
Stores ranking information based on the Group-By ports.
Joiner
Stores index values for the master source table as configured in the join condition.
Stores master source rows.
Lookup
Stores lookup condition information.
Stores lookup data that is not stored in the index cache.




Cache files located in which directory?
Informatica server locate index and data cache files in $PMCacheDir .
For index cache file it store with *.idx format and  for data cache file *.dat.

After successfully executing session Informatica server delete index and data cache files.

 
Cache in Informatica
Cache in Informatica
Explain Briefly about Session Caches?

Aggregator Cache, Rank Cache, Lookup Cache, Joiner Cache.


Aggregator Cache : 

When the Informatica Server runs a session with an Aggregator transformation, it stores data in memory until it completes the aggregation. When you partition a source that uses an Aggregator transformation, the Informatica Server creates one memory cache and one disk cache for each partition. It routes data from one partition to another based on group key values of the transformation

Rank Cache: 

When the Informatica Server runs a session with a Rank transformation, it compares an input row with rows in the data cache. If the input row out-ranks a stored row, the Informatica Server replaces the stored row with the input row.

Joiner Cache:

When the Informatica Server runs a session with a Joiner transformation, it reads all the rows from the master source and builds memory caches based on the master rows. After building these caches, the Informatica Server reads rows from the detail source and performs the joins.
The Informatica Server creates the index cache as it reads the master source into the data cache. The Informatica Server uses the index cache to test the join condition. When it finds a match, it retrieves row values from the data cache. 

To increase join performance, the Informatica Server aligns all data for joiner caches on an eight byte boundary.

Lookup Cache:

The Informatica Server builds a cache in memory when it processes the first row of data in a cached Lookup transformation. It allocates memory for the cache based on the amount you configure in the transformation or session properties. The Informatica Server stores condition values in the index cache and output values in the data cache. The Informatica Server queries the cache for each row that enters the transformation.

What is meant by Incremental Aggregation where it can be used?
Incremental Aggregation is used to improve session performance It is used only if source changes incrementally between sessions, and capture those incremental changes.

Comments

  1. Wonderful answers. Really a very good website for reference. Keep up the good work. Thanks for such a clear explanation.

    ReplyDelete
  2. very helpful thanks

    ReplyDelete
  3. what is size of Data Cache and Index cache?

    ReplyDelete

Post a Comment

Popular posts from this blog

Contact Me

Do You have any queries ?                   If you are having any query or wishing to get any type of help related Datawarehouse, OBIEE, OBIA, OAC then please e-email on below. I will reply to your email within 24 hrs. If I didn’t reply to you within 24 Hrs., Please be patience, I must be busy in some work. kashif7222@gmail.com

Top 130 SQL Interview Questions And Answers

1. Display the dept information from department table.   Select   *   from   dept; 2. Display the details of all employees   Select * from emp; 3. Display the name and job for all employees    Select ename ,job from emp; 4. Display name and salary for all employees.   Select ename   , sal   from emp;   5. Display employee number and total salary   for each employee. Select empno, sal+comm from emp; 6. Display employee name and annual salary for all employees.   Select empno,empname,12*sal+nvl(comm,0) annualsal from emp; 7. Display the names of all employees who are working in department number 10   Select ename from emp where deptno=10; 8. Display the names of all employees working as   clerks and drawing a salary more than 3000   Select ename from emp where job=’clerk’and sal>3000; 9. Display employee number and names for employees who earn commission   Select empno,ename from emp where comm is not null and comm>0. 10

Informatica sample project

Informatica sample project - 1 CareFirst – Blue Cross Blue Shield, Maryland (April 2009 – Current) Senior ETL Developer/Lead Model Office DWH Implementation (April 2009 – Current) CareFirst Blue Cross Blue Shield is one of the leading health care insurance provided in Atlantic region of United States covering Maryland, Delaware and Washington DC. Model Office project was built to create data warehouse for multiple subject areas including Members, Claims, and Revenue etc. The project was to provide data into EDM and to third party vendor (Verisk) to develop cubes based on data provided into EDM. I was responsible for analyzing source systems data, designing and developing ETL mappings. I was also responsible for coordinating testing with analysts and users. Responsibilities: ·          Interacted with Data Modelers and Business Analysts to understand the requirements and the impact of the ETL on the business. ·          Understood the requirement and develope