Oracle Access Manager (OAM) After Daylight Savings Time In the Database "ORA-01878: specified field not found in datetime or interval ... CALL AMSESSION_USERLOCK_V2_PURGE"
(Doc ID 2886074.1)
Last updated on SEPTEMBER 16, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Access Manager (OAM) After Daylight Savings Time In the Database " ORA-01878: specified field not found in datetime or interval ... CALL AMSESSION_USERLOCK_V2_PURGE"
- The following error was noticed after Day light saving hours.
- The number of partitions are growing rapidly in database. Partitions are not removed like prior to DST.
- Session partitioning in place using SmePartitionedTableScript.sql and instructions from Oracle Access Manager (OAM) Intermittent Issue After Authentication The Protected Resource/Application Fails To Load "OAM System Error" (Doc ID 2633078.1)
- No purging happened from 03/13/2022 2:00 am onward.
- Above exception appear in OAM server logs at certain specific intervals.
- OAM Server and OAM DB are in the same time zone
- OAM BP level, Jan-2022 BP Patch 33751903; 12.2.1.4.220113 (BP09)
- Java version on OAM = java version "1.8.0_311" -Java version on RAC Super cluster (database version 19.6) . DB is using JDK "1.8.0_271"
Changes
Daylight Savings Time - Day light savings clock rolled from 2:00 AM on Sunday, March 13 to 3:00 AM.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |