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

Node or Nodes Unable to Rejoin the Cluster, Troubleshooting Client-to-Cluster Connectivity Problems

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

7-10 Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide Node or Nodes Unable to Rejoin the Cluster I If you have an Ethernet cluster interconnect, use ping to ensure that the rejoined node or nodes can communicate with other nodes in the cluster. For information about using the ping utility to test redundant Ethernet cluster interconnect connections, see "Verifying Cluster Communications" in Chapter 5, "Installation and Configuration." 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 an entry for the OSDs exists. I Make sure the OracleCMService and all other Oracle services have started without error. From the Services screen, scan the list of services and check to see if the Oracle services have started. From the Application log, check 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 in the "Verifying Cluster Communications" section in Chapter 5, "Installation and Configuration."

  • 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
7-10
Compaq Parallel Database Cluster Model PDC/O1000 for Oracle8i and Windows 2000 Administrator Guide
Node or Nodes Unable to Rejoin the Cluster
■
If you have an Ethernet cluster interconnect, use ping to ensure that the
rejoined node or nodes can communicate with other nodes in the cluster.
For information about using the ping utility to test redundant Ethernet
cluster interconnect connections, see “Verifying Cluster
Communications” in Chapter 5, “Installation and Configuration.”
■
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 an entry for the OSDs exists.
■
Make sure the OracleCMService and all other Oracle services have
started without error. From the
Services
screen, scan the list of services
and check to see if the Oracle services have started. From the
Application log, check 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 in
the “Verifying Cluster Communications” section in Chapter 5,
“Installation and Configuration.”