When repeating incremental or differential backups using Oracle Agent, the job intermittently fails with a communications failure has occurred
| Article:TECH176686 | | | Created: 2011-12-12 | | | Updated: 2013-05-08 | | | Article URL http://www.symantec.com/docs/TECH176686 |
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
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
Environment
Backup Exec Oracle Agent
Oracle RDBMS 10g (Grid) and 11g (Grid)
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
Backup Exec 2010:
A hotfix is now available for this issue with Backup Exec 2010 R3 Rev 5204. Refer to the Hotfix link under Related Articles at the end of this article to obtain the hotfix needed to resolve the issue.
Backup Exec 2010 R3 Rev 5204 Hotfix 191248 - http://www.symantec.com/docs/TECH191248
Note : Please upgrade to 2010 R3 and apply the above fix if the above issue is encountered in a previous version of Backup Exec.
Backup Exec 2012:
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
|
|
| Source | Error Code |
| Value | 0XE000846B |
| Description | The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent |
| Source | Error Code |
| Value | 0xe000fe30 |
| Description | A communications failure has occurred |
| Source | ETrack |
| Value | 2642747 |
| Description | Repeating oracle inc/diff backups intermittently fail with 0xe000fe30. deadlock on BEDB is reported in the event log. |
| Source | ETrack |
| Value | 2733477 |
| Description | Repeating oracle inc/diff backups intermittently fail with 0xe000fe30. deadlock on BEDB is reported in the event log. |
Article URL http://www.symantec.com/docs/TECH176686
Terms of use for this information are found in Legal Notices
Thank you.