2026-08-31 · run 2026-08-31-oracle-datapump-port

Oracle Data Pump port (snapshot/restore)

What was done

Ported bin/snapshot.sh and bin/restore.sh to Oracle using Data Pump (expdp/impdp), closing the last engine for the snapshot/restore tooling.

The port

• snapshot.sh (oracle) — exports as SYSTEM (ORACLE_PASSWORD) because the schema owner carries only DB_DEVELOPER_ROLE and cannot read the DATA_PUMP_DIR directory object. expdp SCHEMAS=keycloak writes the dump into a GUID-named subdirectory of DATA_PUMP_DIR inside the container; the script locates it (find /opt/oracle/admin) and docker compose cp's it out to snapshots/<name>.dump.
• restore.sh (oracle) — DROP USER keycloak CASCADE, recreate it exactly as the gvenzl image does (DB_DEVELOPER_ROLE, USERS tablespace), copy the dump back in, then impdp SCHEMAS=keycloak EXCLUDE=USER TABLE_EXISTS_ACTION=REPLACE. EXCLUDE=USER avoids the benign ORA-31684 user already exists (the user is pre-created so the password/grants survive, which a SCHEMA-only dump does not carry). An Oracle model_version (read keycloak.migration_model via SYSTEM) preserves the no-re-migration gate.

Result

./bin/snapshot.sh baseline-oracle-test    -> snapshots/baseline-oracle-test.dump (4.8M)
./bin/restore.sh baseline-oracle-test
  ==> restored schema reports model 26.7.3
  ==> ready
  ==> restored baseline-oracle-test — running 26.7.3, schema 26.7.3, no re-migration

Schema intact after restore: 100 tables, migration_model 26.7.3, 1 user.

Remaining Oracle item

• S4 DML-only — untested; a non-owner user needs synonyms under the user-is-schema model.