Creation of another IDS instance

Dear All, In my CentOS 7 linux server we installed IDS 12.10FC8. Now we need another instance for another database project. How to do this. I am very new to Informix. 1. What steps need to follow. 2. What are the prerequisites. 3. How to differentiate both configuration files like ONCONFIG, SQLHOSTS, Services file, DBSERVERNAME, INFORMIXDIR, SERVERNUM,PORTNUMBER, ROOTPATH, etc. 3. How to manager both. Please help me on this. Thanks in advance.

Creation of another IDS Instance in same server/machine.

Similar to the existing build. 1. Select a new servername 2. Decide on new storage paths for the new instance 3. Decide on new network port/servicename for the new instance. 4. Add required sqlhosts entries for the new server. 5. Create a new onconfig file check each entry if it conflicts with an existing server. The following will certanly need to be different - DBSERVERNAME/DBSERVERALIASES - SERVERNUM - ROOTPATH/ROOTOFFSET - If onbar is used then BAR_ACT_LOG/BAR_DEBUG_LOG - If ISM is used then ISM_DATA_POOL/ISM_LOG_POOL - If Java Stored Procedures are used JVPLOGFILE/JVPPROPFILE - If Informix mirroring is used MIRRORPATH/MIRROROFFSET - If ontape is used TAPEDEV/LTAPEDEV Anything with a pathname may well need changing. 6. Install server as for the existing server. Regards, David. > On 25 August 2017 at 09:09 MUKESH TANUKU <mukeshbt1328@gmail.com> wrote: > > > Creation of another IDS Instance in same server/machine. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hi, assuming you want to create the second instance with the same version of Informix: - use the same directory where informix server is installed, i.e. $INFORMIXDIR is the same. - choose a different SERVERNUM (server number), - choose a different server name (and set $INFORMIXSERVER accordingly), - if desired: choose different name(s) for DBSERVERALIASES, - create a different onconfig file in $INFORMIXDIR/etc (and set $ONCONFIG accordingly), ( my onconfig files usually are named "onconfig.${INFORMIXSERVER}" ) - create separate shell scripts for each server instance to set the environment for each instance: - $INFORMIXDIR (is the same) - $INFORMIXSERVER (is different) - $ONCONFIG (is different) - $INFORMIXSQLHOSTS (can be the same, but will be different if you choose to have separate sqlhosts files (see below)) - $PATH and the library path environment variable, $CLASSPATH if needed, will all be the same. - you best create a new directory where you can place the chunks for the new dbspaces of the new instance, - best practice: create symbolic links to the chunk files, and then use the symbolic links when creating dbspaces and chunks and as value for ROOTPATH in the onconfig file. - choose a new file name (or better a new directory location) for the message and console log files. - if using ON-Bar choose new file names (or better directory location) for the BAR activity and BAR debug log files, - if using ON-Bar you may want to think about creating new (i.e. different) storage pools for the new instance. - you may want to think about creating a separate alarm program shell script, especially if you want to handle logical log file backups differently. Usually this is in $INFORMIXDIR/etc/alarmprogram.sh . - in the new onconfig file: - set SERVERNUM, DBSERVERNAME (and DBSERVERALIASES, if applicable), ROOTPATH (and MIRRORPATH, if applicable) to the new values. - set MSGPATH and CONSOLE according to the choosen path names of the message/console log files, - if using ON-Bar for backup and restore: set BAR_ACT_LOG and BAR_DEBUG_LOG to the chosen new file/path names, - if using ON-Bar and you chose to create new storage pools for the new instance: set parameters ISM_DATA_POOL and ISM_LOG_POOL accordingly, - if you chose to create a new alarm program shell script: set parameter ALARMPROGRAM accordimgly, - set parameter FULL_DISK_INIT to 1 ( in the new onconfig file only ! ) - create new entries in the sqlhosts file: - you can use the same sqlhosts file for multiple server instances. If you want to use separate sqlhosts files, then you create them and need to set $INFORMIXSQLHOSTS accordingly for each instance's environment. - at minimum add one entry for the new $INFORMIXSERVER name, - if desired add entries for DBSERVERALIASES names, - create new service names in /etc/services using different port numbers. Use these new service names for the new sqlhosts entries. - you CHECK AGAIN, that the ROOTPATH values in the different onconfig files are: - really different, - and the symbolic links (that you hopefully use) point to different files/locations or - do not cause an overlap (especially if using raw devices): look out for ROOTOFFSET and ROOTSIZE. - set the environment for the new server (using the newly created shell script). - do "onstat -c | egrep ROOT" to check that you get the new and correct environment. - you should now be ready to do "oninit -i" ... and when it asks your confirmation for the disk initialization: again make sure that you are working with the correct environment for the new instance. (The seeting of FULL_DISK_INIT to value 0 in the old instance environment hopefully prevents you from obliterating the old instances data.) I hope I did not forget anything important. Others may correct me in case I'm wrong. :-) Regards, Martin Fuerderer -- Informix Development Germany HCL Technologies Germany GmbH Frankfurter Ring 17 80807 Munich, Germany [1]http://www.hcltech.com/de --DISCLAIMER-- ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------- From: "MUKESH TANUKU" <mukeshbt1328@gmail.com> To: ids@iiug.org Date: 08/25/2017 10:09 AM Subject: Creation of another IDS instance [39752] Sent by: ids-bounces@iiug.org _________________________________________________________________ Dear All, In my CentOS 7 linux server we installed IDS 12.10FC8. Now we need another instance for another database project. How to do this. I am very new to Informix. 1. What steps need to follow. 2. What are the prerequisites. 3. How to differentiate both configuration files like ONCONFIG, SQLHOSTS, Services file, DBSERVERNAME, INFORMIXDIR, SERVERNUM,PORTNUMBER, ROOTPATH, etc. 3. How to manager both. Please help me on this. Thanks in advance. ********************************************************************** ********* Forum Note: Use "Reply" to post a response in the discussion forum. References 1. http://www.hcltech.com/de

