Topic
  • 7 replies
  • Latest Post - ‏2013-03-13T15:28:18Z by SystemAdmin
SystemAdmin
SystemAdmin
304 Posts

Pinned topic "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

‏2012-12-07T15:37:39Z |
I'm using IBM Infosphere Optim 8.1 with fixpack (I think..)

I'm getting "ODBC SQL State: HY104 Invalid precision value" error when inserting an extract file to my destination db.

I noticed that the error occurs when one of my table has a column with one of the types of "VarChar(Max)" , "VarBinary" , "nVarchar(Max)" , "XML"...

I think it's data size problem.. Please help and fix this bug!!!!

Note: When I alter columns from varchar(max) to varchar(8000) or from nvarchar(max) to nvarchar(4000) problem doesn't appear. But I'm really tired of this dumb solution...
Updated on 2013-03-13T15:28:18Z at 2013-03-13T15:28:18Z by SystemAdmin
  • KaoriN
    KaoriN
    5 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2012-12-11T01:49:37Z  
    Hi,

    You are using Microsoft SQL Server, correct?

    To use varchar(max) on SQL Server, you need to use "SQL Narive Client" driver. It is a requirement of SQL Server. If you don't have, you can download it from Microsoft web site.

    Thanks,
    Kaori
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2012-12-14T13:58:46Z  
    • KaoriN
    • ‏2012-12-11T01:49:37Z
    Hi,

    You are using Microsoft SQL Server, correct?

    To use varchar(max) on SQL Server, you need to use "SQL Narive Client" driver. It is a requirement of SQL Server. If you don't have, you can download it from Microsoft web site.

    Thanks,
    Kaori
    Yes it fixed max problem but I still have Date type problem. And probably XML error too... That's why I changed my connections into sql server from native client earlier.
    Any suggestions about how to fix Date type column errors??
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2013-01-09T13:25:03Z  
    Yes it fixed max problem but I still have Date type problem. And probably XML error too... That's why I changed my connections into sql server from native client earlier.
    Any suggestions about how to fix Date type column errors??
    Can you describe the other error you are having when using the Native Client?
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2013-03-01T08:23:03Z  
    I'm getting "odbc sql state: 22007 invalid date format" when I try to INSERT a table withe a Date type column...
    I'm using SQL Server Native Client 11.0 for ODBC...

    I really need help to fix this problem.
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2013-03-01T08:24:17Z  
    I'm getting "odbc sql state: 22007 invalid date format" when I try to INSERT a table withe a Date type column...
    I'm using SQL Server Native Client 11.0 for ODBC...

    I really need help to fix this problem.
    Datetime type doesn't cause an error but DATE is btw..
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2013-03-05T19:50:31Z  
    Hello,

    Is there any way to get an extract file with a row of data that exhibits the problem, along with the release of SQL Server that you are using?

    Thanks,
    Kevin
  • SystemAdmin
    SystemAdmin
    304 Posts

    Re: "ODBC SQL State: HY104 Invalid precision value" INSERT ERROR

    ‏2013-03-13T15:28:18Z  
    Hello,

    Is there any way to get an extract file with a row of data that exhibits the problem, along with the release of SQL Server that you are using?

    Thanks,
    Kevin
    Sure.
    I'm useing SQL Server 2008.
    My sample XF is in attachment.