...
| 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 --nocheckdb option for creating a support package if creating the support package fails to connect to either the Mine or Apply database
|
For APPLY, ensure the command console is run from the APPLY server so that the APPLY logs and PLOGs can be found:
| No Format | ||
|---|---|---|
| ||
dbvrep> support package APPLY Packaging into ZIP file: ./dbvisit_support_dbvrep_d112f_apply.z9sJ.zip for process apply, addinfo [] Failed to open logfile /home/oracle/d112f/log/dbvrep_APPLY_d112f.log 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. |
...
Or the command support package can be created with one command:
| No Format | ||
|---|---|---|
| ||
$ dbvrep --ddcfile ORCL-APPLY.ddc support package APPLY |
...
| Note | ||
|---|---|---|
Use the --nocheckdb option for creating a support package if creating the support package fails to connect to either the Mine or Apply database
|
2-way replication
For 2-way replication 4 support packages can be created (MINE, APPLY, MINE1, APPLY1).
...