Skip Headers
Oracle® Database Reference
11g Release 2 (11.2)

E40402-14
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

DBA_APPLY_ERROR

DBA_APPLY_ERROR displays information about the error transactions generated by all apply processes in the database. Its columns are the same as those in ALL_APPLY_ERROR.

Column Datatype NULL Description
APPLY_NAME VARCHAR2(30)   Name of the apply process at the local database which processed the transaction
QUEUE_NAME VARCHAR2(30) NOT NULL Name of the queue at the local database from which the transaction was dequeued
QUEUE_OWNER VARCHAR2(30) NOT NULL Owner of the queue at the local database from which the transaction was dequeued
LOCAL_TRANSACTION_ID VARCHAR2(22)   Local transaction ID for the error transaction
SOURCE_DATABASE VARCHAR2(128)   Database where the transaction originated
SOURCE_TRANSACTION_ID VARCHAR2(128)   Original transaction ID at the source database
SOURCE_COMMIT_SCN NUMBER   Original commit system change number (SCN) for the transaction at the source database
MESSAGE_NUMBER NUMBER   Identifier for the message in the transaction that raised an error
ERROR_NUMBER NUMBER   Error number of the error raised by the transaction
ERROR_MESSAGE VARCHAR2(4000)   Error message of the error raised by the transaction
RECIPIENT_ID NUMBER   User ID of the original user that applied the transaction
RECIPIENT_NAME VARCHAR2(30)   Name of the original user that applied the transaction
MESSAGE_COUNT NUMBER   Total number of messages inside the error transaction
ERROR_CREATION_TIME DATE   Time that the error was created
SOURCE_COMMIT_POSITION RAW(64)   Original commit position for the transaction
ERROR_TYPEFoot 1  VARCHAR2(23)   NULL if the apply process can access all of the LCRs in the error transaction. When the ERROR_TYPE is NULL, manage the error transactions using the instructions in Oracle Streams Concepts and Administration.

EAGER ERROR if the apply process cannot access all of the LCRs in the error transaction. This error type typically means that the apply process was applying LCRs in a large transaction. When the ERROR_TYPE is EAGER ERROR, manage the error transaction using the instructions in Oracle Database XStream Guide.

ERROR_POSITIONFoot 2  RAW(64)   NULL if the apply process can access all of the LCRs in the error transaction. When the ERROR_TYPE is NULL, manage the error transactions using the instructions in Oracle Streams Concepts and Administration.

EAGER ERROR if the apply process cannot access all of the LCRs in the error transaction. This error type typically means that the apply process was applying LCRs in a large transaction. When the ERROR_TYPE is EAGER ERROR, manage the error transaction using the instructions in Oracle Database XStream Guide.

RECORD LCR indicates that a single LCR has been recorded as requested by user-specified error handling configuration

RECORD TXN NO LCRS indicates that the identified transaction encountered an error and only the transaction ID is recorded as requested by user-specified error handling configuration

RECORD TXN WITH LCRS indicates that the identified transaction encountered and error. The entire transaction is recorded as requested by user-specified error handling configuration.

UNHANDLED ERRORS NO LCR indicates that the identified transaction encountered an error and there was no error handling specified for this handler. No LCRs are recorded for this transaction.


Footnote 1 This column is available starting with Oracle Database 11g Release 2 (11.2.0.2).

Footnote 2 This column is available starting with Oracle Database 11g Release 2 (11.2.0.4)