Ingres Corporation |
2.0 Operating System Support
2.1 Preprocessor and Compiler Support
4.0 Installation Considerations
4.1 RPM Support
4.2 Installing Ingres
4.3 How to Upgrade Using RPM
4.4 Post Installation
4.5 Documentation
4.6 Installing on a System without a C Compiler
4.7 Shared Library Path
4.8 Visual Tools
4.9 Protocols Supported
4.10 Raw Transaction Log Files and Raw Database Locations Not Supported on Linux
4.11 BEA Tuxedo Support
5.0 General Considerations
5.1 Requirements for the Ingres Demonstration Application
This readme contains information specific to Ingres® running under Itanium Linux.
The following operating systems are supported (as of the publishing of this document):
Kernel and glibc requirements:
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.
GCC v3.2 up to v4.2 (GNU Compiler Collection, C)
Disk space requirements are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 90 MB |
DBMS Server with Ingres Net Install | 145 MB |
Full installation plus documentation | 460 MB |
RPM 4.1.1 or later
To install Ingres using the new graphical installation wizard, run the script ingres_install found in the directory created when the saveset is extracted. Alternatively Ingres can be installed using ingres_express_install.sh or rpm directly. For more information, see the Quick Start Guide.
Due to a number of problems observed during upgrade of Ingres RPMs, please consult the instructions in the Linux Getting Started Guide before upgrading.
The only supported method for backing out patches installed against Ingres 2006 is to reinstall the RPM from the base release. Therefore, make sure you keep the RPM used for your most recent install so that a patch can be backed out, if necessary.
Ingres documentation can be installed on Linux systems by installing the documentation RPM file that can be downloaded separately.
This version of Ingres requires that the DBMS server executables be re-linked so that utilities such as CKPDB and ROLLFORWARDDB will function for users other than “ingres”. If a C compiler is present, the server is re-linked at install time. If not, a warning is issued and the install continues as usual. If users other than “ingres” 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 library variable for Itanium Linux is LD_LIBRARY_PATH.
The Visual DBA suite is not included as part of the Ingres 10.0 for Itanium Linux. However, these tools can be deployed on a Windows PC against Itanium Linux.
Note: Versions of VDBA prior to Ingres 2006 require a patch in order to work against this release of Ingres.
TCP/IP Native
Research has shown that raw transaction log files and raw database locations on Linux do not provide performance benefits. To simplify administration, a decision has been made to not support this feature on Linux.
BEA Tuxedo 9.1 is supported with this version of Ingres. Please visit http://www.bea.com.
Eclipse Ingres DTP Plug-in
To connect to Ingres from the Eclipse SDK, you must download and install the following versions of Java Runtime Environment, Eclipse and necessary plug-ins, which you can obtain from the Eclipse Data Tools Project page at http://www.eclipse.org/datatools/.
Component | Version |
---|---|
Java Runtime Environment | 1.5 |
Eclipse Software Development Kit (SDK) | 3.2.1 |
Eclipse Modeling Framework (EMF) | 2.2.2 |
Graphical Editing Framework (GEF) | 3.2.2 |
Data Tools Platform (DTP) | 1.0 |
Ingres DTP plug-in | 1.0.0 |