Oracle Access Manager 11g R2PS3 (OAM 18.104.22.168): Is Truncating oam_session And oam_session_attributes Table Supported?
(Doc ID 2461701.1)
Last updated on OCTOBER 18, 2019
Applies to:Oracle Access Manager - Version 22.214.171.124.180417 and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Due to amount of load the oam_session and oam_session_attributes table has grown to a very large size. We have enabled hash partitioning for oam_session_attributes table. Due to excessive growth of these tables. We want to truncate them during a maintenance window. The purge script provided with RCU will take hours and might not complete in maintenance window time.
Is truncating oam_session and oam_session_attributes table supported? Is there any specific requirement that needs to be taken care of before truncating or after truncating these tables?
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