Unable to insert a record into the table due to {0}
Posted: Mon Jul 18, 2011 12:41 pm
I have a job that loads an oracle Table in Upsert Mode ( Update Then Insert ) . Table has 2 column composite primary key , but no other constraints . The job aborts unexpectedly with an error message
The Message ID for this message is :
and is not to be seen in the parallel engine message reference PDF book. ( Probably is an error message specific to ora upsert operator )
When I previously encountered this issue & error message with loading another table , I found that it was related to tablespace being filled up and oracle was not able to insert a row ( either from DS or through Oracle SQL ) , and was able to get it fixed by asking for an increase in tablespace size .
However in this case , The SQL insert works fine from the oracle client and DBA confirmed that no tablespace issues exist, but somehow fails in datastage , since i have 75,000 odd rows in the source Dataset , I cannot try to insert them all one by one manually. So Im guessing it must be a bug with an unsupported Oracle error code , and thats the reason why job aborts without a reject happening to the reject link.
Has anyone encountered this so far and worked around it ?
Code: Select all
Unable to insert a record into the table due to {0}.
Code: Select all
IIS-DSEE-TOUP-00022,
When I previously encountered this issue & error message with loading another table , I found that it was related to tablespace being filled up and oracle was not able to insert a row ( either from DS or through Oracle SQL ) , and was able to get it fixed by asking for an increase in tablespace size .
However in this case , The SQL insert works fine from the oracle client and DBA confirmed that no tablespace issues exist, but somehow fails in datastage , since i have 75,000 odd rows in the source Dataset , I cannot try to insert them all one by one manually. So Im guessing it must be a bug with an unsupported Oracle error code , and thats the reason why job aborts without a reject happening to the reject link.
Has anyone encountered this so far and worked around it ?