Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

How to Unregister Older Unused Versions of the Resource Type

If you have migrated all existing resources to the newest version of the resource type and have no further need for the older version of that resource type, unregister the older versions.

  1. On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
  2. Retrieve a list of the registered resource type versions and unregister the version you no longer wish to use.
    # clresourcetype list | grep myrt
    XYZ.myrt:1.0
    XYZ.myrt:2.0
    # clresourcetype unregister XYZ.myrt:1.0
  3. If the resource type has the RT_system property set to TRUE, you must set it to FALSE before you can remove the resource type.

    If the following text appears after you run clresourcetype unregister from Step 2, you must set the property to TRUE by typing the commands that appear below the output below.

    clrt: (C944871) Operation not allowed on system resource type <XYZ.myrt:1.0>
    # clresourcetype set -p RT_system=FALSE XYZ.myrt:1.0
    # clresourcetype unregister XYZ.myrt:1.0

    By default, the RT_system property by default is set to TRUE on the preinstalled resource types LogicalHostname and SharedAddress. If you have upgraded to a newer version of one of these preinstalled resource types, you will have to set RT_system to FALSE before unregistering the older version. In this example, all of the existing LogicalHostname resources have been migrated to version 4.0 of LogicalHostname.

    # clresourcetype list
    …
    SUNW.LogicalHostname.3
    SUNW.LogicalHostname:4
    …
    # clresourcetype set -p RT_system=FALSE SUNW.LogicalHostname:3
    # clresourcetype unregister SUNW.LogicalHostname:3