Re: Setting Up a Second Instance

I've just set up four instances, my basic steps were: o Determine breakdown of dbspaces and sizing. In my case I determined that I wanted four dbspaces: one each for root, logical logs, physical logs, and data. I also contacted our system administrator and arranged for four UNIX devices (these will be chunks in Informix lingo) to be available in the correct sizes, one for each of the dbspaces (there are many ways to architect the dbspaces, not going into that here) Important Note: two instances may not share the same chunk). o Each instance has its own onconfig file, so I copied an existing onconfig file. I also decided what naming conventions I would use. In my case I the instances were called d1, d2, d3, d4. So for d1, the onconfig file was called onconfig.d1. For d2, onconfig.d2, and so on. I continued this naming convention with other files, such as the online log, since each instance has its own log file. o The instance then needs to be initialized. Set and export ONCONFIG and INFORMIXSERVER, then execute onmonitor to bring up the administrative ui (continuing with my naming convention, ONCONFIG=onconfig.d1, INFORMIXSERVER=server1_shm (forgot to mention the $INFORMIX/etc/sqlhosts -you'll entries in there for each instance since the server name must be different for each). Then choose menu item PARAMETERS, then INITIALIZE - then follow the flow. o After initialization the logical and physical logs are in the root dbspace. If you want them in their own space, you'll have (a) create then using onspaces, do an Informix archive to get them recognized, then remove the logical logs that are in root; similar for physical log, but its a move, and can be done via onmonitor:PARAMETERS. This is only a quick synopsis - you really need to read up on this, search for posts and replies in this newsgroup on this subject. Gotchas: o Make sure each server number, set in onconfig, is unique (I used 1, 2, 3, 4). o Each instance must be backed up (archived in Informix lingo) separately. o Each instance has it's own resources, including log files. o Make sure you know which instance you're referencing - I do this buy changing my UNIX prompt whenever I change instances - I do thing automatically with built-in shell functions that are initialized during login via .profile. If you have test and production, you don't want to take the engine off-line thinking you are referencing test when in reality you are referencing production. But don't worry, if you do and they fire you, then you can just go on to the next client and do it to them (just joking!). Paul Crompton wrote: > If I am going to try to set up a second instance, for testing and some > development what are some steps and gottcha's that I should be aware. > > We've been running Informix for about 6 months so I a still learning how to > work with it. > > We are running IDS 7.30.UC5 on an HP-UX 10.2 > > Any help will be greatly appreciated. > > TIA > Paul Crompton > pcrompton@clerk-of-court.co.lee.fl.us > > * Paul EXT. 2270