Page Comparison

...

The proper way to contacting Dbvisit Support is via the servicedesk: http://

...

support.dbvisit.com

...

We request that you only log one ticket per issue.
You may also want to check  the  Dbvisit Replicate knowledge base first if it is a question and not an error.

Dbvisit Support is the single point of contact for all Dbvisit products. To help collect all the information needed by the support team, Dbvisit Replicate contains a built-in trace file packaging facility. This will typically be the first item that a Dbvisit support technician will ask for. Use the command SUPPORT PACKAGE process_type to create a zip file containing the files for the specified process, running this command in turn on

...

FETCHER,

...

MINE and

...

$ ./dbvrep --ddcfile LINA.ddc support package MINE
Initializing.....done
DDC loaded from database (124 variables).
Dbvisit Replicate version 2.0.01.740
Copyright (C) Avisit Solutions Limited and Dbvisit Software Limited. All rights reserved.
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.APPLY servers.  More details on support packages can be found here:  Creating Support packages