Valid For
Replicat
Description
Use the REPFETCHEDCOLOPTIONS parameter to determine how Replicat responds to operations for which a fetch from the source database was required. The Extract process fetches column data when the transaction record does not contain enough information to construct a SQL statement or when a FETCHCOLS clause is used. See "{FETCHCOLS | FETCHCOLSEXCEPT} (column_list)" for more information.
Default
None
Syntax
REPFETCHEDCOLOPTIONS
[, INCONSISTENTROW ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, LATESTROWVERSION ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, MISSINGROW ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, NOFETCH ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, REDUNDANTROW ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, SNAPSHOTROW ALLOW|IGNORE|REPORT|DISCARD|ABEND]
[, SETIFMISSING string]
INCONSISTENTROWDetermines the action to perform when column data was successfully fetched by row ID, but the key did not match. Either the row ID was recycled or a primary key update occurred after this operation (and prior to the fetch). Valid values are
LATESTROWVERSION actionProvides a response when column data was fetched from the current row in the table. Valid values are:
NOFETCH actionPrevents fetching. One use for this option is when the database is a standby and Oracle GoldenGate does not have a database connection. In this case, an attempt to fetch from the database would result an error. Other scenarios may warrant the use of this parameter as well.
When Oracle GoldenGate cannot fetch data it normally would fetch, it probably will cause data integrity issues on the target.
The following are valid actions that can be taken when a NOFETCH is encountered:
ABENDWrite the operation to the discard file and abend the Replicat process. This is the default.
ALLOWProcess the operation unless the record length is zero (0).
IGNOREIgnore the operation. If fetch statistics are being reported in the process report (based on STATOPTIONS settings) they will be updated with this result.
REPORTWrite the record to the discard file and process the operation.
DISCARDWrite the record to the discard file, but do not process the operation. If fetch statistics are being reported in the process report (based on STATOPTIONS settings) they will be updated with this result.
MISSINGROW actionProvides a response when only part of a row (the changed values) is available to Replicat for processing. The column data that is missing from the trail typically could not be fetched because the row was deleted between the time the change record was created and when the fetch was triggered, or because the row image required was older than the undo retention specification.
Valid values are:
REDUNDANTROWIndicates that column data was not fetched because column data was previously fetched for this record.
SETIFMISSING [string]Provides a value when a fetch was unsuccessful (and the value is missing from the trail record) but the target column has a not-null constraint. It takes an optional ASCII string as a value for CHAR and BINARY data types or defaults to the following.
CHAR, VARCHAR: Single space
BINARY, VARBINARY: A NULL byte
TIMESTAMP: Current date/time
FLOAT, INTEGER: Zero
Besides SETIFMISSING, you can use the COLMAP clause of the MAP statement to map a value for the target column. See "COLMAP (column_mapping)" for more information.
SNAPSHOTROWIndicates that column data was fetched from a snapshot. Generally, this option would only be used for reporting or discarding operations. Valid values are: