DB2 ESE 9.7.5 Trial Installation Instructions

8/9/2019 DB2 ESE 9.7.5 Trial Installation Instructions

1/25

IBM SoftwareInformation Management

IBM DB2 ESE 9.7 Trial Virtual Appliance Installation Guide


2/25


IBM DB2 ESE 9.7 Trial Virtual Appliance© Copyright IBM Corp. 2011. All rights reserved Page 2 of 25

Table of Contents

1 Before You Begin ............................................................3 2 Introduction .....................................................................3

2.1 Software Components Reference....................................3

3 Hardware and Software Prerequisites...........................3 3.1

Hardware Prerequisites ...................................................3

3.2

Software Prerequisites.....................................................4

4 Getting Started ................................................................4 4.1

Installation of the Appliance (Workstation Image).............4

4.2

Before you start ...............................................................5

5

Configuration of the DB2 Virtual Appliance..................6

6 Working with Your Installed System ...........................14 6.1

VMware Tools Install .....................................................14

6.2

Starting and Stopping DB2 service ................................14

6.3

IBM Data Studio ............................................................19

7 Repackaging..................................................................22 8 Appendix........................................................................23

8.1

IBM DB2 Configurations ................................................23

9 Additional Information..................................................24 9.1

Feedback.......................................................................24


3/25



1 Before You Begin

Experience the power of DB2 by using the provided DB2 Enterprise 9.7 Virtual Appliance image. This image is designed to runin VMware® Workstation 5.5 / VMware Player 2.0 or later.

2 Introduction

This document details the deployment procedure for DB2 Enterprise 9.7 Trial Virtual Appliance. It will allow you to experiencethe fully functional DB2 data server in a VMware based virtual image (VM). The VM also includes customized YaST modules toguide you through the configuration steps.

2.1 Software Components Reference

The following matrix is meant to provide you with an overview of the software components that are going to be installed in thevirtual appliance, as well as driver versions that are to be applied as part of the deployment.

Version Comment

SUSE Linux Enterprise Server 11 + SP1

DB2 Enterprise 9.7 FP5 DB2 Enteprise 9.7 trial license will expire 90days after the first login of the VA

Technology Explorer for IBM DB2 4.1 Alpha 4

ibm_db2 PHP driver 1.8.3

IBM Data Studio 2.2.1.0

3 Hardware and Software Prerequisites

Before installation of the DB2 Enterprise 9.7 Trial Virtual Appliance can commence, please ensure that you have met allprerequisites as detailed below.

3.1 Hardware Prerequisites

The DB2 Enterprise 9.7 Trial Virtual Appliance is available in both a 32-bit and 64-bit version.It is required that you have met the following specifications on your host machine:

Attention: Before you begin using the provided DB2 Enterprise 9.7 Trial Virtual Appliance, please make sure you read this guidethoroughly in order to ensure the successful deployment of the DB2 virtual appliance.


4/25



Requirement Specification Memory on host machine Minimum: 1.5 GB

Disk space on host machine Minimum: 8.0 GB

3.2 Software Prerequisites

This Image is designed to run in VMware Workstation 5.5 / VMware Player 2.0 or later. You may download the software from theVMware website: http://www.vmware.com.

4 Getting Started4.1 Installation of the Appliance (Workstation Image)

To run the DB2 virtual appliance (either 32 or 64 bit), perform the following steps:

1. Copy and extract the self-extracting package into a temporary directory. The self-extracting package name should be in

the form of:

DB2_ESE_9.7_trial_VA_bit.exe

2. Extract the contents of the package to the desired directory. On Linux® you may use the command:

unrar x DB2_ESE_9.7_trial_VA_bit.exe

(You will need an unrar utility that is supported on your platform.)On Windows®, you can extract the contents by executing the following self-extracting package:

DB2_ESE_9.7_trial_VA_bit.exe

3. Open VMware in your host operating system.

4. Open the VMware image that was extracted to a directory in step two. You may do this by clicking File > Open and

browsing to the directory the files were extracted in.

Attention: The uncompressed image files will take up about 4 GB of space and the size will grow as you use the DB2 virtualappliance. Please make sure you have enough free disk space before un-compressing the self-extracted package.


5/25



4.2 Before you start

4.2.1 Taking Snapshots of the Virtual Appliance

