Home > Articles > Data > DB2

DB2 UDB Installation

This chapter is from the book

This chapter is from the book

Installing DB2 UDB

To install DB2 UDB on a Solaris operating environment, you can choose from among several options. You must be root to install DB2.

The available installation methods for DB2 on Solaris are:

  • The DB2 Installer graphical interface (db2setup)— This Java program is supplied with the DB2 UDB product and is the recommended choice. It detects and configures communication protocols to use with the DB2 Administration Server (DAS) service and DB2 instances (these instances will be discussed later). It will also create the necessary userids and groups, and define an instance at installation time. The other methods require you to manually configure your system. It is a Java GUI, and will have the same look and feel on all platforms. In addition, it only installs the DB2 binaries into opt/IBM/db2/V8.1.

  • A text-based DB2 Installer program (db2_install)— This program is also supplied with the DB2 UDB product. It does not detect or configure communication protocols. It does not create a DB2 instance or the DAS service, either. While db2_install requires more tailoring than db2setup, it allows you to place the binaries into a location other than /opt/IBM/db2/V8.1; however, there will still be links placed there. After using db2_install, you can still use db2setup to “set up” your instance, including creating users/groups and the administration daemon (db2as).

  • The install command (pkgadd) of the Solaris operating environment— Using the install command requires you to know the complete syntax.

  • An installation utility available in your environment— For example, if the CDE (Common Desktop Environment) has been installed in your environment, the software installation tool can be used. This is a better choice than using the install command. However, neither communication detection nor configuration is performed. And, the DAS service and DB2 instance are not created.

The installation program of choice (db2setup) detects the active communication protocols on your system and configures them to work with DB2 UDB. It will create the database instance when DB2 UDB is installed, as well as the administration service or daemon, the DAS. The DAS service is used by the DB2 UDB administration tools, including the Control Center and Configuration Assistant, to satisfy requests. The second instance, called DB2, is used to create and manage databases.

The DB2 Installer program is the recommended choice. It is consistent across all UNIX environments. To run the DB2 Installer program, perform the following steps:

  • Log on to the system as root (the UNIX system administrator).

  • Mount the CD-ROM file system.

  • From the directory where the CD-ROM is mounted, type db2setup. The Java graphical interface will start up. If you are doing the installation remotely, remember to export your Display variable appropriately. Figure 2.5 shows an example of the initial screen.

    02fig05.jpgFigure 2.5. Initial db2setup Screen

As illustrated in Figures 2.6 and 2.7, db2setup allows you to view the Installation Prerequisites and the Release Notes for the latest possible information available. It would be valuable for you to review this information before proceeding.

02fig06.jpgFigure 2.6. Installation Notes

02fig07.jpgFigure 2.7. Release Notes

Figure 2.8 shows the components you can install from the distribution CD image. We have chosen the ESE, and the following panels provide tailoring options to allow you to override default selections, including components to install, user/group definitions, communications settings, and notification options.

02fig08.jpgFigure 2.8. Product Installation Selection Screen

After selecting to install the ESE, the Installer program will check your system, followed by your acknowledgment of the license agreement. After you agree to the license (Figure 2.9) , you can choose what kind of install to execute, Typical, Compact, or Custom. In Figure 2.10, we have chosen a typical install, but we will review some of the custom options later in this chapter. You may also choose whether or not you wish to install the Warehouse Center or Satellite Administration function.

02fig09.jpgFigure 2.9. DB2 License Agreement

02fig10.jpgFigure 2.10. Choose Installation Type

Figure 2.11 shows the components that are installed with a Typical install.

02fig11.jpgFigure 2.11. Components Installed with a Typical Installation of DB2 ESE

The next screen, Figure 2.12, gives you the option of saving your installation into a response file, which will allow you to remotely install the same image of DB2 on other machines. In fact, you can create a response file without actually installing DB2 on a machine.

02fig12.jpgFigure 2.12. Install DB2, Create a Response File, or Both

The db2setup tool can create users and groups for you, as well as define services and create instances. The next panel prompts for the userid that will be used for the DAS. As shown in Figure 2.13, the default is dbasusr1 in group dasadm1 (both of which will be created in this example).

