DB2 Version 9 For Linux, UNIX, And Windows

2y ago
1.07 MB
109 Pages
Last View : 1m ago
Last Download : 6m ago
Upload by : Raelyn Goode

DB2 DB2 Version 9for Linux, UNIX, and WindowsGetting started with DB2 installation and administration on Linux andWindowsGC10-4247-00

DB2 DB2 Version 9for Linux, UNIX, and WindowsGetting started with DB2 installation and administration on Linux andWindowsGC10-4247-00

Before using this information and the product it supports, be sure to read the general information under Notices.Edition NoticeThis 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 www.ibm.com/shop/publications/orderv To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwideTo 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 International Business Machines Corporation 1993, 2006. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsAbout this book . . . . . . . . . . . vPart 1. Getting started with DB2installation . . . . . . . . . . . . . 1Chapter 1. Installation prerequisites . . . 3Disk and memory requirements . . . . . . . . 3Getting started with database authorities . . . . . 3Windows installation prerequisites . . . . . . . 5Installation requirements for DB2 clients andservers (Windows) . . . . . . . . . . . 5Security issues when installing the DB2 databasemanager . . . . . . . . . . . . . . . 6Granting user rights (Windows) . . . . . . . 9DB2 system administrator group considerations(Windows) . . . . . . . . . . . . . . 9Extending the directory schema (Windows) . . . 10Linux installation prerequisites . . . . . . . . 11Installation requirements for DB2 clients andservers (Linux) . . . . . . . . . . . . 11Centralized user-management considerations(Linux) . . . . . . . . . . . . . . . 14Automatic database backup . .Automatic statistics collection . 35. 36Chapter 7. DB2 administration anddevelopment tools . . . . . . . . . . 39Basic GUI navigation concepts . . . . . .Getting started with the Control Center . . .Setting up notification and contact lists . . .Getting started with the Command Editor . .Getting started with the Health Center . . .Getting started with the Task Center . . . .Getting started with the Journal . . . . .Getting started with the Configuration AssistantGetting started with the Replication Center . .Getting started with the Web Command CenterGetting started with the Web Health Center .3942464649505254555657Part 3. Appendixes . . . . . . . . . 59Appendix A. Installing DB2 serversusing response files . . . . . . . . . 61Chapter 2. Installation . . . . . . . . 17Response file installation basics . . . . . . . . 61Response file considerations . . . . . . . . . 61Creating a response file using the DB2 Setup wizard 62Installing DB2 servers (Windows) .Installing DB2 servers (Linux) . .Appendix B. Language support . . . . 65.Chapter 3. Verifying your installation. 17. 1923Verifying the installation of DB2 servers using FirstSteps (Linux and Windows) . . . . . . . . . 23Verifying the installation using the command lineprocessor (CLP) . . . . . . . . . . . . . 24Chapter 4. DB2 product licensing . . . 25DB2 product license files . . . . . . .Registering a DB2 product or feature licenseusing the License Center . . . . . . .Checking DB2 license compliance . . . .Upgrading a Try and Buy license . . . .key. 25. 25. 26. 27.656667676871. 71Appendix D. Uninstalling your DB2product . . . . . . . . . . . . . . 73. 31. 31Uninstalling your DB2 product (Windows) . . . .Uninstalling your DB2 products (Linux) . . . . .Removing DB2 products using the db2 deinstallor doce deinstall command (Linux) . . . . .Stopping DB2 instances (Linux). . . . . . .Stopping the DB2 administration server (Linux)Removing the DB2 administration server (Linux)Removing DB2 instances (Linux) . . . . . . 31. 32Appendix E. DB2 Database technicalinformation . . . . . . . . . . . . . 79Chapter 5. Basic administration . . . . 31Chapter 6. Automatic maintenance . . . 35 Copyright IBM Corp. 1993, 2006Appendix C. Installing DB2 fix packsApplying fix packs .Part 2. Getting started with DB2administration . . . . . . . . . . . 29Creating your own database . . . . . . .Database basics . . . . . . . . . .Creating your own database using the CreateDatabase with the Automatic Maintenancewizard . . . . . . . . . . . . .Verifying your new database . . . . .Changing the DB2 interface language (Windows) . .Changing the DB2 interface language (Linux) . . .Supported DB2 interface languages . . . . . .Language identifiers for running the DB2 Setupwizard in another language . . . . . . . . .Displaying the db2setup command in your nationallanguage . . . . . . . . . . . . . . .Overview of the DB2 technical information . . .Documentation feedback . . . . . . . .DB2 technical library in hardcopy or PDF format .73747475757676. 79. 79. 80iii

