About “The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream”

[rabbit-mom]

when I using TVP to bulkinsert to a table,this exception occured,and I do not konw to solve it?
"com.microsoft.sqlserver.jdbc.SQLServerException: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter 0 (""), row 0, column 0: Data type 0x6C has an invalid precision or scale."
What reason is this?How to solve it?

[gordthompson]

Can you provide a Minimal, Complete, and Verifiable example?

[rabbit-mom]

Hi,thanks for your response,next is my example:

SQLServerDataTable sourceDataTable=new SQLServerDataTable();
sourceDataTable.addColumnMetadata("actuAmount",Types.DECIMAL);
sourceDataTable.addColumnMetadata("amount",Types.DECIMAL);
sourceDataTable.addRow(new BigDecimal(0.0000).setScale(4,BigDecimal.ROUND_HALF_UP),new BigDecimal(1098.0000).setScale(4,BigDecimal.ROUND_HALF_UP));
SQLServerCallableStatement pStmt = (SQLServerCallableStatement) DataSource.getConnection("DBName").prepareCall("exec spT_TbaleA_i ?");
pStmt.setStructured(1,"TVP_TbaleA",sourceDataTable);
pStmt.execute();

I found the problem is at "new BigDecimal(0.0000).setScale(4,BigDecimal.ROUND_HALF_UP)",the precision is four and the value is 0.0000,it will throws that exception.Eagerly looking forward to your reply.

[gordthompson]

I can reproduce the issue using the above Java code along with

CREATE TYPE [dbo].[TVP_TbaleA] AS TABLE(
    [c1] [decimal](18, 4) NOT NULL,
    [c2] [decimal](18, 4) NULL,
    PRIMARY KEY CLUSTERED 
(
    [c1] ASC
)WITH (IGNORE_DUP_KEY = OFF)
)

and

CREATE PROCEDURE [dbo].[spT_TbaleA_i] 
    @tbl dbo.TVP_TbaleA READONLY
AS
BEGIN
    SET NOCOUNT ON;
    SELECT c1 + c2 AS cSum FROM @tbl;
END

As decribed, it is the

new BigDecimal(0.0000).setScale(4,BigDecimal.ROUND_HALF_UP)

argument to SQLServerDataTable#addRow that is causing the exception. Both

new BigDecimal(1.0000).setScale(4,BigDecimal.ROUND_HALF_UP)

and

new BigDecimal(0.0000)

work fine.

[xiangyushawn]

@rabbit-mom which version of the driver do you use? could you please try with a newer version? This bug seems to be fixed since 6.1.2

[gordthompson]

My repro above was with the latest production release: 6.0.8112.100

Re-tested with version 6.1.4 and the error did not occur, so this appears to be the same issue as #92.

[xiangyushawn]

@gordthompson thank you for getting back to us and confirming with us. I am going to close this issue then. @rabbit-mom please free feel to re-open the issue if you see this issue again with newer version of the driver. Thank you.

[rabbit-mom]

Thank you very much, the problem has been resolved.