Ingres Corporation |
2.0 Operating System Support
2.1 Preprocessor and Compiler Support
4.0 Installation Considerations
4.1 Shared Library Path
4.2 Syscheck -v
4.3 Visual Tools
4.4 Protocols Supported
4.5 Operating System Threads
4.6 64-Bit File Support
4.7 64-Bit Embedded SQL and Embedded QUEL Fortran Applications
4.8 64-Bit Embedded Forms
4.9 Upgrade from 32-Bit to 64-Bit Versions of Ingres
This readme contains information specific to Ingres® running under Sun Solaris on AMD Opteron.
Ingres 32-bit and 64-bit for Sun Solaris on x86 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.
To check if a 64-bit kernel is running on Sun Solaris, issue the following command:
isainfo -kv
If the return from the command is "64-bit amd64 kernel modules" then a 64-bit kernel is running.
Sun Studio 10 with additional patches 117837 and 117846
Sun Studio 11
Sun Studio 12
The 64-bit Ingres library must be used to build 64-bit user applications (located in $II_SYSTEM/ingres/lib/lp64).
Disk space requirements for Sun Solaris 64-bit are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 93 MB |
DBMS Server with Ingres Net Install | 241 MB |
Full installation plus Documentation | 525 MB |
The library variable for Sun Solaris is LD_LIBRARY_PATH, which must be set in the user environment to include $II_SYSTEM/ingres/lib. In addition, for 64-bit installations, LD_LIBRARY_PATH_64 must also be set in the user environment to include $II_SYSTEM/ingres/lib/lp64.
You may see a discrepancy between what the C-shell command "limit" returns and what syscheck -v returns for the per-process limit on open file descriptors. This is because Ingres extends its default per-process limit for open file descriptors. The output from syscheck -v is correct. Here is a description of how to interpret the output:
System Hard Limit
This is the absolute maximum number of open file descriptors that the operating system will permit. On Solaris, this value is 1024.
System Soft Limit
This is the maximum number of open file descriptors that Ingres could conceivably get, depending on how many open files other processes have at that point in time. This value is also 1024 because Ingres uses SETRLIMIT() to extend the default value of 64.
The Visual DBA suite is not included as part of the Ingres 10.0 for Solaris. However, these tools can be deployed on a Windows PC against an Ingres installation on Solaris.
Note: Versions of VDBA prior to Ingres 2006 require a patch in order to work against this release of Ingres.
TCP/IP Native
Ingres on Solaris x86 exploits Operating System threads.
To utilize 64-bit file support, your file system must support large files.
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 applications 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.