[IBM][CLI Driver] CLI0143E Invalid precision value

esivaprasad · Post by **esivaprasad** » Fri May 22, 2015 4:51 am

Hi All,
Job designing like this :

DB2 stage - > XFM stage -> DB2 stage

source query used in db2 stage:
'select 'S' as no ,'Sucess' as def_va ,REQUEST_ID,REQUEST_SEQ_NO from MDCRDBA.textract_recurr_tbl WHERE REQUEST_ID=#REQUEST_ID# AND REQUEST_SEQ_NO=#REQUEST_SEQ_NO# and REQUEST_STATUS_CD <> 'F' ; '

Query in taget( db2 ) stage
'UPDATE MDCRDBA.textract_recurr_tbl SET REQUEST_STATUS_CD=?,ERROR_MSG_TX=?,REQUEST_END_TS=? WHERE REQUEST_ID=? AND REQUEST_SEQ_NO=?;'

we are getting following error frequently .
FATAL Error :
'MDCR_Success_Update..Success_Update: SQLExecDirect: DB2 error info message '[IBM][CLI Driver] CLI0143E Invalid precision value. SQLSTATE=HY104'.
DSTAGE-DB2CLI-0009`:`SQLBindParameter: Failed to bind a parameter. '

WARNING:
'Attempting to Cleanup after ABORT was raised in stage MDCR_Success_Update..Success_Update'.

please help me how to resolve this error.

Thanks & Regards,

chulett · Post by **chulett** » Fri May 22, 2015 7:18 am

Really really truly a Server job?

esivaprasad · Post by **esivaprasad** » Fri May 22, 2015 7:26 am

Yes, its really a server job.

chulett · Post by **chulett** » Fri May 22, 2015 9:12 am

Then off we go to the Server forum!

chulett · Post by **chulett** » Fri May 22, 2015 9:30 am

A couple of things. If you Reset the aborted job, does an message appear in the log labelled "From previous run..."? If so, please post the contents. Also, are any of your values NULL? Googling around finds some articles on NULL values causing that error but other than that there's not much information out there. Worst case, you may need to involve your official support provider.

ray.wurlod · Post by **ray.wurlod** » Fri May 22, 2015 3:47 pm

For every VarChar, Char, Decimal, Float and Double column, check to see that there is a non-zero entry in the Precision cell in the Columns grid.

esivaprasad · Post by **esivaprasad** » Mon May 25, 2015 7:58 am

Hi Craig,

when in next run this failed job reset, in log there is no log like "From previous run...".

Thanks

chulett · Post by **chulett** » Tue May 26, 2015 6:36 am

That's too bad as it means we don't have that diagnostic information. If the other information that Ray and I posted don't help, involve your official support provider.