home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!pmafire!mica.inel.gov!ux1!news.byu.edu!hamblin.math.byu.edu!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!wupost!darwin.sura.net!jvnc.net!ams.com!e-math.ams.com!ash
- From: ash@ulysses.mr.ams.com (Alan Harder)
- Subject: Re: Problem installing Ingres 6.4/02 under SunOS 4.1.3
- In-Reply-To: richard@ariel.ucs.unimelb.EDU.AU's message of 16 Nov 1992 11:02:14 +1100
- Message-ID: <ASH.92Nov16110704@ulysses.mr.ams.com>
- Sender: news@e-math.ams.com (USENET News System)
- Nntp-Posting-Host: ulysses.mr.ams.com
- Organization: American Math. Society
- References: <jstewart.721685840@cunews> <1e6oe6INNcrr@ariel.ucs.unimelb.EDU.AU>
- Date: Mon, 16 Nov 1992 16:07:04 GMT
- Lines: 82
-
- In article <1e6oe6INNcrr@ariel.ucs.unimelb.EDU.AU> richard@ariel.ucs.unimelb.EDU.AU (Richard Begg) writes:
-
- jstewart@alfred.carleton.ca (John Stewart) writes:
-
- >|I just installed Ingres 6.4/02 on a Sparcstation 10 running SunOS 4.1.3 but
- >|when it tries to start up it fails with the following error
-
- >|---------------------- RESOURCE CHECKING COMPLETE -----------------------
-
-
- >|Allocating 401408 bytes of shared memory...
-
- >|!shmat for id 201 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
- >|Could not create the system segment, does your kernel have enough
- >|shared memory or has this program already been run?
-
- >|-----------------------------------------------------------------------------
-
- >|Has anyone seen this problem before? I'm not entirely surprised since
- >|the release notes only guarantee that it works under 4.1.1 or 4.1.2.
-
- > This problem is due to a lack of shared memory configured in the Kernel
- > rather than a OS version problem. The fix is to add more shared memory
- > with a line something like this in your kernel config file. e.g.
-
- > options SHMSIZE=2000 # allocate 2MB of shared memory
-
- > I trust you have all the sysV IPC stuff turned on as well (semaphores etc).
-
- Actually, there is a problem running 6.4/02 on 4.1.3 on the MP class
- machines which causes this error.
-
-
- I found the following on Ingres Advisor:
-
- >Abstract:
- >OS_CONFIG: Ingres 6.4 is not certified against SunOS 4.
- >1.3. However if you do use this combination, one action
- >you need to take before you can startup Ingres on this unsupported
- >OS follows.
-
-
- >Expert note:
- >You will encounter some problem starting up Ingres if you try to run
- >Ingres on SunOS 4.1.3, which is not yet certified.
-
- >The problem resides in the way Ingres attach the LG/LK shared segment
- >through csinstall; we use an adress as a parameter to shmat (0xf4000000)
- >that worked on SunOS 4.1.2 and doesn't work anymore on SunOS 4.1.3.
- >Fortunately, we can set II_LG_MAP_ADDR to the value 0x10000000
- >(ingsetenv II_LG_MAP_ADDR 10000000). SunOS 4.1.3 will accept to attach
- >your segment there.
-
- >These tests were done using a SPARC 10 Model 30.
- >There were no other problem reported; tests were done with a database
- >and disks from a SPARC 2 (!). Performance ratio between SPARC 2 and
- >SPARC 10 was not measured but the customer was more than happy. SPARC
- >10 behaves as its competitors RS6000 and HP9000/7x0 for graphics and
- >seems to run Ingres server better.
-
- >NOTE: Remember we have not yet certified on SunOS 4.1.3 and this
- >environment variable is UNSUPPORTED.
-
-
- >Releases affected: 6.4/01(su4.u42) - Releases not affected:
- >Errors:
- >Bugs/SIRS:
-
-
- Well, the document is wrong, because 6.4/02 is now certified for use
- with 4.1.3. The rest of it is right, though. The above fix worked
- for us.
-
-
-
-
- -Alan Harder
-
- These opinions are mine. You can't have them. Stop, thief!
-