Oracle的SID为check_db。如果URL为
jdbc:oracle:thin:@192.168.2.2:1521:dddddd会报错:connection refused(......)。如果 ID 地址错误,或端口错误,或SID为 check_db,也就是真正的SID,就报错:The network Adapter could not establish the connetion.也就是我的连接是正常的。同样的语句,连接Windows 2000上的Oracle没有问题,有问题的是安装在Linux服务器上的Oracle。 望不吝指教。
jdbc:oracle:thin:@192.168.2.2:1521:dddddd会报错:connection refused(......)。如果 ID 地址错误,或端口错误,或SID为 check_db,也就是真正的SID,就报错:The network Adapter could not establish the connetion.也就是我的连接是正常的。同样的语句,连接Windows 2000上的Oracle没有问题,有问题的是安装在Linux服务器上的Oracle。 望不吝指教。
解决方案 »
- sql语句面试题 求解答(貌似挺难的)
- java中的正则表达式问题
- ajax 省市级联
- 带参数的跳转
- 菜niao问题:关于===注册小系统====== 乱码怎么解决
- SSH框架导入struts,hibernate,spring分先后顺序吗>>
- 去掉重复行的问题?
- 请问:我下了一个jsp网站工程,可以在本机上面运行,我怎样去弄懂它是怎么做的呀,以提高自已的水平
- jsp中如何判断并打开客户端的word程序?
- 请问配好过Tomcat IIS HowTo:将Tomcat装入IIS的大哥,是怎么配的啊。我注册表那个地方不是很明白,结果是原来的IIS还能用,可Tomcat却不能
- 大家讨论:java与.net谁的发展空间改大?该以哪个为主导方向?
- 偶的第一个servlet,怎么总出问题呢?
但是把文件放到数据库server上就没有问题了
步骤:oracle安装目录-----》BIN----》TNSLSNR 双击启动
试一下
Date: 19 Nov 2001 10:47:25 +0100
Message-ID: <[email protected]>
Subject: [suse-oracle] Jdbc thin driver problem solved (was: jdbc thin driver: connection refused
Short summary: If you have problems with connecting your NT client to
your Linux server using jdbc thin client, be sure that the server
machine name as known at the server exists at the client (and is the
same name).
Long story:
* Jon Haugsand
> To all who have tried to help me, thanks. I have now gotten some help
> from Oracle and though they could not find the cause of my problem,
> they found a way to live with it. (They suspect some bad
> configuration.) Here is a summary of the problem and the suggested
> cure, just in case others should struggle with the same problem.
>
> I have two Oracle servers, one Linux and one NT. I have two Oracle
> clients, one Linux and one NT. All in all, four machines
> interconnected through tcp/ip. Each client attempts to connect to
> each server using both standard protocol (?), e.g. using sqlplus and
> the jdbc thin driver, all in all I have 8 connection scenarios.
>
> Oracle on Linux is 8.1.7 (both server and client).
> Oracle on NT is 8.1.6 (both server and client).
> Several jdbc thin drivers are tested, including the latest downloaded
> from Oracle.
>
> Linux server NT server
> ------------------------------------------------------------
> Linux sqlplus OK OK
> Linux jdbc thin OK OK
> NT sqlplus OK OK
> NT jdbc thin fails OK
>
> Driver is oracle.jdbc.driver.OracleDriver
>
> The connection string used: jdbc:oracle:thin:@192.168.22.35:1521:ora8
>
> The NT jdbc thin client failed with:
> java.sql.SQLException: Io exception: The Network Adapter could
> not establish the connection
> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
> at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:335)
> at
> oracle.jdbc.driver.OracleConnection.<init>
> (OracleConnection.java:361) at
> oracle.jdbc.driver.OracleDriver.getConnectionInstance
> (OracleDriver.java:442)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:321)
> at java.sql.DriverManager.getConnection(DriverManager.java:517)
> at java.sql.DriverManager.getConnection(DriverManager.java:177)
> at Nytest.main(Nytest.java:54)
> java.lang.RuntimeException: SQL Exception Io exception:
> The Network Adapter could not establish the connection
> at Nytest.main(Nytest.java:70)
>
>
> Failed connection enters the listener which does not complain, but no
> activity is found on the server. (That is, I do not know how to
> measure such things. The trace and log files were almost, but not
> completely, empty and obscure.)
>
> A curious observation is that if I restart the listener at the Linux
> server, the NT jdbc thin client works for a few minutes, and then
> fails again.
>
> --------------------------------
> OK, then the CURE:
>
> The Oracle support suggested I use the following (white space free)
> connection string (structured here for readability):
>
> jdbc:oracle:thin:@(DESCRIPTION=
> (ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)
> (HOST=192.168.22.35)
> (PORT=1521)))
> (CONNECT_DATA=(INSTANCE_NAME=ora8)
> (SERVICE_NAME=sil2002.norges.bank.no)))
>
> Lo and behold, this works. Thanks again for all helpfullness on this
> email list.
(Just after I sent this information, I discovered something. The
following is a copy of what I sent to the Oracle team.)
I have now discovered what might be the cause of the problem, and
I suggest that you test this out, and eventually report this to the
network development folks in your company.
What have been the situation up to now is that the Linux server has
not been a part of the local DNS i our company. That is, the server
name (banklab3) was not known as such at the NT client. Therefore, I
had to use the IP address. However, the server itself, and the Linux
client, uses the /etc/hosts file to be able to map from number to name
and vica versa.
Today, we inserted the Linux server banklab3 into the local DNS server such
that the NT client now knows that banklab3 has the matching IP address.
Today we have no problems with using the jdbc thin client as we had before.
Can it be so that the Oracle server at the Linux machine does not
"feel comfortable" with numbers and maps the IP address to its name
and returns this to the client, which does not accept this because it
does not know anything about this name?
If so, this is ceratinly not a preferred behaviour of the server, who
should respect the clients view of the world. (I humbly still admit
that there may also be some configuration problems with our Linux
server that makes this really a complex multi cause problem.)