I tried to loged into the database using Cocobase Mapping Administrator (4.0). I have put the classes12.zip in classpath and I am using the thin driver but as soon as I click Login the error message is flashed "Network Adapter error". I wrote small java program with same URL and Driver and was able to connect to the database. I am not getting whats the problem with Cocobase. I am using windows 2000.

This is typically the result of not having a TNS Listener for
TCP/IP configured. See the Tutorials (The BEA BMP tutorial
for Weblogic 6 for instance), and many of them show you how
to install and configure Oracle for JDBC...

CocoAdmin assumes a properly configured DB & JDBC environment,
but for customer convenience we've included configuration
documentation for CocoBase.

THOUGHT Support

You'll need to reread his post to better answer his question.

The oracle database is already properly configured and responding to JDBC requests just fine (his little test JDBC program is running quite happily, as is the program at the end of this message).

But when I put the exact same information into the CocoAdmin "Open New DB Connection" dialog, I get "Login Failed". Interestingly, if I select a JDBC driver that isn't in the CLASSPATH, and click the "Login >" button, I get the same error message.

I'm wondering if it could be a license issue with a really poor error message selection. I don't know how old my evaluation license is, but it could be over 30 days...

package persist;

import java.sql.Connection;
import java.sql.DriverManager;

public class JDBCCheck {

public static void main(String[] args) throws Exception {
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection con = DriverManager.getConnection
("jdbc:oracle:thin:@tom:1521:CNDS", "USER", "PASSWORD");
return;
} // void main(String[])

} // class JDBCCheck

The issue you described was typically the result of TNS
listener issues in the past, but engineering thinks this might
be installer/proxy firewall related.

The other strong possibility is that you have a Proxy Firewall on installation, and that a Proxy configuration
firewall file was written into the CocoBase distribution.
Unless you are using a database outside of your firewall,
you should edit and remove the Proxy settings from this
file:
demos/resources/ProxyConfig.properties

It can cause the symptoms you've described. This
instruction pops up in the GUI installer, but perhaps you
didn't notice it, or ignored it when you installed the
product.

THOUGHT Support

[Edited by admin on 09-09-2002 at 03:46 AM]