OGG - ERROR:ADD SCHEMATRANDATA PREPARECSN NONE
(Doc ID 2921204.1)
Last updated on DECEMBER 11, 2024
Applies to:
Oracle Database Cloud Exadata Service - Version N/A to N/A [Release 1.0]Oracle GoldenGate - Version 19.1.0.0.0 and later
Information in this document applies to any platform.
Symptoms
An execution error occurs for the lowercase object name in the schema when we executed 'ADD SCHEMATRANDATA PREPARECSN NONE'.
It seems like the reason why executed "SCHEMA"."TABLE" which are identified by uppercase letters when executed SQL to source DB.
What can we do here?
・ If it is a product defect, is it possible to create a fix patch? and if it is possible to create a fix patch, when will it be provided?
・Is there a workaround (such as setting a SQL statement executed internally on the DB side by executing it directly)?
ERROR DETAILS:
GGSCI> ADD SCHEMATRANDATA <SCHEMA> PREPARECSN NONE
2021-10-27 13:20:19 INFO OGG-01788 SCHEMATRANDATA has been added on schema "<SCHEMA>".
2021-10-27 13:20:20 INFO OGG-01976 SCHEMATRANDATA for scheduling columns has been added on schema "<SCHEMA>".
2021-10-27 13:20:20 ERROR OGG-01790 Failed to ADD SCHEMATRANDATA on schema "<SCHEMA>" because of the following SQL error: ORA-06564: object "<SCHEMA>"."<OBJECT_NAME>" does not exist
ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 581
ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 625
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 1444
ORA-01403: no data found
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 1438
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_IVK", line 574
ORA-06512: at "SYS.DBMS_CAPTURE_ADM", line 410
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |