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 Replication 9.8.0 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Overview
  3. Datatype Mappings for DB2 for Linux, UNIX, and Windows Sources
  4. Datatype Mappings for Microsoft SQL Server Sources
  5. Datatype Mappings for MySQL Sources
  6. Datatype Mappings for Oracle Sources
  7. Datatype Mappings for Virtual Source Columns

Datatype Mapping Reference

Datatype Mapping Reference

Back Next

Oracle Source and Oracle Target

Oracle Source and Oracle Target

The following table identifies the recommended datatype mappings for Data Replication configurations with an Oracle source and an Oracle target:
Oracle Source Datatype
Oracle Target Datatype
Comments
BINARY_DOUBLE
BINARY_DOUBLE
When replicating an 8-byte floating-point numeric value to a BINARY_DOUBLE column on the target, the Applier rounds this value and preserves only 15 digits after the decimal point by default. Use the apply.merge.double_precision runtime parameter to change the default precision value.
BINARY_FLOAT
BINARY_FLOAT
When replicating an 8-byte floating-point numeric value to a BINARY_FLOAT column on the target, the Applier rounds this value and preserves only 15 digits after the decimal point by default. Use the apply.merge.double_precision runtime parameter to change the default precision value.
BLOB
BLOB
By default, the Applier cannot insert change data into LOB and LONG columns if the total row data size exceeds 4000 bytes. In this case, set the apply.oracle.use_returning_into runtime parameter to 1 to configure the Applier to use the RETURNING INTO clause to insert change data into LOB and LONG columns.
If the global.lob_truncation_size runtime parameter is set to 64000 bytes or less, InitialSync handles BLOB data as RAW data to improve performance.
Oracle piecewise operations are supported for SQL Apply mode only.
The Applier cannot load change data to Oracle LOB columns in Merge Apply mode.
Use the global.lob_truncation_size runtime parameter to set the maximum size of a source LOB value that the Applier and InitialSync can replicate to the target. Maximum supported size for change data capture is 50 MB.
CHAR(
n
)
CHAR(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
-
CLOB
CLOB
By default, the Applier cannot insert change data into LOB and LONG columns if the total row data size exceeds 4000 bytes. In this case, set the apply.oracle.use_returning_into runtime parameter to 1 to configure the Applier to use the RETURNING INTO clause to insert change data into LOB and LONG columns.
Oracle piecewise operations are supported for SQL Apply mode only.
The Applier cannot load change data to Oracle LOB columns in Merge Apply mode.
Use the global.lob_truncation_size runtime parameter to set the maximum size of a source LOB value that the Applier and InitialSync can replicate to the target. Maximum supported size for change data capture is 50 MB.
DATE
DATE
-
FLOAT(
p
)
FLOAT(
p
)
-
INTERVAL DAY TO SECOND
INTERVAL DAY (%s) TO SECOND (%s)
-
INTERVAL YEAR TO MONTH
  • INTERVAL YEAR(1) TO MONTH
    Mapping condition: 
    p
     == 1
  • INTERVAL YEAR(2) TO MONTH
    Mapping condition: 
    p
     == 2
  • INTERVAL YEAR(3) TO MONTH
    Mapping condition: 
    p
     == 3
  • INTERVAL YEAR(4) TO MONTH
    Mapping condition: 
    p
     == 4
  • INTERVAL YEAR(5) TO MONTH
    Mapping condition: 
    p
     == 5
  • INTERVAL YEAR(6) TO MONTH
    Mapping condition: 
    p
     == 6
  • INTERVAL YEAR(7) TO MONTH
    Mapping condition: 
    p
     == 7
  • INTERVAL YEAR(8) TO MONTH
    Mapping condition: 
    p
     == 8
  • INTERVAL YEAR(9) TO MONTH
    Mapping condition: 
    p
     == 9
-
LONG
CLOB
By default, the Applier cannot insert change data into LOB and LONG columns if the total row data size exceeds 4000 bytes. In this case, set the apply.oracle.use_returning_into runtime parameter to 1 to configure the Applier to use the RETURNING INTO clause to insert change data into LOB and LONG columns.
For Merge Apply mappings, map source columns with the LONG datatype to target columns with the VARCHAR(40000) datatype.
LONG columns are not supported for materializing Oracle targets with DBLinks.
Maximum supported size is 8 KB.
Oracle piecewise operations are supported for SQL Apply mode only.
LONG RAW
BLOB
By default, the Applier cannot insert change data into LOB and LONG columns if the total row data size exceeds 4000 bytes. In this case, set the apply.oracle.use_returning_into runtime parameter to 1 to configure the Applier to use the RETURNING INTO clause to insert change data into LOB and LONG columns.
LONG RAW columns are not supported for materializing Oracle targets with DBLinks.
Oracle piecewise operations are supported for SQL Apply mode only.
The Applier cannot load change data to Oracle LOB columns in Merge Apply mode.
Use the global.lob_truncation_size runtime parameter to set the maximum size of a source LOB value that the Applier and InitialSync can replicate to the target. Maximum supported size for change data capture is 50 MB.
NCHAR(
n
)
NCHAR(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
-
NCLOB
NCLOB
By default, the Applier cannot insert change data into LOB and LONG columns if the total row data size exceeds 4000 bytes. In this case, set the apply.oracle.use_returning_into runtime parameter to 1 to configure the Applier to use the RETURNING INTO clause to insert change data into LOB and LONG columns.
Oracle piecewise operations are supported for SQL Apply mode only.
The Applier cannot load change data to Oracle LOB columns in Merge Apply mode.
Use the global.lob_truncation_size runtime parameter to set the maximum size of a source LOB value that the Applier and InitialSync can replicate to the target. Maximum supported size for change data capture is 50 MB.
NUMBER(
p
,
s
)
  • NUMBER
    Mapping condition: 
    p
     == -1 and 
    s
     == -1
  • NUMBER(*, 0)
    Mapping condition: 
    p
     == -1 and 
    s
     == 0
  • NUMBER(
    p
    ,
    s
    )
    Mapping condition: 
    p
     != 0 and 
    s
     == 0
  • NUMBER(
    p
    ,
    s
    )
    Mapping condition: 
    p
     != 0 and 
    s
     != 0
-
NVARCHAR(
n
)
NVARCHAR(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
-
NVARCHAR2(
n
)
NVARCHAR2(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
-
RAW(
n
)
  • RAW(
    n
    )
    Mapping condition: 
    n
     <= 2000
  • BLOB
    Mapping condition: 
    n
     > 2000
Oracle piecewise operations are supported for SQL Apply mode only.
TIMESTAMP(0)
TIMESTAMP(0)
-
TIMESTAMP(0) WITH LOCAL TIME ZONE
TIMESTAMP(0) WITH LOCAL TIME ZONE
-
TIMESTAMP(0) WITH TIME ZONE
TIMESTAMP(0) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(1)
TIMESTAMP(1)
-
TIMESTAMP(1) WITH LOCAL TIME ZONE
TIMESTAMP(1) WITH LOCAL TIME ZONE
-
TIMESTAMP(1) WITH TIME ZONE
TIMESTAMP(1) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(2)
TIMESTAMP(2)
-
TIMESTAMP(2) WITH LOCAL TIME ZONE
TIMESTAMP(2) WITH LOCAL TIME ZONE
-
TIMESTAMP(2) WITH TIME ZONE
TIMESTAMP(2) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(3)
TIMESTAMP(3)
-
TIMESTAMP(3) WITH LOCAL TIME ZONE
TIMESTAMP(3) WITH LOCAL TIME ZONE
-
TIMESTAMP(3) WITH TIME ZONE
TIMESTAMP(3) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(4)
TIMESTAMP(4)
-
TIMESTAMP(4) WITH LOCAL TIME ZONE
TIMESTAMP(4) WITH LOCAL TIME ZONE
-
TIMESTAMP(4) WITH TIME ZONE
TIMESTAMP(4) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(5)
TIMESTAMP(5)
-
TIMESTAMP(5) WITH LOCAL TIME ZONE
TIMESTAMP(5) WITH LOCAL TIME ZONE
-
TIMESTAMP(5) WITH TIME ZONE
TIMESTAMP(5) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(6)
TIMESTAMP(6)
-
TIMESTAMP(6) WITH LOCAL TIME ZONE
TIMESTAMP(6) WITH LOCAL TIME ZONE
-
TIMESTAMP(6) WITH TIME ZONE
TIMESTAMP(6) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(7)
TIMESTAMP(7)
-
TIMESTAMP(7) WITH LOCAL TIME ZONE
TIMESTAMP(7) WITH LOCAL TIME ZONE
-
TIMESTAMP(7) WITH TIME ZONE
TIMESTAMP(7) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(8)
TIMESTAMP(8)
-
TIMESTAMP(8) WITH LOCAL TIME ZONE
TIMESTAMP(8) WITH LOCAL TIME ZONE
-
TIMESTAMP(8) WITH TIME ZONE
TIMESTAMP(8) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
TIMESTAMP(9)
TIMESTAMP(9)
-
TIMESTAMP(9) WITH LOCAL TIME ZONE
TIMESTAMP(9) WITH LOCAL TIME ZONE
-
TIMESTAMP(9) WITH TIME ZONE
TIMESTAMP(9) WITH TIME ZONE
Oracle TIMESTAMP WITH TIME ZONE in the time zone region (TZR) format is not supported.
VARCHAR(
n
)
VARCHAR(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
-
VARCHAR2(
n
)
VARCHAR2(
n'
)
n'
 = (
n
 + 
SrcMinCharsetSize
 - 1) / 
SrcMinCharsetSize
Oracle piecewise operations are supported for SQL Apply mode only.
0 COMMENTS
We’d like to hear from you!