1. Understanding Scheduled Processes
  2. Unlock Scheduled Process that Incrementally Loads SR Audit Data

Unlock Scheduled Process that Incrementally Loads SR Audit Data

Use the Unlock Scheduled Process that Incrementally Loads SR Audit Data process to remove the process lock created by the Execute Incremental Load of SR Audit Data for ReportingLoads Service Request Lifecycle Data scheduled process if there's is no instance of that scheduled process running, but you'reyou are unable to start a new instance.

Removes the process lock created by the Loads Service Request Lifecycle Data process when that process fails to remove its lock automatically.

When to Use

The process should only be run if the scheduled Loads Service Request Lifecycle Data process is unable to start and no other instance of the process is currently running. It should not be run under any other circumstance.

It should only be necessary to run this process if the Loads Service Request Lifecycle Data process is aborted (either manually or through some unexpected system event, such as a server crash) and doesn’t get a chance to clean up before exiting.

Privileges Required

Verify that you have the following roles or privilege:

  • To administer the job, one of the following roles are required with delete, execute, read and update:

    • ORA_SVC_HELPDESK_ADMINISTRATION

    • ORA_SVC_SR_ADMINISTRATOR

  • To schedule the job, the following privilege is required:

    • SVC_SCHEDULE_SERVICE_JOBS_PRIV

Before You Start

Review the following before scheduling this on demand process:

  • Don't run this process if the Loads Service Request Lifecycle Data process is currently running.

  • Execution Time:

    • The execution time is less than 2 seconds.

  • Compatibility:

    • No other processes are triggered when this job runs.

    • No potential impact on the server performance while this job is running.

    • There can be only one instance of the job running at any one time.

    • There are no issues with business processes executing in parallel with this job.

    • This scheduled process is incompatible with itself; therefore, only one instance of the job should be running at any particular time.

Parameters

None.

Troubleshooting Information

Use this information to troubleshoot the scheduled process.

  • Notification of job completion would be using the standard scheduled process job notification system.

  • If the scheduled job doesn't run successfully, it should be submitted again.

  • This scheduled process is idempotent, and no cleanup activity is required if the job fails.

  • To verify that this scheduled process has been successful, schedule the Loads Service Request Lifecycle Data process and confirm it is successfully able to load data.