Database endpoints
Check a schema migration
Check the state and progress of one online schema migration.
GET /v1/tenants/{tenant}/migrations/{id}
- Keep the migration IDUse the ID returned when changes were submitted.
- Read state and progressInspect row and chunk copying work.
- Choose the next operationCut over or investigate according to the reported state.
Before you start
Use your database bearer token.
Use the ID returned by Start a schema migration. Check its state before cutover or abort.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
id | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
Read state before taking action. Row and chunk progress show copying work; CutoverPending still needs the cutover step. Use this endpoint to track the ID returned at submission.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 429 | Honor Retry-After when present; back off. |
| 503 | Honor Retry-After when present; check write outcomes. |