data wipped out on target table
872029Jul 21 2011 — edited Jul 25 2011Hi All,
It is very strange that in my Active-Active GG setup, i was reported that all the data in a table in the target wipped out except one record.
Schema and table name: RELEASE_APP2.PORT_INST
IDEV1 has 98 records
IDEV2 has 1 record only
Here are the steps i performed to troubleshoot this:
1. checked 'View report <extract>/<replicat>, found no activities regarding the data lost
2. checked stats: stats <extract>/<replicat> name, table <owner.table>
and there is no sign of any operations performed on that particular table.
3. I have exception tables setup on both source and target server to trap errors but i can't find any errors logged on the exception table.
here is my replicat setup
-- Identify the Replicat group:
REPLICAT CEPREP1
-- Use HANDLECOLLISIONS while Source is Active
--HANDLECOLLISIONS
-- State that source and target definitions are identical:
ASSUMETARGETDEFS
-- Specify database login information as needed for the database:
USERID goldengate_owner, PASSWORD xxxxxx
-- This starts the macro for exception handler
MACRO #exception_handler
BEGIN
, TARGET goldengate_owner.exceptions
, COLMAP ( rep_name = "CEPREP1"
, table_name = @GETENV ("GGHEADER", "TABLENAME")
, errno = @GETENV ("LASTERR", "DBERRNUM")
, dberrmsg = @GETENV ("LASTERR", "DBERRMSG")
, optype = @GETENV ("LASTERR", "OPTYPE")
, errtype = @GETENV ("LASTERR", "ERRTYPE")
, logrba = @GETENV ("GGHEADER", "LOGRBA")
, logposition = @GETENV ("GGHEADER", "LOGPOSITION")
, committimestamp = @GETENV ("GGHEADER", "COMMITTIMESTAMP"))
, INSERTALLRECORDS
, EXCEPTIONSONLY;
END;
-- This ends the macro for exception handler
-- Specify error handling rules:
--REPERROR (<error>, <response>)
REPERROR (DEFAULT, EXCEPTION)
REPERROR (DEFAULT2, ABEND)
REPERROR (-1, EXCEPTION)
REPERROR (-1403, EXCEPTION)
DDL INCLUDE ALL, EXCLUDE OBJNAME "GOLDENGATE_OWNER.*"
DDLERROR DEFAULT IGNORE RETRYOP
MAP GGATE_T1.*, TARGET GGATE_T1.*;
MAP GGATE_T1.* #exception_handler()
MAP RELEASE_APP2.*, TARGET RELEASE_APP2.*;
MAP RELEASE_APP2.* #exception_handler()
Any help as to how dig into this issue would be appreciated.
Thanks,
pbhand.