Contacting Support

Contacting Dbvisit Support servicedesk: http://support.dbvisit.com

Dbvisit Support is the single point of contact for all Dbvisit products. To help collect all the information needed by the support, Dbvisit Replicate contains a built-in trace file packaging facility. Use command SUPPORT PACKAGE process to create a zip file containing the files for the specified process, running this command in turn on FETCHER, MINE and APPLY servers.

$ dbvrep --ddcfile ORCL-MINE.ddc support package MINE
Initializing.....done
DDC loaded from database (124 variables).
Dbvisit Replicate version 
DDC file LINA.ddc loaded.
Packaging into ZIP file: dbvisit_support_dbvrep_MINE.7IPy.zip for process MINE, addinfo []
Trying retrieving +DATA/src/onlinelog/group_1.276.748600819 from ASM.
If this fails, restart with NOASM added to the SUPPORT command.
Packaging data from database. If this fails, restart SUPPORT PACKAGE with NODB option.
====> If instructed by support, run as SYSDBA the script get_logtrace.jTZ4.sql
and upload the generated tracefile (script will show the name) to Dbvisit Support as well.

The created file includes the process name and a unique identifier, so multiple runs of the packaging command won't overwrite past zip files.

The command can take further arguments, forcing it to skip some files – use it only if packaging otherwise fails.

Creating support package from command console

The support package command can also be run from the Command Console:

For MINE, ensure the command console is run from the MINE server so that the MINE logs and PLOGs can be found:

dbvrep> support package MINE
Packaging into ZIP file: ./dbvisit_support_dbvrep_d112f_mine.PNR_.zip for process mine, addinfo []
Packaging data from database. If this fails, restart SUPPORT PACKAGE with NODB option.
====> If instructed by support, run as SYSDBA the script get_logtrace.jsKz.sql and upload the generated tracefile (script will show the name) to Dbvisit Support as well.

Use the --nocheckdb option for creating a support package if creating the support package fails to connect to either the Mine or Apply database

dbvrep> support package MINE --nocheckdb

For APPLY, ensure the command console is run from the APPLY server so that the APPLY logs and PLOGs can be found:

dbvrep> support package APPLY
Packaging into ZIP file: ./dbvisit_support_dbvrep_d112f_apply.z9sJ.zip for process apply, addinfo []
Failed to open logfile /home/oracle/d112f/log/dbvrep_APPLY_d112f.log
Packaging data from database. If this fails, restart SUPPORT PACKAGE with NODB option.
====> If instructed by support, run as SYSDBA the script get_logtrace.jsKz.sql and upload the generated tracefile (script will show the name) to Dbvisit Support as well.

Or the command support package can be created with one command:

$ dbvrep --ddcfile ORCL-APPLY.ddc support package APPLY

Use the --nocheckdb option for creating a support package if creating the support package fails to connect to either the Mine or Apply database

dbvrep> support package MINE --nocheckdb

2-way replication

For 2-way replication 4 support packages can be created (MINE, APPLY, MINE1, APPLY1).

On the source server:

dbvrep --ddcfile ORCL-MINE.ddc support package MINE
dbvrep --ddcfile ORCL-APPLY1.ddc support package APPLY1

On the target server:

dbvrep --ddcfile ORCL-MINE1.ddc support package MINE1
dbvrep --ddcfile ORCL-APPLY.ddc support package APPLY