Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Ingres Topics / September 2004

Tip: Looking for answers? Try searching our database.

URGENT:  Cannot allocate shared memory

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Frank Fan - 21 Sep 2004 11:23 GMT
Hi,

Ingres 4.6  on  HPUX 10.20
It have been working for a long time and don't have any problem before
today. Besides, We don't change any configurations recently.

I found one database couldn't be accessed and other databases works fine
in the same server, So I tried to restart ingres. But Ingres couldn't
start and some error messages attached below.
Currently, shnmax of HP kernel is 201326592  and connected_sessions is 256.
From the error message , it seems like lack of shared memory.  In fact,
I've killed all processes about ingres and cleaned shared memory with
$II_SYSTEM/ingres/utility/ipcclean.

Any help would be highly appreciated.

Frank

-------------------------------------------------------------------

Allocating 5890048 bytes of shared memory...

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

 -----------------------------------------------------------------------
|                           ***ERROR***                                 |
|                                                                       |
| Cannot allocate shared memory for the logging and locking system.     |
| You can either free shared memory or reconfigure the locking and      |
| logging system with less users.                                       |
|                                                                       |
| Please run 'iistartup -init' when you have solved this problem.       |
|                                                                       |
 -----------------------------------------------------------------------

Checking INGRES installation environment...

INGRES installation is setup correctly

Starting a DBMS server (iidbms) ...
iirundbms: server would not start.
        II_SYSTEM must be set in your environment.
        Has the csinstall program been run?
        II_DATABASE, II_CHECKPOINT, II_JOURNAL and II_DUMP
                must also be set.  See II_CONFIG/symbol.tbl
        Check the file '$II_SYSTEM/ingres/files/errlog.log'
                for more details concerning internal errors.
        See your Installation and Operations Guide for more
                information concerning server startup.

Checking INGRES installation environment...

INGRES installation is setup correctly

Starting a DBMS server (iidbms) ...
iirundbms: server would not start.
        II_SYSTEM must be set in your environment.
        Has the csinstall program been run?
        II_DATABASE, II_CHECKPOINT, II_JOURNAL and II_DUMP
                must also be set.  See II_CONFIG/symbol.tbl
        Check the file '$II_SYSTEM/ingres/files/errlog.log'
                for more details concerning internal errors.
        See your Installation and Operations Guide for more
                information concerning server startup.
logout
ERROR - Unable to start Ingres session !!!
Frank Fan - 21 Sep 2004 13:08 GMT
Hi all,
    Mark Luijendijk gave me a great help and the problem was resolved
by the following steps.

    Try ipcs|grep ingres. You shouldn't get anything back, however, in
your case
I wouldn't be surprised.

In case Ingres has allocated some resources you'll see something like

m   45282 -rwxr-xr-x   ingres

or so. The first character ("m") points to the resource type. For Ingres
this can be either "m" for memory or "s" for semaphore; the number (45282)
is the "key". You need to remove these before you can restart Ingres. Log on
as Ingres (or root) and type:

ipcrm -<resource-type> <key>

or in case of the above

ipcrm -m 45282

After removal of all the ipcs stuff (ipc BTW stand for Inter Process
Communication) rerun ipcs|grep ingres and nothing should appear. Next, go to
$II_SYSTEM/ingres/files/memory. If there are any files in this directory you
need to remove them all (ONLY WHEN INGRES IS DOWN, WHEN INGRES IS UP THERE
MUST BE FILES INTHIS DIRECTORY, INGRES CREATES THEN FOR YOU).

Finally, check if any Ingres processes are still running (frankly, you
should start with that, but I assumed you alrready did..), if there are any
kill 'em all (except for your login shell ;) ).

Now you should be able to start Ingres. If not, please get back to me.

> Hi,
>
[quoted text clipped - 63 lines]
> logout
> ERROR - Unable to start Ingres session !!!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.