Re: User/Instance allocation problems

Gentelmen, I would like to mention that the "INFORMIX-OnLine Administrator's Guide Version 5.0" (Informix part number 000-7106) has a very clear discription of how to implement "Multiple Residency" on pages 9-6 through 9-11. The basics of which are: Make a copy of tbconfig.std for each instance of Informix OnLine. ie. tbconfig.1, tbconfig.2, tbconfig.3, etc... Make sure that the ROOTPATH, SERVERNUM, DBSERVERNAME, and MSGPATH are unique (and correct) for each tbconfig file. Remember to set and export the TBCONFIG env variable for the instance of OnLine that you wish to work with. Example: export TBCONFIG=tbconfig.1 Once TBCONFIG is set, use tbmonitor to initialize, or startup (and bring Online) that instance of Informix OnLine. Remember to have each user set and export their TBCONFIG env variable to reflect the correct OnLine database server environment. Please keep in mind that this is just my 2 cents worth, no flames please. Regards, Walter S. Tyszka } > The dependenet shared memory parameters of locks, buffers, and } > tablespaces are all more than adequate in all three instances to handle } > the 30 users we are specifying for it to initialize with. However these } > instances will not all start. Simply comes back and says shared memory } > not initalized on the others after we start the first one. We can get just } > one up. If we drop the number of users to 10 in each instance the } > instances will all come online. And this is without touching any other } > parameters. } > } > } } James, } } USERS in the tbconfig file will affect the size of shared memory. } You say that when you do tbinit you only get fatal error in } shared memory initialization...what is getting written, if anything } to the MSGPATH? I can assure you that we don't have some built } in code that is checking the lisenscing. It really does sound like } a kernel parameter (specifically shared memory related) that is } probably causing the problem. I'm unfamiliar with your particular } hardware, but on other systems the parameters I'd check would be } SHMMAX (max size of shared memory segment), SHMSEG (max number of } segments one process can attach to), SHMMNI (total number of shared } memory segments the entire machine can handle) and anything that } would limit the total ammount of shared memory. Hope this helps } out a bit. } } Jacques } } -- } ******************************************************************** } * Jacques P. Renaut "I'd dazzle you with brilliance * } * Informix Advanced Support if I only had the knack..." * } * email: jrenaut@informix.com #include <disclamier.h> * } ******************************************************************** } --