DBMS_SCHEDULER Job Does Not Run When Job Name Preceding It Is Mixed Case
(Doc ID 1254604.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.1 [Release 10.1 to 11.2]Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and environment data used
represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered
with an Oracle database product or other training material. Any similarity to actual environments,
actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
You create a DBMS_SCHEDULER job whose job name is in mixed case.
Changes
An examination of USER_SCHEDULER_JOB_RUN_DETAILS shows that job Job_Num_1 completed successfully. You wait a while longer to see the results of Job_Num_2, yet it never executes.
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 |