Last updated on FEBRUARY 08, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 9.2 to 11.1]
Information in this document applies to any platform.
So it is not a db link issue it is only streams issue as streams not aware of the changing in CharacterSet.In a bi-directional Streams setup replication working fine.
But after changing the CharacterSet each database stores and shows the correct characters we can save any text and read it again without problems, but the whole text content, replicated by streams, goes corrupt.
When updating site A with the select done from site B using database link, and the data is fine (remains fine for both sides).
If creating new tables with Latin characters and streaming them , it works as expected.
The CharacterSet changed according to Oracle guideline (procedure, described in Oracle Globalization Guide, with CS-Scanner and CSALTER).
The streams were stopped before change and started again after change made. Also, verified that queues were empty before changing the CharacterSet.
This occurred and verified for the following changes :
Changing from WE8ISO8859P15 to EE8MSWIN1250
Changing from US7ASCII to WE8MSWIN1252
Changing from WE8MSWIN1252 to UTF8
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms