Oracle Access Manager (OAM) Executes Massive Amount Of Database Queries For Each User Session
(Doc ID 2835028.1)
Last updated on SEPTEMBER 11, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.4.210607 and later Information in this document applies to any platform.
Symptoms
Migrating from Oracle Access Manager (OAM) 11.1.2.3 with Coherence session management to Oracle Access Manager (OAM) 12c which uses database for session management.
Performance is terrible
OAM currently is executing approx. 333 database executes for each user login/logout flow, including authorization of ~35 web resources for each user cycle.
Each query is in itself very rapidly executed, but they quickly sum up to an amount that database cannot deliver and the performance
Database has got 4x CPU capacity, currently at 16 CPU but at no big difference. With 12c, reached 28 flows/sec.
OAM is heavily loaded but most of all, the Database hits its maximum capacity.
OAM 12c topology
4 parallel Apache instances handled by 8 managed OAM servers having 8 CPU cores each.
OID as user store and a database with 4 CPU cores and 64 GB RAM (but currently 16 cores in OAM 12c test env). For all use cases and environments,
all authentication tasks is handled by SAML2 federation.