Ordering printed DB2 books . . . . . . . . .Displaying SQL state help from the command lineprocessor . . . . . . . . . . . . . . .Accessing different versions of the DB2 InformationCenter . . . . . . . . . . . . . . . .Displaying topics in your preferred language in theDB2 Information Center . . . . . . . . . .Updating the DB2 Information Center installed onyour computer or intranet server . . . . . . .DB2 tutorials . . . . . . . . . . . . . .iv82DB2 troubleshooting information .Terms and Conditions . . . . . 87. 888384Appendix F. Notices . . . . . . . . . 89Trademarks . 9184Index . . . . . . . . . . . . . . . 938587Contacting IBM . . . . . . . . . . . 97Getting started with DB2 installation and administration

About this bookThis book provides information on how to install your DB2 product. It alsointroduces DB2 maintenance, administration, and development.For a complete look at the DB2 documentation library, see the DB2 InformationCenter at http://publib.boulder.ibm.com/infocenter/db2help/. Copyright IBM Corp. 1993, 2006v

viGetting started with DB2 installation and administration

Part 1. Getting started with DB2 installation Copyright IBM Corp. 1993, 20061

2Getting started with DB2 installation and administration

Chapter 1. Installation prerequisitesDisk and memory requirementsDisk requirements:The disk space required for your product depends on the type of installation youchoose and the type of file system you have. The DB2 Setup wizard providesdynamic size estimates based on the components selected during a typical,compact, or custom installation.On Windows , you might require significantly more space on FAT (File AllocationTable) drives with large cluster sizes than with NTFS (New Technology FileSystem) drives.Remember to include disk space for required software and communicationproducts.Memory requirements:At a minimum, a DB2 database system requires 256 MB of RAM. For a systemrunning just DB2 and the DB2 GUI tools, a minimum of 512 MB of RAM isrequired. However, 1 GB of RAM is recommended for improved performance.These requirements do not include any additional memory requirements for othersoftware that is running on your system.When determining memory requirements, be aware of the following:v For DB2 client support, these memory requirements are for a base of fiveconcurrent client connections. You will need an additional 16 MB of RAM perfive client connections.v Memory requirements are affected by the size and complexity of your databasesystem, as well as by the extent of database activity and the number of clientsaccessing your system.In DB2 Version 9, the new self-tuning memory feature simplifies the task ofmemory configuration by automatically setting values for several memoryconfiguration parameters. When enabled, the memory tuner dynamicallydistributes available memory resources among several memory consumersincluding sort, the package cache, the lock list and buffer pools.v On Linux , SWAP space at least twice as large as RAM is recommended.Related concepts:v “Self tuning memory” in Performance GuideGetting started with database authoritiesAuthorities provide a way both to group privileges and to control maintenanceand utility operations for instances, databases, and database objects. Users canhave administrative authorities that give full privileges on a set of database objects,or they can have system authorities that give full privileges on managing thesystem but do not allow access to the data. Copyright IBM Corp. 1993, 20063

SYSADM is the highest level of administrative authority. It includes all privilegeson databases within the DB2 instance as well as the authority to grant and revokeall other authorities and privileges.DBADM provides administrative authority for a specific database. It allows theuser to access and modify all objects within that database. A user with DBADMauthority can grant and revoke privileges on the database but cannot grant orrevoke DBADM authority.SYSCTRL is the authority for controlling the resources used by the databasemanager (for example, creating and deleting databases), but it does not allowaccess to the data within the databases.SYSMAINT is the authority for performing maintenance operations, such asstarting and stopping the DB2 server and backing up and restoring databases. Itdoes not allow access to the data within the databases.LOAD authority at the database level, combined with INSERT privilege on a table,allows the user to load data into that table.SECADM (security administrator) level applies at the database level and is theauthority required to create, alter and drop security label components, securitypolicies, and security labels, which are used to protect tables. It is also theauthority required to grant and revoke security labels and exemptions as well as togrant and revoke the SETSESSIONUSER privilege. A user with the SECADMauthority can transfer the ownership of objects that they do not own. TheSECADM authority has no inherent privilege to access data stored in tables andhas no other additional inherent privilege. It can only be granted by a user withSYSADM authority. The SECADM authority can be granted to a user but cannot begranted to a group or to PUBLIC.Database-specific authorities are stored in the database catalogs; system authoritiesare stored in the database manager configuration file for the instance.You can use the Control Center to grant and revoke database authorities.Related concepts:v “Database administration authority (DBADM)” in Administration Guide:Implementationv “Extended Windows security using DB2ADMNS and DB2USERS groups” inAdministration Guide: Implementationv “LOAD authority” in Administration Guide: Implementationv “Security administration authority (SECADM)” in Administration Guide:Implementationv “System administration authority (SYSADM)” in Administration Guide:Implementationv “System control authority (SYSCTRL)” in Administration Guide: Implementationv “System maintenance authority (SYSMAINT)” in Administration Guide:Implementation4Getting started with DB2 installation and administration

Windows installation prerequisitesInstallation requirements for DB2 clients and servers(Windows)For the most up-to-date prerequisite information, seev www.ibm.com/software/data/db2/udb/sysreqs.html.To install a DB2 client or server product, the following operating system, software,and hardware prerequisites must be met:Table 1. Windows installation prerequisitesOperating SystemService PackHardwareWindows XP Professional(32-bit)Service Pack 2 orlaterAll Intel and AMD processorscapable of running thesupported Windows operatingsystems (32-bit and 64-bit)Windows XP Professional x64Windows 2003 Standard Edition(32-bit and 64-bit)Service Pack 1 orlaterWindows 2003 Advanced Edition(32-bit and 64-bit)Windows 2003 DatacenterEdition (32-bit and 64-bit)Additional client considerationsDB2 products continue to be supported on Windows 98, Windows ME,Windows NT , and Windows 2000 until DB2 Universal Database Version8.1 goes out of service. For existing installations and new installations ofDB2 products, upgrading to a more current operating system version ofWindows (such as Windows 2003) is recommended. Version 9 clientscannot be installed on Windows 98, Windows ME, or Windows NT Server4 operating systems. If you wish to continue running DB2 products onback level releases of Windows, you require the following maintenancelevels:v Windows NT Version 4 with Service Pack 6a or laterv Windows 2000 with Service Pack 4 or laterv Internet Explorer 4.01 Service Pack 2Windows XP Service Pack 1 is required for running DB2 applications ineither of the following environments:v Applications that have COM objects using ODBC; orv Applications that use OLE DB Provider for ODBC with OLE DBresource pooling disabledIf you are unsure about whether your application environment qualifies,then it is recommended that you install the appropriate Windows servicelevel.For more information about this COM issue, see the following Microsoft Knowledge Base article:v http://support.microsoft.com/default.aspx?scid KB;EN-US;306414Chapter 1. Installation prerequisites5

