11. What is a lookup transformation?
Used to look up data in a relational table, views, or synonym, The informatica server queries the lookup table based on the lookup ports in the transformation. It compares lookup transformation port values to lookup table column values based on the lookup condition. The result is passed to other transformations and the target.
12.What is Ranker transformation?
Filters the required number of records from the top or from the bottom.
13.What is Slowly changing dimensions?
Slowly changing dimensions are dimension tables that have slowly increasing data as well as updates to existing data.
14.What is the difference between joiner transformation and source qualifier transformation?
You can join heterogeneous data sources in joiner transformation which we cannot do in source qualifier transformation.
15.What is meant by lookup caches?
The Informatica server builds a cache in memory when it processes the first row of a data in a cached look up 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.
16.If a sequence generator (with increment of 1) is connected to (say) 3 targets and each target uses the NEXTVAL port, what value will each target get?
Multiple of 3
17)What is the difference between normal and bulk loading?Which one is recommended?
The main difference between normal and bulk load:
1)In normal load Informatica repository service create logs.
2)In bulk load log is not being created.
3)That is the reason bulk load loads the data fast and if anything goes wrong the data can not be recovered.
4)But in normal load since the log is created the lost data can be recovered.
5)By configuring session to Bulk loading we cannot do 'session recovery' when it get failed.
6)In normal loading we can easily do session recovery.
object ,code page setting for the connection string need to
be selected as required.
19)In incremental loading using Mapping variable if session failed with any of reason in the middle of process. is the Mapping variable remains constant or change?
Mapping Variable will store its value in the repository once the Session run successfully.If the session fails the Mapping Variable will not be updated with the new value.
20)How informatica recognizes mapping?(CTS)
1)Organized by Integration service .
2)Power center talks to Integration Service and Integration service talk to session.
3)session has mapping Structure these are flow of Execution through sessions.
Used to look up data in a relational table, views, or synonym, The informatica server queries the lookup table based on the lookup ports in the transformation. It compares lookup transformation port values to lookup table column values based on the lookup condition. The result is passed to other transformations and the target.
12.What is Ranker transformation?
Filters the required number of records from the top or from the bottom.
13.What is Slowly changing dimensions?
Slowly changing dimensions are dimension tables that have slowly increasing data as well as updates to existing data.
14.What is the difference between joiner transformation and source qualifier transformation?
You can join heterogeneous data sources in joiner transformation which we cannot do in source qualifier transformation.
15.What is meant by lookup caches?
The Informatica server builds a cache in memory when it processes the first row of a data in a cached look up 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.
16.If a sequence generator (with increment of 1) is connected to (say) 3 targets and each target uses the NEXTVAL port, what value will each target get?
Multiple of 3
17)What is the difference between normal and bulk loading?Which one is recommended?
The main difference between normal and bulk load:
1)In normal load Informatica repository service create logs.
2)In bulk load log is not being created.
3)That is the reason bulk load loads the data fast and if anything goes wrong the data can not be recovered.
4)But in normal load since the log is created the lost data can be recovered.
5)By configuring session to Bulk loading we cannot do 'session recovery' when it get failed.
6)In normal loading we can easily do session recovery.
Note:
1)In normal load Informatica creates logs record by record in database level and in bulk mode it will not create detail log. By avoiding that detail writing in bulk mode improve performance.
2)If there are indexes and constraints in the table, you cannot use Bulk Load
You can drop/disable those indexes/constraints (pre session ) , then load the data (use Bulk Load) , and then create/enable the indexes/constraints (post session )
3)Bulk mode improve performance.
18)where to select code page option?(TCS)
In administration console ,while defining the connection 18)where to select code page option?(TCS)
object ,code page setting for the connection string need to
be selected as required.
19)In incremental loading using Mapping variable if session failed with any of reason in the middle of process. is the Mapping variable remains constant or change?
Mapping Variable will store its value in the repository once the Session run successfully.If the session fails the Mapping Variable will not be updated with the new value.
20)How informatica recognizes mapping?(CTS)
1)Organized by Integration service .
2)Power center talks to Integration Service and Integration service talk to session.
3)session has mapping Structure these are flow of Execution through sessions.
2 3
Thanks for reading posts.
ReplyDelete