Ingres Corporation |
2.0 Operating System Support
2.1 Preprocessor and Compiler Support
3.0 System Requirements
3.1 Disk Space Requirements
3.2 Memoryuse User Soft Limit
4.0 Installation Considerations
4.1 Shared Library Path
4.2 Syscheck -v
4.3 Visual Tools
4.4 Protocols Supported
4.5 Ingres/ABF and Fortran
4.6 Operating System Threads
4.7 64-Bit Embedded SQL and Embedded QUEL Fortran Applications
4.8 64-Bit Embedded Forms
4.9 Upgrade from 32-Bit to this Version of Ingres
4.10 Upgrade from Ingres 2.5 64-Bit to Ingres 10.0 on AIX
4.11 Remove Unused Modules in Kernel and Library Memory Before Upgrade
4.12 Configuration of 32-bit Ingres on AIX—Large Address Space Model
This readme contains information specific to Ingres® running under IBM AIX.
This release contains 32-bit and 64-bit support and supersedes earlier 32-bit “rs4.us5” and 64-bit “r64.us5” releases.
Ingres 32-bit and 64-bit for AIX is supported on the following operating systems:
The Ingres product support life cycle policy determines the duration of support for Ingres on these operating systems unless the operating system's manufacturer drops support on a prior date. For the latest information about supported operating systems, visit http://ingres.com/support.
For AIX 5L v5.1, patch level 2 should be applied.
For AIX v5.2, OS patch bos.rte.edit.5.2.0.11 (ptf #U489942) should be applied. Patches to AIX are available to download from the IBM site https://techsupport.services.ibm.com by following the links for UNIX Servers.
To check if a 64-bit kernel is running on AIX, issue the following command as root:
bootinfo –K
If the return from the command is “64”, then a 64-bit kernel is running.
Ingres uses functions from the pthread library (libpthreads) and the reentrant C library (libc_r). Any application using Ingres functions, including existing applications must provide an appropriate runtime environment. C applications should comply with the compiler directives: -qansialias and –D_THREAD_SAFE. Link your application with the reentrant C runtime start-up routine (/lic/crt0_r.o) and the libraries –lc_r and –lpthreads. See the configuration files (such as vac.cfg) in /etc directory for details on stanza xlc_r.
Fortran and COBOL applications should follow their compilers' instructions for creating applications that exploit pthreads.
Micro Focus COBOL clients should follow their compiler's directions for using native AIX threads.
The 64-bit Ingres library must be used to build 64-bit user applications (located in $II_SYSTEM/ingres/lib/lp64). The -q64 flag must also be specified as a compiler option.
Ingres on IBM AIX has the following disk space requirements:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 129 MB |
DBMS Server with Ingres Net Install | 214 MB |
Full installation | 267 MB |
On AIX, the soft limit for memoryuse defaults to 32,768 KB. It is necessary to increase this setting to unlimited by adding an entry of “rss = -1” for ingres user in /etc/security/limits file.
The library variable for IBM AIX 64-bit is LIBPATH.
Examples:
For C shell:
$ setenv LIBPATH "/lib:/usr/ccs/lib:$II_SYSTEM/ingres/lib:$LIBPATH"
For Bourne shell:
% LIBPATH=/lib:/usr/ccs/lib:$II_SYSTEM/ingres/lib:$LIBPATH % export LIBPATH
A user can see file descriptor information by using: syscheck -v. Use the following descriptions to interpret the output:
System Hard Limit—The absolute maximum number of open file descriptors that the operating system will permit. On AIX, this value is 2,147,483,647.
System Soft Limit—The maximum number of open file descriptors that a user session could conceivably get, depending on how many open files other processes have at that point in time. This value is 32,767.
The Visual DBA suite is not included as part of the Ingres 10.0 for AIX. However, these tools can be deployed on a Windows PC against an Ingres installation on AIX.
Note: Versions of VDBA prior to Ingres 2006 require a patch in order to work against this release of Ingres.
TCP/IP Native
To build ABF/Fortran applications, add the Fortran libraries to “abflnk.opt” and “abfdyn.opt.” The “abflnk.opt” and “abfdyn.opt” files are located in the $II_SYSTEM/ingres/files directory.
If you develop some applications which use Fortran procedures and some which do not, you can eliminate the Fortran libraries from the *.opt files and create a new option file with just the Fortran libraries. Then define the environment variable ING_ABFOPT1 to point to the new option file. If you are already using this environment variable to point to an option file which includes your own user libraries, you can add the Fortran libraries to your existing files. The benefit of this method is that you will not link in the Fortran libraries if you are not using Fortran procedures. Note also, for applications that are linked with the shared Fortran system library (default), you must include the location of that library in the search path defined by the environment variable LIBPATH.
Ingres on AIX exploits Operating System (POSIX) threads.
By default, the Fortran preprocessors esqlf and eqf generate 32-bit source files. If you need to build 64-bit applications, specify the option "-g64". For example:
esqlf -g64 payroll.sf
64-bit ABF and Embedded FRS application are not supported with this release.
This version of Ingres gives you the choice to install the 32-bit or 64-bit version. If the 64-bit components are selected for installation, prior 32-bit Ingres versions will be upgraded to the 64-bit version of Ingres. For more information on upgrading an Ingres instance, see the Migration Guide.
Ingres 2.5 64-bit can only run on AIX 4.3.x. Therefore, unload/reload procedures for the Ingres databases must be performed prior to upgrading to this version of Ingres. For more information, see the Migration Guide.
Before running ingbuild in an upgrade installation, run the /usr/sbin/slibclean command as root. This removes any unused object files from the kernel and library memory and allows the old shared library files to be overwritten.
To run 32-bit Ingres on AIX, additional parameters can be set on AIX so that Ingres will properly handle the large space requirement that is beyond the operating system default.
Address Space in 32-bit iimerge
In the Ingres 10.0 distribution, the 32-bit iimerge is able to address the data space up to 4 segments of 250 MB each. However, this setting may need to be changed in some installations. IBM provides the –bmaxdata parameter to configure the data space. For details, refer to the IBM documentation for Large Program Support in General Programming Concepts: Writing and Debugging Programs.
The recommended data segment number is in the range of 1 to 6.
To configure setting for iilink
Select the DBMS component, and then Configure.
Locate the row for image_data_segments.
Use the Edit function to set the segment number.
iilink
If it is not possible to re-link the iimerge executable, as an alternative, you can modify the iimerge binary by using ldedit, or change the setting at runtime.
To modify the iimerge binary by using ldedit command
Example to set 5 data segments:
/usr/ccs/bin/ldedit –bmaxdata:0x50000000 $II_SYSTEM/ingres/bin/iimerge
To change the setting at runtime
LDR_CNTRL to 'MAXDATA=0x50000000'
Doing so increases the addressing space during the load time. It is equivalent to entering 5 as the number of image data segments in CBF, which is used during the link time.
Note: The value 0x50000000 is used as an example only.
Note the settings for the following AIX environment variables or system parameters: