Cross Datatype Mapping Being Used in Replication Causes Data to be Missing or Junk in TeraData (Doc ID 2187875.1)

Last updated on AUGUST 11, 2017

Applies to:

Oracle GoldenGate - Version 11.2.1.0.1 to 12.2.0.1.0 [Release 11.2 to 12.2]
Information in this document applies to any platform.

Symptoms

Oracle to TD GG Replication :: Missing Data



When replicating data from Oracle to TD, the actual data is replaced with
junk data in the target. There are no errors reported in the
extract/pump/replicat.
.
This only occurs when placing this parm in the odbc.ini file
.
CharacterSet=UTF16
.
This was added to support UNICODE Character replication. However if you
remove this entry then NUMBER to VARCHAR replication is working properly.
Note that we cannot remove this entry permanently because we have UNICODE
Characters in other fields; removing this entry will result in failure with
other columns

*******************DATA IN SOURCE DURING INITIAL LOAD:*******************************
Enter user-name:/ as sysdba

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

SQL> select guid, RELEASED_ON from sapsr3.test_table;

GUID RELEASED_ON
-------------------------------- -----------
FAB0C9AF7D031ED688FEB2A2100E81F4 2.0161E+13
364CDACB6B031ED680967F07807C002A 2.0160E+13
FAB0C9AF7D031ED688FE9474845FC1D7 0
FAB0C9AF7D031ED688FE706E94D282DB 2.0161E+13
FAB0CA59FF021ED68B9D212D5691C9E5 2.0161E+13
FAB0CA59FF021ED68BE7872C76960CEE 2.0161E+13

*******************DATA IN TARGET AFTER INITIAL LOAD:*******************************

 BTEQ -- Enter your SQL request or BTEQ command:
select guid, released_on from test_table;

select guid, released_on from test_table;

 *** Query completed. 6 rows found. 2 columns returned.
 *** Total elapsed time was 1 second.

GUID RELEASED_ON
-------------------------------- ---------------
FAB0CA59FF021ED68B9D212D5691C9E5 20160607195052
FAB0C9AF7D031ED688FE9474845FC1D7 0
364CDACB6B031ED680967F07807C002A 20160412134348
FAB0CA59FF021ED68BE7872C76960CEE 20160610194817
FAB0C9AF7D031ED688FE706E94D282DB 20160527101502
FAB0C9AF7D031ED688FEB2A2100E81F4 20160527105356

*******************CHANGE THE DATA IN SOURCE*******************************
SQL> update sapsr3.test_table set released_on = 20160613195052 where guid='FAB0CA59FF021ED68B9D212D5691C9E5';

1 row updated.

SQL> commit;

Commit complete.

SQL> select guid, released_on from sapsr3.test_table where guid='FAB0CA59FF021ED68B9D212D5691C9E5';

GUID RELEASED_ON
-------------------------------- -----------
FAB0CA59FF021ED68B9D212D5691C9E5 2.0161E+13

SQL> select guid, to_char(released_on) from sapsr3.test_table where guid='FAB0CA59FF021ED68B9D212D5691C9E5';

GUID TO_CHAR(RELEASED_ON)
-------------------------------- ----------------------------------------
FAB0CA59FF021ED68B9D212D5691C9E5 20160613195052

SQL>

*******************DATA IN TARGET AFTER THE CHANGE IN SOURCE*******************************
select guid, released_on from test_table;

 *** Query completed. 6 rows found. 2 columns returned.
 *** Total elapsed time was 1 second.

GUID RELEASED_ON
-------------------------------- ---------------
FAB0CA59FF021ED68B9D212D5691C9E5
FAB0C9AF7D031ED688FE9474845FC1D7 0
364CDACB6B031ED680967F07807C002A 20160412134348
FAB0CA59FF021ED68BE7872C76960CEE 20160610194817
FAB0C9AF7D031ED688FE706E94D282DB 20160527101502
FAB0C9AF7D031ED688FEB2A2100E81F4 20160527105356

 BTEQ -- Enter your SQL request or BTEQ command:
select guid, released_on, character_length(RELEASED_ON) from test_table;

select guid, released_on, character_length(RELEASED_ON) from test_table;

 *** Query completed. 6 rows found. 3 columns returned.
 *** Total elapsed time was 1 second.

GUID RELEASED_ON Characters(RELEASED_ON)
-------------------------------- --------------- -----------------------
FAB0CA59FF021ED68B9D212D5691C9E5 7 FAB0C9AF7D031ED688FE9474845FC1D7 0 1
364CDACB6B031ED680967F07807C002A 20160412134348 14
FAB0CA59FF021ED68BE7872C76960CEE 20160610194817 14
FAB0C9AF7D031ED688FE706E94D282DB 20160527101502 14
FAB0C9AF7D031ED688FEB2A2100E81F4 20160527105356 14

 BTEQ -- Enter your SQL request or BTEQ command:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms