Home » RDBMS Server » Networking and Gateways » unable to connect to db from client (Oracle 10.2.01.0 database on linux, oracle 10.2.0.2.0 client on windows)
unable to connect to db from client [message #534175] Sat, 03 December 2011 15:03 Go to next message
emergingdba
Messages: 13
Registered: April 2011
Location: bangalore
Junior Member

Hi,

I was trying to connect to oracle 10g database from oracle 10g client. But unable to do so.

i am able to tnsping the db from client but unable to estatblish sqlplus connection. I get ORA-28547 errow when i issue the command sqlplus hr/***@db1. ORA-1560 when the command sqlplus hr/*** is issued.

Caan't figure out why. Please assist.

I have mentioned the listener and tnsnames.ora files

listener.ora
------------

[oracle@localhost admin]$ more listener.ora
# listener.ora Network Configuration File: /home/oracle/product/10.2.0/db_1/netw
ork/admin/listener.ora
# Generated by Oracle configuration tools.

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /home/oracle/product/10.2.0/db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = DB1)
(ORACLE_HOME = /home/oracle/product/10.2.0/db_1)
(PROGRAM = extproc)
)

)

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.79.131 )(PORT = 1521))
)
)



tnsnames.ora
------------

# tnsnames.ora Network Configuration File: T:\oracle\product\10.2.0\client_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.

DB1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.79.131)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = DB1)
)
)

Re: unable to connect to db from client [message #534176 is a reply to message #534175] Sat, 03 December 2011 15:26 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
>ORA-1560 when the command sqlplus hr/*** is issued.
I suspect that above is not the real error.

please use COPY & PASTE to show what you do & how Oracle responds.

issue following OS commands

env | sort
lsnrctl status
lsnrctl service

COPY command & results then PASTE all back here

It would be helpful if you followed Posting Guidelines - http://www.orafaq.com/forum/t/88153/0/

bcm@bcm-laptop:~$ oerr ora 28547
28547, 0000, "connection to server failed, probable Oracle Net admin error"
// *Cause:   A failure occurred during initialization of a network connection
//           from a client process to the Oracle server.  The connection
//           was completed but a disconnect occurred while trying to
//           perform protocol-specific initialization, usually due to
//           use of different network protocols by opposite sides
//           of the connection.  This usually is caused by incorrect
//           Oracle Net administrative setup for database links or external
//           procedure calls.   The most frequent specific causes are:
//           --  The connection uses a connect string which refers
//               to a Heterogeneous Services agent instead of
//               an Oracle server.
//           --  The connection uses a connect string which includes
//               an (HS=) specification.
//           --  Hitting Ctrl+C before connection initialization is
//               complete.
//           --  Using DRCP on Windows with SQLNET.AUTHENTICATION_SERVICES
//               set to NTS.
//           --  Connection timeout due to SQLNET.INBOUND_CONNECT_TIMEOUT
//               parameter when all shared servers are busy in
//               shared server configuration.
// *Action:  Check Oracle Net administration in the following ways:
//           --  When using TNSNAMES.ORA or an Oracle Names server, make sure
//               that the client connection to the Oracle server uses
//               the correct service name or SID.
//           --  Check LISTENER.ORA on the connection end point's host machine
//               to assure that this service name or SID refers
//               to the correct server.
//           --  Confirm in TNSNAMES.ORA or the equivalent service definition
//               that the connect string does not contain (HS=).
//           --  Set SQLNET.AUTHENTICATION_SERVICES to NONE when using DRCP
//               on Windows.
//
bcm@bcm-laptop:~$ oerr ora 1560
01560, 00000, "LIKE pattern contains partial or illegal character"
// *Cause: like pattern is not formed correctly  
// *Action: make sure like pattern is specified correctly 
bcm@bcm-laptop:~$ 


when was last time SQL*Net worked without error?
what changed since then?
Re: unable to connect to db from client [message #534191 is a reply to message #534175] Sat, 03 December 2011 23:36 Go to previous messageGo to next message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
ORA-1560 when the command sqlplus hr/*** is issued.


Most likely incorrect statement in glogin.sql or login.sql file/

Regards
Michel
Re: unable to connect to db from client [message #534195 is a reply to message #534191] Sun, 04 December 2011 04:27 Go to previous messageGo to next message
emergingdba
Messages: 13
Registered: April 2011
Location: bangalore
Junior Member

Hi Black Swan,

I have gone through the guidelines and will follow it appropriately further on. Thanks for the guidance.I shall run the commands given by you and post it here once i am back home.


Hi Michel,

If it a inappropriate entry in the said files what exactly am i supposed to look for in those files.
Re: unable to connect to db from client [message #534198 is a reply to message #534195] Sun, 04 December 2011 04:48 Go to previous message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
SQL statement that contains a LIKE and may lead to the mentioned error.

Regards
Michel
Previous Topic: Listner start failed after configuring
Next Topic: Need some help about using oracle connection manager
Goto Forum:
  


Current Time: Thu Mar 28 23:55:09 CDT 2024