Rman error when duplicating a database with Rman
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Rman error when duplicating a database with Rman

  1. #1
    Join Date
    Mar 2004
    Location
    IA USA
    Posts
    257

    Rman error when duplicating a database with Rman

    DBAs,

    I was trying to duplicate a database locally using Rman.
    I started the auxiliary database with nomount from sql*plus.
    But when I tried to allocate the auxiliary channel.
    I got the following error:
    (The weird thing is that I can correctly connect to the aux database as shown in the following.)

    MAN> CONNECT AUXILIARY sys/lily@ODLILY

    connected to auxiliary database (not started)

    RMAN> RUN {
    2>
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;}

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of allocate command at 11/02/2005 11:24:40
    RMAN-06403: could not obtain a fully authorized session
    RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    IBM AIX RISC System/6000 Error: 2: No such file or directory


    Any idea?
    Thanks!

  2. #2
    Join Date
    Jul 2002
    Location
    Lake Worth, FL
    Posts
    1,469

    Cool


    Maybe you are not following the correct instructions in the manual!
    "The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb

  3. #3
    Join Date
    Nov 2001
    Posts
    335
    Your auxilary database should be started in nomount mode.

    connected to auxiliary database (not started)
    One, who thinks that the other one who thinks that know and does not know, does not know either!

  4. #4
    Join Date
    Mar 2004
    Location
    IA USA
    Posts
    257
    Thanks for the input.

    I made sure that I startup the aux database with nomount mode.

    SQL> select INSTANCE_NAME ,STARTUP_TIME,DATABASE_STATUS from v$instance;

    INSTANCE_NAME STARTUP_T DATABASE_STATUS
    ---------------- --------- -----------------
    ODLILY 02-NOV-05 ACTIVE

  5. #5
    Join Date
    Nov 2001
    Posts
    335
    So, did it help your problem or was it already in nomount stage at the time youll got the error?
    One, who thinks that the other one who thinks that know and does not know, does not know either!

  6. #6
    Join Date
    Mar 2004
    Location
    IA USA
    Posts
    257
    Thanks,

    I solved this problem. But without knowing why.

    Originally, I did like this:
    export ORACLE_SID=ODLILY( the aux database)
    and then log into rman.
    rman> CONNECT AUXILIARY sys/lily@ODLILY
    got the error.

    Then, I changed to:
    rman> CONNECT AUXILIARY sys/lily
    (without the @ODLILY)
    It worked.

  7. #7
    Join Date
    Nov 2001
    Posts
    335
    Your tnsnames.or has an entry pointing to the location where database was not running. When you removed @ you picked up local database .
    One, who thinks that the other one who thinks that know and does not know, does not know either!

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