...
| 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 |
|---|
Although a default place for On the Windows operating system, the default location for the support package is a in start folder of the application, when start-console is ran run as a Windows Administrator the default folder will be %WINDOWS%\System32. This is feature of Windows not Dbvisit Replicate. |
Creating the APPLY support package from command line.
...
| 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
For APPLY, ensure the command console is run from the APPLY server so that the APPLY logs and PLOGs can be found. If you run the support package from the SOURCE server (where most people typically run dbvrep) it will NOT include the log file and the PLOG. Please get the log file as well and the PLOG from the target server.
Or you can install the ./start_console.sh script on the target server, run the dbvrep console from there as show below.
...