Jdbc connection string

Hi All,
I am trying to connect to sysbase tables with
Connection String: <b>jdbc:sybase:TDS5:DB110:3400:falud002</b>
JDBC Driver: <b>com.sybase.jdbc3.jdbc.SybDriver</b>
But it gives me error in RWB as:
<b>Error during database connection to the database URL 'jdbc:sybase:TDS:DB110:3400:falud002' using the JDBC driver 'com.sybase.jdbc3.jdbc.SybDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sybase:TDS:DB110:3400:falud002': SQLException: JZ0D5: Error loading protocol com.sybase.jdbc3.tds.TDS.'</b>
Please advice....
Xier

Hey
i know you might have done it but just want to make sure whether u have installed the proper drivers for Sybase or not?
Thanx
Aamir

Similar Messages

  • Adworker using wrong JDBC connect string during upgrade to 12.1.3

    Our env
    APPS - 12.1.2 - running on SLES 11
    DB 11.2.0.3 - running on IMB System z
    We cloned PROD to a new host (instance was previously on DB host - debsdb01 and app host debsap03)
    The clone was made to debsdb04 - and app was reconfigured on debsap03
    I got the app to start up and run before taking it down to apply the 12.1.3 patch.
    However, in the process of the 12.1.3 patch, I see the following entry in the ADworker log files.
    JDBC connect string from AD_APPS_JDBC_URL is
    (DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=hostname1.companyname.com)(PORT=1549)))(CONNECT_DATA=(SID=DEV3)))
    where as it should be
    JDBC connect string from AD_APPS_JDBC_URL is
    (DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=hostname4.companyname.com)(PORT=1535)))(CONNECT_DATA=(SID=DEV3)))
    If I do an echo $AD_APPS_JDBC_URL on debspap03, it returns
    JDBC connect string from AD_APPS_JDBC_URL is
    (DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=hostname4.companyname.com)(PORT=1535)))(CONNECT_DATA=(SID=DEV3)))
    Where are the ADWORKERS getting the old value of the DB host name?
    Any help would be appreciated.
    Thanks
    Edited by: 864641 on Sep 16, 2012 7:32 AM

    I believe figured out what the issue was.
    I was (am) running the patch session from a VNC session that was established during the previous version of this instance - so the previous connect string was being used.
    Once I killed the old VNC session and established a new one, I was able to retrieve the correct value for $AD_APPS_JDBC_URL from the command prompt.
    Yes - the value of the $AD_APPS_JDBC_URL was showing the old value in the old VNC session.
    Thanks for all of your input esp on a Saturday - when I thought I would have to wait until Monday to get this figured out.

  • Specify tablespace within JDBC connect string...

    In MySQL, I can specify a database name within a JDBC connect string. Can one specify an Oracle tablespace within a JDBC connect string? The goal is to have one account to access multiple tablespaces.
    Please advise,
    R

    R,
    I think perhaps you misunderstand what a tablespace is in Oracle.
    If you haven't already done so, I suggest reading Oracle Database Concepts and Oracle Database Administrator's Guide which are part of the Oracle documentation and available from:
    http://www.oracle.com/technology/documentation/index.html
    Good Luck,
    Avi.

  • JDBC connection string to an MS Access DB

    Hello,
    I was searching for a package that will allow me to do
    a JDBC connection to an MS Access DB. I found out about RMIJDBC, but I am not sure what I need to specify as my connection string. In SQL Server you usually give a url as well, but how about MS Access?
    How do you do a connection??
    Thank you for your help!
    -Lia-

    Why not using the Jdbc/Odbc driver with the Odbc connection of MS Access ? The driver name is "sun.jdbc.odbc.JdbcOdbcDriver" and the URL is something like "jdbc:odbc:myAccessOdbcName".
    Of course, this is not the fastest driver, but it is provided in standard with the JDK.
    Matthieu

  • Server name problem-jdbc connection string

    hi..
    my server name is SERKANPROX\LOCALHOST .. i couldn't connect to this server with this server name . how can i write the server name in connection string?. this is the part my code:
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
    Connection con = DriverManager.getConnection("jdbc:microsoft:sqlserver://serkanprox//localhost:1 433;DatabaseName=NorthWind","serkan","serkan");
    the exception is : [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    i can connect to the server which name is "serkan" . but when there is a '\' character ,i couldn't..
    how can i can change the connection string for connecting to this server ..
    thanksss

    hi..
    my server name is SERKANPROX\LOCALHOST No it isn't. Get the right server name. This problem has nothing to do with your username and password and such.

  • Jdbc, connection string to a rack

    hello,
    can i connect on jdbc receiver side to a rack ( logical instance instead of a physical instance) or to 2 ipaddresss instead of one in case one node gets down?
    i currently have a connection string as : jdbc:oracle:thin:@ipaddress:port:Databasename
    Please suggest.
    Thanks

    Closing thread.

  • JDBC Connection String for MS Sql Server 2000 with Instance Name

    Hi All,
    I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
    driver when the database server has an Instance Name. If the database server has
    no instance name then I am able to connect using the connection string
    connection=jdbc:weblogic:mssqlserver4:hansa:1433
    But when I have the MS Sql Server DB with an instance name such as "TestInstance",
    then I am unable to connect with any of the connection strings given below
    connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
    Can anybody help me in resolving this issue. Appreciate your help.
    Thanks in advance.
    Vikram

    Vikram wrote:
    Hi All,
    I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
    driver when the database server has an Instance Name. If the database server has
    no instance name then I am able to connect using the connection string
    connection=jdbc:weblogic:mssqlserver4:hansa:1433
    But when I have the MS Sql Server DB with an instance name such as "TestInstance",
    then I am unable to connect with any of the connection strings given below
    connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
    connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
    Can anybody help me in resolving this issue. Appreciate your help.Hi. No type-4 jdbc driver is going to be able to use a name for a DBMS instance.
    Let's assume you have two DBMS instances running on the machine hansa. One
    of them may be listening for tcp connections on port 1433, but the other must not.
    The other most be listening on some other port number you have chosen.
    Therefore, to choose which DBMS instance you want to connect to, use the
    working URL you have, and switch the port number as desired.
    Joe Weinstein
    >
    >
    Thanks in advance.
    Vikram

  • JDBC connection strings

    We're having a problem connecting to one of our databases using JDBC thin. There seem to be two formats for the connection strings:
    jdbc:oracle:thin:@opctest.deq.state.ms.us:1522:TEST8131
    jdbc:oracle:thin:@//opctest.deq.state.ms.us:1522/TEST8131
    From a java app, the first throws an "Io exception: Invalid connection string format, a valid format is: "//host:port/service_name" " error; the second throws a TNS-12514: TNS:listener does not currently know of service requested in connect descriptor error.
    What confuses me more is that if I test this string from a JSP page:
    jdbc:oracle:thin:@opctest.deq.state.ms.us:1522:test8131
    it connects fine.
    The environment is Oracle9i on Red Hat, running MTS. Java app is running on WinXP. Anyone have an idea what's going on?
    Thanks,
    Harry

    I can see a couple of issues in your connect string:
    1. I see you are using the sid in uppercase, TEST8131 instead of test8131. If you are working on a unix environment this makes a difference, so use the lower case instead.
    2. You are using the 1522 port, check with your database administrator if the instance is registered against the 1522 port, otherwise the error TNS-12514 will show up. I will assume it currently works fine since you have declared the jsp using the same address works fine with this port.
    3. Ensure the hostname can be solved just exactly the way you have declared it (fully qualified domain) from the perspective where the jdbc program is running.
    4. the format described here: opctest.deq.state.ms.us:1522/TEST8131 is known as the EZConnect, and it is a 10g feature.
    ~ Madrid

  • Load balance not working right with jdbc connection string?

    For months we've used the following connection string to get Tomcat to open connections to our Oracle 10g RAC:
    jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST
    = db1vip) (PORT = 1521)) (ADDRESS = (PROTOCOL = TCP) (HOST = db2vip)
    (PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED)
    (SERVICE_NAME = orcl) (PREFER_LEAST_LOADED_NODE_ORCL = OFF) ) )
    Today, db2 became inaccessible during prime time, and the web app completely hung--when you tried to type in a username and password to log into the site, it would just hang indefinitely, and the Tomcat log files were complaining about being unable to open a connection to the database because of a network adapter error.
    I would have expected the JDBC driver Tomcat was using to just switch to the other database server, but none of our Tomcat machines did that, and I'm wondering why (they all just hung trying to connect to db2). Our guess is that the difference this time is not that Oracle was down on db2, but that db2 was down entirely. Maybe that connection string works only if the server is up when the database is down, and not when the server is unreachable (we couldn't SSH to the box, and when we tried to get to it locally using a remote access card, a lot of options were grayed out and we couldn't see a shell, so all we could do was reset the box).

    Hi,
    Please refer to the link below:
    SCOM 2012 – Monitoring Oracle Database OLE DB Management Pack Template
    http://stefanroth.net/2012/12/05/scom-2012-monitoring-oracle-database-ole-db-management-pack-template/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • JDBC connection string from POJOs

    I have created a new connection named ConnDB. It was added in Application Resources/Descriptions in file connections.xml.
    I want to access this connection string in my POJOs. How do I grab my connection?

    example :
            DCIteratorBinding dciterb =(DCIteratorBinding)dcbind.get("ParcelsView1Iterator");
            dciterb.executeQuery();
            DCDataControl dc = dciterb.getDataControl();
            ApplicationModule am = (ApplicationModule)dc.getDataProvider();
            Statement st = am.getDBTransaction().createStatement(0);rg Thomas

  • Constructing a correct jdbc connection string

    I am not particularly fluent in JDBC URL construction and though I have come up with many variations, I have so far failed to come up with the single variation that will work for my database :-)
    I am running Oracle 10 and I have a connection to the target database in SqlDeveloper. Opening the properties of my existing connection, I observe that the type is TNS. Looking up the network alias specified in my tnsnames.ora I was then able to get the hostname, the service name, and the port (1521), and I observed that it said "Server=DEDICATED" though I don't appreciate the significance of that last item.
    So I tried IBM's jdbctest tool (among others) with a JDBC URL of:
    jdbc:oracle:thin:<username>/<pwd>@<hostname>:1521:<servicename>
    and with the ojdbc14.jar driver, received this error:
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    I also tried "telnet <hostname> <port>" because jdbctest suggested it, and I received "Connect failed". jdbctest notes that a refused connection means the port is wrong but says nothing about a failed connection. I saw one reference that said the last component of the string should be <dbname> rather than <servicename>. So where do I check the dbname? And what else am I missing?

    jdbc:oracle:thin:<username>/<pwd>@<hostname>:1521:<servicename><servicename> is SID of databsae running on server and not your tnsname alias.
    Telnet can fail if telnet service is not running.
    Did you tried tnsping
    c:\>tnsping <tnsnames.ora service alias>
    Server=DEDICATED indicates that you want to have dedicated oracle process for your applicaiton unlike shared server process where many users share the same proecss. Shared server connection is typically used for large number of db users conencting concurrently.

  • Cannot figure jdbc connection string using LDAP to lookup db

    I found only one example of this
    "jdbc:oracle:thin:@ldap://ldap.acme.com:7777/sales,cn=OracleContext,dc=com"
    My ldap.ora file has this in it:
    DEFAULT_ADMIN_CONTEXT = "dc=ba,dc=ssa,dc=gov"
    DIRECTORY_SERVERS= (s07a29b.ba.ssa.gov:389:636,s1pta34.ba.ssa.gov:389:636,r24300a.ba.ssa.gov:389:636)
    My db is ismarts1
    I've tried all variations I can think of and cannot get it to work. Most obvious would be this:
    jdbc:oracle:thin:@ldap://s078a9b.ba.ssa.gov:389:636/ismarts1,dc=ba,dc=ssa,dc=gov
    but it is not working...
    I don't get the 2 port numbers (if that's what they are) in the ldap.ora list of servers.

    You've confirmed that it works in sql*plus?
    The typical format of the url is
    jdbc:oracle:thin:@ldap://[host]:[port]/[database],cn=OracleContext,[dc=...,dc=...]In your case, you might try
    jdbc:oracle:thin:@ldap://s078a9b.ba.ssa.gov:389/ismarts1,cn=OracleContext,dc=ba,dc=ssa,dc=govSince you do have multiple ldap servers configured, you can also specify more than one in the url separated by a space.
    jdbc:oracle:thin:@ldap://s078a9b.ba.ssa.gov:389/ismarts1,cn=OracleContext,dc=ba,dc=ssa,dc=gov ldap://s1pta34.ba.ssa.gov:389/ismarts1,cn=OracleContext,dc=ba,dc=ssa,dc=govThe 2 port numbers specify the ports ldap listens on, the first being non-ssl and the second being ssl.

  • Configuring RAC-aware JDBC connection in Oracle SQL Developer?

    How can Oracle SQL Developer be configured to properly connect to an [Oracle RAC|http://en.wikipedia.org/wiki/Oracle_RAC] environment, I.E., not just setup to always connect to one of the individual nodes?
    [http://programmersjournal.blogspot.com/2008/08/jdbc-connection-string-for-oracle-rac.html] has an example of a classic and the equivalent RAC-aware version of a JDBC connection string. I've already been using a RAC connection string of the same format from within custom Java applications without issue. I thought the same should be configurable in Oracle SQL Developer by setting the "Connection Type" drop-down to "Advanced", then entering the RAC-aware JDBC connection string as the "Custom JDBC URL". However, upon testing the connection, the following error is displayed at the bottom of the dialog:
    Status : Failure -Test failed: Io exception: NL Exception was generated
    There is no additional information shown on the "Logging Page" view. Using Oracle SQL Developer 1.5.5.
    Thanks!

    Thanks, Barry. Just F.Y.I., it is working for me now that I upgraded to the 2.1 EA as -K- suggested. I had marked his reply as "Correct", but probably should have left a response indicating my success as well.
    Now, if there's anything you could do regarding the [issues around the display performance of CLOBs, etc., in the Query Result view|http://forums.oracle.com/forums/message.jspa?messageID=3906571] , it'd be very appreciated!

  • SQL Developer 3.1 JDBC connect to Teradata fail

    I have the 3.1 release of Oracle SQL developer. I have the JDBC drivers for Teradata. I am tyring to get it to connect but it is failing. The error is very nondescript and of not much benefit. When I create the connection and put in the host name, user ID, default db, and password and click Test I get:
    Status: Failure - Test failed: (null)
    Below is the detail.
    I put this same info into another SQL editor to test the drivers and it connected fine. So the driver and the info I am passing do not seem to be the problem.
    Is there any insight into this error. ( I did see a thread about turning off SSO, except it is already turned off so that is not my issue)
    Please help.
    java.lang.NullPointerException
         at com.teradata.tdgss.jtdgss.TdgssConfigApi.GetMechanisms(Unknown Source)
         at com.teradata.tdgss.jtdgss.TdgssManager.<init>(Unknown Source)
         at com.teradata.tdgss.jtdgss.TdgssManager.getInstance(Unknown Source)
         at com.teradata.jdbc.jdbc.GenericTeraEncrypt.getGSSM(GenericTeraEncrypt.java:623)
         at com.teradata.jdbc.jdbc.GenericTeraEncrypt.getConfig(GenericTeraEncrypt.java:641)
         at com.teradata.jdbc.jdbc.GenericTeraEncrypt.getUserNameForOid(GenericTeraEncrypt.java:734)
         at com.teradata.jdbc.AuthMechanism.<init>(AuthMechanism.java:50)
         at com.teradata.jdbc.jdbc.GenericLogonController.run(GenericLogonController.java:121)
         at com.teradata.jdbc.jdbc_4.TDSession.<init>(TDSession.java:209)
         at com.teradata.jdbc.jdk6.JDK6_SQL_Connection.<init>(JDK6_SQL_Connection.java:30)
         at com.teradata.jdbc.jdk6.JDK6ConnectionFactory.constructConnection(JDK6ConnectionFactory.java:22)
         at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:130)
         at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:120)
         at com.teradata.jdbc.TeraDriver.doConnect(TeraDriver.java:220)
         at com.teradata.jdbc.TeraDriver.connect(TeraDriver.java:153)
         at oracle.jdeveloper.db.adapter.AbstractConnectionCreator.getConnection(AbstractConnectionCreator.java:153)
         at oracle.dbtools.thirdparty.teradata.TeradataConnectionCreator.getConnection(TeradataConnectionCreator.java:31)
         at oracle.jdeveloper.db.adapter.DatabaseProvider.getConnection(DatabaseProvider.java:325)
         at oracle.jdeveloper.db.adapter.DatabaseProvider.getConnection(DatabaseProvider.java:254)
         at oracle.jdevimpl.db.adapter.CADatabaseFactory.createConnectionImpl(CADatabaseFactory.java:60)
         at oracle.javatools.db.DatabaseFactory.createConnection(DatabaseFactory.java:534)
         at oracle.javatools.db.DatabaseFactory.createDatabase(DatabaseFactory.java:208)
         at oracle.jdeveloper.db.DatabaseConnections.getDatabase(DatabaseConnections.java:607)
         at oracle.dbtools.raptor.utils.Connections$ConnectionInfo.getDatabase(Connections.java:156)
         at oracle.dbtools.raptor.utils.Connections.getConnection(Connections.java:1043)
         at oracle.dbtools.raptor.utils.Connections.getConnection(Connections.java:1024)
         at oracle.dbtools.raptor.navigator.DatabaseConnection.openConnectionImpl(DatabaseConnection.java:115)
         at oracle.dbtools.raptor.navigator.AbstractConnectionNode.getConnection(AbstractConnectionNode.java:30)
         at oracle.dbtools.raptor.navigator.ConnectionFilter.getFactory(ConnectionFilter.java:94)
         at oracle.dbtools.raptor.navigator.ConnectionFilter$1.doWork(ConnectionFilter.java:119)
         at oracle.dbtools.raptor.navigator.ConnectionFilter$1.doWork(ConnectionFilter.java:104)
         at oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:515)
         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:662)

    Hi,
    I did a web search for TdgssConfigApi.GetMechanisms null pointer and got lots of hits, but couldn't find any one specific cause. Some had issues with the version of the driver, some with placement of jar files in the correct location (depending on the version, there are 2 or 3), others with the format of the jdbc connect string.
    Try searching for and reading over some of these. Perhaps you can determine if any match your situation.
    Good luck,
    Gary

  • JDBC Connection Reset when using many processes on 64 bit system

    Hi,
    we've a annoying JDBC connection problem since we migrated our Java server to a 64 bit operating system. Here our environment.
    Database Machine:
    Oracle 10g
    Linux 32 Bit (but same problem on 64 Bit)
    Application Servers Machine:
    JDBC driver 11.1.0.6
    SUN Java 1.6.0_06 64bit
    Linux 64 bit (SLES 10 SP2)
    We have 6 different Java server processes (but with the same code) which all create some connections to the same database (running on a different Hardware). All 6 Java server processes starting at the same time (via scripts).
    Everything was fine, until we migrated the application server machine from 32 bit Linux to 64 bit Linux. From this day on, the half (or one more or less) of our application server processes can't longer connect to the database. The application server processes which have the problem product the following stack trace:
    java.sql.SQLRecoverableException: I/O Exception: Connection reset
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:281)
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:118)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:224)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:296)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:611)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:455)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:494)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:199)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:30)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:154)
    at com.aaaa.utils.db.DbConnectionPool.<init>(DbConnectionPool.java:130)
    It looks like a network problem with the system but all other network stuff works without problems, between the two machines.
    - We use the thin JDBC driver (no OCI)
    - No firewalls are active on both systems
    - Both systems are in the same subnet connected to the same switch
    - The DNS configuration on both systems are ok (forward and reverse)
    - We've found the same problem on different application-server/database-server pairs with 64 bit application server hardware - but not all of our 64 bit server systems have this problem.
    - When running application server process and database on the same system (connecting via localhost) the problem does not longer appear.
    - The same database machine connected from a 32 bit application server (with 6 different java processes starting at the same time) works without a problem.
    We've tried a lot of things to isolate the problem - but with no success.
    - Same problem with SUN Java 1.6.0_06 32 bit (on 64 bit Linux)
    - Same problem with SUN Java 1.6.0_15 (32 and 64 bit)
    - Played with some JDBC connection properties (oracle.jdbc.TcpNoDelay, oracle.jdbc.ReadTimeout, oracle.net.CONNECT_TIMEOUT, oracle.net.disableOob, oracle.jdbc.RetainV9LongBindBehavior, oracle.jdbc.StreamChunkSize) without a positive result.
    - We've updated Linux network driver
    - We've changed to an completeky other NIC
    - We've tried an other Linux 64 distribution
    - We've increased the PROCESSES parameter in the init.ora
    - We've tried the JDBC driver 11.1.0.6
    - We've tried the _g version of the JDBC driver, but the debugging output simply tell us "Connection Reset" without a hint why.
    - We've tried a more complex JDBC connect string (
    "jdbc:oracle:thin:@(DESCRIPTION=" +
    "(ADDRESS_LIST=" +
    "(ADDRESS=(PROTOCOL=TCP)" +
    "(HOST=host)" + =
    "(PORT=port)" +
    ")" +
    ")" +
    "(CONNECT_DATA=" +
    "(SERVICE_NAME=sid)" +
    "(SERVER=DEDICATED)" +
    ")" +
    Nothing of this things helped us to isolate the problem.
    When we start our application server processes with a long pause (>1 min) between every process start. The problem does not occure. When we start only one application server with the same number of connections as the 6 different application server processes, everything works fine.
    We have absolute no idea why
    - this only occures on 64 bit Linux
    - independent if it's a 32 bit or 64 bit JVM
    - does not occure on all 64 bit application server machines / database machine pairs
    - never occure on the same 64 bit app server hardware when using a 32 bit Linux
    - using the Oracle JDBC 10g driver (10.xxx) there is no problem (but because of other issues, we need to use the JDBC 11g driver)
    Does anybody has an idea what our problem is?
    Thanks in advance,
    greetings

    I was recently struggling with this exact same problem. I opened a ticket with Oracle and this is what they told me.
    java.security.SecureRandom is a standard API provided by sun. Among various methods offered by this class void
    nextBytes(byte[])
    is one. This method is used for generating random bytes. Oracle 11g JDBC drivers use this API to generate random number during
    login. Users using Linux have been encountering SQLException("Io exception: Connection
    reset").
    The problem is two fold
    1. The JVM tries to list all the files in the /tmp (or alternate tmp directory set by -Djava.io.tmpdir) when
    SecureRandom.nextBytes(byte[]) is invoked. If the number of files is large the
    method takes a long time
    to respond and hence cause the server to timeout
    2. The method void nextBytes(byte[]) uses /dev/random on Linux and on some machines which lack the random
    number generating hardware the operation slows down to the extent of bringing the whole login process to
    a halt. Ultimately the the user encounters SQLException("Io exception:
    Connection reset")
    Users upgrading to 11g can encounter this issue if the underlying OS is Linux which is running on a faulty hardware.
    Cause
    The cause of this has not yet been determined exactly. It could either be a problem in
    your hardware or the fact
    that for some reason the software cannot read from dev/random
    Solution
    Change the setup for your application, so you add the next parameter to the java command:
    -Djava.security.egd=file:/dev/../dev/urandom
    We made this change in our java.security file and it has gotten rid of the error.

Maybe you are looking for