Support packages can be created automatically by the process or the user can create the support package. There are two separate ways to create support packages. The result is the same. The name of the file will be dbvisit_support_dbvrep_<process_type>.unique_id.zip.
...
| No Format |
|---|
|
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. |
| Note |
|---|
Use the --nodb NODB option for creating a support package if creating the support package fails to connect to either the Mine or Apply database | No Format |
|---|
dbvrep> support package MINE --nodbNODB |
|
| Note |
|---|
On the Windows operating system, the default location for the support package is in start folder of the application, when start-console is run as a Windows Administrator the default folder will be %WINDOWS%\System32. This is feature of Windows not Dbvisit Replicate. |
...
| No Format |
|---|
|
$ dbvrep --ddcfile ORCL-APPLY.ddc support package APPLY |
| Note |
|---|
Use the --nodb NODB option for creating a support package if creating the support package fails to connect to either the Mine or Apply database | No Format |
|---|
dbvrep> support package MINEAPPLY --nodbNODB |
|
Creating the APPLY support package from command line
...