top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Obtaining number of rows written to multiple targets in Informatica Power Center

0 votes
607 views

I have a requirement where I need to obtain the number of rows written to multiple targets in my mapping. There are 3 targets in my mapping (T1, T2 and T3). I need the number of rows written to each target separately. These values need to be used in subsequent sessions. I understand that there is a method where I can use separate counters and write them to a flat file and perform a lookup on this file in subsequent mappings. However, I am looking for a direct and better approach to this problem.

posted May 15, 2014 by Rohini Agarwal

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

1 Answer

0 votes

You can use the $PMTargetName@numAffectedRows built-in variables. In your case it would be something like

$PMT1@numAffectedRows
$PMT2@numAffectedRows
$PMT3@numAffectedRows
answer May 19, 2014 by Shweta Singh
Similar Questions
+1 vote

How to Import data from db2 table using informatica power Center without powerexchange.

+1 vote

SQL SERVER 2014 SSIS has been released,we have already got lot of facilities in SQL SERVER 2012 SSIS.Can anybody compare SSIS 2014/SSIS2012 with Informatica Power center ? What are the additional fetures are there in the Informatica new version than SSIS 2012/2014? Or are there functions in SSIS 2014/20122 ,which are not available in Informatica.

0 votes

How to calculate number of rows in flat files in informatica.
As we are doing in Teradata as SEL COUNT (*) FROM ABC.ACCT.

+1 vote

I'm not exactly sure if it will cause an issue or not. But in our environment whenever selecting from large tables we need to include WITH(nolock) otherwise we get deadlocks between select statements and Informatica real time replication trying to populate those tables. Currently we are looking to use SQL jobs to purge old records from tables. Most tables will have less than 1000 rows deleted once a week. During initial purge process there will be several tables that will have millions of records deleted.

Not sure if it would be better to pause real time replication for duration of the purge or just to try to resolve conflicts once those arise.

I don't have a good way to test this in Dev environment because don't have same volume of people hitting server with request, real time updates and everything else that makes up normal load in production. In production this will be running once a week during slow hours that should minimize total load but still don't want to crash Informatica every time this is running.

Note: this question is NOT about how to write delete statements in SQL or breaking delete in small chunks but rather how to avoid conflicts with real time replication with Informatica product.

Database - SQL Server 2012
Replication - Informatica 9.0.1

...