Lets say  i have more then have record in source table  and i have 3 destination table A,B,C. I have to insert first 1 to 10 record in A then 11 to 20 in B and 21 to 30 in C.
Then again from 31 to 40 in A, 41 to 50 in B and 51 to 60 in C……So on upto last record.

Solution:

Generate sequence number using informatica, add filter or router transformations and define the conditions accordingly…

Define group condition as follows under router groups….

Group1 = mod(seq_number,30) >= 1 and mod(seq_number,30) <= 10
Group2 = mod(seq_number,30) >= 11 and mod(seq_number,30) <= 20
Group3 = (mod(seq_number,30) >=21 and mod(seq_number,30) <= 29 ) or mod(seq_number,30) = 0

Connect Group1 to A, Group2 to B and Group3 to C

When using query override, error msg  is ”Invalid lookup override ”  and Below is the Query:

 ”select a.accid, a.trans_date, a.trans_amt from acct_trans a, (select accid, max(trans_date) trans_date from acct_trans group by accid) b where a.accid=b.accid and a.trans_date=b.trans_date”

Sol:

This error may occurs when using sub-queries in a lookup SQL override and the LookupOverrideParsingSetting custom property is not set.

From the Administration Tab, go to the Integration Service > Process Tab
Add a custom property lookupOverrideParsingSetting and set the value =1 .
Disable and re-enable the Integration service and re-run the session.

Use the following formula to determine the size of incoming data:
# input rows ([Sum(column size)] + 16)

A(in)
B(in)
A_Pre(V) = A
B_Pre(V) = B
Comp(V) = IIF( A= A_Pre and B= B_Pre, ‘Y’,'N’)
Basically you need to store the previous values in a variable and compare with incoming data.

2. We don’t have scheduler in Ab Initio like Informatica you need to schedule through script or u need to run manually.

3. Ab Initio supports different types of text files means you can read same file with different structures that is not possible in Informatica, and also Ab Initio is more user friendly than Informatica so there is a lot of differences in Informatica and Ab initio.

4. Both tools are fundamentally different. Which one to use depends on the work at hand and existing infrastructure and resources available.

5. Informatica is an engine based ETL tool, the power this tool is in it’s transformation engine and the code that it generates after development cannot be seen or modified.

6. Ab Initio is a code based ETL tool, it generates ksh or bat etc. code, which can be modified to achieve the goals, if any that cannot be taken care through the ETL tool itself.

7. Initial ramp up time with Ab Initio is quick compare to Informatica, when it comes to standardization and tuning probably both fall into same bucket.

8. AbInitio doesn’t need a dedicated administrator, UNIX or NT Admin will suffice, where as other ETL tools do have administrative work.

9. With recent releases of Informatica, it has a built in Change Data Capture capabilities (extract only the chnaged data through the DB logs), where as Ab Initio has to rely on DB to provide the CDC capabilities, as of now it doesn’t have a way to sniff the DB logs.

10. Another interesting difference noticed is, with Ab Initio you can read data with multiple delimiter in a given record, where as Informatica force you to have all the fields be delimited by one standard delimiter.

11. If we go into component level, each tool has it’s own way of implementing these transformation components.

12. When making a choice there are lot of factors which drive the decision like Existing infrastructure, resources, Project time line. Metadata management, complexity of transforms, data volumes, integration with third party tools, Tool Support etc. not just Budget.

* Error Handling – In Ab Initio you can attach error and reject files to each transformation and capture and analyze the message and data separately. Informatica has one huge log! Very inefficient when working on a large process, with numerous points of failure.

* Robust transformation language – Informatica is very basic as far as transformations go. While I will not go into a function by function comparison, it seems that Ab Initio was much more robust.

* User defined functions – I never developed any in Ab Initio, but I know that you can. Informatica requires that you code custom transformations in C++ (or VB if you are on a windows platform). Ab Initio also allows for custom components, but I have never had to develop one.

* Instant feedback – On execution, Ab Initio tells you how many records have been processed/rejected/etc. and detailed performance metrics for each component. Informatica has a debug mode, but it is slow and difficult to adapt to.

* Consolidated Interface – Ab Initio

Node is the logical representation of a machine in a domain. The machine in which the PowerCenter is installed acts as a Domain and also as a primary node. We can add other machines as nodes in the domain and configure the nodes to run application services such as the Integration Service or Repository Service. All service requests from other nodes in the domain go through the primary node also called as ‘master gateway’.

Domain Configuration Some of the configurations for a domain involves assigning host name, port numbers to the nodes, setting up Resilience Timeout values, providing connection information of metadata Database, SMTP details etc. All the Configuration information for a domain is stored in a set of relational database tables within the repository. Some of the global properties that are applicable for Application Services like ‘Maximum Restart Attempts’, ‘Dispatch Mode’ as ‘Round Robin’/’Metric Based’/’Adaptive’ etc are configured under Domain Configuration

A domain is the primary unit for management and administration of services in PowerCenter. Node, Service Manager and Application Services are components of a domain.