Forum Discussion

userconnect's avatar
userconnect
Level 3
11 years ago

Backup Exec with Oracle RAC 11g

Hello,

Any idea about this error and how can I resolve it ?

I have BE 2012 SP3 and windows 2008 R2 SP1 and I need to backup Oracle RAC on windows 2008 server.

thanks

 

Le script de la base de données a renvoyé une erreur. Pour plus d'informations, dans les journaux des travaux, reportez-vous à la section de sortie du script de la base de données.
Sortie RMAN 
Recovery Manager: Release 11.2.0.4.0 - Production on Tue Feb 18 16:47:16 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

 
connected to target database: DBOCT (DBID=631434509)

 
 
 # -----------------------------------------------------------------
 # RMAN command section
 # -----------------------------------------------------------------
 
 RUN {
 ALLOCATE CHANNEL ch0
     TYPE 'SBT_TAPE';
 SEND 'BSA_SERVICE_HOST=172.20.53.210,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={C51D77C9-4954-405D-9AF0-97B251F41C72},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\RAC-DBOCT-631434509\DBOCT';
 BACKUP
     FULL
     FORMAT 'BE_U'
     TABLESPACE
         'OCT' FORCE;
 
 RELEASE CHANNEL ch0;
 }
using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: SID=739 instance=dboct2 device type=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0

sent command to channel: ch0

Starting backup at 18-FEB-14
channel ch0: starting full datafile backup set
channel ch0: specifying datafile(s) in backup set
input datafile file number=00007 name=+DGDATA/dboct/datafile/oct.282.831899057
input datafile file number=00008 name=+DGDATA/dboct/datafile/oct.283.831899073
channel ch0: starting piece 1 at 18-FEB-14
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch0 channel at 02/18/2014 16:47:21
ORA-19506: echec de creation du fichier sequentiel, nom="BE_6mp0uo0o_1_1", parms=""
ORA-27028: skgfqcre : sbtbackup a renvoye une erreur
ORA-19511: Erreur recue de la couche de gestionnaire de supports, texte du message d'erreur :

 EXIT

Recovery Manager complete.

Périphériques acquis : 1 Flux de données utilisés : 0

Etat de fin du travail 
Fin du travail : mardi 18 février 2014 à 16:45:18
Etat de fin : Echec
Erreur finale : 0xe0000340 - Le script de la base de données a renvoyé une erreur. Pour plus d'informations, dans les journaux des travaux, reportez-vous à la section de sortie du script de la base de données.
Catégorie d'erreur finale : Erreurs des ressources

 

2012
Agent for DB2 on Windows Servers
Agent for Lotus Domino
Agent for Oracle on Windows or Linux Servers
Agents
Backing Up
Backup and Recovery
Backup Exec
Backup Exec (media server only)
Best Practice
  • Siddhant_Saini's avatar
    Siddhant_Saini
    Level 6
    11 years ago

    Hello,

    This error usually occurs if the user doesn't have SYSDBA Database level credentials. I'd request you to refer to the following articles and check the configuration: 
    1. About backing up Oracle RAC resources: http://www.symantec.com/docs/HOWTO24311

    2. Configuring database access on the media server for Oracle operations in Backup Exec 2012: http://www.symantec.com/docs/TECH193196

    3. Install and configure Oracle Agent(for BE 11d and later(the options would be slightly different in BE2012)): http://www.symantec.com/docs/TECH49969

  • userconnect's avatar
    userconnect
    Level 3
    11 years ago

    Hello,

    I checked all the needed informations and i found that this Admin user of Backup exec belong to oracle DBA group and have all permissions allowed.The agent is also well configured on every node with their instances and their authentifications.

    Any other ideas?

    thanks

     

  • Siddhant_Saini's avatar
    Siddhant_Saini
    Level 6
    11 years ago

    If the configuration is fine then the only thing remaining is to log a case with Symantec Support to diagnose the issue further.