Oracle RDB driver Version 3.01.00.01 Connectivity Issue

I have a SQL Server 2000 extended stored procedure connecting to an Oracle RDB data server via an ODBC connection (using Oracle RDB driver Version 3.01.00.01). The SQL Server 2000 runs on a Windows 2000 Server.
This extended stored procedure opens up multiple database connections and maintains them for processing. Usually, everything runs fine.
However, every so often, we have connectivity issues. What happens is as follows:
When we bring a station down and then try to reconnnect, our connection is denied, and we get the error: "recv() unexpected close Ret 0 Err#0 UNKNOWN Unknown WINSOCK Error 0". (This error is logged by the .dll running in the SQL Server processing space.) From the first time we receive a connectivity error like this until the Oracle RDB box is rebooted, we cannot establish another new ODBC connection to that Oracle RDB box --- whether we are trying to establish it programmatically or just via a "test connection" in the ODBC dialogue on the SQL Server box.
We can, however, establish an ODBC connection to another, identically configured, Oracle RDB box from the SQL Server box (without restarting the SQL Server box).
Has anyone had experience with instable connections from Windows system using the Oracle RDB driver to connect to the Oracle RDB? If not, can anyone point me in a direction that would help me research this? I am more familiar with SQL Server than Oracle, and the Oracle DBA on the other end isn't very accessible.
I'd really appreciate any help anyone can give me.
Thanks!

I got same error.. Are you already solve that problem? how? please help me. Thanks

Similar Messages

Oracle Rdb Driver 3.1.0.0 problem with blobs

I am trying to convert an MsAccess application to use an MsAccess front end and an Oracle Rdb back end.
I've created the test database under VMS and can successfully link to the Oracle Rdb tables from MSAccess 2000. One of the main reasons for converting to Oracle Rdb is to be able to store large word documents in the database. I was able to do that using Oracle rdb Driver v 3.00.02.06. I recently converted to Oracle Rdb Driver version 3.1.0.0 and can no longer access the Blob field containing the Word document. MsAccess now sees this field as type Binary and I keep getting an invalid field type error. (with 3.00.02.06 this field was seen by MsAccess as an Ole Object and the getchunk and appendchunk functions for getting and saving a blob worked reasonably well).
Is this a bug in 3.1.0.0 or is there some way to get MsAccess to recognize this Binary field type?

I suspect you'll need to contact Oracle support on this. There aren't, to my knowledge, any RDB folks around here.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Oracle Rdb Driver 3.1.0.0 problem

I am trying to convert an MsAccess application to use an MsAccess front end and an Oracle Rdb back end.
I've created the test database under VMS and can successfully link to the Oracle Rdb tables from MSAccess 2000. One of the main reasons for converting to Oracle Rdb is to be able to store large word documents in the database. I was able to do that using Oracle rdb Driver v 3.00.02.06. I recently converted to Oracle Rdb Driver version 3.1.0.0 and can no longer access the Blob field containing the Word document. MsAccess now sees this field as type Binary and I keep getting an invalid field type error. (with 3.00.02.06 this field was seen by MsAccess as an Ole Object and the getchunk and appendchunk functions for getting and saving a blob worked reasonably well).
Is this a bug in 3.1.0.0 or is there some way to get MsAccess to recognize this Binary field type?

I suspect you'll need to contact Oracle support on this. There aren't, to my knowledge, any RDB folks around here.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Oracle RDB Driver fails with JDBC/ODBC Bridge

Has anyone experienced problems using the latest Oracle RDB
Driver (3.0.2.0) with the JDBC/ODBC Bridge.
We have been using the Oracle ODBC Driver for RDB (2.10.17)
successfully on NT, but it is not supported on W2K. The new
drivers work fine for Access etc., but fail with the bridge.
Specifically, you can step thru a result set, but getObject()
returns null for all fields.
Any suggestions?
Joe

This forum is for general suggestions and feedback about the OTN
site. For technical question about an Oracle product, you can
select the appropriate discussion forum in our 'Discussions'
section at: http://forums.oracle.com/forums/homepage.jsp
Best regards, OTN Team

