Access to replicate tables and stored procedures in a non-Sybase database often requires that the reference to the replicate table or stored procedure be owner qualified.
For example, suppose the Replication Server Maintenance User defined to apply transactions to an Oracle replicate database is orauser. A replicate insert command to table table1 may fail with a “table not found” error if the owner of table1 is bob. When attempting to find table1, Oracle looks for orauser.table1, not bob.table1. To properly identify the replicate table to be updated, you can:
Create an alias at the Oracle replicate database that refers to the correct replicate table. For example, you could create a synonym object in Oracle named table1, which refers to the fully qualified name of bob.table1.
When creating the replication definition, use the with replicate table named [table_owner.['table_name']] clause. To satisfy the example, the clause would be:
with replicate table named bob.table1
If you use RSM, you can also specify the replicate owner
and table name to be used for a replication definition.
The problem becomes a little more complicated when table1 is to be replicated to more than one replicate database (for example, Oracle replicate table bob.table1 and Informix replicate table sue.table1). The option of using the with replicate table named clause in the replication definition supports only one replicate table name.
To work around this issue, you must create multiple replication definitions, one for each unique replicate table name required. Then, each subscription must refer to the correct replication definition. Each replication definition must use the with replicate table named clause.
