Re: corrupting symbol.tbl on network install of OpenROAD -
09-28-2005
, 03:42 AM
Hi Zoe,
We have known the same problem for our clients : image runs on W2000,
dbms runs on HP-UX PA-Risc or HP-UX Itanium.
This is what we do.
We take the output of ingprenv ( shows the contents of the symbol.tbl )
and create a bat file for restoring it :
ingunset variable1
ingunset variable2
....
ingsetenv variable1 value1
ingsetenv variable2 value2
ingsetenv II_GCNII_LCL_VNODE %COMPUTERNAME%
.....
So, the II_GCNII_LCL_VNODE needs a special approach.
Also, we don't include an entry in the script for the II_GCNII_PORT
variable ( not in the ingunset sequence and not in the ingsetenv
sequence ).
So, whenever a client is faced with a corrupt symbol.tbl, we let him
run the bat file. Problem solved .
Other solution :
Alternatively, we recently started upgrading some clients with OR41 SP3
and till now we have not seen any problem with the symbol.tbl with OR41
SP3. As long as you don't upgrade your development PC's with OR41SP3
before your clients, then that should be not a problem. OR41 SP3
runtimes can run plain OR41 or OR41 SP1 images, but OR41 runtimes can
not run OR41SP3 images.
Regards,
Franky Leeuwerck
Advanced Projects & Products
http://www.ap2.be |