Database object names must be delivered to the primary Replication Server in the same format as they are specified in replication definitions. 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 the Replication Agent.
Replication will fail if a database object name is delivered
to the primary Replication Server in a format different from that
specified in the replication definition.
Sybase Replication Agent version 12.6 gives you some control over the way it treats the character case of database object names when it sends LTL to the primary Replication Server. You have three options:
asis – 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.
You specify the character case option you want by setting the value of the ltl_character_case configuration parameter. The parameter values are asis (the default), lower, and upper.
In the case of 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
stored as TABA
create table Tabb is
stored as TABB
create table ‘TaBc’ is
stored as TABC
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
