Using disk refit

If there are no private devices in the cluster, disk refit operates as usual.

If there are one or more private devices in the cluster, disk refit becomes a two-phased operation:

StepsExecuting disk refit when there are private devices in the cluster

You must restore the sysdevices table correctly before you execute disk refit. Use the disk reinit command to add regular or private devices for any missing device entry in the sysdevices table.

For more information on restoring sysdevices, see the System Administration Guide, Volume 2.

  1. Restart the cluster in single-user mode. This is done by starting an instance in the cluster with the -m option. Single-user mode requires only one instance running in the cluster, and no other active connections to the cluster. You must set trace flag 3608.

  2. Issue the disk refit command on the instance. This removes all rows in sysdatabases and sysusages, and rebuilds parts of them from the devices in sysdevices, which are either regular sharable devices accessible by all instances in the cluster, or are private to this instance. At the end of Phase One, the cluster is shut down.

    Adaptive Server prints messages at the end of Phase One that indicate whether disk refit is complete. If it is not, Adaptive Server also prints messages to inform the user which other instances in the cluster have private devices and must perform Phase Two.

    Alternatively, you can use sp_refit_admin 'status' to find instances with private devices on which disk refit has not yet run.

    A sample output:

    1> sp_refit_admin 'status'
    2> go
    You need to run DISK REFIT on the following instances to refit their private devices. instance
    		devicestatus
    ------------------------------------------------------------
    		------------------------------------------------------------         --------------------------------------------------------------
    
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------cluster1_1private_dev1REFITPENDING(1 row affected)(return status = 0)
    
  3. For each instance that have private devices and which still have to run disk refit:

    • Start the instance using the -m option and trace flag 3608.

    • Issue disk refit on that instance.

    disk refit rebuilds sysdatabases and sysusages rows for private devices owned by this instance. When Phase Two for the instance is successfully completed, the cluster shuts down.

  4. Even if you see no errors while executing disk refit, you must check the consistency of sysdatabases and sysusages before resuming normal operation. “Troubleshooting” contains sample SQL statements that help to check and fix common problems encountered by disk refit.

  5. Resume normal operation.