Compaq ProLiant 6500 Compaq Parallel Database Cluster Model PDC/O1000 for Orac - Page 122

Cluster Management Concepts, Powering Off a Node Without Interrupting Cluster€Services

Get Compaq ProLiant 6500 PDF manuals and user guides View all Compaq ProLiant 6500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 122 highlights

6-2 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide Cluster Management Concepts Powering Off a Node Without Interrupting Cluster Services At some time during the life of your cluster you will need to perform an operation on a cluster node that will require it to be powered off. Physically moving the cluster node, removing a hardware device, and adding a hardware device commonly require the node to be powered off. It is a good practice to gracefully shut down the node before powering it off. The process of shutting down a node in a PDC/O1000 can be summarized through the following: 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 shutdown the Oracle instance running on the node. 3. Shut down the server. The node can now be powered off safely. The database will remain accessible since the remaining cluster nodes are operating normally. 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.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
6-2
Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide
Cluster Management Concepts
Powering Off a Node Without Interrupting
Cluster Services
At some time during the life of your cluster you will need to perform an
operation on a cluster node that will require it to be powered off. Physically
moving the cluster node, removing a hardware device, and adding a hardware
device commonly require the node to be powered off.
It is a good practice to gracefully shut down the node before powering it off.
The process of shutting down a node in a PDC/O1000 can be summarized
through the following:
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 shutdown the Oracle instance running on the node.
3.
Shut down the server.
The node can now be powered off safely. The database will remain accessible
since the remaining cluster nodes are operating normally.
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.