Ingres Corporation |
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
5.0 Other Platform Specific Installation Considerations
5.1 Operating System Threads
5.2 64-Bit File Support
5.3 Using hpterm with Ingres
This readme contains information specific to Ingres® running under HP-UX ia64 11i.
The following operating systems are supported (as of the publishing of this document):
HP-UX ia-64 11iv2 for HP Itanium
HP-UX ia-64 11iv3 for HP Itanium
Note: For HP ANSI aC++ Compiler version A.05.50 patches PHSS_28970 and PHSS_28971 MUST be installed before installing Ingres. For more information, contact HP support at http://www.hp.com/support.
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.
HP C/ANSI C version A.05.50+
HP ANSI aC++ version A.05.50+
Micro Focus COBOL Server Express 5.0
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.
Disk space requirements are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 108 MB |
DBMS Server with Ingres Net Install | 181 MB |
Full installation plus documentation | 501 MB |
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 HP-UX ia-64 kernel defaults are currently larger than the Ingres requirements, so no change should be necessary. The following is an example of the minimum values you should have set:
sema=1
semmni=100
semmns=1000
semmnu=30
semume=10
semvmx=32767
semaem=16384
shmem=1
shmmax=512000000
shmmni=100
shmseg=10
Notes:
The library variable for HP-UX ia-64 is SHLIB_PATH or LD_LIBRARY_PATH. One must be set in the user environment to include $II_SYSTEM/ingres/lib.
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 ia-64, 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 60.
The Visual DBA suite is not included as part of the Ingres 10.0 for HP-UX ia64. However, these tools can be deployed on a Windows PC against an Ingres installation on HP-UX ia64.
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 HP-UX ia-64 exploits Operating System threads. Ingres internal threads are not supported.
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
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.