Multiple instances are easy. Here are the steps: 1. You can use the single installation, no need to install again. 2. Normally, unless there is a reason to isolate one instance from the other, they can share a single sqlhosts file. 3. Make entries in the sqlhosts file for the new instances dbservername and dbserver aliases. 4. Create a new ONCONFIG file. You may copy the existing ONCONFIG to a new name then you must change: 1. SERVERNUM 2. DBSERVERNAME 3. DBSERVERALIASES 4. MSGPATH 5. If you will be archiving to disk using ontape then you may want to change the following if they are not set to a directory (ontape will name files with the server name so the instances CAN share archive directories if you want, but it's easier t manage restores if you use different directories): 1. TAPEDEV 2. LTAPEDEV 6. ROOTPATH That's pretty much it. Once you create the ROOTPATH file (if you are not using raw devices), you set INFORMIXSERVER to the new servername and run oninit -iv just like you did to create the first instance. TheFULL_DISK_INIT parameter in the original ONCONFIG file will prevent you from accidentally trashing your existing instance if you run the oninit -i with INFORMIXSERVER set to the wrong value. To manage one server or the other, just set INFORMIXSERVER and ONCONFIG to the one you want to work with and that is the one you will see. Users only need to set INFORMIXSERVER or explicitly connect to <databasename)@<servername>. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Fri, Aug 25, 2017 at 4:08 AM, MUKESH TANUKU <mukeshbt1328@gmail.com> wrote: > Dear All, > > In my CentOS 7 linux server we installed IDS 12.10FC8. Now we need another > instance for another database project. How to do this. I am very new to > Informix. > > 1. What steps need to follow. > 2. What are the prerequisites. > 3. How to differentiate both configuration files like ONCONFIG, SQLHOSTS, > Services file, DBSERVERNAME, INFORMIXDIR, SERVERNUM,PORTNUMBER, ROOTPATH, > etc. > 3. How to manager both. > > Please help me on this. Thanks in advance. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

A word of warning, consider the OP states being a new Informix DBA: - NEVER confuse your $ONCONFIG files - NEVER EVER set two $ONCONFIG files with the same SERVERNUM Failure to follow this guidelines may lead you to completely TRASH your instance. SERVERNUM is the only thing that prevents two instances to startup with the same data files. In the old days, the conflicting ports helped in avoiding that, both once we introduce the ability to start/stop the listeners that safeguard was gone. If you EVER see a message stating a shared memory cannot be created because the IDs are already in use, step back, take a deep breath and review EVERYTHING... you're a step away from disaster. If it happens NEVER EVER change the servernum to circunvent the situation... odds are you already have an instance running, and by changing the SERVERNUM you'll allow the new one to start. There are long standing feature requests to try to make the engine smarter in order to avoid such situations, but the usual resources shortage and the fact that this is not a trivial issue to solve, have been preventing progress... Regards. On Fri, Aug 25, 2017 at 2:13 PM, Art Kagel <art.kagel@gmail.com> wrote: > Multiple instances are easy. Here are the steps: > > 1. You can use the single installation, no need to install again. > > 2. Normally, unless there is a reason to isolate one instance from the > > other, they can share a single sqlhosts file. > > 3. Make entries in the sqlhosts file for the new instances dbservername > > and dbserver aliases. > > 4. Create a new ONCONFIG file. You may copy the existing ONCONFIG to a > > new name then you must change: > > 1. SERVERNUM > > 2. DBSERVERNAME > > 3. DBSERVERALIASES > > 4. MSGPATH > > 5. If you will be archiving to disk using ontape then you may want to > > change the following if they are not set to a directory (ontape will name > > files with the server name so the instances CAN share archive directories > > if you want, but it's easier t manage restores if you use different > > directories): > > 1. TAPEDEV > > 2. LTAPEDEV > > 6. ROOTPATH > > That's pretty much it. Once you create the ROOTPATH file (if you are not > using raw devices), you set INFORMIXSERVER to the new servername and run > oninit -iv just like you did to create the first instance. The> FULL_DISK_INIT parameter in the original ONCONFIG file will prevent you > from accidentally trashing your existing instance if you run the oninit -i > with INFORMIXSERVER set to the wrong value. > > To manage one server or the other, just set INFORMIXSERVER and ONCONFIG to > the one you want to work with and that is the one you will see. Users only > need to set INFORMIXSERVER or explicitly connect to > <databasename)@<servername>. > > Art > > Art S. Kagel, President and Principal Consultant > ASK Database Management > www.askdbmgt.com > > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on the IIUG, nor any other organization with which I am > associated either explicitly, implicitly, or by inference. Neither do > those opinions reflect those of other individuals affiliated with any > entity with which I am affiliated nor those of the entities themselves. > > On Fri, Aug 25, 2017 at 4:08 AM, MUKESH TANUKU <mukeshbt1328@gmail.com> > wrote: > > > Dear All, > > > > In my CentOS 7 linux server we installed IDS 12.10FC8. Now we need > another > > instance for another database project. How to do this. I am very new to > > Informix. > > > > 1. What steps need to follow. > > 2. What are the prerequisites. > > 3. How to differentiate both configuration files like ONCONFIG, SQLHOSTS, > > Services file, DBSERVERNAME, INFORMIXDIR, SERVERNUM,PORTNUMBER, ROOTPATH, > > etc. > > 3. How to manager both. > > > > Please help me on this. Thanks in advance. > > > > > > ************************************************************ > > ******************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...

OH, that reminds me, one item: In the sqlhosts file the new instance needs to use different port numbers or service names pointed to different port numbers than the existing instance! Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Fri, Aug 25, 2017 at 10:07 AM, Fernando Nunes <domusonline@gmail.com> wrote: > A word of warning, consider the OP states being a new Informix DBA: > > - NEVER confuse your $ONCONFIG files > - NEVER EVER set two $ONCONFIG files with the same SERVERNUM > > Failure to follow this guidelines may lead you to completely TRASH your > instance. > SERVERNUM is the only thing that prevents two instances to startup with the > same data files. In the old days, the conflicting ports helped in avoiding > that, both once we introduce the ability to start/stop the listeners that > safeguard was gone. > > If you EVER see a message stating a shared memory cannot be created because > the IDs are already in use, step back, take a deep breath and review > EVERYTHING... you're a step away from disaster. If it happens NEVER EVER > change the servernum to circunvent the situation... odds are you already > have an instance running, and by changing the SERVERNUM you'll allow the > new one to start. > > There are long standing feature requests to try to make the engine smarter > in order to avoid such situations, but the usual resources shortage and the > fact that this is not a trivial issue to solve, have been preventing > progress... > > Regards. > > On Fri, Aug 25, 2017 at 2:13 PM, Art Kagel <art.kagel@gmail.com> wrote: > > > Multiple instances are easy. Here are the steps: > > > > 1. You can use the single installation, no need to install again. > > > > 2. Normally, unless there is a reason to isolate one instance from the > > > > other, they can share a single sqlhosts file. > > > > 3. Make entries in the sqlhosts file for the new instances dbservername > > > > and dbserver aliases. > > > > 4. Create a new ONCONFIG file. You may copy the existing ONCONFIG to a > > > > new name then you must change: > > > > 1. SERVERNUM > > > > 2. DBSERVERNAME > > > > 3. DBSERVERALIASES > > > > 4. MSGPATH > > > > 5. If you will be archiving to disk using ontape then you may want to > > > > change the following if they are not set to a directory (ontape will name > > > > files with the server name so the instances CAN share archive directories > > > > if you want, but it's easier t manage restores if you use different > > > > directories): > > > > 1. TAPEDEV > > > > 2. LTAPEDEV > > > > 6. ROOTPATH > > > > That's pretty much it. Once you create the ROOTPATH file (if you are not > > using raw devices), you set INFORMIXSERVER to the new servername and run > > oninit -iv just like you did to create the first instance. The> > FULL_DISK_INIT parameter in the original ONCONFIG file will prevent you > > from accidentally trashing your existing instance if you run the oninit > -i > > with INFORMIXSERVER set to the wrong value. > > > > To manage one server or the other, just set INFORMIXSERVER and ONCONFIG > to > > the one you want to work with and that is the one you will see. Users > only > > need to set INFORMIXSERVER or explicitly connect to > > <databasename)@<servername>. > > > > Art > > > > Art S. Kagel, President and Principal Consultant > > ASK Database Management > > www.askdbmgt.com > > > > Blog: http://informix-myview.blogspot.com/ > > > > Disclaimer: Please keep in mind that my own opinions are my own opinions > > and do not reflect on the IIUG, nor any other organization with which I > am > > associated either explicitly, implicitly, or by inference. Neither do > > those opinions reflect those of other individuals affiliated with any > > entity with which I am affiliated nor those of the entities themselves. > > > > On Fri, Aug 25, 2017 at 4:08 AM, MUKESH TANUKU <mukeshbt1328@gmail.com> > > wrote: > > > > > Dear All, > > > > > > In my CentOS 7 linux server we installed IDS 12.10FC8. Now we need > > another > > > instance for another database project. How to do this. I am very new to > > > Informix. > > > > > > 1. What steps need to follow. > > > 2. What are the prerequisites. > > > 3. How to differentiate both configuration files like ONCONFIG, > SQLHOSTS, > > > Services file, DBSERVERNAME, INFORMIXDIR, SERVERNUM,PORTNUMBER, > ROOTPATH, > > > etc. > > > 3. How to manager both. > > > > > > Please help me on this. Thanks in advance. > > > > > > > > > ************************************************************ > > > ******************* > > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > > > > > > > ************************************************************ > > ******************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > -- > Fernando Nunes > Portugal > > http://informix-technology.blogspot.com > My email works... but I don't check it frequently... > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Thanks a lot to everyone who responded. I will work on this and get you back with good result. Thank u very much.