Ingres Corporation |
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 ODBC
4.5 User-defined Data Types
4.6 Protocols Supported
5.0 Other Platform Specific Installation Considerations
5.1 Operating System Threads
This readme contains information specific to Ingres® running under SCO UnixWare.
The following operating systems are supported (as of the publishing of this document):
SCO UnixWare 7.1.4
SCO OpenServer 6
Ingres for UnixWare requires that the target system for the installation be at development kit (UDK) of 8.0. If your target system is not at this UDK level then you can download the kit free from: http://www.sco.com/download.
At the time of this writing, this kit is located as follows: When in the SCO Download Center, choose the SCO Product Download link. You are presented a list of available packages for download. Choose the UnixWare and OpenServer Development Kit Feature Supplement 7.1.1b. The list is in alphabetical order so you will have to scroll down to find the feature supplement.
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.
Optimizing C Compilation System (CCS) 4.1 (native)
C++ gcc compiler version 2.95.3pl1
Micro Focus Server Express COBOL 4.0 SP2
These are the UnixWare specific requirements for installing Ingres. For more generic system requirements see the Getting Started guide
Disk space requirements are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 47 MB |
DBMS Server with Ingres Net Install | 121 MB |
Full installation plus documentation | 580 MB |
Ingres requires semaphores and shared memory to be loaded. To ensure that Ingres has sufficient resources, modify the appropriate system parameters with the idtune utility. The following is an example of the statements you should use:
idtune –m SEMMNI (auto-tuned – see note)
idtune –m SEMMSL 50
idtune –m SEMOPM 10
idtune –m SEMUME 10
idtune –m SEMVMX 32767
idtune –m SEMAEM 16384
idtune –m SHMMAX 512000000
idtune –m SHMMIN 1
idtune –m SHMMNI 100
idtune –m SEMSEG 10
Important! The SHMMAX value has increased from previous versions
Notes:
The library variable is LD_LIBRARY_PATH.
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 UnixWare, this value is 2048.
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 2048 because Ingres uses SETRLIMIT() to extend the default value of 64.
The Visual DBA suite is not included as part of Ingres 9.3 for UnixWare. However, these tools can be deployed on a Windows PC against an Ingres installation on UnixWare.
Note: Versions of VDBA prior to Ingres 2006 require a patch in order to work against this release of Ingres.
Ingres on UnixWare supports the following version of ODBC:
unixODBC version 2.2.12
If you are using Ingres User-defined data types (UDTs) and the C-shell (/bin/csh), you must define the SHELL environment as "/bin/sh".
$ setenv SHELL /bin/sh
TCP/IP Native
Ingres on UnixWare exploits Operating System threads.