source and target as the same table (using oracle stage)

csrazdan · Post by **csrazdan** » Wed Apr 25, 2007 4:19 pm

Well -1400 range of sqlcode is related to no data found.

What is the Upsert mode for your job, is it Update only.
Can you change it Insert and Update. See if records get inserted.

If yes.. do you have a PK on the table and still it gets inserted? If yes that would mean your keys are not matching.

Hope it helps.....

kirankota79 · Post by **kirankota79** » Wed Apr 25, 2007 4:21 pm

the key is an integer...but i have changed it to varchar. Will it not work like that?

DSguru2B · Post by **DSguru2B** » Wed Apr 25, 2007 4:23 pm

kirankota79 wrote:3. Employee: When checking operator: When binding output interface field "USER_ID" to field "USER_ID": Implicit conversion; from source type "string[max=20]" to result type "string[max=19]": Possible truncation of variable length string

Thats your culprit right there.

kirankota79 · Post by **kirankota79** » Wed Apr 25, 2007 4:36 pm

Is it Ok if only the key matches........or it should be all the columns to be updated should match?

DSguru2B · Post by **DSguru2B** » Wed Apr 25, 2007 4:40 pm

Only the keys.

kirankota79 · Post by **kirankota79** » Wed Apr 25, 2007 4:45 pm

the key is 'decimal' filed when i see in the table definitions which i imported from database. But when i load the columns in the oracle stage it is becoming as integer. Why is it happpeing? will it cause problems for update?

DSguru2B · Post by **DSguru2B** » Wed Apr 25, 2007 4:55 pm

It might be. Check the length and precision and specify that manually for the key field within datastage. See if the behaviour of your job changes.

us1aslam1us · Post by **us1aslam1us** » Thu Apr 26, 2007 12:41 pm

Also check for the null values in your key field.