Home » Open Source » Programming Interfaces » problem with VB6, ODBC, Access, ORACLE 9i, UNIX (Oraclle 9i, HP UNIX, ODBC 9.02.00.8)
problem with VB6, ODBC, Access, ORACLE 9i, UNIX [message #350980] Sun, 28 September 2008 13:29 Go to next message
OlafCologne
Messages: 2
Registered: September 2008
Location: Cologne
Junior Member
We have an application, which under NT without error with two
Databases works. The database can be accessed from VB6 on a
ACCESS.MDB (Acces 97 or Access 2003, both testet) via an ODBC driver.

The two databases are identical, a database and productive
a test database.

The application is now under WIN XP (SP3) run.

With a database always breaks the connection after starting 30s.
Regardless of whether activities are true or not. The other database working correctly. There was also a PC equipped with the same result. There were several drivers tried.

ORACLE Driver 9.02.00.8 and also the current MS ODBC driver and many other versions.

All settings in the registry, etc. to the respective
Databases, to the name, identical. I have changed all timeout parameters - no effect. On the server are also SQLNet.ora and Listener.ora identical.

What can be the cause?

Thanks


ODBC SQL.log

Error by Oracle ODBC Oracle Driver

exe_8_0_0 cc8-fc4 EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 07CC3530
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)

exe_8_0_0 cc8-fc4 ENTER SQLExecDirectW
HSTMT 07CC3530
WCHAR * 0x51C416C0 [ -3] "SELECT "LVSOWN"."SYSTEM_PARA"."SYS_ID" FROM "LVSOWN"."SYSTEM_PARA" WHERE (("SYS_TYP" = 40 ) AND ("SYS_NAME" = 'USER_TIMEOUT' ) ) \ 0"
SDWORD -3

exe_8_0_0 cc8-fc4 EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 07CC3530
WCHAR * 0x51C416C0 [ -3] "SELECT "LVSOWN"."SYSTEM_PARA"."SYS_ID" FROM "LVSOWN"."SYSTEM_PARA" WHERE (("SYS_TYP" = 40 ) AND ("SYS_NAME" = 'USER_TIMEOUT' ) ) \ 0"
SDWORD -3

DIAG [S1000] [Oracle][ODBC][Ora]ORA-03114: Nicht mit ORACLE verbunden
(3114)


Error by Microsoft ODBC Oracle Driver

exe_8_0_0 b2c-714 ENTER SQLAllocStmt
HDBC 07CC1830
HSTMT * 10F418A4

exe_8_0_0 b2c-714 EXIT SQLAllocStmt with return code -1 (SQL_ERROR)
HDBC 07CC1830
HSTMT * 10F418A4

DIAG [08S01] [Microsoft][ODBC driver for Oracle][Oracle]ORA-03114: Nicht mit ORACLE verbunden (3114)

exe_8_0_0 b2c-714 ENTER SQLErrorW
HENV 07CC1788
HDBC 07CC1830
HSTMT 00000000
WCHAR * 0x0012B910 (NYI)
SDWORD * 0x0012B95C
WCHAR * 0x02B3C220
SWORD 4095
SWORD * 0x0012B948

exe_8_0_0 b2c-714 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 07CC1788
HDBC 07CC1830
HSTMT 00000000
WCHAR * 0x0012B910 (NYI)
SDWORD * 0x0012B95C (3114)
WCHAR * 0x02B3C220 [ 80] "[Microsoft][ODBC driver for Oracle][Oracle]ORA-03114: Nicht mit ORACLE verbunden"
SWORD 4095
SWORD * 0x0012B948 (80)


Shocked
icon10.gif  Re: problem with VB6, ODBC, Access, ORACLE 9i, UNIX [message #352370 is a reply to message #350980] Tue, 07 October 2008 06:28 Go to previous message
OlafCologne
Messages: 2
Registered: September 2008
Location: Cologne
Junior Member
The problem is solved. Cool

The application has with the other side a socket-communications, but for what the function of the application was irrelevant.

In case of error (leading to an opposite position was always the case), was the socket before re-opening 2x closed. Once in the program "as scheduled", the second time in OpenCom DLL.

By the 2nd Close is probably also the port of the database connection is closed.

Under WIN NT was so probably not the case.

Previous Topic: Multiple value parameters with JDBC
Next Topic: Interfacing with UPS WorldShip
Goto Forum:
  


Current Time: Fri Sep 19 22:59:46 CDT 2014

Total time taken to generate the page: 0.07976 seconds