1Z0-062 · Question #224
You want to schedule a job to rebuild atable's indexes after a bulk insert, which must be scheduled as soon as a file containing data arrives on the system. What would you do to accomplish this?
The correct answer is A. Create a file watcher and an event-based job for bulk insert and then create another job to. Automating a file-arrival-triggered bulk insert followed by an index rebuild requires a file watcher, an event-based job for the insert, and a chained dependent job for the rebuild.
Question
You want to schedule a job to rebuild atable's indexes after a bulk insert, which must be scheduled as soon as a file containing data arrives on the system. What would you do to accomplish this?
Options
- ACreate a file watcher and an event-based job for bulk insert and then create another job to
- BCreate a file watcher for the bulk inserts and then create a job to rebuild indexes.
- CCreate a job array and add a job for bulk insert and a job to rebuild indexes to the job array.
- DCreate an event-based job for the filearrival event, then create a job for bulk insert, and then
How the community answered
(21 responses)- A71% (15)
- B10% (2)
- C14% (3)
- D5% (1)
Why each option
Automating a file-arrival-triggered bulk insert followed by an index rebuild requires a file watcher, an event-based job for the insert, and a chained dependent job for the rebuild.
A file watcher detects the incoming file and raises an arrival event; an event-based job subscribes to that event to execute the bulk insert; a second dependent job then rebuilds the indexes - this three-component design ensures correct sequencing and full end-to-end automation.
Creating only a file watcher and an index-rebuild job omits the event-based job that performs the bulk insert upon file arrival, leaving the bulk insert step unscheduled.
Job arrays group jobs for batch processing but do not support event-based triggering on file arrival and do not enforce sequential dependency between the bulk insert and the index rebuild.
This option is truncated and incomplete, and does not describe a valid end-to-end solution that handles file arrival, bulk insert, and index rebuild in the correct sequence.
Concept tested: Oracle Scheduler file watcher and event-based job chaining
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/oracle-scheduler-concepts.html
Topics
Community Discussion
No community discussion yet for this question.