In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0

Hi !
Without any problems i'm using the Oracle JDBC Driver version - 10.1.0.3.0 to access to the
Oracle database (Oracle Database 10g Release 10.2.0.1.0 - 64bit Production).
But exchanging the JDBC Driver 10.1.0.3.0 to 10.1.0.5.0 brings up the following problem:
the statement
con.prepareStatement(sql, resultSetType, resultSetConcurrency, resultSetHoldability)
(with parameters resultSetType = 1003, resultSetConcurrency = 1007, resultSetHoldability= 1)
returns null !
while using the Oracle JDBC Driver version - 10.1.0.3.0 the statement (with same parameters)
returns a correct PreparedStatement.
Every hint or idea is welcome.
Best regards,
Claus

Duplicate post:
In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0
Claus,
Pardon me if I am stating the obvious, but why don't you use the 10.2 JDBC driver with your 10.2 database? The driver is part of the database distribution. Otherwise, you can download the driver from the OTN Web site.
Good Luck,
Avi.

Oracle ODBC Driver version

Hello,
I installed the latest ODAC version (ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio (11.2.0.2.1)) on my Windows system.
However, when I check the ODBC driver version in ODBC Data Source Administrator I see:
Orcale in OraClient11g_home1 - version 11.01.00.07
I was expecting version 11.2.0.2.0
How can I check what Oracle ODBC driver version I have installed?
Thank you,
M.R

Problem solved, the driver has been updated but not the version number+ (there is a bug filled for that).
Edited by: user7047382 on Jan 12, 2011 9:51 AM

Oracle jdbc driver spending 40 seconds to make connection to Oracle db 11g

we are using weblogic 10.3.3 and teh default Oracle11.1.0.7 Driver ojdbc6.jar to talk to Oracle db 11.2.0.1
After reviewing weblogic logs I see that it takes 50 secodns for each connection to db
HHere is a snippet (note I put in a 10 sec login dleay as i was experimenting, butt eh problem still occurs with or without login delay)
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001516> <Connection Pool "acm_repository" connected to Database: "Oracle", Version: "Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options".>
Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001517> <Connection Pool "acm_repository" using Driver: "Oracle JDBC driver", Version: "11.1.0.7.0-Production".>
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "acm_repository".>
<Dec 21, 2010 1:28:19 AM GMT> <Info> <JDBC> <BEA-001066> <Delaying 10 seconds before making a acm_repository pool connection.>
<Dec 21, 2010 1:29:09 AM GMT> <Info> <JDBC> <BEA-001068> <Connection for pool "acm_repository" created.>
There is someting wrong in this environment
I donwloaded the _g version fo teh exact same driver and had weblogic use it so I could generate verbose logs
Here is a snippet fo teh oracle drivers verbose log file . If you notice the key parts
it seems like its spending 40 second to make the connection, goes into a setConnectionDuringExceptionHandling method and creates the connection
can someone shed light on what causes itto go into an exception state
This happens for each and every connection but only in one specific environment
we have other environments which seem towork fine with the exact same product versions except for this environment
Thank you for any guidance on troubleshooting this further
-Y
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection parseConnectionProperty_Object
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection readOCIConnectionPoolProperties
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection readConnectionProperties
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection initialize
TRACE_16: Enter: null, null, null
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection initialize
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLine
TRACE_16: Enter:
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLineUnchecked
TRACE_16: Enter:
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLineUnchecked
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.PhysicalConnection needLine
TRACE_16: Exit
Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.T4CConnection logon
**TRACE_16: Enter:**
**Dec 21, 2010 1:27:38 AM oracle.jdbc.driver.T4CConnection connect**
**TRACE_16: Enter: "10.135.3.80:1521:EPFDSQA"**
**Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.T4CMAREngine setConnectionDuringExceptionHandling**
**TRACE_16: Enter:**
**Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.T4CMAREngine setConnectionDuringExceptionHandling**
TRACE_16: ExitDec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: Enter: 178, 8100
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: return: 178
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion findDriverCharSet
TRACE_16: Exit
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion <init>
TRACE_16: Enter: 178, 178, 2000
Dec 21, 2010 1:28:18 AM oracle.jdbc.driver.DBConversion init
TRACE_16: Enter: 178, 178, 2000

I would file an oracle jdbc bug to begin with, but I am guessing the driver is simply waiting
for the DBMS to respond, so yo may need a good DBA to see what the DBMS thinks is going
on at the time. I did hear of a case where the DBMS was doing some auditing, logging
some info during every login. This info was being written to an OS file which just happened
to be remote-mounted and would occasionally take 30 seconds, which caused connection
requests to timeout at the driver end.... WebLogic is just asking the driver for a connection
using your properties, so it's not involved directly with the problem....

Insert into CLOB fails with Oracle ODBC driver version 9.02.00.65

I tried to insert into CLOB using the latest Oracle ODBC driver 9.02.00.65 and it fails. But the same works with earlier versions of ODBC driver earlier to 9.02.00.65 ie., 9.02.00.63.
Here is the code snippet I tried. Any help now is highly appreciated as I am in the crunch time.
I tried the same code snippet with VARCHAR2 column with the same driver and it works.
** CONVDSN.C - This is the ODBC sample code for
** creating File DSN pointers to machine DSNs.
**This code is furnished on an as-is basis as part of the ODBC SDK and is
**intended for example purposes only.
#include <windows.h>
#include <stdio.h>
#include <tchar.h>
#include <sql.h>
#include <sqlext.h>
#include <odbcinst.h>
#include <sqltypes.h>
#define MAXDATALEN 25 //maximum data length per column
#define MAX_COL 15 //maximum column in result set
#define MAX_ROW 100 //maximum number of rows
#define MAXBUFLEN 256
#define SQLERR_FORMAT "SQL Error State:%s, Native Error Code: %lX, ODBC Error: %s"
#define MAXDISPLAYSIZE MAX_COL*(MAXDATALEN+1)
#define SQLWRNMSGTITLE "SQL_SUCCESS_WITH_INFO results"
#define SQLERRCNTDTITLE "SQL_ERROR results continued"
#define SQLWRNMSGTITLE "SQL_SUCCESS_WITH_INFO results"
#define SQLWRNCNTDTITLE "SQL_SUCCESS_WITH_INFO results continued"
#define NULLDATASTRING "SQL_NULL_DATA"
#define SQLERRMSGTITLE "SQL_ERROR results"
// prototypes
void ExpandFileName(LPSTR szFileDSNName, LPCSTR szDSNName);
void MakeLegalName(LPSTR szLegalDSNName, LPCSTR szDSNName);
// main routine: Iterate through the user and system DSNs, creating a pointer
// to each.
void FAR PASCAL DisplayError(SQLRETURN nResult, HWND hWnd, SWORD fHandleType, SQLHANDLE handle);
void insertSelectClob();
void checkRcCode(RETCODE rc);
int main (int argc, char* argv[])
     insertSelectClob();
