ALL_APPLY_ERROR_MESSAGES

ALL_APPLY_ERROR_MESSAGES displays information about the individual messages in an error transaction generated by the apply processes that dequeue messages from queues accessible to the current user.

For XStream inbound servers, each message in an error transaction is a logical change record (LCR).

Note:

DBA_APPLY_ERROR_MESSAGES displays information about the individual messages in all of the error transactions generated by all apply processes in the database.

Column Datatype NULL Description
MESSAGE_ID RAW(16)   Unique identifier of the message stored in the error queue
LOCAL_TRANSACTION_ID VARCHAR2(22)   Local transaction ID for the error transaction
TRANSACTION_MESSAGE_NUMBER NUMBER   Message number of the message that raised the error. The message number is a sequence number for the messages in the transaction, starting with 1.
ERROR_NUMBER NUMBER   Error number of the error raised by the transaction. The error number is populated only for the LCR that raised the error. This field is NULL for the other LCRs in the transaction.
ERROR_MESSAGE VARCHAR2(4000)   Error message of the error raised by the transaction. The error message is populated only for the LCR that raised the error. This field is NULL for the other LCRs in the transaction.
SOURCE_OBJECT_OWNER VARCHAR2(128)   Owner of the object at the source database
SOURCE_OBJECT_NAME VARCHAR2(128)   Name of the object at the source database
OBJECT_OWNER VARCHAR2(128)   Owner of the target table
OBJECT_NAME VARCHAR2(128)   Object name of the target table
PRIMARY_KEY VARCHAR2(4000)   Primary key of the table row that caused the source transaction to fail at the target
POSITION RAW(64)   The LCR position
OPERATION VARCHAR2(100)   The DML or DDL operation represented in the LCR
CONFLICT_TYPE VARCHAR2(18)  

Conflict type. Possible values:

  • INSERT ROW EXISTS: DML operation is INSERT and a row already exists with the specified key value.

  • UPDATE ROW EXISTS: DML operation is UPDATE. A row with the specified key exists but has conflicting values for some columns.

  • UPDATE ROW MISSING: DML operation is UPDATE and no row with the specified key value exists.

  • DELETE ROW EXISTS: DML operation is DELETE. A row with the specified key exists but has conflicting values for some columns

  • DELETE ROW MISSING: DML operation is DELETE and no row with the specified key value exists.

APPLIED_STATE VARCHAR2(22)  

Conflict applied state. Possible values:

  • WON: Incoming LCR was applied in its entirety

  • PARTIAL: Incoming LCR was applied for one or more conflict groups

  • LOST: Incoming LCR was not applied

  • SITE PRIORITY, WON: Site priority resolution was in effect and incoming LCR was applied in its entirety

  • SITE PRIORITY, PARTIAL: Site priority resolution was in effect and incoming LCR was applied for one or more conflict groups

  • SITE PRIORITY, LOST: Site priority resolution was in effect and incoming LCR was not applied

SEQ# NUMBER   Trail file number (Oracle GoldenGate)
RBA NUMBER   Position with Trail file (Oracle GoldenGate)
CONFLICT_INFO VARCHAR2(4000)   Identifies the conflict group information
SOURCE_PACKAGE_NAME VARCHAR2(128)   Package name of the source for procedural replication
PACKAGE_NAME VARCHAR2(128)   Package name of the destination for procedural replication
MESSAGE CLOB   The content of the LCR. Content includes column name and value for old and/or new values in DML LCRs. For DDL LCRs, the content is the text of the DDL SQL.

See Also: