1403 Oracle Error -Upsert
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
1403 Oracle Error -Upsert
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,
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,
Thanks,
Vinay
Vinay
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.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Premium Member
- Posts: 353
- Joined: Wed Apr 06, 2005 8:45 am
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.
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.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 8
- Joined: Tue Jan 30, 2007 11:22 pm
- Location: Chennai
- Contact:
Re: 1403 Oracle Error -Upsert
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.
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.
-
- Participant
- Posts: 8
- Joined: Tue Jan 30, 2007 11:22 pm
- Location: Chennai
- Contact:
Re: 1403 Oracle Error -Upsert
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
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
-
- Participant
- Posts: 51
- Joined: Mon Feb 05, 2007 1:53 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