Answer / benzdev

As per writer buffer here can hold multiple 7500 records
i.e 15000
even though we apply commit points in target the
integration service waits for writter buffer to fill
completely.
Answer is d) 15000,30000,40000

Answer / satish lomte

ANS (C)
a session is configured with target-based commit interval
of 10,000. The writer buffers fill every 7,500 rows. When
the Informatica Server reaches the commit interval of
10,000, it continues processing data until the writer
buffer is filled. The second buffer fills at 15,000 rows,
(i.e. 15000>=10000) and the Informatica Server issues a
commit to the target. If the session completes
successfully, the Informatica Server issues commits after
15,000, 22,500 (i.e. 22500>=20000), 30,000,(30000>=30000)
and 40,000 rows. (i.e. 37500>=40000 FALSE, so second buffer
is filled after 37500 and commits at 40,0000 )

Also
The writer buffer available depends on the dtm buffer block
size as configured in the session. The default is 64000
bytes. Say for example your target row is 2000 bytes long,
that would mean that each buffer block could hold 32 rows.
If you set your target commit interval at 100 then it would
actually commit at 128 rows. 3 buffer blocks would be 32 x
3 = 96 rows, which is less than the commit interval. 4
buffer blocks would be 32 x 4 = 128 rows.

Answer / vandan

Informatica server issues commit commands as follows as per
your question
15000, 22500, 30000, 37500, 40000

Answer / sajj

Target Based Commit

During a target-based commit session, the Informatica Server continues to fill the writer buffer after it reaches the commit interval. When the buffer block is filled, the Informatica Server issues a commit command. As a result, the amount of data committed at the commit point generally exceeds the commit interval.

In above example, a session is configured with target-based commit interval of 10,000. The writer buffers fill every 7,500 rows. When the Informatica Server reaches the commit interval of 10,000, it continues processing data until the writer buffer is filled. Example says multiple buffer so the second buffer fills at 15,000 rows, and the Informatica Server issues a commit to the target. If the
session completes successfully, the Informatica Server issues commits after 15,000, 22,500, 30,000, and 40,000 rows. So the Answer is "C"

Answer / baby

b

Answer / sree

the answer is C

Answer / nagesh

Ans (C)
A session is configured with target-based commit interval
of 10,000. The writer buffers fill every 7,500 rows. When
the Informatica Server reaches the commit interval
of 10,000, it continues processing data until the writer
buffer is filled. The second buffer fills at 15,000 rows,
and the Informatica Server issues a commit to the target.
If the
session completes successfully, the Informatica Server
issues commits after 15,000, 22,500, 30,000, and 40,000
rows.

Comment on significance of oracle 9i in informatica when compared to oracle 8 or 8i?

1 Answers  

can we use lookup t/r in flat files?what are the t/r's can be used in flat files when compared to relational DB?

2 Answers   IBM,

How can we update a record in the target table without using update strategy?

0 Answers  

What is the difference between informatica 7.0 and 8.0?

0 Answers  

what is the use of Java Transformation in Informatica 8.x?

2 Answers   TCS,

A Flat file located in unix source folder. data transfer every day 8 am. can ask 5 question for above scenario validation. recently i have faced this question.

1 Answers   TATA,

Can anyone tell me the new features in Informatica 9 Version?

2 Answers   Syntel,

Which one is better performance wise connected/un-connected lkp?why?

2 Answers   HCL, TCS,

version controlling in informatica?

3 Answers  

What is partioning?how many types of partinings are there

2 Answers   HCL,

What is incremental aggregation?

0 Answers  

Can you use flat files in Mapplets.

0 Answers