DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: RMAN

  1. #1
    Join Date
    Aug 2000
    Posts
    52
    Hello Friends...
    I am usinfg rman while resyncing the catalog i am getting following error .
    Can some one help me ?

    Sanjay

    RMAN> resync catalog;

    RMAN-03022: compiling command: resync
    RMAN-03023: executing command: resync
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-20029: cannot make a snapshot controlfile
    RMAN-03026: error recovery releasing channel resources
    RMAN-00569: ================error message stack follows================
    RMAN-03006: non-retryable error occurred during execution of command: resync
    RMAN-07004: unhandled exception during command execution on channel default
    RMAN-10035: exception raised in RPC: ORA-00230: operation disallowed: snapshot c
    ontrolfile enqueue unavailable
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 1826
    RMAN-10031: ORA-230 occurred during call to DBMS_BACKUP_RESTORE.CFILEMAKEANDUSES
    NAPSHOT

  2. #2
    Join Date
    Feb 2001
    Posts
    163
    From Metalink

    ----------------------------------------------------------------

    Problem Description
    --------------------

    You are trying to run a backup, and the backup job fails because RMAN cannot
    make a snapshot control file. The message stack is as follows:

    RMAN-08502: set_count=11 set_stamp=333299261
    RMAN-08010: channel dev1: including datafile 1 in backupset
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-08512: waiting for snapshot controlfile enqueue
    RMAN-20029: cannot make a snapshot controlfile
    RMAN-03026: error recovery releasing channel resources
    RMAN-08031: released channel: dev1
    RMAN-00569: ================error message stack follows================
    RMAN-03006: non-retryable error occurred during execution of command: backup

    RMAN-07004: unhandled exception during command execution on channel dev1
    RMAN-10032: unhandled exception during execution of
    job step 1: ORA-06512: at line 90
    RMAN-10035: exception raised in RPC: ORA-00230:
    operation disallowed: snapshot controlfile enqueue unavailable
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 1826
    RMAN-10031: ORA-230 occurred during call to
    DBMS_BACKUP_RESTORE.CFILEMAKEANDUSESNAPSHOT


    Solution Description
    ----------------------

    When RMAN needs to back up or resynchronize from the control file, it first
    creates a snapshot or consistent image of the control file. If one RMAN job is
    already backing up the control file while another needs to create a new snapshot
    control file, then you may see the following message:

    RMAN-08512: waiting for snapshot controlfile enqueue


    Under normal circumstances, a job that must wait for the control file enqueue
    waits for a brief interval and then successfully retrieves the enqueue.
    Recovery Manager makes up to five attempts to get the enqueue and then fails the
    job. The conflict is usually caused when two jobs are both backing up the control
    file, and the job that first starts backing up the control file waits for service
    from the media manager.

    To determine which job is holding the conflicting enqueue:

    1. After you see the first RMAN-08512: waiting for snapshot controlfile enqueue
    message, start a new SQL*Plus session on the target database:

    % sqlplus sys/sys_pwd@prod1


    2. Execute the following query to determine which job is causing the wait:

    SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
    FROM v$session s, v$enqueue_lock l
    WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2;


    You should see output similar to the following (the output in this example has
    been truncated):

    SID User Program Module Action Logon
    --- ---- -------------------- ------------------------- ---------------- ---------
    9 SYS rman@h13 (TNS V1-V3) backup full datafile: c1 0000210 STARTED 21-JUN-99


    After you have determined which job is creating the enqueue, you can do one of the
    following:

    - Wait until the job creating the enqueue completes
    - Cancel the current job and restart it once the job creating the enqueue completes
    - Cancel the job creating the enqueue

    Commonly, enqueue situations occur when a job is writing to a tape drive, but the tape
    drive is waiting for a new cassette to be inserted. If you start a new job in this
    situation, you will probably receive the enqueue message because the first job cannot
    complete until the new tape is loaded.


    References
    ----------
    Oracle8i Recovery Manager User's Guide and Reference
    Release 2 (8.1.6)
    Part Number A76990-01
    .


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