@DATE funtions outputs wrong results in Ogg v12.3.x
(Doc ID 2461160.1)
Last updated on OCTOBER 24, 2018
Applies to:Oracle GoldenGate - Version 18.104.22.168.10 and later
Information in this document applies to any platform.
If @DATE function fails for years ending 00, then we may be running into this issue.
@DATE function in OGG 12.3 / DB 12.2 is not working as expected. It has been tested in OGG 12.3 / 11g and the issue persists. It has been tested in OGG 12.1 / DB 11g and it works fine and we are getting the desired value.
MAP source.test, TARGET source.test_target, COLMAP (id=id, a = @DATE
('YYYY-MM-DD', 'YYYYDDD', a));
The column (a) is number in source and date in target.
SQL> insert into source.test values (1,100013);
1 row created.
Expected Value :
SQL> select to_date('100013','yyyyddd') from dual;
Bad value after @DATE is used on Target Record
SQL> select * from source.test_target;
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