js

My /etc/system has the following:

set semsys:seminfo_semmni=100
set semsys:seminfo_semmns=1000
set semsys:seminfo_semmnu=30
set semsys:seminfo_semmsl=50
set semsys:seminfo_semopm=10
set semsys:seminfo_semume=10
set semsys:seminfo_semusz=96
set semsys:seminfo_semvmx=32767
set semsys:seminfo_semaem=16384
set shmsys:shminfo_shmmax=512000000
set shmsys:shminfo_shmseg=10
set shmsys:shminfo_shmmni=100

set rlim_fd_cur = 2048


syscheck -v says:

Checking host "s1006" for system resources required to run Ingres 2006...

64-bit kernel running.

514 file descriptors per-process required.
65536 is the current system hard limit.
65536 is the current system soft limit.

145678336 byte shared memory segment required by LG/LK sub-systems.
4112384 byte shared memory segment required by DBMS server(s).
0 byte shared memory segment required by shared DBMS cache(s).
0 bytes is the maximum shared memory segment size.

3 shared memory segments required.
0 is the total number of shared memory segments allocated by the system.
0 shared memory segments are currently available.

35 semaphores required.
1000 is the total number of semaphores allocated by the system.
1000 semaphores are currently available.

2 semaphore sets required.
100 is the total number of semaphore sets allocated by the system.
100 semaphore sets are currently available.

339707k bytes of swap space required.
4662104k bytes is total swap space allocated by the system.
4631368k bytes is the total swap space currently available.

Your system may not have sufficient resources to run Ingres 2006 as
configured.


Thus, I cannot start up ingstart

js

As you can see it sees the semaphore settings correctly, but not shared
memory. Probably a parsing error somewhere.

karl & betty schendel

I take it this is Solaris? I thought I fixed that. Either it doesn't
work on your version (which is ...?) or the fix didn't make it into
Ingres 2006.

Anyway, temporary replace $II_SYSTEM/ingres/utility/syscheck with a
symlink to /bin/true and Ingres should come up fine.
Don't lose the original syscheck, you might want it later.

Karl

PS it's not parsing /etc/system, it's reading some kernel junk.
The facility rcheck was using changed from version to version IIRC.

js

I am using Solaris9 ( as per Subject ).
BTW ... I am using the Community Edition


Thanks. I'll try this later.

goj993

Another thing to check - are the shmsys and semsys modules loaded?
Check with modinfo. If they're not loaded, load them using modload and
add to /etc/system:
forceload: sys/semsys
forceload: sys/shmsys