Versions Compared

Old Version 3

changes.mady.by.user Jakub Sejba

Saved on

compared with

New Version Current

changes.mady.by.user Jakub Sejba

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Run Setup Wizard as usually and create a new replication using all script generated by Setup Wizard.
  2. Do not start mine, apply and fetcher processes.
  3. Backup <ddc_name>-APPLY.ddc file on apply server.

  4. On mine server run

    Code Block
    sh start-console.sh show all > <ddc_name>-APPLY.ddc

  5. Open new <ddc_name>-APPLY.ddc file and delete

    Code Block
    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

    Code Block
    OK-0: Completed successfully.

    from the end of the file.

  6. Check that every parameter is printed on one line only. Sometimes you can find incorrect formatting like this:

    Code Block
    *.DDC_PASSWORD =
53616c7465645f5f8098ca975d0f9e56cd1f7174ff6da2adfa304f82a50b1f1f

    Fix if necessary.

  7. Remove all lines that do not set any value, for example:

    Code Block
    *.FETCHER_PEER =

    (note: there can be a space character at the end of the line which causing parameters to be set incorrectly)

  8. Add "memory_set " at the beginning of every line.
  9. Find every occurrence of the following parameters:
    • DDC_DATABASE
    • DDC_DATABASE_DBID
    • DDC_PASSWORD
    • DDC_SCHEMA
    • DDC_USER

    and comment them out by adding # sign at the beginning of the line (every occurrence means parameters with *., MINE., APPPLY., FETHCER. prefixes)

  10. Comment out all occurrences of MINE_PASSWORD parameter.
  11. Copy the new <ddc_name>-APPLY.ddc file from the mine server to the apply server.
  12. Do not change <ddc_name>-run-<hostname>.sh script on apply server. The script used to call the old apply ddc file which instructed the process to read all the parameters from the DDC database (see the load ddcdb command in the backed up script). Now the new apply ddc file contains all the parameters and does not read the DDC database.
  13. Start the replication (all processes) as usually.
Info

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.