jcs.add_job_wait_event

on-site-related topic PL/SQL API jcs.add_job_wait_event

Summary

Make a job wait on an additional event.

Privileges

the caller must be able to see the job. If the job is owned by the user, the user must have the ADD_JOB_WAIT_EVENT system privilege. If the job is owned by someone else, the user must have the ADD_ANY_JOB_WAIT_EVENT system privilege and UPDATE privilege on the job's Queue.

Specification

Copy 
procedure add_job_wait_event(job_id in number,
event_name in varchar2,
clears_event in boolean default false,
can_commit in boolean default false,
event_partition in varchar2 default null)

Used with languages that support the boolean datatype.

Parameters

  • job_id - the ID of the job
  • event_name - the name of the event to wait for
  • clears_event - is the event cleared immediately when this job receives the raised event?
  • can_commit - should this be committed immediately?
  • event_partition - the Partition of the event to wait for If it is not filled in the default Partition is assumed

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

can_commit_autonomous

Specification

Copy 
procedure add_job_wait_event(job_id in number,
event_name in varchar2,
clears_event in varchar2,
can_commit in varchar2,
event_partition in varchar2 default null)

Used with languages that do not support the boolean datatype; clears_event and can_commit are passed as const.jcs_yes or const.jcs_no.

Parameters

  • job_id - the ID of the job
  • event_name - the name of the event to wait for
  • clears_event - is the event cleared immediately when this job receives the raised event?
  • can_commit - should this be committed immediately?
  • event_partition - the Partition of the event to wait for If it is not filled in the default Partition is assumed

Specification

Copy 
procedure add_job_wait_event(script in varchar2,
event_name in varchar2,
clears_event in boolean default false,
event_partition in varchar2 default null)

Parameters

  • script - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
  • event_name - the name of the event to wait for
  • clears_event - is the event cleared immediately when this job receives the raised event?
  • event_partition - the Partition of the event to wait for If it is not filled in the default Partition is assumed

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

database_modified