Chain Job (Allow_Runs_In_Restricted_Mode set to TRUE) Hangs While Executed In Restricted Session.
(Doc ID 1931174.1)
Last updated on JANUARY 07, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Chain job not working properly when setting 'ALLOW_RUNS_IN_RESTRICTED_MODE' attribute for this job .
A regular job with ALLOW_RUNS_IN_RESTRICTED_MODE = TRUE works fine in restricted mode.
The job starts, but when it gets to the first program in the chain, it just hang.
Changes
Restart the instance in restricted session mode (startup restrict).
As per documentation
" allow_runs_in_restricted_mode : If TRUE, the job is permitted to run when the database is in restricted mode, provided that the job owner is permitted to log in during this mode."
Check the status of "allow_runs_in_restricted_mode" using the following query :
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 |