Compaq ProLiant 8500 Compaq Parallel Database Cluster Model PDC/05000 for Orac - Page 196

Troubleshooting Client-to-Cluster Connectivity Problems

Page 196 highlights

Troubleshooting 7-9 I If you are using two dual-port Ethernet adapters in each node to connect to both the client LAN and the Ethernet cluster interconnect, make sure that the cables are installed between the correct adapter ports and switches. I Make sure the OSDs have been properly installed on the affected node or nodes by running the OUI on the cluster's primary node. Click Installed Products and verify that an entry for the OSDs exists. I Make sure the OracleCMService and all other Oracle services have started without error. From the Services screen, check to see if the services have started. From the Event Viewer, check the Applications log for error messages about the Oracle services. I Run Object Link Manager from each node to verify that the Oracle partitions and symbolic link associations are accurately displayed. I Verify that the node or nodes have access to the shared storage. Run Disk Management and make sure that all the shared disk resources appear as expected. If the view is not consistent across all cluster nodes, refer to Appendix A, "Diagnosing and Resolving Shared Disk Problems." Troubleshooting Client-to-Cluster Connectivity Problems A Network Client Cannot Communicate With the Cluster I Verify that the user ID has sufficient rights to perform the desired action. I Make sure proper network connectivity exists by verifying that the connections from the network client to the cluster are cabled correctly. Additionally, verify that the network routers/switches/hubs used in the client LAN are powered on and properly cabled. I Make sure that pinging an IP address over the client LAN from a client to the cluster issues a correct reply. Perform ping testing as described under "Verifying Cluster Communications" in Chapter 5, "Installation and Configuration." I Make sure that the TNSNames.ora file is properly configured on client and cluster nodes as defined by the Oracle Net8 Config Assistant utility.

  • 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

Troubleshooting
7-9
If you are using two dual-port Ethernet adapters in each node to connect
to both the client LAN and the Ethernet cluster interconnect, make sure
that the cables are installed between the correct adapter ports and
switches.
Make sure the OSDs have been properly installed on the affected node
or nodes by running the OUI on the cluster
s primary node. Click
Installed Products
and verify that an entry for the OSDs exists.
Make sure the OracleCMService and all other Oracle services have
started without error. From the
Services
screen, check to see if the
services have started. From the Event Viewer, check the Applications
log for error messages about the Oracle services.
Run Object Link Manager from each node to verify that the Oracle
partitions and symbolic link associations are accurately displayed.
Verify that the node or nodes have access to the shared storage. Run
Disk Management and make sure that all the shared disk resources
appear as expected. If the view is not consistent across all cluster nodes,
refer to Appendix A,
Diagnosing and Resolving Shared Disk
Problems.
Troubleshooting Client-to-Cluster
Connectivity Problems
A Network Client Cannot Communicate With the
Cluster
Verify that the user ID has sufficient rights to perform the desired
action.
Make sure proper network connectivity exists by verifying that the
connections from the network client to the cluster are cabled correctly.
Additionally, verify that the network routers/switches/hubs used in the
client LAN are powered on and properly cabled.
Make sure that pinging an IP address over the client LAN from a client
to the cluster issues a correct reply. Perform ping testing as described
under
Verifying Cluster Communications
in Chapter 5,
Installation
and Configuration.
Make sure that the TNSNames.ora file is properly configured on client
and cluster nodes as defined by the Oracle Net8 Config Assistant utility.