Ingres Corporation

Ingres® 10.0 for HP-UX on PA-RISC (hp2.us5)


1.0 Welcome

2.0 Operating System Support
2.1 Preprocessor and Compiler Support

3.0 System Requirements
3.1 Semaphores and Shared Memory

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 Using hpterm with Ingres
4.8 64-Bit Embedded SQL and Embedded QUEL Fortran Applications
4.9 64-Bit Embedded Forms
4.10 Upgrade from 32-Bit to 64-Bit Versions of Ingres


1.0 Welcome

This readme contains information specific to Ingres® running under HP-UX for PA-RISC.


2.0 Operating System Support

This release contains 32-bit and 64-bit support and supersedes earlier 32-bit "hpb.us5" and 64-bit "hp2.us5" releases.

Ingres 32-bit and 64-bit for HP-UX is supported on the following operating systems.

HP-UX 11iv1 for PA-RISC

HP-UX 11iv2 for PA-RISC

HP-UX 11iv3 for PA-RISC

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 HP-UX for PA-RISC, issue the following command:

getconf KERNEL_BITS

If the return from the command is "64", then a 64-bit kernel is running.


2.1 Preprocessor and Compiler Support

HP C/ANSI C version B.11.31.01

HP aC++ version A.03.77

HP FORTRAN 90 V3.1.3

Object COBOL/UX for HP-UX 11.0

Micro Focus Server Express 4.0 SP2

If your machine does not have a version of the c89 compiler, you must change c89 to cc in the iisysdep file (located in $II_SYSTEM/ingres/utility). The modified line should be changed from CC=c89 to CC=cc.

The 64-bit Ingres library must be used to build 64-bit user applications (located in $II_SYSTEM/ingres/lib/lp64). The +DD64 flag must also be specified as a compiler option.


3.0 System Requirements

Disk space requirements are as follows:

System Configuration Space Required
Client Only (Ingres Net) Install 95 MB
DBMS Server with Ingres Net Install 250 MB
Full installation plus Documentation 530 MB


3.1 Semaphores and Shared Memory

Ingres requires semaphores and shared memory to be loaded. You can do so by configuring shared memory and semaphore settings through the HP System Administration Manager tool, SAM, in the Kernel Configuration section. The following is an example of values you should have set:

sema=1

semmap=66

semmni=100

semmns=1000

semmnu=30

semume=10

semvmx=32767

semaem=16384

shmem=1

shmmax=512000000

shmmni=100

shmseg=10

Important! The shmmax value has increased from previous versions.

Notes:


4.0 Installation Considerations


4.1 Shared Library Path

The library variable for HP-UX is SHLIB_PATH. In addition, for 64-bit installations, LD_LIBRARY_PATH 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 HP-UX for PA-RISC, 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 HP-UX. However, these tools can be deployed on a Windows PC against an Ingres installation on HP-UX.

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


4.4 Protocols Supported

TCP/IP Native


4.5 Operating System Threads

Ingres on HP-UX for PA-RISC exploits Operating System threads.


4.6 64-Bit File Support

To utilize 64-bit file support, your file system must support large files. The 'fsadm' utility allows you to change a file system back and forth between large files and no large files. The conversion of these file systems must be done on an unmounted file system. For example:

/usr/sbin/fsadm -F hfs -o largefiles /dev/vg02/lvol1


4.7 Using hpterm with Ingres

The hpterm is a HP supplied terminal emulator for the X Window system. It provides Term0 emulation for programs that cannot use the window system directly. When running some of the Ingres front-end programs through hpterm, you may notice that the lines drawn on the screen do not look right. To solve this problem, you need to use an alternate font with the hpterm. For example, invoke hpterm as follows:

$ hpterm –fn hp8.8x16 –fb line.8x16

Here we have specified "line.8x16" as the font to be used when displaying alternate text (line drawing characters). See hpterm(1) for further details. This solution will always work, but puts restrictions on the font size that you can use, as "line.8x16" is the largest line-drawing font supplied by HP.


4.8 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.9 64-Bit Embedded Forms

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


4.10 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.