Using EXIT_CALL_TYPE
Use EXIT_CALL_TYPE
to indicate when, during processing, the Extract or Replicat process (the caller) calls a user exit routine. A process can call a routine with the following calls.
Table 3-1 User Exit Calls
Call type | Processing point |
---|---|
|
Valid when the |
|
Called just before either of the following:
|
|
Called just before an Extract or Replicat checkpoint is written. |
|
Called during Extract processing before an ASCII input record is written to the discard file. The associated ASCII buffer can be retrieved and manipulated by the user exit using callback routines. This call type is not applicable for use with the Replicat process. |
|
Called during Replicat processing before a record is written to the discard file. Records can be discarded for several reasons, such as when a value in the Oracle GoldenGate change record is different from the current version in the target table.The associated discard buffer can be retrieved and manipulated by the user exit using callback routines. This call type is not applicable for use with the Extract process. |
|
Called just after either of the following:
|
|
Called during Extract or Replicat processing just before Oracle GoldenGate terminates after a fatal error. |
|
Called during Replicat processing when a marker from a NonStop server is read from the trail, and before writing to the marker history file. |
|
This call is the basis of most user exit processing. When |
|
Called at the start of processing. The user exit can perform initialization work, such as opening files and initializing variables. |
|
Called before the process stops gracefully or ends abnormally. The user exit can perform completion work, such as closing files or outputting totals. |
|
Set by the user exit routines to instruct the caller how to respond when each exit call completes. |
Parent topic: User Exit Functions