DBMS Schedule Affected After Time Zone Enabled In Application
(Doc ID 2899048.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Financial Services Revenue Management and Billing Cloud Service - Version NA and laterInformation in this document applies to any platform.
Symptoms
On RMB v2.7.0.1 against FW 4.3.0.6, DBMS batch job schedule is affected and practically impossible to use.
The issue occurs when there is difference in time zone. When application enabled time zone and DB time zone are same, this issue would not come at first place. So changing DB time zone would not be a feasible solution. There is no impact with Framework property setup for "setInstallationTimeZone" property to update timezone for Application & Scheduler. Even after creating new program, schedule and job, there is no difference with the impact.
ACTUAL BEHAVIOR
----------------------------
DBMS schedule is affected after time zone enabled in application.
EXPECTED BEHAVIOR
---------------------------------
Time Zone update should not impact DBMS Schedule.
The property "ouaf.database.session.setInstallationTimeZone" also does not work for the online batch job submission if installation option timezone is ahead of the Application/DB server timezone. For example the installation option time zone is Australia(AUT) and the application/DB server is India (IST). So this needs a fix for online job submission as well as via DBMS scheduler.
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 |
| Cause |
| Solution |
| References |