I am getting a very long delay (about 2 minutes) opening initial connections on my 11g2 development server. Sometimes I get "ORA-28547" and no connection at all. However, the problem disappears on the second attempt.
post results from following OS commands below
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. //
970864 wrote:since you choose to purposefully disregard a polite request for details,
Yes, we have taken all of those steps and no progress. It is worth noting that occi instant client does not use tnsnames infrastructure.
tags to make it legible, use the Preview tab to check.
970864 wrote:How can they been inactive !!!
@jgarry, thanks. The instances are nearly all inactive most of the time, and our instance is the only one experiencing this problem.
There are no WAIT states on netstat -a.
Occi, is opening and closing connections in rapid succession. (That's a choice of our testing framework, not ours.) This is a dev environment, not production. The delay occurs with SQLPlus and SQLDev as well, which leads me to believe it's not occi.