Events
Oracle Cloud Infrastructure Database Migration service emits events in Oracle Cloud Infrastructure (OCI), which are structured messages that indicate state changes in resources.
You can define rules in the OCI Event Service to get notified of events happening in an OCI native service and use the Notification Service (ONS) to send notifications or trigger events.
Table 11-3 Database Migration Service Event Types
| Resource | Attributes (Common for Object) | Event name | Notes |
|---|---|---|---|
| Migration |
|
Migration Clone Begin | When a migration clone request is received. |
| Migration Clone End | When a migration clone request is completed. | ||
| Migration Create Begin | When a migration create request is received. | ||
| Migration Create End | When a migration create request is completed. | ||
| Migration Delete Begin | When a migration delete request is received. | ||
| Migration Delete End | When a migration delete request is completed. | ||
| Migration Evaluate Begin | When a migration evaluate request is received. | ||
| Migration Evaluate End | When a migration evaluate request is completed. | ||
| Migration Start Begin | When a migration start request is received. | ||
| Migration Start End | When a migration start request is completed. | ||
| Migration State Change | When a migration state change request is received. | ||
| Migration Update Begin | When a migration update request is received. | ||
| Migration Update End | When a migration update request is completed. | ||
| Job |
compartmentId compartmentName resourceName resourceIdavailabilityDomain eventID |
Job Abort Begin |
When a job abort request is received. |
|
Job Abort End |
When a job is aborted. | ||
|
Job Delete Begin |
When a job delete request is received. | ||
|
Job Delete End |
When a job is deleted. | ||
|
Job Resume Begin |
When a job resume request is received. | ||
|
Job Resume End |
When a job resume is completed. | ||
|
Job State Changed |
When a job state is changed. | ||
|
Job State Failed |
When a job fails. | ||
|
Job State Successful |
When a job state is successful. | ||
|
Job State Waiting |
When a job update request is in waiting state. | ||
|
Job Update Begin |
Called when the state of job is changed. | ||
|
Job Update End |
When a job update request is completed. | ||
| Connection |
|
Connection Create
Begin |
When a connection create request is sent. |
|
Connection Create End |
When a connection create request is completed. | ||
| Connection Delete Begin | When a connection delete request is sent. | ||
| Connection Delete End | When a connection delete request is complete. | ||
|
Connection Update Begin |
When a connection update request is sent. | ||
|
Connection Update End |
When a connection update request is completed. | ||
| Phase |
compartmentName compartmentId migrationName migrationId jobName jobId phaseName phaseStatus |
Phase Begin | Emitted when the phase starts. |
| Phase End | Emitted when the phase ends. |
Table 11-4 Example Use Cases
| Use case | Event | Attribute filters | Action |
|---|---|---|---|
| To start a process when Migration XYZ is started | Migration - Start | migrationName=XYZ | Function or Streaming |
To start a function for a given job after the Data Pump file is uploaded and before import starts (You must also configure a pause after phase ZDM_UPLOAD_DATAPUMP_DUMP_FILES, and the function must call the API to resume the job)
|
Job - State Change |
jobId=job_OCID jobLifecycleState=PAUSED phaseName=ZDM_UPLOAD_DATAPUMP_DUMP_FILES |
Function |
| To send a notification whenever a Migration in my compartment is failing | Job - State Change | compartmentId=myCompartmentIdmigrationLifecycleState=FAILED | Notification |
| To send a notification when Migration XYZ starts waiting on replication | Job - State Change |
migrationName=XYZ jobLifecycleState=PAUSED phaseName=ZDM_MONITOR_GG_LAG |
Notification |
| To send a notification when Migration XYZ starts Data Pump export | Phase - Begin |
migrationName=XYZ phaseName=ZDM_DATAPUMP_EXPORT |
Notification |
For information about the migration job phases, see Oracle migration phases.
Parent topic: Reference