Ingres error under 6.4/03 running SUNOS 4.1.3

Ingres error under 6.4/03 running SUNOS 4.1.3

Post by Thomas J Lohm » Fri, 12 Mar 1993 07:13:47



Hi, I'm trying to get Ingres up and running and it seems to fail
during the allocation of shared memory.  I am wondering if anyone has
any ideas what could be causing this error.  It seems to me that someone
a while back had a similar error...In case you missed the subject header,
they're running Ingres6.4/03 on top of SUNOS 4.1.3.

Here is the error message:

   Allocating 671744 bytes of shared memory...

   !shmat for id 101 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?

Any help would be greatly appreciated,

--tom

    Thomas Lohman - Research Specialist/Software Engineer
    MIT Building 36 - Room 297
    Cambridge, MA. 02139

    Phone: 617-258-6485

--
    Thomas Lohman - Research Specialist/Software Engineer
    MIT Building 36 - Room 297
    Cambridge, MA. 02139

 
 
 

Ingres error under 6.4/03 running SUNOS 4.1.3

Post by Kevin Hopkin » Fri, 12 Mar 1993 19:52:33


In your message you said:
-> Hi, I'm trying to get Ingres up and running and it seems to fail
-> during the allocation of shared memory.

->    Could not create the system segment, does your kernel have enough
->    shared memory or has this program already been run?

I have just moved Ingres from a SparcStation2 to a SparcStation10/30 under
SunOS 4.1.3, though it was version 6.3. We had the same problem and Ingres
support told us to set the ingres variable II_LG_MAP_ADDR to e0000000 and
then startup ingres as normal. Worked a treat! The problem is that some
machines have their stacks at different addresses. This solution seems to
cure the problem.

The value of II_LG_MAP_ADDR may vary depending on your hardware. If unset
it ingres uses the correct value on SS2 machines, and I presume most
others.

+-----------------------------------------------------------------------------+
| Kevin Hopkins, Technical Services Coordinator, Technical Services Group,    |
| Department of Computer Science, University of Nottingham, University Park,  |
| Nottingham, ENGLAND, NG7 2RD                                                |
+-----------------------------------------------------------------------------+

+-----------------------------------------------------------------------------+

 
 
 

Ingres error under 6.4/03 running SUNOS 4.1.3

Post by Calgary (Kal-gr » Sat, 13 Mar 1993 07:44:03


This has been posted several times, but what's one more time??

In the release notes you are advised to set the following env variable for
SUN OS 4.1.3 ...

ingsetenv II_LG_MAP_ADDR 10000000

Cheers,

Paul

 
 
 

Ingres error under 6.4/03 running SUNOS 4.1.3

Post by Joe Polivi » Sun, 14 Mar 1993 01:59:02


We recently had a similar problem in trying to bring up INGRES
on SunOs 4.1.2 and INGRES 6.4/02.  Evidently there is a known
Sun bug in release 4.1.2 that stops the INGRES 'csinstall'
utility from operating correctly.  'csinstall' will hang up
until cancelled.  INGRES Tech Support provided me with this
information, and also gave me the patch number from Sun
that fixes the problem.
--
Joe Polivick
Database Administration
Indiana University

 
 
 

Ingres error under 6.4/03 running SUNOS 4.1.3

Post by Peter Boothby--Sun Melbourne » Tue, 16 Mar 1993 14:47:05



Quote:

>Hi, I'm trying to get Ingres up and running and it seems to fail
>during the allocation of shared memory.  I am wondering if anyone has
>any ideas what could be causing this error.  It seems to me that someone
>a while back had a similar error...In case you missed the subject header,
>they're running Ingres6.4/03 on top of SUNOS 4.1.3.

>Here is the error message:

>   Allocating 671744 bytes of shared memory...

>   !shmat for id 101 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?

Try this before startup:

ingsetenv II_LG_MAP_ADDR 10000000

I think this has something to do with the change of the base address of the
stack in 4.1.3. Ingres have a default shared memory address that clashes with
the change so you need to use this environment variable to change it. There
is a note to this effect in the release notes for 6.4/03.

---
Pete Boothby
============================================================================


  \_,-._/  180 Albert Rd                      Phone : +61 3 696 0099
       v   Melbourne, Vic  3205                 Fax : +61 3 690 0948
===========================================================================

 
 
 

1. RFI: ingres 6.4/03 versus 6.4/04

We are looking into upgrading our installation
from ingres 6.4/03 to 6.4/04 on sunOS 4.1.3 for
sparc 2 and 10.

Questions:

What are the advantages of upgrading the servers?

What are the advantages of upgrading the clients?

Is the /04 client compatible with the /03 server?

Why are all my questions have the same lenght?

Merci/Thank you,

Pierre Osborne

2. Composite fields with Access 2.0/7.0

3. 6.4/03 Installation Problems - SunOS 4.1.3 + DNS

4. VFP6 find all databases this directory and lower

5. Ingres 6.4/05 (axp.vms/03) patch 5430 very slow

6. Cold Fusion - Paradox access error

7. Ingres 6.4/03 on Solaris 2.5.1

8. ETL Discussion Groups?

9. Ingres 6.4/05/03

10. Ingres 6.4/05/03 on the Alpha

11. Lost DB Events in INGRES 6.4/03

12. Images Compilation FAILES, SCO UNIX, INGRES 6.4/03

13. Ingres 6.4/05 (axp.vms/03) patch 5430 very slow