Ingres Corporation

Ingres® 10.0 for HP Tru64 UNIX (axp.osf)


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 Syscheck -v
4.2 Shared Library Path
4.3 Visual Tools

5.0 Other Platform Specific Installation Considerations
5.1 Connectivity with Pre-2.6 Ingres for Tru64
5.2 Existing Applications
5.3 Kernel Configuration Parameters
5.4 JDBC Support on Tru64


1.0 Welcome

This readme contains information specific to Ingres® running under HP Tru64 UNIX.


2.0 Operating System Support

Ingres for HP Tru64 UNIX is supported on the following operating systems.

HP Tru64 UNIX 5.1b

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.


2.1 Preprocessor and Compiler Support

Compaq C++ for Tru64 UNIX 6.5

Compaq Fortran for Tru64 UNIX Systems 5.5

Compaq C for Tru64 UNIX 6.5


3.0 System Requirements


3.1 Disk Space Requirements

Ingres for HP Tru64 UNIX requires the following disk space:

System Configuration Space Required
Client only (Ingres Net) 77 MB
DBMS Server with Ingres Net 126 MB
Full installation 196 MB


3.2 Semaphores and Shared Memory

Ingres requires a certain amount of semaphore and shared memory resources. You may need to increase these parameters. Consult your HP Tru64 UNIX documentation or system administrator for details of modifying kernel parameters.

For a typical Ingres instance, the following setting may be suitable:

semmni 1000

semmsl 50

semopm 10

semume 10

semvmx 32767

semaem 16384

shmmax 512000000

shmmin 1

shmmni 100

shmseg 10

Notes:


4.0 Installation Considerations


4.1 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 HP Tru64 UNIX, this value is 4096.

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 4096 because Ingres uses SETRLIMIT() to extend the default value.


4.2 Shared Library Path

The library variable for HP Tru64 UNIX is LD_LIBRARY_PATH.


4.3 Visual Tools

The Visual DBA suite is not included as part of the Ingres 10.0 for HP Tru64 UNIX. However, these tools can be deployed on a Windows PC against an Ingres installation on Tru64 UNIX.

Note: Versions of VDBA prior to Ingres 2006 require a patch to work against this release of Ingres.



5.0 Other Platform Specific Installation Considerations


5.1 Connectivity with Pre-2.6 Ingres for Tru64

Versions of Ingres prior to 2.6 running under HP Tru64 UNIX, which will need to access data stored on an HP Tru64 Ingres 10.0 instance, or visa-versa, must execute the following on both installations of Ingres to allow connectivity to or from the older version:

ingsetenv II_FORCE_HET true

Failure to do so will cause connection to fail with error codes such as E_LC0023 and E_LQ00AF.


5.2 Existing Applications

If you are upgrading a version of Ingres prior to 2.6, and you have applications statically linked with libingres.a, you must either re-link the applications, or use ingsetenv to set II_FORCE_HET to true. Failure to do so will cause applications to fail with error codes such as E_LC0023 and E_LQ00AF.


5.3 Kernel Configuration Parameters

Ingres instances using OS threads that are configured for a very large number of locking and/or logging requirements will allocate a large number of POSIX process shared objects. The HP Tru64 UNIX kernel has an internal hash table used to manage these objects. If the number of POSIX process shared objects required by Ingres is large enough, startup of the Ingres Recovery Server process may take a significant amount of time. This is because of the long overflow chains in this hash table, which slows down POSIX process shared object allocation.

As of HP Tru64 UNIX 5.1b, there is a kernel parameter pshared_hash_size that controls the number of hash buckets allocated by the kernel. If Ingres Recovery Server (dmfrcp) startup performance problems are experienced, then the value of this parameter should be increased. The optimum new value is dependent upon a number of factors; however there is little cost of having a high value. An initial value of 131072 is suggested in this situation.


5.4 JDBC Support on Tru64

The JDBC driver provided in this release requires JRE/JDK version 1.5 for the feature functionality. However, the Java Runtime Environment and SDK currently available on the HP site (http://h18012.www1.hp.com/java/download/index.html ) is Version 1.4.2-8.

In this case, you can do one of the following:

  1. If it is necessary to use the new functionality in the Ingres 10.0 JDBC Driver, contact HP Support to request the JRE/JDK 1.5.

  2. Use the Ingres 9.1.x JDBC driver (version 3.2.x), which continues to work on Tru64. The driver can be downloaded from http://esd.ingres.com.


Copyright © 2010 Ingres Corporation. All rights reserved.