return 0;
void FAR PASCAL DisplayError(SQLRETURN nResult, HWND hWnd, SWORD fHandleType, SQLHANDLE handle)
     UCHAR szErrState[SQL_SQLSTATE_SIZE+1]; // SQL Error State string
     UCHAR szErrText[SQL_MAX_MESSAGE_LENGTH+1]; // SQL Error Text string
     char szBuffer[SQL_SQLSTATE_SIZE+SQL_MAX_MESSAGE_LENGTH+MAXBUFLEN+1];
     // formatted Error text Buffer
     SWORD wErrMsgLen; // Error message length
     UDWORD dwErrCode; // Native Error code
     int iSize; // Display Error Text size
     SQLRETURN nErrResult; // Return Code from SQLGetDiagRec
     SWORD sMsgNum = 1;
     SWORD fFirstRun = TRUE;
     char szDispBuffer[MAXDISPLAYSIZE+1]; // Display Buffer
     szBuffer[0] = '\0';
     do
          // continue to bring messageboxes till all errors are displayed.
          // more than one message box may be reqd. as err text has fixed
          // string size.
          // initialize display buffer with the string in error text buffer
          strcpy(szDispBuffer, szBuffer);
          // call SQLGetDiagRec function with proper ODBC handles, repeatedly until
          // function returns SQL_NO_DATA. Concatenate all error strings
          // in the display buffer and display all results.
          while ((nErrResult = SQLGetDiagRec(fHandleType, handle, sMsgNum++,
               szErrState, &dwErrCode, szErrText,
               SQL_MAX_MESSAGE_LENGTH-1, &wErrMsgLen)) != SQL_NO_DATA)
               if(nErrResult == SQL_ERROR || nErrResult == SQL_INVALID_HANDLE)
               break;
               wsprintf(szBuffer, SQLERR_FORMAT, (LPSTR)szErrState, dwErrCode, (LPSTR)szErrText);
               iSize = strlen(szDispBuffer);
               if (iSize && (iSize+strlen(szBuffer)+1) >= MAXDISPLAYSIZE)
               break;
               if (iSize)
               strcat(szDispBuffer, "\n");
               strcat(szDispBuffer, szBuffer);
          // display proper ERROR or WARNING message with proper title
          if (nResult == SQL_SUCCESS_WITH_INFO)
               MessageBox(hWnd, szDispBuffer, (fFirstRun? SQLWRNMSGTITLE : SQLWRNCNTDTITLE),
               MB_OK | MB_ICONINFORMATION);
          else
               MessageBox(hWnd, szDispBuffer, (fFirstRun? SQLERRMSGTITLE : SQLERRCNTDTITLE),
               MB_OK | MB_ICONEXCLAMATION);
          if (fFirstRun)
               fFirstRun = FALSE;
     while (!(nErrResult == SQL_NO_DATA || nErrResult == SQL_ERROR || nErrResult == SQL_INVALID_HANDLE));
void insertSelectClob()
SQLCHAR clobdata[1001];
SQLCHAR resultdata[1001];
SQLINTEGER ind = SQL_DATA_AT_EXEC;
SQLCHAR *bufp;
     SQLINTEGER cbOrderID = sizeof(SQLSMALLINT);
     SQLSMALLINT sTmp=13;
     SQLCHAR *sqlStmt1 = _T("INSERT INTO clobtbl(id, clob1) VALUES(?, ?)");
     SQLCHAR *sqlStmt2 = _T("SELECT id, clob1 FROM clobtbl");
//     SQLCHAR *sqlStmt1 = _T("INSERT INTO testInsert(id, clob1) VALUES(?, ?)");
// SQLCHAR *sqlStmt2 = _T("SELECT id, clob1 FROM testInsert");
int clobdatalen, chunksize, dtsize, retchklen;
     HENV envHnd;
HDBC conHnd;
HSTMT stmtHnd;
RETCODE rc;
     int nRowcnt=0;
     SQLPOINTER pToken = NULL;
rc = SQL_SUCCESS;
// ENV is allocated
rc = SQLAllocEnv(&envHnd);
// Connection Handle is allocated
rc = SQLAllocConnect(envHnd, &conHnd);
rc = SQLConnect(conHnd, T("testd734"), SQLNTS, T("ipathdba"), SQLNTS, T("ipathdba"), SQLNTS);
printf(_T("Insert CLOB1 using SQLPutData...\n[%s]\n"), sqlStmt1);
// Set CLOB Data
int i;
SQLCHAR ch;
for (i=0, ch=_T('A'); i< sizeof(clobdata)/sizeof(SQLCHAR); ++i, ++ch)
if (ch > _T('Z'))
ch = _T('A');
clobdata[i] = ch;
clobdata[sizeof(clobdata)/sizeof(SQLCHAR)-1] = _T('\0');
clobdatalen = lstrlen(clobdata); // length of characters
chunksize = clobdatalen / 7; // 7 times to put
     rc = SQLAllocHandle(SQL_HANDLE_STMT, conHnd, &stmtHnd);
