Compaq ProLiant 6400R Compaq Parallel Database Cluster Model PDC/05000 for Ora - Page 73

Oracle8i Enterprise Manager, Oracle8i Certification, Application Failover and Reconnection Software - server series

Page 73 highlights

Cluster Software Components 3-7 Oracle8i Enterprise Manager Oracle8i Enterprise Manager is responsible for monitoring the state of both the database entities and the cluster members. It primarily manages the software components of the cluster. Hardware components are managed with Compaq Insight Manager. Do not install Oracle8i Enterprise Manager on any of the PDC/O5000 nodes. To conserve cluster resources (memory, processes, etc.), it must be installed on a separate server that is running Oracle8i and has network access to the cluster nodes. Before installing Oracle8i Enterprise Manager, read its documentation to ensure it is installed and configured correctly for an Oracle8i Parallel Server environment. Oracle8i Certification To ensure that Oracle8i Parallel Server is used in a compatible hardware environment, Oracle has established a certification process, which is a series of test suites designed to stress an Oracle8i Parallel Server implementation and verify stability and full functionality. All hardware providers who choose to deliver platforms for use with Oracle8i Parallel Server must demonstrate the successful completion of the Oracle8i Parallel Server for Windows 2000 Certification. Neither Oracle nor Compaq will support any implementation of Oracle8i Parallel Server that does not strictly conform to the configurations certified with this process. For a complete list of certified Compaq servers, see the Compaq Parallel Database Cluster Model PDC/05000 Certification Matrix for Windows 2000 at www.compaq.com/solutions/enterprise/ha-pdc.html Application Failover and Reconnection Software When a network client computer operates in a clustered environment, it must be more resilient than when operating with a stand-alone server. Because a client can access the database through any of the cluster nodes, the failure of the connection to a node does not have to prevent the client from reattaching to the cluster and continuing its work. Oracle clustering software provides the capability to allow the automatic reconnection of a client and application failover in the event of a node failure.

  • 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 Software Components
3-7
Oracle8
i
Enterprise Manager
Oracle8
i
Enterprise Manager is responsible for monitoring the state of both the
database entities and the cluster members. It primarily manages the software
components of the cluster. Hardware components are managed with Compaq
Insight Manager.
Do not install Oracle8
i
Enterprise Manager on any of the PDC/O5000 nodes.
To conserve cluster resources (memory, processes, etc.), it must be installed
on a separate server that is running Oracle8
i
and has network access to the
cluster nodes. Before installing Oracle8
i
Enterprise Manager, read its
documentation to ensure it is installed and configured correctly for an Oracle8
i
Parallel Server environment.
Oracle8
i
Certification
To ensure that Oracle8
i
Parallel Server is used in a compatible hardware
environment, Oracle has established a certification process, which is a series
of test suites designed to stress an Oracle8
i
Parallel Server implementation and
verify stability and full functionality.
All hardware providers who choose to deliver platforms for use with Oracle8
i
Parallel Server must demonstrate the successful completion of the Oracle8
i
Parallel Server for Windows 2000 Certification. Neither Oracle nor Compaq
will support any implementation of Oracle8
i
Parallel Server that does not
strictly conform to the configurations certified with this process. For a
complete list of certified Compaq servers, see the
Compaq Parallel Database
Cluster Model PDC/05000 Certification Matrix for Windows 2000
at
www.compaq.com/solutions/enterprise/ha-pdc.html
Application Failover and Reconnection
Software
When a network client computer operates in a clustered environment, it must
be more resilient than when operating with a stand-alone server. Because a
client can access the database through any of the cluster nodes, the failure of
the connection to a node does not have to prevent the client from reattaching to
the cluster and continuing its work.
Oracle clustering software provides the capability to allow the automatic
reconnection of a client and application failover in the event of a node failure.