ODBC Driver V8.00.58.00 Error

Question

Hi
I am experimenting an Oracle ODBC error while selecting more than 2500 records from a database table.
Does anyone known the cause of the error?
Thanks in advance.
==== ENVIRONMENT DESCRIPTION ====
The database server is ORACLE Version 8.0.5.2.1
My database table has the following structure:
CREATE TABLE MY_TABLE
PK_PKEY NUMBER(9) NOT NULL ,
FK_FKEY1 NUMBER(9) NOT NULL ,
FK_FKEY2 NUMBER(5) NOT NULL ,
FIELD1 NUMBER(1) NOT NULL ,
FIELD2 NUMBER(5) NOT NULL ,
CONSTRAINT MY_TABLE_FILED1 CHECK(FIELD1 BETWEEN 0 AND 1),
CONSTRAINT PK_MY_TABLE_KEY PRIMARY KEY (PK_PKEY)
The table is populated with 3000 records where FIELD1 is always equal to 1 (this value is relevant for the queries).
The application that executes the queries to the table is written in Visual C++ 6.0, the database connection is made through ODBC datasouce using the MFC ODBC database classes (CDatabase and CRecordset).
The Oracle client installed to access the database server is from version: ORACLE ODBC driver - Version 8.00.58.00 - Oracle Corporation SQORA32.DLL 1/5/00.
The SQL queries executed in the application are:
QUERY1: SELECT pk_pkey FROM my_table
QUERY2: SELECT pk_pkey FROM my_table where FIELD1=1
QUERY3: SELECT pk_pkey FROM my_table where FIELD1=1 ORDER BY pk_pkey
The C++ application only creates a CDatabase object (m_cDatabase.OpenEx((LPCTSTR)_T(DSN=tc1;UID=myuser;PWD=mypwd))) and a CRecordset object with the previous created database connection. The queries are executed using a simple procedure described in the end of the email.
I test several combinations using the queries described above and the results are quite different. The combinations performed where:
TEST1 - First QUERY2 then QUERY3 RESULT 1
TEST2 - First QUERY1 then QUERY3 RESULT 1
TEST3 - First QUERY3 then QUERY2 RESULT 2
TEST4 - First QUERY3 then QUERY1 RESULT 1
TEST5 - First QUERY1 then QUERY2 RESULT 1
TEST6 - First QUERY2 then QUERY1 RESULT 3
TEST7 - First QUERY1 then QUERY1 RESULT 3
TEST8 - First QUERY2 then QUERY2 RESULT 3
TEST9 - First QUERY3 then QUERY3 RESULT 3
== RESULT DESCRIPTIONS ==
- RESULT 1
The first query is executed successfully but the application catches a database exception when executing the second query.
Database Exception: Restricted data type attribute violation
State: 07006, Native:0, Origin:[ORACLE][ODBC]
- RESULT 2
The first query is executed successfully but the application crash while executing the second query.
The application does not catch any database exception.
The crash description is:
Unhanded exception Application.exe (SQORA32.DLL):0xC0000005 Access Violation
- RESULT 3
The queries returned the expected results. No errors where reported.
==== END OF ENVIRONMENT DESCRIPTION ====
*** VERY IMPORTANT NOTE ***
1. Each test generates a log file where it is possible to confirm the results of the tests.
2. Another element is that the number of times the first query is consecutive executed before the second one does not influence the result of the tests.
3. The error is reported always after the 2500 record is fetch.
4. I executed exactly the same test where the only modification was the version of the ODBC driver used in the client and the tests ran successfully. The results are correct if the client driver is one of the following:
ORACLE ODBC driver - Version 8.01.05.00 - Oracle Corporation SQORA32.DLL 16/02/1999
ORACLE ODBC driver - Version 8.00.05.00 - Oracle Corporation SQORA32.DLL 06/12/1998
5. I also executed the tests with the ORACLE ODBC driver version 8.00.59.00 and the results where the same as from driver v8.00.58.00
6. If I create a restriction in the queries to return less than 2500 records the test are performed successful in all drivers.
== PROCEDURE ==
All the queries are executed in a simple procedure like:
bool CTesteDBDlg::ExecuteTeste(void)
int nIndex = 1;
CString strSQL;
CString strText;
try
CRecordset cRecordset(&m_cDatabase);
strSQL.Format(_T("SELECT pk_pkey FROM my_table"));
//strSQL.Format(_T("SELECT pk_pkey FROM my_table WHERE field1=1"));
//strSQL.Format(_T("SELECT pk_pkey FROM my_table WHERE field1=1 ORDER BY pk_pkey"));
if(!cRecordset.Open(CRecordset::snapshot, (LPCTSTR)strSQL,
CRecordset::readOnly))
return false;
CString strDBValue;
while(!cRecordset.IsEOF())
cRecordset.GetFieldValue((int)0, strDBValue);
LOG_DEBUG_MESSAGE(eLow,(_T("ExecuteTeste1: Index=%ld - Value=%s"), nIndex, strDBValue));
nIndex++;
cRecordset.MoveNext();
catch(CDBException* pDBException)
TCHAR szCauze[256];
pDBException->GetErrorMessage(szCauze, 255);
LOG_DEBUG_MESSAGE(eLow,(_T("Database Exception: Code=%d - Desc = %s"), pDBException->m_nRetCode, szCauze));
return false;
return true;
null

Answer 1

Mr. Cordeiro sent me the project and data he's using. When I run the test program on my 8.0.6 client machine with the 8.0.6 ODBC driver, I see no failures. When I run the test program on my 8.1.6 client machine with the 8.1.6.1 driver, however, I see the problems Mr. Cordeiro describes. If I install the current evelopment build of our 8.1.6 driver, however, the problems disappear. Unfortunately, I don't have an 8.0.5 client machine to test on right now.
I suspect that the problem here has been identified previously, has already been fixed, and will be shipped with the next release of the driver.
My only hesitation here is that the 8.0.5.8 and 8.0.6.0 ODBC drivers are identical code, just linked with different client libraries, so it's unclear why the 8.0.6 client is working while the 8.0.5 client, apparently, is failing. It is possible that there is/was a bug in one of the layers under the ODBC driver which is causing the problem and that different versions of our code hit or miss this problem. I would strongly suggest that you apply the latest Oracle patch kit for your client (i.e. 8.0.5.2.6 for the 8.0.5 client) to see if that fixes your problem. These patch kits are available from the Oracle FTP site-
ftp://oracle-ftp.oracle.com/server/patchsets/wgt_tech/server/windowsNT/
Justin Cave
ODBC Development