Error logging using Oracle OCI
Posted: Tue Nov 11, 2003 3:41 am
Hi
I've been using the Oracle OCI stage in DataStage 5.2.2. The stage writes out a number of rows to various tables in the database, and rolls back all rows should an error be encountered when writing any one row (eg. value too long for column).
In the transformer which feeds the OCI stage, I also have a reject row with no constraints on it. In the case that rows fail constraints within the transformer, rows are passed to this reject file. However, in the case that a row fails at the database, no row is written to the reject link.
I understand from reading past posts that this functionality may not be implemented in some version of DataStage. Assuming this is the case for 5.2.2, can anyone offer advice on a way in which I could remedy the problem? I don't want to use an ODBC stage, as Oracle doesn't support any ODBC clients on UNIX. Also, there are many database constraints and so validating data before it reaches OCI would be very expensive.
Thanks for your help
David
I've been using the Oracle OCI stage in DataStage 5.2.2. The stage writes out a number of rows to various tables in the database, and rolls back all rows should an error be encountered when writing any one row (eg. value too long for column).
In the transformer which feeds the OCI stage, I also have a reject row with no constraints on it. In the case that rows fail constraints within the transformer, rows are passed to this reject file. However, in the case that a row fails at the database, no row is written to the reject link.
I understand from reading past posts that this functionality may not be implemented in some version of DataStage. Assuming this is the case for 5.2.2, can anyone offer advice on a way in which I could remedy the problem? I don't want to use an ODBC stage, as Oracle doesn't support any ODBC clients on UNIX. Also, there are many database constraints and so validating data before it reaches OCI would be very expensive.
Thanks for your help
David