Specify When to Run Global Extract Jobs

You can set up and monitor once-only or regular data extract jobs – for example, once per day at midnight – for Business Intelligence data from an Oracle Applications Cloud data source in the Manage Extract Schedules dialog box.

Click the Manage Extract Schedules button in the panel tab and select the Manage Extract Schedules link to open the dialog box.

Field Name How to Use
Schedules This list shows schedules submitted in the last 24 hours. Use the Add option to set up once-only or regular data extract. Use the Delete Schedule option to delete the currently selected schedule. Click a schedule's name to preview or edit its details. In the Shedule Details, click the Edit option to update the details of the currently selected schedule. Use the Switch to BI Broker Extract option to apply BI Broker mode to the schedule. This changes the extract mode of all the data stores in the schedule.
Note: When you change a schedule to BI Broker mode, all of its data stores use that mode. This allows you to set the mode for multiple data stores, but BICC won't validate the mode using this option. The implementer has to validate the status after the schedule is updated. BI Broker mode doesn't support all data stores. It's strongly recommended that you set the mode at the the data store level and test before implementing the mode for all data stores in a schedule.

It’s recommended that you periodically purge the Schedules list, as not all completed schedules are shown. To do this, use the Delete Inactive Schedules option.

Schedule Requests This list shows the details of data extract processes for the Schedule that's currently selected in the Schedules list. A new row is created in the table every time an Cloud extract request is processed. Use the Delete option to delete the details of the currently selected request. If you delete a schedule job from this list, it doesn't remove the BI Cloud data that's been extracted and loaded by that job.

Monitor a Cloud Extract

In the Schedules dialog, click Actions and select the option for the last run corresponding to the job type, Cloud Data Extract or Deleted Record Extract. Each job type displays in its own dialog, which lists the last cloud extract or deleted record extract status of each VO with status of SUCCESS or FAILURE for each data store and error messages in the case of failures. The ESS Request Id column displays the job for which the VO extraction last ran.

Scheduled jobs also write logs that can be used to review issues causing errors or shared with Oracle Support to resolve a service request. To download logs, click Help and select Download Logs.

For scheduled jobs, whether successful or not, an extraction status file in JSON format is uploaded to external storage. The files have a default expiration date, and have the following file name format, depending on job type:
  • Cloud Data Extracts:EXTRACT_STATUS_DATA_SCHEDULE_<Schedule Id>_REQUEST_<request_id>.JSON

  • Deleted Record Extracts:EXTRACT_STATUS_DELETED_SCHEDULE_<Schedule Id>_REQUEST_<request_id>.JSON

Column Content
Name VO name
status VO extract status
errorMessage If extract failed, any resulting error status
runDate Run date of the extract of the VO
queryDurationInSec Time the query took to run, in seconds
extractDurationInSec Time the extract of the query results took, in seconds
uploadDurationInSec Time the upload to external storage took, in seconds
totalDurationInSec Total duration of the job
rowCount Number of rows extracted