dbTalk Databases Forums  

corrupting symbol.tbl on network install of OpenROAD

comp.databases.ingres comp.databases.ingres


Discuss corrupting symbol.tbl on network install of OpenROAD in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Zoe
 
Posts: n/a

Default corrupting symbol.tbl on network install of OpenROAD - 09-27-2005 , 04:05 AM






Good morning,

Setup.
1/Unix server running Ingres 2.6. On solaris 9.
2/Image server running OpenROAD 4.1 on windows 2000. It uses a IngNet
connection to the above unix box.
3/ OpenROAD is on a network drive. It is not installed on the users
PCs.

I am hoping that you could provide me with some information as to why
the symbol.tbl file on a windows 2000 machine appears to corrupt. And
seems to prevent users from connecting.

I have seen a number of posts of the symbol.tbl corrupting and that the
solution is to copy an uncorrupt file back into place. I have a few
questions.
- Is there a fix for this?
- Or is a known issue that CA will get around to looking at?
- Whyis the file being corrupted?
- Would just setting a read-only flag on the symbol.tbl prevent
corruption or cause more problems?

Apologies for all the questions. I am not that familer with the details
of OpenROAD. I thank you in advance for your information.

- Zoe


Reply With Quote
  #2  
Old   
franky.leeuwerck@gmail.com
 
Posts: n/a

Default 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


Reply With Quote
  #3  
Old   
Zoe
 
Posts: n/a

Default Re: corrupting symbol.tbl on network install of OpenROAD - 09-30-2005 , 03:26 AM



Thank you Franky, Peter and Nigel for taking the time to reply to my
post. And explained why the problem possibly happens and how its NOT a
good idea to set the symbol.tbl to read only.

I shall certainly give the batch file a try as it would be useful to be
able to quickly restore the service to the users.

Thanks again. Have a great weekend.

Zoe


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.