Re: Several instances of IDS 7.3X

Alejandro: You have to find out what exactly is causing the fatal error. You need to use oninit with the verbose (-v) option or look at the end of the message log (MSGPATH) file. Ron On Thu, 14 Sep 2000, Sistema Unico (CNA) wrote: > Hi Ron !!! > > Thanks for your recomendation about reading the Answers ON-Line of Informix. > Here I have the document. > I could set up two instances, for the same user "informix". This user > executes the .profile1 environment file for the instance #1 or the .profile2 > for the second instance. I could initialize just the first instance but not > the second. In the initialization of the second instance I obtain the sign > "Fatal Error in shared memory creation". I have a SUN Ultra-5 computer with > 64 MB RAM, and the two instances have configured the Resident segment Size > in 46000KB, and I can't change that quantity trough the ONMONITOR utility. > > Thanking in advance. > > Regards, > > Alejandro Cabrera > > > Alejandro wrote: > > I need to know how I can set up several instances of the Informix Dynamic > > Server 7.3x in the configuration files "sqlhosts", "onconfig" and the > > ".profile" (environment file). > > Now I have only one instance but I want to add one more...please I'd like > to > > see an example of several instances configuration. > > > > Thanks. > > > > Alejandro Cabrera > > acabrera@topmail.com.ar > > This is known as "multiple residency". Details can are in your IDS > Administrator's Guide, which can be found in the Answers Online > CD or at www.informix.com/answers. (And, dare I say it, > it's also covered in my book ;). See summary of the process below. > > NOTE: Multiple residency will eat > another bunch of shared memory, semaphores, and other OS resources. You > may need to increase semaphore parameters, shared memory, etc. > You'll also need to account for the instance in your system's startup and > shutdown scripts. Mult. residency is much better if you want a test > instance > or need to tune instances in different ways, but you have to be aware of the > downsides. > > Anyway, here is a summary of how to do it: > > 1. Create a new onconfig file in $INFORMIXDIR/etc. I suggest that you > use a naming convention of onconfig.INSTANCE_NAME, where INSTANCE_NAME > describes this instance. Example: onconfig.test. > > 2. Modify the new onconfig file to meet the new instance's needs. Make > SURE that you change all parameters that reference pathnames on the system > (ROOTPATH, MSGPATH, etc.) so they don't overwrite any existing data. > You'd also need to change at least SERVERNUM, DBSERVERNAME and > DBSERVERALIASES. > For the DBSERVER* values, I would generally use INSTANCE_NAME from step 1, > followed by the type of connection (_tcp, _shm, etc.). Example: test_shm. > There may be other parameters, but these are the first ones that come to > mind. > > 3. Create disk and links for the ROOTPATH. > > 4. Add your new DBSERVER* values in $INFORMIXDIR/etc/sqlhosts. > > 5. Update /etc/services with the network connections from the DBSERVER* > values. > > 6. In user profiles, set: INFORMIXDIR, INFORMIXSERVER, PATH, and ONCONFIG > to reflect the new values. > > 7. Initialize. > > This is just from memory, so I'd suggest that you review some of the above > references before proceeding. > > Ron F. > > ________________________________________________________________________ > Ron Flannery <mailto:rflanner@informixhandbook.com>, 248-887-8470x40 > > Lead author, Informix Handbook President, One Point Solutions > "Your Complete Reference" "Informix & Web/Database solutions" > http://www.informixhandbook.com http://www.one-point.com > ________________________________________________________________________ > >