RA8000/ESA12000 configuration using CLI/SWCC.
Installing the Secure Path Driver and Secure Path
Agent
The following section describes how to install the Secure Path drivers and
configuration management agent on a cluster node.
NOTE: It is only necessary to perform the steps in this section for the first
RA8000/ESA12000 Storage Subsystem; the steps are not required for additional storage
subsystems.
To install the Secure Path Driver and Secure Path Agent:
1. Insert the StorageWorks Secure Path Software CD in your CD-ROM
drive.
2. If you have CD AUTORUN enabled on your server, the Secure Path
setup program will start automatically. Otherwise, choose Run from the
Start menu and enter the command shown below, substituting your
CD-ROM's drive letter for the one shown.
drive_letter:\SPINSTAL\SETUP.EXE
3. When the setup starts, choose the Server Install option. The server
option will install the drivers and the agent required by Secure Path.
4. Click Yes if prompted to overwrite the HSZInstall data.
Yes
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-33
5. Make sure to enter a validation password. For cluster configurations,
make sure the password is the same for each member of the cluster.
NOTE: Be prepared to designate those clients you wish to allow to manage the host.
These names have to be fully qualified (for example, " myserver.mydomain.com" ). There
are many ways to configure TCP/IP on your network, including: a) host files on servers
and clients or b) DNS, with NetBios using DNS resolution. Check with your system
administrator to ensure proper network configuration.
6. Restart the node.
7. Repeat the steps 1 through 6 for the other nodes in the cluster.
Installing Secure Path Manager
The following section describes how to install the Secure Path management
application on a cluster node. Install this application on all cluster nodes. To
minimize network traffic, run it from one node.
NOTE: It is only necessary to perform the steps in this section for one RA8000/ESA12000
Storage Subsystem; the steps are not required for additional storage subsystems.
To install Secure Path Manager:
1. Insert the StorageWorks Secure Path Software CD in your CD-ROM
drive.
2. If you have CD AUTORUN enabled on your server, the Secure Path
setup program will start automatically. Otherwise, choose Run from the
Start menu and enter the command shown below, substituting your
CD-ROM's drive letter for the one shown.
drive_letter:\SPINSTAL\SETUP.EXE
3. When the setup starts, choose the Client Install option. The client option
will install the Secure Path Management graphical user interface.
4. Repeat steps 1 through 3 for the other nodes in the cluster.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-34 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Specifying Storage Unit I/O Paths
You must assign storage units (storagesets) to one or the other array
controllers to specify which controller is used to access units at system boot
time. The preferred_path unit attribute assigns units to either "this" controller
or the "other" controller. In effect, this procedure specifies on which Fibre
Channel Arbitrated Loop path (controller and host adapter) the I/O will travel
in all normal operations.
Initially, it is recommended that you balance the available storagesets between
the buses. As storage demands are defined and individual drive throughput
requirements are understood, adjustments to the disk I/O path configuration
can be made using the StorageWorks Secure Path Manager.
To load balance the storagesets between controllers:
1. From the CLI Window, enter the following command to obtain a list of
all units defined in the storage subsystem:
show units
2. Enter the following command to specify preferred_path for units:
set unit# preferred=this_controller
or
set unit# preferred=other_controller
3. Verify that the above changes were made by entering the following
command:
show units full
4. Repeat these steps for each storage subsystem.
You have completed the software configuration required to support your
Secure Path environment. Now you are ready to monitor and manage Secure
Path activity using the Secure Path Manager.
Power Up the Second Storage Hub
After installing Secure Path software, power up the second storage hub and
restart all nodes in the cluster.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-35
Creating Partitions
Using Windows NT Server Disk Administrator, you must create one extended
partition on each virtual disk you created previously in "Configuring a
Storageset." In the Disk Administrator, virtual disks appear as Disk 0, Disk 1,
and so on.
Subdivide the extended partition into logical partitions. The first logical
partition is a small fraction of the extended partition and is used by Secure
Path software to identify the virtual disk as an Oracle Parallel Server shared
database resource.
Other logical partitions contain the rest of the extended partition capacity and
are used for Oracle Parallel Server shared database resources. One logical
partition is required for each Oracle Parallel Server shared database resource.
See Oracle8 Enterprise Edition Getting Started Release 8.0.5. for
Windows NT for information on Oracle Parallel Server database guidelines
and requirements for subdividing the large extended partitions into logical
partitions.
To create partitions on a virtual disk:
1. Run Windows NT Server Disk Administrator from one node.
2. Create a large extended partition using all of the virtual disk space.
3. Within the extended partition, create a small (50 megabytes) logical
partition (for Secure Path) as the first logical partition.
NOTE: Make the small logical partitions in a storageset different in size by 1 megabyte,
for example, 50 megabytes for Disk 0, 51 megabytes for Disk 1, and so on. This provides
an easy way to identify the disk.
4. Format the small logical partition with NTFS.
5. Assign a drive letter to the small logical partition. Note the drive letter;
the drive letter assignments must be the same on all nodes in the cluster.
6. Assign a partition label (10 letters maximum) to the small logical
partition.
7. Using the rest of the space in the extended partition, create logical
partitions for shared database resources. Oracle requires unformatted,
raw partitions; do not format these logical partitions.
8. Repeat steps 1 through 7 for all virtual disks on an RA8000/ESA12000
Storage Subsystem.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-36 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
9. Select Commit Changes Now from the File Menu.
10. Restart the node from which Disk Administrator is running.
11. Run Disk Administrator from the other nodes and verify that the same
virtual disks, extended partitions, and logical partitions are seen by all
nodes in the cluster. On each node, assign the same drive letters to the
small logical partitions that you assigned on the first node.
12. Restart all nodes in the cluster.
13. After all nodes restart, open Disk Administrator on all nodes and verify
that the drive letters are identical on all nodes.
Using Secure Path Manager
This section describes how to use Secure Path Manager to monitor and
manage an RA8000/ESA12000 Secure Path for Windows NT environment.
NOTE: This section assumes that RA8000/ESA12000 storagesets have already been
configured, using SWCC or CLI, and that the drives have been partitioned with
Windows NT Server Disk Administrator.
StorageWorks Secure Path Manager is a Graphical User Interface (GUI) utility
that:
Reports the status of the two paths
s
Reports disk status (path assignment, failover, and failback activity)
s
Enables (manual) drive failback upon path restoration
s
It is recommended that Secure Path Management application remain active (or
minimized) to provide continuous Secure Path status monitoring.
To monitor and manage a Secure Path environment using Secure Path
Manager as described in the following sections, proceed as follows:
1. From the Start menu, select Programs, StorageWorks.
2. Select the Secure Path Manager application icon.
3. Log in by entering the server name and password assigned in the
"Installing the Secure Path Driver and Agent" section described
previously.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-37
IMPORTANT: If you make changes to the Secure Path Agent Configuration, the changes
will not go into effect until you stop and restart the Secure Path Agent Service from the
Windows NT Services Control Panel.
Determining Disk Identity
To identify drives configured in a multipath environment, use one of the
following methods:
Move the cursor over a disk icon. Secure Path Manager will display the
s
various identities of a drive-port/bus/target/LUN, or the associated drive
letter .
Right-click the mouse on the disk icon to launch the properties dialog
s
for the drive.
The drive information displayed should allow you to quickly map the
storageset to operating system identity and determine which storagesets are
currently serviced through each path:
The port/bus/target/LUN information refers to the physical identity of
s
the drive's corresponding storageset (unit) as designated by the storage
subsystem.
The disk number refers to the number assigned to a drive by the
s
Windows NT Server Disk Administrator.
The drive letter appearing above the drive icon is assigned to that
s
partition (if one exists) by the System Administrator. Multiple drive
letters associated with one LUN is not allowed.
Balancing the I/O Load
The Secure Path Manager can be used to statically load balance your Secure
Path configuration by following the procedure below:
1. Identify "hot" drives, which are those that consistently experience the
greatest I/O load while running workloads typical of your production
environment.
2. Enable Windows NT disk performance statistics if you have not done so
already, by issuing diskperf -y from a command window and restarting
your system.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-38 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
3. Use Windows NT Performance Monitor to characterize individual drive
loading in terms of throughput (I/Os per second) and/or bandwidth
(bytes per second), whichever is more appropriate for your application.
4. Note the path assignments of hot drives.
5. Balance the overall I/O load by evenly distributing (reassigning drive
primary path) as much as possible, the hot drives between the two paths.
Use the drag and drop feature to drag a disk icon from its current
primary path to a new primary path. See the Secure Path documentation
for more information on this feature.
6. Run your workload, monitor, and readjust as necessary.
Defining a Persistent Secure Path
RA8000/ESA12000 Drive Configuration
When the primary path for a drive is changed using the Secure Path Manager,
the preferred_path assignment for the corresponding storage unit on the
RA8000/ESA12000 does not change. If the preferred_path is not changed to
the new path, the unit will revert to its original preferred_path if both the
RA8000/ESA12000 and host server are power cycled together. To make the
primary path assignment persistent for those drives you have reassigned with
the Secure Path Manager, reset the preferred_path attribute for the
corresponding storage unit on the RA8000/ESA12000.
To define a persistent Secure Path RA8000/ESA12000 drive configuration:
1. Use the CLI command show units to show the preferred_path settings
for all units. This command will also indicate which controller each
storageset is currently online with ("this" or "other").
2. Use the CLI command set unit# preferred=this_controller or set unit#
preferred path=other_controller to change the preferred path attribute to
the appropriate path. For instance, if a storage unit is reported as being
"online to other controller" but is preferred to "this" controller, you
should change the preferred_path attribute to the "other" controller.
3. Repeat this procedure for each storage unit that is online to a path that is
not its preferred path.
4. Restart all storage subsystems and all nodes in the cluster.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-39
Installing Oracle Software
Using the Oracle8 Enterprise Edition Getting Started Release 8.0.5 for
Windows NT, follow the steps to install Oracle Enterprise Edition release
8.0.5 software on all cluster nodes, including:
Oracle Server, release 8.0.5
s
Oracle Parallel Server Option, release 8.0.5
s
Oracle Parallel Server Manager, release 8.0.5
s
Oracle Enterprise Manager, release 8.0.5
s
After installing Oracle software, the Oracle manual instructs you to install
vendor-supplied operating system dependent modules (OSDs). Return to this
document to install the Compaq OSDs.
Verifying Cluster Communications
Use the ping utility to verify that each node in the cluster can communicate
with every other node.
Run the ping utility from each node in the cluster. Ping the client LAN name
of every node in the cluster. The client LAN name and client LAN IP address
were assigned to each cluster node while using SmartStart to perform the
automated software installation steps.
When using the client LAN name with the ping command, the IP address
displayed by the ping utility should be the client LAN IP address.
For the Ethernet cluster interconnect, a cluster interconnect name and IP
address were assigned to each cluster node. Ping the Ethernet cluster
interconnect name of every node in the cluster.
When using an Ethernet cluster interconnect name, the IP address displayed by
the ping utility should be an Ethernet cluster interconnect address.
If the ping utility does not return the expected IP addresses, check the entries
in the hosts and lmhosts files at %SystemRoot%\system32\drivers\etc.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-40 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
For example, the command ping node1 should return the following type of
information.
Pinging node1.loc1.yoursite.com [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Refer to Section 7, "Troubleshooting" for more information.
Installing the Compaq OSDs
You must install the OSDs on each node in the cluster. However, you need to
run the NodeList Configurator only once (on one node) to configure the nodes
in the cluster because the NodeList Configurator copies information to the
other nodes in the cluster, provided that:
The servers are communicating through a local area network using a
s
TCP/IP protocol.
The person running the NodeList Configurator has administrative rights
s
and a common login on every node.
To install the Compaq operating system dependent modules (OSDs) for Oracle
Parallel Server, use the setup program on the Compaq Parallel Database
Cluster for Oracle8 Parallel Server Release 8.0.5 CD. The CD contains the
following OSD-related products:
OSD modules
s
Interprocessor communication (IPC) module
s
Cluster Manager (CM) module
s
Input/output (I/O) module
s
Start module
s
Performance management (PM) module
s
Installation and configuration software for the OSDs
s
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-41
OSD Installation Steps
The setup program performs the following tasks:
Copies the OSDs to the internal hard drive of the server.
s
Sets up registry entries for file location and standard registry parameters
s
for the OSDs.
Creates a Start menu icon for the NodeList Configurator program
s
provided with the OSDs.
Prompts you to run the NodeList Configurator, a program that allows
s
you to configure the nodes (servers) in the cluster. This program also
enters the Oracle instance ID into the registry of each node.
To install the OSDs:
1. Log in as a user who has administrator privileges on all nodes in the
cluster. If all servers in the cluster are in the same Windows NT Server
domain, log in as a user who is a member of the Domain Administrators
group. If the servers are in different domains, create a local user on each
server with the same Windows NT Server user name and password on
each node. Then make that local user a member of the local
Administrators group on each node before installing the OSDs.
2. Insert the Compaq Parallel Database Cluster for Oracle8 Parallel Server
Release 8.0.5 CD into the CD-ROM drive.
3. Start the OSD installation by clicking the Start button and select Run.
The Run dialog box appears.
4. Type d:\setup and click OK. Substitute the letter assigned to the CD
drive for d. The setup program describes the license agreement and
displays the readme file. It also prompts you for information including
your name, company, and where you want to install the OSD software.
5. Click Next on the Setup Type dialog box to install the Compaq OSD
components.
6. When the setup program completes, it prompts you to run the NodeList
Configurator. Leave the checkbox unselected and click Next and then
Finish to exit.
NOTE: Run the NodeList Configurator only once, after the OSDs have been installed on all
nodes in the cluster. When prompted to run the NodeList Configurator on the last node,
select the checkbox and then run the NodeList Configurator.
7. Install the OSDs on the remaining nodes in the cluster by repeating
steps 1 through 6.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-42 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Run the NodeList Configurator
1. Type the following information in the NodeList Configurator dialog box
for each node in the cluster. It is required that the host names you
indicate for the client LAN and cluster interconnect are the same as
those you entered in the hosts and lmhosts files at
%SystemRoot%\system32\drivers\etc.
Computer Name Name of this computer in the Microsoft network
Client LAN Name of this computer in the client LAN. Can be the same
as the Computer Name.
Cluster Interconnect Name of this computer in the cluster interconnect. Must not
be the same as the Computer Name.
Oracle Home Directory Location where Oracle is installed
ORACLE_SID System ID identifying the Oracle instance.
2. Type the name of the database, if it is different from the default of OPS.
3. When you have completed the information in the NodeList Configurator
dialog box, click OK. The information you entered is copied to the other
nodes, provided they are all up and running and are communicating
through an Ethernet local area network.
4. When the program indicates the setup process is complete, click Finish
to exit the program.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-43
Figure 5-5. NodeList Configurator dialog box
Installing Object Link Manager
IMPORTANT: Before configuring Oracle software, you must install Object Link Manager.
This is required to maintain the symbolic links between disk partitions and Oracle data
files. Failure to install Object Link Manager can result in the Oracle database not starting
or, if it starts, in not finding the correct data.
Windows NT Server assigns disk numbers to drives in the shared storage
subsystems based on the order in which the shared storage subsystems are
powered on. Through the symbolic links created by SETLINKS, Oracle Server
uses the order in which disks are brought online to determine the location of its
database files.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-44 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Therefore, the order in which disks are brought online directly affects the disk
numbers assigned to the disk, which in turn affects the ability of Oracle Server
to find Oracle data files. If shared storage subsystems are powered off and then
powered on in a different order than they were when the cluster was initially
configured, the order and numbering of the shared disk drives will change for
all nodes in the cluster.
To avoid this problem, install Object Link Manager. Object Link Manager
simplifies the creation and maintenance of symbolic links between disk
partitions and Oracle data files by placing the symbolic link names directly
into the disk partitions, thereby tracking the symbolic links dynamically. This
means that if the order in which disk drives are brought online changes, Oracle
Server can find the correct data files and can properly start the Oracle
database.
You must install Object Link Manager before configuring Oracle software.
before
For instructions on installing and using Object Link Manager, see the readme
file on the Compaq Parallel Database Cluster Model PDC/O5000 for Oracle
Parallel Server Release 8.0.5 Clustering Software CD at:
\Object Link Manager\readme.txt
Configuring Oracle Software
Use Oracle8 Enterprise Edition Getting Started Release 8.0.5 for Windows NT
to configure the Oracle software. Configuring Oracle software includes
configuring Oracle Parallel Server, Oracle Parallel Server Manager, Oracle
Enterprise Manager, and administering multiple instances.
Additional Notes on Configuring Oracle Software
In addition to the steps outlined in the Oracle documents, you must perform
several additional steps as described in this section.
Set OraclePGMSService to Start in Manual Mode
Before configuring Oracle software, verify that the OraclePGMSService is set
to start in manual, not automatic, mode. It defaults to start in automatic mode.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-45
If Your Database is Not Called OPS
The database name defaults to OPS, but you can change it. You enter the
database name in the OPSCONF utility and the NodeList Configurator
program. However, to run the OPSCONF utility successfully with a database
name other than OPS, you must first:
Run the NodeList Configurator program. The NodeList Configurator
s
updates the appropriate entries in the registry that OPSCONF depends
on.
Edit the database name in the ORACLE_DIR\database\init.ora,
s
ORAHOME\database\init_com.ora, and ORACLE_DIR\ops\ops.sql
files on each node.
Create a Symbolic Link for OPS_CMDISK
The OPS_CMDISK file contains status information for all nodes in the cluster.
Using the Object Link Manager, you must create a symbolic link from the
OPS_CMDISK file to a disk partition.
Do Not Configure the OSD Layer
or Add an ORACLE_SID Entry
When configuring Oracle, do not perform the steps for configuring the OSD
layer and adding an ORACLE_SID entry to the registry. You completed these
tasks by configuring the nodes in the cluster using the setup utility for the
OSDs and the NodeList Configurator.
Create Services
There might be an omission in the Oracle manual concerning using the
SID
CRTSRV batch file. When you enter the crtsrv SID command, you must
follow it with a password. This same password is required when you connect
to an instance using the server manager, SVRMGR30.
The Oracle manual indicates that some vendors might require changing the
password for the Oracle SID and the OracleTNSListener to the administrator's
password for the node. Do not change the password as instructed.
Configure the Network
There might be an omission in the Oracle manual regarding the step of testing
the configuration. You should restart the Oracle service before starting
SVRMGR30.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-46 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Start the Database in Parallel Mode
IMPORTANT: Before starting the database in parallel mode, restart all nodes in the
cluster.
There might be an omission in the Oracle manual regarding starting the
database using SVRMGR30. Before starting the database using SVRMGR, log
on as user INTERNAL.
Verifying the Hardware and Software
Installation
Cluster Communications
Use the ping utility to verify that each node in the cluster can communicate
with every other node.
Run the ping utility from the installing cluster node. Verify the installing node
can communicate with all cluster nodes by pinging the client LAN name and
cluster interconnect name of every node in the cluster.
When using the client LAN name, the IP address displayed by the ping utility
should be the client LAN IP address. When using an Ethernet cluster
interconnect name, the IP address displayed by the ping utility should be the
Ethernet cluster interconnect address. If this is not the case, check the entries
in the hosts and lmhosts files at %SystemRoot%\system32\drivers\etc.
Access to Shared Storage from All Nodes
Open Windows NT Server Disk Administrator to verify that the same shared
disk resources seen from this node are the same as those seen from every other
cluster node.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
Installation and Configuration 5-47
OSDs
After verifying all the nodes have access to the shared storage, start an Oracle
instance. For example, at a c: command prompt start an instance by entering:
net start oracleserviceORACLE_SID
If the OSDs are installed correctly, a message will appear that the Oracle
service has started successfully.
If the Oracle service did not start successfully, run the Services applet in the
Windows NT Server control panel. If the OSDs are running, the OraclePGMS
service should be started. If the PGMS service has not started, you can check
these two logs for details about why the Oracle Service did not start:
\Compaq\OPS\error.log
s
%SystemRoot%\system32\pgms.log
s
Client Access to the OPS Database
Use Oracle Enterprise Manager to verify client access to the OPS database.
See the Oracle documentation included on the Oracle8 Enterprise Edition CD.
Power Distribution Guidelines
It is recommended you connect most cluster components to a Compaq power
distribution unit (PDU). PDUs connect to an uninterruptible power source
(UPS) or building power. The power distribution units and UPSs are the only
cluster components connected to a building power source. If there is no UPS,
the PDU plugs into building power.
It is also recommended to connect cluster components, such as servers, storage
subsystems, switches, and hubs, to two PDUs and UPSs so the cluster
components continue to operate if one PDU or UPS fails.
Server Power Distribution
Figure 5-6 shows an example of server power distribution for a three-node
cluster. Power supply #1 of each server is connected to PDU #1. Power
supply #2 of each server is connected to PDU #2.
PDU #1 is connected to UPS #1, and PDU #2 is connected to UPS #2. Each
UPS is connected to building power.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
5-48 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Building
Proliant Servers PDU UPS
Power
Power
Supplies
Figure 5-6. Server power distribution in a three-node cluster
Having two PDUs and UPSs in the cluster provides two paths from the servers
to building power and means that the cluster stays up and running if a PDU or
UPS fails in one of the paths.
Storage Subsystem Power Distribution
The power distribution for storage subsystem enclosures, with respect to
connecting them to PDUs and UPSs, can be configured similarly to the
example shown for server power distribution.
Each enclosure in an RA8000/ESA12000 Storage Subsystem has two AC
power inlets. Substituting power inlets for power supplies and storage
subsystem enclosures for ProLiant servers in Figure 5-6, you can provide two
redundant paths from the storage subsystem enclosures to building power.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: f-ch5 Installation and Configuration.doc Last Saved On: 9/8/99 3:03 PM
6
Chapter
Cluster Management
Throughout the life of your cluster, in addition to monitoring ongoing
activities, you might need to increase storage capacity, improve cluster
performance, or upgrade hardware or software components. This chapter
describes these management activities for Compaq Parallel Database Cluster
Model PDC/O5000 for Oracle8 Release 8.0.5 (PDC/O5000).
IMPORTANT: The procedures in this chapter contain high-level instructions that
summarize what has already been discussed in either the Oracle8 documentation,
StorageWorks documentation, Secure Path documentation, or elsewhere in this guide.
The topics addressed in this chapter include:
Management applications
s
Managing network clients connected to a cluster
s
Monitoring cluster events
s
Managing a cluster in a degraded condition
s
Power sequencing guidelines
s
Software maintenance
s
Managing changes to shared storage
s
Replacing or adding a cluster node
s
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-2 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Management Applications
Monitoring Server and Network Hardware
Compaq Insight Manager is used to manage the server and network hardware
components of your cluster. Compaq Insight Manager, loaded from the
Compaq Management CD, is an easy-to-use software utility for collecting
server and network information. Compaq Insight Manager performs the
following functions:
Monitors server fault conditions and system status
s
Forwards server alert fault conditions
s
Remotely controls servers
s
In Compaq servers, each hardware subsystem, such as network adapters,
system processors, and system memory, has a robust set of management
capabilities. Compaq Full Spectrum Fault Management notifies of impending
fault conditions.
Several steps are required to configure the system for Compaq Insight
Manager. For example, you must:
Load Insight agents on each cluster node
s
Install the Compaq Insight Manager Console
s
Make sure that proper user rights are granted
s
For additional information concerning Compaq Insight Manager, see the
Compaq Server Setup and Management pack.
Monitoring Storage Subsystem Hardware
StorageWorks Command Console (SWCC) is used to monitor the storage
subsystem hardware components of your cluster. The SWCC is a graphical
user interface that can be used as an alternative to Command Line Interpreter
for managing an RA8000/ESA12000 Storage Subsystem.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-3
Managing Shared Storage
There are two levels of management with shared drives. The physical disks
and the drive arrays created from them are managed with RA8000/ESA12000
utilities. The logical drives are created and managed with the Windows NT
Disk Administrator.
The PDC/O5000 manages the shared disks with the graphical StorageWorks
Command Console and with the Command Line Interpreter. The multipath
component of the shared storage subsystems is managed with Secure Path
Manager.
Using the Command Line Interpreter
The Command Line Interpreter (CLI) enables comprehensive, precise control
over the RA8000/ESA12000 Storage Subsystem. The CLI supports dozens of
commands to configure, modify, and diagnose problems in the storage
subsystem. For example, the CLI enables you to configure the failover setting
of the array controllers, set the RAID levels of the drives, and view the
connections between the servers and the storage subsystem.
For additional information, see the StorageWorks documentation.
Using the Compaq StorageWorks
Command Console
The StorageWorks Command Console is a graphical user interface used to
create and manage storage subsystems for the PDC/O5000. While the
Command Line Interpreter CLI Window provides very detailed control over
the storage subsystem, the StorageWorks Command Console replicates most
of the CLI Window functions in a graphic form and provides a user-friendly
method of executing CLI commands.
See the StorageWorks documentation for details about using SWCC.
Using the Secure Path Manager
Secure Path Manager is a component of the Compaq StorageWorks Secure
Path software included in the PDC/O5000 cluster kits. The Secure Path
Manager is used to manage the redundant paths of the shared storage system.
It is used in conjunction with the CLI and the SWCC, which are used
primarily to manage shared disks, array controllers, and storage enclosures.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-4 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Secure Path Manager is the client application used to manage multipath
configurations of the RA8000/ESA12000 Storage Subsystem and provides the
following features:
Displays a graphical representation of the current multipath environment
s
Indicates the location and state of all configured storagesets on each of
s
the paths
Provides the capability to move storagesets between FC-AL paths in
s
order to facilitate static load balancing
For additional information see the Secure Path documentation on the Secure
Path CD.
Windows NT Server Disk Administrator
Windows NT Server Disk Administrator is first run after the drive arrays have
been configured by the RA8000/ESA12000 utilities. Disk Administrator is
used to:
Partition the drive arrays
s
Create logical drives
s
Assign drive letters
s
Format the logical drives
s
For additional information about Disk Administrator, see your Windows NT
Server documentation.
Monitoring Cluster Performance
Several tools exist to monitor performance of your cluster. Use the tools to
regularly monitor the performance of each node and each Oracle instance. The
gathered information might identify a disparity in the workload being
performed by each node, which signifies a need to adjust the distribution of the
workload so that the overall cluster performance is maximized.
Compaq Insight Manager can be used to gather low-level, in-depth
s
hardware statistics for the server and networking hardware components
used in the cluster.
StorageWorks Command Console gathers hardware statistics for the
s
storage subsystem components.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-5
Windows NT Performance Monitor gathers performance characteristics
s
of many objects. Examples of monitored objects are memory, processor,
hard drive performance, network software, and application software.
Oracle8 Performance Manager captures, computes, and presents
s
performance data about the Oracle database. Specific data about Oracle8
Parallel Server metrics are monitored and viewed with this application.
Monitoring the Database
Oracle8 Enterprise Manager uses agents to continuously monitor database
activities and offers a graphical console allowing administrators to manage the
database. From the Enterprise Manager Console, the administrator can
administer, diagnose, and tune multiple databases. Jobs can also be scheduled,
software can be distributed, and objects and events can be monitored from the
console.
Several steps are required to properly configure the system for Oracle8
Enterprise Manager. Additional steps are required to integrate the management
of parallel databases. For example, you must create an Enterprise Manager
Repository on the console node, you must have sufficient rights on the console
machine as well as on the managed cluster nodes, and you need to install
Oracle agents on each managed node.
Be sure to read through the Oracle8 documentation. Two helpful starting
points are the Oracle8 Enterprise Manager Administrator's Guide and the
Oracle8 Parallel Server Management User's Guide.
Oracle8 Enterprise Manager and its corresponding documentation are shipped
as part of Oracle8 Enterprise Edition.
Managing a Remote Cluster
Both Oracle8 Enterprise Manager and Compaq Insight Manager can be run
from any network client machine that has network access to the cluster nodes.
They can operate on Windows NT Server or Windows 95.
Before installing Compaq Insight Manager and Oracle8 Enterprise Manager, it
is recommended that you read through the corresponding documentation to
determine how to set up and configure each of these programs to run remotely.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-6 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Managing Network Clients Connected
to a Cluster
An important aspect of managing network clients is informing users that their
applications are now running on a cluster. As the cluster is initially brought
into production, it can be helpful to describe in a memorandum the effects a
cluster will have on user ability to access the database.
Because users experience some disruption of service and possibly a
performance degradation while a node is being removed or integrated into the
cluster, they might become concerned about the availability and stability of
their applications. Prior to removing or adding a node, forewarn users that they
might notice a brief disruption in their ability to access their database. Inform
them to wait several seconds before attempting to reaccess their database.
Monitoring Cluster Events
The majority of cluster events can be viewed either within the Windows NT
Server Event Log or within specific error log files:
The Oracle8 Server events are sent to the Application Event Log and
s
can be viewed with the Windows NT Server Event Viewer. For other
Oracle8 log files and trace files, refer to the Oracle documentation.
The lower-level software components (those involved with managing
s
the cluster aspects of the product) send events to error log files.
G The Group Membership Service (PGMS) logs messages to
%SystemRoot%\System32\pgms.log.
G By default, the OracleCMService sends messages to
C:\compaq\ops\error.log.
NOTE: If the OSDs are not installed in the default directory, the log files will be in the
same directory as the OSDs.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-7
Managing a Cluster in a Degraded
Condition
Due to the high-availability benefits of clustering, applications and network
clients remain operational even while some cluster components do not. When
the cluster enters a degraded condition, it is helpful to follow this
troubleshooting process:
1. Determine what caused the degradation.
2. Determine whether the condition affects one cluster node, multiple
cluster nodes, or all cluster nodes.
If one or more nodes is unaffected by the condition, and if enough
performance can be obtained from the unaffected nodes, continue
operating the database.
3. Determine whether the condition will continue to worsen.
4. Determine how critical it is to repair the problem.
5. If the problem is not considered to be critical, wait until a nonpeak time
to service the problem.
6. If the problem is critical but does not affect all cluster nodes, shut down
the Oracle instances on the affected nodes and wait until a nonpeak time
to service the problem.
7. If the problem is critical and affects all the cluster nodes, shut down the
database instances on all cluster nodes and service the problem.
Secure Path and Drive Status Monitor
The two paths (Path 0 and Path 1) are displayed in green by the Secure Path
Manager when both paths (host adapters, cabling and controllers) are
functioning normally. The Secure Path Manager keeps track of the primary
path (bus assignment) for each disk in the storage subsystem. When operating
normally, the Secure Path Manager displays each disk on the primary path to
which it has been assigned as a disk icon, shaded gray. If a drive letter has
been assigned to the disk, it will be displayed above the disk icon. If a fault
occurs, the failover drives will be displayed in shades of yellow and green.
The original path will turn red to indicate the path fault.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-8 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Automatic Failover Detection and Status Reporting
When a path fails (Secure Path software detects the loss of drive I/O due to
adapter, cable or controller malfunction), the Secure Path software will:
Perform an automatic failover and move the affected drives to the
s
alternate path
Log failover events in the Windows NT Server system Event Log
s
Report the path failure through Windows pop-up message
s
Reflect the drives reassignment to the failover path on the display
s
NOTE: Check the Windows NT Server system Event Log or entries generated by the
Secure Path software to help determine which components of the path have
malfunctioned. Look for entries by the HSZdisk and RAIDisk drivers.
The Secure Path software continuously monitors the operational status of
drives configured on each path. Following the occurrence of any drive failure,
the Secure Path Manager reflects the updated Secure Path configuration within
its second refresh interval, or sooner if the end user presses F5.
F5
If the Secure Path software detects the failure of an I/O completion on a drive,
it immediately moves that drive to its alternate path and reroutes outstanding
I/O accordingly. When the Secure Path Manager discovers the failover of at
least one drive, it generates a Windows pop-up message and designates the
path as failed by changing its color from green to yellow. If the entire FC-AL
path fails, then all drives on the that path are moved over to the other path.
When all drives have been failed-over, the Secure Path Manager colors the
failed path red.
Secure Path Manager indicates that a failover has occurred as follows:
The failed path changes from green to red.
s
The affected disk icons relocate from their primary path to the alternate
s
path, indicating that disk I/O has been failed over to the alternate path.
On the alternate path, the disk icons that have been failed over from
s
their primary path reappear, shaded green.
A Windows pop-up message appears to report the failure.
NOTE: For a quick reference of the disk colors and their meaning, select Legend from the
View pull-down menu. The three possible drive states are identified and displayed in
color. Refer to the Help files for possible path colors.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-9
Manual Failback and Status Reporting
Once a failed path is restored, the disks that had been failed over to an
alternate path must be failed back manually, one at a time. As a safeguard, the
Secure Path Manager does not automatically fail back drives. Rather, it
enables disks to be manually failed back after the administrator validates the
integrity of the path. For a failed path to return to the normal (green) state, the
path must be restored and one or both of the following events must occur:
All of the failed-over disks are failed back to it.
s
The Windows NT Server node is restarted.
s
Failback Methods
You can restore failed over drives to their primary path by using one of the
following failback methods:
Failback Method 1:
s
a. In the Secure Path Manager Toolbar, click on the Failback button.
b. If more than one drive failed over, you can click Select All to select
all the failed over disk drives, then click OK.
Failback Method 2: In the Secure Path Manager Toolbar, click on the
s
Failback button.
a. In the Secure Path Manager Toolbar, click on the Failback button.
b. Select the disk that failed from the list, then click OK. If more than
one disk drive requires failback, repeat for each disk drive that has
failed back.
Failback Method 3: Drag and drop each failed-over disk icon to its
s
primary path. If more than one disk drive requires failback, repeat for
each disk drive that has failed back.
Continue until all disk drives are failed back and the restored path turns green.
As each drive returns to its primary path, the drive icons will return to their
normal yellow and gray color. (The disk icon may appear above or beneath the
path line, depending on your exact placement of the mouse.) The failback
path's color will not return to green until all failed-over drives have been
restored to their primary path.
NOTE: The order and spacing of the disk icons displayed on the paths can be refreshed
using the View/Refresh pull-down menu of the Secure Path Manager window or by
pressing F5.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-10 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Power Sequencing Guidelines
At some time during the life of your cluster, you might need to perform an
operation on a cluster node that will require that it be powered down.
Physically moving the cluster node, removing a hardware device, and adding a
hardware device commonly require the node to be powered down. The
following information about powering up or powering down a node applies to
an existing cluster that has already been installed.
Powering Down a Node Without Interrupting
Cluster Services
It is a good practice to gracefully shut down a node before powering it down.
As long as the remaining cluster nodes are operating normally, the database
will remain accessible.
Shutting Down a Node
Before powering down a node in a PDC/O5000, gracefully shut it down as
follows:
1. Make sure that clients connecting to the database through the node can
reconnect to the database through one of the other nodes.
2. Properly shut down the Oracle instance running on the node.
3. Shut down Windows NT Server on the node.
The node can now be powered down safely.
Powering Down a Node
After you have shut down the node gracefully, be sure to power down the
cluster components in the following order:
1. ProLiant servers
Shutting down and powering down the servers first allows them to
perform tasks such as flushing queued database write transactions to
disk and properly terminating running processes.
2. Ethernet switches
3. RA8000/ESA12000 master enclosure
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-11
4. RA8000/ESA12000 expansion enclosures
5. Storage hubs (remove the AC power cord)
Powering Up a Node
Be sure to power up the cluster components in the following order:
1. Storage hubs (power is applied when the AC power cord is plugged in)
2. RA8000/ESA12000 expansion enclosures
3. RA8000/ESA12000 master enclosure
4. Ethernet switches
5. ProLiant servers
Software Maintenance
Uninstalling the OSDs
At some point, you might need to uninstall the operating system dependent
modules (OSDs) from a node. Some example situations are:
When a node is being permanently removed from the cluster
s
When a node is being replaced
s
When a node is being added to the cluster
s
When the OSDs are being upgraded to a newer revision level
s
Prior to uninstalling the OSDs, be sure to shut down the Oracle instance and
stop the Oracle services running on all nodes. Use the Windows NT Server
Add/Remove Programs control panel applet to remove the OSDs. Remove the
item shown as "Compaq OSD Modules for Oracle Parallel Server."
Uninstalling Secure Path
To uninstall Fibre Channel software and hardware from your system:
1. Launch the Windows NT control panel and choose Add/Remove
Programs.
2. Select StorageWorks Secure Path Manager and click Add/Remove.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-12 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
3. Select StorageWorks Secure Path Agent and click Add/Remove.
4. Select StorageWorks RAIDisk and click Add/Remove.
5. Uninstall HSZdisk by selecting StorageWorks HSZdisk and clicking
Add/Remove.
IMPORTANT: Do not restart the system at this time; restart after installing HSZdisk to
keep drive letter assignments in order.
6. Remove the Fibre Channel host adapter using the SCSI control panel by
selecting the driver and clicking Remove.
7. Shut down and power off all nodes.
8. Remove the Fibre Channel host adapter and cable paths.
9. Power up all nodes.
10. Verify the configuration by checking the event logs.
The uninstall process is complete.
Upgrading Oracle8 Server
The design of the PDC/O5000 is tightly integrated with Oracle8 Server.
Significant changes in Oracle8 Server will likely affect the operation of the
cluster.
Before upgrading to any new release of Oracle8 Server, consult your Compaq
and Oracle Service representatives. Make sure that the new release is certified
and supported on the PDC/O5000, and get assistance to determine what
procedure you should follow to perform the upgrade properly.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
Cluster Management 6-13
Managing Changes to Shared Storage
Adding New Storagesets to Increase Storage
Capacity
During the life of your PDC/O5000, you might need to expand the capacity of
your shared storage subsystem. The following steps describe how to add a
storageset to the RA8000/ESA12000 Storage Subsystem and how to allocate it
to Oracle8.
IMPORTANT: This activity requires restarting the cluster nodes, so it is recommended
you perform these steps during nonpeak hours.
To add new storagesets to a Secure Path configuration:
1. Physically add the SBBs to the RA8000/ESA12000 storage enclosures.
2. Use the CLCI window to discover the newly added SBBs.
3. Use HSG80 Storage Window, located within the SWCC program, to
create new storagesets on the storage subsystem.
4. Follow the procedures in the "Configuring a Storageset" and "Creating
Partitions" subsections in Chapter 5, "Installation and Configuration" to
configure a new storageset unit, verify access to it, and create partitions
for it.
5. Use the CLI Window to specify a storage unit I/O path for the new unit.
6. Restart all host nodes so Windows NT Server and the Secure Path
software can configure the new unit.
7. Run Secure Path on one cluster node. This enables Secure Path to
recognize the newly-added logical drive volumes and partitions.
8. Perform the necessary Oracle commands to associate the new data files
to the database. See the Oracle8 Enterprise Edition Getting Started
Release 8.0.5 for Windows NT for information.
Compaq Confidential Need to Know Required
Writer: EGardner Project: Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide Comments:
Part Number: 153668-001 File Name: g-ch6 Cluster Management.doc Last Saved On: 9/8/99 3:04 PM
6-14 Compaq Parallel Database Cluster Model PDC/O5000 for Oracle8 Release 8.0.5 Administrator Guide
Expanding a Virtual Disk Within a Storageset
Expanding the size of a virtual disk within a storageset is a complex process
and should be attempted only by the site database administrator.
The major steps in expanding a virtual disk within a storageset are:
1. Backup the database.
2. Shut down the Oracle instance on each cluster node.
3. Delete the extended partition on the virtual disk to be expanded.
4. Recreate the virtual disk with the added capacity.
5. Perform the steps in "Configuring a Storageset" and "Creating
Partitions" in Chapter 5, "Installation and Configuration" for the re-
created virtual disk.
6. Restore the database.
Replacing a Failed Drive in a Storage Subsystem
At some point you might need to replace a failed drive in an
RA8000/ESA12000 storage subsystem. With RAID employed, the
replacement of a drive is managed by the storage subsystem. It is assumed you
are using RAID levels 1, 3/5, or 0+1 for all devices in the storage subsystem.
When a disk drive fails in a RAIDset, the array controller automatically places
the disk drive into the failedset; however, the storageset can operate without
one of its members.
IMPORTANT: If the failed drive is not part of a fault-tolerant drive array, you can lose
some or all of the data on the failed drive. RAID level 0 does not provide fault tolerance.
The operating system and Oracle8 are unaware of the replacement of the drive.
You do not need to power down the cluster components to replace a failed
drive.
To replace a failed drive in a storage subsystem:
1. Identify the failed drive by typing the following CLI command and
pressing Enter:
Enter
show failedset
The command returns the name of the failed disk drive.
| 153668-001
|
