Oracle error messages relating to the rejected records
Moderators: chulett, rschirm, roy
Oracle error messages relating to the rejected records
Hi,
I have to retrieve Oracle error messages relating to the rejected records in parallel job.
I know only this way:
in OCI Stage I can set Upsert as "Write mode" and selecting "Output rejected records" I can retrieve sqlcode associate to rejected rows.
If I use Load as write mode, How can I do the same thing?
Are there any other ways to retrieve Oracle error in parallel job?
thanks
George
I have to retrieve Oracle error messages relating to the rejected records in parallel job.
I know only this way:
in OCI Stage I can set Upsert as "Write mode" and selecting "Output rejected records" I can retrieve sqlcode associate to rejected rows.
If I use Load as write mode, How can I do the same thing?
Are there any other ways to retrieve Oracle error in parallel job?
thanks
George
The Load method is executed outside of DataStage and that is why the single rejected rows and messages aren't visible the way they are with 'upsert'. I think that the error log files should be visible after the job run is finished and has errors, and that file can be read and interpreted.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
thanks a lot for the response.ArndW wrote:The Load method is executed outside of DataStage and that is why the single rejected rows and messages aren't visible the way they are with 'upsert'. I think that the error log files should be visible after the job run is finished and has errors, and that file can be read and interpreted.
I focused on "LOAD" mode to be able to performe a truncate before insert besides retrieve Oracle error.
In "UPSERT" mode it's not possible performe a truncate before insert, so I have to find another way to truncate table before insert.
right?
thanks again
thanks a lot for the response.ArndW wrote:The Load method is executed outside of DataStage and that is why the single rejected rows and messages aren't visible the way they are with 'upsert'. I think that the error log files should be visible after the job run is finished and has errors, and that file can be read and interpreted.
I focused on "LOAD" mode to be able to performe a truncate before insert besides retrieve Oracle error.
In "UPSERT" mode it's not possible performe a truncate before insert, so I have to find another way to truncate table before insert.
right?
thanks again
Why not do your truncate as part of the before-sql?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
That's a pretty compelling argument, in my opinion!
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
I didn't work with OCI stage, but if there's a 'user-defined upsert' it can fix the problem by putting the 'truncate' statement instead if the insert statement and the 'insert' statement instead of the update one at the stage.dstgx08 wrote: Because there isn't before-sql part in stage OCI of parallel job
But you won't get the sqlloader advantages here with this suggestion.
Hope this could help,
Regards.