================================= MACHINE SPECIFIC NOTES FOR INFORMIX Dynamic Server 7.31.FD2 PRODUCT RELEASE DATE: 29 Aug 2001 ================================= INFORMIX Dynamic Server Shared Memory and Kernel Parameters: ================================================================== SHMMAX: 2147483648 (2 GB) SHMMIN: 1 SHMALL: Not Applicable SHMMNI: 4096 SHMSEG: Not Applicable SHMBRK: Not Applicable MAXMEM: Not Applicable SEMMNI: Not Applicable SEMMNS: Not Applicable SEMMSL: Not Applicable NFILES: Not Applicable LOCATION OF SHARED MEMORY: ========================= The ONCONFIG variable SHMBASE should be set to the following SHMBASE 0x700000000000000L Machine Specific Notes: ======================= 1. This release is a 64-bit version of Informix Dynamic Server product. In order to migrate to this version from previous 32-bit versions of server (32-bit Versions 5.x,7.2x,7.3x), please follow the migration process described in the INFORMIX Migration Guide for Informix Dynamic Server 7.3. In order to revert back to 7.30.FC no explicit reversion is needed. In order to revert back to any other version of INFORMIX Server, users will have to export their existing databases on this version of INFORMIX Dynamic Server using dbexport and import the databases to the required INFORMIX Dynamic Server version using dbimport. Please refer to INFORMIX Dynamic Server Administrator's Guide (Volume 2) for more information on dbexport and dbimport. 2. The product was built on AIX 4.3.2. The following OS patches are REQUIRED: a) Apar number IX84385 (Informix Bug 102304) b) Apar number IX84126 (Informix Bug 101046) c) Apar number IY01759 (Informix Bug 104662) Contact IBM service to obtain these OS patches. 3. The Informix 7.31 Servers and Connectivity(SCT) products require that the drivers for a) Portable Streams Environment (PSE) and b) Asynchronous IO (AIO) be loaded on the AIX system on which the Informix 7.31 SCT products are used. The Informix 7.31 SCT executables use entry points defined by these drivers. Portable Streams Environment (PSE) can be loaded using /usr/sbin/strload command and Asynchronous IO (AIO) device can be enabled (loaded) using either the 'smit' interface or using the two commands /usr/sbin/chdev -l aio0 -a autoconfig="available" /usr/sbin/mkdev -l aio0 For further information consult AIX documentation. 4. Kernel AIO(KAIO) is supported in this release. There are two possible scenarios: (a) OS patch with apar no IX84126 is installed - This is the ideal case. This uses the signal mechanism for KAIO and it is the preferred mechanism. (b) OS patch with apar no IX84126 is NOT installed - This may be due to the condition that the patch is not available (Contact IBM Support). In this scenario it is REQUIRED to set a environment variable IFMX_AIXKAIO_POLLING before bringing up the engine. This uses the polling mechanism for KAIO. The performance of the engine with the polling mechanism for KAIO is lower than the performance of the engine with the signal mechanism for KAIO. If the OS patch is not present and, if the environment variable IFMX_AIXKAIO_POLLING is not set, the server currently hangs (informix bug 105805). For either of the scenarios mentioned above KAIO uses a new environment variable, named IFMX_AIXKAIO_NUM_REQ for its operation. This environment variable was introduced as a fix for the bug 101043. The environment variable is explained below. IFMX_AIXKAIO_NUM_REQ - The value assigned to this environment variable defines the number of aio control blocks to be used by KAIO. The valid values, range from 512 to 4096. The default value for this parameter is 1024. For more information contact Informix Technical Support. 5. The UNIX graphical tools provided with this release requires X Windows System X11R5 and Motif Version 1.2.3 or later runtime libraries. 6. The following protocol(s)/interface(s) are supported for this platform: a. Berkeley sockets using TCP/IP To use TCP/IP, the NETTYPE in the ONCONFIG file and the nettype field in the sqlhosts file entry must be set to "onsoctcp". b. IPC using stream pipe (Implemented using Unix Domain Sockets) To use IPC with stream pipe, the NETTYPE in the ONCONFIG file and the nettype field in the sqlhosts file entry must be set to "onipcstr". c. To use IPC with shared memory, the NETTYPE in the ONCONFIG file and the nettype field in the sqlhosts file entry must be set to "onipcshm". 7. OnArchive tape drives/tape drivers: OnArchive has been tested and is supported on this platform only with 8mm tape drives. The tape device needs to be configured to have block size of 512 and to use extended file marks. OnArchive MAX_SPACE qualifier should be set to a minimum value of 256 on this platform. 8. TERMINFO is supported in this release. 9. Some operating systems lower the priority of processes as the processes age. NOAGE (ONCONFIG variable) which controls priority aging is supported on this platform. a) If NOAGE is set to 1, the CPU VPs are set to a fixed default priority of 65. b) To override the default priority value for CPU VP class, set the following environment variable (as shown below for sh/ksh) in the range of 50 to 90. The recommended range of priority value is 60 to 90. For example, to set CPU VP priority to 60, set: export INFX_CPUVP_PRIORITY=60 The server checks and sets the CPU VP process to the defined priority if the defined value is within the above range. 10. C2 Operating System Audit is supported in this release. This section gives the necessary configuration changes to the OS audit subsystem in order for Informix-OnLine audit events to be recorded in the system audit log. a. The OS audit subsystem must be operational, and auditing enabled. b. The auditing must be configured for binary or stream mode. c. A new event INFORMIX_DBMS must be introduced to the audit subsystem. d. INFORMIX_DBMS event must be added in a relevant class definition. To receive Informix-OnLine audit data, the operating system audit subsystem must be configured to accept events of the type INFORMIX_DBMS. The event type INFORMIX_DBMS must be introduced to the OS, by inserting a line defining this event in the file /etc/security/audit/events. (Please pay careful attention to the format, even of the comments, because they are parsed by the auditselect and perhaps by other audit library functions at runtime.) Lines extracted from /etc/security/audit/events: * INFORMIX audit events INFORMIX_DBMS = printf "%s" Lines extracted from /etc/security/audit/config: classes: infx = INFORMIX_DBMS users: root = infx Important files in configuring OS audit subsystem: events, config, bincmds, streamcmds After configuring the system, enable auditing with the new configuration. Refer to the Operating system documentation on how to accomplish this. The OS auditing must be enabled for all users that might use the OnLine product, and for the event type INFORMIX_DBMS, of the relevant class. Please see the man pages for "audit", "auditpr", "auditselect", and other related commands for details on configuring auditing on the system. To select which INFORMIX-OnLine events are to be audited, specify audit masks using the "onaudit" utility. Refer to the INFORMIX-OnLine Trusted Facility Manual (TFM) for further details. To extract audit records from operating system audit trail files, "auditselect" and "auditpr" utilities can be used. To extract INFORMIX Dynamic Server records use "onshowaudit -O" which is configured to use /audit/trail by default. If the system is configured to use a different audit file, use "onshowaudit" utility with -f option to specify the required audit file. For example, to use /etc/security/audit/trail file, specify: onshowaudit -O -f "/etc/security/audit/trail" 11. OnSNMP is supported on this platform: For AIX, OnSNMP is based on PEER Network's Subagent Development Kit release 2.3. The distribution includes the following under $INFORMIXDIR: bin/onsnmp the OnSNMP subagent. bin/onsrvapd the daemon which spawns a subagent for each server it discovers. etc/*V1.mib etc/*V2.mib etc/*.my 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; files with the 'my' extention are transitional that may be used as a last resort. Follow these steps to configure the Vendor Master Agent 1) Modify the file /etc/snmpd.peers to allow the OnSNMP subagent executable 'onsnmp' to register as a peer: "onsnmp" 0.0 "" 2. Modify the file /etc/snmpd.conf and add smux 0.0 "" Refer to the installation notes that accompany the master agent and network manager for more details. Note: OnSNMP is supported only on single engine per host in this release. If multiple engines are running on the same host, the values returned by the subagent are only for the first engine, and all subagents for the subsequent engines will fail to start. 12. Enterprise Replication (ER) is supported in this release. 13. High Performance Loader (HPL) is supported on this platform. The HPL utilities onpload and ipload require a minimum of 35MB of memory and 70MB of swap space in order to run. User-defined conversion routines must be provided in a dynamic, 64-bit shared library called ipldd07a_64.so. This library must be located in /usr/lib (or must have a link provided in /usr/lib). Information on how to create a 64-bit shared library - The environment variable OBJECT_MODE=64 can be used 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 a 64-bit object is to be generated. The shared object can be created from the 64-bit object files by using the ld command ld -b64 -bE: <64-bit_object_files> -o ipload require X Windows System X11R5 and Motif 1.2.3 or greator runtime libraries. 14. In this release, ipload can connect to Informix Dynamic server only using TCP/IP sockets protocol. For ipload to connect to IDS server using shared memory (ipcshm) protocol, please ensure the following: a. The onconfig parameter DBSERVERALIASES includes a server name which has its NETTYPE as soctcp. b. Whenever ipload is used, environment variable INFORMIXSERVER should be set to the server name with the soctcp NETTYPE. Please refer to INFORMIX Dynamic Server Administrator's Guide for more information regarding DBSERVERALIASES parameter and the INFORMIXSERVER environment variable. 15. This product supports the Informix Large Memory Addressability (LMA) feature. Informix LMA provides the ability to support system configurations with greater than 4GB of RAM. Most UNIX systems are limited to at most 4GB of RAM based on the memory addressing limitations of 32-bit architectures. The following ONCONFIG parameters will be affected by LMA. The maximum number of BUFFERS supported is 536870912 The maximum number of LRU queues has been increased from 128 to 512. The Buffer pool is allocated in a separate set of shared memory segments (instead of putting all the buffers in the resident and virtual memory segments). The DS_TOTAL_MEMORY, which is the total memory available for decision support memory is only limited by amount of virtual memory available. The sort memory comes out of the DS_TOTAL_MEMORY memory and hence there is not explict limit on the amount of sort memory. The read ahead parameter RA_PAGES is only limited by BUFFERS and therefore can be any value less than 536870912. The "chunk" write algorithm is not dependent on the amount of buffers/shared memory and can write as many pages in a single I/O as possible. The maximum chunk size is still limited at 2 GB. The maximum size of a single shared memory segment is 2 GB. But the total shared memory assigned to a server can be larger. 16. Informix Enterprise Command Center (IECC) support * IECC ServerAgent 3.01.UC1 is supported for this release on this platform. * The IECC ServerAgent High Availability Feature(HA) is NOT supported for 64bit Servers. Effects of not having HA support: Without HA, every IECC client connection which is trying to access a Dynamic Server which is offline, will realize that it cannot connect to the server after a timeout of 30 seconds. With HA, this will be very fast, as the admagent can get the information of the server state by attaching directly to a shared memory segment. If logical logs become full on the database server, all existing and incoming IECC client connections will hang until logs are backed up. With HA, admagent can determine whether logs are backed up by attaching to shared memory segment, and then it can prevent further IECC client connections to the server, until the logs are backed up. Users using IECC to administor 64-bit Dynamic Servers are advised to customize their Logical Log Alerts to a suitable threshhold value and perform logical log backups as and when the alerts occur. This will prevent the situation of logical logs becoming full. In the case the logs become full and IECC clients hang, please refer to server message log. See if the logs are full and issue "ontape -a" to backup the logical logs. * For more information please refer to IECC Users Guide and the IECC Client Release Notes. 17. In this release, the INFORMIX Tools(for e.g. isql, c4gl, rds) and 32-bit ESQL/C applications can connect to this Informix Dynamic server only using soctcp protocol. 18. Communications Support Service using Communications Support Module (CSM) with - Simple-Password is supported in this release. The CSM library is called ispws07a.so. - DCE-GSS CSM is NOT supported in this release. Due to the common naming library convention of CSM client and Server libraries, there is a known issue (Informix bugs 103708 and 107052) which prevents co-existence of a 32bit Client and 64bit server in the same installation location (same INFORMIXDIR). If you wish to use CSM and would like to use 32bit client with 64bit servers, then please following EITHER of the specified workarounds to avoid the problem 1) Install 32bit client and 64bit server in DIFFERENT locations i.e different INFORMIXDIR OR 2) If you wish to install 32bit client and 64bit server in the SAME location, then please note the following configuration changes.. You need to use DIFFERENT concsm.cfg files for Client and Server. You can achieve this by setting INFORMIXCONCSMCFG enviroment variable to different files based on whether it is a client or a server environment. (Refer to Section 4-14 of Administrator's Guide for Informix Dynamic Server Version 7.3, for details on how to configure and use CSM) Server concsm.cfg should have the following entry For Simple-Password CSM: SPWDCSM ("/usr/informix/lib/csm/ispws07a.so", "", "") Client concsm.cfg should have the following entry For Simple-Password CSM: SPWDCSM ("/usr/informix/lib/csm/ispws09a.so", "", "") Please note that this problem is specific to ClientSDK 2.20.x and IDS 7.31.x combination and ONLY applicable if CSM is used and co-existence of 32bit Client and 64bit server in the same installation location is desired. This will be fixed in future releases. 19. The name of the 64-bit Informix Shared optical library on AIX is iosm07a_64.so. 20. The Processor Affinity feature (ON_CONFIG variables AFF_SPROC, AFF_NPROCS) that allows the pinning of CPU VPs to physical processors in a multi-cpu configuration is not supported in this release. As an alternative, on AIX 4.3.2, the bindprocessor command can be used to bind the specific CPU VP to a processor on IBM SMP platforms. The process id for CPU VPs can be obtained using 'onstat -g sch' command. bindprocessor pid processornum where processornum is 0,1, ... n (display with "bindprocessor -q") 21. The OnPerf performance monitoring capability is not supported on this platform. 22. The DB/Cockpit DBA monitoring tool is not supported in this release. 23. Shared Memory Residency feature is not supported on this platform. 24. The new protocol used for supporting MaxConnect is onsocimc. For more information on how to configure your server to use with MaxConnect, please refer to the following documents: Guide to Informix MaxConnect Ver 1.0. 7.31 Server Release Notes. 25. The Online Backup and Restore Utility(ONBAR) is available with this release. ON-bar uses the XBSA interface. Some of the functions called by ON-Bar are in a shared library supplied by third party storage management vendors. For ON-Bar to access the functions, the library has to be installed in one of the three ways noted below: 1. Rename the library to /usr/lib/ibsad001_64.so 2. Create /usr/lib/ibsad001_64.so as a symbolic link to the library. 3. Set the BAR_BSALIB_PATH parameter in $INFORMIXDIR/etc/$ONCONFIG to the full pathname of the library. ON-Bar requires that the storage manager insert a row into the bar_version table of the sysutils database which describes the compatibility of a particular storage manager's shared library with the ON-Bar version. Only the storage management vendors have this information. If ON-bar returns 0x8c (139 decimal) to its caller or displays the message: ERROR: Version of XBSA shared library is not compatible with version of On-BAR. in the ON-Bar activity log, then select the contents of the bar_version table and consult your storage manager documentation or contact your storage management vendor. The following is the content of bar_version table: ||| where is the version of the 7.3 ON-Bar, is the release version of the XBSA shared library, is the name of this Storage Manager, is the version of the Storage Manager application. To load a storage manager version, first edit the file $INFORMIXDIR/etc/sm_versions (create if it does not exit) and enter a line giving the ON-bar version, the XBSA version, the Storage Manager name and the Storage Manager version. For example, 1|1.0.1|ism|ISM.2.20.UC1.114| Load the values into the bar_version table by running the following script as user 'informix': dbaccess sysutils - << EOF load from '$INFORMIXDIR/etc/sm_versions' insert into bar_version; EOF Run onbar -b -L0 and check your online and onbar log files as defined in onconfig to see the following messages: Level 0 Archive started on rootdbs Archive on rootdbs Completed. If there is no parameter BAR_ACT_LOG defined in the onconfig file, then onbar writes its log to /tmp/bar_act.log file. 26. Informix Storage Manager (ISM) is supported in this release. The devices that are currently supported are Type Model Capacity (GB) Firmware 4mm --- ADIC: DAT 2000a 2 rev 6.09 DAT 8000a 4-8 rev 7.09 DAT 8008 4-8 DAT 8024 12-24 Andataco: ENC-4200S 2-4 rev T503 ENC-4400S 4-8 rev 9401 Box Hill: DTH4 4-8 Compaq: 2/8 GB DAT 2-4 rev. 1211 4/8 GB DAT 4-8 rev. 4ao, 0316 DEC StorageWorks: TLZ07 4-8 rev. 491A, 553A TLZ09 4-8 rev. 0172 TLZ10 12-24 Hewlett-Packard: 35470A (JetStore 2000) 2 rev. 6.09 35480A (JetStore 5000) 2-4 rev. 7.09 C1520A/E, C1525A, C2224B/C 2 rev. 6.09 C1521A/E, C1526A, C2225A/B 2-4 rev. 7.09 C1528A, C1529A (SureStore DAT8i 8e) 4-8 rev. 9401 C1533A (SureStore 6000) 4-8 rev. 9401 C1520G/H, C1525G/H, C1534 (SureStore 2000i/e) 2 rev. T503 C1521 G/H, C1523 G/H, C1536 (SureStore 5000i/e) 2-4 rev. T503 C1555D, C1556D, C5653C (SureStore DAT24) 12-24 C1528A, C1529A (SureStore DAT8 i/e) 4-8 rev. 9401 C1537A 12-24 C1538 2-4 C1539 4-8 Seagate Tape: Python 43x0 2 rev. 2.26, 2.50 Python 43x2 2-4 rev. 3.58, 3.59-1 Python 43x4 2-4 rev. 3.58 CTD-4000 2-4 CTD-8000 4-8 Scorpion 2(STD22000N, STD62000N) 2 Scorpion 4(STD24000N, STD64000N) 2-4 Scorpion 8(STD28000N, STD68000N) 4-8 Sony: SDT5000 4-8 rev. 3.26 SDT5200 4 rev. 3.02 SDT7000 4-8 rev. 0148 SDT9000 12-24 SDT10000 Storage Dimensions: DDS-2 Tape Backup 4-8 rev. 9401 WangDAT: 3100 2 rev. 1.1 3200 2-4 rev. 1.1 3400DX 4-8 rev. 1.10 8mm EXB ------- Andataco: ENC 8505XLS 7-14 rev. 06S1 Box Hill: CT5 5-10 CT7 7-14 Exabyte: 8505XL 7-14 rev. 06S1 * 8900 Mammoth 20-40 rev. 21C Eliant 820 7-14 rev. 63 Hitachi: MT8M1 20-40 IBM: 8mm 8505 5 rev. 6S0A Storage Dimensions: 8mm Tape Backup 5 rev. 06M0 8mm AIT-1 --------- Sony AIT SDX-300, SDX-300C 25-50 rev. 0300 Cybernatics CY-8000 35-70 3480/3490 --------- IBM: 3480 .2 3490E .8-1.6 Memorex-Telex 5490E 4 .8-1.6 Philips/LMS: TD3610 .8-1.6 StorageTek: 4480 .8-1.6 rev i4.23 4890 .8-1.6 9490 .8-1.6 35x0 Magstar ------------- IBM: 3570 Magstar(B/C00) 5-10 rev. 3245 3590 Magstar(B Model) 10-20 rev. D0l8_1 C0 9840 ----- HP: A5598A 9840 Drive for 20/700 20 A5606A 9840 Tape Drive Assembly for 10/588 StorageTek: 9840 DLT --- ADIC: DS9200 10-20 rev. 9105, 9410 DS9300D 15-30 rev. 8203 DS9400D 20-40 rev. C504 DS9700D 35-70 Andataco: ENC-6001-30S 15-30 rev. 8203 ENC-6001-40S 20-40 rev. C504 Box Hill: DLT3 15-30 DLT4 20-40 Breece Hill: Q1 20-40 Compaq: 10/20 GB DLT 10-20 rev. 9410 15/30 GB DLT 15-30 rev. 8203, A001 Conner (Cipher): MS20DLT T860DLT .86 rev. 10 Digital StorageWorks: TZ87N 10-20 rev. 9514 TZ88 20-40 rev. CA19 TZ89 35-70 Hewlett-Packard: 30e C1549A 15-30 rev. 8203 40e/i/r 20-40 rev. C504, CC37 Quantum: DLT2000 10-20 rev. 9105, 9410 DLT2000XT 15-30 rev. 8203 DLT4000 20-40 rev. C504, CC37 DLT7000 35-70 Storage Dimensions: DLT4000 20-40 rev. CA19 Tandberg: DLT7000 5 35-70 Optical ------- Cybernetics CY-3600 2.6 Hewlett-Packard: Corsair I (C1716C) .6 Corsair II 1300T/C1716T 1.3 Corsair III 2600FX/C1113F 2.6 IBM: Multifunction (M-O Mode Only) 1.3 Maxoptics: T4 2.6 rev. B000 Sony: SMO-541 2.6 rev. 1.09 SD-3 ----- StorageTek: Redwood 50 *AIX does not support 1024 bytes/sector media, the capacities for AIX are 1.2 GB and 2.4 GB (512bytes/sector) 27. Known defect(s) a. PTS 127680 - ARC-E-01576, UNEXPECTED INTERNAL FATAL ERROR HAS OCCURRED WHILE RUNNING LIST/DBSPACESET=* b. PTS 147782 - AIX 64 BIT Stack Trace doesn't work using ONSTAT -G STK or KILL -7. Using onstat -g stk command to dump a stack for a thread or kill -7 to obtain the stack from a running thread doesn't work on AIX 64bit port at least with 7.31.FD1. Actually the program counter seems to be correct, but the stack tracing code has a problem to find the funtion name in the bound symbol table. This is tentatively SCHeduled for the FD3 release.