Creation of support package is extremely important procedure which will help you with resolving issues with Dbvisit Support. In addition to normal support package, there is also possibility to use dbvctl to create dbvctl specific support package.

Dbvctl Support package is only a subset of normal Support package and contains information about the database and OS, but doesn’t contain any logfiles from dbvagentmanager or dbvcontrol. As a result, dbvctl support package is very small and can be used in cases dbvcontrol isn’t accessible.

1 1. Generating Support Package
2 2. Dbvctl Support Package
- 2.1 2.1 Generic Dbvctl Support Package
- 2.2 2.2 PID specific Dbvctl Support Package
3 3. Generating Support Package with Dbvisit StandbyMP 12.1
- 3.1 3.1 Generic GUI Support package
- 3.2 3.2 Task Specific GUI Support package

1. Generating Support Package

Users running Dbvisit StandbyMP version 12.1 need to either upgrade to newest version 12 release or use the procedure described at the end of this page

Dbvisit Support package functionality offers easy generation of support package including automatically needed tracefiles: user no longer needs to know the exact PID of the failed process, nor it is necessary to select failed task as it was in versions 11 or 10. You only need to input approximate time around which the failure occured.

This approach helps to prevent many roundtrips when communicating with Dbvisit Support, because all necessary tracefiles for troubleshooting the issue will be included. It is possible to use GUI and dbvcli to generate support package.

1.1 Time based Support Package in GUI

To create GUI Support package, go to ACTIONS pane and select “Create Support Package”:

Afterwards, select date and time when the failure occured:

You can select day (1) and time (2). if you want to generate support package for issue which just happened, simply click on suggested time, in this example 9:00 am (2).

Afterwards, you can select collection period (1) which is relative to the time you selected (2) and will include all traces generated “around” the time:

In this example traces from 5AM - 1PM would be included (selected time is 9AM -+ 4 hours). Once ready, click the “create” button (3).

The download will start automatically once the support package is completed.

1.2 Time based Support Package in CLI

It is possible to use also dbvcli to generate the support package. It follows the same concept as the GUI support package:

/usr/dbvisit/standbymp/bin/dbvcli -d <DDC> support-package

As when using GUI, you will need to enter target time and collection period “around” the target time. You can select destination directory on the host to which the support package will be downloaded.

Example:

[oracle@czlin0231]$ /usr/dbvisit/standbymp/bin/dbvcli -d SLASH support-package
Connecting to the Control Center at czlin0232:4433 ✓

Getting time from primary ✓

Support Package Period 1/2
Enter the target time when the problem occurred. The support package will
include data from around this time.

Time zone: CET (+01:00)
Format: 2026-01-20 08:42 or 2026-01-20T08:42

Target date and time:

> 2026-01-20 02:30

Support Package Period 2/2
Select the data collection time period, in hours.

Data collection time period:

( ) 4 hours
(•) 8 hours
( ) 12 hours
( ) Manual Entry

Creating support package ✓

Output Directory
Enter the directory in which to store the support package.

A file named sp-SLASH-20260120084331+0100.zip will be stored in this directory.

Output Directory:

> /home/oracle

Downloading support package ✓

Support package successfully downloaded to '/home/oracle/sp-SLASH-20260120084331+0100.zip'.

1.3 Task Specific Support package in GUI

You are able to create support package for any (failed) task which you see in the right task bar. Simply click on it:

And choose “Create Support Package”

the button will then change to “download support package” once the action is finished:

There is no dbvcli option for task-specific support package

2. Dbvctl Support Package

Dbvctl support package can be either generic, ot PID specific. Both contain same information, but PID specific support package will contain task specific tracefiles. If you’re not sure or don’t know the PID, generate generic support package and Dbvisit Support will guide you further.

Advantage of dbvctl support package is that it can be used also in case dbvcontrol isn’t available.

2.1 Generic Dbvctl Support Package

Generic Dbvctl support package is fast and easy way how to collect information about your system for Dbvisit Support. It is usually significantly smaller than dbvcontrol support package.

Generic Support package will never contain specific tracefiles for failed tasks such as CSD, SYNC etc ..

To Create dbvctl support package, run on primary as oracle user:

$ /usr/dbvisit/standbymp/oracle/dbvctl -d <DDC> -f support_package

The <DDC> string can be determined by executing:

$ ls -l /usr/dbvisit/standbymp/oracle/conf/dbv*env
-rw-r--r--. 1 oracle oinstall 26339 Feb 24 09:25 /usr/dbvisit/standbymp/oracle/conf/dbv_SLASH.env

So for this example the command you would need to run would be:

$ /usr/dbvisit/standbymp/oracle/dbvctl -d SLASH -f support_package

It is only ever needed to run the support package command on one of the servers. Support package will automatically download files from the other server.

If there are issues with network however, we recommend to run this command on primary and standby and upload both file to Dbvisit Support.

Resulting support package is generated in “support” directory as seen in the output:

$ /usr/dbvisit/standbymp/oracle/dbvctl -d SLASH -f support_package
Support package /usr/dbvisit/standbymp/oracle/support/sp_SLASH_202502241332.tar.gz
created.

Generation of support package can take up to few minutes. You can ignore occasional errors such as “broken pipe”.

2.2 PID specific Dbvctl Support Package

PID specific dbvctl support package contains all information present in dbvctl generic support package along with specific tracefiles for failed task. The PID must be specified when creating this support package:

$ /usr/dbvisit/standbymp/oracle/dbvctl -d <DDC> -f support_package -a pid=<PID>

You will be able to see the PID only if you would manually execute dbvctl command

The PID value can be always seen in task header in CLI (in this example 2820307):

$ /usr/dbvisit/standbymp/oracle/dbvctl -d SLASH
=============================================================
Dbvisit Standby Database Technology (12.1.0RC) (pid 2820307)
dbvctl started on czlin0231: Mon Feb 24 12:50:12 2025
=============================================================

>>> Obtaining information from standby database (RUN_INSPECT=Y)... done
    Thread: 1 Archive log gap: 4. Transfer log gap: 0
...

So for this example, the command to create PID specific dbvctl support package would be:

/usr/dbvisit/standbymp/oracle/dbvctl -d SLASH -f support_package -a pid=2820307

3. Generating Support Package with Dbvisit StandbyMP 12.1

Support package in 12.1 relies on the old concept of PID and task selection to provide necessary tracefiles. User can either choose to generate generic support package which will contain no tracefiles at all, or generate support package for specific

3.1 Generic GUI Support package

To create Generic GUI Support package, go to ACTIONS pane and select “Create Support Package”:

Leave selected the primary site (if primary is not accessible choose standby).

Do NOT use tracefile or PID fields, leave them empty.

Once the support package is created, download it to your client:

As with dbvctl support package, the creation can take several minutes.

3.2 Task Specific GUI Support package

You are able to create support package for any (failed) task which you see in the right task bar. Simply click on it:

And choose “Create Support Package”

the button will then change to “download support package” once the action is finished: