- Installing DB2 UDB Servers
- Before You Begin
- Installing DB2 UDB
- Installed Directory Structure
- Considerations in an NIS Environment
- Distributed Installation
- Sample Response Files
- Creating a Response File
- Distributed Installation with a Response File
- Installing DB2 with db2_install
- DB2 UDB Environment Definitions
- DB2 Profile Registry
- Managing the DB2 Profile Registry
- The db2set Command
- Environment Variables
- Hierarchy of the DB2 UDB Environment
- DB2 Administration Server (DAS)
- DAS Process
- DB2 Instances
- Creating the Sample Database
- Using the Command Line Processor (CLP)
- Uninstalling DB2 Products
- Stopping the DAS Instance
- Stopping All DB2 Instances
- Removing the DAS Instance
- Removing DB2 Instances
- Removing DB2 Products
Before starting the installation of DB2 UDB products, check the hardware and software requirements, such as disk requirements, memory requirements, and OS requirements. The electronic (HTML or pdf) documentation has information about the most current requirements. Be aware, however, that the only supported hardware is the Solaris UltraSPARC processor family. The best place to look for these requirements is the DB2 Information Center on the IBM Web page, in the section “Installation on UNIX.”
Figure 2.1 shows the online documentation opened to the Solaris prerequisites section.
Figure 2.1. DB2 Information Center
Beginning with Version 7, DB2 UDB stopped supporting pre-UltraSPARC processors, sun4m and sun4d architectures, or earlier (as returned by the uname -m command). The only supported machines now use UltraSPARC processors, which include systems such as SunBlades and rack-mounted machines like the 280 and 480, mid-range systems such as the Sunfire 1280 or 4800, and enterprise systems like the E6800 and E15000.
Supported Operating System Level
DB2 UDB Version 8 was built on Solaris 7, but supports Solaris 8 and 9. DB2 UDB Version 7 supports Solaris 2.6, Solaris 7, Solaris 8, and Solaris 9. In all cases, it is recommended that the latest patch cluster and “recommended and security” patches be installed from the Sun Web site:
In addition, SUNWlibC and the J2SE Solaris patch cluster are required to install DB2.
The communication protocol to use between DB2 clients and the DB2 UDB server in the Solaris operating environment is TCP/IP. TCP/IP is provided with the Solaris OS, and is the only protocol available for client connections, not to mention the simplest to define and the most likely protocol to be used. During setup of a DB2 instance, several port definitions are required in the /etc/services file, one of which defines the TCP/IP port used by clients to connect to the instance. There is also a set of ports defined in the services file that are used by DB2 in “intra-partition” communication, in partitioned environments. These ports are defined automatically, placed in the services file by db2setup, and can be tailored during the db2setup process. Figure 2.2 shows a sample of the port setting that would appear in the /etc/services file for a system with two DB2 instances (db2inst1 and db2inst2).
Figure 2.2. Sample /etc/System File Port Definitions
APPC (CPI-C) connectivity through the DB2 Connect server support feature requires SNAP-IX for Solaris V7.02. There is no support for inbound APPC connections to DB2 UDB servers on Solaris, only TCP/IP. The SNA APPC support is for outbound APPC connectivity. As a general rule, TCP/IP is the recommended communications protocol, even in DB2 Connect scenarios.