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

Troubleshooting Oracle8i and OSD Installation Problems and Error Messages

Page 192 highlights

Troubleshooting 7-5 Troubleshooting Oracle8i and OSD Installation Problems and Error Messages Potential Difficulties Installing the OSDs with the Oracle Universal Installer I The Oracle Universal Installer (OUI) uses an inventory file to track which components of the OSDs have been installed on each of the cluster nodes. A single inventory file is maintained on the node from which the OUI was initially run. All subsequent uses of the OUI must be made from that same installing node. I Installing onto a cluster node that already contains some or all of the OSD components will likely result in an incomplete installation. If difficulties persist, contact your support representative for assistance. I The OUI uses the network connections to transfer files from the primary node to the other cluster nodes. Use the ping utility to ensure that proper node-to-node connectivity exists. I The OUI requires administrator rights on all cluster nodes. To verify connectivity and access rights for each node, issue the following from the command line on the primary node: C: net use \\machine_name\C$ * /User: in which the "*" results in the system prompting you for a password, and the password is not echoed. If successful, the net use command returns: "The command completed successfully." I Determine whether or not you need to deinstall a partial OSD installation. An incomplete installation can result in a partial installation of the OSDs on the cluster. If this occurs, you must clean up after the partial installation (by removing it) before you can successfully run the OUI again. An incomplete OSD installation could result for various reasons, for example: G A cable is no longer seated tightly into its connector. G The node from which you are running the OUI cannot communicate with all other nodes in the cluster. G The user running the OUI does not have administrator privileges on all cluster nodes.

  • 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-5
Troubleshooting Oracle8
i
and OSD
Installation Problems and Error Messages
Potential Difficulties Installing the OSDs with the
Oracle Universal Installer
The Oracle Universal Installer (OUI) uses an inventory file to track
which components of the OSDs have been installed on each of the
cluster nodes. A single inventory file is maintained on the node from
which the OUI was initially run. All subsequent uses of the OUI must be
made from that same installing node.
Installing onto a cluster node that already contains some or all of the
OSD components will likely result in an incomplete installation. If
difficulties persist, contact your support representative for assistance.
The OUI uses the network connections to transfer files from the primary
node to the other cluster nodes. Use the ping utility to ensure that proper
node-to-node connectivity exists.
The OUI requires administrator rights on all cluster nodes. To verify
connectivity and access rights for each node, issue the following from
the command line on the primary node:
C: net use \\
machine_name
\C$ * /User: <
admin_login
>
in which the
*
results in the system prompting you for a password,
and the password is not echoed.
If successful, the net use command returns:
“The command completed successfully.”
Determine whether or not you need to deinstall a partial OSD
installation. An incomplete installation can result in a partial installation
of the OSDs on the cluster. If this occurs, you must clean up after the
partial installation (by removing it) before you can successfully run the
OUI again. An incomplete OSD installation could result for various
reasons, for example:
G
A cable is no longer seated tightly into its connector.
G
The node from which you are running the OUI cannot communicate
with all other nodes in the cluster.
G
The user running the OUI does not have administrator privileges on
all cluster nodes.