Oracle Online Backup Problem.

[Baiju_2]

Hi,

We are faing a problem in oralce online backup tru Omniback.

The error reported is as follows.

This seems to be some permission problem in omniback config. If any body faced this problem please update us.



RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel dev_0
RMAN-10035: exception raised in RPC: ORA-00230: operation disallowed: snapshot controlfile enqueue unavailable
RMAN-10031: ORA-230 occurred during call to DBMS_BACKUP_RESTORE.CFILEMAKEANDUSESNAPSHOT

[T G Manikandan]

RMAN troubleshooting guide
//*
Backup Fails Because of Control File Enqueue: Scenario
In this scenario, a backup job fails because RMAN cannot make a snapshot control file. The message stack is as follows:

set_count=11 set_stamp=333299261
channel dev1: including datafile 1 in backupset
waiting for snapshot controlfile enqueue
waiting for snapshot controlfile enqueue
cannot make a snapshot controlfile
error recovery releasing channel resources
released channel: dev1

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
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

Backup Fails Because of Control File Enqueue: Diagnosis
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:

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 obtains 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:

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

% sqlplus 'SYS/sys_pwd@prod1 AS SYSDBA'


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-01

Backup Fails Because of Control File Enqueue: Solution
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 after 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, then you will probably receive the enqueue message because the first job cannot complete until the new tape is loaded.

*//

[Kurt Beyers.]

Baiju,

What is your config? I guess OB is your central backup solution.What is the release of OB and Oracle? Are you using a recovery catalog or are you storing it into the control file?

If you check your configuration from Omniback, is it successfull? If you run a preview backup, is it successfull? Have you installed the patches for Oracle of Omniback?

Kurt