Ensures the byte order of NCLOB data is sent correctly to the replicate database.
The correct byte order is necessary when you are replicating with different primary and replicate database types , or primary and replicate databases that are on different platforms (little endian Windows to big endian UNIX).
big
When replicating Oracle to Oracle, you need to know the endian for the replicate database and set the parameter so the correct endian is sent to the replicate. The same applies when replicating to databases other than Oracle.
If lr_ntext_byte_order is set to little, ltl_big_endian_unitext must be set to false.
Big endian indicates a left-to-right byte-order architecture; little endian indicates a right-to-left byte-order architecture.
The default behavior of Replication Agent is to force any unicode data to big endian order, as defined by configuration parameter ltl_big_endian_unitext. In order to allow configuration parameter lr_ntext_byte_order to successfully override the SQL Server byte order, you must also set ltl_big_endian_unitext configuration parameter to false whenever the lr_next_byte_order parameter is used.
When ltl_big_endian_unitext is set true by default, Replication Agent ensures that all unicode data is sent in big endian order.
When set to false, ltl_big_endian_unitext allows unicode data to be sent in the byte order that is used when the data is stored in the transaction log file
In contrast, lr_ntext_byte_order, forces the result of Unicode data read from the transaction log to be in the requested byte order, regardless of how it normally exists in the transaction log file.