Monday 3 March 2008

Connect to Discoverer Plus/Viewer is Very Slow in the Connection Phase

OracleAS Discoverer Plus 10.1.2 installation, is really slow in the connection phase, both from APPS links and Standalone connection. After the insert of the login details in the Connect Box it is showing for approx 20 minutes the following page :

Request Progress

Processing your request
The page you have requested is taking some time to process. Please wait...

The Cause is that the Connect descriptor resolve slowly as it did not contain a valid entry.

Having the following entry in the sqlnet.ora :

NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT, ONAMES, HOSTNAME)

will delay the authentication, as it will first try to authenticate the connect descriptor through OID, where it does not exist.

A simple configuration gain is to change the way the client looks up the connect descriptor. This connect descriptor must be translated by Oracle Net into the network protocol location of the database (IP address and port number) and the name of the database service.

There are a variety of methods to store this information, such as in a TNSNAMES.ORA (TNSNAMES) file, Oracle Internet Directory (OID - LDAP), Oracle Names (ONAMES) or using the Host Naming Adapter.

The default connect descriptor lookup path is to first look in the local naming file TNSNAMES.ORA, then to try the well-known Oracle Names servers, and then finally to try the Host Naming Adapter. The parameter that influences this lookup order is NAMES.DIRECTORY_PATH parameter in the SQLNET.ORA file.

-- To implement the solution, Update the sqlnet.ora file in the Discoverer ORACLE_HOME from :

NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT, ONAMES, HOSTNAME)

to

NAMES.DIRECTORY_PATH= (TNSNAMES)

if the connect descriptor is configured to be resolved via tnsnames.ora, otherwise order the list with the right connect descriptor which is used first.

2 comments:

Naga Shankar said...

Hi Sir,

thanks for a really good post .

i am using the Discoverer 11g(11.1.1.2) version and we are having a similar kind of issue. we have 25gb of physical memory and when can only run 500 discoverer viewer sessions . in EM we see that when 500 is hit the memory is at 99.70+ after that who ever login ,they get the viewer is busy page . please let us know if it is a bug or something . or can we increase the memory consumption of the Discoverer viewer/plus .

we really appreciate your quick responce .

thanks
naga

soahib said...

Can you please let us know the fix for the issue encountered on 11g discoverer.

any solution will be highly appreciated.