Creating a standby database

[forum_admin]

Creating a standby database can either be done using the traditional method (using cold or hot backups) or using RMAN.

Please see the following documentation on how to create a standby database using both these methods.
For Linux/Unix: http://www.dbvisit.com/docs/Creating...base_linux.pdf

For Windows:
http://www.dbvisit.com/docs/Creating_a_standby_database_windows.pdf

RMAN does a very nice job of creating a standby database without having to take the database down.

Once the standby database is created, Dbvisit will ensure that the standby database is kept up to date.

[milka]

Hello,
I'm trying to make a standby database as you explain but I'm not able to connect the auxiliary database.

On the PRIMARY server :

orapwd file=pwdlsyb.ora password=pass entries=5
orapwd file=pwdlsybstby.ora password=pass entries=5

tnsnames=

lsyb =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ipPrimaryServer)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = lsyb)
    )
  )

lsybstby =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ipStandbyServer)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = lsyb)
    )
  )

listener=

listener_lsyb =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ipPrimaryServer)(PORT = 1521))
    )
  )

SID_LIST_listener_lsyb =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = lsyb)
      (ORACLE_HOME = /sw/app/oracle/product/10.2/db_1)
      (SID_NAME = lsyb)
    )
  )

#
# TRACE_LEVEL_LISTENER = ADMIN
SSL_CLIENT_AUTHENTICATION = FALSE

On the STANDBY server :

orapwd file=pwdlsyb.ora password=pass entries=5
orapwd file=pwdlsybstby.ora password=pass entries=5

tnsnames=

LSYB =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ipStandbyServer)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = lsyb)
    )
  )

listener=

SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = lsyb)
      (ORACLE_HOME = /sw/app/oracle/product/10.2/db_1)
      (SID_NAME = lsyb)
    )
  )

SSL_CLIENT_AUTHENTICATION = FALSE

LISTENER =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ipStandbyServer)(PORT = 1521))
  )

lsyb is open
lsybstby is nomount

I'm not able to connect standby database (lsybstby) from the primary server
ORACLE_SID=lsyb

oracle@> rman target / auxiliary sys/pass@lsybstby

Recovery Manager: Release 10.2.0.4.0 - Production on Fri Jun 12 14:58:43 2009

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: LSYB (DBID=43144853)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied

Can you help me please ?

[Mike Donovan]

Hello Milka,

Here are some initial things to check, in relation to the password file.

1. Just create the one password file on each server. The naming convention that Oracle will search for is: orapwSID. The SID must match the ORACLE_SID environment variable. (If orapwSID can not be found, Oracle will look for a file named orapw).

2. In addition to creating the password file, you must also set the init.ora parameter REMOTE_LOGIN_PASSWORDFILE to either SHARED or EXCLUSIVE (on both servers). It cannot be set to NONE, as this means that Oracle ignores any password file. Privileged users then have to be authenticated by the operating system - and this is actually the default value for this parameter.

3. Try logging into both databases, from the primary server, in this way:
$ sqlplus sys/pass@lsyb as sysdba
$ sqlplus sys/pass@lsybstby as sysdba

Are you now able to connect to the standby database?
Please let us know the result.

Kind regards,
Dbvisit support

[Arjen Visser]

With Dbvisit version 5.2 and onwards, the standby database can be created automatically. Rman is no longer needed.

Run dbvisit_setup:

=========================================================
     Dbvisit Standby Database Technology 
           http://www.dbvisit.com

     Dbvisit Database setup
       Default values will be shown in []

  Options:
       1) New Dbvisit Database setup (combines options 2,3,4)
       1a) New Dbvisit RAC Instance setup (combines options 2,3,4)

       2) New Dbvisit Database configuration (DDC) file setup
       3) New Dbvisit Archive Management Module (AMM) setup
       4) New Dbvisit Database repository (DDR) setup

       5) Manage Dbvisit Database repository (DDR)
       6) Update Dbvisit Database configuration (DDC) file

       7) Create Standby Database

       9) Uninstall Dbvisit Database repository (DDR)
       E) Exit

=========================================================
Please enter choice : 7

Choose option 7 to enter the create Standby Database sub menu and choose the method for creating the standby database:

     Create Standby Database sub menu

     Primary database will NOT be shutdown.
  Options:
       1) Create Standby Database (copy directly to standby server)
       2) Create Standby Database (using temporary location on dbvisit11)
       3) Create normal file system Standby Database from ASM primary database

       r) Return to main menu

       For slow networks or very large databases, the standby database may be
       created manually. Please see the Dbvisit User Guide for information.

=========================================================
Please enter choice :

Option 1 and 2 is for regular file system databases.
Option 3 is for ASM primary databases.

The standby database will now be automatically created on the standby server.