Troubleshooting guide

grant all privileges on <tableowner>.PTAB1 to public
8.
Log in to Replication Server:
isql –Usa –Psa_pass –SSAMPLE_RS
If you have not set up the sample Replication Server instance, enter your Replication
Server instance name in place of SAMPLE_RS.
9.
Alter the replication definition that you created earlier to point to the correct replicate
table:
alter replication definition <repdefname>
with replicate table named <tableowner>.ptab1
go
10.
Create a subscription against the replicate connection.
To create the ptab1_sub subscription for the
<repdefname> replication definition:
create subscription ptab1_sub
for <repdefname>
with replicate at rds.rdb
without materialization
go
where
<repdefname> is the replication definition that you altered in the previous step, and
rds . rdb is the name of the replicate SAP HANA database connection created earlier.
For information on using the create subscription command in direct load materialization,
see Replication Server Reference Manual .
11.
On the Microsoft SQL Server database, insert data into the primary ptab1 table and
commit:
insert into ptab1
values (5, "Joel Robinson")
go
commit
go
12.
On the SAP HANA database, verify that the data replicated to the replicate PTAB1 table:
SELECT * FROM <tableowner>.PTAB1;
See also
• Configuring Replication Server for Replication from the Primary Database on page 61
Resetting the Primary Microsoft SQL Server Database for Replication
In a test environment, you may occasionally need to reset the replication environment.
1.
Protect your new environment from old log information by using this command in the
Replication Agent to archive all current redo log data:
ra_locator move_truncpt
2.
Reinitialize Replication Agent, which refreshes the Replication Agent repository rather
than overwriting it:
CHAPTER 5: Microsoft SQL Server-to-SAP HANA Database Replication Setup
76 Replication Server