Subscribe

SMO 3.0.1 - Connection reset errrors when trying to connect to repository

[ Edited ]

Customer is running RHEL51 with Oracle 10GR2.  When trying to connect to the repository to create a profile, the conection always fails with a "Connection Reset" error. See below.  Below is the TNSPING and SQLPLUS connection strings that do work with the same connection string:

[root@joebravo ~]# smo diag jdbc -host samtheeagle -sid site -port
1522 -username smorep -password xxxxxxxx
    SMO-15301: Trying to connect to...
    SID: site
    Host: samtheeagle
    Port: 1522
    Username: smorep
    Password: ******
    As Sysdba: No
    SMO-15302: JDBC URL: jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = samtheeagle)(PORT = 1522)))(CONNECT_DATA = (SID = site)))
    SMO-15303: Attempting connection ...
    SMO-15305: Error occurred while attempting connection: IO exception: Connection reset
    SMO-15307: JDBC Connected: No

HERE IS THE TNSPING CONNECT STRING:

[root@joebravo ~]# tnsping site

TNS Ping Utility for Linux: Version 10.2.0.4.0 - Production on
01-JUN-2009 16:43:00

Copyright (c) 1997,  2007, Oracle.  All rights reserved.

Used parameter files:
/usr/local/oracle/product/10.2.0/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = samtheeagle.backstopsolutions)(PORT = 1522)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SITE))) OK (0 msec)

HERE IS THE CONNECT STRING FOR SQLPLUS:

[root@joebravo ~]# sqlplus smorep/xxxxxxxx@site

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options

Re: SMO 3.0.1 - Connection reset errrors when trying to connect to repository

Hi Mike,

Can you send in a system dump? ( If this error causes problems with

the dump then please send in the contents of ~/.netapp/smo/3.0.1/ )

One thing you might try is specifying a fully qualified host name to

the jdbc diag command and see if that makes a difference.

Thanks,

Carl