Ingres Corporation |
2.0 Operating System Support
2.1 Preprocessor and Compiler Support
3.0 System Requirements
3.1 Disk Space Requirements
4.0 Installation Considerations
4.1 RPM Support
4.2 Documentation
4.3 Mounting the CD-ROM
4.4 Installing on a System Without a C Compiler
4.5 Visual Tools
4.6 Web Server Support
4.7 Protocols Supported
4.8 Raw Transaction Log Files and Raw Database Locations Not Supported on 32-bit Linux
4.9 BEA Tuxedo Support
This readme contains information specific to Ingres® running under 32-bit Linux.
The following operating systems are supported (as of the publishing of this document):
32-bit Linux Kernel 2.4 with glibc 2.2 or 2.3 C-language libraries
32-bit Linux Kernel 2.6 with glibc 2.3 C-language libraries
Ingres supports these operating systems for the duration of their life cycle (as determined by the operating system's manufacturer or until Ingres Corporation announces that it is dropping support). For the latest information about supported operating systems, visit http://www.ingres.com/support.
GCC 3.2.3 to 3.4.3 (C, C++, Fortran, and Ada)
Micro Focus Server Express 4.0 SP1
These are the 32-bit Linux specific requirements for installing Ingres. For more generic system requirements see the Getting Started guide
Disk space requirements are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 68 MB |
DBMS Server with Ingres Net Install | 180 MB |
Full installation plus documentation | 284 MB |
As of the time this readme was published, the installation of Ingres requires RPM with a version in the range 3.0.6 through 4.2.2, except for RPM version 4.1. If RPM 4.1 is installed, it must be upgraded to version 4.1.1 or higher before you can install Ingres.
RPM 4.1 fails to set environment variable RPM_INSTALL_PREFIX. Attempting to install Ingres with RPM 4.1 will lead to numerous "cannot find file" errors, and a failed install. For further details of this RPM bug, see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75057.
On RedHat Linux, the rpmbuild package is required to rename ingres packages using the iirpmrename utility.
Note: When installing multiple Ingres RPM packages, it is important that you install the "ingres2006" (core) package before any other package. In the case where multiple packages are being installed with the same RPM command, make sure the "ingres2006" package appears on the command line first, before any other packages. Failure to do so can cause the installation to complete incorrectly or even fail completely.
These instructions allow you to upgrade any Ingres r3 release prior to Ingres r3 3.0.2 (any.lnx/116) using RPM and avoid Problem INGINS300 and Problem INGINS331. These instructions are to be used in addition to the Ingres Migration Guide.
Upgrading Ingres r3 3.0.1 (int.rpl/103) using rpm -Uvh will result in the uninstall scripts being run after the upgrade has completed. While this will not remove any data or configuration files it may render parts of the installation inoperable. (e.g. iigcc, iijdbc etc.) The .ingIIbash setup scripts under ~ingres may also be removed.
Upgrading an RPM installation which has been installed in a location other than the default can result in all installed file being removed (not DB's or generated config). This is caused by a bug in RPM version 4.1.1.
Note: The following procedure uses Ingres r3 3.0.1 (int.rpl/103) as the version being upgraded, but the procedure is similar for upgrading all versions prior to Ingres r3 3.0.2 (any.lnx/116).
Upgrading Ingres r3 3.0.1 (int.rpl/103) RPMs
rpm -qa | grep ca-ingres | grep 103
All packages must be upgraded at once. Any attempt to perform an upgrade on a single or smaller group of packages will fail.
For default installation location:
rpm -ivh --replacefile --replacepkgs \
complete list of RPM files to be installed
Any other installation location:
rpm -ivh --replacefiles --replacepkgs --prefix <II_SYSTEM> \
complete list of RPM files to be installed
rpm -qa | grep ca-ingres | grep 103
Then, if the list returned is okay, remove them:
rpm -qa | grep ca-ingres | grep 103 | xargs rpm -e --justdb
Note: If you tried using rpm -Uvh instead of the instructions above, binary and other installed files (for example, iimerge) may be removed when rpm -Uvh is used with --prefix to upgrade an installation. Should this occur, simply re-run the same command using the additional flags --replacefiles and --replacepkgs, and all the missing files will be replaced. Database or configuration files will not be affected.
Ingres documentation can be installed on Linux systems by installing the documentation rpm file supplied with the distribution.
Most 32-bit Linux distributions automatically mount the CD-ROM as soon as it is placed in the drive. If the CD-ROM is mounted, running the command "mount" will return an entry for /dev/cdrom.
If the CD-ROM is not mounted then it can be done manually. In general, the CD-ROM should be mounted to either /mnt/cdrom or /media/cdrom, depending on the distribution. The following example shows how to mount the CD-ROM on a RedHat 32-bit Linux system.
As root execute this command:
mount /dev/cdrom /mnt/cdrom
This version of Ingres requires that the DBMS server executables be re-linked for utilities such as CKPDB and ROLLFORWARDDB to function for users other than the instance owner. If a C compiler is present, the server will be re-linked at install time. If not, a warning will be issued and the install will continue as usual. If users other than the instance owner require the use of these utilities, the DBMS server must be re-linked by hand with the following command:
iilink -noudts
A C compiler must be installed for this command to complete successfully.
The Visual DBA suite is not included as part of the Ingres r3 Open Source for 32-bit Linux. However, these tools can be deployed on a Windows PC against 32-bit Linux.
Ingres for 32-bit Linux supports the following web server:
Apache HTTP server version 1.3
TCP/IP Native
Research has shown that raw transaction log files and raw database locations on 32-bit Linux do not provide performance benefits. To simplify administration, this feature is not supported on Ingres 2006 for 32-bit Linux.
BEA Tuxedo 8.1 is supported with this version of Ingres. Please visit http://www.bea.com for more information.