728x90


Informix Dynamic Server and Linux -- Up and running

A cookbook for installing Linux and IDS





IDS was one of the first commercial database products ported to Linux. Today the advantages of running IDS 10.0 on the Linux platform are:

  • Support for new Linux platforms
  • Transparent optimization and exploitation of Linux environments
  • Exploitation of Linux 2.6 kernel features
  • Utilization of asynchronous I/O and direct I/O for enhancing I/O performance
  • Processor affinity to achieve improved scalability and parallelism
  • Performance optimization using configurable page sizes
  • Additional installation methods on Linux systems
  • Simple Network Management Protocol (SNMP) support
  • Interprocess communication with stream pipes
  • Scalability on the 2.6 kernel

This article describes a test configuration of IDS on Linux. By following the details I describe, you should be able to customize your own IDS configuration on Linux. We'll start by looking at the setup of Linux itself.

Installing Linux

Technical details for the sample system

The system used for installing Linux and IDS was a standard PC:

  • Pentium III 600MHz
  • 512MB RAM
  • 2 x 15.3GB disks (Maxtor 51536U3 ATA)

For IDS version 10.0 (32-bit) the CPU must be compatible with an Intel i686. Compatible CPU types should be at a minimum Intel Pentium II / Pentium Pro or AMD Athlon. For our sample system, the first disk was dedicated for installing the Linux OS, and the second disk provided space for the IDS databases. No partitions should exist on the disks.

Red Hat Enterprise Linux 4

For this example, Red Hat Enterprise Linux AS release 4 (Nahant) was installed on the sample PC. The following steps will help you to set up a Linux system that is ready to install and run IDS. Please note, the installation of Linux will destroy any operating system and data on the PC.

Detailed instructions can be found at the "Red Hat Enterprise Linux Documentation" page in the document "Red Hat Enterprise Linux Installation Guide for the x86, Itanium, and AMD64 Architectures.". See the Related topics section "Learn" for links.

During installation, you can use the default settings in most cases. Here are some hints and exceptions:

  • Boot the PC from the first of the 4 CDs.
  • In step Language Selection choose English.
  • In step Keyboard Configuration choose the layout for your keyboard.
  • In step Upgrade Examine select Install Red Hat Enterprise for a fresh install.
  • In step Automatic Partitioning select /dev/hda only (deselect /dev/hdb).
  • In step Package Installation Defaults select Customize software packages ....
  • In step Package Group Selection, make these selections:
    • in chapter Applications select Graphical Internet (get Firefox browser).
    • in chapter Development select Legacy Software Development (get packages for compatibility to older Red Hat versions).
  • Reboot after the installation is completed.
  • Log in as user root and open a terminal (Applications -> System Tools -> Terminal).
  • For IDS graphical tools, install OpenMotif runtime from CD #3:
    • Put CD #3 in the drive. It should be automatically mounted
    • To install the package, type following command in the terminal:
      1
      rpm -Uvh /media/cdrom/RedHat/RPMS/openmotif-2.2.3-6.RHEL4.2.i386.rpm
    • To eject the CD from the drive type the command:
      1
      eject
  • To access IDS raw devices with Kernel Asynchronous Input Output (KAIO), install libaio from CD#3:
    • Put CD#3 in the drive. It should be automatically mounted.
    • To install the package, type following command in the terminal:
      1
      rpm -Uvh /media/cdrom/RedHat/RPMS/libaio-0.3.102-1.i386.rpm
    • To eject the CD from the drive type the command:
      1
      eject

Novell SUSE Linux Enterprise Server 9

For this example SUSE Linux Enterprise Server 9 (SLES 9) was installed on the sample PC. The following steps should help to set up a Linux system which is ready to install and run IDS. Please note, the installation will destroy any operating system and data on the PC.

Detailed instructions can be found at the "SUSE Linux Documentation" page in the document "SUSE LINUX Enterprise Server 9 Administration and Installation" (PDF). See the Related topics section "Learn" for links.

During installation, you can use the default settings in most cases. Some hints and exceptions are listed below:

  • Boot the PC from the first of the 4 binary CDs.
  • In step Select your language, choose English (US).
  • In step Installation Settings
    • Click on Keyboard layout and choose the appropriate layout.
    • Click on Partitioning and check swap and root partitions are created in /dev/hda.
      • Choose Base partition setup on this proposal.
      • Choose root partition (should be /dev/hda2) and change its file system type to ext3 using the Edit menu.
    • Click on Time Zone and choose the appropriate time zone.
  • Accept the installation settings and confirm the start of installation.
  • Reboot after the installation is completed.
  • Log in and open a terminal (click on terminal looking icon in the panel).

Installing IDS

For this example, the trial version of IDS version 10 (32-bit) can be downloaded using installed Firefox or Konqueror browser from "Informix product family -- How to get Informix product downloads -- IBM Software" page. See the Related topics section "Get products and technologies" for a link. Click on Informix Dynamic Server EE V10.0 Trials for getting the tar archive iif.10.00.UC3R1TL.Linux.tar and save it to /tmp directory. Sign in with IBM ID and password may be required. Choose download using http.

If you are not already logged in as user root, then switch user id to root:

1
su -

Create group and user informix, and enter password:

1
2
3
groupadd informix<br>
useradd -g informix -m informix<br>
passwd informix

Unpack the downloaded archive of IDS:

1
2
3
4
mkdir /opt/informix<br>
chown informix:informix /opt/informix<br>
cd /opt/informix<br>
tar xvf /tmp/iif.10.00.UC3R1TL.Linux.tar

If you purchased IDS version 10, then you will probably get the IDS bundle. In this case copy the contents of directory SERVER of the unpacked bundle to the working directory and proceed.

Set environment:

1
export INFORMIXDIR=/opt/informix

Install the IDS packages:

1
./install_rpm -acceptlicense=yes

Logout from user root:

1
exit

Configuring IDS

Set up the environment

If you are not already logged in as user informix, then switch user id to informix:

1
su - informix

Create an environment file called ids.env using a graphical text editor (such as gedit or kate), for example:

1
gedit ids.env

Or, use the famous console editor vi:

1
vi ids.env

Add the following lines to the ids.env file:

1
2
3
export INFORMIXDIR=/opt/informix<br>
export INFORMIXSERVER=demo_on<br>
export PATH=$INFORMIXDIR/bin:$PATH

Save the file and exit the editor.

Set the environment for IDS:

1
. ./ids.env

(type: dot blank dot slash ids.env)
Each time you need to access this IDS instance you can set the environment from this file again.

Create and edit IDS configuration files:

1
2
3
cd $INFORMIXDIR/etc<br>
cp onconfig.std onconfig<br>
cp sqlhosts.std sqlhosts

Edit file onconfig using the editor of choice (see above), change parameters from - to:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
ROOTPATH        /dev/online_root
-
ROOTPATH        /home/informix/dbspaces/online_root
 
MSGPATH         /usr/informix/online.log
-
MSGPATH         /home/informix/logs/online.log
 
LTAPEDEV        /dev/tapedev
-
LTAPEDEV        /dev/null
 
DBSERVERNAME
-
DBSERVERNAME    demo_on

Find the network node hostname of the machine:

1
uname -n

asterix is printed for example.

Edit file sqlhosts using the editor of choice (see above), change line from - to:

1
2
3
demo_on onipcshm        on_hostname     on_servername
-
demo_on onipcshm        asterix         demo_on

(Replace the word "asterix" with the network node hostname of your machine.)

Create the logs directory:

1
2
cd<br>
mkdir logs

Create the root dbspace:

1
2
3
4
mkdir dbspaces<br>
cd dbspaces<br>
touch online_root<br>
chmod 660 online_root

Startup and shutdown

Start and initialize the configured IDS instance:

1
oninit -iv

prints following message:

1
2
3
This action will initialize IBM Informix Dynamic Server;
any existing IBM Informix Dynamic Server databases will NOT be accessible -
Do you wish to continue (y/n)?

If you are certain that you want to initialize this instance of IDS, type y to initialize the instance. Note, all data will be lost if the instance has been used previously.

Now IDS is running. For testing purposes, you can create the demo database by executing the script dbaccessdemo7 To access databases, the console utility dbaccess can be used.

You can shut down the IDS instance with the command:

1
onmode -ky

and started (without initialization) with this command:

1
oninit

IDS documentation can be read online at "IBM Informix Dynamic Server information center" page. Manuals for all Informix products in different languages can be found at "Informix library" page. See the Related topics section "Learn" for links.

Configuring a raw device

The whole second disk from the example machine can be configured as a raw device. Please note all data will be lost on this disk.

The first step is to create a partition. For this, use the interactive console utility fdisk. Switch to user id root to run following commands:

1
fdisk /dev/hdb

For example:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
The number of cylinders for this disk is set to 29651.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
 
Command (m for help): m
Command action
   a   toggle a bootable flag
   b   edit bsd disklabel
   c   toggle the dos compatibility flag
   d   delete a partition
   l   list known partition types
   m   print this menu
   n   add a new partition
   o   create a new empty DOS partition table
   p   print the partition table
   q   quit without saving changes
   s   create a new empty Sun disklabel
   t   change a partition's system id
   u   change display/entry units
   v   verify the partition table
   w   write table to disk and exit
   x   extra functionality (experts only)
 
Command (m for help): o
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
 
 
The number of cylinders for this disk is set to 29651.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
 
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-29651, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-29651, default 29651):
Using default value 29651
 
Command (m for help): p
 
Disk /dev/hdb: 15.3 GB, 15303075840 bytes
16 heads, 63 sectors/track, 29651 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
 
   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1               1       29651    14944072+  83  Linux
 
Command (m for help): w
The partition table has been altered!
 
Calling ioctl() to re-read partition table.
Syncing disks.

To make sure the OS is informed about the partition table changes, run this command:

1
partprobe

Once the partition /dev/hdb1 is created, its permissions must be changed for use by IDS:

1
2
chown informix:informix /dev/hdb1<br>
chmod 660 /dev/hdb1

Note, the change of permissions may be required again after reboot of the machine. This can be done using an init script.

If you are not already logged in as user informix, then switch user id to informix:

1
su - informix

Set the environment for IDS:

1
. ./ids.env

(Type: dot blank dot slash ids.env)

To remember which chunks are configured, create symbolic links in the dbspaces directory:

1
ln -s /dev/hdb1 /home/informix/dbspaces/chunk1

Now we create the chunk path named '/home/informix/dbspaces/chunk1' of the dbspace named 'dbspace1'. The size of the partition in kilobytes can be found in raw 'Blocks' in output of 'fdisk' command 'p'. It is given as parameter of option '-s' and has the value 14944072 in our example. Switch to userid informix and set ids.env environment to run following commands:

1
2
onspaces -c -d dbspace1 -p /home/informix/dbspaces/chunk1 -o 0 -s
14944072

For testing, create the demo database in dbspace1:

1
dbaccessdemo7 -dbspace dbspace1

Conclusion

In this article we've walked through the installation and configuration of specific versions of Red Hat Enterprise Linux and SUSE Linux Enterprise Server for running IDS 10, to help you get Informix up and running on Linux without difficulty. Adaptation for newer versions of the operating systems should be easy by updating the version numbers of mentioned packages.

https://www.ibm.com/developerworks/data/library/techarticle/dm-0603breitfeld/index.html

728x90
728x90

Informix Version : Informix 12.10.FC5W1

OS : Windows 2012 R2

 

윈도우 2012에 인포믹스 설치 중 아래와 같은 오류가 발생했습니다. 찾아보니 설치프로그램의 호환성 이슈인 것 같습니다. 설치프로그램의 호환 모드를 Windows 7으로 했을 때 잘 설치되었습니다.

 

The Application has Unexpectedly Quit



Invocation of this Java Application has caused an

Invocation TargetException. This application will not exit (LAX)



ZeroGu6: Windows DLL failed to load
    at ZeroGa4.b(DashoA10*..)
    at ZeroGa4.b(DashoA10*..)
    at com.zerog.ia.installer.LifeCycleManager.b(DashoA10*..)
    at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..)
    at com.zerog.ia.installer.Main.main(DashoA10*..)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.zerog.lax.LAX.launch(DashoA10*..)
    at com.zerog.lax.LAX.main(DashoA10*..)

 

http://www-01.ibm.com/support/docview.wss?uid=swg21686842

728x90
728x90

서버: Oracle SPARC T5-2

CPU: 2장 (각 16 코어, 128 가상프로세서, 총 32코어, 256 가상프로세서) 

OS: Oracle Solaris 10 Update 9

RAM: 256GB

DBMS: IBM Informix 12.10.FC2 Workgroup Edition


작년에 Fernando Nunes씨가 포스팅한 글에서의 환경은 HP-UX Itanium이긴 하였으나 결과적으로 원인은 같은 것으로 보인다.


# ./ids_install

Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...


Launching installer...


./ids_install: /tmp/install.dir.13028/Solaris/resource/jre/jre/bin/java: 실행할수 없음



GNU tar를 쓰면 해결된다는 글이 다수 있어 시도해보았다.

솔라리스에 다행히 gtar가 설치되어 있었다.


# mv /usr/sbin/tar /usr/sbin/tar_old

# mv /usr/sfw/bin/gtar /usr/sfw/bin/tar


GNU tar를 사용해서 해결은 되었으나 결국에는 제품 설치 패키지내의 파일이름이 길거나 공백이 있지 않나 싶다. 



설치하면서 인스턴스를 생성하는 옵션을 지정할 때에는 다른 오류가 있었다.

===============================================================================

Server Instance Creation

------------------------


Create a server instance?


  ->1- Yes - create an instance

    2- No - do not create an instance


ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::


인스턴스를 생성하도록 선택한 다음 진행하면 아래와 같이 설치 중 오류가 발생한다.


===============================================================================

Installing...

-------------


 [==================|==================|==================|==================]

 [------------------|------------------|------------------|------------------]

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0xffffffff7e94ddfc, pid=13656, tid=2

#

# JRE version: 6.0_17-b04

# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode solaris-sparc )

# Problematic frame:

# C  [libc.so.1+0x4ddfc]

#

# An error report file with more information is saved as:

# /tmp/install.dir.13656/hs_err_pid13656.log

#

# If you would like to submit a bug report, please visit:

#   http://java.sun.com/webapps/bugreport/crash.jsp

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#


인스턴스 생성하는 옵션에서 No를 선택하면 오류없이 설치된다.

에러 로그 파일을 열어보면 자바 스택이 보이는데 자바 버전, 서버 환경 등의 원인등으로 추측할 수 밖에.



http://informix-technology.blogspot.kr/2013/04/1210-install-issue-on-hp-ux-problema-na.html

http://community.flexerasoftware.com/archive/index.php?t-188987.html

http://www-01.ibm.com/support/docview.wss?uid=swg21296299


728x90
728x90

Problem(Abstract)

This article describes an alternate way to install IBM Informix Dynamic Server.

Cause

Occasionally, IBM Informix Dynamic Server fails to install using the install_server script. Reasons for this vary.

Resolving the problem

If the install_server script is failing you can try the following command to install IBM Informix Dynamic Server:

문서상에는 11.50버전부터 가능한 것으로 되어있습니다.


    java -cp IIF.jar run



http://www-01.ibm.com/support/docview.wss?uid=swg21613223&myns=swgimgmt&mynp=OCSSGU8G&mync=E

728x90

+ Recent posts