Compaq ProLiant 6500 Compaq Parallel Database Cluster Model PDC/05000 for Orac - Page 169

Expanding a Logical drive Within a Storageset, Replacing a Failed Drive in a Storage Subsystem

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 169 highlights

Cluster Management 6-15 Expanding a Logical drive Within a Storageset Expanding the size of a logical drive within a storageset is a complex process and should be attempted only by the site database administrator. The major steps in expanding a logical drive within a storageset are: 1. Back up the database. 2. Shut down the Oracle instance on each cluster node. 3. Delete the extended partition on the logical drive to be expanded. 4. Recreate the logical drive with the added capacity. 5. Perform the steps in the following subsections for the recreated logical drive. G "Configuring a Storageset" in Chapter 5, "Installation and Configuration." G "Creating Partitions" in Chapter 5, "Installation and Configuration." 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 MA8000/EMA12000 Storage Subsystem. It is assumed you are using RAID levels 1, 0+1, 3/5, or 5 for all devices in the storage subsystem. When a disk drive fails in a RAIDset or mirrorset, the array controller automatically places it into the failed set and reduces the storageset so that it 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. With RAID employed, the effects of replacing a drive are felt only by the storage subsystem. The operating system and Oracle8i are unaware of the activity. You do not need to power off the cluster components to replace a failed drive.

  • 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
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
Cluster Management
6-15
Expanding a Logical drive Within a Storageset
Expanding the size of a logical drive within a storageset is a complex process
and should be attempted only by the site database administrator.
The major steps in expanding a logical drive within a storageset are:
1.
Back up the database.
2.
Shut down the Oracle instance on each cluster node.
3.
Delete the extended partition on the logical drive to be expanded.
4.
Recreate the logical drive with the added capacity.
5.
Perform the steps in the following subsections for the recreated logical
drive.
G
“
Configuring a Storageset
”
in Chapter 5,
“
Installation and
Configuration.
”
G
“
Creating Partitions
”
in Chapter 5,
“
Installation and Configuration.
”
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
MA8000/EMA12000 Storage Subsystem. It is assumed you are using RAID
levels 1, 0+1, 3/5, or 5 for all devices in the storage subsystem. When a disk
drive fails in a RAIDset or mirrorset, the array controller automatically places
it into the failed set and reduces the storageset so that it 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.
With RAID employed, the effects of replacing a drive are felt only by the
storage subsystem. The operating system and Oracle8
i
are unaware of the
activity. You do not need to power off the cluster components to replace a
failed drive.