Ideally, if all the data servers in your replication system are not case sensitive, no special consideration is required.
The following items can be used to help in a situation where some of the servers are case sensitive:
Use the replicate as clause in replication definitions. When you create a replication definition, either manually, you can specify a separate replicate name for table and column names. Use this feature to specify the case required by your replicate database.
If your primary data is replicated to more than one
replicate site, you might have to create a separate replication
definition for each unique replicate table name.
Configure the Replication Agent accordingly. If the option is available, you can configure the Replication Agent to send object names in the same case as the primary database stores them. You can force the case to be anything you like, as long as the LTL generated by the Replication Agent matches the case used in the replication definition.
Use an alias at the replicate site. As an alternative to creating replication definitions with the replicate as clause, you can create an alias at the replicate database that matches the case in the primary database and points to the desired replicate table name.
