Extended Datatype Support (EDS) for SQL Apply
(Doc ID 559353.1)
Last updated on SEPTEMBER 25, 2022
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.1.0.7 [Release 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Oracle Server - Enterprise Edition - Version: 11.1.0.7 to 11.1.0.7
Information in this document applies to any platform.
Purpose
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Schema: OBJUSER
Trigger: PLAYERS_STBY_TRG
*******************
Extended Datatype Support (EDS) is the ability for SQL Apply to extend support for additional datatypes that are not natively supported yet by SQL Apply. EDS relies on a new capability in Oracle Database 10g Release 2 Patch Set 3 (10.2.0.4) and Oracle Database 11g Release 1 Patch Set 1 (11.1.0.7) that allows triggers to fire on the logical standby database. Use the explanation and examples below as a guide to add extended support to your logical standby database for datatypes not natively supported.
EDS is also available for Streams to handle datatypes not natively supported. For additional information, see the Maximum Availability Architecture (MAA) technical brief Extended Datatype Support on the Oracle Technology Network (OTN).
Scope
Prerequisites:
- Any user that owns a base table that requires EDS must have EXECUTE privilege on the DBMS_LOGSTDBY package.
- As recommended for tables that SQL Apply supports natively, tables supported with EDS should have either a primary key or non-null unique index defined.
Restrictions:
- Once EDS is in place for a table, neither the table definition nor the type definitions used within the table can be modified.
- Although tables that contain LOB columns are supported natively by SQL Apply, tables with LOB columns that require EDS are not currently supported.
Details
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
Purpose |
Scope |
Details |
Overview |
Configuring EDS |
Troubleshooting |
References |