configuring RMAN
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: configuring RMAN

  1. #1
    Join Date
    Jul 2006
    Posts
    195

    configuring RMAN

    I am in the process of setting up RMAN. I have one DB, called PRI where
    I intend to put my target and catalog in my PRI DB.

    What I don't understand is why I need to create a orapwd file? Can't I
    just do something like this?

    rman target sys/sys@PRI catalog rman/rman@PRI

    I guess I have a few questions:

    1) When does the orapwd file come into play? What entry needs to
    be placed into it


    2) What is the default directory where the orapwd should be created?

    3) is target the really the "DB" am backing up? If not, how do you specify
    the DB to backed up

    4) Lastly lets say I have another DB called "sec" on another machine? would this be the syntax to use to connect

    rman target sys/sys@SEC catalog rman/rman@PRI

    As mentioned above, why do I need a orapwd and when will it get used?

    Thanks to all who answer this post?

    does yor
    ORACLE_SID need to be set correctly? Ie lets say I have another DB called
    "sec" on the same machine as PRI what command would I use to back that
    up? and would anything need to go into the orapwd file, if so what?

  2. #2
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    1. password file required to connect as a DBA user from remote machines. You need to create the password file with SYS / password and set the value for ENTRIES =
    2. $ORACLE_HOME/dbs in UNIX and $ORACLE_HOME\database in windows

    3. Yes, target is the DB that you want to backup

    4. Correct

    You need to use the correct service names when connecting to RMAN.

    This helps you to understand more about orapwd utility.

    http://www.oracleutilities.com/OSUtil/orapwd.html

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  3. #3
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    Quote Originally Posted by vnktummala View Post

    4. Correct
    If PRI is the DB that he wants to back up and SEC database has to be the catalog database, then the syntax is not correct. In this case, the connect string should be as follows if PRI identfies the service name of Primary database and SEC of seconday database:

    rman target sys/sys@PRI catalog rman/rman@SEC
    lucky

  4. #4
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    I have one DB, called PRI where
    I intend to put my target and catalog in my PRI DB.
    4) Lastly lets say I have another DB called "sec" on another machine? would this be the syntax to use to connect

    rman target sys/sys@SEC catalog rman/rman@PRI
    My understanding about question 4 is, the poster have a db called SEC and want to backup that DB.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  5. #5
    Join Date
    Jul 2006
    Posts
    195
    Now that you guys completely confused me lets try this again.

    As mentioned I have a DB called pri, which is my target DB and where
    I intend to put my catalog. In addition, all my access to the catalog will
    be done with the user RMAN/RMAN.

    For this situation, it sounds like I DONT need a password file for this situation
    am I correct?

    This would be the command line

    # backup PRI DB and access the catalog with rman user in pri. within pri
    # rman user has sysdba privs?

    rman target sys/sys@PRI catalog rman/rman@PRI

    My second situation is that I want to backup a DB called "sec", which
    is on a different machine as "pri" (catalog is in pri).

    For this situation, it sounds like I need an orapwd file to access the catalog
    in "pri" from the user "rman"

    # backup sec DB and access the catalog with rman user in pri. This command
    # will use the user "rman" in the orapwd file to access the catalog.

    rman target sys/sys@SEC catalog rman/rman@PRI

    The issue as I see it is that we can't get the privs for "rman" since we are
    using a different DB "sec" to backup, hence the need for the orapwd file.


    Do I have it right? Thanks for everybody's help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width