01-18-2017 01:58 AM
I try to backup an Oracle DB Server which fails with the following message:
Server - db01.company.local Backup Exec server is running Backup Exec version 14.2.1180.3142 with FP-5. Set Information - Oracle-Linux::\\db01.company.local\DBORA001 The Database script returned an error. Refer to the Database script output section in job logs for more details. Business-critical resource backup error: Unable to back up resource Oracle-Linux::\\db01.company.local\DBORA001, which was tagged as business-critical. Ensure that the resource is online and then try again. RMAN Output Recovery Manager: Release 12.1.0.2.0 - Production on Wed Jan 18 10:29:10 2017 Copyright (c) 1982, 2015, Oracle and/or its affiliates. All rights reserved. RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows ORACLE error from target database: ORA-03113: end-of-file on communication channel Prozess-ID: 106074 Session-ID: 159 Seriennummer: 5566 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== ORA-03114: not connected to ORACLE # ----------------------------------------------------------------- # RMAN command section # ----------------------------------------------------------------- RUN { SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO 'BE_'; ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE'; SEND 'BSA_SERVICE_HOST=192.168.0.110,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={5B0EC2EF-6927-43FC-9458-57A4855D183B},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\db01.company.local\DBORA001'; BACKUP INCREMENTAL LEVEL=0 FORMAT 'BE_U' DATABASE FORCE PLUS ARCHIVELOG FORCE NOT BACKED UP DELETE INPUT; BACKUP CURRENT CONTROLFILE FORMAT 'BE_U'; RELEASE CHANNEL ch0; } executing command: SET CONTROLFILE AUTOBACKUP FORMAT RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of set command at 01/18/2017 10:29:11 ORA-03114: not connected to ORACLE EXIT Recovery Manager complete. Devices acquired: 1 Data streams used: 0 Job Completion Status Job ended: Wednesday, January 18, 2017 at 10:29:12 AM Completed status: Failed Final error: 0xe0000340 - The Database script returned an error. Refer to the Database script output section in job logs for more details. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-832 Errors Click an error below to locate it in the job log Backup- Oracle-Linux::\\db01.company.local\DBORA001The Database script returned an error. Refer to the Database script output section in job logs for more details. Exceptions Click an exception below to locate it in the job log Backup- Oracle-Linux::\\db01.company.local\DBORA001Unable to back up resource Oracle-Linux::\\db01.company.local\DBORA001, which was tagged as business-critical. Ensure that the resource is online and then try again.
I can see a few errors in the RMAN output but wasn't able to resolve it. Other servers don't have this problem. The Oracle Database server runs on 'Oracle Linux 7.3'.
Any ideas what's causing this?
Is the ORA-03113 message the root cause or maybe the RMAN-06901 message?
01-18-2017 07:20 AM
Fomr the Backup Exec can you ping db01.company.local? If not add it to your host file. It looks like Backup Exec is unable to resolve the name.
01-18-2017 10:46 AM - edited 01-18-2017 10:49 AM
Yep, I can reach db01.company.local just fine. I also added the server (hostname and FQDN) to the local hosts file as well. DNS name resolution back and forth is working as expected.
I also added IPC protocol to the listener.ora and restartet it in case RALUS uses this instead of TCP but no success.
BTW: I updated the backup server to version 2016 today (and also RALUS agent on the DB server. Issue still happens with the same error message.