Amazon Partner

Thursday 10 February 2011

Building Standby database ( without backup) from Primary Database

Oracle 11g has many feature which allow DBA's manage there database more esily and quickly. One of the feature which made DBA's life much easy is build standby database without backup i.e. building from Primary/Active Database.

This feature comes with following benifits.
* No Need to backup
* NO need to sheep backup to Standby server,
* No hessle of Mounting backup to Standby server as nfs or anything like that.

Building standby database is done using RMAN command DUPLICATE which we used before to duplicate database.


Step by Step.

1. Create pfile from spfile on the primay database.

2. scp pfile to new server.
3. edit pfile
4. Create spfile
5. startup nomount;
6. Create listener and Tnsnames.
7. Start standby database using RMAN duplicate database
$ rman

Recovery Manager: Release 11.2.0.2.0 - Production on Thu Feb 10 22:18:23 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

RMAN> CONNECT TARGET SYS/password@DB_DG_SITEB
connected to target database: DBPRD (DBID=39856714)

RMAN> Connect auxiliary SYS/password@DB_DG_SITEA
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04006: error from auxiliary database: ORA-01031: insufficient privileges

Above error occured if you forget to copy password file from primary site.
Fix this by coping password file from primary/production site.

SITEA>scp $ORACLE_HOME/dbs/orapwDBPRD1 oracle@SITEB:$ORALE_HOME/dbs/orapwDBPRD1

RMAN> Connect auxiliary SYS/password@DB_DG_SITEA
connected to auxiliary database: DBPRD (not mounted)




DUPLICATE TARGET DATABASE
FOR STANDBY
FROM ACTIVE DATABASE;

Thursday 3 February 2011

Ho to Manually Configure Database Vault Administrator Configuration for Grid Control


Deploying Database Vault Administrator to the Database Console OC4J Container

To manually deploy Database Vault Administrator to the Database Console OC4J container:
  1. Stop Oracle Database Console.
    • UNIX: Go to the $ORACLE_HOME/bin directory and run the following command:
      ./emctl stop dbconsole
      
    • Windows: In the Administrative Services, select the Services utility, and then right-click the OracleDBConsolesid service. Select Stop from the menu.
  2. Create a backup copy and then open the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/server.xml file.
  3. Add the following line before the  element:
    
    
    On Windows systems, replace $ORACLE_HOME with the absolute path to your Oracle Database home.
  4. Create a backup copy and then open the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/http-web-site.xml file.
  5. Add the following line before the element:
    
    
  6. Restart Oracle Database Console.
    • UNIX: Go to the $ORACLE_HOME/bin directory and run the following command:
      ./emctl start dbconsole
      
    • Windows: In the Administrative Services, select the Services utility, and then right-click the OracleDBConsolesid service. Select Start from the menu.
After you complete these steps, you can start Oracle Database Vault Administrator by using the following URL:
https://hostname:port/dva
For example:
https://myserver:1158/dva
If you are unsure of the port number, open the ORACLE_HOME/host_sid/sysman/config/emd.properties file and search for REPOSITORY_URL. In most cases, the host name and port number are the same as Oracle Enterprise Manager Database Control.