Tuesday, June 2, 2009

Checking for Apply Errors

Checking for Apply Errors
To check for apply errors, run the following query:COLUMN APPLY_NAME HEADING 'ApplyProcessName' FORMAT A10
COLUMN SOURCE_DATABASE HEADING 'SourceDatabase' FORMAT A10
COLUMN LOCAL_TRANSACTION_ID HEADING 'LocalTransactionID' FORMAT A11
COLUMN ERROR_NUMBER HEADING 'Error Number' FORMAT 99999999
COLUMN ERROR_MESSAGE HEADING 'Error Message' FORMAT A20
COLUMN MESSAGE_COUNT HEADING 'Messages inErrorTransaction' FORMAT 99999999
SELECT APPLY_NAME,
SOURCE_DATABASE,
LOCAL_TRANSACTION_ID,
ERROR_NUMBER,
ERROR_MESSAGE,
MESSAGE_COUNT
FROM DBA_APPLY_ERROR;
If there are any apply errors, then your output looks similar to the following:Apply Local Messages in
Process Source Transaction Error
Name Database ID Error Number Error Message Transaction
---------- ---------- ----------- ------------ -------------------- -----------
APPLY_FROM MULT3.NET 1.62.948 1403 ORA-01403: no data f 1
_MULT3 ound
APPLY_FROM MULT2.NET 1.54.948 1403 ORA-01403: no data f 1
_MULT2 ound
If there are apply errors, then you can either try to reexecute the transactions that encountered the errors, or you can delete the transactions. If you want to reexecute a transaction that encountered an error, then first correct the condition that caused the transaction to raise an error.
If you want to delete a transaction that encountered an error, then you might need to resynchronize data manually if you are sharing data between multiple databases. Remember to set an appropriate session tag, if necessary, when you resynchronize data manually.
-- regards,Rohit Sinha"It takes a minute to have a crush an hour to like someone and a day to love someone but it takes a lifetime to forget someone"

No comments:

Post a Comment