Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width5%

 

Column
width95
Panel

------------------------------------------------------------------------------

 You can create a standby database by transferring the database files directly 
to the standby server,
or by copying them to a temporary local location first. By using a temporary
location the time taken to place the database in backup mode is reduced.
If the database is very large then use a temporary location (answer No).
If either a primary or a standby database is ASM, you have to use a temporary
location (answer No).

Do you want to copy database files directly to the standby server? [Yes]:
Database files will be copied directly to the standby server: Y
Is this correct? <Yes/No> [Yes]: Y

 

 

7. It is possible to use secure shell (SSH) compression "on the fly" during transfer of the database files. Using SSH compression may speed up the transfer if the network is slow, however it may take additional CPU cycles:

...

12. The standby database will now be created. Once completed the next steps to take will be shown:

Section
Column
width10%5%

 

Column
width90%95%
Panel
bgColorCCC
Creating standby database... 
Backing up datafile 1...
Backing up datafile 2...
Backing up datafile 3...
Backing up datafile 4...
Backing up datafile 5...
Backing up datafile 10...
Creating standby controlfile controlfile...
Creating standby parameter file...
Backup of primary database completed.
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_10_87_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_1_81_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_1_82_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_2_83_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_3_84_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_4_85_1.piece...
Compressing /var/tmp/tmp1/dbv_dbvisitp_dbf_5_86_1.piece...
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_10_87_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_10_87_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_1_81_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_1_81_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_1_82_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_1_82_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_2_83_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_2_83_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_3_84_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_3_84_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_4_85_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_4_85_1.piece.gz ... 
Transferring /var/tmp/tmp1/dbv_dbvisitp_dbf_5_86_1.piece.gz to host
 dbvisit32.avisit.co.nz:/var/tmp/tmp2/dbv_dbvisitp_dbf_5_86_1.piece.gz ... 
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_10_87_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_1_81_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_1_82_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_2_83_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_3_84_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_4_85_1.piece.gz...
Uncompressing /var/tmp/tmp2/dbv_dbvisitp_dbf_5_86_1.piece.gz...
Shutting down standby database on dbvisit32.avisit.co.nz...
Standby database dbvisitp5 on dbvisit32.avisit.co.nz shutdown.

Remote spfile /oracle/orabase/product/10.1.0/Db_1/dbs/spfiledbvisitp5.ora
backed as
/oracle/orabase/product/10.1.0/Db_1/dbs/spfiledbvisitp5.ora.201111231612.
Remote spfile /oracle/orabase/product/10.1.0/Db_1/dbs/spfiledbvisitp5.ora
deleted.
Spfile created on the remote server.

Restoring standby control files...
Starting Standby Database dbvisitp5...
Standby Database dbvisitp5 started nomount.
Standby database dbvisitp5 on dbvisit32.avisit.co.nz startup nomount.

Shutting down standby database on dbvisit32.avisit.co.nz...
Standby database dbvisitp5 on dbvisit32.avisit.co.nz shutdown.

Standby control files restored.
Starting Standby Database dbvisitp5...
Standby Database dbvisitp5 started .
Standby database dbvisitp5 on dbvisit32.avisit.co.nz mounted.

Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_10_87_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_1_81_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_1_82_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_2_83_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_3_84_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_4_85_1.piece...
Catalog backup piece /var/tmp/tmp2/dbv_dbvisitp_dbf_5_86_1.piece...
Restoring datafile 1...
Restoring datafile 2...
Restoring datafile 3...
Restoring datafile 4...
Restoring datafile 5...
Restoring datafile 10...

=>Standby database created without tempfiles. If you wish to manually add
standby tempfiles please perform the following steps:
1. Run Dbvisit on the primary first, then on the standby to sync the newly
created standby database.
2. Open standby database in READ ONLY mode:
dbv_oraStartStop open dbvisitp
2. Add temporary files using SQL statement ALTER TABLESPACE ADD TEMPFILE
3. Restart standby database:
dbv_oraStartStop restart dbvisitp

Performing Oracle Checkpoint.
Waiting 3 seconds for log switch completion...

Standby database created.
To complete creating standby database, run dbvisit on the primary and standby
databases to ensure standby database is in synch with primary.

Please press <Enter> to continue...

...