Page 1 of 1

DS Bulk load

Posted: Thu Nov 22, 2012 7:51 am
by saj
Hi All ,
I am getting the below error when trying to run the DS job which has oracle bulk load option enabled

The connector was configured to write data in bulk load mode and the reject condition for checking constraints was selected for the reject link. For this operation to work it is necessary to also provide the exceptions table name. (CC_OraConnection::checkEnvironment, file CC_OraConnection.cpp, line 4,921)The connector was configured to write data in bulk load mode and the reject condition for checking constraints was selected for the reject link. For this operation to work it is necessary to also provide the exceptions table name. (CC_OraConnection::checkEnvironment, file CC_OraConnection.cpp, line 4,921)

After giving the reject link also the same error is coming up. Please help

Posted: Thu Nov 22, 2012 9:29 am
by chulett
Your issue and solution are detailed in the message you posted. "Bulk load" in Oracle means sqlldr and that utility has the option to capture rejects to an exceptions table rather than failing. In order for it to do that you must tell it the name of the exceptions table to write to. I don't have access right now but I would imagine that this would not be handled by a reject link but rather by a property you set within the stage.

For (perhaps more than you'd ever want) detail on the subject, Tom Kyte has a couple of blog posts on the subject:

http://tkyte.blogspot.com/2005/07/how-cool-is-this.html

http://tkyte.blogspot.com/2005/07/how-c ... rt-ii.html

Posted: Thu Nov 22, 2012 10:18 am
by saj
We have mentioned the exception table name also ..

Posted: Thu Nov 22, 2012 11:27 am
by chulett
And what happened - you got the exact same error? You mentioned it where exactly?

Posted: Thu Nov 22, 2012 1:37 pm
by saj
yes , we got the same error which has been posted

Posted: Thu Nov 22, 2012 5:39 pm
by chulett
One of two questions answered...

Note that I honestly don't know the answer here, just trying to get past the obvious issues and hoping that someone who's actually done this shows up and lends a hand. :wink:

Posted: Fri Jul 10, 2015 11:48 am
by laloe84
This problem arises because you previously used a Oracle stage with different constraints. Try to put again a Oracle target stage and review what are the constraints selected then cleared all the selected constraints ..save and compile the Job again. This worked for me.

Posted: Fri Jul 10, 2015 12:06 pm
by qt_ky
What was the full text of the error message(s) - warnings and aborts? Reviewing that would be a good place to start.

Posted: Fri Jul 10, 2015 1:42 pm
by chulett
Glad what you did worked for you but wondering how you have any idea that the original poster 'previously used a Oracle stage'... 3 years ago. :wink: