Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Backup Exec errors attempting backup of Oracle db

Created: 08 Nov 2011 | 1 comment

Hello - I'm trying to set up a backup of a new Oracle server and am having problems getting Backup Exec to connect to the db.  Using Backup Exec 2010 R2 SP1 on Server 2003 Enterprise x64 SP2, and Oracle server is Oracle 10.2.0.5 running on Server 2008 R2 Standard SP1.  The 1st problem I had was the backup failing and RMAN returning:

  # -----------------------------------------------------------------
 # RMAN command section
 # -----------------------------------------------------------------
 
 RUN {
 ALLOCATE CHANNEL ch0
     TYPE 'SBT_TAPE';
 SEND 'BSA_SERVICE_HOST=IP_of_server,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={A6E0433D-FDF9-4195-BD69-B3493EC9B836},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\server\orcl';
 BACKUP
     INCREMENTAL LEVEL=0
     FORMAT 'BE_U'
     DATABASE FORCE PLUS ARCHIVELOG FORCE;
 BACKUP CURRENT CONTROLFILE
     FORMAT 'BE_U';
 
 RELEASE CHANNEL ch0;
 }
 
connected to target database (not started)

using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 11/07/2011 16:26:16
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available

Recovery Manager complete. 

Following article TECH124389, I added INBOUND_CONNECT_TIMEOUT parameters to the listener.ora and sqlnet.ora files and restarted the listener.  When I tried again, I got the error:  Final error: 0xe000848c - Unable to attach to a resource.  Make sure that all selected resources exist ...

Following article TECH64606, I checked the authentication for both the server and the db.  Both returned Successful when tested under Resource Credentials.  When I tried again, I was back to the original RMAN error. 

Knocking my head on this - I'm baffled.  Any ideas?

Comments 1 CommentJump to latest comment