Re: shared memory ininitialization problem

Informix-Admnistrator wrote: > > Greetings! > > We're in trouble because we can't initialize shared memory. What might > be the problem? > > Here is an excerpt from the error log, showing the different types of > error messages we have got so far: [SNIP] > we removed the process with the key 52564801 (had to become su first, > because owner = root ). > Then we changed Shared memory parameters in the onconfig file, ran > oninit -s, but then we have got the second type of error message.> > Is it a Unix (Solaris) or Informix problem? Where is the place to look > at for documentation? Looks to me like this is either a new machine or you recently build a new kernel and the system config parameters are not properly set. Check out the release notes for usable minimum values for the kernel build parameters and build and boot a new kernel. I am reasonable certain that this is hte problem. HOWEVER, read on. I have a few suggestions below on your ONCONFIG parameters. > RESIDENT 0 # Forced residency flag (Yes = 1, No = > 0) If you have enough memory set RESIDENT to 1. The can make a VERY BIG difference in performance especially on Sun hardware. > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 1 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps> to one Separate issue but if you have a multiprocessor box and are only using one CPUVP set SINGLE_CPU_VP to 1 and the engine will be able to reduce its overhead needed to support multiple CPU VPs. > #SHMBASE 0x0a00000 # Shared memory base address > ORIGINAL? > SHMBASE 0x0A000000L # GEAENDERT NACH ADMIN G 37-65 KB Look up the correct value for your platform in the release notes. The value in the onconfig.std and in your previous ONCONFIG file from an earlier version may no longer be valid. Art S. Kagel