home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!gatech!darwin.sura.net!uvaarpa!cv3.cv.nrao.edu!mail-to-news-gateway
- From: drcoles@somnet.sandia.gov (Dwight R Coles)
- Subject: Shared Memory Address Bug, Ingres on Sun 4.1.3
- Message-ID: <9301071943.AA09853@somnet.Sandia.GOV>
- Sender: root@nrao.edu (Operator)
- Organization: National Radio Astronomy Observatory
- Date: Thu, 7 Jan 1993 19:43:02 GMT
- Lines: 41
-
- Sorry if you on the list have already heard of this bug, but since
- I've been off of it for two months, I don't know if it has been
- discussed. Anyway....
-
- Ingres (ver 6.4/02/00) fails to iistartup properly on Sun 4.1.3
- due to a bad shared memory address. This bug popped up at 4.1.3,
- as things were OK under 4.1.2 and earlier. You will recognize it
- by the following output from the step in iistartup which
- "allocates shared memory":
-
- !shmat for id 102 at address F4000000 fails
- !errno = 22
- !Can't map locking segment into memory at address FFFFFFFF
- !Check or adjust the value of II_LG_MAP_ADDR.....
-
- To fix this, set the Ingres variable II_LG_MAP_ADDR to 10000000.
- Example:
-
- ingsetenv II_LG_MAP_ADDR 10000000
-
- You will probably want to stick this line into the rc or the rc.local
- file immediately before the "su ingres...." line.
-
-
-
- A second bug which we found on the Ingres 6.4/02/00 tape for Suns is
- that the ingres/files/iishutdown file is in compressed form (.Z). If
- you are doing a new install, there is no iishutdown available when
- iibuild tries to do it (the iishutdown step occurs BEFORE the uncompress
- step). Thus, after reading the tape, you may want to:
-
- cd utility
- uncompress iishutdown.Z
- cd ..
-
- On updated installs, you simply get to use the old version of iishutdown
- to shut down any old versions of Ingres back-ends (which is fine). Then
- the uncompress command overwrites the iishutdown file with a new copy.
-
- Later - Dwight Coles drcoles@sandia.gov
-
-