This content has been marked as final. Show 8 replies
Do you have keycols? The 1403 error is just like in regular ole SQL, cannot insert null into a column that has not null as a constraint.1 person found this helpful
I did not use keycols I am using table & MAP clauses in extract & replicat process.
Edited by: LazyDBA11g on Nov 7, 2012 8:58 PM
Replicat stopped because it hit an unhandled error, and from what you're describing, there probably weren't any updates on that table until the one that cause replicat to bomb. So, do you have keycols for the table?1 person found this helpful
ORA-1403 IS 'NO DATA FOUND'. The replicat is trying to either delete or update a record that doesn't exist in the target table.1 person found this helpful
Did you check the count of both the tables after initial load?
Anyways you should put in exception handling into your replicat so that it doesn't abend when it encounters any such exception and logs it to a table. here is a good article on the same.
Thanks a lot .. can u plz explain as how to use keycols ?
Please try one more thing, add these lines at the end of your extract process, replace your GG owner and replicated schema name:
Could you determine if table has PK or UQ ?1 person found this helpful
What is supplemental logging setting on source DB ? (select * from v$database)
Thanks for ur response. I performed initial load by using datapump and after that replication was working fine. But replication stopped later during business hours giving abovesaid errors.
1. Yes please table has PK
2. The supplemental logging is as below:
Any clue ?????
SQL> alter database add supplemental log data; SQL> ALTER SYSTEM SWITCH LOGFILE; SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE; --verify SUPPLEME -------- YES SQL>
Edited by: LazyDBA11g on Nov 7, 2012 9:00 PM