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-2347530.1
Update Date:2018-02-13
Keywords:

Solution Type  Problem Resolution Sure

Solution  2347530.1 :   SLConsole - Error Warn Info Logs Show Missing Information Between Logs Collected from Separate Times  


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




In this Document
Symptoms
Changes
Cause
Solution


Applies to:

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

Symptoms

Error, warn and info collected via SLConsole at different times has missing information.

Compared 2 Error-Warn files collected about 5 hours apart and found differences are warning messages had changed, while all error messages remained the same. To explain how this can happen is the Error-Warn file collected is concatenation of multiple current files from library log and does not contain any archive files.

See examples below:

log_error <<<<<<<<<<<<<<<<< current file
log_error.0 <<<<< archive file
log_error.1
log_error.2

log_warning <<<<<<<<<<<<<< current file
log_warning.0 <<<<< archive file
log_warning.1
log_warning.2

log_info <<<<<<<<<<<<<< current file
log_info.0 <<<<<<<< archive file

log_trace <<<<<<<<<<<<<< current file
log_trace.0 <<<<< archive file
log_trace.1
log_trace.2
log_trace.3
log_trace.4
log_trace.5
log_trace.6
log_trace.7
log_trace.8
log_trace.9
log_trace.10

Changes

 

Cause

 As a file reaches its size limit, new file is create as <log_xxxxx> and previous information is renamed <log_xxxxx.0> as archive. These files rotate quickly pending on how busy a library is.

Solution

Bottom line is the error-warn-info report log you collect from SLConsole are concatenation of current files and does not include files that are archived.

 


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