My Oracle Support Banner

Suddently Portal Logins Fail And/Or Portal Hangs / When Portal Users Login, OID Is Generating 16 Database Connections For Each User Login (Doc ID 965589.1)

Last updated on AUGUST 27, 2019

Applies to:

Oracle Internet Directory - Version 10.1.2 and later
Information in this document applies to any platform.


Problem description:
Suddently, at times users are authenticated ok and other times an error displayed in the browser.  The symptoms match <Note 461237.1> (Portal Performance Slows Down as User Load Increases - Users Start Getting Internal Server Error and Eventually Portal Hangs), but OID tuning/suggestions therein have already been applied to OID.

After more testing, found out that whenever any user signs on to the Portal page, the Portal server runs its procedure 'portal.wwsec_app_priv.process_signon' on the database normally, but then the OID server generates sixteen (16) database connections, all running the same sql, for example:

SELECT AttrValue FROM ct_uniquemember WHERE EntryID = :entryID AND ATTRTYPE = 'dgr'

(Note: The attribute type 'dgr' is related to dynamic groups.)

Oracle Internet Directory (OID) 10.1.4 with Oracle Access Manager (OAM) and Portal integration on separate, all-virtual servers.

Existing static groups are small / have only a few members, but using several large and/or nested dynamic groups, i.e. with 50-7000+ members each. (The total potential number of users can be around 90k+.)

As per recommendations in <Note 458703.1>, OID server has already been tuned with orclserverprocs set to 4 and orclmaxcc set to 10.  Also, already ran oidstats.sql and applied the bitmap index for large groups (which is not necessary as this index applies to large static groups only and does not affect dynamic groups performance).

Also tried applying OAM related tuning to OID, but after further testing found that OAM does not play a role in the problem at all.  Further, OAM ldap objects are not stored in OID, but rather are accessed via OVD from a Sun ldap server, which syncs to OID, but none of the OAM objectclasses/attributes are sync'd to OID, therefore OID tuning for OAM is not necessary in this environment either.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.