This section describes functionality and command changes from previous releases. See the associated man pages for more information.
Sun Cluster 2.2 - The following Solstice HA 1.3 commands have been replaced in or removed from Sun Cluster 2.2:
|
Solstice HA 1.3 |
Sun Cluster 2.2 |
---|---|---|
Replaced |
hainstall |
scinstall |
hainetconfig |
hadsconfig |
|
haremove |
scinstall |
|
hasetup |
scconf / scinstall |
|
hastart |
scadmin startcluster (first node) scadmin startnode (remaining nodes) |
|
hastop |
scadmin stopnode |
|
Removed |
hacheck |
|
hafstab |
||
halicense |
||
haload |
The Sun Cluster 2.1 command scinstall(1M) has been changed for Sun Cluster 2.2. Refer to the scinstall(1M) man page for current syntax and usage.
Sun StorEdge Volume Manager (SSVM) - The following (1M) commands and options are supported only with SSVM. See the associated man pages for more information.
confccdssa
scconf -q
scconf -F
scconf -S
scadmin reldisks
scadmin resdisks
Solstice DiskSuite - The following changes apply to Solstice DiskSuite.
The reserve option to the scadmin(1M) command is used only with Solstice DiskSuite.
The scdidadm(1M) command is new for Solstice DiskSuite configurations. It is used to create mappings between disk ID instance numbers and remote paths to the disk, and to check disk ID major numbers.
In Sun Cluster 2.2, Oracle's Group Membership Services (GMS) daemon is no longer started as part of the Sun Cluster framework with scogms(1M). This means that for Oracle Parallel Server databases, the GMS daemon must be started manually using the binary ogmsctl that is provided by the Oracle Parallel Server Option installation on a cluster node. The ogmsctl daemon must be up and running even when the instance on the node is started in exclusive mode. Therefore, this daemon should be running when the database is created.
The GMS binaries ogms and ogmsctl are located in the /bin directory under $ORACLE_HOME. The default home directory for the GMS daemon is /tmp/.ogms. This directory contains trace files and the gms0000.dat file.
The GMS daemon must be started from the oracle user login. The following commands start the GMS daemon.
# su - oracle $ ogmsctl start |
For the daemon to start successfully, the node upon which it is run must be a cluster member.
The following command stops the GMS daemon.
$ ogmsctl stop |
The ogmsctl command has the following options.
Option |
Description |
---|---|
start |
Starts GMS |
stop |
Stops GMS |
abort |
Kills GMS |
trace=x |
Sets trace level to x |
status |
Determines whether GMS is running |
interactive |
Enters GMS debugger mode |
ogms_home=x |
Sets GMS home directory to x |
global-status |
Gets a list of active GMS nodes |
group-status domain group |
Gets a list of group member information |