Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1561479.1
Update Date:2017-09-27
Keywords:

Solution Type  Problem Resolution Sure

Solution  1561479.1 :   SL8500/SL3000 - Result Code 3260: "Failed To Backup Database Io Errorbackup Db: Stats"  


Related Items
  • Sun StorageTek SL3000 Modular Library System
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Remote
  •  




In this Document
Symptoms
Cause
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: This problem is transparent on SDP customer will see the error anyway.
Created from <SR 3-7308194483>

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to Not Applicable [Release All Releases to N/A]
Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

3260: "subId=2 Failed to backup database io errorbackup db: stats", exception=java.io.IOException

This message is presented via SDP.

Cause

3260 - (5X)
subId=2 Failed to backup database io errorbackup db: stats, exception=java.io.IOException: File /usr/local/idcard/db_backup/stats.db couldn't be removed for backup

  
This library error event is a library code error obviously indicating an i/o error attempting to update the stats database in non-volatile memory. It has no impact to operations and can be ignored.  There is no current work around and is not related to user permission levels.  Internally the code logs in as root to update files.
 
3260 - (5X)
subId=2 Failed to backup database io errorbackup db: stats, exception=java.io.IOException: File /usr/local/idcard/db_backup/stats.db couldn't be removed for backup
(Errors Started - 2013-06-08 13:23:15 Errors Stopped - 2013-06-12 13:23:15)


file permits are ok.
-rw-r--r-- 1 root 0 40960 Jun 1 13:23 stats.db

Solution

No actions are needed.  Should these errors become an issue, open a service request to the TSC, provide a SL8500/SL3000 LogSnap.  The issue will be reviewed for any related issues.

This error code does not indicate a problem with library performance.  The customer can re-open the Service Request if they have any questions.
 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback