Create a maintenance user in the replicate SAP IQ data server, or you can use
the existing maintenance user.
Create the connection to the replicate SAP IQ database from the replicate
Replication Server using the relevant connection
profile and the maintenance user from step 1, such
as dbmaint.
Adaptive Server:
create connection to IQSRVR.iqdb
using profile rs_ase_to_iq;standard
set username to dbmaint
set password to dbmaint
go
Oracle:
create connection to IQSRVR.iqdb
using profile rs_oracle_to_iq;standard
set username to dbmaint
set password to dbmaint
go
At the primary database, if a table owned by dbo is not marked as owner_on, you must
enable owner_on
for the table so that SAP IQ can find the table
since dbo does
not exist in SAP IQ.
Adaptive Server
Adaptive Server 15.0.3 and later:
sp_setrepdefmode testtab, ‘owner_on’
go
Versions earlier than Adaptive Server 15.0.3:
sp_setreptable testtab, ‘true’, ‘owner_on’
go
Oracle
pdb_setreptable testtab, mark, owner
go
Recreate the replication definition to include owner
information since you have enabled owner_on for Adaptive Server or owner for Oracle.
If there are referential constraints between tables,
you must alter the replication definition to define referential
constraints so that Replication Server is aware of the referential
constraints and can perform bulk apply in the proper order.
Enable RTL for the connection to the replicate database:
alter connection to iqserver_name.rdb
set dsi_compile_enable to 'on'
After suspending and resuming the connection, the change in
the connection takes effect.
Create subscriptions for each table. If the primary
and replicate database are synchronized, include the without
materialization clause in the subscription. Otherwise
you must enable autocorrection during materialization.
You can now replicate directly from the primary data server to SAP IQ.