// Step 1: Prepare
rc = SQLPrepare(stmtHnd, sqlStmt1, SQL_NTS);
// checkSQLErr(envHnd, conHnd, stmtHnd, rc);
// Step 2: Bind Parameter with SQL_DATA_AT_EXEC
rc = SQLBindParameter(stmtHnd,
1,
SQL_PARAM_INPUT,
SQL_C_SSHORT,
SQL_INTEGER,
0,
0,
&sTmp,
0,
&cbOrderID);
rc = SQLBindParameter(stmtHnd,
2,
SQL_PARAM_INPUT,
SQL_C_CHAR,
SQL_LONGVARCHAR,
clobdatalen*sizeof(CHAR),
0,
(SQLPOINTER)clobdata,
clobdatalen*sizeof(CHAR),
&ind);
// checkSQLErr(envHnd, conHnd, stmtHnd, rc);
// Step 3: Execute
rc = SQLExecute(stmtHnd);
     while (rc == SQL_NEED_DATA) {
          rc = SQLParamData(stmtHnd, &pToken);
          if (rc == SQL_NEED_DATA) {
               for (dtsize=0, bufp = clobdata;
                    dtsize < clobdatalen;
                    dtsize += chunksize, bufp += chunksize)
               int len;
               if (dtsize+chunksize < clobdatalen)
                    len = chunksize;
                    rc = SQLPutData(stmtHnd, bufp, len*sizeof(SQLCHAR));
               else
                    len = clobdatalen-dtsize;
                    rc = SQLPutData(stmtHnd, bufp, SQL_NTS);
          rc = SQLParamData(stmtHnd, &pToken);
// Fails as row count retrieved is zero.
     rc = SQLRowCount(stmtHnd, &nRowcnt);
     if(rc != SQL_SUCCESS)
          DisplayError(rc, NULL, SQL_HANDLE_ENV, conHnd);
rc = SQLFreeStmt(stmtHnd, SQL_CLOSE);
printf(_T("Finished Update\n\n"));
rc = SQLAllocStmt(conHnd, &stmtHnd);
if (rc != SQL_SUCCESS)
printf(_T("Failed to allocate STMT\n"));
exit(-1);
// Clear Result Data
memset(resultdata, 0, sizeof(resultdata));
chunksize = clobdatalen / 15; // 15 times to gut
rc = SQLExecDirect(stmtHnd, sqlStmt2, SQL_NTS); // select
     if(rc != SQL_SUCCESS)
          DisplayError(rc, NULL, SQL_HANDLE_ENV, conHnd);
// Step 2: Fetch
rc = SQLFetch(stmtHnd);
for(dtsize=0, bufp = resultdata;
dtsize > sizeof(resultdata)/sizeof(CHAR) && rc != SQL_NO_DATA;
dtsize += chunksize-1, bufp += chunksize-1)
int len; // len should contain the space for NULL termination
if (dtsize+chunksize<sizeof(resultdata)/sizeof(CHAR))
len = chunksize;
else
len = sizeof(resultdata)/sizeof(CHAR)-dtsize;
// Step 3: GetData
rc = SQLGetData(stmtHnd,
2,
SQL_C_CHAR,
(SQLPOINTER)bufp,
len*sizeof(CHAR),
&retchklen);
if (!_tcscmp(resultdata, clobdata))
printf(_T("Succeeded!!\n\n"));
else
printf(_T("Failed!!\n\n"));
     if (conHnd)
          SQLFreeConnect(conHnd);
     if (envHnd)
          SQLFreeEnv(envHnd);
}

Hi,
Since 9.2 has been desupported for error correction you will not be able to download that version from OTN. You should ask whoever is providing the training if their is an alternate version you can use. The only versions that you will be able to download from oracle.com is 10.2 11.1, and 11.2.

Oracle RDB driver for java

hello.
i connect to my oracle driver using this
Class.forName("oracle.jdbc.driver.OracleDriver");
but now i have to use oracle RDB and i want to ask how that is done?
do i have to download another jar for that?
and how is the connection string done?
thanks

nope.
you're getting me all wrong
i already have ojdbc14.jar and i already connected to oracle 9iHow did you do that without knowing the connection string?
the problem is with oracle RDB jdbc
that's another different matter.What? I don't understand.
oracle rdb runs under open vms and you have to
install some other things before the rdb jar itself.I don't know about running Oracle on OpenVMS. Sorry.
and i also need the connections tring for the class.How did you "connect" without it?
I gave you a link to the docs, which should tell you what the connection string syntax is. It'll look something like this:
jdbc:oracle:thin:@host:1521:database%

Downloading new firmware version still did not solve connection issue!

I was told my support on live chat to try downloading the newest version of the firmware for my wireless router WRT54G. I had 3.something from 2004.
I now have 4.21.1 and I STILL cannot see my router in my View Available Wireless Networks list. I see my neighbors' connections, but I want mine.
Has anyone found a solution to this yet...Downloading the latest firmware seems useless.
I am now wired in, but not what I wanted

did you reset the router after the firmware upgrade ?? if not , reset the router for 30 seconds..do a power cycle and then reconfigure it ..

Connecting to different servers with Oracle Rdb

Hi,
I have downloaded the Odbc-Driver driver for Rdb and made successful connections to my database server. The name of the server is hardcoded with the odbc administrator. How is it possible to use different servers from asp-script ?
regards
Martin

I have done this, but the Driver (Oracle Rdb Driver, Version 3.00.02.04) do not understand the "DB"-Parameter correctly. The databasename is transferred to the server without the attach-command. So I can only make the connect to a preattached service. This is a known problem by Oracle.

Oracle ODBC Driver - latest version

Hello,
I installed the latest ODAC version (i.e. ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio (11.2.0.2.1)) on my Windows system.
However, when I check the ODBC driver version in ODBC Data Source Administrator I see:
Oracle in OraClient11g_home1 - version 11.01.00.07
I was expecting version 11.2.0.2.0
Also, if I create a new ODBC data source and click on Test Connection -> About, I get:
Oracle ODBC Driver
Version 11.1.0.7.0
Copyright @ 1996, 2007 Oracle
I am really confused, why I cannot see the latest 11.2.0.2 version installed???
Thank you,
M.R

There's a bug filed for that. The driver is actually 11202 (you can check the build date), but the version number didnt get rev'd.
Greg

Problems moving ODBC RDB driver from 2.1.13 to 3.x

Hello. I'm new.
I doubt that anyone can assist us in our situation, but I can't find any help anywhere else.
We've been using Forms (see info below, please) for years with ODBC for RDB driver version 2.10.13.00. We would like to move to ODBC for RDB driver version 3.x (3.2 is the latest, I believe) for several reasons.
However, when I run our application against a data source using the new driver, it crashes quite frequently when committing changes. I do not know why. I get a win32 exception dialog box, and nothing else (no forms dump file).
BUT when I turn on SQL Tracing, everything works just fine! When I turn on Driver Logging, it sometimes works and sometimes doesn't, depending on which driver logging setting I use.
When it fails, the last line in the rdbodbc.log file is...
.._uCnvBinaryToChar 0X00000000
or...
bccSQLExecuteLckd
or...
the dml statement
.0X03A27DF8: INSERT INTO ORGANIZATION ( ORGANIZATION_ID,ORGANIZATION_NA
.ME,ORGANIZATION_NAME_2,ADDRESS_1,ADDRESS_2,CITY,STATE,ZIP_1,ZIP_2,EMAI
.L_ADDRESS,REMARK_1,REMARK_2 ) VALUES ( ?, ?,NVL( ?,' '),NVL( ?,' '),N
.VL( ?,' '),NVL( ?,' '),NVL( ?,'XX'),NVL( ?,0),NVL( ?,0),NVL( ?,' '),NV
.L( ?,' '),NVL( ?,' ') ) RETURNING DBKEY INTO ?
...depending on the driver logging setting.
One particular form always seems to crash on a simple insert statement within a block's On-Insert trigger. The block contains only items with a number or char data type. I have made a great many code variations and it doesn't make it work, but I can get it to work if I place an alert message right before the insert statement or a win_api_utility.sleep(...) statement. And as I mentioned before, it works fine if I turn on SQL Tracing.
So, I am not sure if there is some known issue with Forms and ODBC RDB driver 3.x that we can work around, or if Forms 6i just won't work with the newer driver. Our application contains hundreds of often complex forms, so any fix would have to be relatively simple to implement.
Thanks very much.
Forms 6i (6.0.8.13.0) - running client/server
Oracle RDB database (7.1)
Windows XP
OCA 6.0.5.35.0

Follow-up for anyone interested since apparently no one else in the internet world has this problem. :)
When I activate OCA_DEBUG_ERROR (i.e., set registry OCA_DEBUG_ERROR = TRUE under \\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE), everything works, but I do see this debug message: "OCA-30002 ubofgrd function not supported", which does not get logged when I use the older driver. So, again, if I slow things down enough, it works, but it won't work without logging/tracing turned on. An OCA bug, I suppose?