(Optional) At any point in time when you are using the virtual appliance, if you wish to capture the current state of the image, youcan take a snapshot of the image by doing the following:

1. Click on the button on the top panel.

2. Enter the name of the Snapshot and press on OK button to save the snapshot.

To revert to an earlier snapshot, click on the button. In the Manage Snapshot window, click on the snapshot you wish torevert to, and then click on the “Go to” button.

4.2.2 Starting up the DB2 Virtual Appliance

To start up the DB2 virtual appliance, press the button.

You might be asked whether you have moved or copied the virtual machine. Choose “I copied it” and click [OK] to continue.


6/25



5 Configuration of the DB2 Virtual Appliance

This section describes the detailed procedures on how to successfully configure the DB2 virtual appliance.

1. After powering on the Virtual Machine, select DB2 Enterprise 9.7.5 SLES11 SP1-bit [ VMX ] from the bootmenu. Please note this is the default option and will be selected automatically if you miss this menu.


7/25



2. Wait for the system to boot up and, if everything is successful, you should see the Language and Keyboard layoutscreen, as shown below. Click Next to continue.

3. Now you should see the Welcome screen. Click Next to continue.

4. You must accept the Novell License Agreement in order to continue; otherwise, the virtual appliance will halt.


8/25



5. You also must accept the IBM DB2 License Agreement in order to continue. Click Next.

6. You can change the hostname of your virtual machine if you wish in the following configuration screen. Note that if youare going to configure a static IP address for this virtual machine, you should uncheck the “Change hostname viaDHCP” checkbox. The next configuration screen will allow you to set the static IP. Click Next to continue.


9/25



7. The next configuration screen, as shown below, allows you to optionally configure the network card in your virtua

machine. It has been preset to use DHCP. You can use the button to choose a static IP address andchange any of the configurations. Click Next to continue.


10/25



8. The next screen allows you to change the timezone of your machine. Please use the drop-down menus and the button

to change this configuration. Press Next to continue.

9. The following screen prompts you to choose a password for the root user. Please choose a secure password and pressNext to continue.


11/25



10. The next screen prompts you to choose passwords for the DB2 instance user, DB2 fenced user, and DB2

administration server user. You can change the default user and group values by un-checking thecheckbox. Press Next to continue.

11. The next screen will show a progress of the DB2 configuration. The DB2 system and instance users will be created.


12/25



12. The next screen shows a summary of the DB2 configuration. All tasks should report a status of OK. Press Next tocontinue.

13. The next screen asks you to enter a name for the production database. You can leave the field blank to create thedatabase at a later time. Press Next to continue.


13/25



14. The next screen shows a summary of the DB2 Database Creation. All tasks should report a status of OK. You wilnotice that only the default tablespaces are created in the database. If you wish to create additionaldatabase/tablespaces, creation scripts are created for your convenience. Mark down the location of these scripts andyou will be able to create the desired database objects at a later time. Press Next to continue.


14/25



15. At this point, when you press the Next button, the suseconfig process will run to complete the setup of your system.This takes a minute or so. You should now see the login screen of the system.

The system is now ready to be used and the DB2 database manager is started. To understand the configurations that havebeen applied to your system, you can read about them in the section 8 Appendix.

6 Working with Your Installed System

6.1 VMware Tools Install

It is highly recommended that the end user install the VMware Tools version that comes with their VMware product after the DB29.7 Virtual Appliance has been fully configured. VMware Tools brings in many benefits for the use of any virtual applianceincluding better clock synchronization with the host system, improved file movement between the host and guest OS (ifapplicable), and improved GUI responsiveness. For more information on VMware Tools, please refer to your VMware productmanual.

6.2 Starting and Stopping DB2 service

In the deployed DB2 virtual appliance environment, a package is installed automatically which allows the user to easily start andstop DB2 and setup required kernel environment with one single command.

6.2.1 Starting and Stopping DB2 with rcdb2

The rcdb2 tool is pre-installed on the virtual appliance for your convenience. With one single rcdb2 command, you are able to:

► check the current status of DB2 Administration Server and instances

► setup required kernel parameters and start DB2 and activate all existing DB2 databases


15/25



► stop DB2 services all at once

