Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration Connectors
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Oracle CDC V2 Connector
  3. Oracle CDC connections
  4. Mappings and mapping tasks with Oracle CDC V2 Connector
  5. Oracle CDC administration
  6. Data type reference
  7. Connection overrides reference

Oracle CDC V2 Connector

Oracle CDC V2 Connector

Back Next

Oracle CDC V2 and transformation data types

Oracle CDC V2 and transformation data types

The following table lists the Oracle CDC V2 data types that
Data Integration
 supports and the corresponding transformation data types:
Datatype
Supported for CDC?
Transformation Data Type
BFILE
No
Column data that has this datatype is not completely logged in the Oracle redo logs and cannot be captured.
BINARY_DOUBLE
Yes
-
BINARY_FLOAT
Yes
-
CHAR
Yes
-
DATE
Yes
The date must be in the range Jan 1, 0001 A.D. to Dec 31, 9999 A.D. in the Gregorian calendar. Dates beyond 9999 A.D. cause an error.
Also, PowerExchange does not support negative dates, such as
-0001-12-20-00-00-00
. If PowerExchange receives a negative date, it substitutes an absolute value for the date and tolerates the Oracle log record that contains the date.
FLOAT
Yes
If you set the ORACLE_UNHANDLED_NUMASCHAR statement to Y in the dbmover.cfg file, PowerExchange registration processing for Oracle CDC source tables converts FLOAT columns that have a precision greater than 15 to VARCHAR columns. This setting can prevent data loss.
LOBs
Yes
Datatypes supported for Oracle LOBs are BLOB, CLOB, and NCLOB. PowerExchange can capture change data from LOB columns and non-LOB columns in the same source table, within the maximum row size limit of 8 MB.
LONG
No
Columns that have this datatype cannot be included in capture registrations.
LONG RAW
No
Columns that have this datatype cannot be included in capture registrations.
NCHAR
Yes
-
NUMBER
Yes
PowerExchange handles NUMBER columns as follows:
  • Numbers that have a precision value less than 10 and a scale of 0 are treated as INTEGER.
  • Numbers that have a defined precision and scale are treated as NUMCHAR.
  • Numbers that have an undefined precision and scale are treated as double-precision floating point numbers by default.
If you set the ORACLE_UNHANDLED_NUMASCHAR statement to Y in the dbmover.cfg file, PowerExchange registration processing for Oracle CDC source tables treats NUMBER columns that have a precision greater than 28 or an undefined length as variable length strings. This setting can prevent data loss.
NVARCHAR2
Yes
-
RAW
Yes
-
ROWID
Yes
-
TIMESTAMP
Yes
The date must be in the range Jan 1, 0001 A.D. to Dec 31, 9999 A.D. in the Gregorian calendar. Dates beyond 9999 A.D. cause an error.
Also, PowerExchange does not support negative dates, such as
-0001-12-20-00-00-00
. If PowerExchange receives a negative date, it substitutes an absolute value for the date and tolerates the Oracle log record that contains the date.
TIMESTAMP WITH TIME ZONE
Yes
PowerExchange captures data with this datatype as a UTC timestamp.
The date must be in the range Jan 1, 0001 A.D. to Dec 31, 9999 A.D. in the Gregorian calendar. Dates beyond 9999 A.D. cause an error.
Also, PowerExchange does not support negative dates, such as
-0001-12-20-00-00-00
. If PowerExchange receives a negative date, it substitutes an absolute value for the date and tolerates the Oracle log record that contains the date.
PowerCenter does not support this datatype. If you use PowerCenter to materialize a target table from a source table that includes this datatype, manually override the datatype in Source Analyzer with the timestamp datatype. Also, edit the generated SQL select statement that PowerCenter sends to PowerExchange to use the sys_extract_utc() function. Syntax: 
select sys_extract_utc(tmstmpwith_tz) from 
schema
.
source_table
TIMESTAMP WITH LOCAL TIME ZONE
Yes
PowerExchange captures data with this datatype as a UTC timestamp.
The date must be in the range Jan 1, 0001 A.D. to Dec 31, 9999 A.D. in the Gregorian calendar. Dates beyond 9999 A.D. cause an error.
Also, PowerExchange does not support negative dates, such as
-0001-12-20-00-00-00
. If PowerExchange receives a negative date, it substitutes an absolute value for the date and tolerates the Oracle log record that contains the date.
PowerCenter does not support this datatype. If you use PowerCenter to materialize a target table from a source table that includes this datatype, manually override the datatype in Source Analyzer with the timestamp datatype. Also, edit the generated SQL select statement that PowerCenter sends to PowerExchange to use the sys_extract_utc() function. Syntax: 
select sys_extract_utc(tmstmpwith_tz) from 
schema
.
source_table
UROWID
No
-
User-defined types (UDTs)
No
-
VARCHAR2
Yes
-
XML types
No
-
0 COMMENTS
We’d like to hear from you!