Oracle JDBC Driver 10.1.0.4.0 and IndexOutOfBounds-Exception

Hello all,
we´ve experienced a weird problem using the Oracle JDBC driver version 10.1.0.4.0. While executing SELECT statement we get an ArrayIndexOutOfBounds exception from the JDBC driver. Here´s the stacktrace:
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at oracle.jdbc.driver.T4CDateAccessor.saveDataFromOldDefineBuffers(T4CDateAccessor.java:212)
at oracle.jdbc.driver.T4CPreparedStatement.saveDefineBuffersIfRequired(T4CPreparedStatement.java:405)
at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:859)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:949)
at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:532)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1037)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2946)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
We couldn´t find anything on the web on this error. We´re using Weblogic 8.1 SP4 with JDBC version. Does anyone have a hint or an idea what could be the problem here?
Thanks for any help in advance!
Cheers,
Joerg

I may have a related bug, I get a similiar exception when running JIRA...
java.lang.ArrayIndexOutOfBoundsException: -1
at oracle.jdbc.driver.DateTimeCommonAccessor.computeJulianDay(DateTimeCommonAccessor.java:341)
at oracle.jdbc.driver.DateTimeCommonAccessor.getMillis(DateTimeCommonAccessor.java:386)
at oracle.jdbc.driver.DateAccessor.getTimestamp(DateAccessor.java:142)
at oracle.jdbc.driver.OracleResultSetImpl.getTimestamp(OracleResultSetImpl.java:1018)...I tried the 10.1.0.2 and 10.1.0.4 drivers, both throw the same exception. I would try the 10.2 drivers, but they just hang! Gotta love Oracle QA!

Select * from table not working with Oracle OBDC driver

Hello,
In our web development we have been using the MS ODBC for Oracle
driver to connect to our Oracle db. We decided to try the
Oracle ODBC driver because it supports the commandTimeout
property in ASP which the MS driver does not. The problem I'm
running into now is that all of our select * from table
statements appear not to be working. The Oracle ODBC driver
version we are using is ver 8.00.05.00. Is there something that
I'm not doing properly? If I take the same select * from table
statement and name the columns, I dont get any error. Otherwise
I'm getting a Subscript out of range error. It seems strange to
me that this driver would not support a select * from table
statement (which I''m told is the case by another developer
here).
Is there something I'm missing?
Thanks,
Pete

I'm positive I have a connection. Otherwise I wouldn't get a
response when I name the columns instead of using *.
There must be something else that I'm missing or doing wrong.
I've actually been looking into alternative ODBC drivers to see
if I have the same problems but none that I have found support
commandTimeout.
Any other ideas?

Oracle RDB driver  Version 3.01.00.01 Connectivity Issue

Similar Messages

Maybe you are looking for

Oracle RDB driver Version 3.01.00.01 Connectivity Issue