=================================
MACHINE SPECIFIC NOTES
FOR
IBM INFORMIX Dynamic Server 11.10.UC3 PRODUCT RELEASE
ON IBM AIX 5L 32bit
DATE: 09 Dec 2008
=================================
OS Information : Built on AIX 5L 5.3 Technology Level 4 SP 2.
Certified on AIX 6.1.
System Requirements
===================
1. This product was built on AIX 5L 5.3 Technology Level 4 SP 2 using the
following compilers:
IBM XL C/C++ Compiler 7.0.0.8
C Set ++ Runtime 8.0.0.0
2. AIX patch requirement:
AIX 5L Technology Level 4 service pack 02 or higher is required at
runtime on your OS.
AIX 5L 5.3:
APAR number IY66195
APAR number IY71363
APAR number IY83580
If the system has the following libc version installed, APAR
number IY89597 is required:
bos.rte.libc 5.3.0.51
If the system is on Technology Level 5, the concluding service
pack (CSP) is required. Technology Level 6 is recommended.
If the system is on the following Technology Level, fix of IZ01229
is required:
Technology Level 6 - APAR number IZ01229
Technology Level 7 - APAR number IZ15400
AIX 6.1:
APAR number IZ13235
3. The IBM Informix Dynamic Server requires that the drivers for
- Portable Streams Environment (PSE)
- Asynchronous IO (AIO)
be loaded on the AIX system where the IBM Informix Dynamic Server is
used. The IBM Informix Dynamic Server executables use entry points
defined by these drivers.
The PSE driver can be loaded using the "/usr/sbin/strload" command. The
AIO device can be enabled using either the AIX "smit" interface or by
doing the following.
To enable AIO after subsequent reboots, issue the following commands
as root:
/usr/sbin/chdev -l aio0 -a autoconfig=available
/usr/sbin/mkdev -l aio0
For further information, refer to the AIX documentation.
4. The UNIX graphical tools provided with this release require X Window
system X11R6 and Motif 2.1 or later runtime libraries.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
6. If you are using Java UDRs, Please refer to "AIX Loader Domains" under
J/Foundation section for details.
7. IDS installer uses AIX file system expansion
If file system expansion is necessary for an installation, a warning will
be included in the preinstall summary dialog of the installation wizard.
At that point, the user can choose to cancel the installation if expansion
is not desired.
If the installation is performed in silent mode, file system expansion
occurs automatically without warning.
Only the install file systems can be expanded. File system expansion of
temporary directories will not occur, and insufficient available space in
temporary directories will cause the installation to fail. The only
exception to this is during launcher execution.
Check the following web site for the latest AIX system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/aix.html
System Configuration
====================
1. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x30000000L
If you are using Java UDRs, refer to the J/Foundation section for setting
the SHMBASE value.
2. Environment Variables
If you are using Java UDRs, set environment variable LDR_CNTRL to
include the value "USERREGS" and "LOADPUBLIC" before starting IBM
Informix Dynamic Server.
export LDR_CNTRL=LOADPUBLIC@USERREGS
Feature Notes (alphabetized by feature)
=============
1. Greater Than 2GB Chunk & File Support
The "crfs" command can be issued with the "-a" option by root to enable
large file support. This is essential to use the greater than 2 GB Chunk
& File Support features.
crfs -a bf=true ... will create a large file enabled file system.
Refer to the manual pages for more information on this Command.
2. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
3. Informix Storage Manager (ISM 2.2)
This product is installed with IDS. The ISM XBSA shared library name is
$INFORMIXDIR/lib/libbsa.o.
4. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 BIT ADDRESSES).
In order for the machine name specified in the SQLHOSTS file to resolve
to the correct IP address, the name services files on the Operating System
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/netsvc.conf should be configured to fetch IPv6
address. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
5. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
6. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM which uses the AIX
native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use JDK 1.4.2 which
can be downloaded from IBM's Java website:
http://www.ibm.com/java/jdk/download/index.html
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
Location of Shared Memory:
-------------------------
When using IBM Informix Dynamic Server with J/Foundation, the ONCONFIG
variable SHMBASE should be set to the following:
SHMBASE 0x40000000L
On AIX, the Java heap allocated by the Java Virtual Machine is created
in the lowest available segment. If SHMBASE is set to 0x30000000L, the
Java heap will be created at an address after the server shared memory
segments. This can cause the server to fail with an assertion error if
additional shared memory segments are dynamically allocated later.
When SHMBASE is set to 0x40000000L or above, the 3rd segment (0x30000000)
is available for the JVM's Java heap, and the server can dynamically add
shared memory segments beyond 0x40000000.
If you must use 0x30000000L as SHMBASE, allocate enough shared memory
segments before starting the J/Foundation server. Refer to the to the
J/Foundation Developer's Guide for information on how to preallocate
virtual shared memory segments.
Using JVM Heapsize >= 128 MB
----------------------------
With JDK 1.4.x, creating the JVM with a heapsize >= 128 MB fails with the
following error:
Unable to alloc heap of requested size, perhaps the maxdata value is
too small - see README.HTML for more information.
**Out of memory, exiting**
The IBM Java team acknowledges that this is a side-effect of the JVM
memory management model chosen for JDK 1.4.x
If you need to use JVM heapsize >= 128 MB, enable the use of the AIX
Large Memory Model feature to avoid the above mentioned problem.
This feature can be enabled by setting the LDR_CNTRL environment variable:
export LDR_CNTRL=MAXDATA=<# of segments reserved for data heap>
For example:
export LDR_CNTRL=MAXDATA=0x20000000
In this example, access is enabled to 2 segments (where each segment is
256 MB). Note that the allocation is done up-front and reserved;
therefore, the value chosen should be based on the needs of your Java
UDRs. If the required JVM heapsize is 128 or 256 MB, 0x20000000 is
sufficient. Also, since this allocation is reserved for the JVM, the
SHMBASE value in the server ONCONFIG file must be set appropriately.
In general, compute the value of SHMBASE as follows:
SHMBASE = <value of LDR_CNTRL=MAXDATA> + 0x30000000
For example, if LDR_CNTRL=MAXDATA=0x20000000, SHMBASE can be set to
0x50000000 or above.
This environment variable should be set before starting the IBM Informix
Dynamic Server instance used for executing Java UDRs. If the server is
already up, bring down and then bring up the server for the environment
variable to take effect.
AIX Loader Domains
------------------
If multiple shared libraries are loaded onto two VPs, one of which is
a Java VP, and the libraries are not loaded in the same order on each
VP, executing a function from the libraries can cause the IBM Informix
Dynamic Server to core dump with the following message in online.log:
09:35:58 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: ill
09:35:58 Who: Session(15, informix@ibms70, 46918, 1075033896)
Thread(41, sqlexec, 4010c7d8, 3)
File: mtex.c Line: 372
09:35:58 Action: Please notify Technical Support.
You would typically encounter this error if your application is using
both C UDRs and Java UDRs.
To resolve this problem, the AIX loader domains concept is used. The
loader domain provides a means of loading shared libraries at the same
virtual address in a set of processes. The loader domain file is created
during the installation of the IBM Informix Dynamic Server. This is
installed as "/var/adm/ifx_loader_domain".
IBM Informix Dynamic Server with J/Foundation on AIX requires the loader
domain file "/var/adm/ifx_loader_domain" to exist at all times. If the
file does not exist, create it as superuser using the following commands:
touch /var/adm/ifx_loader_domain
chgrp informix /var/adm/ifx_loader_domain
chmod 660 /var/adm/ifx_loader_domain
7. Kernel Asynchronous I/O (KAIO)
KAIO is enabled by default on this platform. The AIO driver must be
configured into the AIX system for KAIO to work. Instructions are
provided in the "System Requirements" section above. If AIO is not
configured, the IBM Informix Dynamic Server will report the following
error while starting:
0509-037 System error: error data is: oninit
0509-023 Symbol kaio_rdwr in /usr/lib/libc.a is not defined.
0509-023 Symbol listio in /usr/lib/libc.a is not defined.
0509-023 Symbol acancel in /usr/lib/libc.a is not defined.
0509-023 Symbol iosuspend in /usr/lib/libc.a is not defined.
0509-022 Cannot load library libc.a[aio.o].
0509-026 System error: Cannot run a file that does not have a valid
format
To disable KAIO, set the environment variable KAIOOFF.
KAIOOFF=1 ; export KAIOOFF ( for Bourne or Korn shell )
setenv KAIOOFF 1 ( for C shell )
8. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1).
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
9. No Age (Disable Priority Aging)
The no aging feature that disables priority aging of CPU virtual processors
by the operating system can be activated by setting the noage option of the
VPCLASS configuration parameter for the CPU virtual processors. For example,
the following ONCONFIG entry specifies that there are 8 CPU VPs, each
without aging:
VPCLASS cpu,num=8,noage
When NOAGE is activated, all oninit processes will run at priority 60
with fixed priority round robin type scheduling.
Note: The NOAGE configuration parameter is deprecated; it is replaced by
the VPCLASS configuration parameter with the noage option.
To override the default priority value for CPU VP class, set the
environment variable INFX_CPUVP_PRIORITY to the desired priority,
within limits (50 to 90) before starting the server.
The server checks and sets the CPU VP process to the defined priority
if the defined value is within the above range.
10. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library
supplied by third party storage management vendors. For ON-Bar to
access these functions, the library must be installed in one of the
three ways noted below.
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so.
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
Previously, the shared library file was needed to be in the /usr/lib
directory. Now it needs to be under $INFORMIXDIR/lib.
11. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
12. Optical
The name of the IBM Informix shared library for Optical on AIX is
"iosm11a.so". This library must be located in $INFORMIXDIR/lib
(or must have a link provided in $INFORMIXDIR/lib). Refer to the
"Optical Subsystem Guide" for more information about enabling optical
functionality.
13. Pluggable Authentication Module (PAM)
PAM functionality is supported on AIX operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System
vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
14. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
15. Shared Memory Residency
Shared Memory Residency is supported. This feature can be enabled by
setting ONCONFIG parameter RESIDENT to a non-zero value.
16. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on AIX is libixspw.so.
17. Strong authentication via the authenticate method
The ability to use the AIX authenticate() method is added on the AIX
platform. This allows the database administrator to configure the
authentication mechanism as they see fit. This feature does not support
challenge and response while authenticating.
To configure a particular port the system administrator will need to add
an entry, s=4, to the options field in the sqlhosts file. When this entry
is present in the server sqlhost file the new authentication method will
be used.
Example:
srvname olsoctcp machname prtname s=4
Note: When using the new authentication method, implicit connections
will not be allowed. Since implicit connections rely on the trusted
host mechanism in the server, it is not allowed in conjunction with the
authenticate method.
When using CSS/CSM the new authentication method will be disabled.
Features not Supported
======================
1. Shared Disk Secondary Servers
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM INFORMIX Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON IBM AIX 5L 64bit
DATE: 08 Dec 2008
=================================
OS Information : Built on AIX 5L 5.3 Technology Level 4 SP 2.
Certified on AIX 6.1.
System Requirements
===================
1. This product was built on AIX 5L 5.3 Technology Level 4 SP 2 using the
following compilers:
IBM XL C/C++ Compiler 7.0.0.8
C Set ++ Runtime 8.0.0.0
2. AIX patch requirement:
AIX 5L Technology Level 4 service pack 02 or higher is required at
runtime on your OS.
AIX 5L 5.3:
APAR number IY66195
APAR number IY71363
APAR number IY83580
If the system is on the Technology Level lower than 6:
APAR number IY89007
If the system has the following libc version installed, APAR
number IY89597 is required:
bos.rte.libc 5.3.0.51
If the system is on Technology Level 5, the concluding service
pack (CSP) is required. Technology Level 6 is recommended.
If the system is on the following Technology Level, fix of IZ01229
is required:
Technology Level 6 - APAR number IZ01229
Technology Level 7 - APAR number IZ15400
AIX 6.1:
APAR number IZ13235
3. The IBM Informix Dynamic Server requires that the drivers for
- Portable Streams Environment (PSE)
- Asynchronous IO (AIO)
be loaded on the AIX system where the IBM Informix Dynamic Server is
used. The IBM Informix Dynamic Server executables use entry points
defined by these drivers.
The PSE driver can be loaded using the "/usr/sbin/strload" command. The
AIO device can be enabled using either the AIX "smit" interface or by
doing the following.
To enable AIO after subsequent reboots, issue the following commands
as root:
/usr/sbin/chdev -l aio0 -a autoconfig=available
/usr/sbin/mkdev -l aio0
For further information, refer to the AIX documentation.
4. The UNIX graphical tools provided with this release require X Window
system X11R6 and Motif 2.1 or later runtime libraries.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
6. If you are using Java UDRs, please refer to "AIX Loader Domains" under
J/Foundation section for details.
7. IDS installer uses AIX file system expansion
If file system expansion is necessary for an installation, a warning will
be included in the preinstall summary dialog of the installation wizard.
At that point, the user can choose to cancel the installation if expansion
is not desired.
If the installation is performed in silent mode, file system expansion
occurs automatically without warning.
Only the install file systems can be expanded. File system expansion of
temporary directories will not occur, and insufficient available space in
temporary directories will cause the installation to fail. The only
exception to this is during launcher execution.
Check the following web site for the latest AIX system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/aix.html
System Configuration
====================
1. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x700000000000000L
If you are using Java UDRs, refer to the J/Foundation section for setting
the SHMBASE value.
2. Environment Variables
a. It is recommended that the environment variable INFORMIXSTACKSIZE be set
to 128 (the default is 64) if the application involves operations which
would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
b. If you are using Java UDRs, set environment variable LDR_CNTRL to
include the value "USERREGS" and "LOADPUBLIC" before starting IBM
Informix Dynamic Server.
export LDR_CNTRL=LOADPUBLIC@USERREGS
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a_64.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
To create a 64-bit shared library, the environment variable OBJECT_MODE
should be set to 64 to convey to the compiler that a 64-bit object is to
be generated. The "-q64" flag for cc can also be used to indicate to the
compiler that 64-bit object is to be generated.
2. Informix Storage Manager (ISM 2.2)
This product is installed with IDS. The ISM XBSA shared library name is
$INFORMIXDIR/lib/libbsa.o.
3. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS file to resolve to
the correct IP address, the name services files on the operating system
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/netsvc.conf should be configured to fetch IPv6
address. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
4. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
5. J/Foundation (Java in the Server)
J/Foundation supports the 64bit JRE 1.4.2 release from IBM which uses
the AIX native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use 64bit JDK 1.4.2
which can be downloaded from IBM's Java website:
http://www.ibm.com/java/jdk/download/index.html
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
Location of Shared Memory:
-------------------------
When using IBM Informix Dynamic Server with J/Foundation, the ONCONFIG
variable SHMBASE should be set to the following:
SHMBASE 0x700000010000000
On AIX, the Java heap allocated by the Java Virtual Machine is created
in the lowest available segment. If SHMBASE is set to 0x700000000000000,
the Java heap will be created at an address after the server shared
memory segments. This can cause the server to fail with an assertion
error if additional shared memory segments are dynamically allocated
later.
When SHMBASE is set to 0x700000010000000 or above, the 700000000000000
segment is available for the JVM's Java heap, and the server can
dynamically add shared memory segments beyond 0x700000010000000.
If you must use 0x700000000000000 as SHMBASE, allocate enough shared
memory segments before starting the J/Foundation server. Refer to the
"J/Foundation Developer's Guide for information on how to preallocate
virtual shared memory segments.
AIX Loader Domains
------------------
If multiple shared libraries are loaded onto two VPs, one of which is
a Java VP, and the libraries are not loaded in the same order on each
VP, executing a function from the libraries can cause the IBM Informix
Dynamic Server to core dump with the following message in online.log:
09:35:58 Assert Failed: Exception Caught. Type: MT_EX_OS, Context: ill
09:35:58 Who: Session(15, informix@ibms70, 46918, 1075033896)
Thread(41, sqlexec, 4010c7d8, 3)
File: mtex.c Line: 372
09:35:58 Action: Please notify Technical Support.
You would typically encounter this error if your application is using
both C UDRs and Java UDRs.
To resolve this problem, the AIX loader domains concept is used. The
loader domain provides a means of loading shared libraries at the same
virtual address in a set of processes. The loader domain file is created
during the installation of the IBM Informix Dynamic Server. This is
installed as "/var/adm/ifx_loader_domain".
IBM Informix Dynamic Server with J/Foundation on AIX requires the loader
domain file "/var/adm/ifx_loader_domain" to exist at all times. If the
file does not exist, create it as superuser using the following commands:
touch /var/adm/ifx_loader_domain
chgrp informix /var/adm/ifx_loader_domain
chmod 660 /var/adm/ifx_loader_domain
6. Kernel Asynchronous I/O (KAIO)
KAIO is enabled by default on this platform. The AIO driver must be
configured into the AIX system for KAIO to work. Instructions are
provided in the "System Requirements" section above. If AIO is not
configured, the IBM Informix Dynamic Server will report the following
error while starting:
0509-037 System error: error data is: oninit
0509-023 Symbol kaio_rdwr in /usr/lib/libc.a is not defined.
0509-023 Symbol listio in /usr/lib/libc.a is not defined.
0509-023 Symbol acancel in /usr/lib/libc.a is not defined.
0509-023 Symbol iosuspend in /usr/lib/libc.a is not defined.
0509-022 Cannot load library libc.a[aio.o].
0509-026 System error: Cannot run a file that does not have a valid
format
To disable KAIO, set the environment variable KAIOOFF:
KAIOOFF=1 ; export KAIOOFF ( for Bourne or Korn shell )
setenv KAIOOFF 1 ( for C shell )
7. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers
or shared memory and can write as many pages in a single I/O as
possible.
- The maximum size of any shared memory segment is 68719460352 bytes.
- The value for SHMADD is 67108848 kilobytes.
8. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade module requires Websphere MQ 6.0 package to be installed.
On 64-bit AIX platforms, after installing Websphere MQ, remove the
symbolic links from /usr/lib to the 32-bit WebSphere MQ libraries using
the 'dltmqlnk' command described in Websphere MQ manual "Quick Beginnings
for AIX".
Note: MQ DataBlade module expects Websphere MQ libraries installed in the
default location /usr/mqm. Otherwise create symbolic links from
/usr/mqm/lib64 to the 64-bit Websphere MQ libraries.
9. Network Protocols
The following protocols or interfaces are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1).
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server
using either the TCP/IP sockets or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
10. No Age (Disable Priority Aging)
The no aging feature that disables priority aging of CPU virtual processors
by the operating system can be activated by setting the noage option of the
VPCLASS configuration parameter for the CPU virtual processors. For example,
the following ONCONFIG entry specifies that there are 8 CPU VPs, each
without aging:
VPCLASS cpu,num=8,noage
When NOAGE is activated, all oninit processes will run at priority 60
with fixed priority round robin type scheduling.
Note: The NOAGE configuration parameter is deprecated; it is replaced by
the VPCLASS configuration parameter with the noage option.
To override the default priority value for CPU VP class, set the
environment variable INFX_CPUVP_PRIORITY to the desired priority,
within limits (50 to 90) before starting the server.
The server checks and sets the CPU VP process to the defined priority
if the defined value is within the above range.
11. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library
supplied by third party storage management vendors. For ON-Bar to
access these functions, the library must be installed in one of the
three ways noted below.
a. Rename the library to $INFORMIXDIR/lib/ibsad001_64.so.
b. Create $INFORMIXDIR/lib/ibsad001_64.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
12. OnSNMP
The SNMP agent is based on PEER Network's SubAgent Development Kit.
The distribution includes the following files installed under
$INFORMIXDIR:
bin/onsnmp The OnSNMP subagent itself, packaged as a
separate process.
bin/onsrvapd The daemon which spawns a subagent for each server
it discovers.
snmp/*V1.mib
snmp/*V2.mib
MIB files defining the instrumentation provided
with OnSNMP. Files with 'V1' conform to SNMP
version 1 and share the widest acceptance; files
with 'V2' conform to SNMP version 2.
Refer to the installation notes that accompany the AIX master agent and
network manager for more details.
On this platform OnSNMP is supported on a host that is running one, and
only one server. If multiple servers are running on the same host, the
subagents for subsequent servers may fail to start.
Follow these steps to configure the AIX Master Agent:
a. Modify the file /etc/snmpd.peers to allow the OnSNMP subagent
executable "onsnmp" to register as a peer:
"onsnmp" 0.0 ""
b. Modify the file /etc/snmpd.conf and add
smux 0.0 "" <Local IP address>
13. Optical
The name of the IBM Informix shared library for Optical on AIX is
"iosm11a_64.so". This library must be located in $INFORMIXDIR/lib
(or must have a link provided in $INFORMIXDIR/lib). Refer to the
"Optical Subsystem Guide" for more information about enabling optical
functionality.
14. Pluggable Authentication Module (PAM)
PAM functionality is supported on AIX operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System
vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
15. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
16. Shared Memory Residency
Shared Memory Residency is supported. This feature can be enabled by
setting ONCONFIG parameter RESIDENT to a non-zero value.
17. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
on AIX is libixspw.so.
Features not Supported
======================
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version from previous versions of the server
(64-bit as well as 32-bit), refer to the migration process described in
the IBM Informix Migration Guide, Version 11.10.
To revert from this 64-bit version to all versions other than 32-bit
9.2x, 9.30, 9.40 and 10.00, refer to the IBM Informix Migration Guide,
Version 11.10.
To revert from 64-bit 11.10 (this server) to 32-bit 11.10:
-------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should
be in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32 -d
c. Shutdown the 64-bit server.
d. Start up the 32-bit 11.10 server by setting your INFORMIXDIR
environment variable to point to the 32-bit distribution.
To revert from 64-bit 11.10 (this server) to 32-bit 10.00, 9.40, 9.30
or 9.2x:
---------------------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should be
in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32
c. Revert to 9.2x, 9.30, 9.40, or 10.00 32-bit by following the steps
described in the IBM Informix Migration Guide, Version 11.10, in the
section "Reverting from Dynamic Server 11.10".
2. All UDRs and DataBlade modules that are built in 32-bit mode must be
re-compiled in 64-bit mode to work with the 64-bit server. If you have
any UDRs that were developed on 32-bit, make sure that the proper size
and alignment of the data structures are used for the UDRs to work
correctly on 64-bit after re-compilation in 64-bit mode.
3. All UDRs and DataBlade modules that are built in 64-bit on AIX 4.3.3 or
lower must be recompiled on AIX 5L 5.3. 64-bit binaries built on AIX 4.3.3
or lower are not compatible on AIX 5L 5.3.
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.HC3 PRODUCT RELEASE
ON HEWLETT PACKARD HP-UX 32-Bit
DATE: 09 Dec 2008
=================================
OS Information : Built on HP-UX 11i (aka 11.11), Certified on 11i V2 (aka 11.23)
and 11i v3 (aka 11.31).
System Requirements
===================
1. HP-UX 11i package and patch information for the IBM Informix Dynamic
Server
The product is built on HP-UX 11.11 with the following package and
patches:
Bundle Name Description
----------- -----------
B3901BA B.11.11.14 HP C/ANSI C Developer's Bundle for
HP-UX (S800)
B3913DB C.03.65 HP aC++ Compiler (S800)
B3394BA B.11.11.02 HP-UX Developer's Toolkit for 11.11
BUNDLE B.11.11 Patch Bundle
BUNDLE11i B.11.11.0306.1 Required Patch Bundle for HP-UX 11i,
June 2003
FEATURE11-11 B.11.11.0209.5 Feature Enablement Patches for
HP-UX 11i, Sept 2002
GOLDAPPS11i B.11.11.0506.4 Applications Patches for HP-UX 11i v1,
June 2005
GOLDBASE11i B.11.11.0506.4 Base Patches for HP-UX 11i v1, June 2005
HPUX11i-OE B.11.11.0312 HP-UX 11i Operating Environment Component
HPUXBase64 B.11.11 HP-UX 64-bit Base OS
HPUXBaseAux B.11.11.0312 HP-UX Base OS Auxiliary
HWEnable11i B.11.11.0312.4 Hardware Enablement Patches for HP-UX
11i v1, December 2003
Patch Name Description
---------- -----------
PHKL_30542 s700_800 11.11 eventport (/dev/poll) pseudo driver
PHSS_30970 s700_800 11.11 ld(1) and linker tools cumulative patch
IBM recommends to install the latest Developer's Bundle, Required Patch
Bundle and Patch Bundle on your OS.
2. The UNIX graphical tools provided with this release require X Windows
System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, the environment variable SHLIB_PATH may need to be set
to include these locations.
3. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
4. The Server installation script creates the path
/usr/lib/informix/IDS.11.10.HC3-JRE1.4 as a symbolic link, it points
to
$INFORMIXDIR/extend/krakatoa/jre
If J/Foundation is used, the environment variable SHLIB_PATH may need to
include following paths:
"/usr/lib/informix/IDS.11.10.HC3-JRE1.4/lib"
"/usr/lib/informix/IDS.11.10.HC3-JRE1.4/lib/PA_RISC"
"/usr/lib/informix/IDS.11.10.HC3-JRE1.4/lib/PA_RISC/native_threads"
"/usr/lib/informix/IDS.11.10.HC3-JRE1.4/lib/PA_RISC/server"
Check the following web site for the latest HP-UX system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/parisc.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. On HP-UX,
these entries are in /stand/system.
nfile: 5000
semmni: 3000
semmns: 3000
semmnu: 1400
shmmax: 4294967296
shmmni: 500
shmseg: 500
- The value of the kernel parameter "semmnu" should be set to at least
the maximum number of open ipcshm connections, plus the number of
semaphore undo structures required by other processes in the system.
The recommended value of "semmnu" is between 2K and 4K for larger
systems.
- The value of the kernel parameter "shmmax" should be set to 4GB or the
maximum allowable on the system. Setting "shmmax" to a high value
will prevent the OS from creating multiple shared memory segments
which can degrade performance.
- This server release is built to take advantage of the Large File
Descriptor support provided by HP-UX, which increases the number of
simultaneous user connections per server instance from 2000 to 60000.
To take advantage of this feature, the following kernel parameters
might need to be increased depending on the application.
maxfiles_lim - Maximum number of files that can be opened by a process
simultaneously.
nfile - Maximum number of files that can be opened system-wide.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following
SHMBASE 0x0L
Feature Notes (alphabetized by feature)
=============
1. Direct I/O
IBM Informix Dynamic Server does not use direct I/O by default. To enable
direct I/O, set the onconfig parameter DIRECT_IO to 1.
Currently direct I/O is supported only for Veritas file systems on this
platform.
Currently kernel asynchronous I/O (KAIO) cannot be used with direct I/O
on this platform.
2. Greater than 2GB Chunk & File Support
Refer to the man page for fsadm(1M) and fsadm_hfs(1M) for how to
enable large file support on your system. This is essential to use the
greater than 2 GB Chunk & File Support features for cooked files.
3. Greater than 2GB Shared Memory Support
In order to access greater than 2 GB of shared memory, some of the
server binaries have been linked with the "-N" linker option to change
them to EXEC_MAGIC executable format. This results in the data section
starting immediately after the text section, allowing for a larger data
space (approximately 1.9GB). In addition, the "chatr" command should
be run, as root, on the server and server utilities to make them
SHMEM_MAGIC. The SHMEM_MAGIC executable format enables the binaries to
access greater than 2 GB of shared memory.
For example,
chatr -M <executable>
The maximum limit on the shared memory that can be accessed with this
feature is 2.75 GB.
4. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a.sl. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
5. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
6. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM Corporation, which
uses the HP native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use JDK 1.4.2 which
can be downloaded from HP's Java website:
http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
7. Kernel Asynchronous I/O (KAIO)
KAIO is DISABLED by default on this platform. To enable KAIO, set the
environment variable KAIOON.
KAIOON=1; export KAIOON (for Bourne or Korn Shell)
setenv KAIOON 1 (for C Shell)
The following are prerequisites for using KAIO:
a. The HP KAIO driver "asyncdsk" is installed and linked into the
kernel.
b. Ensure that the KAIO driver is up and running. Check if
/dev/async exists. If it does not, follow these steps:
1) su root
2) If using HP hardware/OS redundancy or mirroring, create the
async device as follows:
/usr/sbin/mknod /dev/async c 101 0
Otherwise, if using IBM Informix mirroring or no hardware/OS
mirroring, or no mirroring at all, create the async device as
follows:
/usr/sbin/mknod /dev/async c 101 4
3) chmod 0666 /dev/async
4) Make sure the following entry exists in the /etc/privgroup file
informix MLOCK
After adding this entry, execute the following command
/sbin/rc1.d/S400set_prvgrp start
An environment variable IFMX_HPKAIO_NUM_REQ is provided to specify the
number of simultaneous KAIO requests that are processed by the server at
one time. The value can be set in the range of 10 to 5000, the default
is 1000. If the following error occurs,
"KAIO: out of OS resources, errno = %d, pid = %d"
consider increasing the value of IFMX_HPKAIO_NUM_REQ.
For example:
IFMX_HPKAIO_NUM_REQ=2300; export IFMX_HPKAIO_NUM_REQ
(for Bourne or Korn Shell)
setenv IFMX_HPKAIO_NUM_REQ 2300 (for C Shell)
8. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1) if the /dev/poll pseudo driver is
available. Please make sure that patch PHKL_30542 eventport (/dev/poll)
pseudo driver is installed on HP-UX 11.11 if FASTPOLL is desired.
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
9. No Age (Disable Priority Aging)
The no aging feature that disables priority aging of CPU virtual processors
by the operating system can be activated by setting the noage option of the
VPCLASS configuration parameter for the CPU virtual processors. For example,
the following ONCONFIG entry specifies that there are 8 CPU VPs, each
without aging:
VPCLASS cpu,num=8,noage
When the noage option is used, all oninit processes will run at priority 180
with SCHED_NOAGE type scheduling. When idle, oninit processes will have the
priority of 154, which is the highest idle priority. This priority level
will prevent oninit processes from being aged when idle.
Note: The NOAGE configuration parameter is deprecated; it is replaced by
the VPCLASS configuration parameter with the noage option.
To override the default priority value for CPU VP class, set the
environment variable IFMX_CPUVP_PRIORITY to the desired priority, within
limits (154 to 190) before starting the engine.
If IFMX_CPUVP_PRIORITY is not within the limits, the priority will be
set to the default value of 180.
10. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways noted
below.
a. Rename the library to $INFORMIXDIR/lib/ibsad001.sl.
b. Create $INFORMIXDIR/lib/ibsad001.sl as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
Workaround for error -43399:
When using ON-Bar to perform backups, the following error may appear
in the onbar activity log file:
"(-43399) ERROR: No response was received from the database server.
Aborting ON-Bar"
To prevent this error, set the SINGLESEG_OFF environment variable
to 1, which changes how IDS allocates shared memory segments, and
then shutdown and re-start the server.
11. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
12. Optical
The name of the IBM Informix shared library for Optical on HP-UX is
iosm11a.sl. This library must be located in $INFORMIXDIR/lib (or must
have a link provided in $INFORMIXDIR/lib). Refer to the "Optical
Subsystem Guide" for more information about enabling optical functionality.
13. Pluggable Authentication Module (PAM)
PAM functionality is supported on HPUX operating system. The PAM is
dependent on the libpam.sl library supplied by the Operating System
vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
14. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
15. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on HP-UX is libixspw.sl.
Features not Supported
======================
1. TERMINFO
2. IPv6 Support
3. Shared Disk Secondary Servers
Known Defects
=============
Please refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in This Release
=============================
Please refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON HEWLETT PACKARD HP-UX 64bit
DATE: 08 Dec 2008
=================================
OS Information : Built on HP-UX 11i (aka 11.11), Certified on 11i V2 (aka 11.23)
and 11i v3 (aka 11.31).
System Requirements
===================
1. HP-UX 11i package and patch information for the IBM Informix Dynamic
Server
The product is built on HP-UX 11.11 with the following package and
patches:
Bundle Name Description
----------- -----------
B3901BA B.11.11.14 HP C/ANSI C Developer's Bundle for
HP-UX (S800)
B3913DB C.03.65 HP aC++ Compiler (S800)
B3394BA B.11.11.02 HP-UX Developer's Toolkit for 11.11
BUNDLE B.11.11 Patch Bundle
BUNDLE11i B.11.11.0306.1 Required Patch Bundle for HP-UX 11i,
June 2003
FEATURE11-11 B.11.11.0209.5 Feature Enablement Patches for
HP-UX 11i, Sept 2002
GOLDAPPS11i B.11.11.0506.4 Applications Patches for HP-UX 11i v1,
June 2005
GOLDBASE11i B.11.11.0506.4 Base Patches for HP-UX 11i v1, June 2005
HPUX11i-OE B.11.11.0312 HP-UX 11i Operating Environment Component
HPUXBase64 B.11.11 HP-UX 64-bit Base OS
HPUXBaseAux B.11.11.0312 HP-UX Base OS Auxiliary
HWEnable11i B.11.11.0312.4 Hardware Enablement Patches for HP-UX
11i v1, December 2003
Patch Name Description
---------- -----------
PHKL_30542 s700_800 11.11 eventport (/dev/poll) pseudo driver
PHSS_30970 s700_800 11.11 ld(1) and linker tools cumulative patch
IBM recommends to install the latest Developer's Bundle, Required Patch
Bundle and Patch Bundle on your OS.
2. The UNIX graphical tools provided with this release require X Windows
System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, the environment variable SHLIB_PATH may need to be set
to include these locations.
3. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
4. The Server installation script creates the path
/usr/lib/informix/IDS.11.10.FC3-JRE1.4 as a symbolic link,
it points to
$INFORMIXDIR/extend/krakatoa/jre
If J/Foundation is used, the environment variable SHLIB_PATH may need to
include following paths:
"/usr/lib/informix/IDS.11.10.FC3-JRE1.4/lib"
"/usr/lib/informix/IDS.11.10.FC3-JRE1.4/lib/PA_RISC2.0W"
"/usr/lib/informix/IDS.11.10.FC3-JRE1.4/lib/PA_RISC2.0W/native_threads"
"/usr/lib/informix/IDS.11.10.FC3-JRE1.4/lib/PA_RISC2.0W/server"
Check the following web site for the latest HP-UX system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/parisc.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. On HP-UX,
these entries are in /stand/system.
nfile: 5000
semmni: 3000
semmns: 3000
semmnu: 1400
shmmax: 4398046511104
shmmni: 500
shmseg: 500
- The value of the kernel parameter "semmnu" should be set to at least
the maximum number of open ipcshm connections, plus the number of
semaphore undo structures required by other processes in the system.
The recommended value of "semmnu" is between 2K and 4K for larger
systems.
- The value of the kernel parameter "shmmax" should be set to the
maximum allowable on the system. Setting "shmmax" to a high value
will prevent the OS from creating multiple shared memory segments
which can degrade performance.
- This server release is built to take advantage of the Large File
Descriptor support provided by HP-UX, which increases the number of
simultaneous user connections per server instance from 2000 to
60000.
To take advantage of this feature, the following kernel parameters
might need to be increased depending on the application:
maxfiles_lim - Maximum number of files that can be opened by a process
simultaneously.
nfile - Maximum number of files that can be opened system-wide.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following
SHMBASE 0x0L
3. Environment Variables
It is recommended that the environment variable INFORMIXSTACKSIZE be
set to 128 (the default is 64) if the application involves operations
which would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
Feature Notes (alphabetized by feature)
=============
1. Direct I/O
IBM Informix Dynamic Server does not use direct I/O by default. To enable
direct I/O, set the onconfig parameter DIRECT_IO to 1.
Currently direct I/O is supported only for Veritas file systems on this
platform.
Currently kernel asynchronous I/O (KAIO) cannot be used with direct I/O
on this platform.
2. Greater than 2GB Chunk & File Support
Refer to the man page for fsadm(1M) and fsadm_hfs(1M) for how to
enable large file support on your system. This is essential to use the
greater than 2 GB Chunk & File Support features for cooked files.
3. High-Availability Data Replication (HDR)
HDR between HP PA-RISC and HP Itanium is supported for 64-bit IBM
Informix Dynamic Server. The server versions must match, and the binaries
should be compiled for each platform (UDR binaries must be compiled for
respective platforms).
Example: HDR between IDS 11.10.FC1 (PA-RISC version) on HP 9000 and IDS
11.10.FC1 (Itanium version) installed on HP Itanium is supported as
long as all other HDR requirements are met.
Please note that this configuration is not supported if the IBM Informix
Dynamic Server on HP-UX PA-RISC uses any Java UDR or DataBlade modules
that are not supported on the IBM Informix Dynamic Server on HP-UX Itanium.
4. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a.sl. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
5. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
6. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM Corporation, which
uses the HP native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use JDK 1.4.2 which
can be downloaded from HP's Java website:
http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
7. Kernel Asynchronous I/O (KAIO)
KAIO is DISABLED by default on this platform. To enable KAIO, set the
environment variable KAIOON.
KAIOON=1; export KAIOON (for Bourne or Korn Shell)
setenv KAIOON 1 (for C Shell)
The following are prerequisites for using KAIO:
a. The HP KAIO driver "asyncdsk" is installed and linked into the
kernel.
b. Ensure that the KAIO driver is up and running. Check if
/dev/async exists. If not, follow these steps:
1) su root
2) If using HP hardware/OS redundancy or mirroring, create the
async device as follows:
/usr/sbin/mknod /dev/async c 101 0
Otherwise, if using IBM Informix mirroring or no hardware/OS
mirroring, or no mirroring at all, create the async device as
follows:
/usr/sbin/mknod /dev/async c 101 4
3) chmod 0666 /dev/async
4) Make sure the following entry exists in the /etc/privgroup file
informix MLOCK
After adding this entry, execute the following command
/sbin/rc1.d/S400set_prvgrp start
An environment variable IFMX_HPKAIO_NUM_REQ is provided to specify the
number of simultaneous KAIO requests that are processed by the server at
one time. The value can be set in the range of 10 to 5000, the default
is 1000. If the following error occurs,
"KAIO: out of OS resources, errno = %d, pid = %d"
consider increasing the value of IFMX_HPKAIO_NUM_REQ.
For example:
IFMX_HPKAIO_NUM_REQ=2300; export IFMX_HPKAIO_NUM_REQ
(for Bourne or Korn Shell)
setenv IFMX_HPKAIO_NUM_REQ 2300 (for C Shell)
8. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers
or shared memory and can write as many pages in a single I/O as
possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Please refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
9. MQ DataBlade Module
The MQ DataBlade module provides meachanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires minimum version 6.0 of Websphere MQ package to be
installed.
Note: MQ DataBlade expects Websphere MQ libraries installed in the
default location /opt/mqm. Otherwise create symbolic links
from /opt/mqm/lib64 to the 64-bit Websphere MQ libraries.
10. Network Protocols
The following protocol or interfaces are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of PROTOCOL in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1) if the /dev/poll pseudo driver is
available. Please make sure that patch PHKL_30542 eventport (/dev/poll)
pseudo driver is installed on HP-UX 11.11 if FASTPOLL is desired.
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server
using either the TCP/IP sockets or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
11. No Age (Disable Priority Aging)
The no aging feature that disables priority aging of CPU virtual processors
by the operating system can be activated by setting the noage option of the
VPCLASS configuration parameter for the CPU virtual processors. For example,
the following ONCONFIG entry specifies that there are 8 CPU VPs, each
without aging:
VPCLASS cpu,num=8,noage
When the noage option is used, all oninit processes will run at priority 180
with SCHED_NOAGE type scheduling. When idle, oninit processes will have the
priority of 154, which is the highest idle priority. This priority level
will prevent oninit processes from being aged when idle.
Note: The NOAGE configuration parameter is deprecated; it is replaced by
the VPCLASS configuration parameter with the noage option.
To override the default priority value for CPU VP class, set the
environment variable IFMX_CPUVP_PRIORITY to the desired priority, within
limits (154 to 190) before starting the engine.
If IFMX_CPUVP_PRIORITY is not within the limits, the priority will be
set to the default value of 180.
12. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways noted
below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.sl.
b. Create $INFORMIXDIR/lib/ibsad001.sl as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
This shared library must be compiled in 64-bit mode.
Workaround for error -43399:
When using ON-Bar to perform backups, the following error may appear
in the onbar activity log file:
"(-43399) ERROR: No response was received from the database server.
Aborting ON-Bar"
To prevent this error, set the SINGLESEG_OFF environment variable
to 1, which changes how IDS allocates shared memory segments, and
then shutdown and re-start the server.
13. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
14. Optical
The name of the IBM Informix shared library for Optical on HP-UX is
iosm11a.sl. This library must be located in $INFORMIXDIR/lib (or must
have a link provided in $INFORMIXDIR/lib). Refer to the "Optical
Subsystem Guide" for more information about enabling optical functionality.
15. Pluggable Authentication Module (PAM)
PAM functionality is supported on HPUX operating system 11.11 for 64 bit.
The PAM is dependent on the libpam.sl library supplied by the Operating
System vendor. This PAM library is not available in HP-UX 11.11 64 bit by
default. The PAM library is required, if any of the servers is configured
to use PAM. Please contact HP customer support to obtain the necessary PAM
patch.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
16. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
17. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
HP-UX is libixspw.sl.
Features not Supported
======================
1. TERMINFO
2. IPv6 Support.
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version from previous versions of the server
(64-bit as well as 32-bit), refer to the migration process described in
the IBM Informix Migration Guide, Version 11.10.
To revert from this 64-bit version to all versions other than 32-bit
9.2x, 9.30, 9.40 and 10.00, refer to the IBM Informix Migration Guide,
Version 11.10.
To revert from 64-bit 11.10 (this server) to 32-bit 11.10:
----------------------------------------------------------
a. Disconnect all users from this server. The 64-bit engine should
be in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32 -d
c. Shutdown the 64-bit server.
d. Bring up the 32-bit 11.10 server by setting your INFORMIXDIR
environment variable to point to the 32-bit distribution.
To revert from 64-bit 11.10 (this server) to 32-bit 10.00, 9.40, 9.30
or 9.2x:
---------------------------------------------------------------------
a. Disconnect all users from this server. The 64-bit engine should be
in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32
c. Revert to 9.2x, 9.30, 9.40, or 10.00 32-bit by following the steps
described in the IBM Informix Migration Guide, Version 11.10, in the
section "Reverting from Dynamic Server 11.10".
2. All UDRs and DataBlade modules that are built in 32-bit mode must be
re-compiled in 64-bit mode to work with the 64-bit server. If you have
any UDRs that were developed on 32-bit, make sure that the proper size
and alignment of the data structures are used for the UDRs to work
correctly on 64-bit after re-compilation in 64-bit mode.
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON HEWLETT PACKARD HP-UX Itanium 2
DATE: 09 Dec 2008
=================================
OS Information : Built on HP-UX 11i V2 (aka 11.23) Itanium.
Certified on 11i v3 (aka 11.31).
System Requirements
===================
1. This product was built on HP-UX 11i V2 (aka 11.23) Itanium using the
following compilers:
HP aC++/ANSI C B3910B A.06.07 [Feb 2 2006]
and with the following packages:
Bundle Name Description
----------- -----------
B3394BA B.11.23.03 HP-UX Developer's Toolkit for 11.23
B3901BA C.11.23.09 HP C/ANSI C Developer's Bundle (S800)
B3913DB C.11.23.09 HP aC++ Compiler (S800)
BUNDLE B.11.23 Patch Bundle
BUNDLE11i B.11.23.0409.3 Required Patch Bundle for HP-UX 11i v2
(B.11.23), September 2004
2. The UNIX graphical tools provided with this release require X Windows
System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, the environment variable LD_LIBRARY_PATH may need to be set
to include these locations.
3. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest HP Itanium system
requirements for IBM Informix Dynamic Server:
http://www-306.ibm.com/software/data/informix/ids/requirements/itanium.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. On HP-UX IA64,
these entries are in /stand/system.
shmseg: 512
shmmni: 512
shmmax: 4398046511104
semmnu: 1400
semmns: 4096
semmni: 4096
nfile: 5000
- The value of the kernel parameter "semmnu" should be set to at least
the maximum number of open ipcshm connections, plus the number of
semaphore undo structures required by other processes in the system.
The recommended value of "semmnu" is between 2K and 4K for larger
systems.
- The value of the kernel parameter "shmmax" should be set to the
maximum allowable on the system. Setting "shmmax" to a high value
will prevent the OS from creating multiple shared memory segments
which can degrade performance.
- This server release is built to take advantage of the Large File
Descriptor support provided by HP-UX, which increases the number of
simultaneous user connections per server instance from 2000 to
60000.
To take advantage of this feature, the following kernel parameters
might need to be increased depending on the application:
maxfiles_lim - Maximum number of files that can be opened by a process
simultaneously.
nfile - Maximum number of files that can be opened system-wide.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following
SHMBASE 0x0L
3. Environment Variables
It is recommended that the environment variable INFORMIXSTACKSIZE be set
to 256 (the default is 96) if the application involves operations which
would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
Feature Notes (alphabetized by feature)
=============
1. Greater Than 2GB Chunk & File Support
Please refer to the man page for fsadm(1M) and fsadm_hfs(1M) for how to
enable large file support on your system. This is essential to use the
greater than 2 GB Chunk & File Support features for cooked files.
2. High-Availability Data Replication (HDR)
HDR between HP PA-RISC and HP Itanium is supported for 64-bit IBM
Informix Dynamic Server. The server versions must match, and the binaries
should be compiled for each platform (UDR binaries must be compiled for
respective platforms).
Example: HDR between IDS 11.10.FC2 (PA-RISC version) on HP 9000 and IDS
11.10.FC2 (Itanium version) installed on HP Itanium is supported as
long as all other HDR requirements are met.
Please note that this configuration is not supported if the IBM Informix
Dynamic Server on HP-UX PA-RISC uses any DataBlade module that are not
supported on the IBM Informix Dynamic Server on HP-UX Itanium.
3. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
This shared library must be compiled in 64-bit mode on HP-UX Itanium.
4. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
5. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM Corporation, which
uses the HP native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use JDK 1.4.2 which
can be downloaded from HP's Java website:
http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
6. Kernel Asynchronous I/O (KAIO)
KAIO is DISABLED by default on this platform. To enable KAIO, set the
environment variable KAIOON.
KAIOON=1; export KAIOON (for Bourne or Korn Shell)
setenv KAIOON 1 (for C Shell)
The following is a prerequisite for using KAIO:
a. The HP KAIO driver "asyncdsk" is installed and linked into the
kernel.
b. Ensure that the KAIO driver is up and running. Check if
/dev/async exists. If not, follow these steps:
1) su root
2) If using HP hardware/OS redundancy or mirroring, create the
async device as follows:
/usr/sbin/mknod /dev/async c 101 0
Otherwise, if using IBM Informix mirroring or no hardware/OS
mirroring, or no mirroring at all, create the async device as
follows:
/usr/sbin/mknod /dev/async c 101 4
3) chmod 0666 /dev/async
4) Make sure the following entry exists in the /etc/privgroup file
informix MLOCK
After adding this entry, execute the following command
/sbin/rc1.d/S400set_prvgrp start
An environment variable IFMX_HPKAIO_NUM_REQ is provided to specify the
number of simultaneous KAIO requests that are processed by the server at
one time. The value can be set in the range of 10 to 5000, the default
being 1000. If the following error occurs:
"KAIO: out of OS resources, errno = %d, pid = %d"
consider increasing the value of IFMX_HPKAIO_NUM_REQ.
For example:
IFMX_HPKAIO_NUM_REQ=2300; export IFMX_HPKAIO_NUM_REQ
(for Bourne or Korn Shell)
setenv IFMX_HPKAIO_NUM_REQ 2300 (for C Shell)
6. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers
or shared memory and can write as many pages in a single I/O as
possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
8. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires minimum version 6.0 of Websphere MQ to be installed.
9. Network Protocols
The following protocol or interfaces are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and IPC stream pipe interfaces.
FASTPOLL in the ONCONFIG file can be set to 0 to disable the fast poll.
By default the fast poll is enabled (value is 1).
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server
using either the TCP/IP sockets or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
10. No Age (Disable Priority Aging)
The no aging feature that disables priority aging of CPU virtual processors
by the operating system can be activated by setting the noage option of the
VPCLASS configuration parameter for the CPU virtual processors. For example,
the following ONCONFIG entry specifies that there are 8 CPU VPs, each
without aging:
VPCLASS cpu,num=8,noage
When the noage option is used, all oninit processes will run at priority 180
with SCHED_NOAGE type scheduling. When idle, oninit processes will have the
priority of 154, which is the highest idle priority. This priority level
will prevent oninit processes from being aged when idle.
Note: The NOAGE configuration parameter is deprecated; it is replaced by
the VPCLASS configuration parameter with the noage option.
To override the default priority value for CPU VP class, set the
environment variable IFMX_CPUVP_PRIORITY to the desired priority, within
limits (154 to 190) before starting the engine.
If IFMX_CPUVP_PRIORITY is not within the limits, the priority will be
set to the default value of 180.
11. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways noted
below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
This shared library must be compiled in 64-bit mode on HP-UX Itanium.
12. Optical
The name of the IBM Informix shared library for Optical on HP-UX is
iosm11a.so. This library must be located in $INFORMIXDIR/lib (or must
have a link provided in $INFORMIXDIR/lib).
This shared library must be compiled in 64-bit mode on HP-UX Itanium.
Refer to the "Optical Subsystem Guide" for more information about enabling
optical functionality.
13. Pluggable Authentication Module (PAM)
PAM functionality is supported on HPUX 11i V2 operating system.
The PAM is dependent on the libpam.so library supplied by the
Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
14. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
15. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
HP-UX is libixspw.so.
Features not Supported
======================
1. TERMINFO
2. OnSNMP
3. IPv6 Support
Migrating to this 64-bit Version
================================
1. In addition to supporting migration from previous IBM IDS version on HP-UX
Itanium, this server for the HP-UX Itanium architecture also supports
migration of IBM Informix databases from HP-UX on PA-RISC systems. Please
refer to the IBM Informix Migration Guide.
2. To migrate IBM Informix databases from HP-UX on a PA-RISC system to this
server, the Informix databases on the PA-RISC system should be running
on the same release level of IBM IDS 64-bit or 32-bit servers.
3. If IBM IDS server on PA-RISC is running on a lower release level than this
IBM IDS server on Itanium, then the IBM IDS server on PA-RISC should be
first upgraded to the same IBM IDS release level as this Itanium server
on PA-RISC, before it can be migrated to HP-UX Itanium.
4. The IBM IDS servers on PA-RISC should be running on a HP-UX O/S on which
the IBM IDS has been certified.
The step-by-step migration process
==================================
The process of migrating an IBM IDS database from a PA-RISC system to an
HP-UX Itanium system is described in the section below. The data can be
migrated from the PA-RISC system to HP-UX Itanium system either by moving
the disks containing the data from the PA-RISC system to the HP-UX Itanium
system, or by copying the data from the disks on the PA-RISC system to the
disks on the HP-UX Itanium system. Moving the disks can be achieved by
physically re-cabling the disks from the PA-RISC system to the HP-UX Itanium
system or, as in the case of a disk array, by re-configuring the LUNs to be
visible to the HP-UX Itanium system. Moving the disks to the HP-UX Itanium
system will be generally quicker and easier than copying, but copying has the
advantage of having a back-up on the PA-RISC system. It is expected that the
choice between copy or move be made depending on the customer environment and
their requirements.
It is assumed that users performing the migration are experienced with HP-UX
system administration and IBM Informix database administration. The steps
described are intended to serve as a guide for them. Please check the man pages
of the HP-UX commands used for more information regarding these commands.
Please work with HP technical support in case assistance is required for using
the HP-UX commands or for setting up the HP-UX systems.
Unless otherwise specified, all the HP-UX commands used should be performed
as the user "root".
Steps required on the PA-RISC System
====================================
1. Make sure that the IBM Informix database is running on (or upgraded to)
IBM IDS with the same release level as the target release IBM IDS on
HP-UX Itanium.
2. Take a level-0 backup of the system following the steps described in the
IBM Informix Migration Guide and shut down the IDS 32bit or 64bit server.
3. Copy the required configuration files (e.g. onconfig) to the HP-UX Itanium
system (please refer the IBM Informix Migration Guide for a complete list
of configuration files).
4. If the "move" option is chosen, do the following:
- Unmount the file systems containing any cooked files.
- Remove or comment out the above file system entries in /etc/fstab.
- Deactivate the volume group by invoking the command:
"vgchange -a n /dev/<volume group>"
- Create a map file by invoking the command:
"vgexport -s -m <map file> /dev/<volume group>"
- Copy the <map file> over to the HP-UX Itanium system.
5. If "copy" option is chosen, do the following:
- Copy all raw devices using "dd" command. The raw devices can be copied
to a tape first and the tape can then be restored on the HP-UX Itanium
system. If both the PA-RISC and HP-UX Itanium systems are on the same
network, "dd" command can be used through a network pipe to the HP-UX
Itanium system, as in the following example:
dd if=/dev/rawdev1 bs=1024 | remsh itanium1 "dd of=/dev/rawdev1 bs=1024"
where "rawdev1" is the raw device and "itanium1" is the hostname of
the HP-UX Itanium system. Please ensure that the raw device ("rawdev1"
in this example) exists on the HP-UX Itanium system and it is
the same size or larger than the raw device on the PA-RISC system.
- The cooked files can be copied using "tar". They can also be copied to
a tape first and the tape can then be restored on the HP-UX Itanium
system.
Steps required on the HP-UX Itanium System
==========================================
1. Make sure that the target release server for HP-UX Itanium is installed
on HP-UX Itanium system.
2. Ensure that the Itanium system has the O/S version HP-UX 11i Version 2
(11.23) and the recommended patches (listed in this document) are
installed.
3. Ensure that the kernel parameters have been tuned as recommended in this
document.
4. If you have used the "move" option, do the following:
- Invoke "ioscan" command to recognize the new disks.
- Invoke "insf -H <hw-path>" to install special device files for the new
disks.
- Create device directory and group by invoking the commands:
mkdir /dev/<volume group>;
mknod /dev/<volume group>/group c 64 0x030000
(where 0x030000 is a unique number which should not already exist in
/dev/vg*)
- Import the volume group by invoking the command:
vgimport -s -m <map file> /dev/<volume group>
where the <map file> was created on the PA-RISC system and copied to
the HP-UX Itanium system.
- Activate the newly imported volume group by invoking the command:
vgchange -a y /dev/<volume group>
- Mount the file systems containing cooked files.
- Add the file system entry in /etc/fstab
5. Make sure that the owner and group for raw devices and cooked files are
"informix".
6. Make sure the permissions are 660 for the raw devices and the cooked
files.
7. Re-create any links to the raw devices or cooked files as they existed
on the PA-RISC system.
8. Edit the onconfig file and sqlhost file to reflect the changes in the
Itanium environment (e.g. some PATH variables and hostname). Please refer
IBM Informix Migration Guide for more information.
9. Start the server on the HP-UX Itanium system by invoking "oninit"
and verify that the server is online. Please refer IBM Informix Migration
Guide for more information on starting the server after migration.
10. All UDRs and DataBlades modules that are built on PA-RISC (in 64-bit as
well as 32-bit mode) must be re-compiled on HP-UX Itanium, in 64-bit mode
to work with the 64-bit server on HP-UX Itanium. If you have any UDRs that
were developed on 32-bit, make sure that the proper size and alignment of
the data structures are used for the UDRs to work correctly on 64-bit after
re-compilation in 64-bit mode.
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Releases
==================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous releases.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.UC3 PRODUCT RELEASE
On Linux Intel
DATE: 08 Dec 2008
=================================
OS Information : Built on Red Hat Enterprise Linux ES release 4 (Nahant Update 3).
Certified on RHEL 5, SUSE SLES 10 and Asianux 2.0,
Ubuntu Server Edition 6.06.1 LTS, and Debian 4.0.
And also certified on Red Hat Enterprise Linux ES release 4,
RHEL 5, SUSE SLES 10 and Asianux 2.0, Debian 4.0 and
Ubuntu Server Edition 6.06.1 LTS for x86_64 (EM64T/AMD64).
System Requirements
===================
1. This product was built on Red Hat Enterprise Linux ES release 4
(Nahant Update 3, Kernel: 2.6.9, Glibc: 2.3.4) for i686 compatible
processors. The i686 version of glibc is required. The following
compilers were used:
gcc and c++ compiler 3.4.5 20051201 (Red Hat 3.4.5-2)
The following packages have to be installed on your Linux system:
libaio-0.3.105
libgcc-3.4.5
libstdc++-3.4.5
ncurses-5.4
pam-0.77
This product has been certified on:
- Red Hat Enterprise Linux ES release 5 (Kernel: 2.6.18, Glibc: 2.5)
for i686 and x86_64 (EM64T/AMD64). The following packages have to be
installed:
libaio-0.3.106
libgcc-4.1.1
libstdc++-4.1.1
ncurses-5.5
pam-0.99.6.2
- SUSE SLES 10 (Kernel: 2.6.16, Glibc: 2.4) for i686 and x86_64
(EM64T/AMD64). The following packages have to be installed:
libaio-0.3.104
libgcc-4.1.0
libstdc++-4.1.0
ncurses-5.5
pam-0.99.3.0
- Asianux 2.0 (Kernel: 2.6.9, Glibc: 2.3.4) for i686 and x86_64
(EM64T/AMD64). The following packages have to be installed:
libaio-0.3.103
libgcc-3.4.3
libstdc++-3.4.3
ncurses-5.4
pam-0.77
- Ubuntu Server Edition 6.06.1 LTS (Kernel: 2.6.15, Glibc: 2.3.6) for
i686 and x86_64 (EM64T/AMD64). The following packages have to be
installed:
bc 1.06
libaio1 0.3.104
libgcc 4.0.3
libncurses 5.5
libpam 0.79
- Debian 4.0 (Kernel: 2.6.18, Glibc: 2.3.6) for i686 and x86_64
(EM64T/AMD64). The following packages have to be installed:
libaio1 0.3.106
libgcc 4.1.1
libncurses 5.5
libpam 0.79
2. System Specific Update level on x86_64 (EM64T/AMD64) for KAIO problem
A problem is found when IDS running on RHEL 4 for x86_64 with update
level below 4. This is tracked as Red Hat bugzilla bug number 86891
(RIT86891- "32bit program using AIO io_queue_init returns -22 in 64bit
system").
When IDS is suffering from this OS defect (i.e. a 32-bit IDS version in
RHEL 4 below UL4 and using KAIO), the server will give an assertion
failure, and the instance will not start, and print the following message
in the server log:
09:49:54 Assert Failed: initializing KAIO failed
09:49:54 Who: Session(1, xyz@abc, 0, (nil))
Thread(14, kaio, 0, 1)
File: kaioapi.c Line: 246
09:49:54 Results: io_queue_init(32768) failed returning -22, errno = 0
09:49:54 Stack for thread: 14 kaio
A circumvention in this case can be to disable KAIO. The fix is to upgrade
RHEL 4 for x86_64 to at least update 4.
3. The UNIX graphical tools ipload, onperf and xtree only require
OpenMotif runtime libraries version 2.2.x. The minimum version is
2.2.3, i.e. openmotif-2.2.3 or openmotif-libs-2.2.3.
4. The ISM scripts need ksh. Install it as /bin/ksh. On Ubuntu Server Edition,
pdksh needs to be installed.
If the product runs on Ubuntu Server Edition x86_64, the following
32-bit packages are required:
libc6-i386
libncurses
The 32-bit libncurses is missing and not packaged, you need to copy
it from a i386 (32bit) installation: /lib/libncurses.so.5 to x86_64
32-bit compat libs: /lib32/libncurses.so.5.
If the product runs on Debian 4.0 x86_64, the following 32-bit packages
are required:
libc6-i386
lib32ncurses5
5. If a suitable library libaio.so.1 is found, IBM Informix Dynamic Server
enables Kernel Asynchronous I/O (KAIO) automatically. Otherwise KAIO is
disabled. The minimum version of libaio is 0.3.103.
6. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest Linux system requirements for IBM
Informix Dynamic Server:
http://www.ibm.com/software/data/informix/linux/ids.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. They can
either be dynamically changed in the /proc file system or are defined
in the kernel sources and can be changed by rebuilding the kernel.
SHMMAX: 33554432
SHMMIN: 1
SHMMNI: 128
SHMSEG: 128
SHMALL: 4194304
SEMMNI: 128
SEMMSL: 250
SEMMNS: 32000
SEMOPM: 32
- The value of the kernel parameter "SEMMSL" should be set to at least
100. This is the maximum number of semaphores per set.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE is set to the following:
SHMBASE 0x44000000L
- SHMBASE can also be set to start above the shared library addresses.
When doing so, ensure that dynamically loaded shared libraries
do not collide with the shared memory segments.
The address space layout can be checked by the following command:
$ cat /proc/<pid of oninit process>/maps
- Some Linux distributions (e.g. SUSE SLES 10) provide a way to dynamically
change the default start address for shared libraries on a per-process
basis. This feature is available if the file /proc/$$/mapped_base
exists.
To change the start address for shared libraries of the oninit processes,
the new start address needs to be specified by the user root in the shell
from where oninit is started. For example, the following sets the start
address of shared libraries to 0xB0000000L:
$ echo $$
29712
$ su root
Password:
# echo 0xB0000000 > /proc/29712/mapped_base
# exit
$ oninit
3. JRE Shared Libraries
In order to ensure the JRE shared libraries are loaded properly, the
following steps are necessary:
a. Add the following lines at the end of /etc/ld.so.conf
<$INFORMIXDIR>/extend/krakatoa/jre/bin
<$INFORMIXDIR>/extend/krakatoa/jre/bin/classic
<$INFORMIXDIR>/extend/krakatoa/jre/lib
This assumes the bundled JRE in $INFORMIXDIR/extend/krakatoa/jre
is used. Substitute <$INFORMIXDIR> by the value of your
INFORMIXDIR environment variable.
c. Run ldconfig as root
# ldconfig
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
library called ipldd11a.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
Depending on the location of the shared libraries, OS stack and etc., a
suitable location of pload shared memory spaces needs to be determined.
Linux system administrator is the best person to find the correct values
for PLOAD_SHMBASE for his particular system. The suggestive values for
PLOAD_SHMBASE could be 0x10000000L, or 0x44000000L.
2. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS file to resolve
to the correct IP address, the name services files on the operating system
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/nsswitch.conf should be configured to fetch IPv6
address. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
3. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
4. J/Foundation (Java in the Server):
J/Foundation supports the JRE 1.4.2 release from IBM Corporation, which uses
the Linux native threads based Java Virtual Machine.
JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and should
be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use the JDK 1.4.2, which
can be downloaded from:
http://www.ibm.com/developerworks/java/jdk/eclipse/
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
5. Kernel Asynchronous I/O (KAIO)
KAIO is enabled by default on this platform. It can be disabled by setting
the environment variable KAIOOFF=1 in the environment of the process that
starting the server.
When using KAIO, it is recommended to run poll threads on separate VPs by
specifying NET as VP class in the NETTYPE onconfig parameter, e.g.
NETTYPE ipcshm,...,...,NET or
NETTYPE soctcp,...,...,NET
On Linux, there is a system wide limit of the maximum number of parallel
KAIO requests. The file /proc/sys/fs/aio-max-nr is containing this value.
It can be increased by the Linux system administrator, e.g. by
# echo new_value > /proc/sys/fs/aio-max-nr
The current number of allocated requests of all OS processes is visible
in /proc/sys/fs/aio-nr.
By default, IBM Informix Dynamic server is allocating half of the maximum
number of requests, and assigns them equally to the number of configured
CPU VPs. The number of requests allocated per CPU VP can be controlled by
the environment variable KAIOON, by setting it to the required value before
bringing up the server. The minimum value for KAIOON is 100. If Linux is
about to run out of KAIO resources, e.g. when dynamically adding many CPU
VPs, warnings will be printed to the online.log file. In this case, the
Linux system administrator should add KAIO resources as described above.
6. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires minimum version 6.0 of Websphere MQ to be installed.
7. Network Protocols
The following protocols and interfaces are supported on this platform:
SOCKETS using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1).
The protocol used for supporting MaxConnect on this platform is "onsocimc".
8. Online Backup and Restore (ON-Bar)
ON-Bar uses the XBSA interface. Some of the functions invoked by ON-Bar
are in a shared library supplied by third party storage management vendors.
For ON-Bar to access the functions, the library must be installed in one of
the three ways noted below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
9. OnSNMP
The SNMP agent is based on PEER Network's SubAgent Development Kit.
The distribution includes the following files installed under
$INFORMIXDIR:
bin/onsnmp The OnSNMP subagent itself, packaged as a
separate process.
bin/onsrvapd The daemon which spawns a subagent for each
server it discovers.
bin/snmpdp PEER Network's master agent.
snmp/peer/CONFIG PEER Network's configuration file.
snmp/*V1.mib
snmp/*V2.mib
MIB files defining the instrumentation provided
with OnSNMP. Files with 'V1' conform to SNMP
version 1 and share the widest acceptance; files
with 'V2' conform to SNMP version 2.
Refer to the installation notes that accompany the master agent for
more details.
- To use the IBM Informix OnSNMP, any "snmpd" process running on
the machine has to be killed, before starting the "snmpdp"
process as user root.
- The runsnmp.ksh script mentioned in the OnSNMP manual is not
available in this platform. This script is not present in the
$INFORMIXDIR.
- OnSNMP is supported on a host that is running one and only one
server. If multiple servers are running on the same host, the
subagents for subsequent servers may fail to start.
10. Optical
The Optical feature has not been tested with the Optical Simulator.
The name of IBM Informix shared library for Optical on Linux is
"iosm11a.so". This library must be located in $INFORMIXDIR/lib (or
must have a link provided in $INFORMIXDIR/lib).
Refer to the "Optical Subsystem Guide" for more information about
enabling optical functionality.
11. Pluggable Authentication Module (PAM)
PAM functionality is supported on Linux operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
12. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
13. Raw Character Devices
Some Linux distributions support binding a raw character device to a
block device. Any block device may be used. IBM Informix Dynamic Server
supports using raw character devices.
14. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on Linux is libixspw.so.
Features not supported
======================
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt (Enterprise and Workgroup
Editions) or doc/idse_defects_11.10.txt (Express Edition) for the information
regarding known issues in this release.
Defects Fixed in the current Release
====================================
Refer to section II in doc/ids_defects_11.10.txt (Enterprise and Workgroup
Editions) or doc/idse_defects_11.10.txt (Express Edition) for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
On Linux x86_64
DATE: 08 Dec 2008
=================================
OS Information : Built on Red Hat Enterprise Linux ES release 4 (Nahant Update 3).
Certified on RHEL 5, SUSE SLES 10 and Asianux 2.0,
Ubuntu Server Edition 6.06.1 LTS, and Debian 4.0.
System Requirements
===================
1. This product was built on Red Hat Enterprise Linux ES release 4 (Nahant
Update 3, Kernel: 2.6.9, Glibc: 2.3.4) for x86_64 compatible processors.
The following compilers were used:
gcc and c++ compiler 3.4.5 20051201 (Red Hat 3.4.5-2)
The following package have to be installed on your Linux system:
libaio-0.3.105
libgcc-3.4.5
libstdc++-3.4.5
ncurses-5.4
pam-0.77
This product has been certified on:
- Red Hat Enterprise Linux ES release 5 (Kernel: 2.6.18, Glibc: 2.5).
The following packages have to be installed:
libaio-0.3.106
libgcc-4.1.1
libstdc++-4.1.1
ncurses-5.5
pam-0.99.6.2
- SUSE SLES 10 (Kernel: 2.6.16, Glibc: 2.4). The following packages
have to be installed:
libaio-0.3.104
libgcc-4.1.0
libstdc++-4.1.0
ncurses-5.5
pam-0.99.3.0
- Asianux 2.0 (Kernel: 2.6.9, Glibc: 2.3.4). The following packages
have to be installed:
libaio-0.3.103
libgcc-3.4.3
libstdc++-3.4.3
ncurses-5.4
pam-0.77
- Ubuntu Server Edition 6.06.1 LTS (Kernel: 2.6.15, Glibc: 2.3.6).
The following packages have to be installed:
bc 1.06
libaio1 0.3.104
libgcc 4.0.3
libncurses 5.5
libpam 0.79
- Debian 4.0 (Kernel: 2.6.18, Glibc: 2.3.6). The following packages
have to be installed:
libaio1 0.3.106
libgcc 4.1.1
libncurses 5.5
libpam 0.79
2. The UNIX graphical tools ipload, onperf and xtree only require
OpenMotif runtime libraries version 2.2.x. The minimum version is
2.2.3, i.e. openmotif-2.2.3 or openmotif-libs-2.2.3.
3. The ISM scripts need ksh. Install it as /bin/ksh. On Ubuntu Server Edition,
pdksh needs to be installed.
If the product runs on Ubuntu Server Edition x86_64, the following
32-bit packages are required:
libc6-i386
libncurses
The 32-bit libncurses is missing and not packaged, you need to copy
it from a i386 (32bit) installation: /lib/libncurses.so.5 to x86_64
32-bit compat libs: /lib32/libncurses.so.5.
If the product runs on Debian 4.0 x86_64, the following 32-bit packages
are required:
libc6-i386
lib32ncurses5
4. If a suitable library libaio.so.1 is found, IBM Informix Dynamic Server
enables Kernel Asynchronous I/O (KAIO) automatically. Otherwise KAIO is
disabled. The minimum version of libaio is 0.3.103.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest Linux system requirements for IBM
Informix Dynamic Server:
http://www.ibm.com/software/data/informix/linux/ids.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. They
can either be dynamically changed in the /proc file system or are defined
in the kernel sources and can be changed by rebuilding the kernel.
SHMMAX: 4398046511104
SHMMIN: 1
SHMMNI: 4096
SHMSEG: 128
SHMALL: 4194304
SEMMNI: 4096
SEMMSL: 250
SEMMNS: 32000
SEMOPM: 32
- The value of the kernel parameter "SEMMSL" should be set to at least
100. This is the maximum number of semaphores per set.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE is set to the following:
SHMBASE 0x44000000L
3. Environment Variables
It is recommended that the environment variable INFORMIXSTACKSIZE be
set to 128 (the default is 64) if the application involves operations
which would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
4. JRE Shared Libraries
In order to ensure the JRE shared libraries are loaded properly, the
following steps are necessary:
a. Add the following lines at the end of /etc/ld.so.conf
<$INFORMIXDIR>/extend/krakatoa/jre/bin
This assumes the bundled JRE in $INFORMIXDIR/extend/krakatoa/jre
is used. Substitute <$INFORMIXDIR> by the value of your
INFORMIXDIR environment variable.
b. Run ldconfig as root
# ldconfig
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
64-bit library called ipldd11a.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
Depending on the location of the shared libraries, OS stack and etc., a
suitable location of pload shared memory spaces needs to be determined.
Linux system administrator is the best person to find the correct values
for PLOAD_SHMBASE for his particular system. The suggestive values for
PLOAD_SHMBASE could be 0x10000000L, or 0x44000000L.
2. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
3. Kernel Asynchronous I/O (KAIO)
KAIO is enabled by default on this platform. It can be disabled by setting
the environment variable KAIOOFF=1 in the environment of the process that
starting the server.
When using KAIO, it is recommended to run poll threads on separate VPs by
specifying NET as VP class in the NETTYPE onconfig parameter, e.g.
NETTYPE ipcshm,...,...,NET or
NETTYPE soctcp,...,...,NET
On Linux, there is a system wide limit of the maximum number of parallel
KAIO requests. The file /proc/sys/fs/aio-max-nr is containing this value.
It can be increased by the Linux system administrator, e.g. by
# echo new_value > /proc/sys/fs/aio-max-nr
The current number of allocated requests of all OS processes is visible
in /proc/sys/fs/aio-nr.
By default, IBM Informix Dynamic server is allocating half of the maximum
number of requests, and assigns them equally to the number of configured
CPU VPs. The number of requests allocated per CPU VP can be controlled by
the environment variable KAIOON, by setting it to the required value before
starting the server. The minimum value for KAIOON is 100. If Linux is
about to run out of KAIO resources, e.g. when dynamically adding many CPU
VPs, warnings will be printed to the online.log file. In this case, the
Linux system administrator should add KAIO resources as described above.
4. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers
or shared memory and can write as many pages in a single I/O as
possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
5. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires minimum version 6.0 of Websphere MQ to be installed.
Note : For supported version of operating system's please refer
"WebSphere MQ for Linux V6.0 Quick Beginnings" manual.
6. Network Protocols
The following protocols or interfaces are supported on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces.
FASTPOLL in the ONCONFIG file can be set to 0 to disable the fast poll.
By default the fast poll is enabled (value is 1).
Remote 32-bit or 64-bit applications and tools (example: ESQL/C, 4GL, ISQL)
can only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server
using either the TCP/IP sockets or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is "onsocimc".
7. Online Backup and Restore (ON-Bar)
ON-Bar uses the XBSA interface. Some of the functions invoked by ON-Bar
are in a shared library supplied by third party storage management vendors.
For ON-Bar to access the functions, the library must be installed in one
of the three ways noted below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
This shared library must be compiled in 64-bit mode.
8. OnSNMP
The SNMP agent is based on PEER Network's SubAgent Development Kit.
The distribution includes the following files installed under
$INFORMIXDIR:
bin/onsnmp The OnSNMP subagent itself, packaged as a
separate process.
bin/onsrvapd The daemon which spawns a subagent for each
server it discovers.
bin/snmpdp PEER Network's master agent.
snmp/peer/CONFIG PEER Network's configuration file.
snmp/*V1.mib
snmp/*V2.mib
MIB files defining the instrumentation provided
with OnSNMP. Files with 'V1' conform to SNMP
version 1 and share the widest acceptance; files
with 'V2' conform to SNMP version 2.
Refer to the installation notes that accompany the master agent for
more details.
- To use the IBM Informix OnSNMP, any "snmpd" process running on
the machine has to be killed, before starting the "snmpdp"
process as user root.
- The runsnmp.ksh script mentioned in the OnSNMP manual is not
available in this platform. This script is not present in the
$INFORMIXDIR.
- OnSNMP is supported on a host that is running one and only one
server. If multiple servers are running on the same host, the
subagents for subsequent servers may fail to start.
9. Optical
The Optical feature has not been tested with the Optical Simulator.
The name of IBM Informix shared library for Optical on Linux is
iosm11a.so". This library must be located in $INFORMIXDIR/lib (or
must have a link provided in $INFORMIXDIR/lib). Refer to the
"Optical Subsystem Guide" for more information about enabling optical
functionality.
10. Pluggable Authentication Module (PAM)
PAM functionality is supported on Linux operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System
vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
11. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
12. Raw Character Devices
Some Linux distributions support binding a raw character device to a
block device. Any block device may be used. IBM Informix Dynamic Server
supports using raw character devices.
13. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
Linux is libixspw.so.
14. J/Foundation (Java in the Server):
J/Foundation supports the JRE 1.4.2 release from IBM Corporation, which uses
the Linux native threads based Java Virtual Machine.
JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and should
be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use the JDK 1.4.2, which
can be downloaded from:
http://www.ibm.com/developerworks/java/jdk/linux/download.html
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
Features not supported
======================
1. IPv6 Support
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version server from 10.00 versions of the
server (for Linux x86-64 as well as Linux x86 32bit), refer to the
migration process described in the IBM Informix Migration Guide, Version
11.10.
To revert from this 64-bit version to 10.00 64-bit versions refer to
the IBM Informix Migration Guide, Version 11.10.
To revert from 64-bit 11.10 (this server) to 32-bit 11.10:
----------------------------------------------------------
a. Disconnect all users from this server. The 64-bit engine should
be in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32 -d
c. Shutdown the 64-bit server.
d. Bring up the 32-bit 11.10 server by setting your INFORMIXDIR
environment variable to point to the 32-bit distribution.
To revert from 64-bit 11.10 (this server) to 32-bit 10.00:
----------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should be
in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32
c. Revert to 10.00 32-bit by following the steps described in the IBM
Informix Migration Guide, Version 11.10, in the section "Reverting
from Dynamic Server 11.10".
2. All UDRs and DataBlades modules that are built in 32-bit mode must be
re-compiled in 64-bit mode to work with the 64-bit server. If you have
any UDRs that were developed on 32-bit, make sure that the proper size
and alignment of the data structures are used for the UDRs to work
correctly on 64-bit after re-compilation in 64-bit mode.
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in the current Release
====================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
On Linux Power Series
DATE: 09 Dec 2008
=================================
OS Information : Built on Red Hat Enterprise Linux ES release 4 (Nahant Update 6).
Certified on RHEL 5, SUSE SLES 10 and Asianux 2.0.
System Requirements
===================
1. This product was built on Red Hat Enterprise Linux ES release 4
(Nahant Update 6) for 64-Bit Power Series Architecture with Kernel
version 2.6.9-55.EL and glibc 2.3.4-2.39, using the following
compilers:
gcc/g++ 3.4.6 20060404 (Red Hat 3.4.6-9)
The following packages have to be installed on your Linux system:
elfutils-libelf-0.97.1
libaio-0.3.105
libgcc-3.4.6
libstdc++-3.4.6
ncurses-5.4
pam-0.77
This product has been certified on:
- Red Hat Enterprise Linux ES release 5 (Kernel: 2.6.18, Glibc: 2.5).
The following packages have to be installed:
elfutils-libelf-0.125
libaio-0.3.106
libgcc-4.1.1
libstdc++-4.1.1
ncurses-5.5
pam-0.99.6.2
- SUSE SLES 10 (Kernel: 2.6.16, Glibc: 2.4). The following packages
have to be installed:
libaio-0.3.104
libelf-0.8.5
libgcc-4.1.0
libstdc++-4.1.0
ncurses-5.5
pam-0.99.3.0
- Asianux 2.0 (Kernel: 2.6.9, Glibc: 2.3.4). The following packages
have to be installed:
elfutils-libelf-0.97.1
libaio-0.3.103
libgcc-3.4.3
libstdc++-3.4.3
ncurses-5.4
pam-0.77
2. The UNIX graphical tools ipload, onperf and xtree only require
OpenMotif runtime libraries version 2.2.x. The minimum version is
2.2.3, i.e. openmotif-2.2.3 or openmotif-libs-2.2.3.
3. The ISM scripts need ksh. Install it as /bin/ksh.
4. If a suitable library libaio.so.1 is found, IBM Informix Dynamic Server
enables Kernel Asynchronous I/O (KAIO) automatically. Otherwise KAIO is
disabled. The minimum version of libaio is 0.3.103.
5. The High Performance Loader utilities, onpload and onpladm, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
5. libelf.so should be a valid link on the system. Generally,
/usr/lib64/libelf.so is linked to /usr/lib64/libelf.so.1.
Check the following web site for the latest Linux system requirements
for IBM Informix Dynamic Server:
http://www-306.ibm.com/software/data/informix/linux/ids.html
System Configuration
====================
1. Kernel Parameters
The values of the kernel parameters that were used for testing this
product are given below. These values might need to be tuned depending
on the application and availability of system resources. They
can either be dynamically changed in the /proc file system or are defined
in the kernel sources and can be changed by rebuilding the kernel.
SHMMAX: 4398046511104
SHMMIN: 1
SHMMNI: 4096
SHMSEG: 4096
SHMALL: 4194304
SEMMNI: 128
SEMMSL: 250
SEMMNS: 32000
SEMOPM: 32
- The value of the kernel parameter "SEMMSL" should be set to at least
100. This is the maximum number of semaphores per set.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x100000000
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines must be provided in a dynamic, shared
64-bit library called ipldd11a.so. This library is installed in the
$INFORMIXDIR/lib directory. You can set the location of this file with
the HPL_DYNAMIC_LIB_PATH configuration parameter in file pointed to by
PLCONFIG environment variable. For more details, refer the manual
"High-Performance Loader User's Guide".
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
2. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with
the embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
3. Kernel Asynchronous I/O (KAIO)
KAIO is enabled by default on this platform. It can be disabled by setting
the environment variable KAIOOFF=1 in the environment of the process that
starting the server.
When using KAIO, it is recommended to run poll threads on separate VPs by
specifying NET as VP class in the NETTYPE onconfig parameter, e.g.
NETTYPE ipcshm,...,...,NET or
NETTYPE soctcp,...,...,NET
On Linux, there is a system wide limit of the maximum number of parallel
KAIO requests. The file /proc/sys/fs/aio-max-nr is containing this value.
It can be increased by the Linux system administrator, e.g. by
# echo new_value > /proc/sys/fs/aio-max-nr
The current number of allocated requests of all OS processes is visible
in /proc/sys/fs/aio-nr.
By default, IBM Informix Dynamic server is allocating half of the maximum
number of requests, and assigns them equally to the number of configured
CPU VPs. The number of requests allocated per CPU VP can be controlled by
the environment variable KAIOON, by setting it to the required value before
starting the server. The minimum value for KAIOON is 100. If Linux is about
to run out of KAIO resources, e.g. when dynamically adding many CPU VPs,
warnings will be printed to the online.log file. In this case, the Linux
system administrator should add KAIO resources as described above.
4. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers or
shared memory and can write as many pages in a single I/O as possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
5. MQ DataBlade
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires Websphere MQ 6.0 package to be installed.
Note : MQ DataBlade expects Websphere MQ libraries installed in the
default location /opt/mqm. Otherwise create symbolic links
from /opt/mqm/lib64 to the 64-bit Websphere MQ libraries.
6. Network Protocols
The following protocol(s)/interface(s) are supported besides shared memory
on this platform:
Berkeley sockets using TCP/IP
IPC using stream pipe (implemented using Unix Domain Sockets)
To use sockets with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the sqlhosts file.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with TCP/IP and stream pipe interfaces. FASTPOLL
in the ONCONFIG file can be set to 0 to disable the fast poll. By default
the fast poll is enabled (value is 1).
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server using
either the TCP/IP sockets or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
7. Online Backup and Restore (ON-Bar)
ON-Bar uses the XBSA interface. Some of the functions invoked by ON-Bar
are in a shared library supplied by third party storage management
vendors. For ON-Bar to access the functions, the library must be installed
in one of the three ways noted below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
8. OnSNMP
The SNMP agent is based on PEER Network's SubAgent Development Kit.
The distribution includes the following files installed under
$INFORMIXDIR:
bin/onsnmp The OnSNMP subagent itself, packaged as a
separate process.
bin/onsrvapd The daemon which spawns a subagent for each
server it discovers.
bin/snmpdp PEER Network's master agent.
snmp/peer/CONFIG PEER Network's configuration file.
snmp/*V1.mib
snmp/*V2.mib
MIB files defining the instrumentation provided
with OnSNMP. Files with 'V1' conform to SNMP
version 1 and share the widest acceptance; files
with 'V2' conform to SNMP version 2.
Refer to the installation notes that accompany the master agent for
more details.
- To use the IBM Informix OnSNMP, any "snmpd" process running on
the machine has to be killed, before starting the "snmpdp"
process as user root.
- The runsnmp.ksh script mentioned in the OnSNMP manual is not
available in this platform. This script is not present in the
$INFORMIXDIR.
- OnSNMP is supported on a host that is running one and only one
server. If multiple servers are running on the same host, the
subagents for subsequent servers may fail to start.
9. Optical
The Optical feature has not been tested with the Optical Simulator.
The name of IBM Informix shared library for Optical is "iosm11a.so".
This library must be located in $INFORMIXDIR/lib (or must have a link
provided in $INFORMIXDIR/lib). Refer to the "Optical Subsystem Guide"
for more information about enabling optical functionality.
10. Pluggable Authentication Module (PAM)
PAM functionality is supported on Linux operating system.
The PAM is dependent on the libpam.so library supplied by the
Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
11. Processor Affinity
The processor affinity feature, that allows the pinning of a CPU VP
processor to a physical processor in a multi-cpu configuration, is
supported on this platform.
12. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on Linux is libixspw.so.
Features not supported
======================
1. J/Foundation
2. IPv6 Support.
3. Basic Text Search DataBlade Module
4. Web Feature Service DataBlade Module
5. XML Publishing
6. Shared Disk Secondary Servers
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in the current Release
====================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.UC3 PRODUCT RELEASE
ON SUN SOLARIS
DATE: 09 Dec 2008
=================================
OS Information : Built on Solaris 9, Certified on Solaris 10
System Requirements
===================
1. This product was built on Solaris 9 using the following compilers
from Sun Studio 11:
Sun C 5.8 Patch 121015-02 2006/03/29
Sun C++ 5.8 Patch 121017-02 2006/04/19
2. Solaris patch information for the IBM Informix Dynamic Server
a. Install the recommended patch cluster for your OS version.
The cluster is available at http://sunsolve.Sun.COM/.
For example, if you are running Solaris 9, download and install
9_Recommended.zip
b. The product is built and tested with the following patches.
120760-06 Sun Studio 11: Compiler Common patch for Sun C C++ F77 F95
121017-02 Sun Studio 11: Patch for Sun C++ 5.8 compiler
121015-02 Sun Studio 11: Patch for Sun C 5.8 compiler
111711-15 SunOS 5.9 32-bit shared library patch for C++
112963-25 Linker Patch (32-bit)
111722-04 SunOS 5.9 Math Library libm patch
112785-52 X11 Xsun
On Solaris 10:
119963-07 Shared library patch for C++
c. System specific patch for VP notify problem
Some Solaris OS and system patch combinations can be one of the
many possible causes of the VP countdown problem, where the
instance appears to hang and the following message appears in
the online log:
12:00:13 VP Notify mechanism incomplete after 5 minutes.
This can be due to slow network file access. Will
try 12 more times.
This issue can occur in the following releases:
Solaris 9 with patch 116527-01 and without patch 116527-02
Solaris 10 without patch 118833-18
Resolution:
Solaris 9 with patch 116527-02 or later
For Solaris 10, patch 118833-24 or later is recommended
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102281-1
d. Sun Solaris 10 patch alert
Installation of certain Sun Solaris patches can cause a listener thread
within the Informix Dynamic Server to fail with an operating system
error of 13, preventing new network connections to the database server.
Sun Microsystems, Inc. has issued a Sun Alert Notification (Sun Alert
ID 102576) for this problem:
On Solaris 10 libnsl(3LIB) or TLI/XTI API routines May Cause Listener
Programs for Databases or Other Network Aware Applications to Stop
Responding.
This issue can occur in the following releases:
Solaris 10 with patch 118833-04 through 118833-23 and without
patch 118833-24
Resolution:
Solaris 10 with patch 118833-24 or later
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102576-1
3. IBM Informix Dynamic Server is supported to work with and without Zones
on Solaris 10. Read the following document for more information:
ftp://ftp.software.ibm.com/software/data/informix/ids/IDS-SunSPARC-reqs.pdf
4. The UNIX graphical tools provided with this release require X Windows
System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, set the environment variable LD_LIBRARY_PATH to include
these locations: /usr/openwin/lib and /usr/dt/lib.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest Solaris system requirements for
IBM Informix Dynamic Server:
http://www-306.ibm.com/software/data/informix/ids/requirements/sparc.html
System Configuration
====================
1. Kernel Parameters
a) The values of the kernel parameters that were used for testing this
product on the OS Solaris 9 systems are given below. These values might
need to be tuned depending on the application and availability of system
resources. These entries are in /etc/system.
set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=100
set shmsys:shminfo_shmmax=268435456
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=100
The value of the kernel parameter "semmsl" should be set to at least
100. This is the maximum number of semaphores per set.
b) On Solaris 10, all System V IPC facilities are either automatically
configured or can be controlled by resource controls.
The following kernel parameters are either removed or commented out
from /etc/system:
semsys:seminfo_semmap
semsys:seminfo_semmns
semsys:seminfo_semmnu
semsys:seminfo_semume
shmsys:shminfo_shmmin
shmsys:shminfo_shmseg
The following obsolete IPC tunables are replaced by their resource
controls with the new default values:
semsys:seminfo_semmni
semsys:seminfo_semmsl
shmsys:shminfo_shmmax
shmsys:shminfo_shmmni
Refer to the rctladm(1m) man page for more information about
available resource controls.
c) IDS Failure with a Large Intimate Shared Memory Page Size
On certain hardware configurations, Solaris 10 can use very large
memory pages for Solaris Intimate Shared Memory (ISM): 32 MB or
256 MB instead of the previous limit of 4 MB. IDS uses Solaris ISM
for shared memory segments that are forced to be memory-resident by
the RESIDENT configuration parameter, however IDS might experience
problems if 32 MB or 256 MB pages are used by Solaris (APAR
36804462).
If you receive a message that contiguous shared memory segment
allocation failed and the value of the SHMBASE configuration
parameter is the same as its value in onconfig.std, then IDS might
fail unexpectedly. To prevent this problem, set the Solaris 10
operating system mmu_ism_pagesize configuration parameter to limit
the memory pages to 4 MB for ISM. To set this parameter, edit the
/etc/system file and add the following line:
set mmu_ism_pagesize = 4194304
Then restart the Solaris computer.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x0A000000L
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines for the High Performance Loader must be
provided in a dynamic, shared library called ipldd11a.so. This shared
library is installed in the $INFORMIXDIR/lib directory. You can set the
location of this file with the HPL_DYNAMIC_LIB_PATH configuration
parameter in file pointed to by PLCONFIG environment variable. For more
details, see the "High-Performance Loader User's Guide".
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
2. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS file to resolve to
the correct IP address, the name services files on the operating system
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/nsswitch.conf should be configured to fetch IPv6
addresss. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address, then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
3. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with the
embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
4. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from Sun Microsystems, which
uses the Solaris native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use the JDK 1.4.2, which
can be downloaded from:
http://java.sun.com/javase/index.jsp
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
5. Network Protocols
The following protocols and interfaces are supported on this platform:
TLI using TCP/IP
SOCKETS using TCP/IP
IPC using stream pipe
To use TLI with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "ontlitcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drtlitcp"
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while supporting
SQLI connections you could add a DBSERVERALIASES entry to ONCONFIG which
corresponds to the sqlhosts file.
When using either TLI or SOCKETS, set the "connections" field in
the ONCONFIG NETTYPE parameter and the kernel driver ndd parameter
"tcp_conn_req_max_q" to the maximum number of expected concurrent
connections.
If the "tcp_conn_req_max_q" is set too low, you will see a client
error with sqlcode = -908 and isamcode = 13. If the NETTYPE
"connections" field is set too low, you will see a server
listener-thread error with err = -25571.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with all TCP/IP and stream pipe interfaces.
FASTPOLL in the ONCONFIG file can be set to 0 to disable the fast poll.
By default the fast poll is enabled (value is 1).
The protocol used for supporting MaxConnect on this platform is
"ontliimc".
6. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways noted
below:
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so.
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
7. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
8. Optical
The name of the IBM Informix shared library for Optical on Solaris is
iosm11a.so. This library must be located in $INFORMIXDIR/lib (or must
have a link provided in $INFORMIXDIR/lib).
Refer to the "Optical Subsystem Guide" for more information about
enabling optical functionality.
9. Pluggable Authentication Module (PAM).
PAM functionality is supported on Solaris operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
10. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
Solaris is libixspw.so.
Features not supported
======================
1. Shared Disk Secondary Servers
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON SUN SOLARIS 64bit
DATE: 09 Dec 2008
=================================
OS Information : Built on Solaris 9, Certified on Solaris 10
System Requirements
===================
1. This product was built on Solaris 9 using the following compilers
from Sun Studio 11:
Sun C 5.8 Patch 121015-02 2006/03/29
Sun C++ 5.8 Patch 121017-02 2006/04/19
2. Solaris patch information for the IBM Informix Dynamic Server
a. Install the recommended patch cluster for your OS version.
The cluster is available at http://sunsolve.Sun.COM/.
For example, if you are running Solaris 9, download and install
9_Recommended.zip
b. The product is built and tested with the following patches.
120760-06 Sun Studio 11: Compiler Common patch for Sun C C++ F77 F95
121017-02 Sun Studio 11: Patch for Sun C++ 5.8 compiler
121015-02 Sun Studio 11: Patch for Sun C 5.8 compiler
111712-15 SunOS 5.9 64-bit shared library patch for C++
112963-25 Linker Patch (32-bit)
111722-04 SunOS 5.9 Math Library libm patch
112785-52 X11 Xsun
On Solaris 10:
119963-07 Shared library patch for C++
c. System specific patch for VP notify problem
Some Solaris OS and system patch combinations can be one of the
many possible causes of the VP countdown problem, where the
instance appears to hang and the following messages appearing in
the online log:
12:00:13 VP Notify mechanism incomplete after 5 minutes.
This can be due to slow network file access. Will
try 12 more times.
This issue can occur in the following releases:
Solaris 9 with patch 116527-01 and without patch 116527-02
Solaris 10 without patch 118833-18
Resolution:
Solaris 9 with patch 116527-02 or later
For Solaris 10, patch 118833-24 or later is recommended
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102281-1
d. Sun Solaris 10 patch alert
Installation of certain Sun Solaris patches can cause a listener thread
within the Informix Dynamic Server to fail with an operating system
error of 13, preventing new network connections to the database server.
Sun Microsystems, Inc. has issued a Sun Alert Notification (Sun Alert
ID 102576) for this problem:
On Solaris 10 libnsl(3LIB) or TLI/XTI API routines May Cause Listener
Programs for Databases or Other Network Aware Applications to Stop
Responding.
This issue can occur in the following releases:
Solaris 10 with patch 118833-04 through 118833-23 and without
patch 118833-24
Resolution:
Solaris 10 with patch 118833-24 or later
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102576-1
3. IBM Informix Dynamic Server is supported to work with and without Zones
on Solaris 10. Read the following document for more information:
ftp://ftp.software.ibm.com/software/data/informix/ids/IDS-SunSPARC-reqs.pdf
4. The UNIX graphical tools provided with this release require 64-bit
X Windows System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, set the environment variable LD_LIBRARY_PATH to include
these locations: /usr/openwin/lib/sparcv9 and /usr/dt/lib/sparcv9.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest Solaris system requirements
for IBM Informix Dynamic Server:
http://www-306.ibm.com/software/data/informix/ids/requirements/sparc.html
System Configuration
====================
1. Kernel Parameters
a) The values of the kernel parameters that were used for testing this
product on Solaris 9 systems are given below. These values might need
to be tuned depending on the application and availability of system
resources. These entries are in /etc/system.
set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=500
set shmsys:shminfo_shmmax=4398046511104
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=500
set shmsys:shminfo_shmseg=100
The value of the kernel parameter "semmsl" should be set to at least
100. This is the maximum number of semaphores per set.
b) On Solaris 10, all System V IPC facilities are either automatically
configured or can be controlled by resource controls.
The following kernel parameters are either removed or commented out
from /etc/system:
semsys:seminfo_semmap
semsys:seminfo_semmns
semsys:seminfo_semmnu
semsys:seminfo_semume
shmsys:shminfo_shmmin
shmsys:shminfo_shmseg
The following obsolete IPC tunables are replaced by their resource
controls with the new default values:
semsys:seminfo_semmni
semsys:seminfo_semmsl
shmsys:shminfo_shmmax
shmsys:shminfo_shmmni
Refer to rctladm(1m) man page for more information about available
resource controls.
c) IDS Failure with a Large Intimate Shared Memory Page Size
On certain hardware configurations, Solaris 10 can use very large
memory pages for Solaris Intimate Shared Memory (ISM): 32 MB or
256 MB instead of the previous limit of 4 MB. IDS uses Solaris ISM
for shared memory segments that are forced to be memory-resident by
the RESIDENT configuration parameter, however IDS might experience
problems if 32 MB or 256 MB pages are used by Solaris (APAR
36804462).
If you receive a message that contiguous shared memory segment
allocation failed and the value of the SHMBASE configuration
parameter is the same as its value in onconfig.std, then IDS might
fail unexpectedly. To prevent this problem, set the Solaris 10
operating system mmu_ism_pagesize configuration parameter to limit
the memory pages to 4 MB for ISM. To set this parameter, edit the
/etc/system file and add the following line:
set mmu_ism_pagesize = 4194304
Then restart the Solaris computer.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x10A000000L
3. Environment Variables
It is recommended that the environment variable INFORMIXSTACKSIZE be
set to 128 (the default is 64) if the application involves operations
which would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines for the High Performance Loader must be
provided in a dynamic, shared library called ipldd11a.so. This shared
library is installed in the $INFORMIXDIR/lib directory. You can set the
location of this file with the HPL_DYNAMIC_LIB_PATH configuration
parameter in the file pointed to by PLCONFIG environment variable. For
more details see the "High-Performance Loader User's Guide".
To create a 64-bit shared library, the flags "-xarch=v9" can be used
to convey to the compiler that a 64-bit object is to be generated.
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
2. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS file to resolve to
the correct IP address, the name services files on the operating system
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/nsswitch.conf should be configured to fetch IPv6
addresss. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address, then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
3. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with the
embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
4. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from Sun Microsystems, which
uses the Solaris native threads based Java Virtual Machine.
The JRE 1.4.2 is available under $INFORMIXDIR/extend/krakatoa/jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is $INFORMIXDIR/extend/krakatoa
For developing Java UDRs used with J/Foundation, use the JDK 1.4.2 which
can be downloaded from
http://java.sun.com/javase/index.jsp
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in $INFORMIXDIR/etc.
5. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 536870912.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available (2^40)/2 MB. The sort memory comes out of the
DS_TOTAL_MEMORY memory and hence there is no explicit limit on the
amount of sort memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 536870912. The
"chunk" write algorithm is not dependent on the amount of buffers or
shared memory and can write as many pages in a single I/O as possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
6. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade module requires minimum version 6.0 of Websphere MQ
package to be installed.
Note: MQ DataBlade module expects Websphere MQ libraries installed in
the default location /opt/mqm. Otherwise create symbolic links
from /opt/mqm/lib64 to the 64-bit Websphere MQ libraries.
7. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
TLI using TCP/IP
SOCKETS using TCP/IP
IPC using stream pipe
To use TLI with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "ontlitcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drtlitcp"
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while supporting
SQLI connections you could add a DBSERVERALIASES entry to ONCONFIG which
corresponds to the sqlhosts file.
When using either TLI or SOCKETS, set the "connections" field in
the ONCONFIG NETTYPE parameter and the kernel driver ndd parameter
"tcp_conn_req_max_q" to the maximum number of expected concurrent
connections.
If the "tcp_conn_req_max_q" is set too low, you will see a client
error with sqlcode = -908 and isamcode = 13. If the NETTYPE
"connections" field is set too low, you will see a server
listener-thread error with err = -25571.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server using
either the TCP/IP or the IPC stream pipe protocols.
Fast poll is supported with all TCP/IP and stream pipe interfaces.
FASTPOLL in the ONCONFIG file can be set to 0 to disable the fast poll.
By default the fast poll is enabled (value is 1).
The protocol used for supporting MaxConnect on this platform is
"ontliimc".
8. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways
noted below.
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so.
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
This shared library must be compiled in 64-bit mode.
9. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
10. Optical
The name of the IBM Informix shared library for Optical on Solaris is
iosm11a.so. This library must be located in $INFORMIXDIR/lib (or must
have a link provided in $INFORMIXDIR/lib).
Refer to the "Optical Subsystem Guide" for more information about
enabling optical functionality.
11. Pluggable Authentication Module (PAM)
PAM functionality is supported on Solaris operating system. The PAM is
dependent on the libpam.so library supplied by the Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid widespread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
12. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM on
Solaris is libixspw.so.
Features not supported
======================
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version from previous versions of the server
(64-bit as well as 32-bit), refer to the migration process described in
the IBM Informix Migration Guide, Version 11.10.
To revert from this 64-bit version to all versions other than 32-bit
9.2x, 9.30, 9.40 and 10.00, refer to the IBM Informix Migration Guide,
Version 11.10.
To revert from 64-bit 11.10 (this server) to 32-bit 11.10:
-------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should
be in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32 -d
c. Shutdown the 64-bit server.
d. Start up the 32-bit 11.10 server by setting your INFORMIXDIR
environment variable to point to the 32-bit distribution.
To revert from 64-bit 11.10 (this server) to 32-bit 10.00, 9.40, 9.30
or 9.2x:
----------------------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should be
in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32
c. Revert to 9.2x, 9.30, 9.40 or 10.00 32-bit by following the steps
described in the IBM Informix Migration Guide, Version 11.10, in the
section "Reverting from Dynamic Server 11.10".
2. All UDRs and DataBlade modules that are built in 32-bit mode must be
re-compiled in 64-bit mode to work with the 64-bit server. If you have
any UDRs that were developed on 32-bit, make sure that the proper size
and alignment of the data structures are used for the UDRs to work
correctly on 64-bit after re-compilation in 64-bit mode.
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON SUN SOLARIS AMD/Opteron 64bit
DATE: 09 Dec 2008
=================================
OS Information : Built on Solaris 10 on AMD/Opteron
System Requirements
===================
1. This product was built and tested on Solaris 10 AMD/Opteron using the
following compilers from Sun Studio 11:
Sun C 5.8 Patch 121016-02 2006/03/31
Sun C++ 5.8 Patch 121018-02 2006/04/26
with the following patches:
120759-12 Sun Studio 11_x86: Sun Compiler Common patch for x86 backend
121018-02 Sun Studio 11_x86: Patch for Sun C++ 5.8 compiler
121016-02 Sun Studio 11_x86: Patch for Sun C_x86 5.8 Compiler
121616-01 Sun Studio 11_x86: Patch for Sun dbx 7.5_x86 Debugger
118677-02 SunOS 5.10_x86: patch for Solaris make and sccs utilities
121208-03 SunOS 5.10_x86: ld & libc.so.1 Patch
119961-02 SunOS 5.10_x86, x64, Patch for assembler
119964-06 SunOS 5.10_x86: Shared library patch for C++_x86
120754-02 SunOS 5.10_x86: Microtasking libraries (libmtsk) patch
121621-02 SunOS 5.10_x86: Patch for mediaLib in Solaris
The product was built with the following compiler option:
"-xtarget=generic64 -xarch=amd64"
This compiler option is expanded to:
"-xarch=amd64 -xcache=64/64/2:1024/64/16 -xchip=opteron"
2. Solaris patch information for the IBM Informix Dynamic Server
a. Install the recommended patch cluster for your OS version.
The cluster is available at http://sunsolve.Sun.COM/.
For example, if you are running Solaris 10, download and install
10_x86_Recommended.zip.
b. System specific patch for VP notify problem
Some Solaris OS and system patch combinations can be one of the
many possible causes of the VP countdown problem, where the
instance appears to hang and the following messages appearing in
the online log:
12:00:13 VP Notify mechanism incomplete after 5 minutes.
This can be due to slow network file access. Will
try 12 more times.
This issue can occur in the following releases:
Solaris 10 without patch 118855-15
Resolution:
Solaris 10 with patch 118855-15 or later
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102281-1
c. Sun Solaris 10 patch alert
Installation of certain Sun Solaris patches can cause a listener thread
within the Informix Dynamic Server to fail with an operating system
error of 13, preventing new network connections to the database server.
Sun Microsystems, Inc. has issued a Sun Alert Notification (Sun Alert
ID 102576) for this problem:
On Solaris 10 libnsl(3LIB) or TLI/XTI API routines May Cause Listener
Programs for Databases or Other Network Aware Applications to Stop
Responding.
This issue can occur in the following releases:
Solaris 10 with patch 118855-03 through 118855-19 and without patch
118855-20
Resolution:
Solaris 10 with patch 118855-20 or later
For more information visit:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102576-1
d. Sun Solaris 10 Maintenance Update 4
Some IBM Informix Dynamic Server utilities stop unexpectedly on
systems running Solaris 10 Update 4, especially if the systems have
Intel processors.
Resolution: Solaris 10 Update 5 or later.
3. IBM Informix Dynamic Server is supported to work with and without Zones
on Solaris 10. Read the following document for more information, this
would be also applicable to Solaris AMD/Opteron system:
ftp://ftp.software.ibm.com/software/data/informix/ids/IDS-SunSPARC-reqs.pdf
4. The UNIX graphical tools provided with this release require 64-bit
X Windows System X11R6 and Motif 2.1 or later runtime libraries.
If these tools cannot find the location of the X and Motif shared
libraries, set the environment variable LD_LIBRARY_PATH to include
these locations: /usr/openwin/lib/amd64 and /usr/dt/lib/amd64.
5. The High Performance Loader utilities, onpload and ipload, require a
minimum of 35 MB of memory and 70 MB of swap space in order to run.
Check the following web site for the latest Solaris AMD/Opteron system
requirements for IBM Informix Dynamic Server:
http://www-306.ibm.com/software/data/informix/ids/requirements/solaris-x86.html
System Configuration
====================
1. System V IPC Parameters
On Solaris 10, all System V IPC facilities are either automatically
configured or can be controlled by resource controls.
Check project.max-shm-memory on your system, IBM recommend the value
of 4398046511104 for the IBM Informix Dynamic Server.
Refer to rctladm(1m) man page for more information about available
resource controls.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x10A000000L
3. Environment Variables
It is recommended that the environment variable INFORMIXSTACKSIZE be
set to 128 (the default is 64) if the application involves operations
which would require the IBM Informix Dynamic Server to perform recursive
database tasks (for example, cascading deletes).
Feature Notes (alphabetized by feature)
=============
1. High Performance Loader
User-defined conversion routines for the High Performance Loader must be
provided in a dynamic, shared library called ipldd11a.so. This shared
library is installed in the $INFORMIXDIR/lib directory. You can set the
location of this file with the HPL_DYNAMIC_LIB_PATH configuration parameter
in the file pointed to by PLCONFIG environment variable. For more details
see the "High-Performance Loader User's Guide".
To create a 64-bit shared library, the flags "-xarch=amd64" can be used
to convey to the compiler that a 64-bit object is to be generated.
Onpload will use shared memory during its execution. It will allocate
memory beyond the address for the server, leaving room for server shared
memory expansion.
2. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS file to resolve to
the correct IP address, the name services files on the operating system
should be correctly configured. If the machine has IPv6 address configured
and the listener thread is bound to an IPv6 address, then the name
resolution files /etc/nsswitch.conf should be configured to fetch IPv6
addresss. Also use the appropriate /etc/hosts setting if local machine
settings are used.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in nodename field of SQLHOSTS
file. Client applications should also use the same setting.
3. ISMP - InstallShield Multi-Platform
A JRE is embedded in the installation program. If you have problems with the
embedded JRE, you can use your own. The minimum recommended JRE version
is 1.4.2.
4. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM. Most UNIX systems are limited to 4GB of
RAM based on the memory addressing limitations of 32-bit architectures.
The values for the following ONCONFIG parameters are increased from
32-bit to 64-bit platform by LMA support:
- The maximum number of buffers in BUFFERPOOL is 536870912.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available (2^40)/2 MB. The sort memory comes out of the
DS_TOTAL_MEMORY memory and hence there is no explicit limit on the
amount of sort memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 536870912. The
"chunk" write algorithm is not dependent on the amount of buffers or
shared memory and can write as many pages in a single I/O as possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The value for SHMADD is 4294967296 kilobytes.
Please refer to IBM Informix Administrator's Reference manual for the
information about the related configuration parameters setting.
5. MQ DataBlade Module
The MQ DataBlade module provides mechanism for data exchange between
IDS and queues managed by Websphere MQ.
MQ DataBlade requires minimum version 6.0 of Websphere MQ to be installed.
6. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
TLI using TCP/IP
SOCKETS using TCP/IP
IPC using stream pipe
To use TLI with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "ontlitcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drtlitcp"
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onsoctcp".
b. To enable an IBM Data Server Client to connect to Informix
Dynamic Server, NETTYPE in the ONCONFIG file and the value data
of protocol in the sqlhosts file entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while supporting
SQLI connections you could add a DBSERVERALIASES entry to ONCONFIG which
corresponds to the sqlhosts file.
When using either TLI or SOCKETS, set the "connections" field in
the ONCONFIG NETTYPE parameter and the kernel driver ndd parameter
"tcp_conn_req_max_q" to the maximum number of expected concurrent
connections.
If the "tcp_conn_req_max_q" is set too low, you will see a client
error with sqlcode = -908 and isamcode = 13. If the NETTYPE
"connections" field is set too low, you will see a server
listener-thread error with err = -25571.
To use IPC (interprocess communication) with stream pipe:
a. NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
Fast poll is supported with all TCP/IP and stream pipe interfaces.
FASTPOLL in the ONCONFIG file can be set to 0 to disable the fast poll.
By default the fast poll is enabled (value is 1).
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server using
either the TCP/IP or the IPC stream pipe protocols.
The protocol used for supporting MaxConnect on this platform is
"ontliimc".
7. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a shared library supplied
by third party storage management vendors. For ON-Bar to access these
functions, the library must be installed in one of the three ways
noted below.
a. Rename the library to $INFORMIXDIR/lib/ibsad001.so.
b. Create $INFORMIXDIR/lib/ibsad001.so as a symbolic link to the
library.
c. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG
to the full pathname of the library.
This shared library must be compiled in 64-bit mode.
8. Optical
The name of the IBM Informix shared library for Optical on Solaris is
iosm11a.so. This library must be located in $INFORMIXDIR/lib (or must have
a link provided in $INFORMIXDIR/lib).
Refer to the "Optical Subsystem Guide" for more information about
enabling optical functionality.
9. Pluggable Authentication Module (PAM)
PAM functionality is supported on Solaris (64bit) operating system.
The PAM is dependent on the libpam.so library supplied by the
Operating System vendor.
Use of PAM can be enabled or disabled by the system administrator. By
default, IBM IDS will use the traditional authentication mechanism in
order to avoid wide spread changes required by the users.
The PAM service identifies the PAM module. This PAM module typically
resides in /usr/lib/security and its parameters are listed in
/etc/pam.conf.
10. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on Solaris is libixspw.so.
Features not supported
======================
1. J/Foundation (Java in the Server)
2. OnSNMP
3. Shared Disk Secondary Servers
4. Basic Text Search DataBlade Module
5. Web Feature Service DataBlade Module
6. XML Publishing
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version from previous versions of the server
(64-bit as well as 32-bit), refer to the migration process described in
the IBM Informix Migration Guide, Version 11.10.
To revert from this 64-bit version to all versions other than a 32-bit
server, refer to the IBM Informix Migration Guide, Version 11.10.
2. To revert from 64-bit 11.10 (this server) to a 7.31 32-bit server by
following the steps described in the IBM Informix Migration Guide, Version
11.10, in the section "Reverting from Dynamic Server 11.10".
To revert from 64-bit 11.10 (this server) to 32-bit 9.2x:
---------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should be
in online mode.
b. Run the following command as user informix or DBA:
$INFORMIXDIR/etc/conv/update.sh -32
c. Revert to 9.2x 32-bit by following the steps described in the IBM
Informix Migration Guide, Version 11.10, in the section, "Reverting
from Dynamic Server 11.10".
Known Defects
=============
Refer to section I in doc/ids_defects_11.10.txt for the information
regarding other known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in doc/ids_defects_11.10.txt for the information
regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in doc/ids_defects_11.10.txt for the information
regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2007, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.TC3 PRODUCT RELEASE
ON Windows
DATE: 08 Dec 2008
=================================
OS Information : Built on Windows Server 2003, Certified on Windows XP
(except Home Edition), Windows Server 2008 and
Windows Vista (except Home Edition).
System Requirements
===================
1. This product is built on Windows Server 2003 with Service Pack 2 using the
following compiler from Microsoft Visual Studio 2005:
Microsoft Visual C++ 2005
The product is tested on Windows 2003 with Service Pack 1 and 2, Windows
XP with Service Pack 2, and Windows Vista.
2. Operating system patches information for the IBM Informix Dynamic Server
The following patches are required if you intend to configure Informix
Dynamic Server instances with larger than the default shared memory size,
such as increasing the number of buffers and locks from their default size
during installation.
Windows 2003 Service Pack 1
873453 Fix for "The base memory address setting of the Samlib.dll file
in Windows Server 2003 may interfere with programs that require
a large shared memory setting."
912570 Fix for "Programs that require lots of memory may not run after
you install Windows Server 2003 Service Pack 1."
913409 Fix for "A program that allocates a large block of contiguous
memory may not start or may intermittently fail in Windows
Server 2003."
924054 Fix for "Programs that request lots of contiguous memory may
fail after you install security update 921883 (MS06-040) on a
Windows Server 2003 Service Pack 1-based computer or a Windows
XP Professional x64 Edition-based computer."
Windows 2003 Service Pack 2
948656 Fix for "A program that allocates a large block of contiguous
memory may not start or may intermittently fail in Windows
Server 2003 with Service Pack 2."
Windows XP Service Pack 2
894472 Fix for "Third-party programs that require lots of memory do
not run in Windows XP Service Pack 2."
For information about Microsoft service packs and patches, see the Microsoft
Support web site at http://support.microsoft.com.
3. Enable Connections on Windows Vista
To enable connections between database servers on the Vista operating
system, you must enable network discovery and NetBIOS over TCP/IP.
To enable connections:
1) From the Control Panel, double-click Network and Sharing.
2) In the Sharing and Discovery section of the Network and Sharing Center,
click Network discovery and then Turn on network discovery.
3) In the Network section, click View Status next to the Local Area
Connection.
4) In the Local Area Connection Status dialog box, click Properties.
5) In the Local Area Connection Properties dialog box, choose the
appropriate Internet Protocol Version and click Properties.
6) In the Internet Protocol Version Properties dialog box, click Advanced.
7) On the WINS page of the Advanced TCP/IP Settings dialog box, click
Enable NetBIOS over TCP/IP and then click OK.
8) Continue clicking OK or Close until all dialog boxes are closed.
4. Using the Error Messages Utility
You might get the following error when using the Error Messages utility
on Vista:
"The Help for this program was created in Windows Help format,
which was used in previous versions of Windows and it is not
supported in Windows Vista."
The workaround is to download the Windows Help program (WinHlp32.exe)
from the following Microsoft support Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=6ebcfad9-d3f5-4365-8070-334cd175d4bb&displaylang=en
Check the following web site for the latest Windows system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/windows.html
System Configuration
====================
1. Location of Shared Memory
The ONCONFIG variable SHMBASE is recommended to be set to the following:
SHMBASE 0xc000000L
2. Support maximum shared memory
The database server can access shared-memory larger than two gigabytes
on Windows. However, you must enable this feature with an entry in the
Windows boot file.
To add the entry, edit the boot.ini file (located in the top level, or
root directory). You can either add a new boot option or use the currently
existing boot option. To enable support for more than two gigabytes, add
the following text to the end of the boot line:
/3GB
Feature Notes (alphabetized by feature)
=============
1. Informix Interface for TSM
The Informix Interface DLL for TSM is installed as
%INFORMIXDIR%\bin\libtxbsa.dll
To use Tivoli Storage Manager with Informix databases, refer to IBM
Informix Backup and Restore Guide.
2. Informix Storage Manager (ISM 2.2)
The product is installed with IDS at location of %ISMDIR%. The
XBSA shared library name is %ISMDIR%\bin\libbsa.dll.
To use Informix Storage Manager with Informix databases, refer to IBM
Informix Backup and Restore Guide.
3. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS registry to resolve
to the correct IP address, the name services files on the Operating System
should be correctly configured.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in nodename field of server
registry.
4. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM Corporation.
The JRE 1.4.2 is available under %INFORMIXDIR%\extend\krakatoa\jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>/jre
where <jvphome> is %INFORMIXDIR%\extend\krakatoa
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in %INFORMIXDIR%\etc.
5. LDAP Authentication
This feature is set up and configured like the Pluggable Authentication
Module (PAM) that is used on UNIX and Linux. Use the LDAP Authentication
Support module when you want to use an LDAP server to authenticate your
system users.
The authentication module is a dynamic link library that resides in the
%INFORMIXDIR%\dbssodir\lib\security directory. The parameters of the module
are listed in the %INFORMIXDIR%\dbssodir\pam.conf file.
The source code for a fully functional LDAP Authentication Module and
samples of the required configuration files are included in the
%INFORMIXDIR%\demo\authentication directory. You can modify the code for
your specific LDAP Authentication Support module.
6. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
SOCKETS using TCP/IP
IPC using named pipe
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the value data of PROTOCOL in the
SQLHOSTS registry entry must contain "onsoctcp"
b. To enable an IBM Data Server Client to connect to Informix Dynamic
Server, NETTYPE in the ONCONFIG file and the value data of PROTOCOL
in the SQLHOSTS registry entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the SQLHOSTS registry entry.
To use IPC (interprocess communication) with named pipe:
a. NETTYPE in the ONCONFIG file and the value data of PROTOCOL in the
SQLHOSTS registry entry must contain "onipcnmp".
7. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a dynamic link library
supplied by third party storage management vendors. For ON-Bar to access
these functions, you must specify the library name and location in the
BAR_BSALIB_PATH ONCONFIG parameter.
For example, if you are using ISM:
Set BAR_BSALIB_PATH to %ISMDIR%\bin\libbsa.dll
For example, if you are using TSM:
Set BAR_BSALIB_PATH to %INFORMIXDIR%\lib\libtxbsa.dll
8. Simple Password Communications Support Module
The name of the IBM Informix dynamic link library for Simple Password CSM
on Windows is libixspw.dll. This dynamic link library is installed in
%INFORMIXDIR%\bin.
Features not supported
======================
1. Shared Disk Secondary Servers
Known Defects
=============
Refer to section I in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
(Enterprise or Workgroup Editions) or idse_win_fixed_and_known_defects_11.10.txt
(Express Edition) for the information regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
(Enterprise or Workgroup Editions) or idse_win_fixed_and_known_defects_11.10.txt
(Express Edition) for the information regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
for the information regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2002, 2008.
=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 11.10.FC3 PRODUCT RELEASE
ON Windows x64
DATE: 08 Dec 2008
=================================
OS Information : Built on Windows Server 2003 x64, Certified on Windows XP x64,
Windows Server 2008 x64 and Windows Vista x64.
System Requirements
===================
1. This product is built on Windows 2003 with Service Pack 2 using the
following compiler:
Microsoft Visual Studio 2005 - Ver. 8.0.50727.762 - C/C++
Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) is required
to be installed on the system.
The product is tested on Windows 2003 x64 with Service Pack 2, Windows
XP x64 with Service Pack 2, and Windows Vista x64.
2. Operating system patches information for the IBM Informix Dynamic Server
Windows 2003:
Service Pack 2
948656 Fix for "A program that allocates a large block of contiguous
memory may not start or may intermittently fail in Windows
Server 2003 with Service Pack 2."
Windows XP:
Service Pack 2
894472 Fix for "Third-party programs that require lots of memory do
not run in Windows XP Service Pack 2."
For information about Microsoft service packs and patches, see the Microsoft
Support web site at http://support.microsoft.com.
3. Enable Connections on Windows Vista
To enable connections between database servers on the Vista operating
system, you must enable network discovery and NetBIOS over TCP/IP.
To enable connections:
1) From the Control Panel, double-click Network and Sharing.
2) In the Sharing and Discovery section of the Network and Sharing Center,
click Network discovery and then Turn on network discovery.
3) In the Network section, click View Status next to the Local Area
Connection.
4) In the Local Area Connection Status dialog box, click Properties.
5) In the Local Area Connection Properties dialog box, choose the
appropriate Internet Protocol Version and click Properties.
6) In the Internet Protocol Version Properties dialog box, click Advanced.
7) On the WINS page of the Advanced TCP/IP Settings dialog box, click
Enable NetBIOS over TCP/IP and then click OK.
8) Continue clicking OK or Close until all dialog boxes are closed.
4. Using the Error Messages Utility
You might get the following error when using the Error Messages utility
on Vista:
"The Help for this program was created in Windows Help format,
which was used in previous versions of Windows and it is not
supported in Windows Vista."
The workaround is to download the Windows Help program (WinHlp32.exe)
from the following Microsoft support Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=6ebcfad9-d3f5-4365-8070-334cd175d4bb&displaylang=en
5. IDS uninstallation
Due to an issue in installer tool, the registry entries created by installer
will not be automatically removed after IDS uninstall. The work around is
to cleanup existing registry entries under HKLM->Software->Informix->DBMS.
Check the following web site for the latest Windows system requirements
for IBM Informix Dynamic Server:
http://www.ibm.com/software/data/informix/ids/requirements/windows.html
System Configuration
====================
1. Location of Shared Memory
The ONCONFIG variable SHMBASE is recommended to be set to the following:
SHMBASE 0x80000000L
Feature Notes (alphabetized by feature)
=============
1. Informix Interface for TSM
The Informix Interface DLL for TSM is installed as
%INFORMIXDIR%\bin\libtxbsa.dll
To use Tivoli Storage Manager with Informix databases, refer to IBM
Informix Backup and Restore Guide.
2. Informix Storage Manager (ISM 2.2)
The product is installed with IDS at location of %ISMDIR%. The
XBSA shared library name is %ISMDIR%\bin\libbsa64.dll.
To use Informix Storage Manager with Informix databases, refer to IBM
Informix Backup and Restore Guide.
3. IPv6 Support
IBM Informix Server supports Internet Protocol Version 6 (128 Bit Internet
Addresses) as well as IPv4 (32 Bit Addresses).
In order for the machine name specified in the SQLHOSTS registry to resolve
to the correct IP address, the name services files on the Operating System
should be correctly configured.
For compatibility with older IBM Informix client and server products,
assign the same hostname with both an IPv4 address and an IPv6 address.
If the listener needs to be bound to an IPv4 address and the name services
resolve the name in the order of the IPv6 address followed by IPv4 address,
then an explicit IPv4 address needs to be put in the nodename field of the
server registry.
4. J/Foundation (Java in the Server)
J/Foundation supports the JRE 1.4.2 release from IBM Corporation.
The JRE 1.4.2 is available under %INFORMIXDIR%\extend\krakatoa\jre and
should be used with J/Foundation.
To use this JRE, set the value of the ONCONFIG variable JVPJAVAHOME as
follows:
JVPJAVAHOME <jvphome>\jre
where <jvphome> is %INFORMIXDIR%\extend\krakatoa
For IBM Informix Dynamic Server ONCONFIG settings for J/Foundation,
refer to "onconfig.std" in %INFORMIXDIR%\etc.
5. Large Memory Addressability (LMA)
IBM Informix LMA provides the ability to support system configurations
with greater than 4GB of RAM.
The values for the following ONCONFIG parameters are increased from
32-bit limit by LMA support:
- The maximum number of buffers in BUFFERPOOL is 2147483647.
- The maximum of LRU queues for lrus field in BUFFERPOOL is 512.
- The DS_TOTAL_MEMORY, which is the total memory available for
decision support memory, is only limited by the amount of virtual
memory available. The sort memory comes out of the DS_TOTAL_MEMORY
memory and hence there is no explicit limit on the amount of sort
memory.
- The read ahead parameter RA_PAGES is only limited by the number of
buffers and therefore can be any value less than 2147483647. The
"chunk" write algorithm is not dependent on the amount of buffers
or shared memory and can write as many pages in a single I/O as
possible.
- The maximum size of any shared memory segment is 4398046511104 bytes.
- The maximum value for SHMADD is 4294967296 kilobytes.
Refer to IBM Informix Administrator's Reference manual for the information
about the related configuration parameters setting.
6. LDAP Authentication
This feature is set up and configured like the Pluggable Authentication
Module (PAM) that is used on UNIX and Linux. Use the LDAP Authentication
Support module when you want to use an LDAP server to authenticate your
system users.
The authentication module is a dynamic link library that resides in the
%INFORMIXDIR%\dbssodir\lib\security directory. The parameters of the module
are listed in the %INFORMIXDIR%\dbssodir\pam.conf file.
The source code for a fully functional LDAP Authentication Module and
samples of the required configuration files are included in the
%INFORMIXDIR%\demo\authentication directory. You can modify the code for
your specific LDAP Authentication Support module.
7. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
SOCKETS using TCP/IP
IPC using named pipe
To use SOCKETS with TCP/IP:
a. NETTYPE in the ONCONFIG file and the value data of PROTOCOL in the
SQLHOSTS registry entry must contain "onsoctcp"
b. To enable an IBM Data Server Client to connect to Informix Dynamic
Server, NETTYPE in the ONCONFIG file and the value data of PROTOCOL
in the SQLHOSTS registry entry must contain "drsoctcp"
If a CLI or JCC client wants to connect to IDS via DRDA while
supporting SQLI connections you could add a DBSERVERALIASES entry
to ONCONFIG which corresponds to the SQLHOSTS registry entry.
To use IPC (interprocess communication) with named pipe:
a. NETTYPE in the ONCONFIG file and the value data of PROTOCOL in the
SQLHOSTS registry entry must contain "onipcnmp".
Remote 32-bit applications and tools (example: ESQL/C, 4GL, ISQL) can
only connect to the IBM Informix Dynamic Server using the TCP/IP
protocol.
Local 32-bit applications and tools can connect to the 64-bit server using
either the TCP/IP or the IPC named pipe protocols.
8. OnLine Backup and Restore (ON-Bar)
Some of the functions invoked by ON-Bar are in a dynamic link library
supplied by third party storage management vendors. For ON-Bar to access
these functions, you must specify the library name and location in the
BAR_BSALIB_PATH ONCONFIG parameter.
For example, if you are using ISM:
Set BAR_BSALIB_PATH to %ISMDIR%\bin\libbsa64.dll
For example, if you are using TSM:
Set BAR_BSALIB_PATH to %INFORMIXDIR%\lib\libtxbsa.dll
9. Simple Password Communications Support Module
The name of the IBM Informix dynamic link library for Simple Password CSM
on Windows is libixspw.dll. This dynamic link library is installed in
%INFORMIXDIR%\bin.
Features not supported
======================
1. Basic Text Search DataBlade Module
2. OnSNMP
3. MQ DataBlade Module
4. Shared Disk Secondary Servers
5. Web Feature Service DataBlade Module
6. XML Publishing
Migrating to this 64-bit Version
================================
1. To migrate to this 64-bit version from version 10.00 of the server
(Windows 32-bit), refer to the migration process described in the
IBM Informix Migration Guide, Version 11.10.
To migrate from a 32-bit 11.10 server to this 64-bit version:
-------------------------------------------------------------
Due to IDS defect idsdb00138023, 32-bit and 64-bit versions of IDS 11.10
cannot co-exist on the same machine. The following steps can be followed
to migrate from 11.10 32-bit to 11.10 64-bit on the same machine.
a. Install 32-bit product and initialize the instance with data as needed.
b. Uninstall 32-bit product - but choose the default option "Remove server
binaries only".
c. Install 64-bit product - custom mode to the same location - do not
create a new instance.
d. Starting the instance should use the new binaries with dbspaces
converted.
To revert from 64-bit 11.10 (this server) to 32-bit 11.10:
----------------------------------------------------------
Due to IDS defect idsdb00138023, 32-bit and 64-bit versions of IDS 11.10
cannot co-exist on the same machine. The following steps can be followed
to revert from 11.10 64-bit to 11.10 32-bit on the same machine.
a. Install 64-bit product and initialize the instance with data as needed.
b. The 64-bit server should be in online mode. Make sure no users connected
with this server.
c. Run the following command as user informix or DBA:
%INFORMIXDIR%\etc\conv\update.exe -32 -d
d. Shutdown the 64-bit server.
e. Uninstall 64-bit product - but choose the default option "Remove server
binaries only".
f. Install 32-bit product - custom mode to the same location - do not
create a new instance.
g. Bring up the 32-bit 11.10 server by setting your INFORMIXDIR
environment variable to point to the 32-bit distribution.
To revert from 64-bit 11.10 (this server) to 32-bit 10.00:
----------------------------------------------------------
a. Disconnect all users from this server. The 64-bit server should be
in online mode.
b. Run the following command as user informix or DBA:
%INFORMIXDIR%\etc\conv\update.exe -32
c. Revert to Version 10.00 32-bit by following the steps described in
the IBM Informix Migration Guide, Version 11.10, in the section
"Reverting from Dynamic Server 11.10".
2. All UDRs and DataBlades modules that are built in 32-bit mode must be
re-compiled in 64-bit mode to work with the 64-bit server. If you have
any UDRs that were developed on 32-bit, make sure that the proper size
and alignment of the data structures are used for the UDRs to work
correctly on 64-bit after re-compilation in 64-bit mode.
Known Defects
=============
Refer to section I in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
for the information regarding known issues in this release.
Defects Fixed in current Release
================================
Refer to section II in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
for the information regarding defects fixed in this release.
Defects Fixed in Previous Release
=================================
Refer to section III in
%INFORMIXDIR%\release\en_us\04e4\ids_win_fixed_and_known_defects_11.10.txt
for the information regarding defects fixed in previous release.
(C) Copyright IBM Corp. 2007, 2008.