We are using Update Strategy Transformation in mapping how can we know whether insert or update or reject or delete option has been selected during running of sessions in Informatica.
RE: We are using Update Strategy Transformation in map...
In Designer while creating Update Strategy Transformation uncheck "forward to next transformation". If any rejected rows are there automatically it will be updated to the session log file.
Update or insert files are known by checking the target file or table only.
RE: We are using Update Strategy Transformation in map...
hi,
if u r using an update strategy in ur mapping, there is no such oprtion to check or uncheck for these operations.when u have to perform any of the DML or database operations u have to code it in the UPD manually. so there is no chance for checking this. if u have used DD_UPDATE or DD_REJECT, u can only know it by querying the target table.if its rejected then through session log.
RE: We are using Update Strategy Transformation in map...
Use a lookup transformation this will take a snapshot of the table before sending to update strategy. You can use active lookup, it will keep track of the data coming in and will help to identify new/old rows.
RE: We are using Update Strategy Transformation in mapping how can we know whether insert or update or reject or delete option has been selected during running of sessions in Informatica.
In general DWH scenario, we create TABLE_REJECT or FILE_REJECT to keep a check of the rejected records. For all the updates happening we keep timestamp or some other flag in the database.
Before the update strategy itself if you know under what circumstances you need to perform insert, update, reject or delete put an indicator and check the indicator value in the update strategy to write to the target.
OR
use a router grouping on the indicator before the update strategy and create different groups for update, reject, delete or insert and write into the file. This is just for testing puproses.
