Asynchronous execution

By default, job execution in dct-toolkit is synchronous, and the dct-toolkit command waits for the job to complete or fail. To exit the command without waiting for job completion, add the --no-wait option.

$ dct-toolkit refresh_vdb_from_bookmark vdb_id=2-ORACLE_DB_CONTAINER-4 \
  bookmark_id=a5de7eb7dcfe442dbcb667287c8c8d94 --no-wait
---
job:
  id: "ef73afd4bd86471db702703147d846ec"
  status: "STARTED"
  is_waiting_for_telemetry: false
  type: "VDB_REFRESH"
  localized_type: "VDB Refresh"
  target_id: "2-ORACLE_DB_CONTAINER-4"
  target_name: "vpdb01"
  start_time: "2025-02-10T09:11:10.225631Z"
  ...

You can then use the returned job ID with get_job_by_id to check status.

$ dct-toolkit get_job_by_id job_id=ef73afd4bd86471db702703147d846ec
---
id: "ef73afd4bd86471db702703147d846ec"
status: "STARTED"
is_waiting_for_telemetry: false
type: "VDB_REFRESH"
localized_type: "VDB Refresh"
target_id: "2-ORACLE_DB_CONTAINER-4"
target_name: "vpdb01"
percent_complete: 47
...

Because get_job_by_id includes sub-job status information from the engine, scripts typically narrow the output to the DCT job status only and use that value to determine the next action.