The following tables describe the available hook operations for dSources and VDBs managed through DCT on connected CD engines. Where hooks execute depends on the object type and ingestion model — see Hook operations for details.
dSource hook operations
|
Hook |
Description |
|---|---|
|
Pre-sync |
Executed before the SnapSync operation of a dSource. Can quiesce data for capture during SnapSync or stop application processes that may interfere with SnapSync. |
|
Post-sync |
Executed after the SnapSync operation of a dSource. Undoes changes made by pre-sync hooks. Runs regardless of the success of pre-sync hooks or SnapSync. |
VDB hook operations
|
Hook |
Description |
|---|---|
|
Configure clone |
Runs after initial provision or after a refresh, once the VDB has started. During a refresh, this hook precedes the post-refresh hook. |
|
Pre-refresh |
Runs before a refresh, before the VDB is stopped. Can cache data from the VDB for restoration after the refresh. |
|
Post-refresh |
Runs after a refresh, after the VDB has started and after configure clone. Will not run if the refresh or pre-refresh hook fails. Can restore cached data after refresh completion. |
|
Pre-rollback |
Runs before a rollback (rewind), before the VDB is stopped. Can cache data from the VDB for restoration after rewind. |
|
Post-rollback |
Runs after a rollback (rewind), after the VDB has started. Will not run if the rewind or pre-rewind hook fails. Can restore cached data after rewind completion. |
|
Pre-snapshot |
Runs before a snapshot. Can quiesce data for capture or stop processes that may interfere with the snapshot. |
|
Post-snapshot |
Runs after a snapshot. Runs regardless of the success of the snapshot or pre-snapshot hook. Can undo changes made by the pre-snapshot hook. |
|
Pre-start |
Runs before the startup of a VDB. Can initialize configuration files or stop processes that might interfere with the VDB. |
|
Post-start |
Runs after the startup of a VDB. Can clean up temporary files, restart processes stopped by pre-start hooks, or log notifications. |
|
Pre-stop |
Runs before the shutdown of a VDB. Can quiesce data or processes prior to the VDB shutdown. |
|
Post-stop |
Runs after the shutdown of a VDB. Can log notifications, clean up temporary files, or manage related processes. |
Order of execution of hooks for VDB operations
The table below shows which hooks run during each VDB operation, listed in execution order from top to bottom.
|
Provision |
Refresh |
Rollback |
Snapshot |
Start |
Stop |
|---|---|---|---|---|---|
|
Pre-start |
Pre-refresh |
Pre-rollback |
Pre-snapshot |
Pre-start |
Pre-stop |
|
Post-start |
Pre-stop |
Pre-stop |
Post-snapshot |
Post-start |
Post-stop |
|
Configure clone |
Post-stop |
Post-stop |
|
|
|
|
Run masking job |
Pre-start |
Pre-start |
|
|
|
|
Pre-snapshot |
Post-start |
Post-start |
|
|
|
|
Post-snapshot |
Configure clone |
Configure clone |
|
|
|
|
|
Run masking job |
Run masking job |
|
|
|
|
|
Post-refresh |
Post-rollback |
|
|
|
|
|
Pre-snapshot |
Pre-snapshot |
|
|
|
|
|
Post-snapshot |
Post-snapshot |
|
|
|
Staging server hooks
Staging server hooks are connector-specific and execute on the configured staging server. These are currently applicable to SAP ASE.
|
Hook |
Description |
|---|---|
|
Pre validated sync |
Runs on the staging server before a validated sync operation. |
|
Post validated sync |
Runs on the staging server after a validated sync operation. |