DB2API Stage giving diffrent result

[swades]

Hello,

I have a job in which I am doing update and insert to a target table. I want to have update 1st and then insert which is I am doing thru 2 dufferent link to 2 DB2UDB API Stage from a transformer(link order of executing is setup)


Tranformer--------------->DB2UDB Update
--------------->DB2UDB Insert


Job runs without any warning. it is "loading ( updating)" as per expectation.
when I rerun job it is not doing "loading ( updating)" as per expectation. Again this behavior is not Consistence. Anytime there is no Warning.

In Both Stages Transaction Isolation is : Cursor Stability
Array size: 50 and Transation Size: 50

Following Massages I am Getting which I cant Understand it means:

DB2UDB_insert,0: Logging delayed metadata.
DB2UDB_target,0: Logging delayed metadata.

Thanks

[chulett]

when I rerun job it is not doing "loading ( updating)" as per expectation.

You've said neither what it actually does when you rerun the job, nor what your expectation is. Need more details on the nature of your problem, like how you differentiate inserts from updates for one.

Can't help you with the 'logging delayed metadata' message. Searched the forum and, while it has been mentioned before, there's not answer out there as to what it means.

[swades]

Thank for reply

My Expectation:
I have to have update and insert both after tranformer.
Update : update existing rows based on key column. set values which I got from Tranformer ( in Update link).

Insert : Insert record. values which I got in Insert link


Rerun :

After 1st run I got result X but when I delete X and again run I am not getting result X ( X is not ant value. It is just Example)

Thnaks

[ray.wurlod]

How did you effect the deletes? Did you COMMIT this transaction?

[swades]

Thanks Ray,

I am doing delete thru DB2 control center ( i.e. Command line ) I am also doing commit after delete.


Thanks