Additional software considerationsv MDAC 2.8 is required. The DB2 Setup wizard will install MDAC 2.8 if itis not already installed.vvvvvNote: If a previous version of MDAC (for example, 2.7) is alreadyinstalled, DB2 install will upgrade MDAC to 2.8. For a typicalinstall, MDAC 2.8 is installed. For a compact install, MDAC 2.8 isnot installed. For a custom install, MDAC 2.8 is installed but onlyif you have not deselected the default which is to install it. If youdeselect MDAC as part of a custom install, it will not be installed.If you plan to use LDAP (Lightweight Directory Access Protocol), youshould use either a Microsoft LDAP client or the IBM Tivoli DirectoryServer v6 client (also known as the IBM LDAP client which is includedwith DB2). Prior to installation of the Microsoft Active Directory, youwill need to extend your directory schema using the db2schex utility,which can be found on the installation media.The Microsoft LDAP client is included with the operating system forWindows XP, and Windows Server 2003.If you plan to use the Tivoli Storage Manager facilities for the backupand restoration of your databases, you need the Tivoli Storage ManagerClient Version 4.2.0 or later.– For Windows 64-bit operating systems, you require the TSM clientAPI Version 5.1.If you have the IBM Antivirus program installed on your operatingsystem, it must be disabled or uninstalled to complete a DB2 installation.TCP/IP support must be enabled to view online help.One of the following browsers is required to view online help, run theDB2 install launchpad (setup.exe), and to run First Steps (db2fs):– Internet Explorer 5.5 and up– Mozilla 1.4 and up– Firefox 1.0 and up– Netscape 7.0 and upRelated concepts:v “Support changes for 32-bit and 64-bit DB2 servers” in Migration GuideRelated tasks:v “An overview of installing your DB2 product (Windows)” in Quick Beginnings forDB2 ServersRelated reference:v “IBM Software Development Kit for Java levels for DB2 products” in QuickBeginnings for DB2 Serversv “Communication protocols supported” in Quick Beginnings for DB2 ClientsSecurity issues when installing the DB2 database managerSecurity considerations are important to the DB2 administrator from the momentthe product is installed.To complete the installation of the DB2 database manager, a user ID, a groupname, and a password are required. The GUI-based DB2 database manager install6Getting started with DB2 installation and administration

program creates default values for different user IDs and the group. Differentdefaults are created, depending on whether you are installing on UNIX orWindows platforms:v On UNIX and Linux platforms, if you choose to create a DB2 instance in theinstance setup window, the DB2 database install program creates, by default,different users for the DAS (dasusr), the instance owner (db2inst), and thefenced user (db2fenc). Optionally, you can specify different user namesThe DB2 database install program appends a number from 1-99 to the defaultuser name, until a user ID that does not already exist can be created. Forexample, if the users db2inst1 and db2inst2 already exist, the DB2 databaseinstall program creates the user db2inst3. If a number greater than 10 is used,the character portion of the name is truncated in the default user ID. Forexample, if the user ID db2fenc9 already exists, the DB2 database installprogram truncates the c in the user ID, then appends the 10 (db2fen10).Truncation does not occur when the numeric value is appended to the defaultDAS user (for example, dasusr24).v On Windows platforms, the DB2 database install program creates, by default, theuser db2admin for the DAS user, the instance owner, and fenced users (you canspecify a different user name during setup, if you want). Unlike UNIXplatforms, no numeric value is appended to the user ID.To minimize the risk of a user other than the administrator from learning of thedefaults and using them in an improper fashion within databases and instances,change the defaults during the install to a new or existing user ID of your choice.Note: Response file installations do not use default values for user IDs or groupnames. These values must be specified in the response file.Passwords are very important when authenticating users. If no authenticationrequirements are set at the operating system level and the database is using theoperating system to authenticate users, users will be allowed to connect. Forexample on UNIX operating systems, undefined passwords are treated as NULL.In this situation, any user without a defined password will be considered to have aNULL password. From the operating system’s perspective, this is a match and theuser is validated and able to connect to the database. Use passwords at theoperating system level if you want the operating system to do the authentication ofusers for your database.When working with DB2 Data Partitioning Feature (DPF) on UNIX operatingsystem environments, the DB2 database manager by default uses the rsh utility torun some commands on remote nodes. The rsh utility transmits passwords in cleartext over the network, which can be a security exposure if the DB2 server is not ona secure network. You can use the DB2RSHCMD registry variable to set the remoteshell program to a more secure alternative that avoids this exposure. One exampleof a more secure alternative is ssh. See the DB2RSHCMD registry variabledocumentation for restrictions on remote shell configurations.After installing the DB2 database manager, also review, and change (if required),the default privileges that have been granted to users. By default, the installationprocess grants system administration (SYSADM) privileges to the following userson each operating system:Windows environmentsA valid DB2 database user name that belongs tothe Administrators group.Chapter 1. Installation prerequisites7

UNIX platformsA valid DB2 database user name that belongs tothe primary group of the instance owner.SYSADM privileges are the most powerful set of privileges available within theDB2 database manager. As a result, you might not want all of these users to haveSYSADM privileges by default. The DB2 database manager provides theadministrator with the ability to grant and revoke privileges to groups andindividual user IDs.By updating the database manager configuration parameter sysadm group, theadministrator can control which group of users possesses SYSADM privileges. Youmust follow the guidelines below to complete the security requirements for boththe DB2 database installation and the subsequent instance and database creation.Any group defined as the system administration group (by updating sysadm group)must exist. The name of this group should allow for easy identification as thegroup created for instance owners. User IDs and groups that belong to this grouphave system administrator authority for their respective instances.The administrator should consider creating an instance owner user ID that is easilyrecognized as being associated with a particular instance. This user ID should haveas one of its groups the name of the SYSADM group created above. Anotherrecommendation is to use this instance-owner user ID only as a member of theinstance owner group and not to use it in any other group. This should control theproliferation of user IDs and groups that can modify the instance, or any objectwithin the instance.The created user ID must be associated with a password to provide authenticationbefore being permitted entry into the data and databases within the instance. Therecommendation when creating a password is to follow your organization’spassword naming guidelines.Note: To avoid accidentally deleting or overwriting instance configuration or otherfiles, administrators should consider using another user account, which doesnot belong to the same primary group as the instance owner, for day-to-dayadministration tasks that are performed on the server directly.Related concepts:v “General naming rules” in Administration Guide: Implementationv “User, user ID and group naming rules” in Administration Guide: Implementationv “Authentication” in Administration Guide: Planningv “Authorization” in Administration Guide: Planningv “Naming rules in a Unicode environment” in Administration Guide:Implementationv “Naming rules in an NLS environment” in Administration Guide: Implementationv “Location of the instance directory” in Administration Guide: Implementationv “UNIX platform security considerations for users” in Administration Guide:Implementationv “Windows platform security considerations for users” in Administration Guide:ImplementationRelated reference:v “Communications variables” in Performance Guide8Getting started with DB2 installation and administration

Granting user rights (Windows)This topic describes the steps required to grant user rights on Windows operatingsystems. Specific user rights are recommended for user accounts required to installand set up DB2.Prerequisites:To grant advanced user rights on Windows you must be logged on as a localAdministrator.Procedure:1. Click Start and select Run .2. Type secpol.msc and click OK.3. Select Local Security Policy.4. In the left window pane, expand the Local Policies object, then select UserRights Assignment. the right window pane, select the user right that you want to assign.From the menu, select Action — Security.Click Add, then select a user or group to assign the right to, and click Add.Click OK.If your computer belongs to a Windows 2000 or Windows Server 2003 domain, thedomain user rights may override your local settings. In this case, your NetworkAdministrator will have to make the changes to the user rights.Related concepts:v “User, user ID and group naming rules” in Administration Guide: ImplementationRelated reference:v “Required user accounts for installation of DB2 server products (Windows)” inQuick Beginnings for DB2 ServersDB2 system administrator group considerations (Windows)By default, system administrative (SYSADM) authority is granted to any valid DB2user account that belongs to the Administrators group on the computer where theaccount is defined. If the account is a local account, then it must belong to the localAdministrators group. If the account is a domain account, then it must belong tothe Administrators group at the domain controller or the local Administratorsgroup.For example, if a user logs on to a domain account and tries to access a DB2database, the DB2 database server goes to a domain controller to enumerategroups (including the Administrators group). You can force the DB2 databaseserver to always perform group lookup on the local computer by setting theregistry variable DB2 GRP LOOKUP local and adding the domain accounts (orglobal groups) to the local group.For a domain user to have SYSADM authority, they must belong to the localAdministrators group or the Administrators group at the domain controller. Sincethe DB2 database server always performs authorization at the machine where theChapter 1. Installation prerequisites9

