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-1332389.1
Update Date:2018-05-24
Keywords:

Solution Type  Problem Resolution Sure

Solution  1332389.1 :   FSC3E40 Subsystem is out of Conditional Capacity  


Related Items
  • Sun StorageTek VSM System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
  •  
  • _Old GCS Categories>Announcements>All Product Lines>Support Systems
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Applies to:

Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Information in this document applies to any platform.

Symptoms

Customer's system receives FSC3E40 when subsystem is out of conditional capacity.  The VSM has reached 100%.  The VTDs start receiving intervention required messages and can not mount VTVs


Changes

 

Cause

The VTSS reached 100%.  The box is full of data and can not either recall any VTVs or create new VTVs.

Solution

The customer should monitor their subsystem and work data off as soon as possible.
Commands to keep abreast of when this issue happens:

VT D A DET - Verify the particular VSM has Active migrates
VT D Q DET - Verify the particular VSM does not have queued processes
VT D VTSS - Display the VSM to verify the DBU percentage
VT D RTD - Review RTDs to verify if there are hardware issues

If this does not bring anything up that is the cause, it may be necessary to pause initiators so jobs do not request those VTDs on the VSM until the DBU has had time to work down.

References

<NOTE:1332413.1> - VSM - FSC3E41 & FSC3E42 Production Partition Conditional Capacity Low Threshold Reached

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