1403 Oracle Error -Upsert

vinaymanchinila · Post by **vinaymanchinila** » Mon Mar 12, 2007 1:58 pm

Hi,

When I run a job which reads from SQL and loads into Oracle table using Oracle Ent Stage, I get the "sqlcode:1403 " error. When I take the Update stmt from the stage and execute it in Toad it works fine !

I did try to change the 'Update Else Insert' option to 'Insert else Update' but its the same error, did any one have this issue with Oracle Ent stage?

There are no date columns in my target oracle table,all the columns are char or varchar or decimal.
Thanks,

DSguru2B · Post by **DSguru2B** » Mon Mar 12, 2007 2:09 pm

Sql Code 1403 means that the update record was not found according to the listprovided by Vincent. Is your key a char column ? What happens when you change that to varchar. There might be an issue of spaces with char field.

vinaymanchinila · Post by **vinaymanchinila** » Mon Mar 12, 2007 2:36 pm

I had Decimal and Char as key columns and I changed it to Decimal and VarChar, still the same 1403 error and all the source rows are rejected.

Curious , if it does not find the key coulmn shouldnt the job insert the row ?

Thanks

DSguru2B · Post by **DSguru2B** » Mon Mar 12, 2007 2:43 pm

The stage tries to insert, if the insert fails with error code (-1), it will then try to update. The issue here is. It fails on update as well. What happens if you do only update?

Try to capture the record thats causing this error. See whats different. Does that value exist ?
For debugging purposes, replace the enterprise stage with ORA OCI stage. See if the problem persists.

kumar_s · Post by **kumar_s** » Mon Mar 12, 2007 10:15 pm

Were you able to locate the record which gives out this error? Any thing special about that record?

Sathish321 · Post by **Sathish321** » Tue Mar 13, 2007 3:55 am

Hey Vinay,

I had the same issue in my project also. IBM people suggested me to use DRS stage in place of Oracle entp stage. Now its working fine, U can also try with DRS stage.

Sathish321 · Post by **Sathish321** » Tue Mar 13, 2007 3:56 am

Hey Vinay,

I had the same issue in my project also. IBM people suggested me to use DRS stage in place of Oracle entp stage. Now its working fine, U can also try with DRS stage.

Thanks,
Sathish

kumar_s · Post by **kumar_s** » Tue Mar 13, 2007 4:46 am

Hi Sathish,
Do you have any eCase number for this?

DSguru2B · Post by **DSguru2B** » Tue Mar 13, 2007 7:01 am

Yea but demand for a patch. Why use DRS stage when oracle enterprise stage is there for the very same reason.

travissolt · Post by **travissolt** » Mon Jun 11, 2007 3:48 pm

We have been having the same issue and I am just curious if the fixes really worked and if any issues have since deveolped. Basically the upsert logic does not seem to work correctly all the time for some of our jobs. It appears to give erroneous 1403 errors on an upsert vs insert and -1 errors on an insert vs update. The errored out data does not break any of the key contsaints so I am not sure why it does not work (if we write SQL inserts and updates we can load the data manually). You refer to a DRS stage below as opposed to an oracle entp stage. What is the DRS stage as I am not familair? Thanks

DSXchange

1403 Oracle Error -Upsert

1403 Oracle Error -Upsert

Re: 1403 Oracle Error -Upsert

Re: 1403 Oracle Error -Upsert