Ingres Corporation

Ingres® 10.0 for Sun Solaris on SPARC (su9.us5)


1.0 Welcome

2.0 Operating System Support
2.1 Preprocessor and Compiler Support

3.0 System Requirements
3.1 Disk Space Requirements
3.2 Semaphores and Shared Memory

4.0 Installation Considerations
4.1 Shared Library Path
4.2 Syscheck -v
4.3 Visual Tools
4.4 High Availability Support
4.5 Protocols Supported
4.6 BEA Tuxedo Support
4.7 Support for Priority Paging
4.8 Ingres/ABF and Fortran
4.9 64-Bit Embedded SQL and Embedded QUEL Fortran Applications
4.10 64-Bit Embedded Forms
4.11 Upgrade from 32-Bit to 64-Bit Versions of Ingres


1.0 Welcome

This readme contains information specific to Ingres running under Sun Solaris for SPARC.


2.0 Operating System Support

This release contains 32-bit and 64-bit support and supersedes earlier 32-bit “su4.us5” and 64-bit “su9.us5” releases.

Ingres 32-bit and 64-bit for Sun Solaris on SPARC is supported on the following operating systems:

Sun Solaris 8 for SPARC compliant (UltraSPARC or SPARC64)

Sun Solaris 9 for SPARC compliant (UltraSPARC or SPARC64)

Sun Solaris 10 for SPARC compliant (UltraSPARC or SPARC64)

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 we are dropping support). For the latest information about supported operating systems, visit http://www.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 sparcv9 kernel modules," then a 64-bit kernel is running.


2.1 Preprocessor and Compiler Support

Forte Developer 6 update 2

Sun ONE Studio 7 Compiler Collection

Sun ONE Studio 8 Compiler Collection

Sun Studio 9

Sun Studio 10

Sun Studio 11

Sun Studio 12

Micro Focus Server Express 5.0

The 64-bit Ingres library must be used to build 64-bit user applications (located in $II_SYSTEM/ingres/lib/lp64). The 64-bit mode flag must also be specified as a compiler option (-m64 for Sun Studio 12, -xarch=v9 for the previous versions).

Note: The recommended version of the Studio 10 Compiler is REV=2005.01.07 with additional patches 117836 and 117832.


3.0 System Requirements


3.1 Disk Space Requirements

Ingres for Sun Solaris 64-bit has the following disk space requirements:

System Configuration Space Required
Client Only (Ingres Net) Install 130 MB
DBMS Server with Ingres Net Install 524 MB (including a 256 MB log file)


3.2 Semaphores and Shared Memory

Ingres requires semaphores and shared memory to be loaded. You can do so by adding set commands to the /etc/system file. The following is an example of the statements you should add:

forceload: sys/semsys

forceload: sys/shmsys

For Solaris 8

set shmsys:shminfo_shmmin=1

set shmsys:shminfo_shmseg=10

For Solaris 8 and 9

set semsys:seminfo_semmni=100

set semsys:seminfo_semmns=1000

set semsys:seminfo_semmnu=30

set semsys:seminfo_semmsl=50

set semsys:seminfo_semopm=10

set semsys:seminfo_semume=10

set semsys:seminfo_semusz=96

set semsys:seminfo_semvmx=32767

set semsys:seminfo_semaem=16384

set shmsys:shminfo_shmmax=512000000

set shmsys:shminfo_shmmni=100

Notes:


4.0 Installation Considerations


4.1 Shared Library Path

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 be set in the user environment to include $II_SYSTEM/ingres/lib/lp64.


4.2 Syscheck -v

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.


4.3 Visual Tools

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 to work against this release of Ingres.


4.4 High Availability Support

DBMS Server Requirement

When using the Ingres High Availability Option, the Ingres DBMS server is installed and configured as a typical installation, provided that the system files and database files are installed on the cluster file system.

How the Database Probe Function is Configured

A feature of the Solaris Cluster software, the database Probe function allows the Cluster to verify that an application is still working correctly and still accessible.

To determine how the probe script operates, examine the IngresSCAgent/bin/ingres_probe file.

To use the ingres_probe feature you must first create a database with a table that contains the column "cluster_monitor".  The owner of the database and table must also be defined if it does not already exist. The following commands are an example of how to create the necessary database and table.

$ sql iidbdb
* create USER <User> \g
* commit \g\q $ sql <Database> -u<User>
* create table <User>.<Table>( cluster_monitor DATE); \g
* insert into <User>.<Table> (Cluster_monitor ) values(DATE('NOW')); \g
* commit \g\q


4.5 Protocols Supported

TCP/IP Native

SNA LU6.2


4.6 BEA Tuxedo Support

The following versions are supported with this version of Ingres:

BEA Tuxedo 9.1

BEA Tuxedo 10.0

For more information, please visit http://www.bea.com.


4.7 Support for Priority Paging

The algorithm used on Solaris to determine paging priority determines the priority of an in-memory page using the file attributes of the file from which it was paged. Pages from executable files have a higher priority than pages from data files. Prior to release 2.6, Ingres would make all database data files executable, giving them a higher priority in the system cache. This action second-guesses the systems paging algorithm, and may have a detrimental effect on system performance, because executable image pages may be paged out in favor of Ingres data pages. In this release, any newly created Ingres data files will not be executable, allowing the Solaris paging algorithm to treat them as normal data pages when executing its paging algorithm. Pre-existing data file attributes will not be changed, and if the new behavior is desired throughout Ingres, the system administrator will need to run the chmod UNIX command on all existing Ingres data files.


4.8 Ingres/ABF and Fortran

The F77 Fortran libraries required for the F77 compiler have changed locations and some libraries have been deleted for the newer versions of the compiler. Users who have F77 should determine which version of the compiler they are using and verify the location of the required libraries. If you are using Fortran procedures within your Ingres/ABF applications, you must link in the required Fortran libraries. The following is a list of the required libraries for the various F77 versions and additional lines that you should add to your abflnk.opt and abfdyn.opt files. The libraries are located in: /opt/SUNWspro/lib. The abflnk.opt and abfdyn.opt files are located in the $II_SYSTEM/ingres/files directory. Add these lines to abflnk.opt and abfdyn.opt:

-L$II_SYSTEM/ingres/lib -linterp.1 -lframe.1

-lq.1 -lcompat.1 -lcurses -lgen

-L/opt/SUNWspro/lib -lF77 –lm

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 that includes your own user libraries, you can add the Fortran libraries to your existing file. The benefit of this method is that you will not link in the Fortran libraries if you are not using Fortran procedures. For applications linked with the shared Fortran system library (default), you must include the location of that library in the search path that is defined by the environment variable LD_LIBRARY_PATH.


4.9 64-Bit Embedded SQL and Embedded QUEL Fortran Applications

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


4.10 64-Bit Embedded Forms

64-bit ABF and Embedded FRS applications are not supported with this release.


4.11 Upgrade from 32-Bit to 64-Bit Versions of Ingres

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.


Copyright © 2010 Ingres Corporation. All rights reserved.