The following Step-by-step example shows steps needed to configure APPLY process for using DDC file instead of DDC database.
On mine server run
sh start-console.sh show all > <ddc_name>-APPLY.ddc |
Open new <ddc_name>-APPLY.ddc file and delete
Initializing......done DDC loaded from database (368 variables). Dbvisit Replicate version 2.7.20_unreleased.5952 Copyright (C) Dbvisit Software Limited. All rights reserved. DDC file /home/oracle/<ddc_name>/<ddc_name>-MINE.ddc loaded. |
from the beginning and
OK-0: Completed successfully. |
from the end of the file.
Check that every parameter is printed on one line only. Sometimes you can find incorrect formatting like this:
*.DDC_PASSWORD = 53616c7465645f5f8098ca975d0f9e56cd1f7174ff6da2adfa304f82a50b1f1f |
Fix if necessary.
Remove all lines that do not set any value, for example:
*.FETCHER_PEER = |
(note: there can be a space character at the end of the line which causing parameters to be set incorrectly)
and comment them out by adding # sign at the beginning of the line (every occurrence means parameters with *., MINE., APPPLY., FETHCER. prefixes)
Configuring the process to use DDC file instead of DDC database does not mean that given process is not connecting to the database. It only means that the process does not read configuration parameters from the DDC database. You can disable access to the database completely by adding parameter MINE_PASSWORD into the list of parameters commented out in step 9. |