The rcdb2 tool is registered in the default SLES OS startup and stop sequence, so that when the system is shutdown andstarted up, DB2 services will be stopped and started up automatically. This can eliminate the user’s need to stop DB2 manuallybefore turning off the machine, or start DB2 services manually after every system bootup. To check the current status of DB2,run the following command with the root user:

To stop DB2, run the following command with the root user:

To start DB2, run the following command with the root user:

Every time rcdb2 start is executed, it will verify and set the required kernel parameters to run DB2 on the system. When thekernel parameters are verified in place, the tool will start DB2 Administration Server as well as every DB2 instances anddatabases on the system.

To restart DB2, run the following command with the root user:

6.2.2 Kernel Parameter settings in rcdb2

In a default Linux environment, the default kernel parameter values are not sufficient when running DB2 database on a systemThe DB2 virtual appliance customized rcdb2 start/stop script updates the recommended kernel parameters for a virtualized DB2server.

By default, the DB2 virtual appliance customized rcdb2 start/stop script updates the following kernel parameters every timercdb2 start/restart is executed.

# rcdb2 statusDAS: running Instance db2inst1 (/opt/ibm/db2/V9.7): running

# rcdb2 stopStopping DAS: done Stopping instance db2inst1 (/opt/ibm/db2/V9.7): done

# rcdb2 startStarting DAS: done Starting instance db2inst1 (/opt/ibm/db2/V9.7): done Activating database ANYDB for db2inst1 done

# rcdb2 restartStopping DAS: done Stopping instance db2inst1 (/opt/ibm/db2/V9.7): done Starting DAS: done Starting instance db2inst1 (/opt/ibm/db2/V9.7): done Activating database ANYDB for db2inst1 done


16/25



If you are certain and would still like to modify the kernel parameters, execute the following command to modify the kerneparameters temporarily. Note that you must have root authority to modify kernel parameters.

# /sbin/sysctl -w =

For example, if you would like to set the value of kernel.msgmax to 65536:

# /sbin/sysctl –w kernel.msgmax=65536

NOTE: The kernel parameters will only be modified temporarily. Every time the system is rebooted, or when rcdb2 start/restart is

executed, the kernel parameters will be updated to the above default virtualized DB2 environment settings.6.2.3 DB2 Registry and DBM/DB Configuration Settings

During the initial DB2 configuration module, certain Database Manager settings have been pre-configured for your DB2environment. These settings are configured based on expert recommendations for easy administration. However, if you havespecific business requirements for your DB2 environment, you may change the parameters as required.

6.2.3.1 Database Manager Configuration Parameters

Check section 8 Appendix.

6.2.3.2 Database Configuration Parameters

If you have chosen to create a database in the DB2 configuration module, or you have used the

“/home/${DB2INSTANCE}/bin/createDatabase” script to create a database, the following database configuration

parameters would have been applied automatically:

auto_maint ON;auto_db_backup OFF;auto_tbl_maint ON;

Attention: It is strongly recommended to keep the default DB2 kernel parameter settings. Modifying any default DB2 kernelparameters may result in DB2 running on the system not able to perform properly.

kernel.shmmax = kernel.shmall = kernel.shmmni = 4096kernel.msgmni = 1024kernel.msgmnb = 65536kernel.msgmax = 65536kernel.sem = 250 256000 32 4096vm.swappiness = 0vm.dirty_ratio = 10vm.dirty_background_ratio = 5fs.file-max = 262144


17/25



auto_runstats ON;auto_reorg ON;

All other database parameters are set to the DB2 default values.

6.2.3.3 Displaying DB2 profile registry / Configuration parameters

To display a list of configured DB2 profile registry parameters:

db2set –all

To display a list of configured DB2 Database Manager Configuration parameters:

db2 attach to db2 get dbm cfg show detail

To display a list of configured DB2 Database Configuration parameters:

db2 connect to db2 get db cfg show detail

6.2.3.4 Modifying DB2 profile registry / Configuration parameters

If any of the above parameters do not fit your business requirements, you may change the parameters using the following

utilities.To update DB2 profile registry parameters:

db2set =

To update Database Manager (DBM) configuration parameters:

db2 update dbm cfg using

To update Database (DB) configuration parameters:

db2 update db cfg for using

6.2.4 Database and Tablespace Creation Utilities

Once you have successfully deployed the DB2 virtual appliance, you will be provided with scripts for creating additionaldatabases and tablespaces.