account is defined, adding a domain user to the local Administrators group on theserver does not grant the domain user SYSADM authority to this group.To avoid adding a domain user to the Administrators group at the domaincontroller, create a global group and add the domain users to which you want togrant SYSADM authority to it. Then update the DB2 configuration parameterSYSADM GROUP with the name of the global group.To update the DB2 configuration parameter, enter the following commands:db2 update dbm cfg using sysadm group global groupdb2stopdb2startRelated concepts:v “System administration authority (SYSADM)” in Administration Guide:ImplementationRelated reference:v “sysadm group - System administration authority group name configurationparameter” in Performance GuideExtending the directory schema (Windows)If you plan to use the Lightweight Directory Access Protocol (LDAP) directoryserver feature with Windows 2000 or Windows Server 2003, you should extend theActive Directory schema to contain DB2 object classes and attribute definitions.You should perform this task before you install any DB2 products.Extending the directory schema ensures that:v The default DB2 instance, created during the installation, is cataloged as a DB2node in Active Directory provided the installation user ID had sufficientprivileges to write to Active Directory.v Any databases that the user creates after installation will automatically becataloged into Active Directory.If you decide to install your DB2 product and create databases before you extendthe directory schema, you will have to manually register the node and catalog thedatabases.Prerequisites:Your Windows user account must have Schema Administration authority.Procedure:To extend the directory schema:1. Log onto the domain controller.2. Run the db2schex.exe program from the installation CD with a user accountthat has Schema Administration authority. You can run this program withoutlogging off and logging on again, as follows:runas /user:MyDomain\Administrator x:\db2\Windows\utilities\db2schex.exewhere x: represents the CD drive letter.10Getting started with DB2 installation and administration

When db2schex.exe completes, you can proceed with the installation of yourDB2 product.Related reference:v “Installation requirements for DB2 clients and servers (Windows)” on page 5v “CATALOG LDAP DATABASE command” in Command Referencev “REGISTER command” in Command ReferenceLinux installation prerequisitesInstallation requirements for DB2 clients and servers (Linux)For the most up-to-date prerequisite information, see tml.For the latest information on supported Linux distributions, point your browser tohttp://www.ibm.com/db2/linux/validate.The supported operating systems for Linux include:v Red Hat Enterprise Linux 4 (RHEL4) Update 2v SUSE Linux Enterprise Server 9 (SLES9) Service Pack 2To install a DB2 client or server product, the following distribution requirements,hardware, and communications prerequisites must be met:Table 2. Linux prerequisitesDistribution RequirementsHardwareYou should update your kernel configuration parameters DB2 server products are supported on:in preparation for your Linux distribution. The defaultv x86 (Intel Pentium , Intel Xeon , and AMD Athlon)values for particular kernel parameters are not sufficientv x86–64 (Intel EM64T and AMD64)when running a DB2 database system.v IA64 (Intel Itanium 2 or higher)You may also have other products or applications thatv POWER (any iSeries or pSeries that support Linux)require Linux system resources. You should set thev (Server only)eServer zSeries .kernel configuration parameters based on the needs of– The Database Partitioning Feature (DPF) is notyour Linux system working environment.supported.The kernel configuration parameters are set inv (Client only)64-bit zSeries or System z9 boxes./etc/sysctl.conf. See the Modifying kernel parameters(Linux) section of the DB2 Information Center.Refer to your operating system manual for informationon setting and activating these parameters using thesysctl command.Package requirements (server only):The following tables list the package requirements for SUSE Linux and Red Hatdistributions for DB2 Version 9 partitioned servers.v The pdksh Korn Shell package is required for all DB2 systems.v A remote shell utility is required for partitioned database systems. DB2 supportsthe following remote shell utilities:– rsh– sshChapter 1. Installation prerequisites11

