Progress
Version 9
Product Update Bulletin


PROCLUSTER Command

A Failover Clusters command that starts an automated failover process for a Progress database and its related resources. Failover is the movement of a cluster resource from one node in the cluster to another node. If something goes wrong on one node, or the node needs to be taken offline for maintenance, cluster resources can failover to another node to provide continual access.

Once the database is created and resides on a shared disk, the database can be enabled and managed as a cluster resource so that it will failover properly. For more information on Failover Clusters and using the PROCLUSTER, command, see "Failover Clusters."

SYNTAX

Operating system
Syntax
UNIX
Windows
procluster db-name 

[ enable [ -pf params-file ] [ AI ] [ BI ] 

[ APW=n ] [ WDOG ] 

| disable 

| start 

| stop 

| terminate 

| looksalive 

| isalive ] 

PARAMETERS

db-name

Specifies the fully qualified path of the database.

enable

Enables the database so that it will failover properly. Before the database can be enabled it must be created and reside on a shared disk. The database must not be in use when it is enabled as a cluster resource. If PROCLUSTER enable is successful, the text message The cluster REGISTER command was successful is returned.

Enabling Progress as a cluster resource also creates the file <dbname>Resources.cluster. This is a text file that contains names of resources dependent on the database resource. If the database was not enabled with any helper processes or performance enhancers like AIW,APW, BIW, WDOG, the .cluster file will be empty; otherwise, it will contain the resource names of the dependent resources as registered with the cluster manager. Do not edit or delete this file. Clusters manages this file, and deletes it when the database is disabled.

When you enable a database as a resource using PROCLUSTER enable, Clusters performs the following:

params-file

Specifies the file containing any parameters that the database requires when started.

AI

Directs PROCLUSTER to enable the after image files, and an AI writer as resources with a dependency on the database. After-imaging must have previously been enabled on the database. For more information about after-imaging, see the Progress Database Administration Guide and Reference .

BI

Directs PROCLUSTER to enable a BI writer as a resource with a dependency on the database.

APW=n

Directs PROCLUSTER to enable n number of asynchronous page writers as a resource with a dependency on the database.

WDOG

Directs PROCLUSTER to enable the Watchdog process as a resource with a dependency on the database.

disable

Removes the identified database as a cluster resource if this database has previously been enabled. Specifying the database name with the disable parameter automatically disables any other optional dependencies specified when the database was enabled.

When you remove a database resource using PROCLUSTER disable, Clusters does the following:

start

Starts a cluster-enabled database. The resource must have been previously enabled as a member of the cluster.

NOTE: PROCLUSTER will append -pf db-name.pf to the proserve command that is generated to start the database. The start command will fail if this parameter file is not found.

PROCLUSTER must be used in place of PROSERVE or other tools for Clusters to function properly.

stop

Stops a cluster-enabled database. The database must be a member of the cluster.

When you stop the database with PROCLUSTER stop, Clusters does the following:

terminate

Forces a registered or cluster-enabled database to shut down. The database must be a member of the cluster.

looksalive

Determines if a resource looks operational by querying the cluster manager cache if available, or the active system for the status of the database specified. The database must be a member of the cluster and the database name must contain the fully qualified path.

To determine if a resource looks operational, enter the following command:

procluster db-name looksalive 

The looksalive exit status returns the following text if the database looks alive:

Resource: db-name State: Looks Alive 

The database must be enabled and started to return this message.

All other states return the following:

Resource: db-name State: Not Alive 

isalive

Determines if a resource is actually operational by querying the status of the database specified. The database must be a member of the cluster and the database name must contain the fully qualified path.

To determine if a resource is actually operational, enter the following command:

procluster db-name isalive 

The isalive exit status returns the following text if the database returns a successful query:

Resource: db-name State: Is Alive 

All other states return the following:

Resource: db-name State: Not Alive 


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095