ODBC function "SQLBindParameter" reported: SQLSTA

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nishantrk
Premium Member
Premium Member
Posts: 23
Joined: Fri May 27, 2011 11:43 am

ODBC function "SQLBindParameter" reported: SQLSTA

Post by nishantrk »

Hi

I am trying to update SQLServer DB reading data from a dataset.
while updating the DB i am getting the below error.

ODBC_STGY_STR,0: ODBC function "SQLBindParameter" reported: SQLSTATE = HY104: Native Error Code = 0: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Legacy Driver]Invalid precision value (CC_OdbcDBStatement::dbsBindInputs, file CC_OdbcDBStatement.cpp, line 404)

Dataset column definition

(
LOC_I:int16 {quote=none};
GO_D:nullable timestamp {null_field=''};
SITE_TYPE_C:nullable string[1] {null_field=''};
MDSE_LVL_Q:nullable int16 {quote=none, null_field=''};
BLDG_LVL_Q:nullable int16 {quote=none, null_field=''};
)

Table definition
LOC_I,smallint,no,2,5 ,0 ,no,(n/a),(n/a),NULL
GO_D,datetime,no,8, , ,yes,(n/a),(n/a),NULL
SITE_TYPE_C,char,no,1, , ,yes,no,yes,SQL_Latin1_General_CP1_CI_AS
MDSE_LVL_Q,smallint,no,2,5 ,0 ,yes,(n/a),(n/a),NULL
BLDG_LVL_Q,smallint,no,2,5 ,0 ,yes,(n/a),(n/a),NULL


The dataset definitions have been directly imported throught table definition import utitlity .Also this job is working fine in the DEV enviorment but failing in TEST enviroment. We think it might be due to some setting either in Dataste or at dATABASE IN sql server..Can you please help us with this ..thanks
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The only data types that support precision in your example are the datetime/timestamp and the string/char. Check the precision settings for these in the database tables to which each environment (dev and the other) connects.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply