DB2InstallingServers-db2ise1051.pdf

IBM DB2 10.5for Linux, UNIX, and Windows

Installing DB2 ServersUpdated October, 2014

GC27-5514-01

NoteBefore using this information and the product it supports, read the general information under Appendix B, Notices, onpage 669.

Edition Notice

This document contains proprietary information of IBM. It is provided under a license agreement and is protectedby copyright law. The information contained in this publication does not include any product warranties, and anystatements provided in this manual should not be interpreted as such.

You can order IBM publications online or through your local IBM representative.v To order publications online, go to the IBM Publications Center at http://www.ibm.com/shop/publications/

order

v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/planetwide/

To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU(426-4968).

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

Copyright IBM Corporation 1993, 2014.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

http://www.ibm.com/shop/publications/orderhttp://www.ibm.com/shop/publications/orderhttp://www.ibm.com/planetwide/http://www.ibm.com/planetwide/

Contents

Part 1. Installation requirements forDB2 database products . . . . . . . 1

Chapter 1. Checking installationprerequisites by using thedb2prereqcheck command. . . . . . . 3

Part 2. DB2 servers and IBM dataserver clients . . . . . . . . . . . 11

Chapter 2. An overview of installingDB2 database servers (Linux and UNIX) 13

Chapter 3. An overview of installingDB2 database servers (Windows) . . . 15

Chapter 4. Non-root installationoverview (Linux and UNIX) . . . . . . 17Differences between root installations and non-rootinstallations . . . . . . . . . . . . . . 17Limitations of non-root installations . . . . . . 18Thin server instance topology overview (Linux andAIX) . . . . . . . . . . . . . . . . . 20

Setting up a thin server instance environment(Linux and AIX) . . . . . . . . . . . . 22Mounting a thin server instance (Linux and AIX) 23Supported instance management functions in athin server instance environment . . . . . . 25

Installing DB2 database servers as a non-root user 31Enabling root-based features in non-rootinstallations with db2rfe . . . . . . . . . 33

Reducing the size of your DB2 product installationimage . . . . . . . . . . . . . . . . 34

Chapter 5. Java software support forDB2 database products . . . . . . . 37

Chapter 6. Preparing to install DB2database servers . . . . . . . . . . 41Disk and memory requirements . . . . . . . 41Installation prerequisites for database servers . . . 42

Prerequisites for a DB2 database serverinstallation (Linux and UNIX) . . . . . . . 42Prerequisites for a DB2 database serverinstallation (Windows). . . . . . . . . . 58Additional installation considerations (AIX) . . 67Additional installation considerations (HP-UX) 68Additional installation considerations (Linux) . . 69Additional installation considerations (Solaris). . 76

Setting up Network Time Protocol . . . . . . . 77

Configuring hosts as Network Time Protocolclients . . . . . . . . . . . . . . . 77Setting up a Network Time Protocol server . . . 78

Directory structure for your installed DB2 databaseproduct (Windows) . . . . . . . . . . . . 79Directory structure for your installed DB2 databaseproduct (Linux) . . . . . . . . . . . . . 84DB2 Setup wizard language support . . . . . . 88

Supported DB2 interface languages . . . . . 88Displaying the DB2 Setup wizard in yournational language (Linux and UNIX) . . . . . 89Language identifiers for running the DB2 Setupwizard in another language . . . . . . . . 89Changing the DB2 interface language (Linux andUNIX) . . . . . . . . . . . . . . . 90Changing the DB2 product interface language(Windows). . . . . . . . . . . . . . 91

Password rules . . . . . . . . . . . . . 92Multiple DB2 copies on the same computer(Windows). . . . . . . . . . . . . . . 92Multiple DB2 copies on the same computer (Linuxand UNIX) . . . . . . . . . . . . . . 97IBM Secure Shell Server For Windows service . . . 98Mounting DB2 product media . . . . . . . . 98

Mounting CDs or DVDs (AIX) . . . . . . . 98Mounting CDs or DVDs (HP-UX) . . . . . . 99Mounting the CD or DVD (Linux) . . . . . 100Mounting CDs or DVDs (Solaris OperatingSystem) . . . . . . . . . . . . . . 100

Chapter 7. Installing DB2 databaseservers using the DB2 Setup wizard(Windows). . . . . . . . . . . . . 103

Chapter 8. Installing DB2 serversusing the DB2 Setup wizard (Linuxand UNIX) . . . . . . . . . . . . . 107

Chapter 9. Installing DB2 productswith payload files (Linux and UNIX) . . 111

Chapter 10. DB2 Setup wizardinstallation walkthrough . . . . . . . 115

Chapter 11. Verifying the installationusing the command line processor(CLP) . . . . . . . . . . . . . . . 135

Chapter 12. Taking the first steps afterinstallation . . . . . . . . . . . . 137Deleting a Firefox browser profile . . . . . . 137Applying DB2 licenses . . . . . . . . . . 137

Copyright IBM Corp. 1993, 2014 iii

Updating licenses . . . . . . . . . . . . 139DB2 database product licensing and support . . . 141Post-installation tasks for DB2 database servers(Windows) . . . . . . . . . . . . . . 141

Adding your user ID to the DB2ADMNS andDB2USERS user groups (Windows) . . . . . 141Updating your 32-bit DB2 instances to 64-bitinstances (Windows) . . . . . . . . . . 142Validating your DB2 copy . . . . . . . . 142Setting up notification and contact lists . . . . 143Changing the default DB2 and default IBMdatabase client interface copy after installation(Windows) . . . . . . . . . . . . . 143IBM data server client connectivity usingmultiple copies . . . . . . . . . . . . 154Working with existing DB2 copies . . . . . 156Checking for DB2 updates . . . . . . . . 157Installing the SSH Server component afterinstalling the DB2 product (Windows) . . . . 158

Post-installation tasks for DB2 database servers(Linux and UNIX) . . . . . . . . . . . . 158

Listing DB2 database products installed on yoursystem (Linux and UNIX) . . . . . . . . 158Validating your DB2 copy . . . . . . . . 160Main menu entries for DB2 tools (Linux) . . . 160

First Steps interface . . . . . . . . . . . 161

Part 3. Installing a DB2 pureScaleenvironment . . . . . . . . . . . 163

Chapter 13. Installing a DB2 pureScaleenvironment (AIX) . . . . . . . . . 165Plan your DB2 pureScale Feature installation (AIX) 165Preinstallation of DB2 pureScale Feature (AIX) . . 168

Installation prerequisites for DB2 pureScaleFeature (AIX) . . . . . . . . . . . . 168Configuring communication adapter ports andswitches (AIX) . . . . . . . . . . . . 178Installing and setting up OpenSSH . . . . . 202Setting up db2locssh . . . . . . . . . . 204Shared storage support for DB2 pureScaleenvironments . . . . . . . . . . . . 205Configuring PVIDs for a DB2 pureScale instance(AIX) . . . . . . . . . . . . . . . 209Creating required users for a DB2 pureScaleFeature installation . . . . . . . . . . 210Preinstallation checklist for DB2 pureScaleFeature (AIX) . . . . . . . . . . . . 213User-managed file system support for DB2pureScale environments . . . . . . . . . 218Manually allowing the DB2 installer to takeover a user-managed GPFS cluster . . . . . 220

Installing the DB2 pureScale Feature using the DB2Setup wizard (AIX and Linux). . . . . . . . 221Installing the DB2 pureScale Feature using aresponse file (AIX and Linux) . . . . . . . . 242Installing DB2 pureScale Feature using thedb2_install command. . . . . . . . . . . 243Performing post-installation tasks for the DB2pureScale Feature (AIX) . . . . . . . . . . 245

Registering a DB2 product or feature license keyusing the db2licm command . . . . . . . 245Creating a DB2 pureScale instance ininstallations without an instance . . . . . . 246Setting up a Network Time Protocol server . . 248Configuring hosts as Network Time Protocolclients . . . . . . . . . . . . . . . 249Enabling SCSI-3 PR for DB2 pureScale Feature 250Verifying your DB2 pureScale installation andsetup . . . . . . . . . . . . . . . 252Compiling the GPFS Portability Layer module 252

Taking the first steps after installing the DB2pureScale Feature (AIX) . . . . . . . . . . 253

Adding communication adapter ports to a CF ormember . . . . . . . . . . . . . . 253Adding new members or an additional clustercaching facility . . . . . . . . . . . . 255Adding a netname to a member . . . . . . 256Adding a netname to a cluster caching facility 257Enable or disable remote root login . . . . . 258Changing the db2sshid user ID to a differentuser . . . . . . . . . . . . . . . 258Re-adding a deleted db2sshid user ID . . . . 259Moving from a TCP/IP protocol network to anRDMA protocol network . . . . . . . . 259Moving from an RDMA protocol network to aTCP/IP protocol network . . . . . . . . 261

Chapter 14. Installing a DB2 pureScaleenvironment (Linux) . . . . . . . . 263Plan your DB2 pureScale Feature installation(Linux) . . . . . . . . . . . . . . . 263Preinstallation of DB2 pureScale Feature (Linux) 266

Installation prerequisites for DB2 pureScaleFeature (Linux) . . . . . . . . . . . . 266Installation prerequisites for the DB2 pureScaleFeature in a virtual machine (Linux). . . . . 275Modifying kernel parameters (Linux) . . . . 277Configuring communication adapter ports andswitches (Linux) . . . . . . . . . . . 279Installing and setting up OpenSSH . . . . . 316Setting up db2locssh . . . . . . . . . . 317Shared storage support for DB2 pureScaleenvironments . . . . . . . . . . . . 319Creating required users for a DB2 pureScaleFeature installation . . . . . . . . . . 323Preinstallation checklist for DB2 pureScaleFeature (Linux) . . . . . . . . . . . . 325Manually allowing the DB2 installer to takeover a user-managed GPFS cluster . . . . . 333

GDPC infrastructure and GDPC-specificprerequisite conditions . . . . . . . . . . 334Installing the DB2 pureScale Feature using the DB2Setup wizard (AIX and Linux). . . . . . . . 338Installing the DB2 pureScale Feature using aresponse file (AIX and Linux) . . . . . . . . 359Installing DB2 pureScale Feature using thedb2_install command. . . . . . . . . . . 360DB2 pureScale Feature in a virtual environment(Linux) . . . . . . . . . . . . . . . 362

iv Installing DB2 Servers

Creating a DB2 pureScale instance in a virtualenvironment using a single physical server(Linux) . . . . . . . . . . . . . . 364Consolidating the DB2 pureScale Feature in avirtual environment (Linux) . . . . . . . 365

Performing post-installation tasks for the DB2pureScale Feature (Linux) . . . . . . . . . 367

Registering a DB2 product or feature license keyusing the db2licm command . . . . . . . 367Creating a DB2 pureScale instance ininstallations without an instance . . . . . . 368Setting up a Network Time Protocol server . . 370Configuring hosts as Network Time Protocolclients . . . . . . . . . . . . . . . 372Enabling SCSI-3 PR for DB2 pureScale Feature 372Verifying your DB2 pureScale installation andsetup . . . . . . . . . . . . . . . 374Compiling the GPFS Portability Layer module 374

Taking the first steps after installing the DB2pureScale Feature (Linux) . . . . . . . . . 375

Adding communication adapter ports to a CF ormember . . . . . . . . . . . . . . 375Adding new members or an additional clustercaching facility . . . . . . . . . . . . 377Adding a netname to a member . . . . . . 378Adding a netname to a cluster caching facility 379Enable or disable remote root login . . . . . 380Changing the db2sshid user ID to a differentuser . . . . . . . . . . . . . . . 380Re-adding a deleted db2sshid user ID . . . . 381Moving from a TCP/IP protocol network to anRDMA protocol network . . . . . . . . 381Moving from an RDMA protocol network to aTCP/IP protocol network . . . . . . . . 383

Chapter 15. Creating a shared filesystem . . . . . . . . . . . . . . 385Deleting a shared file system . . . . . . . . 386Retrieving file system information . . . . . . 387

Chapter 16. Configuring a GDPCenvironment . . . . . . . . . . . . 389Getting the cluster installed and running in aGDPC environment . . . . . . . . . . . 390Setting up GPFS replication in a GDPCenvironment. . . . . . . . . . . . . . 399Setting up a RoCE network in a GDPCenvironment (AIX) . . . . . . . . . . . 404Configuring the cluster for high availability in aGDPC environment . . . . . . . . . . . 406Creating the database in a GDPC environment . . 408

Part 4. Installing the DB2Partitioned Database Environment. 409

Chapter 17. Preparing to install theDB2 Partitioned DatabaseEnvironment . . . . . . . . . . . . 411

Preparing the environment for a partitioned DB2server (Windows) . . . . . . . . . . . . 411Updating environment settings for a partitionedDB2 installation (AIX) . . . . . . . . . . 413Verifying port range availability on participatingcomputers (Linux and UNIX) . . . . . . . . 415Creating a DB2 home file system for a partitioneddatabase environment . . . . . . . . . . 416

Creating a DB2 home file system for apartitioned database system (AIX) . . . . . 416Creating a DB2 home file system for apartitioned database system (HP-UX) . . . . 418Creating a file system for a partitioned databasesystem (Linux) . . . . . . . . . . . . 420Creating a DB2 home file system for apartitioned database system (Solaris) . . . . 421

Verifying that NFS is running (Linux and UNIX) 423Creating groups and users in a partitioneddatabase environment . . . . . . . . . . 424

Creating required users for a DB2 serverinstallation in a partitioned databaseenvironment (AIX) . . . . . . . . . . 424Creating required users for a DB2 serverinstallation in a partitioned databaseenvironment (HP-UX) . . . . . . . . . 426Creating required users for a DB2 serverinstallation in a partitioned databaseenvironment (Linux) . . . . . . . . . . 427Creating required users for a DB2 serverinstallation in a partitioned databaseenvironment (Solaris Operating System) . . . 428

Chapter 18. Setting up a partitioneddatabase environment . . . . . . . 431

Chapter 19. Verifying the installation 435Verifying access to the registry on theinstance-owning computer (Windows) . . . . . 435Verifying a partitioned database server installation(Linux and UNIX) . . . . . . . . . . . . 435Verifying a partitioned database environmentinstallation (Windows) . . . . . . . . . . 436

Chapter 20. Taking the first steps afterthe DB2 Partitioned DatabaseEnvironment installation . . . . . . 439Setting up a working collective to distributecommands to multiple AIX nodes . . . . . . 439Updating the node configuration file (Linux andUNIX) . . . . . . . . . . . . . . . . 440

Format of the DB2 node configuration file . . . 441Enabling communications between databasepartition servers (Linux and UNIX) . . . . . . 447Enabling the execution of remote commands(Linux and UNIX) . . . . . . . . . . . . 449

Chapter 21. Response files . . . . . 453

Contents v

Installing database partition servers onparticipating computers using a response file(Windows) . . . . . . . . . . . . . . 453Installing database partition servers onparticipating computers using a response file(Linux and UNIX) . . . . . . . . . . . . 454

Part 5. Installing DB2 productsand features using a response file. 457

Chapter 22. Response file installationbasics . . . . . . . . . . . . . . 459

Chapter 23. Response file uninstallbasics . . . . . . . . . . . . . . 461

Chapter 24. Response fileconsiderations for a DB2 pureScaleenvironment . . . . . . . . . . . . 463

Chapter 25. Creating a response fileusing the DB2 Setup wizard or theDB2 Instance Setup wizard . . . . . 467

Chapter 26. Response file installationof DB2 overview (Linux and UNIX) . . 469Creating a response file using the sample responsefile . . . . . . . . . . . . . . . . . 469Installing a DB2 database product using a responsefile (Linux and UNIX) . . . . . . . . . . 470Installing the DB2 pureScale Feature using aresponse file (AIX and Linux) . . . . . . . . 471Installing database partition servers onparticipating computers using a response file(Linux and UNIX) . . . . . . . . . . . . 472Response file error codes (Linux and UNIX) . . . 473Uninstalling a DB2 database product, feature, orlanguage using a response file (Linux and UNIX) . 474

Chapter 27. Response file installationof DB2 overview (Windows) . . . . . 477Making the DB2 installation files available for aresponse file installation (Windows) . . . . . . 477Setting up shared access to a directory (Windows) 478Editing a response file (Windows) . . . . . . 478Installing a DB2 product using a response file(Windows) . . . . . . . . . . . . . . 479Installation of DB2 products using MicrosoftSystems Center Configuration Manager (SCCM). . 480Response file error codes (Windows) . . . . . 480Response file installation using a batch file(Windows) . . . . . . . . . . . . . . 481Uninstalling a DB2 product, feature, or languageusing a response file (Windows) . . . . . . . 482

Chapter 28. The response filegenerator . . . . . . . . . . . . . 483

Chapter 29. Available sampleresponse files . . . . . . . . . . . 485

Chapter 30. Sample response files(Linux, UNIX, and Windows) . . . . . 487

Chapter 31. Response file keywords 489

Chapter 32. Embedding the DB2installation image (Linux and UNIX) . . 507

Chapter 33. Exporting and importing aprofile . . . . . . . . . . . . . . 509

Chapter 34. Stopping DB2 processesduring an interactive installation(Windows) . . . . . . . . . . . . . 511

Chapter 35. Stopping DB2 processesduring a response file installation(Windows). . . . . . . . . . . . . 513

Part 6. Installing the DB2Information Center . . . . . . . . 515

Chapter 36. DB2 Information Centerinstallation options . . . . . . . . . 517

Chapter 37. Installing the DB2Information Center using the DB2Setup wizard (Windows). . . . . . . 519

Chapter 38. Installing the DB2Information Center using the DB2Setup wizard (Linux) . . . . . . . . 521

Chapter 39. Starting or stopping theInformation Center (Linux andWindows) . . . . . . . . . . . . . 525

Part 7. Installing and upgradingSA MP with the DB2 installer . . . 527

Chapter 40. IBM Tivoli SystemAutomation for Multiplatforms (SAMP) base component . . . . . . . . 529

Chapter 41. License terms for usingIBM Tivoli System Automation forMultiplatforms (SA MP) integratedwith IBM DB2 server . . . . . . . . 531

vi Installing DB2 Servers

Chapter 42. Supported software andhardware for IBM Tivoli SystemAutomation for Multiplatforms (SAMP). . . . . . . . . . . . . . . . 533

Chapter 43. Installing IBM TivoliSystem Automation for Multiplatforms(SA MP) . . . . . . . . . . . . . . 535Installing IBM Tivoli System Automation forMultiplatforms (SA MP) using the DB2 installer . . 535Installing IBM Tivoli System Automation forMultiplatforms (SA MP) using the installSAMinstall script . . . . . . . . . . . . . . 537

Chapter 44. Installing, updating, anduninstalling automated failover scriptsfor the IBM Tivoli System Automationfor Multiplatforms (SA MP). . . . . . 539Installing, updating, and uninstalling automatedfailover scripts for the IBM Tivoli SystemAutomation for Multiplatforms (SA MP) using DB2installer . . . . . . . . . . . . . . . 539Installing, updating, and uninstalling automatedfailover scripts for the IBM Tivoli SystemAutomation for Multiplatforms (SA MP) manually . 540

Chapter 45. IBM Tivoli SystemAutomation for Multiplatforms (SAMP) install and uninstall logs . . . . 543

Part 8. IBM Data Studio integratedinstallation with DB2 databaseproducts . . . . . . . . . . . . . 545

Chapter 46. Installing IBM Data Studiousing the DB2 Setup wizard(Windows). . . . . . . . . . . . . 547

Chapter 47. Installing IBM Data Studiousing the DB2 Setup wizard (Linux). . 549

Chapter 48. Scenario: Installation ofIBM Data Studio components . . . . 551

Part 9. Using the GuardiumInstallation Manager Client . . . . 553

Part 10. Applying fix packs . . . . 555

Chapter 49. Applying fix packs in DB2database environments . . . . . . . 557Fix pack installation methods . . . . . . . . 559

Universal versus product-specific fix packs . . 560Preparing to install a fix pack . . . . . . . . 562

Checking fix pack prerequisites . . . . . . 563Getting fix packs . . . . . . . . . . . 564Uncompressing fix packs (Linux and UNIX) . . 565Uncompressing fix packs (Windows) . . . . 565Stopping all DB2 processes (Linux and UNIX) 566Stopping all DB2 instances, services andapplications (Windows) . . . . . . . . . 567

Installing a fix pack (Linux and UNIX) . . . . . 568Installing offline fix pack updates to existingDB2 database products (Linux and UNIX) . . . 568Installing offline fix packs to add DB2 databaseproducts (Linux and UNIX) . . . . . . . 569

Installing a fix pack (Windows) . . . . . . . 570Installing a fix pack for a single databaseproduct (Windows) . . . . . . . . . . 570Installing a fix pack for multiple databaseproducts (Windows) . . . . . . . . . . 571Installing a fix pack using a response file(Windows) . . . . . . . . . . . . . 571Installing a fix pack in a Microsoft ClusterServer environment (Windows) . . . . . . 572

After installing a fix pack . . . . . . . . . 575Post-installation tasks for fix packs (Windows) 575Post-installation tasks for fix packs (Linux andUNIX) . . . . . . . . . . . . . . . 577Binding bind files after installing fix packs . . 579

Uninstalling fix packs . . . . . . . . . . 581

Chapter 50. Applying fix packs in DB2pureScale environments. . . . . . . 583Fix pack installation methods . . . . . . . . 583Online fix pack updates in DB2 pureScaleenvironments . . . . . . . . . . . . . 584

Database and instance operations affected by anonline fix pack update in progress . . . . . 587

Preparing to install a fix pack . . . . . . . . 588Checking fix pack prerequisites . . . . . . 589Getting fix packs . . . . . . . . . . . 590Uncompressing fix packs (Linux and UNIX) . . 591Stopping all DB2 processes (Linux and UNIX) 592

Installing online fix pack updates to a higher codelevel on a DB2 pureScale instance . . . . . . 593Installing online fix pack updates to a higher codelevel in a HADR environment . . . . . . . . 599Installing online fix pack updates to a higher codelevel in a GDPC environment . . . . . . . . 603Installing offline fix pack updates to a DB2pureScale instance (simplified method) . . . . . 605Installing offline fix pack updates to a DB2pureScale instance (manual method). . . . . . 606Post-installation tasks for fix packs (Linux andUNIX) . . . . . . . . . . . . . . . . 609

Updating an instance to a higher level within arelease using the db2iupdt command . . . . 611Binding bind files after installing fix packs . . 612

Canceling online fix pack updates . . . . . . 614

Part 11. Converting instances . . . 617

Contents vii

Chapter 51. Converting instances to anew DB2 database product . . . . . 619Converting instances from one DB2 databaseproduct to another (Windows). . . . . . . . 619Converting instances from one DB2 databaseproduct to another (Linux and UNIX) . . . . . 620

Chapter 52. Convert instances to theIBM DB2 pureScale Feature . . . . . 623Planning to convert your environment to a DB2pureScale environment . . . . . . . . . . 623Pre-conversion tasks for DB2 pureScaleenvironments . . . . . . . . . . . . . 623

Verifying that your databases are ready for aDB2 pureScale environment . . . . . . . 624Setting up a GPFS file system for a DB2pureScale environment . . . . . . . . . 625Converting table spaces for a DB2 pureScaleenvironment. . . . . . . . . . . . . 627Backing up databases when converting to a DB2pureScale environment . . . . . . . . . 629

Converting your existing DB2 instances to a DB2pureScale environment . . . . . . . . . . 630

Updating an instance to a DB2 pureScaleinstance with the db2iupdt command . . . . 631

Post-conversion tasks for a DB2 pureScaleenvironment. . . . . . . . . . . . . . 632

Adjusting database configuration parameters tomeet DB2 pureScale environment requirements . 633Backing up databases when converting to a DB2pureScale environment . . . . . . . . . 633

Part 12. Uninstalling . . . . . . . 635

Chapter 53. Uninstalling DB2 databaseproducts . . . . . . . . . . . . . 637Uninstalling your DB2 database product (Linuxand UNIX) . . . . . . . . . . . . . . 637

Stopping the DB2 administration server (Linuxand UNIX) . . . . . . . . . . . . . 637Removing the DB2 administration server (Linuxand UNIX) . . . . . . . . . . . . . 638Stopping root DB2 instances (Linux and UNIX) 639Removing DB2 instances (Linux and UNIX) . . 639Removing DB2 database products using thedb2_deinstall and doce_deinstall commands(Linux and UNIX) . . . . . . . . . . . 640

Uninstalling non-root DB2 database products(Linux and UNIX) . . . . . . . . . . . . 641

Stopping non-root instances (Linux and UNIX) 642Removing non-root DB2 database productsusing db2_deinstall (Linux and UNIX) . . . . 642

Uninstalling your DB2 database product(Windows) . . . . . . . . . . . . . . 643Uninstalling DB2 copies and IBM database clientinterface copies . . . . . . . . . . . . . 644Uninstalling a DB2 database product, feature, orlanguage using a response file (Linux and UNIX) . 651Uninstalling a DB2 product, feature, or languageusing a response file (Windows) . . . . . . . 651Uninstalling fix packs . . . . . . . . . . 652

Chapter 54. Uninstalling the DB2pureScale Feature and the DB2database software . . . . . . . . . 653Dropping a member or cluster caching facility . . 653Manually cleaning a DB2 managed clustered filesystem . . . . . . . . . . . . . . . 655

Chapter 55. Uninstalling IBM TivoliSystem Automation for Multiplatforms(SA MP) . . . . . . . . . . . . . . 657Uninstalling IBM Tivoli System Automation forMultiplatforms (SA MP) using the DB2 installer . . 657Uninstalling IBM Tivoli System Automation forMultiplatforms (SA MP) using the uninstallSAMuninstall script . . . . . . . . . . . . . 658Reverting to an earlier version of SA MP in a DB2HADR environment . . . . . . . . . . . 659

Part 13. Appendixes . . . . . . . 661

Appendix A. DB2 technicalinformation . . . . . . . . . . . . 663DB2 technical library in hardcopy or PDF format 664Displaying SQL state help from the command lineprocessor . . . . . . . . . . . . . . . 666Accessing DB2 documentation online for differentDB2 versions . . . . . . . . . . . . . 666Terms and conditions. . . . . . . . . . . 667

Appendix B. Notices . . . . . . . . 669

Index . . . . . . . . . . . . . . . 673

viii Installing DB2 Servers

Part 1. Installation requirements for DB2 database products

Before you install your DB2 database product, ensure that the system you choosemeets the necessary operating system, hardware, software, communications, diskand memory requirements. The db2prereqcheck command checks whether yoursystem meets the prerequisites for the installation.

Important: For the most up-to-date installation requirements for DB2 databaseproducts, you must start using the DB2 for Linux, UNIX, and Windows systemrequirements technote and DB2 Connect system requirement technote. Thesetechnotes use IBM Software Product Compatibility Reports (SPCR). With theSPCR tool, you can locate and find complete lists of supported operating systems,system requirements, prerequisites, and optional supported software for DB2database products.

Disk and memory requirements on page 41The disk space required for your product depends on the type ofinstallation you choose and the type of file system you have. Likewise,memory requirements are affected by the size and complexity of yourdatabase system.

IBM DB2 pureScale FeatureThere is a list of operating system, software, hardware, and firmwareprerequisites that must be met for each operating system, as follows:v Installation prerequisites for DB2 pureScale Feature (AIX) on page 168v Installation prerequisites for DB2 pureScale Feature (Linux) on page

266

DB2 database and IBM data server client productsFor the most up-to-date installation requirements for DB2 databaseproducts, see the DB2 for Linux, UNIX, and Windows system requirementstechnote. For additional installation considerations for each operatingsystem, refer to the following topics:v Additional installation considerations (AIX) on page 67v Additional installation considerations (HP-UX) on page 68v Additional installation considerations (Linux) on page 69v Additional installation considerations (Solaris) on page 76v Additional installation considerations (Windows) on page 58

Note: The minimum screen resolution that is required for a successfulinstallation is 800 pixels by 600 pixels.

Installation requirements for DB2 Connect productsFor the most up-to-date installation requirements for DB2 Connectproducts, see the DB2 Connect system requirement technote. For additionalinstallation considerations for each operating system, refer to the followingtopics:v Installation requirements for DB2 Connect products (Solaris Operating

System) in Installing and Configuring DB2 Connect Serversv Installation requirements for DB2 Connect server products (Windows)

in Installing and Configuring DB2 Connect Serversv Installation requirements for DB2 Connect server products (Linux) in

Installing and Configuring DB2 Connect Servers

Copyright IBM Corp. 1993, 2014 1

http://www-01.ibm.com/support/docview.wss?uid=swg27038033http://www-01.ibm.com/support/docview.wss?uid=swg27038033http://www-01.ibm.com/support/docview.wss?uid=swg27038051http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/softwareReqsForProduct.htmlhttp://www-01.ibm.com/support/docview.wss?uid=swg27038033http://www-01.ibm.com/support/docview.wss?uid=swg27038033http://www-01.ibm.com/support/docview.wss?uid=swg27038051

v Installation requirements for DB2 Connect server products (AIX) inInstalling and Configuring DB2 Connect Servers

v Installation requirements for DB2 Connect server products (HP-UX) inInstalling and Configuring DB2 Connect Servers

Chapter 5, Java software support for DB2 database products, on page 37You require the appropriate level of IBM Software Development Kit (SDK)for Java to use Java-based tools and to create and run Java applications,including stored procedures and user-defined functions.

Virtualization supportFor details about virtualization technology supported by DB2 products, seehttps://www.ibm.com/developerworks/community/wikis/home?lang=en-us#!/wiki/Information%20Management/page/Virtualization%20Support.

Installation requirements for the DB2 National Language Pack (NLPACK)

On Linux and UNIX operating systems, before installing the DB2NLPACK, a DB2 server or client product must already be installed. Thislist of qualified servers or clients include:v DB2 Advanced Enterprise Server Editionv DB2 Enterprise Server Editionv DB2 Advanced Workgroup Server Editionv DB2 Workgroup Server Editionv DB2 Express Server Editionv DB2 Express-Cv DB2 Connect Enterprise Editionv DB2 Connect Personal Editionv Data Server Clientv Data Server Runtime Client

Installation requirements for DB2 Spatial Extender

v System requirements for installing Spatial Extender in Spatial ExtenderUser's Guide and Reference

Installation requirements for InfoSphere Federation Server products

v Hardware and software requirements for Federation Server athttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.prod.install.core.doc/topics/iiypisrq-sys.html

v Hardware and software requirements for Replication Server or DataEvent Publisher at http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.repl.install.doc/topics/iiypirrq-sys.html

2 Installing DB2 Servers

https://www.ibm.com/developerworks/community/wikis/home?lang=en-us#!/wiki/Information%20Management/page/Virtualization%20Supporthttps://www.ibm.com/developerworks/community/wikis/home?lang=en-us#!/wiki/Information%20Management/page/Virtualization%20Supporthttps://www.ibm.com/developerworks/community/wikis/home?lang=en-us#!/wiki/Information%20Management/page/Virtualization%20Supporthttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.prod.install.core.doc/topics/iiypisrq-sys.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.prod.install.core.doc/topics/iiypisrq-sys.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.repl.install.doc/topics/iiypirrq-sys.htmlhttp://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.repl.install.doc/topics/iiypirrq-sys.html

Chapter 1. Checking installation prerequisites by using thedb2prereqcheck command

You can use the db2prereqcheck command to check the software prerequisites of aspecific DB2 version, generate a report file, and perform other tasks.

Using the db2prereqcheck command, you can determine whether your systemsatisfies the DB2 installation prerequisites without having to start the DB2installation. This command checks prerequisites such as operating system level, theLinux distribution, the AIX Technology Level, C library and runtime patches, andprerequisites that are related to the client, uDAPL, GPL, and DB2 pureScale.

The DB2 product comes with the db2prereqcheck binary and the DB2prereqs.xmlfile. These files are found in the folder where the installation image is located.OnAIX operating systems, the DB2prereqs.xml file is in both the db2/aix/install anddb2/aix/bin directories. The DB2prereqs.xml file contains the prerequisite fromVersion 9.8 Fix Pack 2 to Version 10.5. You must not modify the contents of the file.You must run the db2prereqcheck command in the directory where the installationimage is located.

If you run the db2prereqcheck command with no parameters, it determineswhether the system meets the prerequisites for all the DB2 releases and fix packsthat are defined in the resource XML file.

Important: The behavior of the db2prereqcheck command is changed as of DB2Version 10.5 Fix Pack 4. For more information, see "db2prereqcheck - Checkinstallation prerequisites" topic.v To check the prerequisites for the latest DB2 version that you defined in the

resource XML file, issue the db2prereqcheck command with the -i parameter asshown in the following example:$ ./db2prereqcheck -i

v In DB2 Version 10.5 Fix Pack 4 or later, to check the prerequisites for the latestDB2 version that you defined in the resource XML file, issue the db2prereqcheckcommand with -l parameter, as shown in the following example:$ ./db2prereqcheck -l

v To check whether the system meets the prerequisite for the specific DB2 versionthat you defined in the resource XML file, issue the db2prereqcheck commandwith the -v version_number parameter. For example, to check whether theprerequisites are met for DB2 Version 10.5, issue the following command:$ ./db2prereqcheck -v 10.5.0.0

To check whether the prerequisites are met for DB2 Version 10.5 Fix Pack 4,issue the following command:$ ./db2prereqcheck -v 10.5.0.4

v To generate a report file that contains validation information and output fromthe db2prereqcheck command (including a summary section that lists all failingtests), use the -o parameter. Specify the full report file name path togenerate the report in another directory. The prerequisites for installing the DB2product are displayed on the command screen without the -o parameter, as shown in the following example:$ ./db2prereqcheck -v 10.5.0.0 -o report.rpt


v You can use the -f parameter to specify the XML file, as shown in the followingexample:$ ./db2prereqcheck -i -f ./newDB2prereqs.xml

If you do not specify the -f parameter, the default XML file (DB2installation/cfg/DB2prereqs.xml) is used.

v On AIX64 and Linuxamd64 operating systems, to validate prerequisites for aDB2 pureScale installation, use the -p parameter, as shown in the followingexample:$ ./db2prereqcheck -p -v 10.5.0.0

v On Linuxamd64 operating systems, to validate prerequisites for a specificnetwork configuration of a DB2 pureScale installation, use the db2prereqcheckcommand with both the -p and -t options. Youmust set the network configuration type to a single InfiniBand port cluster,multiple InfiniBand port cluster, single RoCE port cluster, or multiple RoCE portcluster (SINGLE_IB_PORT_CLUSTER,MULT_IB_PORT_CLUSTER,SINGLE_ROCE_PORT_CLUSTER, or MULTI_ROCE_PORT_CLUSTER). You can issue thedb2prereqcheck command, as shown in the following example:$ ./db2prereqcheck -v 10.5.0.0 -p -t

Note: For a DB2 pureScale installation on AIX operating systems that use RoCEnetworks, you must check the AIX and uDAPL software prerequisites manually.The db2prereqcheck command does not validate these levels.

If the db2prereqcheck command indicates that the system fails to meet theprerequisite, DBT3507E, as shown in the following example,Validating ofed ...

Required minimum version and release for ofed: 1.5.2-(null)DBT3507E The db2prereqcheck utility failed to verify installation prerequisitesbecause the utility failed to find the following package or file: "ofed".ERROR: Requirement not matched.

check the requirement page under related reference and run it again. For moreinformation, search the DBT message (for example DBT3507E) on V10.5Information Center.

Sample db2prereqcheck command output

The following sample output was generated on a AIX operating system. Use the -pparameter for a DB2 pureScale installation.> db2prereqcheck -p -v 10.5.0.0==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "AIX"

Validating kernel level ...Required minimum operating system kernel level : "6.1".Actual operating system kernel level: "6.1".Requirement matched.

Validating AIX technology level and service pack ...Required minimum technology level: 6 Service pack: 5Requirement matched.

Validating XL C/C++ Runtime ...Required minimum XL C/C++ Runtime level: 11.1.0.1Actual version: 11.1.0.1Requirement matched.


Validating uDAPL ...Required minimum uDAPL level: 6.1.6.1Actual version: 6.1.6.1Requirement matched.

DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database server with DB2 pureScalefeature. Version: "10.5.0.0".

The following sample output was generated on a AIX operating system. Use the -uparameter for DB2 pureScale uDAPL only.> db2prereqcheck -u -v 10.5.0.0==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "AIX"


DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database server . Version: "10.5.0.0".

==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "AIX"


DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database server with DB2 pureScalefeature. Version: "10.5.0

The following sample output was generated on a AIX operating system. Use the -cparameter for a client installation.> db2prereqcheck -c -v 10.5.0.0==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "AIX"




DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database client . Version: "10.5.0.0".

==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "AIX"

Chapter 1. Checking installation prerequisites by using the db2prereqcheck command 5





DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database client with DB2 pureScalefeature. Version: "10.5.0.0".

The following sample output was generated on a AIX operating system. Use the -sparameter to display a validation summary only.> db2prereqcheck -s -v 10.5.0.0DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database server . Version: "10.5.0.0".


The following sample output was generated on a Linux operating system. Use the-p parameter for aDB2 pureScale installation.> db2prereqcheck -p -v 10.5.0.0==========================================================================Checking DB2 Prerequisites for DB2 Version 10.5.0.0 on Linux

Validating Linux distribution ...Required minimum SUSE version : (null) SP (null)

Validating sles-release ...Required minimum version and release for sles-release: 10-15.45.8Actual version of package: 11.1

Requirement matched.

Validating kernel level ...Required minimum kernel level : 2.6.16Actual kernel level: 2.6.32.45Requirement matched.

Validating C++ Library version ...Required minimum C++ library: libstdc++.so.6Standard C++ library is located at: /usr/lib64/libstdc++.so.6.0.10Actual C++ library: CXXABI_1.3.1

Validating 32 bit version of libstdc++.so.6 ...Found the 64 bit /usr/lib64/libstdc++.so.6 at /usr/lib64Found the 32 bit /usr/lib/libstdc++.so.6 at /usr/libRequirement matched.

Validating libc.so version ...


glibc library is located at: /lib64/libc-2.11.1.soRequired minimum glibc library version: 2.4.0Actual glibc library version: 2.11.1Requirement matched.

Validating libaio.so version ...Loading of libaio.so.1 on system succeed.Requirement matched.

Validating ofed ...Required minimum version and release for ofed: 1.5.2-(null)Requirement matched.

Validating sg3_utils ...Package (or file) found: sg3_utilsRequirement matched.

Validating sg_persist ...Package (or file) found: /usr/bin/sg_persistRequirement matched.

DBT3533I The db2prereqcheck utility has confirmed that all installationprerequisites were met for DB2 database server with DB2 pureScale feature.Version: "10.5.0.0".

The following sample output was generated on a Linux operating system. Use the-p and -t parameters to validate prerequisites for a specific network configuration.The output shows the results of validating a single InfiniBand port clusterconfiguration in a DB2 pureScale environment.db2prereqcheck -v 10.5.0.0 -p -t SINGLE_IB_PORT_CLUSTER

Checking DB2 prerequisites for DB2 database version 10.5.0.0 onoperating system "Linux"

Validating Linux distribution ...Required minimum operating system distribution: "RHEL";Version: "5"; Service pack: "6".Actual operating system distribution Version: "6";Service pack: "1".Requirement matched.

...

Validating Infiniband Support Package: libibcm.x86_64 ...Package (or file) found: libibcm.x86_64Requirement matched.

Validating Infiniband Support Package: librdmacm.x86_64 ...Package (or file) found: librdmacm.x86_64Requirement matched.

...

Validating Reliable Scalable Cluster Technology Package:librdmacm.i686 ...Package (or file) found: librdmacm.i686Requirement matched.

Validating Reliable Scalable Cluster Technology Package:libcxgb3.i686 ...Package (or file) found: libcxgb3.i686Requirement matched.

...


DBT3533I The db2prereqcheck utility has confirmed thatall installation prerequisites were met for DB2 databaseserver with DB2 pureScale feature. Version: "10.5.0.0".

The following sample output was generated on a Linux operating system. Theoutput shows the results of validating a multiple RoCE port cluster configurationin a DB2 pureScale environment.db2prereqcheck -v 10.5.0.0 -p -t MULTI_ROCE_PORT_CLUSTER

==========================================================================Checking DB2 prerequisites for DB2 database version 10.5.0.0 on operatingsystem "Linux"

Validating Linux distribution ...Required minimum operating system distribution: "RHEL"; Version: "6";Service pack: "1".Actual operating system distribution Version: "6"; Service pack: "1".Requirement matched.

...

Validating Infiniband Support Package: libibcm.x86_64 ...Package (or file) found: libibcm.x86_64Requirement matched.

Validating Infiniband Support Package: librdmacm.x86_64 ...Package (or file) found: librdmacm.x86_64Requirement matched.

...

Validating High Performance Networking Package: libibverbs-rocee.x86_64 ...Package (or file) found: libibverbs-rocee.x86_64Requirement matched.

Validating High Performance Networking Package: libmlx4-rocee.x86_64 ...Package (or file) found: libmlx4-rocee.x86_64Requirement matched.

Validating Reliable Scalable Cluster Technology Package: libibcm.i686 ...Package (or file) found: libibcm.i686Requirement matched.

Validating Reliable Scalable Cluster Technology Package: librdmacm.i686 ...Package (or file) found: librdmacm.i686Requirement matched.

...


The following sample output was generated on a Linux operating system. For DB2pureScale uDAPL only, use the -u parameter.> db2prereqcheck -u -v 10.5.0.0==========================================================================Checking DB2 Prerequisites for DB2 Version 10.5.0.0 on Linux


Validating sg3_utils ...Package (or file) found: sg3_utils




All requirement matched for DB2 Server version 10.5.0.0 .

==========================================================================Checking DB2 Prerequisites for DB2 Version 10.5.0.0 on Linux




All requirement matched for DB2 Server version 10.5.0.0 DB2 pureScalefeature.

The following sample output was generated on a Linux operating system. Use the-c parameter for a client installation.> db2prereqcheck -c -v 10.5.0.0==========================================================================Checking DB2 Prerequisites for DB2 Version 10.5.0.0 on Linux


Validating sles-release ...Required minimum version and release for sles-release: 10-15.45.8Actual version of package: 11.1





All requirement matched for DB2 Client version 10.5.0.0 .

==========================================================================Checking DB2 Prerequisites for DB2 Version 10.5.0.0 on Linux


Validating sles-release ...Required minimum version and release for sles-release: 10-15.45.8


Actual version of package: 11.1





Validating libc.so version ...glibc library is located at: /lib64/libc-2.11.1.soRequired minimum glibc library version: 2.4.0Actual glibc library version: 2.11.1Requirement matched.




All requirement matched for DB2 Client version 10.5.0.0 DB2 pureScalefeature.

The following sample output was generated on a Linux operating system. Use the-s parameter to display a validation summary only.> db2prereqcheck -s -v 10.5.0.0All requirement matched for DB2 Server version 10.5.0.0 .

All requirement matched for DB2 Server version 10.5.0.0 DB2 pureScalefeature.

The following sample output was generated on a Linux operating system. Use the-nm parameter or the -nl parameter to validate the type of adapter.> ./db2prereqcheck -v 10.5.0.3 -p -nm coralinst09-ib0Validating ....Validating....Validating "Adapter and " ...The db2prereqcheck utility found that Interface Adapter "coralinst09-ib0" is an InfiniBand Adapterwhich is currently RDMA capable on host "coralinst09".


Part 2. DB2 servers and IBM data server clients

A DB2 database system consists of a DB2 server and IBM data server clients.

A DB2 server is a relational database management system (RDBMS) that deliversdata to its IBM data server clients. If you plan to use a database that resides onthis computer, install a DB2 server. For more information about DB2 servers, go tohttp://www.ibm.com/software/data/db2/

An IBM data server client is an application that allows you to run commands andSQL statements against a DB2 server, connect to a remote DB2 server, and accessits databases.

If you are installing the DB2 pureScale Feature, see topic Part 3, Installing a DB2pureScale environment, on page 163.


http://www.ibm.com/software/data/db2/

Chapter 2. An overview of installing DB2 database servers(Linux and UNIX)

This topic outlines the steps for installing your DB2 server product on AIX,HP-UX, Linux, and Solaris.

Procedure

To install your DB2 server product:1. Review your DB2 product prerequisites.2. Review DB2 upgrade information if applicable.3. Modify kernel parameters on HP-UX, Linux, and Solaris. On all platforms,

except for Linux on x86_32, you must install a 64-bit kernel before proceedingwith the installation, otherwise the installation will fail.

4. Prepare the installation media:

Product DVDIf the DB2 product DVD does not automount, mount your DB2 productDVD.

Installation imageIf you downloaded an installation image, untar the file.

5. Install your DB2 product using one of the available methods:v The DB2 Setup wizardv A silent installation using a response filev Payload file deploymentFor DB2 servers, you can use the DB2 Setup wizard to perform installation andconfiguration tasks, such as:v Selecting DB2 installation type (typical, compact, or custom).v Selecting DB2 product installation location.v Install the languages that you can specify later as the default language for

the product interface and messages.v Install or upgrade the IBM Tivoli System Automation for Multiplatforms

(Linux and AIX).v Setting up a DB2 instance.v Setting up the DB2 Administration Server (including DAS user setup).v Setting up the DB2 Text Search server.v Setting up Administration contact and health monitor notification.v Setting up and configuring your instance setup and configuration (including

instance user setup).v Setting up Informix data source support.v Preparing the DB2 tools catalog.v Specify the DB2 Information Center port.v Creating response files.

6. If you installed a DB2 server using a method other than the DB2 Setup wizard,post-installation configuration steps are required.


Chapter 3. An overview of installing DB2 database servers(Windows)

This topic outlines the steps for installing your DB2 server product on Windows.

Procedure

To install your DB2 server product:1. Review your DB2 database product prerequisites.2. Review DB2 database upgrade information if applicable.3. Prepare the installation media:

Product DVDInsert the DB2 database product DVD into your DVD-ROM drive.

Installation imageIf you downloaded an installation image, extract the file.

4. Install your DB2 database product using:v the DB2 Setup wizard.v a silent installation with a response file.You can use the DB2 Setup wizard to perform installation and configurationtasks, such as:v Selecting DB2 database installation type (typical, compact, or custom).v Selecting DB2 database product installation location.v Setting up IBM SSH Server for Windowsv Installing the languages that you can specify later as the default language for

the product interface and messages.v Setting up DB2 Extended Security.v Setting up a DB2 instance (including instance user setup. By default, it is

same as the DAS user).v Setting up the DB2 Administration Server (including DAS user setup).v Setting up the DB2 Text Search server.v Setting up Administration contact and health monitor notification.v Setting up and configuring your instance setup and configuration (including

instance user setup).v Preparing the DB2 tools catalog.v Specifying the DB2 Information Center port.v Creating response files.v Installing additional products.


Chapter 4. Non-root installation overview (Linux and UNIX)

The DB2 installer automatically creates and configures a non-root instance during anon-root installation. As a non-root user, you can customize the configuration ofthe non-root instance during the installation. You can also use and maintain theinstalled DB2 database product without root privileges.

The non-root installation of a DB2 database product has one DB2 instance withmost features enabled by default.

A non-root installation can be attractive for many groups, such as:v Enterprises that have thousands of workstations and users who want to install a

DB2 database product without consuming a system administrator's timev Application developers who are not typically system administrators but use DB2

database products to develop applicationsv Independent Software Vendors (ISVs) who develop software that does not

require root user authority yet embeds a DB2 database product

Although non-root installations have most of the function of root installations,there are some differences and limitations. You can lift some of the limitations byhaving a root user run the db2rfe command.

Differences between root installations and non-root installationsIn addition to a few limitations, the directory structure of a non-root installation isslightly different than the directory structure of a root installation.

During a root installation, subdirectories and files for the DB2 database product arecreated in a directory of the root user's choosing.

Unlike root users, non-root users cannot choose where DB2 database products areinstalled. Non-root installations are always placed in the $HOME/sqllib directory,where $HOME represents the non-root user's home directory. The layout of thesubdirectories within the sqllib directory of a non-root is similar to that of a rootinstallation.

For root installations, multiple instances can be created. Instance ownership isassociated with the user ID under which the instance was created.

Non-root installations can have only one DB2 instance. The non-root installationdirectory contains all of the DB2 database product files and instance files with nosoft links.

The following table summarizes the differences between root installations andnon-root installations.

Table 1. Differences between root installations and non-root installations

Criteria Root installations Non-root installations

User can select installationdirectory

Yes No. DB2 database productsare installed under the user'shome directory.


Table 1. Differences between root installations and non-root installations (continued)

Criteria Root installations Non-root installations

Number of DB2 instancesallowed

Multiple One

Files deployed duringinstallation

Program files only. Instancesmust be created afterinstallation.

Program files and instancefiles. The DB2 databaseproduct is ready for useimmediately afterinstallation.

Upgrade version andinstance

No No need to uninstall the oldversion before installing thenew version. Install newversion, and upgrade theinstance, together.

Limitations of non-root installationsIn addition to the differences between root installations and non-root installations,there are several limitations on non-root installations. This topic discusses thelimitations to help you decide if you want to use a non-root installation.

Product limitationsSome DB2 database products are not supported in non-root installations:v DB2 Net Search Extenderv Locally installed DB2 Information Center

Note: The locally installed DB2 Information Center is not supported innon-root installations because it requires root user authority to start thedaemon. However, a non-root-installation DB2 instance can beconfigured to use a locally installed DB2 Information Center if it isinstalled on the same computer.

Features and tools limitationsThe following features and tools are not available in non-root installations:v The DB2 Administration Server (DAS) and its associated commands:

dascrt, dasdrop, daslist, dasmigr, and dasupdtv The ability for the db2governor to increase priority is not supportedv Automatic starting of non-root DB2 instances at system reboot is not

supported

Health monitor limitationsThe following health monitor features are not supported in non-rootinstallations:v Running script or task actions on alert occurrencesv Sending alert notifications

Partitioned database limitationOnly single-partition databases are supported in non-root installations. Youcannot add additional database partitions.

Listing DB2 database productsThe output produced by the db2ls command, when run as a non-root user,is different than the output produced when run as a root user. For details,refer to the db2ls command topic.


DB2 copiesEach non-root user can have only one copy of a DB2 database productinstalled.

DB2 instance limitationIn non-root installations, one DB2 instance is created during installation.Additional instances cannot be created.

DB2 instance actions can be performed only by the instance ownerRoot installations and non-root installations can coexist on the samecomputer in different installation paths. However, a non-root instance canbe updated, or dropped (using the db2_deinstall command), only by thenon-root user who owns the non-root instance.

A DB2 instance created by a user with root user authority can be updatedor dropped only by a user with root user authority.

Upgrading limitationRoot instances cannot be upgraded to a non-root instance.

Manual kernel parameter updates requiredAutomatic Linux kernel parameter modification is not supported fornon-root installations. Kernel parameters in non-root installations must beupdated manually as described in the "Modifying Kernel Parameters(Linux)" topic.

Post-installation actions can be performed only by the DB2 instance ownerRoot installations and non-root installations can coexist on the samecomputer. However, only the original non-root user who installed the DB2database product can perform subsequent actions such as:v Applying fix packsv Adding featuresv Installing add-on products

Adjusting ulimit valuesThe ulimit command on UNIX and Linux operating systems sets orreports user resource limits, such as data and stack limits. For rootinstances, the database server dynamically updates required ulimit settingswithout changing the permanent settings. However, for non-root instances,the ulimit settings can only be checked during installation. A warningmessage is displayed if the settings are inadequate. Root user authority isrequired to change the ulimit settings.

Limitations that can be overcome by running db2rfe

There are further limitations on non-root installations which can be overcome byrunning the db2rfe command. The following features and abilities are initiallyunavailable in non-root installations:v Operating system-based authenticationv High Availability (HA) featurev The ability to reserve service names in the /etc/services filev The ability to increase user data limits (ulimits). This ability applies only to AIX.

On other operating systems, user data limits must be increased manually.

Run the Enable root features for non-root install command (db2rfe) to enable thesefeatures and abilities. Running the db2rfe command is optional, and must be runby a user with root user authority.

Chapter 4. Non-root installation (Linux and UNIX) 19

Authentication type in non-root installations

Operating system-based authentication is the default authentication type for DB2database products. Since non-root installations do not support operatingsystem-based authentication, if you choose not to run the db2rfe command afterinstalling your DB2 database product as a non-root user, then you must manuallyset the authentication type. You can do so by updating the following parameters inthe database manager configuration (dbm cfg) file:v clnt_pw_plugin (Client userid-password plug-in configuration parameter)v group_plugin (Group plug-in configuration parameter)v srvcon_pw_plugin (Userid-password plug-in for incoming connections at the

server configuration parameter)

Thin server instance topology overview (Linux and AIX)A thin server instance topology or thin server instance environment consists of onenon-root DB2 server instance and one or more thin DB2 server instances. In thistopology, a non-root installation of DB2 database server product is performed onlyon the code server, rather than on each of the DB2 servers in the network. Only aminimal amount of code and configuration is required on each of the DB2 serversthat deploy a thin server instance topology.

You can create a thin server instance either locally on a code server or on a remoteserver.

In the first case, perform a non-root installation of DB2 database server product ona code server and share the DB2 installation path as a read-only copy to othernon-root users in the network through Network File System (NFS). Multiplenon-root users from the same system (code server) can access the read-only copyof the shared DB2 installation path and create a thin server instance locally on thecode server.

For example, if a DB2 database server is installed on System A (code server) by anon-root user db2inst1 and if that installation path is shared through NFS, thenanother non-root user db2inst2, can use the thin server instance environment tocreate an instance from the shared location of System A.


In the second case, perform a non-root installation of DB2 database server producton a code server and share the DB2 installation path as a read-only copy to othernon-root users in the network through NFS (Network File System). Multiplenon-root users from the remote servers that mount the read-only copy of theshared DB2 installation path on the code server can create a thin server instancelocally on the remote servers.

For example, if a DB2 database server is installed on System A (code server) by anon-root user db2inst1 and if that installation path is shared through NFS andmounted on System B (remote server), then another non-root user db2inst3 can usethe thin server environment to create an instance from the shared location ofSystem A.

~/sqllibdb2inst4

~/sqllibdb2inst5

~/sqllibdb2inst2

Code server

~/sqllibdb2inst3

Non-root DB2 installation

/home/db2inst1/sqllibdb2inst1

Figure 1. Thin server instance on code server

Non-root DB2 installation

~/sqllib

db2inst2

Code server Remote server

NFS mounted

~/sqllibdb2inst3

~/sqllibdb2inst4

~/sqllib

db2inst5

/home/db2inst1/sqllibdb2inst1

Remote server

NFS mounted

NFS exported

NFS exported

Figure 2. Thin server instance on remote server


The instances that are created for db2inst2 and db2inst3 have links to the DB2binary files on the shared location of System A. The DB2 configuration-related filesare available as local files on System B.

Thin server instance environment is supported only on Linux AMD 64 bit and AIX64-bit operating systems. It is not supported on Sun SPARC 64 bit, HP IPF 64 bit,Sun Solaris AMD 64 bit, Linux on System z for S/390 64 bit, and Linux PPC64-bit operating systems.

Thin server instance does not support database partition and pureScale features.

Deploying a thin server instance gives you the advantage of reducing the diskspace requirements on multiple systems in the network. You can create, update,drop, list, and upgrade non-root instances on multiple systems by performing anon-root installation only on one system (code server). If you use thin serverinstance environment for managing instances on remote servers, both the codeserver where the DB2 database server is installed and the remote server thatmounts the shared DB2 installation path, must have the same operating system.For example, if the operating system of the code server is aix64, then the operatingsystem of the remote server must also be aix64.

If you use thin server instance on remote server, DB2 programs must be loadedfrom a code server by using a LAN connection. The extent of performance loss atprogram initialization time depends on variables such as the load on speed of boththe network and the code server.

The following table shows the instance commands that are supported formanaging non-root instances in a thin server instance environment.

Table 2. . Commands that are supported on code servers and remote servers in a thinserver instance environment

Systems Supported Not Supported

Code server v db2_deinstallv db2licmv db2nrupdtv db2nrcfgv db2valv db2rspgnv db2ilistv db2ts

v db2icrtv db2iupdtv db2idropv db2iupgradeNote: These commands arenot supported for an instancethat is automatically createdon the code server duringnon-root DB2 installation:

Remote server v db2icrtv db2iupdtv db2ilistv db2idropv db2iupgradev db2ts

v db2_deinstallv db2licmv db2nrupdtv db2nrcfgv db2valv db2rspgn

Setting up a thin server instance environment (Linux and AIX)You can set up a thin server instance environment by performing a non-root DB2installation on a code server and sharing a read-only copy of the DB2 installationpath to other users in the network by using Network File System (NFS).


Before you beginv Ensure that you understand the limitations of non-root DB2 installations. For

more information, see Limitations of non-root installations on page 18

Procedure

To set up a thin server instance environment:1. Log in to the code server as a non-root user.2. Perform a non-root DB2 installation on the code server. For more information,

see Installing DB2 database servers as a non-root user on page 31. Aftersuccessful non-root installation on code server, an instance is created in the userhome directory as shown in the following example:/home/db2inst1/sqllib/

where, db2inst1 is the non-root user name, and /home/db2inst1 is the homedirectory of the non-root user.

3. Share the non-root copy of DB2 installation path on the code server as aread-only copy to other systems in the network by using NFS. Perform one ofthe following set of substeps:v On Linux operating systems, perform the following substeps:

a. Log in to the code server as a root user.b. In the /etc/exports file, add the following entry:

/home/db2inst1/sqllib (ro,sync,no_subtree_check,no_root_squash)

where, /home/db2inst1 is the home of the instance user.c. Start the NFS server by issuing the following commands.

/etc/init.d/nfsserver restart/etc/init.d/portmap restart/etc/init.d/nfslock startexportfs -aexportfs -v

v On AIX operating systems, perform the following substeps:a. Issue the smit nfs command.b. Click the Network File System (NFS) icon.c. Click the Add a Directory to Exports List icon.d. In the PATHNAME of directory to export field, enter the path name and

directory to export, such as /home/db2inst1/sqllib.e. Click the Mode to export directory icon.f. Select read-only.g. In the HOSTS and netgroups allowed client access field, enter the name

of the code server and remote server.h. Click OK.

Mounting a thin server instance (Linux and AIX)In a thin server instance environment, to enable instance management functions onremote servers you must mount the shared DB2 installation path on the codeserver on each of the remote server in the network.




About this task

In a thin server instance environment, a read-only copy of non-root DB2installation path on the code server is exported by using Network File System(NFS). To use the thin server instance on remote servers in the network, you mustcreate a mount point on each of the remote server in the network. The code serverthat exports the file system has the file system mounted locally. This task explainshow to mount the shared DB2 installation path of the code server on the remoteserver.

Procedure1. Log in to the remote server as a root user.2. Perform the following steps.

For Linux:a. Verify that the mount point on the code server is listed from the remote

server as shown in the following example:showmount -e SYSTEM A

where SYSTEM A is the code server.b. Edit the /etc/fstab file on the remote server and add an entry for shared

directory as shown in the following example:SYSTEM A:/home/db2inst1/sqllib /home/db2inst1/sqllib nfs timeo=100 retrans=5,soft,intr,bg,suid,ro,nolock.

where /home/db2inst1/sqllib is the mount point on the remote server.c. Run the mount command from the remote server as shown in the following

example:mount -t nfs SYSTEM A:/home/db2inst1/sqllib/ /home/db2inst1/sqllib

For AIX:a. Enter the smit nfs command.b. Click the Network File System (NFS) icon.c. Click the Add a File System for Mounting icon.d. Enter the path name of the mount point in the PATHNAME of the mount

point (Path) field.The path name of the mount point is where you must create the DB2 homedirectory. For example, /home/db2inst1/sqllib.

e. Enter the path name of the remote directory in the PATHNAME of theremote directory field.You must enter the same value that you entered in the PATHNAME of themount point (Path) field. For example, /home/db2inst1/sqllib.

f. Enter the hostname of the computer where you exported the file system inthe HOST where the remote directory resides field.This value is the host name of the computer where the file system that youare mounting was created. For example, SYSTEM A.

g. Set the MOUNT now, add entry to /etc/filesystems or both? field to both.h. Set the /etc/filesystems entry will mount the directory on system

RESTART field to yes.i. Set the MODE for this NFS file system field to read-only.j. Set the Mount file system soft or hard field to hard.

A soft mount means that the computer does not try for a long period toremotely mount the directory. A hard mount means that your computer tries


for a long period to mount the directory. This might cause problems in theevent of a system crash. It is recommended that you set this field to hard.The remaining fields can be left to the default settings.

k. Set the Allow execution of SUID and sgid programs in this file system?field to No.

l. Click OK.3. Log out of the remote server.

Supported instance management functions in a thin serverinstance environment

As of DB2 Version 10.5 release, instance management functions are enabled fornon-root instances in a thin server instance environment.

The following instance commands are supported in a thin server instanceenvironment. They are not supported for an instance that is automatically createdduring a non-root DB2 installation on the code server.v db2icrtv db2idropv db2iupdtv db2iupgradev db2ilist

Note: The non-root commands such as db2rspgn, db2val, db2iprune, anddb2_deinstall can be used only on the code server. They are not supported for aninstance that is created locally on the remote server.

db2icrt

You can use the db2icrt command to create a non-root instance in a thin serverinstance environment. For more information, see Creating non-root thin serverinstances (Linux and AIX) on page 26-db2icrt--+--------------+--+-- - d + -h-+ - -?- ---+-

