Troubleshooting guide

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 Oracle database, insert data into the primary ptab1 table and commit:
insert into ptab1 values (4, 'Crow T. Robot');
commit;
12.
On the SAP HANA database, verify that the data replicated to the replicate PTAB1 table:
SELECT * FROM <tableowner>.PTAB1;
Resetting the Primary Oracle Database for Replication
In a test environment, you may occasionally need to reset the replication environment.
1.
Log in to the Replication Agent and suspend replication:
1> suspend
2> go
2.
Archive all current redo log data:
ra_locator move_truncpt
3.
Reinitialize Replication Agent, which refreshes the Replication Agent repository rather
than overwriting it:
ra_admin refresh
Note: If you prefer to delete and replace all the information in the Replication Agent
repository, issue the ra_admin deinit, force command followed by a normal ra_admin init
command (without the force option).
4.
Reset the locator stored in Replication Server:
isql -Usa -Psa_pass -SSAMPLE_RS
connect
CHAPTER 4: Oracle-to-SAP HANA Database Replication Setup
48 Replication Server