-
Bug
-
Resolution: Won't Fix
-
P2
-
None
-
1.1.5
-
None
-
sparc
-
solaris_2.5.1
I am running the following application:
// You need to import the java.sql package to use JDBC
import java.sql.*;
class Employee
{
public static void main (String args [])
throws SQLException, ClassNotFoundException
{
// Load the Oracle JDBC driver
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
// Connect to the database
// You must put a database name after the @ sign in the connection URL.
// You can use either the fully specified SQL*net syntax or a short cut
// syntax as <host>:<port>:<sid>. The example uses the short cut syntax.
String driverURL = "jdbc:odbc:az1";
if(args.length > 0)
driverURL = args[0];
DriverManager.setLogStream(System.out);
Connection conn =
DriverManager.getConnection (driverURL, "ajay", "ajay09");
// Create a Statement
Statement stmt = conn.createStatement ();
// Select the ENAME column from the EMP table
// ResultSet rset = stmt.executeQuery ("select ENAME from EMP");
// Iterate through the result and print the employee names
// while (rset.next ())
// System.out.println (rset.getString (1));
conn.close();
}
}
in JDK 1.1.5, using Intersolv's data direct ODBC drivers.
The ODBC drivers can be found at /net/greatlakes.central/export/home/avohra/odbc.
When I run the above application, I get a java core dump.
The core dump and truss output can be found in
/net/greatlakes.central/export/home/avohra/java-core.
I have submitted a bug against the ODBC driver as well, but
I can't be sure if it is a ODBC driver bug, or a Java bug.
I can't get hold of type 4 JDBC drivers for Informix, hence I am forced
to consider using JDBC-ODBC bridge. I am testing this bridge
on Oracle, later to be used on Informix at an ISV site.
// You need to import the java.sql package to use JDBC
import java.sql.*;
class Employee
{
public static void main (String args [])
throws SQLException, ClassNotFoundException
{
// Load the Oracle JDBC driver
Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
// Connect to the database
// You must put a database name after the @ sign in the connection URL.
// You can use either the fully specified SQL*net syntax or a short cut
// syntax as <host>:<port>:<sid>. The example uses the short cut syntax.
String driverURL = "jdbc:odbc:az1";
if(args.length > 0)
driverURL = args[0];
DriverManager.setLogStream(System.out);
Connection conn =
DriverManager.getConnection (driverURL, "ajay", "ajay09");
// Create a Statement
Statement stmt = conn.createStatement ();
// Select the ENAME column from the EMP table
// ResultSet rset = stmt.executeQuery ("select ENAME from EMP");
// Iterate through the result and print the employee names
// while (rset.next ())
// System.out.println (rset.getString (1));
conn.close();
}
}
in JDK 1.1.5, using Intersolv's data direct ODBC drivers.
The ODBC drivers can be found at /net/greatlakes.central/export/home/avohra/odbc.
When I run the above application, I get a java core dump.
The core dump and truss output can be found in
/net/greatlakes.central/export/home/avohra/java-core.
I have submitted a bug against the ODBC driver as well, but
I can't be sure if it is a ODBC driver bug, or a Java bug.
I can't get hold of type 4 JDBC drivers for Informix, hence I am forced
to consider using JDBC-ODBC bridge. I am testing this bridge
on Oracle, later to be used on Informix at an ISV site.