Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

When it appears that Dbvisit Replicate does not replicate the changes please check the following:

1) Use the "list prepare" command in the Dbvisit Replicate command console:

 

dbvrep>list prepare

Note, when the apply process is not run as the default APPLY, then use the "CHOOSE REPLICATION" command to choose the appropriate process. For example, if the process is called APPLY2, then use "CHOOSE REPLICATION APPLY2"

2) Check that the particular table exists in the Dbvisit Replicate data dictionary table. The following query on the run as the Dbvisit Replicate owner on the target database can be run to verify:

 

SQL> select name, obj_ from DBRSOBJ$ where obj_ in (select SOURCE_OBJECT_ID from
DBRSAPPLY_DICT_TABLES);
NAME OBJ_
------------------------------ ----------
DBRSCOL$ 78949
DBRSOBJ$ 78951
DBRSTAB$ 78953
DEPT 74209
EMP 74211
BONUS 74213
SALGRADE 74214
DBRSUSER$ 78955
DBRSV_$DATABASE 78957

Only the tables listed in this table will be replicated. To replicate other tables use the PREPARE command.

3) Are all tables not being replicated or just a subset? If a subset is replicated, please ensure all the tables to be prepared are known to Dbvisit Replicate. Use the "list prepare" to check which tables are known to Dbvisit Replicate.

4) Use the "healthcheck" command to see if all the processes can communicate with each other. 

 
  • No labels