jhwang@CS.UCLA.EDU (07/01/89)
I was trying to add a node "ipswich" to a distributed database "navy/d" and got the following error message : INGRES ERROR: 26802 User does not have permission to use one of the flags. INGRES ERROR: 26002 Above error from Node: IPSWICH Database: DBDB Request Terminated by Errors I am the owner of this database and should have the permission to add other nodes to coordidator node. Also, INGRES/NET works fine for me since I can issue "rtingres nodename:navy/d" from ipswich to remote access navy/d on the coordinator site. Both nodes are running SunOS 3.5 and use tcp-ip network protocol Can any one tell me what the real problem is ? Thanks, - Andy
robf@squid.rtech.com (Robert Fair) (07/03/89)
>I was trying to add a node "ipswich" to a distributed database "navy/d" >and got the following error message : > >INGRES ERROR: 26802 User does not have permission to use one of the flags. >INGRES ERROR: 26002 Above error from Node: IPSWICH Database: DBDB >Request Terminated by Errors > >I am the owner of this database and should have the permission to >add other nodes to coordidator node. Also, INGRES/NET works fine for >me since I can issue "rtingres nodename:navy/d" from ipswich to >remote access navy/d on the coordinator site. If you are trying to do "ADD NODE" for "IPSWICH" the problem is likely to be that your effective INGRES user (ie STAR/NET login from coordinator site) on the IPSWICH machine doesn't have "Update System Catalogs" privilege (See ACCESSDB). ADD NODE works by adding information to the system catalogs in the database database (dbdb) for the remote node so it knows about your distributed database on the coordinator node. Since updating system catalogs is a privileged operation, it can fail with the above error if you don't have it (The actual error comes because STAR starts up a backend on the IPSWICH machine with the +U flag to update the system catalogs, and you're not allowed to use +U unless you have "Update System Catalogs" privilege.) There are other remote possibilities why its failing, but this is by far the most likely. >- Andy > Robert Fair RTI Technical Support
jhwang@CS.UCLA.EDU (07/12/89)
I tried to create a database "navy" with some of its relations allocated at one site and the others at the other site. Here is what I did : I created navy at one site "kingston" and copied all the data into this site. Later, I went to second site "ipswich" and tried to create some new relations at this site. Firstly, I use create command to create a new relation "test" and hope its data will be allocated at this site. Unfortunately, this data goes to location (directory) under the first machine. I then tried to specify the second site while using the create command. Nevertheless, I still got the error message like : 26826 Could not find database default AREA in IILOCATIONS. My questions are : Is this the right way to do it ? or how can I allocate some relations at one site and remaining relations at the other site ? Any response is appreciated.
robf@squid.rtech.com (Robert Fair) (07/13/89)
[User has problem createing a Star database on multiple sites] Setting up a multiple-site database should be pretty simple if you remember that a Star database links together multiple local databases. The following procedure should work: 1: Create local databases on each of your remote sites 2: Create a STAR database on your coordinator node 3: Create tables. This can be done in one of two ways: - Globally, through STAR - Locally, then create a link in STAR To create tables globally in Star: - Go into the Star database - CREATE the table, specifying node & database: CREATE TABLE mytbl (...) WITH NODE=ipswich, DATABASE=mydbname If you leave off the NODE/DATABASE Star will create the table in the coordinator database, which sounds like the problem the user had. To create tables locally and link in Star: - Access each local database through INGRES/NET - CREATE the table (or for a gateway IMPORT/REGISTER the table) - Go into the Star database - CREATE a LINK to the local table [or in INGRES 6.2 terminology REGISTER the table as a link]. The global method is simpler when the local DBMS is INGRES, while the local CREATE + LINK provides more flexibility for gateways and non-relational systems. Robert Fair Technical Support Relational Technology, Inc
bg0l+@andrew.cmu.edu (Bruce E. Golightly) (07/18/89)
Did you try including the LOCATION=location_name clause in the create?
It wasn't clear from your message. According to the manual I have, the
syntax is:
CREATE TABLE [locations:]linkname
(columnname format [,columnname format...])
[ WITH
[NODE=nodename, DATABASE=dbname,]
[TABLE=tablename,]
[LOCATION=locationname,]
[JOURNALING]
]
Bruce