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-71-1016428.1
Update Date:2017-09-29
Keywords:

Solution Type  Technical Instruction Sure

Solution  1016428.1 :   VSM - What Can Cause A VTV To Become Fenced?  


Related Items
  • Sun StorageTek Virtual Tape Control Software (VTCS)
  •  
  • Sun StorageTek Enterprise Library Software (ELS)
  •  
  • Sun StorageTek VSM System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Library Software>SN-TP: MAINSW VTCS
  •  

PreviouslyPublishedAs
226112


Applies to:

Sun StorageTek Virtual Tape Control Software (VTCS) - Version 6.2 and later
Sun StorageTek Enterprise Library Software (ELS) - Version 7.0 and later
Sun StorageTek VSM System - Version 4 and later
IBM z/OS on System z

Goal

 What can cause a VTV to become fenced?

Solution

A fenced VTV can be a result of:

  • Failed Recall
  • VTSS takes a warm boot (restarts itself).
  • VTV was mounted and being written to during a power hit.
  • One or more hosts writing to a different CDS than is being used by other hosts.
  • The status of the VTV is not as expected as logged in the CDS.

This list is not all inclusive; it is possible there are other symptoms that can result in a fenced VTV.

For information regarding how to resolve the fenced VTV, please review the following documents:

  • How to Clear a Fenced VTV When There is a Good Copy on MVC <Document 1013163.1>
  • How to Clear a Fenced VTV When There is NOT a Good Copy on MVC <Document 1015872.1>

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