The location of the scripts is in the DB2 instance’s home directory under the bin directory:

/home//bin/createDatabase


18/25



/home//bin/createTablespaces

6.2.4.1 createDatabase script

The createDatabase script is executed if you have chosen to create a database in the DB2 configuration module.

The database created will have the following attributes:

► Storage method: Automatic storage database using database/storage path on /db2fs

► Database will be created under: /db2fs//NODE0000/

► Database partitions: 0

► Buffer Pools: A bufferpool named bpool8k is created by default with page size of 8 kB.

If you wish to create an additional database, you can create a database using the preconfigured createDatabase script followingthe following procedures:

1. Login as DB2 instance user

db2server:~ # su – db2inst1

2. Change directory to /home//bin directory:

db2inst1@db2server:~> cd bin

3. Execute the createDatabase script from the bin directory:

db2inst1@db2server:~/bin> ./createDatabase

4. When the database has successfully created, you should see the following message:

db2inst1@db2server:~/bin> ./createDatabase TESTDB[*] Creating database TESTDB... OK[*] Creating db partition groups ... OK[*] Creating buffer pools... OK[*] Configuring database... OK[*] Database created and configured successfully.[*] Restarting instance... OK[*] Database creation complete.

6.2.4.2 createTablespaces script

Once you have created a database in the DB2 configuration or manually using the createDatabase script, you are ready to usethe createTablespaces script to create the data, index, and temporary tablespaces for your database. The createTablespacescript calculates the size of all data, index, and temporary tablespaces based on the space available and recommended certainsizes. If you do not wish to create the tablespaces based on the recommended sizes, you can optionally provide your own sizepreferences for individual tablespaces.

Note: Please note that the provided createTablespaces script depends on the provided createDatabase script. ThecreateTablespace script will not work If you have not created a database using either the DB2 Configuration tool or manuallyexecuted the createDatabase script.


19/25



The createTablespaces script will perform the following:

► Calculates available space across database containers.► Creates three tablespaces of different sizes based on recommended calculated sizings:

o DATA tablespace: available container space divided by 3o INDEX tablespace: available container space divided by 3o TEMP tablespace: available container space divided by 9

► All tablespaces will be created in page size of 8 kB, using bufferpool bpool8k.► Remaining container space will be left as free physical space, which can be used for storing database backups.

To create pre-configure tablespaces using the createTablespace script, please follow the following steps:

1. Login as DB2 instance user

db2server:~ # su – db2inst1

2. Change directory to /home//bin directory:

db2inst1@db2server:~> cd bin

3. Execute the createTablespaces script from the bin directory:

~/bin> ./createTablespaces

4. The recommended tablespace sizing will be displayed. Enter Y to accept the default sizing or N to provide your own

sizing preferences. ~/bin> ./createTablespaces TESTDBPlease verify the following information.Size of the DATA tablespace per partition: 12GBSize of the INDEX tablespace per partition: 12GBSize of the TEMP tablespace per partition: 4GBIs this correct? (Y/N)

5. The tablespaces will then be created. The createTablespaces progress may take several hours to finish. Please waitpatiently for the tablespaces to get created.

6.3 IBM Data Studio

With the advent of IBM® Data Studio comes a major advance in the way DB2® developers and administrators alike carry outtheir day to day functions. Historically, depending on the tasks to be completed, it was common to switch back and forthbetween disparate tools such as Control Center, Health Monitor, Developer Workbench, and even the DB2 Command LineProcessor (CLP).

The release of IBM Data Studio changes all this, facilitating DB2 administration, design, development, and monitoring all withinan integrated, Eclipsed-based environment. Data Studio, the same tool that allows tuning of buffer pools and restriction ofaccess to data objects, can now be used to develop data web services and debug stored procedures. By leveraging the powerof IBM Data Studio, users are certain to enjoy increased productivity as they find themselves able to perform a majority of theirtasks within a single environment.

6.3.1 Launching Data Studio

To launch the IBM Data Studio, login as a DB2 instance user, and execute the following command:


20/25



db2inst1@db2server:~> /opt/IBM/IBM_DataStudio_Standalone/datastudio &

In the Select a workspace dialog, accept the default path (or choose your own) and optionally check the Use this as thedefault and do not ask again checkbox. Click OK.

Data Studio will now start with the Welcome homepage.

Minimize this window by clicking the minimize button located at the top right to bring you into the Data perspective as shownbelow.


21/25




22/25



7 Repackaging

The purpose of pre-integrating software into the DB2 9.7 Virtual Appliance is to alleviate the application installation, configurationand integration tasks from the end-user, making the deployment of the applications on DB2 in a VA easy and painless.

We use SUSE Studio technology to build such appliances which accompany this document. As a SUSE Studio user, you canalso easily build customized appliances with DB2 through integrated templates.

If you are interested in integrating your solution into a DB2 Express-C virtual appliance, you can either search for “db2” on SUSEStudio (http://susegallery.com/search?q=db2), or visit the following links (respective of your desired architecture) to obtain theintegrated templates:32bit – http://susegallery.com/a/EMFF3Y/db2-express-c-972-sles11-sp1-32-bit64bit – http://susegallery.com/a/EMFF3Y/db2-express-c-972-sles11-sp1-64-bit

These templates both contain DB2 Express-C running on Novell® SUSE™ Linux Enterprise Server 11 SP1 operating system.

For more information, or for other editions of DB2, please feel free to contact [email protected] and enter "Use of DB2 9.7Virtual Appliance for Repackaging" in the subject line.


23/25



8 Appendix

The following section provides information on certain configurations already performed on your DB2 Appliance.

8.1 IBM DB2 Configurations

DB2 version installed is 9.7 FP5.

Setting Type Default Configured in VA

Installation Directory /opt/ibm/db2/V9.7 - /opt/ibm/db2/V9.7

DB2 Instance User /Group db2inst1/db2grp1 May be changed by the user on first boot ofthe virtual machine.

DB2 Administration Server User/Group dasusr1/dasadm1 May be changed the user on first boot of thevirtual machine.

DB2 Fenced User/Group db2fenc1/db2fgrp1 May be changed the user on first boot of thevirtual machine.

DB2 Port Number db2c_%INSTANCE%/50001 50001

DFTDBPATH /home/%INSTANCE% /db2fs

DIAGPATH /home/%INSTANCE% /db2fs/diag

DB2COMM N/A TCPIP


24/25



9 Additional Information

9.1 Feedback

Thank you for using DB2 9.7 Virtual Appliance.

We welcome your feedback about your experience on the DB2 virtual appliance. If you notice anything not working correctly, orwould like to comment on your experience on the DB2 virtual appliance, please send your feedback to [email protected]:enter "DB2 9.7 Virtual Appliance" in the subject line.


25/25


IBM DB2 ESE 9 7 T i l Vi t l A li

© Copyright IBM Corporation 2011 All Rights Reserved.

IBM Canada8200 Warden AvenueMarkham, ONL6G 1C7Canada

IBM, the IBM logo, ibm.com and Tivoli are trademarks or registered

trademarks of International Business Machines Corporation in theUnited States, other countries, or both. If these and otherIBM trademarked terms are marked on their first occurrence in thisinformation with a trademark symbol (® or ™), these symbols indicateU.S. registered or common law trademarks owned by IBM at the timethis information was published. Such trademarks may also beregistered or common law trademarks in other countries. A current listof IBM trademarks is available on the Web at “Copyright andtrademark information” at ibm.com/legal/copytrade.shtml

Other company, product and service names may be trademarks orservice marks of others.

References in this publication to IBM products and services do notimply that IBM intends to make them available in all countries in whichIBM operates.

No part of this document may be reproduced or transmitted in any formwithout written permission from IBM Corporation.

Product data has been reviewed for accuracy as of the date of initialpublication. Product data is subject to change without notice. Anystatements regarding IBM’s future direction and intent are subject tochange or withdrawal without notice, and represent goals andobjectives only.

THE INFORMATION PROVIDED IN THIS DOCUMENT ISDISTRIBUTED “AS IS” WITHOUT ANY WARRANTY, EITHEREXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANYWARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE OR NON-INFRINGEMENT.

IBM products are warranted according to the terms and conditions of

the agreements (e.g. IBM Customer Agreement, Statement of LimitedWarranty, International Program License Agreement, etc.) under whichthey are provided.

Documents

DB2 ESE 9.7.5 Trial Installation Instructions