02fig13.jpgFigure 2.13. Creating the DAS User

Once you have supplied information about the DAS userid (you can also select an existing user), DB2 will ask if you wish to create an instance, and if so, what kind of memory model should that instance use (32- or 64-bit), Figure 2.14 shows the screen options. If you have not already modified your kernel parameters, do not create an instance at this time. You can use db2isetup (similar to db2setup, but only for tailoring instances) after you get DB2 installed to create your instances/users/groups, etc. at a later time. Indicate whether an instance will be partitioned or not, as shown in Figure 2.15. Partitioning considerations will be covered in more depth in Chapter 10.

02fig14.jpgFigure 2.14. Instance Creation Selection

02fig15.jpgFigure 2.15. Partitioned Instance or Not?

After deciding to partition (or not) this instance, in Figure 2.16 you define the “instance owning” userid, which becomes the name of this instance.

02fig16.jpgFigure 2.16. Instance Owner Creation

The next step is to define the userid where “fenced” procedures will be run (this will put them into a separate address space, and will help keep a “bad” stored procedure from crashing DB2). You must supply a userid for fenced procedures when creating an instance (Figure 2.17)

02fig17.jpgFigure 2.17. Fenced User Creation.

Following the definition of the fenced user, you must decide if this system will contain tables to use for the monitoring functions within DB2. This information is stored by the administration server for scheduling, notification, and completion information, mainly generated by the Task Center (Figure 2.18).

02fig18.jpgFigure 2.18. Keep DB2 Tools Information in a Local Database?

If you have selected to prepare a local database for use by the DB2 tools, you must tell DB2 the instance, database, and schema you wish to use, as shown in Figure 2.19.

02fig19.jpgFigure 2.19. Define the Instance, Database, and Schema to Use for the DB2 Tools Information

Along with the administration service, which communicates with the graphical management tools supplied with DB2, you will also need to define contact information, to tell DB2 the correct list of contacts to use for sending messages for system notification, as shown in Figure 2.20.

02fig20.jpgFigure 2.20. Contact List for System Notification Messages

To prepare DB2 to interact with the tools shipped with Version 8, you need to specify a database for the tools to use (Figures 2.18 and 2.19). A second notification screen (Figure 2.21) defines who to contact for Health Monitor (one of the tools) messages.

02fig21.jpgFigure 2.21. Health Monitor Contact Information

Finally (at last!), a screen will appear that allows you to verify what is about to be installed or created, the userids and groups that will be used, the services file entries and contact lists you have defined, and the amount of disk space that will be consumed. Check to make sure that what is going to occur is what you intended, by scrolling through the display, then click “Install” to begin the installation (Figure 2.22).

02fig22.jpgFigure 2.22. Installation Actions Confirmation

Don't forget that if you are creating an instance, you MUST have already modified the kernel configuration and rebooted, or the instance creation portion of the db2setup actions will fail.

If you had chosen to do a Custom install (Figure 2.10), you would have been provided other options. Figure 2.23 shows some of the other installation options based on a Custom install.

02fig23.jpgFigure 2.23. Custom Install Options

With a Typical install, you do not have the option to modify the communications parameters during setup (you can still tailor them later) and will get default settings. With the Custom installation path, you can define /etc/services file definitions during the setup process, as shown in Figure 2.24.

02fig24.jpgFigure 2.24. Defining TCP/IP Definitions During a Custom Install

Other options that you can modify are authentication type and Autostart (Figure 2.25) or the Languages you want installed (Figure 2.26).

02fig25.jpgFigure 2.25. Authentication and Autostart Selection

02fig26.jpgFigure 2.26. Choosing Languages in a Custom Install

With that, and selecting “Finish” from the confirmation dialogue in Figure 2.22, you will see a progress screen that shows something is happening (Figure 2.27).

02fig27.jpgFigure 2.27. Installation Progress

Finally, you get a completion dialogue that allows you to review the success of your installation, as shown in Figure 2.28.

02fig28.jpgFigure 2.28. db2setup Completion Results

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020