We're here to help!

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:

  1. Finish the Setup Wizard.
  2. Run the *-all.sh script
  3. Open config/*-wizard-databases.cfg and copy the dbid of the target database.
  4. 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.


    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.

  5. 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.

  6. 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.

  7. Repeat step 6 for *-APPLY.ddc.
  8. Run the *-all.sh script again.
  9. Start Replication.

Krupesh Desai August 12, 2014 15:08

Have more questions? Submit a request