February 25, 2009 at 2:37 pm
I am currently trying to get the gateway delivered with Oracle 11g on our new servers. I am able to configure everything and get the listener running and even able to tnsping. But, when I try to connect via sqlplus, I get the following error:
ORA-28547: connection to server failed, probable Oracle Net admin error
I am running:
C:\oracle\product\11.1.0\tg_1\BIN>sqlplus
Am I doing something wrong with sqlplus?
I have installed Oracle 11g gateway on Windows 2003 (64-bit) servers which have Sql Server 2005 (64-bit) running on them.
Our servers are very secure. I am running the gateway on port 1521 and therefore have that port opened. But, I have read about the redirection once the connection is made and how a second port number is randomly chosen and then used so that port 1521 can go back to listening. Does USE_SHARED_SOCKET really allow only port 1521 to be used. ?
I would appreciate any help you may have on this!!!
March 1, 2009 at 3:46 am
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.
// *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=).
//
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.March 2, 2009 at 9:04 am
PaulB (3/1/2009)
oerr ora 2854728547, 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.
// *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=).
//
Paul B,
Thanks for the response, but I believe I DO want to have HS=OK in tnsnames because I need to use heterogeneous services for the gateway to function.
The part that states that the connect succeeds and then fails sounds right. Because I can tnsping. This is the part that led me to believe it was a firewall port issue. From what I understand the gateway starts out using the 1521 port connection, but, once it is made, it uses another port (randomly chosen from a large range of ports) so that 1521 can be used again to make more connections. We only have port 1521 open...
Does anyone see a flaw in my thought process?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply