=================================
MACHINE SPECIFIC NOTES
FOR
IBM Informix Dynamic Server 9.30.UC7 PRODUCT RELEASE
ON IBM NumaQ DYNIX/ptx
DATE: 10 Dec 2003
=================================
PORT NUMBER: 211048 (CD ROM), 211049 (Electronic Delivery)
IRIS JOB NUMBER: 42017
OS Information : Built on DYNIX/PTX 4.5.1, Certified on 4.5.2, 4.5.3, 4.6.1
System Requirements:
===================
1. DYNIX/ptx 4.5.1 package and patch information for the IBM Informix
Dynamic Server
a. Install the following packages or higher versions:
- DYNIX/ptx(R) Base V4.5.1
- DYNIX/ptx(R) Encryption V4.5.1
- ptx/SPDRIVERS V3.1.0
- ptx/INSTALL V2.0.3
- ptx/BaseComms V1.2.0
- ptx/LAN V4.7.1
- ptx/TCP/IP V4.6.1
- ptx/NFS V4.7.1
- ptx/EFS V1.4.1
- ptx/SVM V2.2.1
- ptx/XWM V4.6.1
- ptx/AGENT V1.4.0
- ptx/C++ V5.2.3
- ptx/C++ Runtime V5.2.3
- ptx/XWM Contributed V4.6.1
- DYNIX/ptx(R) Public Software V4.5.1
- DYNIX/ptx(R) Base Service Pack V4.5.1sp3
b. Install the following patches:
- Layered product Install Patch V1.0.1
- ptx/TCP/IP FP#251764 V4.6.1rv1
- ptx/SPDRIVERS FP#251643 V3.1.0rv1
2. The UNIX graphical tools provided with this release require ptx/WINDOWS
V4.4.1 or X Windows System X11R5 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. For DYNIX/ptx, this should be set to
include /usr/X11R5/lib.
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.
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.
BUFPCT 5
NABUF 1024
MAXAIO 1024
MAXUP 1024
MSGMAP 1024
MSGMAX 65535
MSGMNI 1024
MSGSEG 32767
MSGSSZ 32
MSGTQL 1024
N_TCP_PCB_FREE 1024
N_UDP_PCB_FREE 512
N_UDP_PCB_HDRS 19
NPROC 2000
SEMMAP 8192
SEMMNI 8192
SEMMNS 8192
SEMMNU 8192
SEMMSL 1024
SEMUME 64
SFNOLIM 512
SHM_LOCK_OK 1
SHMMAX 268435456
SHMMNI 2048
- The value of the kernel parameter SEMMSL should be set to 1024 and
SEMMNS to 4096. This is the maximum number of semaphores per set.
See the section on "Configuring Semaphore Parameters" in the IBM
Informix Dynamic Server Migration Guide for details.
- Set the value of the kernel parameter SEMMNU 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 kernel parameters NABUF and MAXAIO must be increased in order to
allow the Informix Dynamic Server to perform correctly. The
recommended value is 128 times the number of CPU VPs. For example, on
a system running 6 IBM Informix CPU VPs, NABUF and MAXAIO need to be
increased by 768.
If the values for NABUF and MAXAIO are too small, the server will
report the following error message:
"KAIO: out of OS resources, errno = 11, pid = "
in the online.log file.
- In order to allow shared memory locking in RAM, the following two
parameters must be set as follows:
SHM_LOCK_OK 1
SHM_LOCK_UID 0 (or -1)
- The maximum size of a shared memory segment allocated by the IBM
Informix Dynamic Server with (SHMBASE at 0x10000000) is about 2.75 GB.
This may be limited by actual memory available and/or kernel
configuration.
- The parameter SFNOLIM must be configured to be slightly greater than
the number of chunks in the database. Furthermore, NFILE must be
increased by the number of chunks multiplied by the number of CPU VPs.
Typically, for a database with 5 CPU VPs and 400 chunks, one would use
SFNOLIM set to 512, and NFILE increased by 2000.
- N_TCP_PCB_FREE should be adjusted to reflect the number of clients
connected to the database via the network. Adjusting N_TCP_PCB_FREE
will adjust NTLI and NTRW automatically.
- The TCP_KEEPIDLE parameter has a default value of 2 hours which is
very high. IBM recommends a value of 10 to 15 minutes.
2. Location of Shared Memory
The ONCONFIG variable SHMBASE should be set to the following:
SHMBASE 0x10000000
3. IBM Informix Dynamic Server versions 7.x and 9.x cannot use raw
partitions on IBM NumaQ DYNIX/ptx ELS (Entry Level System). The generic
system limit for raw I/O transfer size is 128 KB for DYNIX/ptx. It is a
function of the varying disk device drivers to change this allowable
limit during initialization.
The ADAPTEC AHA-1542CF controller on ELS systems limits the maximum raw
I/O size to 120 512-byte blocks (60 KB). The ad(7) man page is
incorrect in stating the limit as 254 sectors (127 KB), as per the
IBM NumaQ DYNIX/ptx Report 211660. The only supported disk driver on
ELS systems is the ADAPTEC AHA-1542CF SCSI. For this reason, the IBM
Informix Dynamic Server versions 7.x and 9.x will not function on ELS
systems with raw disk usage.
4. Audit Support
Configuring the Operating System Audit Subsystem:
------------------------------------------------
The following describes how to configure the OS audit subsystem to
record IBM Informix Dynamic Server audit records in the OS audit log.
In order to have OS audit support, the following steps need to be
followed:
a. A new audit class "ix" must be introduced to the OS audit
subsystem as the class for IBM Informix Dynamic Server generated
audit events.
b. A new event "AU_INFORMIX" must be introduced to the audit
subsystem. This will be an event type belonging to the "ix" audit
class, and will be used by the IBM Informix Dynamic Server.
c. The OS audit subsystem must be configured to audit events of the
event class designated by "ix".
d. The OS audit subsystem must be operational, and auditing enabled.
Starting the Audit System:
-------------------------
After configuring the system, enable auditing with the new
configuration. The OS auditing must be enabled for all users who might
use the IBM Informix Dynamic Server, and for the event type AU_INFORMIX,
of the event class "ix". Refer to DYNIX/ptx System Administration Guide
Volume 2 (System Auditing) in order to accomplish this.
The class type "ix" must be introduced by inserting a line defining the
class in /etc/auclass. The audit class number should be within the
range 91-100 (which is available for definition by users). A sample
entry in /etc/auclass file is shown below:
# IBM Informix Dynamic Server classes
99:ix::For IBM Informix Dynamic Server
The event type AU_INFORMIX must be introduced to the OS by inserting a
line defining this event in the file /etc/auevent. The event type ID
should be within the range 20000 - 29999 (which is the valid range for
user defined audit events). A sample entry in /etc/auevent file is
shown below:
# IBM Informix events
20002:AU_INFORMIX::For IBM Informix Dynamic Server
Pay careful attention to the formats, even of the comments, because they
are parsed by audit commands and by the other audit library functions at
runtime.
Setting up the System Audit Mask:
--------------------------------
To receive IBM Informix Dynamic Server audit data, the audit mask must
be configured to accept class "ix" for the particular user. Refer to the
DYNIX/ptx System Administration Guide Volume 2 (System Auditing) for
more information on audit masks and how to configure them. A sample
entry in the /etc/audit_aliases file (which stores the "alias"
information that uniquely identifies an audit mask) is given below:
# Normal user audit. This will audit the user as they login or change
# user states. It will also audit basic DAC and priv failures.
#
normal: s{login, su, ix},
d{open, ix},
p{ },
o{su, ix}
Important Files in Configuring the OS Audit Subsystem:
-----------------------------------------------------
/etc/audit_aliases
/etc/auevent
/etc/auclass
Audit Log Records:
------------------
To select which IBM Informix Dynamic Server events are to be audited,
specify audit masks using the "onaudit" utility. Refer to the
IBM Informix Dynamic Server Trusted Facility Manual (TFM) for further
details.
To extract audit records from the operating system audit trail, use
"onshowaudit -O" to extract the IBM Informix Dynamic Server records.
Refer to the IBM Informix Dynamic Server TFM for further details.
The IBM Informix Dynamic Server Trusted Facility Manual indicates that
the "-f" option of the onshowaudit utility (to specify the path of audit
trail file) can be used for extracting audit records from the audit
trail only. On IBM NumaQ DYNIX/ptx, however, the user has to specify
the "-f" option of the onshowaudit utility for Operating System managed
auditing also, to extract the audit records created by IBM Informix
Dynamic Server.
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 ipldd09a.so. This
library must be located in /usr/lib (or must have a link provided in
/usr/lib).
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. Network Protocols
The following protocol(s)/interface(s) are supported on this platform:
TLI using TCP/IP
IPC using stream pipe
IPC using shared memory
To use TLI with TCP/IP:
NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "ontlitcp".
To use IPC (interprocess communication) with stream pipe:
NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcstr".
To use IPC (interprocess communication) with shared memory:
NETTYPE in the ONCONFIG file and the nettype field in the
sqlhosts file entry must contain "onipcshm".
The protocol used for supporting MaxConnect on this platform is
"onsocimc".
If you are using a NUMA system and have several IP addresses configured
on the same physical interface, note:
The IBM Informix TCP listener thread binds to a particular IP
address/port. It listens for incoming calls addressed to only one
IP address. If there are multiple IP addresses configured on the
system, a TLI client will not be able to connect to the server.
(If DNS is configured to resolve the hostname on a rotary of the
four IP addresses, you do not know which of those addresses has
been selected by the IBM Informix TCP listener).
The solution is that in the $INFORMIXDIR/etc/sqlhosts file, use
"*hostname" instead of "hostname". It will make the IBM Informix
TCP listener bind to INADDR_ANY instead of a particular address.
3. 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 /usr/lib/ibsad001.so.
b. Create /usr/lib/ibsad001.so as a symbolic link to the library.
c. Set the BAR_BSALIB_PATH parameter in /engops/irb930/vobs/tristarm/sqldist/etc/onconfig.std
to the full pathname of the library.
The IBM Informix Storage Manager (ISM) is supports the following devices:
QIC-525 1/4" cartridge drive (model - Tanberg 3820)
4mm DDS drive (model - HP C1533A)
4mm DDS Autoloader
8mm drive (model - Exabyte EXB-8500DT)
4. OnSNMP
The SNMP agent for OnSNMP is based on SNMP Research (SNMPR).
The IBM NumaQ ptx/Agent and ptx/Agent SDK should be installed to use
this feature. The ptx/Agent 1.3.1 and ptx/Agent SDK 1.3.1 packages
have to be procured from IBM/NumaQ Computer Systems and installed on the
machine to use OnSNMP.
The SR_AGT_CONF_DIR and SR_MGR_CONF_DIR environment variables should
NOT be set.
The IBM Informix Dynamic Server distribution includes the following:
bin/onsnmp The OnSNMP subagent itself, packaged as a
separate process (referred to as a "loosely
coupled dynamic" subagent by SNMP Research).
bin/onsrvapd The daemon which spawns off a subagent for
each server it discovers.
snmp/*V1.mib SNMP V1 compliant MIB files defining the
instrumentation provided with OnSNMP.
snmp/*V2.mib SNMP V2 compliant MIB files defining the
instrumentation provided with OnSNMP.
In order to update the /usr/agent/config/mgr/snmpinfo.dat file with the
onsnmp info.dat file do the following:
a. Generate the dat file from the mibfiles using mosy and postmosy.
b. cd /usr/agent/config/mgr
c. cp snmpinfo.dat snmpinfo.dat.save
d. cd $(INFORMIXDIR)/etc
e. postmosy -merge
5. Optical
The name of the IBM Informix shared library for Optical on DYNIX/ptx is
iosm09a.so. This library must be located in /usr/lib (or must have
a link provided in /usr/lib). Refer to the Guide to the Optical
Subsystem for more information about enabling optical functionality.
6. Partition Profiling
The collection of partition statistics is by default enabled. This
can be disabled by setting the ONCONFIG variable TBLSPACE_STATS to 0.
When TBLSPACE_STATS is set to 0, the output of "onstat -g ppf" will
read "Partition profiles disabled".
Disabling the partition profiling will result in fewer cache
invalidations and less bus traffic due to fewer updates to the partition
structure in the shared memory. This especially benefits NUMA systems,
since disabling partition profiling will reduce intra-quad memory
updates.
7. Shared Memory Residency
To allow resident segment locking:
a. Set the kernel paramenter:
SHM_LOCK_OK 1
b. Set the ONCONFIG parameter:
RESIDENT 1
8. Simple Password Communications Support Module
The name of the IBM Informix shared library for Simple Password CSM
on DYNIX/ptx is libixspw.so.
Known Defects:
=============
NONE.
Defects Fixed in previous Release:
==================================
1. Bug Number: 149257
Short Description:
ON DYNIX/PTX 4.5.1 IF USING TLI TCP CONNECTION ON A NET VP A CONNECTION
HANGS FOREVER.USING TCP ON CPU VP IT WORKS. SHM CONNECTION WORKS ON BOTH.