A simple solution is to add constraint in transformer stage on the incoming data to verify if it is satisfying the check constraint which is defined in the table.If it is satisfying the constraint,then only pass data to target OCI stage.
For example : Suppose there is a table "Emp".It contains a column "Salary".There is a check constraint which says the salary must be greater than 2000(i.e. salary>2000).in this case,in the transformer you will have to add a constraint salary>2000.In this way,OCI stage will get only those valid records which satisfy the check constraint.
Rejecting records which violate the check constraints :
=> From transformer take a link for "otherwise".This link will contain all the data which has violated the check constraint.
=>add a funnel to capture the invalid data from tranformer as well as the OCI reject link.
=>In this way the data can be captured as well.
How is that other post not helping? In short you need to understand why you are violating that check constraint (look it up in the database or talk to your DBA if you are unsure) and then ensure in your job that you pass only "good" values to that column. That could mean setting "bad" ones to a default value or not sending the record to the database at all... depends on your requirements.
Doesn't matter how many there are, check them all if you're unsure which one you're violating. And just specifically look at check constraints rather than constraints in general on the table. Most of the time they will be of the simple "is not null" variety but could also be enforcing a list of valid values (etc).
-craig
"You can never have too many knives" -- Logan Nine Fingers
gssr wrote:But, i want to know which is the cause for this ERROR!!
Any idea
You violated a check constraint, nothing more and nothing less. Talk to your DBA if that is still unclear for some reason. You need to know what check the constraint is enforcing before you'll have a clue what the actual "cause" is.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Then perhaps there's another constraint or you aren't really sending the "6" that you think you are. Any chance it's something silly like a "6 " coming in?
-craig
"You can never have too many knives" -- Logan Nine Fingers
I tried to get into another dataset in target, and i can able to view it in the target output!!
I will try to use a peek stage and update about the feedback