db2iupdt

You can use the db2iupdt command to update a non-root instance to a newerversion of DB2 fix pack level in a thin server instance environment. For moreinformation, see Updating non-root thin server instances (Linux and AIX) onpage 28db2iupdt--+---------------+--+-----+--+-----+--+-------------------------------------+--+-----+-- -j--"TEXT_SEARCH-+-------------+-"- +- -h-+ -,portnumber- - -?-

db2idrop

You can use the db2idrop command to drop a non root instance in a thin serverinstance environment. For more information, see Dropping non-root thin serverinstances (Linux and AIX) on page 29-db2idrop--+--------------+--+-- - d + -h-+ - -?- ---+

db2iupgrade


You can use the db2iupgrade command to upgrade the dbm cfg configurations to anewer version in a thin server instance environment. For more information, seeUpgrading non-root thin server instances (Linux and AIX) on page 30-db2iupgrade--+--------------+--+-- - d + -h-+ - -?- ---+-

db2ilist

You can use the db2ilist command, to list the local instance that is created byusing the db2icrt command in a thin server instance environment.

Creating non-root thin server instances (Linux and AIX)You can create non-root thin server instances locally on a code server and on aremote server in a thin server instance environment.



Procedure

To create non-root thin server instances:1. Set up a thin server instance environment on the code server as a non-root user.

For example, db2inst1. For more information, see Setting up a thin serverinstance environment (Linux and AIX) on page 22.

2. Create non-root thin server instances by performing one of the following set ofsubsteps:v To create another non-root thin server instance locally on the code server,

perform the following substeps:a. Log in to the code server as another non-root thin server instance user.

For example, db2inst2.b. Access the read-only copy of the DB2 installation path that is exported

from the code server. For example, /home/db2inst1/sqllib, wheredb2inst1 is the non-root user who owns the DB2 installation on the codeserver, and /home/db2inst1 is the home directory of the non-root instanceowner.

c. Set the library path in one of the following ways: On Linux operating systems, issue the following command:

export LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib/:/home/db2inst1/sqllib/instance/native/install:$LD_LIBRARY_PATH

On AIX operating systems, issue the following command:LIBPATH=/home/db2inst1/sqllib/lib/:/home/db2inst1/sqllib/instance/native/install:$LIBPATHexport LIBPATH

where, /home/db2inst1/sqllib is the read-only copy of the DB2installation path that is exported from the code server.

d. Change directory to the instance directory:cd /home/db2inst1/sqllib/instance

e. Run the db2icrt command:./db2icrt

f. To enable root-based features for the non-root thin server instance on codeserver, perform the following substeps:1) Log in to the code server as a root user.2) Copy the following configuration file to /tmp or another local

directory.


/home/db2inst1/sqllib/instance/db2rfe.cfg

3) Edit the copied db2rfe.cfg configuration file to update theSVCENAME and SET_ULIMIT parameters. This configuration file isinput to the db2rfe command. The following parameters are availablein thedb2rfe.cfg file:INSTANCENAMESET_ULIMIT (* AIX only)ENABLE_OS_AUTHENTICATION

RESERVE_REMOTE_CONNECTIONSVCENAMESVCEPORT

RESERVE_TEXT_SEARCH_CONNECTIONSVCENAME_TEXT_SEARCHSVCEPORT_TEXT_SEARCH

4) Export the local directory by issuing the following command:DB2LOCAL=/home/db2inst2/sqllibexport DB2LOCAL

where /home/db2inst2 is the home directory of the user db2inst2 whoowns the local instance on the code server.

5) Issue the db2rfe command as shown, specifying the copied db2rfe.cfgfile:./db2rfe -f /tmp/db2rfe.cfg

v To create a non-root thin server instance on the remote server, perform thefollowing substeps:a. As a root user, mount the thin server instance on the remote server as a

read-only file system. For more information, see Mounting a thin serverinstance (Linux and AIX) on page 23.

b. Log in to the remote server as a non-root instance owner. For example,db2inst3






e. Run the db2icrt command:./db2icrt

f. To enable root-based features for the non-root thin server instances onremote server, perform the following substeps:1) Log in to the remote server as a root user.2) Copy the following configuration files to /tmp or another local

directory: /home/db2inst1/sqllib/instance/db2rfe /home/db2inst1/sqllib/instance/db2rfe.cfg


3) Edit the copied db2rfe.cfg configuration file to update theSVCENAME and SET_ULIMIT parameters. This configuration file isinput to the db2rfe command. The following parameters are availablein thedb2rfe.cfg file:INSTANCENAMESET_ULIMIT (* AIX only)ENABLE_OS_AUTHENTICATION

RESERVE_REMOTE_CONNECTIONSVCENAMESVCEPORT

RESERVE_TEXT_SEARCH_CONNECTIONSVCENAME_TEXT_SEARCHSVCEPORT_TEXT_SEARCH

4) Export the local directory by issuing the following commands:DB2LOCAL=/home/db2inst3/sqllibexport DB2LOCAL

where,/home/db2inst3 is the home directory of the user db2inst3 whoowns the local instance on the remote server.

5) Issue the db2rfe command as shown, specifying the copied db2rfe.cfgfile:./db2rfe -f /tmp/db2rfe.cfg

Updating non-root thin server instances (Linux and AIX)You can update non-root thin server instances locally on a code server and on aremote server in a thin server instance environment.



Procedure

To update non-root thin server instances:1. Log in to the code and remote servers as the user who owns the instance.2. Stop all instances by using the db2stop command.3. Unmount the thin server instance on the remote server by issuing the following

command:umount /home/db2inst1/sqllib

where, db2inst1 is the default non-root instance owner on the code server,/home/db2inst1 is the home directory of the default non-root instance owner.

4. Log in to the code server as a non-root user.5. Apply fix pack to the non-root DB2 installation on the code server. For more

information, see Installing offline fix pack updates to existing DB2 databaseproducts (Linux and UNIX) on page 568.

6. Update non-root thin server instances by performing one of the following set ofsubsteps:v To update another non-root thin server instance that was created locally on

the code server, perform the following substeps:a. Log in to the code server as another non-root thin server instance user.

For example, db2inst2.b. Access the read-only copy of the DB2 installation path that is exported

from the code server. For example, /home/db2inst1/sqllib, where


db2inst1 is the non-root user who owns the DB2 installation on the codeserver, and /home/db2inst1 is the home directory of the non-root instanceowner.






e. Run the db2iupdt command:./db2iupdt

v To update the thin server instance on the remote server, perform thefollowing substeps:a. As a root user, mount the thin server instance on the remote server as a

read-only file system. For more information, see Mounting a thin serverinstance (Linux and AIX) on page 23.

b. Log in to the remote server as a non-root instance owner. For example,db2inst3






e. Run the db2iupdt command:./db2iupdt

Dropping non-root thin server instances (Linux and AIX)You can drop non-root thin server instances locally on a code server and on aremote server in a thin server instance environment.

Procedure

To drop non-root thin server instances:1. Log in to the code server as non-root user and ensure that the default instance

that was created during non-root installation on the code server, is running andnot dropped.

2. Drop non-root thin server instances by performing one of the following set ofsubsteps:v To drop the non-root thin server instance that was created locally on the code

server, perform the following substeps:a. Log in to the code server as the user who owns the thin server instance.


b. Stop the instance on the code server by issuing the db2stop command.c. Change directory to the instance directory:

cd /home/db2inst2/sqllib/instance

where, /home/db2inst2 is the home directory of the user db2inst2 whoowns the local instance on the code server.

d. Run the db2idrop command:./db2idrop

v To drop the non-root thin server instance on the remote server, perform thefollowing substeps:a. Log in to the remote server as a non-root user who owns the non-root

thin server instance.b. Stop the instance on the remote server by issuing the db2stop command.c. Change directory to the instance directory:

cd /home/db2inst3/sqllib/instance

where, db2inst3 is the instance owner on the remote server, and/home/db2inst3 is the home directory of the instance owner on theremote server.

d. Run the db2idrop command:./db2idrop

Upgrading non-root thin server instances (Linux and AIX)You can upgrade non-root thin server instances on a code server and on a remoteserver in a thin server instance environment.



Procedure

To upgrade non-root thin server instances:1. Log in to the code and remote servers as the user who owns the instance.2. Stop all instances by using the db2stop command.3. Unmount the thin server instance on the remote server by issuing the following

command:umount /home/db2inst1/sqllib

where, db2inst1 is the default non-root instance owner on the code server,/home/db2inst1 is the home directory of the default non-root instance owner.

4. Log in to the code server as a non-root user.5. Perform a non-root installation of DB2 database product on the code server and

upgrade the non-root instance. For more information, see . "Upgrading non-rootinstallations" in Upgrading to DB2 Version 10.5.

6. Upgrade non-root thin server instances by performing one of the following setof subst

DB2InstallingServers-db2ise1051.pdf

Documents

ibm db2

installed db2

db2 marketing

proprietary information

order db2 publications

ibm publications center

local ibm representative

server instance linux