When repeating incremental or differential backups using Oracle Agent, the job intermittently fails with a communications failure has occurred

Problem

When repeating incremental or differential backups using Oracle Agent, the job intermittently fails with "0xe000fe30 - A communications failure has occurred" in the RMAN Output section of the job log.

When this issue occurs, event ID 57345 is reported with a deadlock message on the media server.

 

Error Message

RMAN Output Section

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/14/2011 12:50:41
ORA-19506: failed to create sequential file, name="BE_qkmu6icv_1_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   BEError(0xe000fe30) A communications failure has occurred.

Job Completion Status
Final error: 0xe000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.
Make sure that the correct version of the Remote Agent is installed and running on the target computer.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.
Final error category: Resource Errors
 

Application Event Log 

Event ID: 57345

Source: Backup Exec

Description:
Database Exception Context:Query JobHistory Error:-536837662: :: -2147467259:Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. :: DB Error Set 0: native=0x4b5 source=Microsoft OLE DB Provider for SQL Server hr=0x80004005 Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Cause

This is a timing issue to access to Backup Exec database (BEDB.)

A Low frequency of occurrence is observed with Backup Exec 2010 R3 and Backup Exec 2012.

Solution

A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

Backup Exec 2010R3 Rev 5204 Hotfix 191248 (TECH191248)
Backup Exec 2012 Rev 1798 Service Pack 2 (TECH203155)
 


Applies To

Backup Exec Oracle Agent

Oracle RDBMS 10g (Grid) and 11g (Grid)

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)