OStress - Invalid precision value

microsoft.public.sqlserver.tools

12 Apr 2007 9:33 AM

Damien

Hi All,

Hope I've picked a suitable group for this. Couldn't find a group
dedicated to performance/optimisation.

I'm using OStress to replay a number of RML files against a 2000
database. I keep seeing a number of errors coming out similar to:

[spid 56]SQLState: HY104, Native Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid precision value
[spid 56]Cookie: 8, global sequence: 2203517
[spid 56]Input file: SQL00068.rml
Failed to bind parameter 1 (SQLBindParameter failed)

If I look in my rml file, my only clue of where to look is given by
the global sequence number. But also, invariably, I tend to find I'm
at a section as follows:


<CONNECT>
    <SEQ>2203516</SEQ>
    <NEXTSEQ>2203517</NEXTSEQ>
    <DELTA>26117500000</DELTA>

    <CMD><![CDATA[-- network protocol: TCP/IP
        set quoted_identifier on
        set implicit_transactions off
        set cursor_close_on_commit off
        set ansi_warnings on
        set ansi_padding on
        set ansi_nulls on
        set concat_null_yields_null on
        set language British
        set dateformat dmy
        set datefirst 1
        ]]></CMD>
    <NTDOMAIN>CCCSNT</NTDOMAIN>
    <NETWORK>TCP/IP</NETWORK>
    <DBID>5</DBID>
    <PACKETSIZE>8000</PACKETSIZE>
</CONNECT>
<RPC>
    <SEQ>2203517</SEQ>
    <NEXTSEQ>2203518</NEXTSEQ>
    <REPLAY_DURATION>1</REPLAY_DURATION>
    <DELTA>26117670000</DELTA>

    <CMD><![CDATA[{call sp_reset_connection}]]></CMD>

</RPC>

Neither of which have any parameters. Only other thing I can think to
look at is the previos RPC which does have parameters, but in some
cases their parameters are all INTs (no PREC), or if they do have
VARCHAR parameters, the PRECedences seem to be correct.

Has anyone encountered this, or does anyone have any ideas of where I
should look next?

TIA,

Damien