Results for “user_export”

12 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SYS.DBMS_JOB is the legacy Oracle-supplied PL/SQL package that provides the programmatic interface for scheduling, modifying, and monitoring database jobs executed by the job queue background processes (JQ0–JQ9, and later CJQ0). Within Oracle E-Business Suite 12.1.1 and 12.2.2, it serves as the underlying scheduling mechanism for a large number of EBS concurrent programs, managers, and maintenance routines that require autonomous, time-driven execution rather than on-demand submission by a user. Because the package resides in the SYS schema, it is not owned or supported by the EBS application schema itself; EBS merely consumes its documented capabilities. The ETRM classification of this object as OTHER reflects that it is a database kernel utility rather than an EBS Application Object Library API, and it is referenced by nine other packages in the ETRM inventory, confirming its wide internal dependency footprint. The source listed in ETRM is delivered wrapped, which is consistent with Oracle's policy of shipping this package in obfuscated form.

Key Procedures and Functions

The documented interface comprises fourteen procedures and functions that together cover the full job lifecycle:

  • SUBMIT — Creates a new job, returning the job number assigned by the database, and schedules it for its first execution.
  • ISUBMIT — Creates a new job with a caller-specified job number rather than a system-generated one, useful when deterministic identifiers are required.
  • REMOVE — Deletes an existing job from the job queue.
  • CHANGE — Modifies an existing job's definition, such as its PL/SQL block, next execution date, or interval.
  • WHAT — Returns the PL/SQL block or procedure call that a job is configured to execute.
  • NEXT_DATE — Returns or alters the next scheduled execution date of a job.
  • INSTANCE — Returns or alters the instance number on which the job is permitted to run, which is significant in Real Application Clusters deployments.
  • INTERVAL — Returns or alters the date expression used to compute the next run date after each execution.
  • BROKEN — Marks a job as broken or non-broken, controlling whether the job queue will attempt further executions.
  • RUN — Forces immediate execution of a job, outside of its normal schedule.
  • USER_EXPORT — Generates the call text required to recreate a job, supporting export and migration scenarios.
  • BACKGROUND_PROCESS — Reports the number of job queue background processes configured, or communicates the result of such a query.
  • IS_JOBQ — Identifies whether the current session is itself a job queue process, allowing callers to behave differently under job queue execution.

Tables Accessed

In a standard Oracle database, DBMS_JOB manipulates the data dictionary views and base tables that underlie the job queue, principally the job definition and job log structures exposed through DBA_JOBS, USER_JOBS, DBA_JOBS_RUNNING, and their ALL_ equivalents. These tables store the job identifier, the PL/SQL body to be executed, the next date, the interval expression, the instance affinity, the broken flag, and execution history. In EBS, access to these objects is normally mediated through the SYS-owned package rather than by direct DML against the dictionary, and the ETRM record does not document any APPS synonyms or application tables referenced directly by this package.

Usage Notes

DBMS_JOB is typically invoked from custom PL/SQL or from database-side stub code rather than from an EBS form, since scheduling is normally initiated by background processes. In EBS 12.1.1 and 12.2.2, the recommended replacement is DBMS_SCHEDULER, and Oracle has long advised migrating job definitions accordingly. Nevertheless, DBMS_JOB remains in use for numerous legacy EBS maintenance and purge routines. The presence of IS_JOBQ and BACKGROUND_PROCESS in the documented interface means integrators commonly check job queue context before running heavy work, and the BROKEN procedure is frequently used to suppress persistently failing jobs during patching or troubleshooting. Because the package is wrapped, EXECUTE privileges and careful testing are essential when altering job definitions.