Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!amdahl!rtech!squid!robf
From: robf@squid.rtech.com (Robert Fair)
Newsgroups: comp.databases
Subject: Re: Ingres/STAR problem
Message-ID: <2908@rtech.rtech.com>
Date: 17 May 89 13:20:18 GMT
References: <QYQ4dqy00WB24U80N0@andrew.cmu.edu>
Sender: news@rtech.rtech.com
Reply-To: robf@squid.UUCP (Robert Fair)
Organization: Relational Technology, Inc.
Lines: 29

[Problem running Star on VMS 5.1]

INGRES has only just been certified to run on VMS 5, including 5.1 - make 
sure you have the most up-to-date version of INGRES.  

[Problem SYSMODing STAR-specific system catalogs]

This is a funny in 5.0 - the Star catalogs are created in the coordinator
database already modified, and shouldn't need changing unless you have
a lot of  activity in adding/deleting machine nodes or links. If you
do need to re-modify the STAR catalogs (iinode, iilink etc) go into
the coordinator database as a user with privilege to access the system
catalogs (the INGRES user is a good idea, or the DBA with the -u flag),
specify the +U flag to allow system catalogs to be updated, check the
table structures with the HELP command, and then simply re-MODIFY them.

Notes: 
1) This procedure is NOT generally recommended or supported, since
   updating the system catalogs can be dangerous if you make a typo.

2) Changing the structure/keys for any system catalogs from the default
   values is strongly NOT recommended, and may have unpleasant results.

In INGRES 6.2 the SYSMOD command seems to handle STAR databases directly, 
and optimizes all the STAR catalogs very nicely!  (At least it did when
I tested it...)

Robert Fair
RTI Tech Support