http://appsdbasworld.blogspot.com

appsdbasworld

 
APPS R12
  • R12.AD.A.DELTA.4 Patch
  • Disable concurrent manager
  • Increasing the number oacore process type(JVM) and...
  • Release12 installation
  • InitSID.ora settings for release12
  • Creating custom top in release12
  • Changing apps password
  • Apps questions
  • Workflow Notification Mailer Setup
  • Schedule downtime in R12
  • Enable/Disable restrict session of Apache
  • APPS 11i
  • Indian localization patch
  • Opening forms from linux machine
  • Replacing Jinitiator with JRE for Oracle Apps 11i
  • Enabling SSL for E-Business suite 11i
  • Executing gather schema statistics at backend
  • Cleaning temporary tablespace
  • How to check versions
  • How to find patchset level
  • Cleaning concurrent manager tables
  • Database General
  • Create A Production (Full or Partial) Duplicate On...
  • Creating a Duplicate Database on a New Host Using ...
  • Database Cloning
  • 11g top new features
  • New background processes in 10g
  • 10g Data Pump
  • Installing Oracle Database 9i (9.2.0.8) on RHEL 4
  • Query to kill inactive sessions
  • Installing 11g(11.1.0) database on Redhat Linux 4
  • Check Deprecated Initialization Parameters in 11g
  • Online backup 9i & 10g
  • Enable/Disable archivelog in 9i
  • Creating recovery catalog in remote database
  • Creating database with create database command
  • Application Server
  • web cache cloning
  • 10g AS installation with linux
  • Operating System
  • Script to start/stop R12 services
  • Basic commands to check system statistics
  • Statspack analyzer
  • Analyze your statspack report
  • Search
    Only search this Blog
    E-mail Subscription

    Enter your email address:

    Delivered by FeedBurner

    Others Coming Soon!
    Your Ad Here
    Creating recovery catalog in remote database
    Monday, June 16, 2008
    Server A - Target database (PROD)
    Server B - Recovery Catalog database (catdb)

    General settings:
    -----------------
    1. RDBMS version and OS version should be same in Server A
    and Server B.
    2. Server A and B should ping each other. Check each other
    entries in /etc/hosts file.
    3. Copy the tnsname.ora entry (server A) add it in server B
    tnsname.ora entry and vice versa. Then check tnsping is happening to each other.

    Step -1: Create password file on target DB (server A)
    -------

    $orapwd file=orapwORACLE_SID (filename) password=password
    Eg: - $orapwd file=orapwPROD password=rolta2k
    (oracle password file default file location is
    $ORACLE_HOME/dbs)
    Then,
    Add parameter remote_login_passwordfile=EXCLUSIVE in
    server A initSID.ora
    And bounce the database once.

    After done this settings you should be able to connect
    server A from server B vice versa through sqlplus.

    Eg: - From Server B just execute,
    $sqlplus sys/sys@PROD as sysdba
    vice versa from server A also,

    Step -2: Create tablespace for recovery catalog to store
    --------
    the target database information in catdb(server B).

    Connect to catalog DB (Server B) where you we need to
    configure the recovery catalog.
    $sqlplus “/as sysdba”


    sql>CREATE TABLESPACE rman
    DATAFILE '/u02/app/oradata/rman/rman01.dbf' size 500m;

    Step -3: Create the Recovery Catalog Owner in the new
    --------
    database(CATDB)

    Sql>CREATE USER rman IDENTIFIED BY rman
    DEFAULT TABLESPACE rman
    QUOTA UNLIMITED ON rman;

    Step –4:Grant the necessary privileges to the schema owner
    --------

    sql> GRANT connect, resource, recovery_catalog_owner TO rman;

    Here the role \"RECOVERY_CATALOG_OWNER\" provides the user
    with all privileges required to maintain and query the
    recovery catalog.

    Step –5:Creating the Recovery Catalog
    --------

    Connect to the Server -B which will contain the catalog as
    the catalog owner.
    $ rman catalog rman/passwd@catdb

    Eg: - $rman catalog rman/rman@UAT04

    Recovery Manager: Release 10.2.0.2.0 - Production
    Copyright (c) 1982, 2005, Oracle. All rights reserved.

    Connected to recovery catalog database

    Step –6:Run the CREATE CATALOG command to create the catalog
    --------

    RMAN> CREATE CATALOG;

    recovery catalog created

    Step – 7: Registering Target Database in the Recovery Catalog
    ---------

    Connect to the target(Server A) database and recovery
    catalog database(Server B). Execute this in catdb(server B)

    $ rman target sys/passwd@prod catalog rman/passwd@catdb

    Eg: - $rman target sys/sys@NPROD catalog rman/rman@UAT04

    Then, register the target database in recovery catalog
    RMAN> REGISTER DATABASE;
    Then, to identify whether has registered properly, execute
    the below command

    RMAN> REPORT SCHEMA;

    It will show the target database (Server A) datafile paths.


    For additional reference:
    -------------------------

    http://download.oracle.com/docs/cd/B19306_01/backup.102/
    b14194/rcmsynta045.htm#sthref722

    http://www.dbapool.com/articles/04110701.html

    http://www.oracle-base.com/articles/9i/RecoveryManager9i.php

    Metalink Doc ID: 360416.1
    Subject: Oracle10g - Getting Started with Recovery Manager(RMAN)
    posted by Senthil Kumaran @ 11:57 PM  
    0 Comments:
    Post a Comment
    << Home
     
    About Me

    Name: Senthil Kumaran
    Home: Oslo, Oslo, Norway
    About Me: I'm working as a oracle applications dba(Apps DBA OCP) and fusion middleware.This views are my own only and not neccessary to match with others
    See my complete profile Add to Technorati Favorites
    Previous Post
    Archives
    Links
    Powered by

    BLOGGER

    Add On

    Add to Google

    Add to My AOL

    Subscribe in Bloglines

    Subscribe in NewsGator Online

    © Oracle AppsDBAs World Blogspot Template by SENTHIL KUMARAN SL