My Oracle Support Banner

DBMS_SCHEDULER ALLOW_RUNS_IN_RESTRICTED_MODE Attribute Does Not Work (Doc ID 968794.1)

Last updated on AUGUST 24, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.1 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Symptoms

Prior to 11g running jobs (either via dbms_scheduler or dbms_jobs) in restricted mode was not possible because an instance started in Restrict Session mode will not allow any secondary process such as job processes to start.

See <Note.313102.1> "Jobs Not Executing Automatically".

In 11g a new feature was introduced to allow jobs to run in restricted session by setting "ALLOW_RUNS_IN_RESTRICTED_MODE" attribute for the job. This was introduced via Enhancement <Bug 5921319>.

So with "ALLOW_RUNS_IN_RESTRICTED_MODE" set, a job should be able to run while instance is in restricted mode.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.