Hi All,
I was new to Datastage. Initially we had done our server jobs in V7.5, but due to some compatibility probs., we shifted to v7.1. The jobs which ran well in 7.5V are showing some errors while running in this 7.1V.
One of the error i am facing here is
K_FDM84_88_JOB..k_exp_JOB_LKP: [IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008
and the other one is
K_FDM84_88_CUSTOMER_D00..k_exp_CUST_DMT_DIM: [IBM][CLI Driver][DB2/6000] SQL0407N Assignment of a NULL value to a NOT NULL column "TBSPACEID=126, TABLEID=5138, COLNO=2" is not allowed. SQLSTATE=23502
Can anyone help me out reg. this issue.
Thanks in Advance,
Error:Datetime field overflow
Moderators: chulett, rschirm, roy
Error:Datetime field overflow
Thanks & Regards,
Kris
Kris
Kris,
both errors are caused by data and should be version independant. The first error should be tracked using a reject link to catch the bad data in the datetime field. The second error is clear, your 2nd column in k_exp_CUST_DMT_DIM is declared as "not nullable" in the database yet you are trying to send it a null value.
both errors are caused by data and should be version independant. The first error should be tracked using a reject link to catch the bad data in the datetime field. The second error is clear, your 2nd column in k_exp_CUST_DMT_DIM is declared as "not nullable" in the database yet you are trying to send it a null value.
</a>Hi ArndW,
Thanks for u'r reply.As u said the first error should be tracked using a reject link.But in the error log, row link was rejected until 10th row & so on. so,how to clear this.Any idea how to catch the bad data & clear this.
Thanks once again
Thanks for u'r reply.As u said the first error should be tracked using a reject link.But in the error log, row link was rejected until 10th row & so on. so,how to clear this.Any idea how to catch the bad data & clear this.
Thanks once again
ArndW wrote:Kris,
both errors are caused by data and should be version independant. The first error should be tracked using a reject link to catch the bad data in the datetime field. The second error is clear, your 2nd column in k_exp_CUST_DMT_DIM is declared as "not nullable" in the database yet you are trying to send it a null value.
Thanks & Regards,
Kris
Kris
kris9999,
in the transform prior to the stage make another output link to a sequential reject file, then use the drop-down list in the constraints to specify that rejected rows should go down there and add the columns that you are interested in to that output stream. this is standard error handling in DS that is documented in the user's guides.
in the transform prior to the stage make another output link to a sequential reject file, then use the drop-down list in the constraints to specify that rejected rows should go down there and add the columns that you are interested in to that output stream. this is standard error handling in DS that is documented in the user's guides.