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

Selecting the Appropriate RAID Levels, RA4000/RA4100 Arrays using Oracle8

Page 75 highlights

4-16 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide Selecting the Appropriate RAID Levels Many factors affect which RAID levels you select for your cluster database. These include the specific availability, performance, reliability, and recovery capabilities required from the database. Each cluster must be evaluated individually by qualified personnel. The following general guidelines apply to RAID selection for a cluster with RA4000/RA4100 Arrays using Oracle8i Parallel Server: I Oracle recommends that some form of disk fault tolerance be implemented in the cluster. I In order to ease the difficulty of managing dynamic space allocation in an Oracle Parallel Server raw volume environment, Oracle recommends the creation of "spare" raw volumes that can be used to dynamically extend tablespaces when the existing datafiles approach capacity. The number of these spare raw volumes should represent from 10 to 30 percent of the total database size. To allow for effective load balancing, the spares should be spread across a number of disks and controllers. The database administrator should decide, on a case by case basis, which spare volume to use based on which volume would have the least impact on scalability (for both speedup and scaleup).

  • 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

4-16
Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide
Selecting the Appropriate RAID Levels
Many factors affect which RAID levels you select for your cluster database.
These include the specific availability, performance, reliability, and recovery
capabilities required from the database. Each cluster must be evaluated
individually by qualified personnel.
The following general guidelines apply to RAID selection for a cluster with
RA4000/RA4100 Arrays using Oracle8
i
Parallel Server:
Oracle recommends that some form of disk fault tolerance be
implemented in the cluster.
In order to ease the difficulty of managing dynamic space allocation in
an Oracle Parallel Server raw volume environment, Oracle recommends
the creation of “spare” raw volumes that can be used to dynamically
extend tablespaces when the existing datafiles approach capacity. The
number of these spare raw volumes should represent from 10 to
30 percent of the total database size. To allow for effective load
balancing, the spares should be spread across a number of disks and
controllers. The database administrator should decide, on a case by case
basis, which spare volume to use based on which volume would have
the least impact on scalability (for both speedup and scaleup).