By default, DB2 uses rsh when executing commands on remote DB2 nodes, forexample, when starting a remote DB2 database partition. To use the DB2 default,the rsh-server package must be installed (see table below). For a comparisonbetween rsh and ssh, see the “Security issues when installing DB2” section of theAdministration Guide: Implementation.If you choose to use the rsh remote shell utility, inetd (or xinetd) must beinstalled and running as well. If you choose to use the ssh remote shell utility,you need to set the DB2RSHCMD registry variable immediately after the DB2installation is complete. If this registry variable is not

DB2 administration.29 Chapter 5. Basic administration.31 Creating your own database.31 Database basics.31 Creating your own database using the . Administration Guide: Implementation 4 Getting started with DB2 installation and administration. Windows installation prerequisites Installation requirements for DB2 clients and

Related Documents:

For the first time ever, DB2 functionality which has previously been available on Linux, Unix, and Windows (LUW) is now available for Mac OS X. These DB2 products are available free of charge through the . DB2 Express-C program. The DB2 Express-C program gives you access to a DB2 data server (DB2 Express-C) and DB2 Client for Mac OS X.

db2_install - Install DB2 database product.712 db2_local_ps - DB2 process status for Linux/UNIX 715 db2acsutil - Manage DB2 snapshot backup objects 717 db2addicons - Create main menu entries for DB2 tools .721 db2admin - DB2 administration server .722 db2adutl - Managing DB2 objects within TSM . . 724

Oracle, SQL Server, and Informix Warehouse and Content Management improvements DB2 Evolution IBM DB2 Family Hosts DB2 UDB for OS/390 DB2 for VSE & VM DB2 UDB for AS/400 Personal OS/2 Win 95, 98 Win NT/2000 Linux Enterprise - Extended AIX Linux Win NT/2000 Solaris HP-UX NUMA-Q Workgroup Linux Win NT/2000 OS/2 AIX Solaris HP-UX Enterprise OS/2 .

DB2 Command Line Editor -is an application you can use to run DB2 commands, operating system commands, or SQL statements. Development Center (V8) / DB2 Developer Workbench (V9) -is used to create business logic for databases (stored procedures and user defined functions). Visual Explain (DB2 LUW version included with client ) lets you view the

DB2 Logs, but Were Afraid to Ask Paul Pendle, Rocket Software Session: 16906. Agenda DB2 Logs Introduction DB2 Logging Components Log Performance How to Leverage the DB2 Log DIY Log Analysis DB2 Log Analysis Tool. DB2 Log Introduction Central to every updating transaction

Basic instructions to drop a table in DB2. Examples Basic Drop Table Syntax db2 connect to {databaseName} db2 drop table {schema}.{table} db2 connect reset The schema is not necessary if it matches the current user name. The "db2" prefix is not necessary if you are already in a DB2 command prompt.

Multisystem. . .52 Directed join with DB2 Multisystem.52 Repartitioned join with DB2 Multisystem.53 Broadcast join with DB2 Multisystem . . .54 Join optimization with DB2 Multisystem. . . .55 Partitioning keys over join fields with DB2 Multisystem.55 Implementation and optimization of grouping with DB2 Multisystem.55 One-step .

Linux in a Nutshell Linux Network Administrator’s Guide Linux Pocket Guide Linux Security Cookbook Linux Server Hacks Linux Server Security Running Linux SELinux Understanding Linux Network Internals Linux Books Resource Center linux.oreilly.comis a complete catalog of O’Reilly’s books on Linux and Unix and related technologies .