Rule-based Transformation To DDL LCR Result ORA-26746,Steps To Correct It Using Custom Rule Based Transformation Function For DDL And Declarative Rule Based Transformation for DML In AStreams Environment.
(Doc ID 1473251.1)
Last updated on FEBRUARY 14, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
This article provides an example of a custom rule-based transformation that renames a schema in the event of certain type of DDL statement and Declarative Rule Based Transformation for renaming the schema name
in the event of DML. Declarative transformations can transform row LCRs only. These row LCRs can be captured by a capture process, captured by a synchronous capture, or constructed and enqueued by an application. Therefore, a DML rule must be specified when you run this procedure. If a DDL is specified, then the procedure raises an error.
And actually, trying to apply that rule-based transformation to DDL LCR rule, gets the following error:
ORA-26746: DDL rule "STRMADMIN"."SOURCE30" not allowed for this operation
So it is needed to create custom transformation function for DDL transformation.
This article considers the following:
Test is performed on below 2 database:
Source Database: DB1
Destination Database: DB2
Schema level replication between schema SOURCE and DESTINATION.
Solution
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
| Goal |
| Solution |
| Associate the rule-based transformations with the DML and DDL apply rule |
| References |