Store DDCDB to a highly secured Target Database
Problem Description
Dbvisit Replicate stores the DDCDB (the application's internal parameters and settings) in the source database by default. Therefore the APPLY process connects to the source database to retrieve and store information about the current replication configuration.
Note:Â the DDCDB is separate to Replicate's internal dictionary tables. The internal dictionary tables reside and are required in both source and target. They are used to keep track of information relating to the objects in the replication configuration.
Sometimes, in a highly secured environment, a connection from target database to source database is not permitted. In such scenarios, the following workaround can be performed to store the DDCDB in the target database:
Solution
Finish the Setup Wizard.
Run theÂ
-all.sh
 script
OpenÂ
config/*-wizard-databases.cfg
 and copy theÂdbid
 of the target database.OpenÂ
config/*-wizard-ddc.cfg
 and find the following variables and change their values accordingly:Note: The values need to be changed two times within this config file - for MINE and APPLY processes. Or three times if FETCHER is also used.
DDC_DATABASE DDC_DATABASE_DBID DDC_PASSWORD DDC_USER
Note:Â If default values ofÂ
DDC_USER
 andÂDDC_PASSWORD
 (dbvrep
 andÂdbvpasswd
 respectively) are used then do not change their values in step 4.RunÂ
start-console.sh
 and encrypt theÂDDC_PASSWORD
 for the target database. Use the encrypted value in step 6:dbvrep> engine encrypt <target_dbvrep_user_password>
Note:Â If the default value ofÂ
DDC_PASSWORD
 is used then step 5 is not required.OpenÂ
-MINE.ddc
 and change the following values accordingly:
memory_set DDC_DATABASE <target database TNS name> memory_set DDC_DATABASE_DBID <DBID of taget database> ( From step 3) memory_set DDC_PASSWORD < Encrypted password from step 5> memory_set DDC_USER <DDC_USER of target database>
Note:Â If the default values ofÂ
DDC_USER
 andÂDDC_PASSWORD
 are used then changingÂDDC_PASSWORD
 andÂDDC_USER
 is not required.Repeat step 6 forÂ
-APPLY.ddc
.
Run theÂ
-all.sh
 script again.
Start Replication.
Krupesh Desai August 12, 2014 15:08