/
Create Support Package

Create Support Package

Creation of support package is extremely important procedure which will help you with resolving issues with Dbvisit Support. For Oracle database, there are two ways how to create support Package:

  • dbvctl support package

  • GUI support package

Dbvctl Support package contains information about the database and OS, but doesn’t contain any logfiles from dbvagentmanager or dbvcontrol.

GUI Support package contains all information from dbvagentmanager and dbvcontrol and can also contain all files present in dbvctl support package

1. 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.

1.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:

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

1.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:

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):

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

2. GUI Support Package

GUI support package will usually contain information from generic dbvctl support package in addition to dbvagentmanager and dbvcontrol tracefiles. Because of this, it’s usually significantly bigger than generic dbvctl support package.

1.1 Generic GUI Support package

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

image-20250224-124659.png

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

image-20250224-124834.png

 

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

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

1.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:

Related content