I've seen this message occur when "root" attempts to run ingstart or
ingstop without "su"ing to "ingres".  If "root" runs ingstart, it sets
up the memory segment so "root" (not "ingres") owns it, and "ingres"
can't access it.  Conversely, if root stops the db, it may not remove
the ingres-owned segments

This doesn't appear to be the case considering the timeline given,
but...

In the event that "root" has tried (and failed) to run ingstart, have
"root" run ingstop, kill the ingres processes if necessary, and use
csreport/cscleanup to remove the shared memory segments.  Then have
"ingres" start the dbms, it should come up ok at that point.

Hi Teisha,

One more important point to check when you get the E_CL2537 message, reported by
the recovery server at startup or the dbms or even a pseudo server (as infodb).
Assuming that all Ingres process are shutdown and there is no more Ingres IPCs allocated.

          ! Even confirmed by a reboot !

Before restarting Ingres, check that the following directory is empty

$II_SYSTEM/ingres/files/memory

If there are some old files left there, you must remove them when Ingres is stopped.

When Ingres is running, all the files under memory must be present and empty.
Never remove them when Ingres is up !

Usually (according to which servers are started):

/home/ingres> cd $II_SYSTEM/ingres/files/memory
/disk2/ingres_260305/ingres/files/memory> ls -l
total 0
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 Repshmem.mem
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 caaudit.mem
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 iievents.001
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 lglkdata.mem
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 server.0
-rw-r--r--   1 ingres     users            0 Aug 19 09:48 server.2
-rw-r--r--   1 ingres     users            0 Aug 19 09:47 sysseg.mem
/disk2/ingres_260305/ingres/files/memory>

HTH,
Cheers,
Jean-Luc

-----Original Message-----
From: info-ingres-bounces@ams.org [mailto:info-ingres-bounces@ams.org]On
Behalf Of Winkler, Teisha
Sent: Tuesday, August 17, 2004 6:26 PM
To: 'info-ingres@ams.org'
Subject: [Info-Ingres] UNIX Defrag Command

    Running Ingres II 2.0 patch 9181 on AIX 4.3.3.

    Running weekend maintenance job in the following order:

        1. Checkpoint
        2. Shut down Ingres Net
        3. Kill any connected sessions
        4. Run some table maintenance to delete data
        5. Run modifies on all user tables
        6. Run verifydb to purge temporary or expired tables
        7. Optimizedb
        8. Sysmod
        9. Stop Ingres completely (Ingres reported down at 08:15:39)
        10. Use UNIX command to defrag all the file systems
(defragfs)
            including /ingres/log, /ingres/jnl, /ingres/dmp,
/ingres/data, /ingres/ckp
        (this begins at 08:15:40 ends at 08:22:23)
        11. Restart Ingres by doing an ingstop and then ingstart

    During step 10 I am getting messages in the errlog.log reporting:

        ::[LOGSTAT         , 3012c040]: Sun Aug 15 08:22:04 2004
E_CL2537_CS_MAP_SSEG_FAIL      Failure in attempt to map the UNIX system
segment (shared memory).  The most common causes of this problem are: 1)
user does not have the required privileges; 2) the shared memory has not
been installed.  If not installed, the CSINSTALL utility can be used to
install the shared memory segment.
       ::[II_JSP          , 30196040]: Sun Aug 15 08:22:05 2004
E_CL2537_CS_MAP_SSEG_FAIL      Failure in attempt to map the UNIX system
segment (shared memory).  The most common causes of this problem are: 1)
user does not have the required privileges; 2) the shared memory has not
been installed.  If not installed, the CSINSTALL utility can be used to
install the shared memory segment.
       ::[II_JSP          , 30196040]: Sun Aug 15 08:22:05 2004
E_DM007F_ERROR_STARTING_SERVER Could not start the server due to an internal
error.

    Sometimes Ingres will come back up. One time it did not. I had to
reboot the server before Ingres would start.

    Does anyone have any experience with the defrag command having
problems with Ingres? Can messages get into the Ingres errlog if Ingres is
down?

    I have no experience with the defrag. I am doing this at my location
as part of a directive towards common maintenance for this Ingres based
system.

    Thanks, teisha

teisha winkler
EDS - Lordstown Complex
Lordstown, OH

Phone:330-824-5711(8-534)
Pager: 330-910-0737

_______________________________________________
Info-ingres mailing list