I-net oranxo driver problem. cannot connect

Question

Hi, im new to the j2ee programming communitty and i was trying to use the i-net type 4 driver to connect to an oracle database. The service name of the oracle database is orcl. i know that the host is the local host, and im pretty sure that the port number is 1521. i dont think i changed it. unfortunately i dont know how to change it. if you could tell me a way to change it once i have already installed it, i would appreciate it.
my code for this problem is
import java.sql.*;
public class testDB{
public static void main(String args[])
     new testDB();
testDB()
     try{
          Connection con = DriverManager.getConnection("jdbc:inetora:localhost:1521:orcl", "scott", "tiger" );
          new com.inet.ora.OraDriver();
          CallableStatement cstmt = con.prepareCall("{call procone(?,?,?)}");
          cstmt.setInt(1,6619211);
          cstmt.setString(2,"Java");
          cstmt.setInt(3,22);
          cstmt.execute();
          con.close();
          }catch(Exception x){
                    System.out.println("exception: "+x);
the error its giving me is the following
com.inet.ora.ORA3SQLException: [OraDriver] Connection Refused:Connect
Anyone know why theres a problem. im sorry i know its probably a dumb question but i cant figure this out.

Answer 1

re: Oracle database and listener:
Oracle does not do things in a simple way. I'll explain things using Oracle's terminology (which I didn't use earlier).
To Oracle, the collection of data-storage (files or devices) that actually has the data is the "database", without regard to any program code or running process.
To Oracle, the memory structures and process (or threads on some OSes) normally used to access a database is called an "instance". (In casual speech, most people call the "instance" the "database"; usually the distinction doesn't matter).
You can have a database without an instance (the program isn't running), an instance without a database (the database hasn't been created or you're using a special Oracle feature called ASM), or you can have multiple instances for one database (an Oracle RAC cluster).
You cannot connect directly to an Oracle instance via a TCP/IP connection (which is normally what a JDBC driver will use, although there are other ways). Instead, Oracle has another program, called the "listener" that brokers connection requests; your program talks to the listener on port 1521 and the listener arranges for your program and the database to connect. The database might actually be on another computer but almost never is, except with RAC clusters or failover configurations. So the listener has to be running for most JDBC programs to work.
SQL*Plus can connect to a database instance via TCP/IP, which requires the listener; however, SQL*Plus can also connect to a database instance that is on the same computer via inter-process communication, which does not require the listener. Stopping the listener process and connecting via SQL*Plus is a common way of putting a database into "maintenance mode", where only the database administrator can make changes to the DB.
The standard Oracle installation will install everything and set up the listener and have it autostart on boot and everything else needed. However, people sometimes disable things they think they don't need, so it's not unheard of for people to turn off the listener becaus they think they don't need it. Or sometimes there's an error and the listener fails to start...