A Library Incidents

Oracle Enterprise Manager Ops Center relies on the library.xml file to manage and maintain the libraries that are backed by NFS shares. This file can be affected by operations that result in an incident being reported.

A.1 UUID is not recognized

Incident: library.xml file was deleted. Please try to recover with uuid <identifier>
Cause: The library.xml file contains the original UUID for the library. Because the library was deleted and created again, the library has a new UUID.
Action: Update the library.xml file with the new UUID.
  1. Edit the library.xml file.

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <LibraryData>
        <IsReadOnly>false</IsReadOnly>
        <UserFriendlyName>Local Storage Library (xvmsrv-005)</UserFriendlyName>
        <Description>Default virtual image local library</Description>
        <CreationTime>1382430667160</CreationTime>
        <ModificationTime>1382430667160</ModificationTime>
        <SemanticTags/>
        <UUID>d46372fa-1f39-4152-b082-7e501fda459d</UUID>
    </LibraryData>
     
    
  2. Change the UUID to the UUID displayed in the incident.

  3. Save and close the file.

  4. Run the OCDoctor utility to verify the library.xml file is in the correct state:

    /var/opt/sun/xvm/OCDoctor/toolbox/library-check.sh 
    
  5. If the OCDoctor output indicates a problem with the library, use the following command to associate the new UUID with the library's location:

    /var/opt/sun/xvm/OCDoctor/toolbox/library-check.sh -f <path/to/library>
    

A.2 Image information is missing

Incident: library.xml is missing some images. Number of images in the xml is n. Number of images in the directory is x.
Cause: Image files have been moved into the NFS share location but Oracle Enterprise Manager Ops Center does not manage them.
Action: Do the following
  1. Run the OCDoctor utility to verify that images are missing:

    /var/opt/sun/xvm/OCDoctor/toolbox/library-check.sh 
    
  2. Verify there is no current jobs that modify the library, such as actions that create a guest or add storage.

  3. Use the OCDoctor utility to restore the library's images:

    /var/opt/sun/xvm/OCDoctor/toolbox/library-check.sh -f <path/to/library> 
    
  4. Save and close the file.

  5. Run the OCDoctor utility to verify the library.xml file is in the correct state:

    /var/opt/sun/xvm/OCDoctor/toolbox/library-check.sh 
    

A.3 File is not readable

Incident: library.xml is corrupted.
Cause: Oracle Enterprise Manager Ops Center cannot open the file.
Action: Create a new library.xml file:
  1. Open a file with the name library.xml.

  2. Enter the following contents, using the format in the example:

    • isReadOnly = false

    • Description is empty. You can add or change using the Edit Attributes action.

    • CreationTime is the current time in EPOC time

    • ModificationTime is the current time in EPOC time

    • SemanticTags is empty.

    • UUID is the UUID displayed in the Incident Details message.

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <LibraryData>
        <IsReadOnly>false</IsReadOnly>
        <UserFriendlyName>Local Storage Library (xvmsrv-005)</UserFriendlyName>
        <Description>Default virtual image local library</Description>
        <CreationTime>1382430667160</CreationTime>
        <ModificationTime>1382430667160</ModificationTime>
        <SemanticTags/>
        <UUID>d46372fa-1f39-4152-b082-7e501fda459d</UUID>
    </LibraryData>