Database object names must be delivered to the primary Replication Server in the same format as they are specified in replication definitions; otherwise, replication will fail. For example, if a replication definition specifies a table name in all lowercase, then that table name must appear in all lowercase when it is sent to the primary Replication Server by Mirror Replication Agent.
To control the way Mirror Replication Agent 15.1 treats the character case of database object names when it sends LTL to the primary Replication Server, set the ltl_character_case configuration parameter to one of the following values:
asis – (the default) database object names are passed to Replication Server in the same format as they are actually stored in the primary data server.
lower – database object names are passed to Replication Server in all lowercase, regardless of the way they are actually stored in the primary data server.
upper – database object names are passed to Replication Server in all uppercase, regardless of the way they are actually stored in the primary data server.
In the Oracle data server, database object names are stored in all uppercase by default. However, if you create a case-sensitive name, the case sensitivity is retained in Oracle.
See the following examples using the asis option:
create table tabA is
stored as TABA
create table Tabb is
stored as TABB
create table ‘TaBc’ is
stored as TaBc
See the following examples using the upper option:
create table tabA is rendered
in LTL as TABA
create table Tabb is
rendered in LTL as TABB
create table ‘TaBc’ is
rendered in LTL as TABC
