"SET ROLE" Under High Concurrency Causes More "latch: row cache objects" and Slower Response Times
(Doc ID 2310611.1)
Last updated on MARCH 09, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
"SET ROLE" under high concurrency causes more "latch: row cache objects" and which is leading to delay in user response time. After further testing found that starting 184.108.40.206, "SET ROLE" statement is performing slow.
Installing patch for known Bug 23575520 and increasing SGA doesn't help.
If we just execute the same "SET ROLE" statement in single session, then no issues.
From testing with 300 concurrent sessions executing SET ROLE statement with 100 roles (roles are empty with no privileges granted to them) listed in it takes following time across various
versions, starting 220.127.116.11 we see high number of 'latch: row cache objects':
Version Time (10046 Trace)
18.104.22.168 17.11 Sec
22.214.171.124 85.33 Sec
126.96.36.199 84.26 Sec
Upgrading database from 188.8.131.52 to 184.108.40.206.
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