OGG-00519
In the remote database, you may not create all objects to resolve dependency problems. Here are some OGG-00519 DDL errors in REPLICAT report below:
2017-08-22 19:52:03 ERROR OGG-00519 Fatal error executing DDL replication: error [Error code [1435], ORA-01435: user does not exist SQL ALTER SESSION SET CURRENT_SCHEMA="PUBLIC"], no error handler present.
2017-08-23 20:18:54 ERROR OGG-00519 Fatal error executing DDL replication: error [Error code [942], ORA-00942: table or view does not exist SQL ALTER PUBLIC SYNONYM "CUSTOMERS" COMPILE /* GOLDENGATE_DDL_REPLICATION */], no error handler present.
Solutions
Let's see the new parameters in the REPLICAT that can ignore the above errors.
[oracle@remote dirprm]$ vi erpapp_r.prm
replicat erpapp_r
assumetargetdefs
userid ogg, password ogg
discardfile ./dirrpte/erpapp_r.dsc, append, megabytes 10
dboptions suppresstriggers
reperror (0001, discard)
reperror (1403, discard)
ddlerror 1430 ignore
ddlerror 1432 ignore
ddlerror 1435 ignore
ddlerror 942 ignore
ddlerror 904 ignore
allownoopupdates
ddl include mapped
map erpapp.*, target erpapp.*;
Please note that, we use ddlerror 942 ignore to pass ORA-00942.
hi sir,
I encounter this problem too.
Do you think it is wierd?
No really, OGG-00519 is a general DDL error, there’re many possible ORA errors could generate it.
For example, a common error from ALTER SESSION statement like this:
SQL> alter session set current_schema=not_existing_schema;ERROR:
ORA-01435: user does not exist
Your users may accidentally make such mistakes. And the mistake propagated to the standby database via Golden Gate. When Golden Gate replayed the statement, it found the error too.
Hi Ed.
Thanks for replicat prm. Its very informational.
Quickquestio, how can I do to see the transaction that are being apply by the Replicat or at least to have more details on the ggserr.log.
Let’s say when we got stuck on one of this transactions and want to see the transaction that is holding the replicat – where can I see this, do you know?
I have used ddl error which resolved the error
Thank you !!!