Invalid dates (00.00.0000) inserted with Oracle8.04 (ODBC 8.05)

From: Thomas Mohr <mohr_at_cas-ps.com>
Date: Tue, 9 Mar 1999 09:44:34 +0100
Message-ID: <7c2n2i$t24@fred.cas-ps.com>

Hi,

I'm just testing Oracle8.04 with Oracle ODBC 8.05. After inserting a date value into the database I encountered invalid dates in one of my table (00-DEC 00) without getting any database error
during the insert.
The Problem occurs when use the following sequence in my odbc tester:

Full Connect:

    dbc: szSqlState = "01004", *pfNativeError = 0, *pcbErrorMsg = 43

          szErrorMsg="[Oracle][ODBC]String data, right truncated." Successfully connected to DSN 'TSTTST'. SQLExecDirect:

    In: hstmt=#3 0x00CF18B0, szSqlStr=VALID, cbSqlStr=-3     Return: SQL_SUCCESS=0
SQLAllocStmt:

    In: hdbc=0x00CF16B0, phstmt=VALID     Return: SQL_SUCCESS=0
SQLPrepare:

    In: hstmt=#4 0x00CF28F0, szSqlStr=VALID, cbSqlStr=32     Return: SQL_SUCCESS=0
SQLBindParameter:

    In: hstmt=#4 0x00CF28F0, ipar=1, fParamType=SQL_PARAM_INPUT=1,

          fCType=SQL_C_CHAR=1, fSqlType=SQL_TIMESTAMP=11, cbColDef=50, ibScale=50, rgbValue=VALID,

          cbValueMax=300, pcbValue=VALID, SQL_LEN_DATA_AT_EXEC=FALSE     Return: SQL_SUCCESS=0
SQLExecute:

    In: hstmt=#4 0x00CF28F0
    Return: SQL_SUCCESS=0

The problem seems to be that I use fCType SQL_C_CHAR and fSqlType SQL_TIMESTAMP.
The same procedure works without problems using Oracle7 and ODBC 2.5.

Any idea if there's a bugfix for oracle8 ?? Has anyone encountered the same problem ??

Oracle support told me something like "problems with implicit conversion and the new oci interface".

Thomas

--

---

Dipl. Inform. Thomas Mohr
email: mailto:mohr_at_cas-ps.com Received on Tue Mar 09 1999 - 02:44:34 CST