Home

Up and Running with DB2 on Linux

1. Table space 3 Long data 1 Long data 2 Long data 3 Figure 1 8 DB2 database objects in a partitioned environment You can see that in a partitioned environment the partition groups are expanded transparently across the partitions In Figure 1 8 we show two logical partitions on the first system and one physical logical partition on the second system Table spaces are assigned to one partition group After you add a system ora logical physical partition you merely extend the partition groups that you want to the new partition In Figure 1 8 one partition group spans partition 2 and partition 3 and one partition group spans all three partitions The table data is distributed among the partitions using an updatable partitioning map and a hashing algorithm which determine the placement and retrieval of each row of data For example if a row is being added to a table the coordinator node checks a partitioning map which specifies the database partition where the row is to be stored The row is only sent to that database partition server with the result that only the interested database partition servers take part in the insert This keeps communications and coordination overhead between nodes as low as possible See Figure 1 9 on page 23 Up and Running with DB2 on Linux INSERT 000120 Joe Manager Reg E
2. List of items Product Jean Shirt Figure 8 4 Result of the XSLT transformation in a Browser You can learn more details about pureXML from The pureXML Guide SC23 5871 The Information Center by selecting Database Fundamentals gt pureXML PureXML DB2 9 pureXML Overview and Fast Start SG24 7298 DB2 9 pureXML Guide SG24 7315 vvvy Important UDB 9 5 does not support pureXML in a partitioned database environment 8 5 Application development tools DB2 provides many robust tools for developing DB2 applications In this section we discuss the explain facility design advisor and application development using JBM Data Studio 462 Up and Running with DB2 on Linux In addition to the development tools described in this section the following tools are also supported Rational Application Developer Microsoft Visual Studio Eclipse 3 2 Zend Framework PHP development Alphablox Blox Builder Ruby on Rails vvvvvy For demonstrating the explain facility and the design advisor we add a column EXPLTEST to the EMPMDC table in the SAMPLE database as shown in Example 8 41 Example 8 41 Add a column to EMPMDC for testing EXPLAIN db2inst1 puget gt db2 alter table EMPMDC add column expltest character 20 DB20000I The SQL command completed successfully db2instl puget gt db2 update empmdc set expltest TEST where div 1 DB20000I The SQL command completed successfully db2instl
3. 1 0 spine 0 875 lt gt 1 498 460 lt gt 788 pages Up and Running with DB2 on Linux Experience the power of the integration of DB2 9 5 and Linux Make it easier to get DB2 for LUW up and running on Linux Leverage DB2 powerful autonomic technology Linux is one of the fastest growing server operating platforms within the past few years DB2 has long been known for its technology leadership This IBM Redbooks publication is an informative guide that describes how to effectively integrate DB2 for Linux UNIX and Windows LUW with SUSE and Red Hat Linux operating systems This book provides both introductory and detailed information about installing configuring managing and monitoring DB2 in a Linux environment We describe the DB2 product family and features for Linux and provide step by step instructions for a single as well as for multiple partition DB2 system installation and configuration We describe how to migrate single and multiple partition DB2 to DB2 Version 9 5 and discuss in detail DB2 database administration in a Linux environment procedures and tools for database backup and recovery online maintenance and system monitoring We discuss DB2 integrated tools and their features and use We discuss aspects of DB2 application development in the Linux environment and provide general tips about building and running DB2 applications on Linux and the use of DB2 application development tools
4. Figure 2 5 Root installation Select the installation type 7 On the Select the installation response file creation or both window Figure 2 6 on page 68 we recommend that you select Install DB2 Workgroup Server Edition Version 9 5 on this computer and save my settings in a response file Then click Next Chapter 2 Installation 67 O froot db2ese rsp Figure 2 6 Root installation Select installation response file creation or both 8 On the Select the installation directory window as shown in Figure 2 7 click Next foptfibm db2jv9 5__ sss Figure 2 7 Root installation Select the installation directory 9 On the next windows as shown in Figure 2 8 on page 69 you can choose whether to install IBM Tivoli System Automation or not and then click Next 68 Up and Running with DB2 on Linux Figure 2 8 Root installation Install Tivoli System Automation 10 Set the user information for the DB2 Administration Server as shown in Figure 2 9 on page 70 This user administers the Database Administration Server 11 On the Set up a DB2 instance window select Create a DB2 instance Click Next 12 On the Set up partitioning options for the DB2 instance window Figure 2 10 on page 70 select Single partition instance and click Next Chapter 2 Installation 69 d 997 ome cesusri fhome dasusr1 E TUEA MERIC EE 4 ISP fle Saecirigis Figure 2 10 Root installation
5. Figure B 1 Defining the DB2 Tools Catalog You can choose the system and then create a new Tools Catalog database as shown in Figure B 2 on page 501 500 Up and Running with DB2 on Linux Create New Tools Catalog MENSA l y ESECATO TOOLSCAT sme jv Crit isle gecies RE Figure B 2 Create new Tools Catalog If you want to use the DB2 Command Line Processor we provide a sample to create the Tools Catalog by using the DB2 CLP manually we include the steps to check the DB2 administration server DAS configuration variations before and after creating Tools Catalog and we show the new table spaces and buffer pool created by the CREATE TOOLS CATALOG command automatically Before we create the Tools Catalog we use GET ADMIN CFG to get the current configurations for DAS as shown in Example B 1 You can see that certain parameters that are associated with the Tools Catalog are currently empty including TOOLSCAT_DB TOOLSCAT_INST and TOOLSCAT_SCHEMA We will use this information to compare the DAS configuration changes made by the CREATE TOOLS CATALOG command at a later time Example B 1 Checking the current DAS configuration db2inst1 Mensa gt db2 get admin cfg Admin Server Configuration Authentication Type DAS AUTHENTICATION SERVER_ENCRYPT DAS Administration Authority Group Name DASADM GROUP dasadm1 DAS Discovery Mode DISCOVER SEARCH Name of the DB2 Server System DB2SYSTEM MENSA Appendix B DB2 Tools C
6. v IBM Data Studio K 9 Data Studio Core Features SQL Routine Development XML Development v v Database Object Management v 2 Java Development 4 Java Routine Development Y SQLJ Development v P Web Services Development v Data Web Services WebSphere Application Server Community Edition Installer version 1 1 0 2 ClearCase Enablement X D aaeh E Show Dependencies Required by features you selected Restore Default Details Figure 5 7 Data Studio features 9 The Summary tab Figure 5 8 on page 207 shows all of your installation specifications Review your choices before installing the IBM Data Studio Developer package If you want to change the choices that you have made on previous pages click Back and make your changes When you are satisfied with your installation choices click Install to install the package 206 Up and Running with DB2 on Linux EJ IBM Installation Manager Sex Install Packages rq Review the summary information Click Back to make changes or click Install gt j E Target Location Package Group Name Installation Directory IBM Software Development Platform fopvIBM SDP70 IBM Installation Manager fopt IBM InstallationManager eclipse Shared Resources Directory opt IBM SDP70Shared Features gt Feature s 1BM In
7. 9 On the Set up a DB2 instance window select Create a DB2 instance and then click Next 10 On the Set up partitioning options for the DB2 instance window as shown in Figure 2 17 on page 82 select Multiple partition instance and specify the number of maximum logical partitions By default the number of maximum logical partitions is 4 Local services entries will be added in etc services after this installation and the entries will appear similar to Example 2 26 DB2 reserves four available ports after 60000 for db2inst1 Example 2 26 Local services entries in etc services DB2_db2inst1 60000 tcp DB2_db2inst1_1 60001 tcp DB2_db2inst1_2 60002 tcp DB2_db2inst1_END 60003 tcp When finished click Next Chapter 2 Installation 81 82 Set up partitioning options for the DB2 instance A DB2 instance can have one or more database partitions which exist on one or more computers Select the partitioning options for this instance Single partition instance The instance will reside only on this computer Select this option if the instance will not be used in a partitioned database environment G Multiple partition instance Select this option to prepare to use the partitioning capability of DB2 Enterprise Server Edition Version 9 5 to store data in multiple database lt partitions To use this functionality you must have a Database Partitioning Feature license If you select this option two response files will
8. Copyright IBM Corp 2008 All rights reserved iii iv 2 2 4 Lab environment 0 00 TE EA EEE eee 46 2 2 5 Setting up NFS for a partitioned database environment installation 46 2 2 6 User and group setup 2 eee eae 50 2 2 7 Enabling ssh for a partitioned database environment installation 53 2 3 Installing DBA ieran fede ERR IEA Boe Bit a das adi Bataan wheats 59 2 3 1 Non root installation 0 00 ee eee 60 2 3 2 Root installation a A a E eee 66 2 3 3 Installing a partitioned database environment 79 2 3 4 Installing DB2 license files 0 0 00 e eee eee 87 2 3 5 Installing DB2 documentation 0 00 e eee eee 87 Chapter 3 Post installation tasks 00 0000 c eee 91 3 1 Control Center setup snena saaa c cee 92 3 2 Preparation for the database creation 0000 eee eee 95 3 2 1 Codepage considerations 0 0 0 c cece nes 95 3 2 2 Table space considerations 00000 eee eee eee 96 3 2 3 Linux specific configuration 0 0 0 eee ee eee 103 3 2 4 Multiple partition specific configuration 20 104 3 3 Creating a database 0 cect ee 107 3 3 1 Creating a single partitioned database 004 107 3 3 2 Creating a multiple partitioned database 112 3 4 Further configuration nassau aaaea 120 3 4 1 Change the online log path 0 0000 cee ee
9. Figure 2 3 Non root installation Installation directory Note Because you are performing a non root installation you cannot change the installation directory 8 The Start copying files and create response file window provides a summary of your installation and configuration settings as shown in Figure 2 4 on page 63 Scroll through this window to verify that your settings are correct and then click Finish 9 After installation read the status report tab and check for any errors If there are no errors click Finish 62 Up and Running with DB2 on Linux DB2 Setup DB2 Workgroup Server Edition Version 9 5 Java support SQL procedures Base server support IBM Software Development Kit SDK for Java TM Communication support TCP IP Replication tools DB2 data source support DB2 LDAP support DB2 Instance Setup wizard First Steps Sample database source Languages English All Products Target directory db2home db2inst1 sq Space required 393 MB New instances Instance name db2inst1 Start instance on reboot Yes TCP IP configuration Figure 2 4 Non root installation Installation summary Note In this case the setup logs are located in tmp db2setup_db2inst1 log and tmp db2setup_db2inst1 err Response file install Unlike the DB2 Setup wizard a DB2 response file installation lets you install DB2 products without any user interaction A response file is an English only text file that
10. Figure 8 5 Select Explain Query in the Control Center In the Explain Query panel you can enter the query as shown in Figure 8 6 m e Explain Query Statement SAMPLE select count from empmdc where expltest TEST Figure 8 6 Explain panel Figure 8 7 on page 467 shows the access path in a graphical view You can right click or double click the graphical items to get more details 466 Up and Running with DB2 on Linux A Access Plan Graph SAMPLE Statement Node Yiew Tools Help BSA OOE B awh Section number 65 Explain date and time 02 04 2008 7 36 39 PM Parallelism None Data Joiner No TBSCAN S 323 07 DB2INST 1 EMPMDC Figure 8 7 The access path displayed graphically in Visual Explain 8 5 2 Design Advisor The Design Advisor can help you significantly improve the performance of your queries It takes a set of SQL statements called a workload and suggests ways to improve the performance The suggestions can include Creating new indexes Creating new materialized query tables MQTs Clustering indexes Converting to multidimensional clustering MDC tables Redistributing tables Deleting unused indexes and MQTs vvvvvy There are two ways to call the Design Advisor from the command line by using the command db2advis and from the Control Center Note The Design Advisor is described in detail in Tuning Database Performance SC23 5867 and in the Information Center by selecting Database
11. db2set i lt instance_name gt lt command gt To set registry values for a global level profile issue db2set g lt command gt You can use the Configuration Assistant db2ca or the db2set command to configure configuration parameters and registry variables When updating the registry changes do not affect the currently running DB2 applications or users Applications that are started after the update has happened use the new values Important registry variables Here is a list of important registry variables gt DB2_DISABLE_FLUSH_LOG Default OFF When an online backup has completed the last active log file is truncated closed and made available to be archived which ensures that your online backup has a complete set of archived logs available for recovery gt DB2DBDFT Default null This registry variable specifies the database alias name to be used for implicit connects If any application has no database connection defined but contains an SQL statement it will connect to the database specified in DB2DBDFT Up and Running with DB2 on Linux gt DB2_PARALLEL_IO Default null This variable enables DB2 to read and write I O in parallel for a specific table space or all table spaces The degree of parallelism is determined by the prefetch size and extent size for the containers in the table space gt DB2COMM Default null This variable determines which protocol to use to communicate with DB2 Usually TCP IP between
12. db2top f collect file C m 5 Example 7 12 Running db2top in collection mode for a period db2inst1 mensa software db2top linux_amd_64 gt db2set DB2DBDFT ITSODB db2inst1 mensa software db2top linux_amd_64 gt db2top f collect filelect file C m 5 01 17 26 minute s 01 01 01 01 01 01 01 Exiting 18 18 19 20 21 01 222 22 22 12 54 38 27 19 218 28 28 Starting DB2 snapshot data collector collection every 2 second s max duration 5 max file growth hour 100 0M hit lt CTRL C gt to cancel 1 0M 2 1M 3 4M 4 7M 6 2M 7 8M written time 45 865 82 7M hour written time 88 219 89 7M hour written time 132 572 93 0M hour written time 180 961 95 1M hour written time 233 386 96 2M hour written time 291 876 97 4M hour Max duration reached 8 1M bytes time was 301 956 Snapshot data collection stored in collect file Chapter 7 Monitoring and troubleshooting DB2 395 gt Running db2top in replay mode with automatic performance analysis To analyze the most active sessions issue the following command in another terminal session while db2top is running in collection mode in the first terminal session as shown in Example 7 13 db2top f collect file b 1 A The analysis report will be generated when the job in the first terminal session is finished Example 7 13 Analyzing the most active sessions db2inst1 mensa software db2top linux_a
13. means REORG is recommended For more information regarding the explanation of the output from REORGCHK refer to DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 4 Reorganize the index and table and monitor the procedure of reorganization using the GET SNAPSHOT command In the Index statistics section of the output shown in Example 6 37 on page 293 we can see that both ELEAF and NDEL are greater than 0 294 Up and Running with DB2 on Linux Tip The meaning of ELEAF and NDEL gt ELEAF Number of pseudo empty index leaf pages NUM_EMPTY_LEAFS A pseudo empty index leaf page is a page on which all of the record identifiers RIDs are marked as deleted but they have not been physically removed gt NDEL Number of pseudo deleted RIDs NUMRIDS_DELETED A pseudo deleted RID is a RID that is marked deleted This statistic reports pseudo deleted RIDs on leaf pages that are not pseudo empty It does not include RIDs marked as deleted on leaf pages where all of the RIDs are marked deleted We can use the commands shown in Example 6 38 to physically remove the leaf pages occupied by pseudo delete Example 6 38 REORG INDEXES and REORGCHK to update statistics db2inst1 mensa gt db2 reorg indexes all for table item allow write access cleanup only all on all dbpartitionnums DB20000I The REORG command completed successfully db2inst1 mensa gt db2 reorgchk update statistics on table db2instl item Doi
14. plus much more IBM Data Studio provides the following features gt Common features for DB2 and IDS ER diagramming Data Distribution Viewer Integrated Query Editor SQL Builder XML Editor XML Schema Editor Data Web Services Schema Management Data Management Security Access Controls Project Management gt Common Features for DB2 SQL Routine Debugger Java Routine Debugger gt Common features for DB2 Linux UNIX and Windows LUW and z OS Update Statistics Visual Explain Chapter 5 IBM Data Studio IBM Data Studio Administration Console DSAC introduced in Version 1 2 is a Web based interface to perform operational database management tasks DSAC provides quick analysis and resolution capabilities to identified data server conditions and scenarios With DSAC you can immediately access critical data server information and functions from anywhere at any time In Version 1 2 DSAC functions include gt Health and availability monitoring Problem determination and recommendations 72 hours of history Ability to monitor up to 100 databases gt Q Replication monitoring and administration For more detailed information refer to the following sources gt General information about Data Studio http www ibm com software data studio gt Online documentation of the Data Studio http publib boulder ibm com infocenter dstudio viri
15. All tables including system tables Configure Settings 4 Back Next gt Finish Cancel Figure 6 19 Select maintenance activity 6 Use Configure Settings to specify the tables from which you want to automatically collect statistics or the tables that you want to automatically reorganize Note Using the Configure Automatic Maintenance wizard you can specify your maintenance objectives The database manager uses these objectives to determine whether the maintenance activities need to be performed and runs only the required maintenance activities during the next available maintenance window a time period that you define Automatic statistics collection Automatic statistics collection helps improve database performance by ensuring that you have up to date table statistics The database manager determines which statistics are required by your workload and which statistics need to be updated The DB2 optimizer uses these statistics to determine which path to use to access the data Chapter 6 Administering databases 279 Statistics can be collected either asynchronously in the background or synchronously by gathering runtime statistics when SQL statements are compiled By default automatic statistics collection is set to ON Real time statistics gathering can be enabled only when automatic statistics collection is enabled Real time statistics gathering is controlled by the AUTO_STMT_
16. Example 8 15 Activate the UDF CREATE FUNCTION to_lower VARCHAR 40 RETURNS VARCHAR 40 FENCED EXTERNAL NAME tolower to_lower NOT VARIANT NO SQL PARAMETER STYLE DB2SQL LANGUAGE C NO EXTERNAL ACTION After that the UDF can be used as demonstrated in Example 8 16 Example 8 16 Execute the UDF db2inst1 puget gt db2 select to_lower AAA from sysibm sysdummy1 1 record s selected If you want to drop the function you can run the command db2 DROP FUNCTION to_lower VARCHAR 40 UDFs can be run in fenced or not fenced mode Fenced routines run as a separate process They have some communication overhead involved Not fenced routines run as part of the database server They are a little bit more efficient than fenced routines However if a not fenced routine crashes it will bring down the database server too Therefore we suggest that you develop routines in fenced mode You can consider running well tested routines on production systems as not fenced routines if performance is important Up and Running with DB2 on Linux 8 3 4 Java Fenced routines can also be run under a different user ID which allows you to secure them from the other instance files While developing the UDFs set the database manager parameter KEEPFENCED to NO so that each call to the UDF will reload the function Note You can obtain more information about UDFs in Developing User defined Routines SQL and External SC23 5855 Java is
17. 5 6 7 8 9 10 11 sqlstate 7 4 3 Operating system log The Linux operating system also has system utilities that provide support for system logging and kernel message trapping Among those utilities syslogd provides a type of logging that many modern programs use Every message that is logged by syslogd normally contains at least a time and a host name field plus a program name field but that depends on the dependability of the logging program The syslog conf file which is located in the etc directory is the main configuration file for the syslogd It specifies the rules for logging by syslogd It is a text file and you can edit it with any favorable text editor to make it applicable to your environment or you can simply use the default values which were set during the Linux installation It is a good practice to check the system log file the file might be named var log messages if you have not changed the default configuration when you face a problem if you are unsure whether the problem is related to the system setting For more information regarding how to set up syslog conf and how to interpret the system log refer to the Linux specific documentation Note Instead of the syslogd package SUSE Linux 10 installs the syslog ng package by default The syslog ng conf file is the main configuration file and is located in etc syslog ng directory 7 5 DB2 Tools for troubleshooting The DB2 product comes with seve
18. Chapter 4 Migration and fix packs 183 2 Migrate the instance that owns the tools catalog database using the procedure that is described in 4 2 3 Migrating instances and databases on page 178 In Example 4 14 on page 183 our instance is dpfusr1 which has already been migrated 3 Migrate the tools catalog database using the steps that are provided in 4 2 3 Migrating instances and databases on page 178 Example 4 15 shows migrating the tools catalog database in our lab Example 4 15 db2tdbmgr dpfusr1l gemini gt db2tdbmgr d toolsdb s cc Tools catalog database migrated successfully to the current level Tools catalog creation If you do not have a tools catalog yet you can create a new one now You can use an existing database or create a new one This database must be local The syntax to create a new database is cc db2 create tools catalog lt catalog_name gt create new database lt database_name gt in the previous command catalog_name is used to identify the DB2 Tools catalog and database_name is the new database Example 4 16 shows how to create a tools catalog database Example 4 16 Tools catalog tables creation in a new database dpfusr1l gemini gt db2 create tools catalog cc create new database toolsdb DB20000I The CREATE TOOLS CATALOG command completed successfully 4 2 7 Migrating DB2 clients 184 After the DB2 server is migrated we recommend that you migrate the DB2 clients
19. Load Wizard ITEMLOAD Figure 6 39 Define column related properties for the load 7 Specify performance and statistics collection options Figure 6 40 on page 332 You can specify options that will impact load performance For example you can specify how the load utility will update the existing indexes rebuild all indexes or rebuild indexes incrementally A full index rebuild is faster than an incremental rebuild If the index is extremely large it will be quicker to perform an incremental rebuild In addition options for statistics collection are also provided in this panel If you do not want to make any modifications take the the defaults Chapter 6 Administering databases 331 Load Wizard TEMLOAD F ggasi gnicie anin E a jop iela erajn lt default gt Figure 6 40 Specify performance and statistics collection options 8 Specify failure options and recovery strategy Options regarding failure handling and recovery strategy are covered in this panel For example if you want the whole load operation to halt when any error occurs during the load operation you can check both boxes for error isolation load job fails and load rollback in the Crash recovery section as shown in Figure 6 41 on page 333 332 Up and Running with DB2 on Linux Load Wizard ITEMLOAD Facai smene saints aiel janaria rove count agaaa ellirinie elect Higar OF POS Sanya aonane Jona lias Figure 6 41 Specify failure options
20. NZ Instance home mounted db2home lt instance gt Local database files Local database files DMS database database db2log1 db2lo0g1 db2log2 db2log2 db2logarc db2logarc Figure 3 4 Partition and file system layout for partitioned databases The setup of db2home lt instance gt and the file system structure for one partition is shown in 2 2 3 Storage planning on page 40 You must configure the file system structure in the same way on the second system too For performance and availability reasons we recommend that you avoid putting user data on the catalog partition When restoring the catalog partition the restore is faster when there is no data on it db2nodes cfg To define which hosts are participating in a partitioned environment you have to modify the db2nodes cfg file located in INSTHOME sqllib The format of the db2nodes cfg file is nodenum hostname logical_port In this format nodenum represents the partition number hostname represents the host name or IP address of the physical machine and ogical_port represents the logical port number of the partition on the same host Chapter 3 Post installation tasks 105 106 In our example we have two machines that each hold one database partition The host mensa will be partition 0 and gemini will be partition 1 Example 3 8 shows the contents of db2nodes cfg for our setup
21. Parameters Results Profiling Data v Success Deploy EMPSALARY ee Buces SHUN EmpSalary sql SCHNEIDER E11 OPERATIONS 200810 SPRINGER E11 OPERATIONS 000310 SETRIGHT E11 OPERATIONS 000230 PARKER E11 OPERATIONS 200630 WONG E21 SOFTWARE SUPPORT 200040 ALONZO E21 SOFTWARE SUPPORT Figure 8 38 Run the stored procedure Alternatively you can run the stored procedure from the command line by entering the following command db2 call EMPSALARY 37000 If you want to debug the procedure set a breakpoint in the procedure select Debug instead of Run when you right click EMPSALARY The Run Configuration window is presented See Figure 8 39 on page 490 Chapter 8 Application development 489 ka AIDA OCOC F Apache Tomcat Project name DataProject Browse DB2 Stored Procedure Location URL jabe db2 crater 50001 SAMPLE retrieveMessagesFromServerOnGetMessage true 1 DB2INST1 EMPSAI URL Jj rater ieveMessag jessage true Eclipse Application Procedure oeansti EMPSALARY Browse Equinox OSGi Framewor Argument lst foo Edit 8 Generic Server F Generic Server External E Java Applet v D Java Application C New_configuration Ju JUnit Jf JUnit Plug in Test Z Remote Java Application e swr Application 37 Name DB2INST1 EMPSALARY INTEGER DataProject Figure 8 39 Run configuration Here you can change the
22. TCPIP To TCPIP Example 7 17 shows a log message extracted from db2diag log It is written into the log file when running the following DB2 commana db2 update db cfg for ITSODB using NEWLOGPATH db2log This message shows that the SQLCODE is 5099 with tokens db2log NEWLOGPATH 9 which are highlighted in bold in our example Use the db2 sq15099 command to check the meaning of SQL5099 This code tells us that reason code 9 means The path cannot be accessed In our example the path cannot be accessed because the write access permission of db2log is only assigned to the root user The user db2inst1 is not permitted to create a subdirectory under db2log After issuing the command chown R db2inst1 db2iadm1 db21og as root user the problem is resolved Example 7 17 Message about setting NEWLOGPATH 2008 02 14 10 32 09 904898 480 11578E825 LEVEL Error PID 25392 TID 47735688390976PROC db2sysc 0 INSTANCE db2inst1 NODE 000 400 Up and Running with DB2 on Linux APPHDL 0 7433 APPID NO db2inst1 080214183209 AUTHID DB2INST1 EDUID 1129 EDUNAME db2agent instance 0 FUNCTION DB2 UDB config install sqlfPdbUpdDbCfgReq probe 923 DATA 1 SQLCA PD_DB2_TYPE SQLCA 136 bytes sqlcaid SQLCA sqlcabc 136 sqlcode 5099 sqlerrml 20 sqlerrmc db2log NEWLOGPATH 9 sqlerrp SQL09050 sqlerrd 1 0x00000000 2 0x00000000 3 0x00000000 4 0x00000000 5 0x00000000 6 0x00000000 sqlwarn 1 2 3 4
23. chown root root ssh keysign chmod 4755 usr 1libexec openssh ssh keysign Setting up public key authentication Public key based authentication allows a single user ID in our case the DB2 instance owning ID in our partitioned database environment to log in as the same user ID on each partition server without being prompted for a password Because the home directory of DB2 partitioned instance owner is shared across all machines a prerequisite for a DB2 partitioned database environment it is possible to complete the entire setup from a single machine The steps to set up public key authentication are 1 Create the ssh directory Log in as the DB2 partitioned instance owning user ID If this ID does not already have a ssh directory create one and ensure that the ssh directory does not allow group or other write access At the same time ensure that your home directory does not allow group or other write access ssh views this as a security exposure and will not allow public key based authentication if the directory permissions are not sufficiently restrictive On our testing environment mensa the instance owning ID is db2inst1 and the home directory is db2home db2inst1 We create the ssh directory with required authorization as shown in Example 2 16 Example 2 16 mkdir ssh directory for user db2inst1 log in as db2inst1 cd db2home chmod 700 db2instl mkdir ssh chmod 700 ssh 2 Generate a key pair From th
24. gt db2start 02 06 2008 16 58 39 0 0 SQL1063N DB2START processing was successful SQL1063N DB2START processing was successful db2instl gemini gt db2level DB21085I Instance db2instl uses 64 bits and DB2 code release SQL09050 with level identifier 03010107 Informational tokens are DB2 v9 5 0 0 s071001 LINUXAMD6495 and Fix Pack 0 Product is installed at opt ibm db2 V9 5 db2inst1l gemini temp gt db2 create database itso automatic storage yes on database db2inst1 USING CODESET UTF 8 TERRITORY BR collate using SYSTEM_819 BR DB20000I1 The CREATE DATABASE command completed successfully Create database objects using the edited DDL db2inst1l gemini temp gt db2 tvf unidb ddl db2inst1l gemini temp gt db2move itso import Application code page not determined using ANSI codepage 1208 kkkkk DB2MOVE kkkkk Action IMPORT Start time Wed Feb 6 17 07 16 2008 Chapter 4 Migration and fix packs 193 Connecting to database ITSO successful Server DB2 Common Server V9 5 0 Binding package automatically home db2inst1 sqllib bnd db2common bnd successful Binding package automatically successful IMPORT table DB2INST1 LOCATION Rows read 2 Inserted 2 Rejected 0 Committed 2 IMPORT table DB2INST1 BRAND Rows read 2 Inserted 2 Rejected 0 Committed 2 IMPORT table DB2INST1 CUSTOMER Rows read 2 Inserted 2 Rejected 0 Comm
25. 20000 DAYS AS HIREDATE INTEGER 10000 RAND 200000 AS SALARY FROM tmpinfo db2inst1 mensa db2home db2inst1l script gt db2 tvf ins_empinfo db2 INSERT INTO db2instl empinfo WITH tmpinfo ID AS VALUES 1 UNION ALL SELECT ID 1 FROM tmpinfo WHERE ID lt 280000 SELECT ID TRANSLATE CHAR INTEGER RAND 1000000 CASE MOD ID 4 WHEN O THEN aeiou bcdfg WHEN 1 THEN aeiou hjkim WHEN 2 THEN aeiou npqrs ELSE aeiou twxyz END 1234567890 AS LASTNAME CURRENT DATE RAND 20000 DAYS AS HIREDATE INTEGER 10000 RAND 200000 AS SALARY FROM tmpinfo DB200001 The SQL command completed successfully Check the notification that is sent by the DB2 system After the DB2 Health Monitor detected that the threshold for warning or alarm has been exceeded it will send warning or alarm messages to the DB2 administration notification log as well as specified contacts if you have configured notifications In our example the notification will be sent to the notification log and to a contact point through e mail We can use the DB2 Journal to check the administration notification log To start the DB2 Journal select Tools gt Journal in any DB2 Tools panel where the Tools menu is available Or from Health Center right click the instance name and select Show Notification Log Then select the Notification Log tab and choose Instance to view the notification log The instance in our example is dbo2inst1 The n
26. Considerations Mixing the server and client version will reduce the capability of using DB2 server functionality Table 4 3 on page 185 shows DB2 9 5 connectivity support Up and Running with DB2 on Linux Table 4 3 Supported connectivity Client connectivity support 32 bit or 64 bit 32 bit or 64 bit Any DB2 9 5 clients can establish 32 bit or DB2 9 5 clients DB2 9 5 server 64 bit connections and use full DB2 9 5 functionality 32 bit or 64 bit Only DB2 9 1 functionality is available DB2 9 1 server 32 bit or 64 bit Only DB2 UDB Version 8 functionality is DB2 UDB available Version 8 server 32 bit or 64 bit 32 bit or 64 bit Only DB2 Version 9 1 functionality is DB2 9 1 clients DB2 9 5 server available 32 bit or 64 bit 32 bit or 64 bit Only DB2 UDB Version 8 functionality is DB2 Version 8 DB2 9 5 server available clients If you have a Version 8 client in the same machine as a DB2 9 5 server or a DB2 9 5 client in a Version 8 server connections to the server from the client using the local node IPC are not supported We recommend that you migrate this client to DB2 9 5 You cannot choose the bit size of a client instance the size is determined by the operating system Migrating DB2 server for Linux supports DB2 clients on UNIX and Windows platforms In this section we provide the migration methods for migrating DB2 clients for Linux and Windows Table 4 4 on page 186 summaries how you can migrate various
27. SVCENAME 137 swap space 420 symmetric multi processor 17 syntax 494 syscatspace 170 sysctl 31 516 Up and Running with DB2 on Linux syslog 497 syslog conf 401 syslogd 401 sysstat package 419 system activity report sar 420 system configuration 35 system managed space SMS 16 system managed storage SMS 40 system managed table spaces 98 T table 16 table function 429 table space 15 16 35 362 tasks view 214 TCP IP 78 team function 216 temporary table space 45 97 TEMPSPACE1 170 threshold 355 timestamp 456 tools catalog 184 Top 414 traceback 497 TRACKMOD 229 transactional enterprise system 2 transactional integrity 438 transfer rate 420 trigger 428 triggering action 428 tutorial session 225 Type 4 driver 451 Typical 61 typical 28 66 80 U UDFs 4 UDTs 177 Unified ODBC 439 UNIX 497 user defined functions UDFs 428 user table space 97 user defined types 177 UTF 8 96 V version recovery 255 view variable 490 virtual memory 417 418 Visual Explain 199 VM VSE 12 Ww Web 2 0 198 Web application 438 Web browser 209 Web services 198 Web browser 12 workload management 5 workspace 211 workspace location 211 X X server 93 XML 217 XML attributes 455 XML document 455 XML Editor 199 XML Schema Editor 199 XML structure 455 XSD 217 XSD document 217 Index 517 518 Up and Running with DB2 on Linux Redbooks Up and Running with DB2 on Linux
28. System out printIn e getMessage nSQLCode e getErrorCode SQLState e getSQLState catch ClassNotFoundException e System out printIn e getMessage Example 8 20 shows how to compile and run the SQLJ program Example 8 20 Compile and run an SQLJ program db2inst1l puget DB2JAVA home db2inst1 sqllib java gt db2inst1 puget gt export PATH DB2JAVA jdk32 bin PATH gt db2inst1 puget sqlj test_sqlj sqlj db2instl puget gt db2sqljcustomize url jdbc db2 localhost lt port gt SAMPLE user db2instl password lt password gt test_sqlj_SJProfile0 ser jcc sq jcc sql jcc sq jcc sq jcc sq jcc sq jcc sq i i i i i i i Begin Customization Loading profile test_sqlj_SJProfile0 Customization complete for profile test_sqlj_SJProfile0 ser Begin Bind Loading profile test_sqlj_SJProfile0 Driver defaults user may override BLOCKING ALL VALIDATE BIND STATICREADONLY YES jcc sq jcc sq jcc sql jcc sq jcc sql jcc sq i i i i i i Fixed driver options DATETIME ISO DYNAMICRULES BIND Binding package TEST_S01 at isolation level UR Binding package TEST S02 at isolation level CS Binding package TEST_S03 at isolation level RS Binding package TEST_S04 at isolation level RR Bind complete for test_sqlj_SJProfiled db2instl puget gt DB2JAVA jdk32 bin java classpath DB2JAVA db2jcc jar test_sqlj
29. The zipped output file db2support zip is in the current directory You can send this file to your DB2 technical service representative for analysis Note If the c option is used the utility will establish a connection to the database 7 6 Linux system monitoring tools There are many Linux system monitoring tools available to help you identify where a performance or system setting issue occurs You can use these tools to monitor system resource usage such as disk I O memory consumption CPU activities and network status Through the utilization of the comprehensive information that is provided by these operating system tools combined with the database system monitoring tools from DB2 you can understand your system more clearly For example you can identify which table space containers are under high disk I O pressure whether the excessive sort heap allocation will lead to a mass of paging space activities if the network bandwidth is the bottleneck causing the poor response time of client applications and so on Then you can make pertinent adjustments to your applications database system or operating system to improve the system performance In this section we discuss several of the most commonly used performance monitoring tools for the Linux platform top iostat vmstat and sar 7 6 1 The top utility 414 The top utility is a useful tool that provides a lot of information on one display Top can show you which process is t
30. To create and configure the DB2 home file system to NFS 1 If you have not already done so create the DB2 home file system for example export db2home on the NFS server by using utilities such as fdisk to create the disk partition and mkfs to create the file system on the disk partition or the YaST tool on SUSE 2 Locally mount the DB2 home file system using the following command mount export db2home 3 Make sure that your new file system has been added to the etc fstab file which will mount the file system each time that the system is restarted Most Linux file system creation utilities for example Disk Druid or YaST automatically add an entry to the etc fstab file when you create a new file system If your DB2 home file system is not found in the etc fstab file you can add it manually In etc fstab you will see an entry for export db2home In our setup the entry is dev sdb5 export db2home ext3 data journal acl user_xattr 12 4 Next add an entry to the efc exports file to automatically export the NFS file system at startup You only need to set up this file on your NFS servers The etc exports file follows this format directory_to_export machinel_name permissions machine2_name permissions machinen_name permissions For example in our etc exports file we have export db2home mensa rw no_root_squash sync gemini rw no_root_squash sync Up and Running with DB2 on Linux Note In the permissions
31. because it cannot be changed easily afterwards A later change requires recreating the database and a data migration using db2look and db2move UTF 8 offers support for all languages and is the best choice if you have to provide worldwide access to your application If you support only your local country and your country uses a single byte codepage you probably want to choose a single byte codepage for your database A database created for a single byte codepage requires less storage If you must support several countries with single byte codepages which can be converted between each other you might want to choose a single codepage for your database It depends on the number of conversions that you have to perform in your architecture If you use pureXML or if you have UTF 8 clients set up your database as UTF 8 The simplest approach however is if your whole architecture was set up for UTF 8 3 2 2 Table space considerations In this section we describe the various types of table space containers and when it is appropriate to use them 96 Up and Running with DB2 on Linux General table space considerations By default DB2 creates three table spaces gt gt gt The catalog table space which stores the catalog tables The user table space which stores all table and index data The temporary table space which is used for storing temporary data while SQL statements are being processed However it makes sense to
32. button 328 Up and Running with DB2 on Linux Load Wizard ITEMLOAD Haan aeiia icine Of aar atin reelection ori elects db2backup datamove item del ea db2backup datamove loadcc msg ey Figure 6 37 Specify input and output files 5 Specify which database partitions participate in the load Figure 6 38 on page 330 You can use the default choice of Load data into all database partitions if you just want to load data into all of the database partitions where the table resides Under certain conditions you might want to load data for a specific database partition or partitions therefore you can choose to Load data into selected database partitions Under Distributing partitions you can specify which database partitions will be used to do the data partitioning work In general you can choose to just Let DB2 decide which database partitions participate Chapter 6 Administering databases 329 Load Wizard ITEMLOAD SEJE Figure 6 38 Specify which database partitions participate in the load 6 Define the input columns and their mapping to the output columns Figure 6 39 on page 331 You can simply use the default mapping if you think the default mapping is appropriate for your situation or you can make modifications in this panel if needed For example if large objects LOBs are involved in your load you might need to specify LOB related options here 330 Up and Running with DB2 on Linux
33. db2 connect reset DB20000I1 The SQL command completed successfully db2inst1 mensa gt db2 backup db itsodb on all dbpartitionnums to db2backup Part Result 0000 DB20000I The BACKUP DATABASE command completed successfully 0001 DB20000I The BACKUP DATABASE command completed successfully Chapter 6 Administering databases 269 Backup successful The timestamp for this backup image is 20080207095407 db2inst1 mensa gt db2 connect to itsodb Database Connection Information Database server SQL authorization ID Local database alias DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB db2inst1 mensa gt db2 drop table tabl DB200001 The SQL command completed successfully db2instl mensa gt db2 select from tab1 SQLO204N DB2INST1 TAB1 is an undefined name SQLSTATE 42704 db2instl mensa gt db2 connect reset DB200001 The SQL command completed successfully To recover the dropped table tab1 follow this procedure 1 Restore the table space in which the dropped table is stored from a database or a table space backup Note that the whole table space is restored which also means that the other tables in that table space are restored and later rolled forward to the current state In our example the dropped table was in table space TSDATA1 which resides in database partitions 0 and 1 In Example 6 29 we restore the table space from the last full backup image Example 6 29 Table space restore for all database partitions db
34. db2inst1 mensa gt db2 CREATE TABLE DB2INST1 TAB1 ID INTEGER NOT NULL NAME CHAR 10 DISTRIBUTE BY HASH ID IN TSDATA1 DB200001 The SQL command completed successfully db2inst1 mensa gt db2_all lt lt 0 lt db2 connect to itsodb db2 import from db2backup rest_table NODEO000 data of del insert into tab1 Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias SQL3109N The utility is beginning to load data from file db2backup rest_table NODE0000 data SQL3110N The utility has completed processing 0 rows were read from the input file SQL3221W Begin COMMIT WORK Input Record Count 0 SQL3222W COMMIT of any database changes was successful Up and Running with DB2 on Linux SQL3149N 0 rows were processed from the input file 0 rows were successfully inserted into the table 0 rows were rejected TROO E S O Number of rows read Number of rows skipped Number of rows inserted Number of rows updated Number of rows rejected Number of rows committed mensa db2 connect to itsodb completed ok db2inst1 mensa gt db2_all lt lt 1 lt db2 connect to itsodb db2 import from db2backup rest_table NODE0001 data of del insert into tab1 Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias SQL3109N The utility is beginning
35. for i in 1 2 3 do echo Wi echo Start backing up database DB ALIAS on node DB2NODE echo nn db2 backup db DB_ALIAS to db2backup with 4 buffers parallelism 2 if 0 then szDate date echo echo backing up database DB_ALIAS on node DB2NODE successfully szDate tee a DBHOME DB_ALIAS 1og echo nu exit 0 fi 248 Up and Running with DB2 on Linux if ne le gu then echo Start another trial fi done szDate date echo echo backing up database DB_ALIAS on node DB2NODE faild after 3 trials szDate tee a DBHOME DB_ALIAS 1og echo exit 8 Modify this sample so that it fits your environment and requirements The new DB2 9 5 feature single system view SSV backup is the recommended way for backing up all database partitions Example 6 13 on page 242 Note For a detailed explanation of backing up databases refer to Chapter 10 Database Backup in Data Recovery and High Availability Guide and Reference SC23 5848 Enable automatic backup DB2 provides automatic maintenance capabilities for performing database backup keeping statistics current and reorganizing tables and indexes as necessary When enabling automatic backup you can specify the following criteria for determining when a backup is required gt Maximum time between backups gt Maximum log space used between backups Using these settings DB2 determines if a backup is required and runs the back
36. outline mode and allows you to quickly navigate within it At the lower right pane you can see other views organized by tabs and the Tasks view is open The Tasks view is a Notepad where you can keep track of your open tasks It also shows tasks that you have annotated in your source files Use the tab to switch to other views The editor pane shows a tree representation of the file content The one shown in the figure is the XML file named NewFile xml The Outline view on the right shows the contents of the same file in a different way If you change anything in the editor the change will be reflected in the Outline view immediately Figure 5 15 shows that we have added a new product element fa Statement1 sql Ei NewFilexm x G1 BE outline 38 gt f 22 xml version 1 0 encoding UTF 8 2xml v e products v e products v E product Y E product xmins http posample org xmins http posample org Yv E description pid 10 E name v e description e price E name Fleece jacket YV E product xmins http posample org E price 19 99 YV E description Y E product name xmins http posample org price b E description E description product Gi description Design Source Figure 5 15 Views You can open new views by selecting Window gt Show View gt and then selecting one of the submenus The new view will be added somewhere in your perspective and you can rearrange it
37. s capability Example 6 40 shows the simple shell script that we use Example 6 40 Start a script to monitor the table reorganization procedure db2instl mensa gt while true gt do gt db2 get snapshot for tables on itsodb gt gt snap out db2pd reorgs d itsodb gt gt snap out sleep 1 gt done Following the startup of the monitor program we start inplace table reorganization by using the command shown in Example 6 41 Example 6 41 REORG TABLE with INPLACE and ALLOW WRITE ACCESS mode db2inst1 mensa gt db2 reorg table item index PK_ITEM_ITEMID jinplace allow write access on all dbpartitionnums DB20000I The REORG command completed successfully DB210241 This command is asynchronous and may not be effective immediately From the output you can read that the inplace table reorganization is asynchronous and might not be effective immediately You have a few options to determine if the inplace table reorganization is finished or what the current status is of the inplace table reorganization While the REORG and our monitor script were running we checked the current status of the REORG command using the SNAPTAB_REORG administrative view as shown in Example 6 42 on page 297 Up and Running with DB2 on Linux Example 6 42 SNAPTAB_REORG administrative view db2inst1 mensa gt db2 select substr tabname 1 10 as tab_name substr reorg_ type 1 30 as reorg_type reorg_status reorg_completion dbpartitionnum from
38. the db2rmln command from a DB2 version or a copy to remove existing links Configure TCP IP for the DB2 instance You must configure your instance with the TCP IP protocol in order for it to accept requests from remote DB2 clients Follow these steps 1 Update the etc services file to specify the service name and port number on which the DB2 server will listen for client requests To update the etc services file use a text editor to add a connection entry For example we added db2c_db2inst1 50001 tcp DB2 connection service port In the previous connection entry db2c_db2inst1 represents the connection service name 50001 represents the connection port number tcp represents the TCP IP communication protocol The service name is arbitrary but it must be unique in the services file Ina partitioned environment make sure that the port number does not conflict with the port numbers that are used by the Fast Communications Manager FCM or any other applications on the system 2 Update the database manager configuration file on the server a Log in as the instance owner b Update the SVCENAME parameter in the DBM configuration file You can specify either the service name or the port number For example we entered db2 update dbm cfg using SVCENAME db2c_db2inst1 Up and Running with DB2 on Linux You can check your SVCENAME by entering db2 get dbm cfg grep SVC 3 Set the DB2COMM registry variable to tcp ip
39. under the control of the scheduler which is integrated into the Tools catalog Refer to Figure 6 9 on page 247 Up and Running with DB2 on Linux Another way to back up the database is to generate the scripts through the Control Center and use your own scheduler to run this backup script periodically Backup Wizard E Schedule 7 Sien Backup 2 5 08 2 43 48 PM PST 0 Backup Database Run once on 2 5 08 at 2 43 48 PM kl Backup Database Backup Database Partition Grouping Figure 6 9 Scheduling backup scripts Back up the database sample script We have already showed you various backup commands in 6 1 4 Backup utility on page 240 In Example 6 18 on page 248 we show you a script to back up our sample database ITSODB which is partitioned Call this script with the db2_a11 command db2_all db2home db2inst1 database_backup ksh db2instl itsodb Chapter 6 Administering databases 247 Example 6 18 Backup script database_backup ksh usr bin ksh Script backing up database echo running against instance 1 echo running against database 2 INSTANCE 1 DB_ALIAS 2 DBHOME finger 1 INSTANCE grep Directory awk print 2 gt if f DBHOME sq llib db2profile then echo File not found DBHOME sq llib db2profile echo please check host and instancename echo u kkkkkkkkkkkkkkkkkk script abnormal ly ended kkkkkkkkkkkkkkkkk exit 1 fi DBHOME sq11ib db2profile
40. 0 DB2_SAMPLE_DATABASE 9 5 0 0 7 5 5 db2support ooooocococoeococoe Base client support Java support SQL procedures Base server support IBM Software Development Kit SDK for Java TM Connect support Communication support TCP IP Replication tools Control Center DB2 data source support DB2 LDAP support DB2 Instance Setup wizard XML Extender Base application development tools First Steps Sample database source The db2support utility is designed to automatically collect all DB2 and system diagnostic data This program generates information about a DB2 server including information about its configuration and system environment The output of this program is stored in one compressed file named db2support zip which is located in the directory that is specified as part of the command invoked under the command line processor In one simple step the tool can gather database Chapter 7 Monitoring and troubleshooting DB2 413 manager snapshots configuration files and operating system parameters which can help you determine the problem more quickly You can use the command db2support h to display the complete list of command options The following basic invocation is usually sufficient for collecting most of the information that is required to diagnose a problem db2support outputpath d dbname c For example execute the following command to collect information about database ITSODB db2support d ITSODB c
41. 0 db2inst1 NODE0000 CATNO000 20080204081423 001 1 Buffers processed dttHttttttte Image Verification Complete successful The db2ckbkp utility can also be used to display the metadata stored in the backup header such as table space and container information or automatic storage paths The backup media header information is shown using the h option as illustrated in Example 6 17 on page 245 The output shows that we used the INCLUDE LOGS clause and also the COMPRESS option to take the backup Up and Running with DB2 on Linux Example 6 17 Using db2ckbkp to show the backup media header db2inst1 mensa db2backup gt db2ckbkp h ITSODB 0 db2inst1 NODE0000 CATNO000 20080205141153 001 Server Database Name ITSODB Server Database Alias ITSODB Client Database Alias ITSODB Timestamp 20080205141153 Database Partition Number 0 Instance db2inst1l Sequence Number 1 Release ID C00 Database Seed 50B96082 DB Comment s Codepage Volume 0 DB Comment Volume DB Comment s Codepage System 0 DB Comment System Authentication Value 1 Backup Mode 1 Includes Logs 1 Compression 1 Backup Type 0 Backup Gran 0 Status Flags 21 System Cats inc 1 Catalog Partition Number 0 DB Codeset UTF 8 DB Territory LogID 1202239916 LogPath database db2inst1 NODE0000 SQL00002 SQLOGDIR Backup Buffer Size 1048576 Number of Sessions 1 Plat
42. 1 which means that a connection can wait until it gets all resources Deadlock problems occur if a connection already holds locks that are required by another application To prevent too many deadlock situations for OTLP set this value to 10 and for DSS set this value to 60 LOGBUFSZ DB2 uses a buffer for log records before writing the records to disk If the value is set too low it results in unnecessary I O on the disk When increasing the value of this parameter consider increasing the DBHEAP parameter too because the log buffer memory is allocated from the database heap SORTHEAP which can be set to AUTOMATIC Each sort has its own amount of memory that is allocated by the database manager This parameter defines the maximum sort memory that can be used When increasing this value examine whether the SHEAPTHRES_SHR Chapter 3 Post installation tasks 141 142 parameter in the database manager configuration file also needs to be adjusted DATABASE_MEMORY which can be set to AUTOMATIC If DATABASE_MEMORY is set to AUTOMATIC STMM tunes it according to the available memory in the system and according to the needs of the various tuning areas If this parameter is set to a fixed value the memory for this particular database is limited to that value and STMM tunes the various areas based on that available memory DFT_DEGREE A value of 1 means there is no intra partition parallelism A value of 1 or ANY means the optim
43. 103 db2profile This file is useful for setting special environment variables such as Tivoli System Management parameters Notes gt Replace NSTHOME with the actual value of the home directory of the instance gt DB2 provides db2cshre under INSTHOME sallib for csh users to set up the DB2 environment 3 2 4 Multiple partition specific configuration 104 In DB2 a database partition is a part of the database that consists of its own data indexes configuration files and transaction logs Partitions are used to create clustered databases where one logical database is split on several systems The partitions can be on the same system logical partitions or on a different system physical partitions Figure 3 4 on page 105 shows the file system layout for our sample partitioned database db2home lt instance gt is the instance home directory In the partitioned database environment db2home is a Network File System NFS mount to export db2home on the first system The other database files are located in local directories on each system The file db2nodes cfg defines the partitions that are part of the partitioned database Up and Running with DB2 on Linux Linux node 1 Linux node 2 Physical instance home export db2home lt instance gt N Node config sqllib db2nodes cfg 7 ae oN IN NLN A Instance home mounted 3 N db2home lt instance gt g T
44. 2 23 Example 2 23 Verify ssh configuration ssh mensa echo hi ssh gemini echo hi These commands complete successfully without prompting for additional verification 2 3 Installing DB2 In this section we explain how to install DB2 using the DB2 Setup db2_install and response file installation methods We discuss the following topics Non root installation Root installation Installing DB2 license files Installing DB2 documentation Adding an additional partition YYYY Y Chapter 2 Installation 59 Note With DB2 Version 9 and later DB2 license files are shipped separately You must install DB2 license files for each DB2 copy no matter which installation method that you choose See 2 3 4 Installing DB2 license files on page 87 2 3 1 Non root installation For non root installation you can use one of the following methods to install single partition database environments gt DB2 Setup wizard gt Response file installation db2setup command with a response file silent install gt db2_instal utility DB2 Setup wizard For non root installation you can use DB2 Setup wizard 1 Ask the Linux system administrator who has root authority to mount the DB2 product CD or DVD using the following command mount t is09660 o ro dev dvd mnt dvd where mnt dvd represents the mount point of the CD or DVD 2 Log in as anon root user run db2setup and select Install a Product on the first window No
45. 200340 31840 0 000290 35340 0 000310 35900 0 Up and Running with DB2 on Linux 200310 35900 0 200330 35370 0 On 64 bit systems the path jdk32 needs to be replaced by the path jdk64 If you want to run the Java code on another database you have to bind the package there first In order to do that you need the file with the suffix ser and you need to run the following command db2sqljbind url jdbc db2 localhost lt port gt SAMPLE user db2inst2 password lt password gt test_sqlj_SJProfile0 ser Like embedded SQL programs in C SQLJ also use a precompiled access path at run time Therefore no compilation of the SQL statements happens at run time You can also grant access to the users at the package level instead of at the table level Stored procedures in Java Only IBM JDKs are supported to create and run Java UDFs and stored procedures Non IBM versions of the SDK for Java are supported only for building and running stand alone Java applications In the database manager configuration the JDK_PATH parameter must point to the directory where your SDK is installed You can view it by running db2 get dbm config grep JDK_PATH This command will show Java Development Kit installation path JDK_PATH home db2inst2 sqllib java jdk32 The path might differ on your local system depending on your instance name and whether you run on a 32 bit or a 64 bit system Now we can start writing a small UDF in Java Examp
46. 4 2 3 Migrating instances and databases 000000 178 4 2 4 Post migration tasks 0 0 0c eee eee 180 4 2 5 Enabling new DB2 9 5 functionality 000 182 4 2 6 Migrating the DB2 Administration Server 182 4 2 7 Migrating DB2 clients 0 0 eee ee 184 4 3 Migrating a single partitioned database 00055 187 4 4 32 bit to 64 bit conversion 2 2 0 0 ee eee 188 4 5 Migrating to anew database 0 eee ee 190 4 6 Fix pack installation 2 0 0 ee eae 195 Chapter 5 IBM Data Studio 0 0 0 0 0c eee eee 197 6 1 INTOGUCHON eeri eee beds Dye bdo ose ee he Ee oS 198 6 2 INStallationis scat Stok Melee abo ae a naan git hme neds aea debate queue Benes 200 5 2 1 Installing IBM Data Studio 0 00 e eee 200 5 2 2 Installing IBM Data Studio Administration Console 207 5 2 3 Migration from the Developer Workbench 210 5 3 Features and functions 00 0000 cece eee 210 5 3 1 Terminology orses nren 00 cece eee eee 211 5 3 2 Team function 0 ee eae 216 3 3 AMLE Edig swt ee avenge a hd ES ye Pet aa dawe a 217 5 3 4 Entity Relationship ER Diagramming 220 5 3 5 Data and object management 0 0 cee eee eee 221 5 3 6 Data Web Services 00 0 c cee ee 223 5 3 7 MPS Aem s ponwte Poot Addeed Stans E Beet eee EDA 224 Chapter 6 Administe
47. 4 JDBC driver The database server is installed on the other machine Separating the application and the database servers as in scenario 2 and 3 is usually a preferred architecture for the larger installations It provides more flexibility in tuning the servers separately applying maintenance tasks and implementing failover DB2 supports multi version installation on one system Different versions or the same version with different fix pack levels can coexist in the same machine For instance you can run a DB2 Version 8 2 and a DB2 Version 9 5 instance on same machine or V8 1 Fix Pack 1 and V8 1 Fix Pack 2 in one system An instance is related to a Linux user ID and can be accessed through the network by a TCP IP port If you want to access a database remotely the database has to be configured to listen on a particular port The port can be configured by using db2 UPDATE DBM CONFIG USING SVCENAME 50000 In addition the TCP IP protocol must be enabled by using db2set DB2COMM tcpip The database manager needs to be restarted afterwards Figure 8 2 shows the concept of the instance setup Linux server Instance for a V8 2 Instance for a V9 5 database listening database listening on port 50000 on port 50002 Application 1 Application 2 Figure 8 2 Instance setup for application connections Chapter 8 Application development 427 8 2 DB2 application objects DB2 sup
48. 40 1207 60 662308 40 1471505 20 0 00 0 00 0 00 eth0 19 80 18 60 3153 20 17137 40 0 00 0 00 0 00 eth0 832 06 1154 51 654760 92 1455199 00 0 00 0 00 0 00 eth0 115 20 152 60 23889 60 165605 60 0 00 0 00 0 00 eth0 769 26 1063 47 638018 56 1315718 56 0 00 0 00 0 00 eth0 523 92 719 32 396419 44 884977 36 0 00 0 00 0 00 For the details about using the sar command refer to the man help pages for sar or other Linux documentation Note As mentioned in 7 6 3 iostat on page 419 the sar utility is in the sysstat package Before using this command you need to make sure that the sysstat package is installed in your system 7 6 5 Other system monitoring tools There are also a multitude of Linux system monitoring tools available for monitoring Linux system resource usage such as these commands gt The ps command which is known to almost everyone is used to report the status of the processes The pstree command can be used to display a tree of processes The netstat command is used to print network related information The nfsstat command is used for network file system NFS specific statistics In addition the pgrep and pkill commands are helpful when you want to look up or signal processes that are based on the name and other attributes of the processes And if you like to use monitoring tools with a graphical user interface Chapter 7 Monitoring and troubleshooting DB2 423 you can use utilities such as gnome system monitor
49. 8 32 Deploy Options panel w 11 In the Routine Options panel keep the defaults Refer to Figure 8 33 on page 487 Click Next Up and Running with DB2 on Linux m 3 Deploy Routines O Routine Options Specify routine options v Guava Stored Procedures Compile options fs if E EMPSALARY IN SALAI Enable d Ta JDK home shomeldb2inst1 sqllib javaljdk32 Browse JDK version 15 0 Database JRE version l Apply Folder Settings Einish Cancel Figure 8 33 Routine Options panel 12 At the Summary panel Figure 8 34 click Finish a 2 Deploy Routines Summary The settings that you specified are summarized here Target database SAMPLE Target schema DB2INST1 Routines to deploy EMPSALARY Error handling Stop and roll back on errors Duplicate handling Drop duplicates Danlou Danio hu buildinea the source 4 Einish Figure 8 34 Summary panel 13 In the Data Output panel Figure 8 35 on page 488 you can see the result of the deployment Chapter 8 Application development 487 Properties Tasks Problems Error Log Model Report RIRE ELOT TaS SAMPLE DB2INST 1 EMPSALARY IN SALARY INTEGER Messages Parameters Results Profiling Data EmpSalary sq FENCED THREADSAFE PARAMETER STYLE JAVA DB2INST1 EMPSALARY Create stored procedure completed DB2INST1 EMPSALARY Removed temporary working directory home db2inst1 IBM rationals
50. 9 5 while the application is still up and running under Version 8 or 9 1 You can then create Version 9 5 test instances and databases with a small amount of data to test your applications while production transactions are running 172 Up and Running with DB2 on Linux When you are ready to move your production systems up to Version 9 5 after making any required changes in your applications or environment you can migrate the instances and databases during off peak times to reduce system downtime and reduce the number of people or systems affected by that downtime We do not recommend this migration in your production environment without testing first 4 2 Migrating multi partitioned database This section provides a list of pre migration tasks and the migration procedures for partitioned databases The procedures to migrate a multi partitioned database from DB2 Version 8 or 9 1 to Version 9 5 are in general the same The high level steps consist of gt Migration preparation This step prepares the instance and the database for migration including backing up databases and checking whether the database is ready to be migrated using the db2migr command gt DB2 Version 9 5 installation gt Migrating instance and databases Actual migrating instance and database gt Post migration Tasks to ensure that the DB2 servers perform as expected gt Enabling new DB2 9 5 functionality gt Migrating Administration Server gt Migrat
51. Administering databases 285 286 Figure 6 24 Reorganize Indexes panel Figure 6 25 shows you the generated commands Show Command CONNECT TO ITSODB REORG INDEXES ALL FOR TABLE DB2INST1 ITEM ALLOW WRITE ACCESS CONNECT RESET Figure 6 25 Generated REORG INDEX command You can reduce the need for index reorganization through a variety of actions such as setting PCTFREE for indexes or enabling the online index defragmentation by setting MINPCTUSED Setting MINPCTUSED will trigger online index leaf page merging when specific conditions are matched Online index leaf page merging can reduce the likelinood of causing index page splits when future activities such as inserts happen on the table Statistics information collection The RUNSTATS option updates the statistics about the characteristics of a table and associated indexes or statistical views These characteristics include the number of records number of pages and average record length The optimizer uses these statistics when determining access paths to the data For a table call this utility when the table has had many updates or after reorganizing the table For a statistical view call this utility when changes to the Up and Running with DB2 on Linux underlying tables have substantially affected the rows returned by the view The view must have been previously enabled for use in query optimization using the ALTER VIEW command The RUNSTATS command can be iss
52. After the table is created issue the LOAD or IMPORT command to add the data to the table The db2100k command preserves all of the properties of a table and is a superior option for table re creation The authority and the privileges that are required for running import with and without creating a new table option are different To use the import utility to create a new table you must have SYSADM authority DBADM authority or CREATETAB privilege for the database To replace data in an existing table or view you must have SYSADM authority DBADM authority or the CONTROL privilege for the table or view To append data to an existing table or view you must have SELECT and INSERT privileges for the table or view The import utility performs the following steps to import the data 1 Locking tables Import acquires either an exclusive X lock or a non exclusive IX lock on the existing target tables depending on whether you allow concurrent access to the table 2 Locating and retrieving data Import uses the FROM clause to locate the input data 3 Inserting data Import either replaces existing data or adds new rows of data to the table 4 Checking constraints and firing triggers As the data is written import ensures that each inserted row complies with the constraints that are defined on the target table Information about rejected rows is written to the messages file Import also fires existing triggers 5 Committing the operati
53. Columns MGRNO ni CHAR 6 o Relationships ADMRDEPT CHAR 3 vy o Statistics LOCATION CHAR 16 o Documentation Primary Key Data Type Length Scale Not Nul Generated Default Value Genei gt Impacted Objects gt DDL Figure 5 27 Table editor In a similar way you can manipulate the other database objects such as aliases buffer pools table spaces roles and privileges 5 3 6 Data Web Services Data Web Services provides you with the capability to generate a Web Service from a query without any coding Right click the statement in the Data Project Explorer view and select Add to Web Service Figure 5 28 on page 224 Chapter 5 IBM Data Studio 223 w x A R Statementt sql 2 E USEF mm amp v SELECT BMPNO SALARY gt FROM EMPLOYEE v 0 DataProject SAMPLE jdbe db2 local host 50001 SAMPLE WHERE SALARY 36000 v SQL Scripts E Open With gt Fal b C3 Web Service CI XML gt a I Delete BunsaL sdh Visual Explain Validate Team P Compare With Replace With ORDER EY LASTNAME C Stored Proce m Rename User Defined Ga User Definey E Copy 10 Add to Web Service 20 Generate Stored Procedure Sn 4 Figure 5 28 Create a Web service from a query These actions create a Web service from that query You can build the Web archive WAR file and deploy it to an application server You also can use it as a framework for your further development If you
54. Command CONNECT TO ITSODB REORG TABLE DB2INST 1 ITEM INDEX DB2INST1 PK_ITEM_ITEMID ALLOW READ ACCESS Figure 6 22 Generated REORG TABLE command Chapter 6 Administering databases 283 284 There are several methods available to reduce the need for a reorganization of a table and its indexes such as setting PCTFREE for a table to preserve a certain percentage of each data page for subsequent insert and update operations For more information refer to Tuning Database Performance SC23 5867 Analyzing the statistics produced by RUNSTATS can indicate when and what kind of reorganization is necessary In addition you can use the REORGCHK command to calculate statistics on the database or use current statistics information to determine if tables or indexes or both need to be reorganized or cleaned up Important After reorganizing a table you need to collect statistics on the table so that the optimizer has the most accurate data for evaluating query access plans Index reorganization To get the best performance from your indexes consider reorganizing your indexes periodically because table updates can cause index page prefetch to become less effective The REORG INDEX option reorganizes all indexes that are defined on a table by rebuilding the index data into unfragmented physically contiguous pages If you specify the Cleanup Only option while reorganizing an index cleanup is performed without rebuilding the indexes D
55. DB2 clients from Version 8 or Version 9 1 to DB2 9 5 in a Windows environment Chapter 4 Migration and fix packs 185 Table 4 4 Migration options in Windows Migrating from Migrating to Migration methods summary Version 8 DB2 DB2 9 5 Data Install the DB2 9 5 Data Server Client Administration Server Client and choose the migrate action in the Client Work with Existing panel The client Version 8 DB2 instance is then automatically Application migrated for you Development Install a new copy of DB2 9 5 Data Client Server Client and then manually Version 9 1 DB2 migrate Version 9 1 or Version 8 client Client instances Version 8 DB2 DB2 9 5 Data Install the Version 9 5 Data Server Run Time Client Server Runtime Runtime Client as a new copy Version 8 DB2 Client Manually migrate your Version 9 1 or Run Time Client Version 8 client instance Lite Version 9 1 DB2 Runtime Client For Linux environments the client migration process is the same for both DB2 Version 9 5 clients The process is 1 Verify that the client supported is described in Considerations on page 184 2 Back up the client configuration The following two commands create two files in your current directory that contain the database manager configuration and information about the cataloged databases db2 get dbm cfg gt dbm_client cfg db2cfexp cfg_profile backup 3 Install the DB2 9 5 client 4 Migrate your client instance DB2HOME bin db2imi
56. DB2 monitoring and troubleshooting features We describe the following topics Health Monitor and Health Center Memory Visualizer and Memory Tracker db2mitrk IBM single system monitor view for DB2 db2top Log files for troubleshooting DB2 problem determination PD problem source identification PSI tools Linux system monitoring tools vvvvvy Copyright IBM Corp 2008 All rights reserved 353 7 1 Health Monitor and Health Center Health Monitor and Health Center are two DB2 features that can help you monitor the health of your DB2 systems These tools add a management by exception capability to DB2 by alerting you to potential system health issues This enables you to address health issues before they become real problems that affect your system 7 1 1 Health indicator and Health Monitor 354 Next we explain the concepts of the health indicator and the Health Monitor Health indicator Prior to using the Health Monitor you need to understand the concept of a health indicator A health indicator is a measurement that gauges the healthiness of an aspect of an object The Health Monitor uses these indicators to evaluate specific aspects of database manager or database performance DB2 comes with default settings for all health indicators Using the Health Center DB2 commands or application programming interfaces APIs you can customize the settings of the health indicators and define who to notify and what script or t
57. E LASTNAME VARCHAR 15 g amp WORKDEPT CHAR 3 E PHONENO CHAR 4 E HIREDATE DATE HP IOY EE E JOB CHAR 8 Z EMPNO F B EDLEVEL SMALLINT C FIRSTNME B SEX CHAR 1 Figure 8 22 Content Assist in Query Builder IE2INSTL EMPLOYEE JOIN DE2INSTL DEPARTMENT 37000 WHERE DE2INSTL FMPLOYEE SALARY siz DEPTNO o E DEPTNAME Creating a stored procedure in Java In Stored procedures in Java on page 453 we discussed how to create stored procedures from the command line In this section we show how easily you can accomplish this task by using the Data Studio The graphical aids provided by the tool make this task much less error prone To start the creation 1 in the Data Project Explorer expand DataProject gt SQL Script EmpSalary sql Right click it and select Generate Stored Procedure We name the procedure EMPSALARY as shown in Figure 8 23 on 480 Up and Running with DB2 on Linux page 481 We take the rest of the default values to create a JDBC program Click Next F D 2 New Stored Procedure 3 Name and Language Specify basic options for creating a stored procedure To preserve case use delimiters for all SQL identifiers Project DataProject al New Name EMPSALARY Language ava v Java options Java package db2inst1 Dynamic SAL using JDBC O Static SAL using SOLJ Root package s1275 SAL translator location home db2inst1 sql
58. Earliest Log Current Log Backup ID L T 20080221114949001 R I S0000876 L0G S0000876 L0G DB2INST1 ITEMLOAD resides in 1 tablespace s 00001 TSDATA2 Comment DB2 Start Time 20080221114949 End Time 20080221115029 Status A EID 1209 Location DB2 Autoloader Data was partitioned on 2 node s and loaded on node 0 Op Obj Timestamp Sequence Type Dev Earliest Log Current Log Backup ID 324 Up and Running with DB2 on Linux C T 20080221114949002 R S S0000876 L0G S0000876 LOG DB2INST1 ITEMLOAD resides in 1 tablespace s 00001 TSDATA2 Comment DB2 Start Time 20080221114949 End Time 20080221115029 Status A EID 1210 Location db2backup datamove copydata ITSODB 4 db2inst1 NODE0000 CATNO000 20080221114949 001 Load table data using the Control Center The Load wizard is available in the DB2 Control Center to invoke the Load wizard 1 From the Control Center expand the object tree until you find the Tables folder 2 Click Tables Any existing tables are displayed in the pane on the right side of the panel the contents pane 3 In the contents pane right click the table that you want and select Load from the pop up menu The Load wizard panel opens Here we demonstrate how to use the Load wizard to load data into a sample table named ITEMLOAD which is defined on database partition 0 through 1 The detailed steps are 1 Invoke the Load Wizard from the DB2 Control Center Figure 6 34 on page 326 Ch
59. Example 8 24 Example 8 24 Running the Java UDF db2inst1 puget gt db2 select hello Java Guru from sysibm sysdummy1 Hello to Java Guru 1 record s selected When developing UDFs we recommend that you set the database manager parameter KEEPFENCED to NO so that the UDF will be reloaded in each call For troubleshooting UDFs check db2diag log for a Java stack trace Up and Running with DB2 on Linux 8 4 pureXML Extensible Markup Language XML becomes more and more important for Web Java and Java 2 Platform Enterprise Edition J2EE development XML is used to store configuration information or to exchange data in a system independent way DB2 has now implemented native XML support This section provides an overview of XML capabilities 8 4 1 Storage model Prior to DB2 9 1 you were able to store XML in DB2 in the following ways gt Store as a character large object CLOB in the database This method preserves the original XML structure but you cannot search by attribute If you want to extract a particular attribute you have to parse the whole XML from the CLOB In order to implement search and extract more efficiently you can create separate columns for the attributes But that increases the needed space and adds maintenance overhead Store all attributes in the relational data model Using this method you parse the XML document to insert into the database To have the original XML document structure rec
60. IBM Corp 2008 All rights reserved 197 5 1 Introduction 198 Enterprises of all sizes and across all industries share common drivers of the investments that they are making in the management of their business data The complexity and cost of supporting and managing data from the initial design of the data structure throughout all phases until properly sunsetting the data continue to increase The demand to deliver an increasing amount of data more rapidly across and beyond the business keeps growing The expensive human resources such as developers architects and administrators work in silos that cause issues such as data models that are not shared across silos Web services are difficult to develop and deploy complex environments use different tools for each data server the life cycle of data is poorly understood and challenging to manage and so on The innovation will be restrained when silos of information are disconnected inaccurate incomplete and out of context New approaches are needed for application delivery and support in order to reduce the time and cost of empowering a broader user audience with more powerful data driven applications IBM Data Studio a foundation for innovation and a comprehensive data management solution is a family of integrated tools for database development and administration It empowers you to effectively design develop deploy and manage your data databases and database applications through
61. In this example mensa is the database partition server that owns the instance Example 4 7 Shows mensa as database partition server that owns the instance dpfusr1 mensa gt more dpfhome dpfusr1 sqllib db2nodes cfg 0 mensa 0 1 gemini 0 2 Stop the instance by running the db2stop force command 3 Log in as root and run the db2imigr command to migrate your instance to Version 9 5 Use the following syntax DB2DIR instance db2imigr u lt fenced_user gt instance_name Up and Running with DB2 on Linux In this command DB2DIR is set to the location that you specified during DB2 9 5 installation fenced_user is the user name under which the fenced user defined functions and stored procedures will run and instance_name is the login name of the instance owner The fenced user is only required if you are migrating from a client instance to a server instance Our input and output are shown in Example 4 8 Example 4 8 Migrating the instance mensa opt ibm db2 V9 5 instance db2imigr dpfusrl db2ckmig was successful Database s can be migrated DBI10701 Program db2imigr completed successfully At this point in time you might want to check the DB2 level to ensure that your instance is now a Version 9 5 instance as shown in Example 4 9 Example 4 9 Check db2level dpfusr1 gemini gt db2level DB21085I Instance dpfusr1l uses 64 bits and DB2 code release SQLO9050 with level identifier 03010107 Informational tokens ar
62. LOCAL Protocol TCPIP Hostname mensa Service name 50001 db2vs puget gt db2 list db directory System Database Directory Number of entries in the directory 1 Database 1 entry Database alias ITSODB Database name ITSODB Node name MENSA Database release level c 00 Comment Test database for ITSO Directory entry type Remote Authentication SERVER Catalog database partition number 1 Alternate server hostname Alternate server port number db2vs puget gt db2 connect to itsodb user db2inst1 Enter current password for db2inst1 Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias Note For more details about DB2 commands refer to the Command Reference SC23 5846 3 9 Configuring licensing Each DB2 product and DB2 feature ships with its own license key To assist you in managing your licenses a compliance report lists the compliance or noncompliance of DB2 features with your current product entitlement To be in compliance with your license agreement you must apply the license key Chapter 3 Post installation tasks 159 You manage all of these licenses through one of the following tools gt The DB2 License Center within the Control Center gt db21licm which is a license management tool command This section provides instructions to configure licensing using both of these tools We discuss the following
63. Memory Management STMM that greatly simplifies the database memory configuration by automatically setting values for several memory configuration parameters The STMM manages memory for the following DB2 memory consumers Buffer pools Package Cache Locking memory Sort memory vvvy The tuning of these areas can be turned on and off individually Tuning is done across different databases and different instances on the same system The memory available for tuning can be limited If no more memory for tuning can be allocated from the operating system or if the memory reaches the limit that you defined the available memory is taken away from another area where the memory is not needed as much For instance if STMM figures out that more memory is needed for one buffer pool it can take this memory away from another buffer pool The frequency of tuning is determined based on the workload and each tuning step is logged in db2diag log and in the directory stmmlog STMM also works on partitioned databases but in this case each system must be the same hardware And the workload and the data must be distributed equally because the tuning parameters are determined on one partition called the tuning partition and then distributed to the other partitions Figure 3 19 on page 134 illustrates how the space in the memory is distributed among the various areas Chapter 3 Post installation tasks 133 db2inst1 db2inst2 db2ins
64. Method Strategy Start time Redistribute V MENSA TSODB Figure 3 18 Redistribute the data Here you can select the partition groups that you want to redistribute and perform the redistribution On the Redistribute Strategy window select Real time system analysis to let DB2 gather information about how much log space is needed and how much log space is available Repeat this analysis for all database partition groups that need to be extended over the added partition The redistribution messages are stored as well in INSTHOME sq l1ib redist lt dbname gt lt part group gt lt time gt 3 6 DB2 configuration 132 DB2 has many configuration parameters that specify the allocation of system resources and the overall configuration of the instance and the database These parameters are stored in the database configuration the database manager configuration and in the registry Because the default values are set for machines with relatively small memory and disk storage you might need to modify them to fit your environment A good starting point for tuning your configuration is the Configuration Advisor or the AUTOCONFIGURE command If you create a new database many of the parameters are already set to AUTOMATIC so that Self Tuning Memory Management STMM takes care of their tuning Up and Running with DB2 on Linux 3 6 1 STMM Self tuning memory management In Version 9 DB2 introduced a new feature Self Tuning
65. NFS In order to get NFS up and running you need to configure the etc exports and etc fstab files The exports file is configured on the server side and specifies which directories are to be shared with which clients and the access rights for each client The fstab file is configured on the client side and specifies which servers to contact for each directory as well as where to place them in the directory tree Up and Running with DB2 on Linux In this section we lead you through the steps that are required to set up NFS gt Get the NFS service running on each machine in the cluster gt Onasingle machine in the cluster the NFS server create a file system to use as the instance home directory if it has not already been created gt Mount this file system locally gt Set this file system to be mounted at each reboot gt Export the DB2 home file system using NFS gt Mount the exported file system on each of the remaining machines in the cluster Get the NFS service running To verify that NFS is running on each computer that will participate in the partitioned database system enter the following command showmount e hostname If you enter showmount without specifying a host name it will check the local system If NFS is not running you will receive a message similar to the following message mount clntudp_create RPC Program not registered To start the NFS gt Make sure that you have the nfs utils a
66. PHP is most often built as an Apache module although it can also be used through Common Gateway Interface CGI Many other Web servers support PHP too including the Apache based IBM HTTP Server If you intend to use PHP with DB2 using a Web server front end you need to consult chapter 1 of Developing PHP Applications for IBM Data Servers SG24 7218 to guide your decision about an HTTP server and to help you learn how to install it with PHP and DB2 Note If you intend to share an HTTP server with WebSphere Application Server the IBM WebSphere Developer Technical Journal article Pair J2EE with PHP to implement a common Web application infrastructure provides instructions to help them coexist http www ibm com developerworks websphere techjournal 0505_krook 0505_kroo k htm Here are further resources for maximizing the benefits of using PHP with DB2 gt Official PHP documentation http www php net docs php gt Zend Core for IBM is a seamless predefined ready to use easy to install and supported PHP development and production environment which features tight integration with DB2 drivers http www zend com en products core for ibm gt Zend Framework is based on simplicity object oriented best practices corporate friendly licensing and a rigorously tested agile codebase http framework zend com gt CakePHP enables PHP users at all levels to rapidly develop robust Web applications http cakephp
67. The changes are captured in the EMPLOYEE_HIST table Example 8 1 Trigger sample to store history data CONNECT TO sample CREATE TABLE employee_hist empno CHAR 6 salary_old DECIMAL 9 2 salary_new DECIMAL 9 2 bonus_old DECIMAL 9 2 bonus_new DECIMAL 9 2 chg_date TIMESTAMP Up and Running with DB2 on Linux CREATE TRIGGER employee_audit AFTER UPDATE OF salary bonus ON employee REFERENCING OLD AS old_row NEW AS new_row FOR EACH ROW MODE db2sq INSERT INTO employee_hist Values old_row empno old_row salary new_row salary old_row bonus new_row bonus current timestamp In Example 8 2 we modify several salary amounts on the employee table to fire the trigger and populate the EMPLOYEE_HIST table By selecting data from EMPLOYEE_HIST you can see how our trigger works Example 8 2 Each update forces one insert into the employee_hist table 55000 where empno 000070 45000 where empno 000110 55000 where empno 000170 65000 where empno 000070 db2 update employee set salary db2 update employee set salary db2 update employee set salary db2 update employee set salary db2instl puget gt db2 select from employee hist order by empno EMPNO SALARY_OLD SALARY _NEW BONUS_OLD BONUS_NEW CHG_DATE 000070 96170 00 55000 00 700 00 700 00 2008 01 29 03 06 17 126586 000070 55000 00 65000 00 700 00 700 00 2008 01 29 03 06 19 649943 000110 66500 00 45000 00 900 00 900 00 2008 01 29 03 06 17 287657
68. You can have the DB2 system take the corrective action automatically when the values for a health indicator setting are exceeded The example consists of the following steps Prepare the DMS table space and the table Review the health indicator for the DMS table space Populate a desired amount of data into the table space Check the notification that is sent by the DB2 system Take corresponding action to resolve current health alerts Set up additional follow up actions D JIB OUN These steps are given in detail 1 Prepare the DMS table space and the table In our example we use a DMS table space with a file container The size of the table space is 10 MB on each partition at its first creation After the table space is created a table with a distribution key is created within the table space Example 7 2 Example 7 2 Prepare the table space and the table for the Health Center db2inst1 mensa db2home db2inst1l script gt db2 tvf crt_sample db2 CREATE LARGE TABLESPACE tbspdms_0 IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING file database db2inst1 NODEO00 N ITSODB T0000008 C0000000 LRG 10M AUTORESIZE NO DB20000I The SQL command completed successfully CREATE TABLE db2instl empinfo ID INTEGER NOT NULL LASTNAME VARCHAR 30 HIREDATE DATE SALARY INTEGER PRIMARY KEY ID in tbspdms_0 DISTRIBUTE BY HASH ID DB20000I1 The SQL command completed successfully 2 Review health ind
69. a database or table space backup as shown in Example 6 52 Example 6 52 Table space backup pending state db2inst1 mensa db2backup datamove gt db2 list tablespaces show detail tail 22 Tablespace ID 7 Name TSDATA2 Type Database managed space Contents All permanent data Large table space State 0x0020 Detailed explanation Backup pending Total pages 51200 Useable pages 51168 Used pages 10720 Free pages 40448 High water mark pages 10720 Page size bytes 8192 Extent size pages 32 Prefetch size pages 32 Number of containers Minimum recovery time 2008 02 08 23 20 58 000000 DB210111 In a partitioned database server environment only the table spaces on the current node are listed db2inst1 mensa db2backup datamove gt db2 backup db itsodb on all dbpartitionnums tablespace TSDATA2 online to db2backup Part Result 0000 DB20000I The BACKUP DATABASE command completed successfully 0001 DB20000I The BACKUP DATABASE command completed successfully Backup successful The timestamp for this backup image is 20080208155111 When loading data in a partitioned database environment only non delimited ASCII ASC and delimited ASCII DEL files can be partitioned PC IXF files cannot be partitioned To load a PC IXF file into a multiple database partitioned table you can first load it into a single partition table and then perform a load operation using the CURSOR file type to move th
70. a secure shell This package _64 rpm is not required if you use the openssh server 4 3p2 24 el5 x86 default configuration of DB2 _64 rpm with rsh openssh askpass 4 3p2 24 el5 x8 6_64 rpm rsh server SLES 10 SP1 x86_64 This package contains a set rsh server 0 17 573 2 x86_64 rp of server programs that m allows users to run RHEL 5 x86_64 commands on remote rsh server 0 17 37 el5 x86_64 rp computers log in to other m computers and copy files between computers rsh rexec rlogin and rcp This package is not required if you configure DB2 to use ssh nfs utils SLES 10 SP1 x86_64 Network File System support nfs utils 1 0 7 36 21 x86_64 rpm package It allows access for RHEL 5 x86_64 local files to remote nfs utils lib 1 0 8 7 2 22 x86_64 r computers pm a For RHEL 5 both 32 bit and 64 bit compat libstdc packages are required for 32 bit applications to run b For SLES 10 and RHEL 5 ksh is required instead of pdksh To check whether you have these packages installed use the rpm q command For instance to check whether pdksh has been installed enter the following command rpm qa grep compat libstdc To install these packages on Red Hat and SUSE use rpm ivh command For example to install compat libstdc on SUSE Linux Enterprise Server SLES 10 on x86_64 mount the SLES 10 SP 1 x86_64 DVD 1 and enter the following command rpm ivh mnt dvd suse x86_64 compat libstdc 5 0 7 22 2 x86_64 rpm 34 Up and
71. actually exists A database is not in an inconsistent state A database is not in a backup pending state A database is not in a restore pending state A database is not in the rollforward pending state Table spaces are in a normal state A database does not contain user defined types UDTs with the name ARRAY BINARY DATALINK DECFLOAT VARBINARY or Extensible Markup Language XML A database does not have orphan rows in system catalog tables that will cause the database migration to fail A database which is enabled as a high availability disaster recovery HADR primary database allows successful connections A database is not in HADR standby role If SYSCATSPACE is a DMS table space and AUTORESIZE is not enabled SYSCATSPACE has at least 50 free pages of the total pages The command syntax is db2ckmig e 1 logfile_name In Example 4 5 we scanned all cataloged databases and saved the results to a text file db2ckmig log Example 4 5 The db2ckmig command dpfusr1 mensa opt ibm db2 V9 5 bin gt db2ckmig e 1 dpfhome dpfusr1 db2ckmig 1og db2ckmig was successful Database s can be migrated We checked the db2ckmig log for any errors and to ensure that the version of DB2CKMIG being run was Version 9 5 and not a previous version Example 4 6 on page 178 shows the db2ckmig log file If the db2ckmig command encounters any error when checking the database you must take act
72. all available snapshot table functions use the following command SELECT SUBSTR FUNCSCHEMA 1 10 FUNCSCHEMA SUBSTR FUNCNAME 1 30 FUNCNAME FROM SYSCAT FUNCTIONS WHERE FUNCNAME LIKE SNAP The SQL table functions have two input parameters gt Database name If you enter NULL the name of the currently connected database is used gt Database partition number To capture a snapshot for the currently connected database partition enter a value of 1 To capture a global aggregate snapshot enter a value of 2 To capture a snapshot from all of the database partitions as shown in Example 7 24 on page 411 do not specify a value for this parameter Note For a detailed overview of the snapshot administrative views and table functions refer to System Monitor Guide and Reference SC23 5865 7 5 4 db2ls With the ability to install multiple copies of DB2 products on your system and the flexibility to install DB2 products and features in the path of your choice you need a tool to help you keep track of what is installed and where it is installed The db2 s command lists the DB2 products and features installed on your Linux and UNIX systems including the DB2 Version 9 HTML documentation You cannot query DB2 products using the Linux native rpm command The db21s command can be used to list gt Where DB2 products are installed on your system and the DB2 product level gt All or specific DB2 products and features in a particular installation
73. and in SQL Reference Volume 2 SC10 4250 Chapter 8 Application development 431 Example 8 5 A simple example of an SQL procedure db2inst1 puget sqllib samples sqlproc gt db2 connect to sample Database Connection Information Database server SQL authorization ID Local database alias DB2 LINUX 9 5 0 DB2INST1 SAMPLE db2inst1 puget sqllib samples sqlproc gt db2 td vf basecase db2 CREATE PROCEDURE update_salary IN employee_number CHAR 6 IN rating INT LANGUAGE SQL BEGIN DECLARE SQLSTATE CHAR 5 DECLARE not_found CONDITION FOR SQLSTATE 02000 DECLARE EXIT HANDLER FOR not_found SIGNAL SQLSTATE 02444 CASE rating WHEN 1 THEN UPDATE employee SET salary salary 1 10 bonus 1000 WHERE empno employee_number WHEN 2 THEN UPDATE employee SET salary salary 1 05 bonus 500 WHERE empno employee_number ELSE UPDATE employee SET salary salary 1 03 bonus 0 WHERE empno employee_number END CASE END DB200001 The SQL command completed successfully Note In the file basecase db2 we use the character as a command terminator because the semicolon is already used to terminate the procedure statements Example 8 6 on page 433 shows how to call the SQL procedure from the command line 432 Up and Running with DB2 on Linux Example 8 6 Procedure call on command line db2inst1 puget gt db2 CALL update_salary 000100 1 Return Status 0 A stored procedure
74. and ksysguard For more information refer to the Linux specific documentation 424 Up and Running with DB2 on Linux Application development It has become increasingly important for a database to effectively support a wide range of open standards and open source products for application development DB2 provides accessibility for many standard interfaces and comes with a full suite of development tools In this chapter we discuss the following topics Application configuration DB2 application objects Programming languages Application development tools vvvy In this chapter we demonstrate the examples by using the SAMPLE database that DB2 provides You can create a sample database in your instance by running the command db2samp1 from the command line Alternatively you can create the SAMPLE database from the First Steps db2fs at the end of the installation or after the installation In our examples we usually refer to the DB2 instance home directory as db2inst1 You can change that name if you want to use a different instance name You can find startup information in Getting Started with Database Application Development GC23 5856 and on this Web site http www ibm com software data db2 ad DB2 provides many programming examples in the directory lt instance home gt sqllib samples Copyright IBM Corp 2008 All rights reserved 425 8 1 Application configuration 426 DB2 supports local and remote application de
75. and recovery strategy 9 Set advanced options Here you can specify additional options associated with the load operation which are not covered by the preceding panels and you can get hints by clicking the option listed in the panel Figure 6 42 on page 334 Chapter 6 Administering databases 333 Load Wizard ITEMLOAD Figure 6 42 Set advanced options for load operation 10 Scheduling task execution If you want to run the load operation without saving task history choose Run now without saving task history Figure 6 43 on page 335 If you want to create the task as a task in the Task Center which allows you to schedule task execution and save task history you can specify the details here 334 Up and Running with DB2 on Linux Dborennieta acii ifaniie Figure 6 43 Scheduling task execution 11 View the task summary and execute it In Figure 6 44 on page 336 the DB2 CLP commands which were generated based on your choices are displayed You can click Finish to submit the command or click Back for further modification of your choices Chapter 6 Administering databases 335 ard 1TEMLOAD CONNECT TO ITSODB LOAD FROM db2backup datamove item del OF DEL ME do2backup datamove loadcc msg REPLACE INTO DB2Ir AMOUNT COPY NO INDEXING MODE AUTOSELECT ISOLATI LOAD_ERRS_ONLY MODE PARTITION_AND_LOAD CONNECT RESET Figure 6 44 View task summary After running the load you can check the message files
76. and server code is available for a wide variety of platforms For example the application can execute on a Windows based machine with a DB2 client for Windows which can then access a DB2 database on a Linux server Likewise the Linux machine can act as a client and access data from UNIX servers or mainframes Multi tier In a multi tier configuration the application DB2 client and the data source typically reside on separate systems Examples of these configurations include but are not limited to the scenarios illustrated in Table 1 1 on page 12 Chapter 1 Introduction 11 12 Table 1 1 Multi tier configuration examples Web browser Web server DB2 database server DB2 client Application client Application server DB2 database server 1 DB2 client DB2 database server 2 Application DB2 connect gateway 0S 390 DB2 client AS 400 VM VSE Application DB2 server DB2 client Secondary data sources for example mainframe DB2 non DB2 and non relational IBM recognizes that in many cases there can be a need for accessing data from a variety of distributed data sources rather than one centralized database The data sources can be from IBM such as DB2 or Informix or non IBM databases such as Oracle or even non relational data such as files or spreadsheets As illustrated in the last scenario in Table 1 1 IBM offers the most comprehensive business integration solution by allowing federated access to a variety of distr
77. and uninstall your packages Installation Manager Directory opt IBM InstallationManager eclipse pS Disk Space Information Volume Available Space I 916GB lt Back Next gt Cancel Figure 5 4 Location for shared resources and Installation Manager Next you can specify if you want to use an existing package group or create a new one We create a new package group using the default location See Figure 5 5 on page 204 Chapter 5 IBM Data Studio 203 Ey IBM Installation Manager Install Packages A package group is a location that contains one or more packages Some packages can be installed into a common package group and will share a common user interface Select an existing package group or create a new one Install License Lecation Features Summary Create a new package group Package Group Name Installation Directory IBM Software Development Platform fopt IBM SDP70 Package Group Name IBM Software Development Platform Installation Directory opvIBM SDP70 Browse Details Disk Space Information Shared Resources Directory opt IBM SDP 70Shared Volume Available Space t 916GB Figure 5 5 Package group IBM Data Studio is an Eclipse based application A version of Eclipse integrated development environment IDE is bundled in the installation package The next panel allows you to extend an existing version of Ecl
78. as opposed to raw devices File system configuration DB2 log space DB2 temporary table space Chapter 2 Installation 35 gt User and group setup User and group requirements Creating users single partition Creating users multi partition DB2 administration server DAS user considerations for a multiple partition environment gt Network configuration for partitioned database installation Enabling ssh Setting up NFS 2 2 1 Considerations 36 DB2 9 5 now supports multiple DB2 copies on a single machine as well as non root installations There are also changes in 32 bit and 64 bit server support You need to understand these changes and take them into account before installing DB2 9 5 Multiple DB2 copies Beginning with DB2 Version 9 DB2 products can be installed in multiple different locations as different DB2 copies on a single machine A DB2 copy refers to one or more installations of DB2 database products in a particular location on the same computer Each DB2 Version 9 copy can be at the same or at different code levels Only one DB2 administration server DAS can be created on a machine regardless of the number of DB2 copies that are installed on the machine We recommend that you migrate your existing DAS to Version 9 5 or create a new DAS in DB2 Version 9 5 This multiple DB2 copies feature is supported by most DB2 products except DB2 Information Center Non root instal
79. authentication and each partition server must have the ssh client and ssh server configured correctly SSH server configuration Use the following steps to configure SSH server These steps must be applied on each physical node 1 Edit the sshd_config file The sshd_config file can be found in etc ssh on Linux Log in as root Change the HostbasedAuthentication parameter to Yes as shown in Example 2 6 This change allows the ssh server to accept host based authentication requests from the ssh clients We commented out the default setting and left it in the file Example 2 6 Edit the sshd_config file HostbasedAuthentication no HostbasedAuthentication yes 2 Edit the etc ssh shosts equiv file The shosts equiv file can be found in etc ssh on Linux If this file does not yet exist create the file Ensure that the file is owned by the root user and only allows user read write access group other read access See Example 2 7 on page 55 Up and Running with DB2 on Linux Example 2 7 Create shosts equiv and modify the file properties cd etc ssh touch shosts equiv chown root root shosts equiv chmod 644 shosts equiv Each host must be able to communicate with every other host in a partitioned database environment so you must set up the shosts equiv file so that it can be reused on all hosts In our example we only have two partition servers mensa and gemini Edit the file as shown in Example 2 8 Example 2 8 E
80. backup restore or reorganization and potentially boost query performance through data partition elimination When you design your database you might want to consider the table partitioning feature for large tables For more details refer to Database Partitioning Table Partitioning and MDC for DB2 9 SG24 7467 The major purpose of row compression is to save disk storage space Additional advantages of row compression include possible disk I O savings increasing buffer pool hit ratio and decreasing backup image sizes For more details refer to Information Center at http publib boulder ibm com infocenter db21uw v9r5 topic com ibm db2 luw admi n dbobj doc doc c0023489 htm1 Chapter 3 Post installation tasks 119 3 4 Further configuration DB2 uses log files to record its transactions To improve the performance and to ease the maintenance work consider changing the location for online logs archive logs and db2diag log 3 4 1 Change the online log path 120 By default the online log path is configured as database db2inst1 NODE0000 SQL00001 SQLOGDIR To change the log path use the Control Center or a command to update the database configuration parameter NEWLOGPATH to the new path The new path becomes effective when the database is in a consistent state and all users are disconnected from the database Note that it is not necessary to issue a db2stop and db2start When the first user reconnects to the database the lo
81. be saved See the help for details Maximum logical partitions This computer will be assigned partition number 0 You can specify the maximum number of logical partitions that can exist on each database partition server This setting applies to all database partition servers in this instance Maximum logical partitions 4 TCP IP Settings Figure 2 17 MPP Installation Set up partitioning options for the DB2 instance 11 On the Set user information for the DB2 instance owner window set the user information for the DB2 instance owner Choose the existing user db2inst1 Note that in our sample db2inst1 s home directory is created on db2home which is NFS shared across the partitioned servers Click Next 12 Set the user information for the fenced user choose the existing user db2fenc1 This user is responsible for executing fenced user defined functions such as UDFs and stored procedures Again note that the home directory location is created on db2home 13 On the Prepare the DB2 Tools catalog window accept the default option Do not prepare the DB2 Tools catalog and click Next 14 Set up notifications If you choose Set up your DB2 server to send notifications specify a Notification SMTP server here and then click Next 15 On the Specify a contact for Health Monitor notification window you can add an Administration contact for this instance and then click Next By default a Health Monit
82. be to perform an offline backup every weekend and an incremental backup during the week 6 1 1 Enable rollforward recovery and log archiving 230 To use all of the functionality available in DB2 to prevent data loss we enable both rollforward recovery and log archiving This combination allows us to recover the database to the point in time of failure The following example steps you through this task in both single and multi partitioned database environments Set up log file management Starting with DB2 Version 8 2 a new log file manager which is fully integrated in the DB2 engine is provided The configuration is performed using the database configuration parameters called LOGARCHMETH and LOGARCHMETRH Up and Running with DB2 on Linux Note The user exit application db2uext2 is no longer needed The database configuration parameters LOGRETAIN and USEREXIT are deprecated in DB2 9 5 but they are still being used by the data servers and clients with prior versions Any value that is specified for these configuration parameters will be ignored by the DB2 9 5 database manager In our example we show you how to archive DB2 logs to disk and Tivoli Storage Manager storage Our first task is to create the file system and directory that will hold the archived log files 1 Use fdisk or any preferred tool to create the file system db2archive and mount it on each host of the database partitioned environment 2 Create directory db2ar
83. can use DB2STOP with the FORCE option Refer to the following steps to restart the database manager as the instance owner in this case db2inst1 1 db2set all grep ADMINSERVER to get the name of the DAS user here dasusr1 2 db2home dasusr1 das bin db2admin stop 3 db2stop force force might be required if other applications are still connected 4 db2start 5 db2home dasusr1 das bin db2admin start Appendix B DB2 Tools Catalog creation 505 At this point in time the Tools Catalog is ready to use You can now start defining schedules using the Task Center 506 Up and Running with DB2 on Linux Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this IBM Redbooks publication IBM Redbooks publications For information about ordering these publications see How to get IBM Redbooks publications on page 510 gt gt gt DB2 UDB Exploitation of the Windows Environment SG24 6893 DB2 9 pureXML Overview and Fast Start SG24 7298 DB2 9 pureXML Guide SG24 7315 DB2 Security and Compliance Solutions for Linux UNIX and Windows SG24 7555 Database Partitioning Table Partitioning and MDC for DB2 9 SG24 7467 Developing PHP Applications for IBM Data Servers SG24 7218 Other publications These publications are also relevant as further information sources IBM DB2 9 5 gt gt gt W
84. code has been compiled the command CREATE FUNCTION is used to register a function into the database manager Example 8 13 shows a UDF written in C It converts a string to lowercase Example 8 13 UDF example written in C tolower c include lt stdio h gt include lt string h gt include lt sqludf h gt void SQL_API_FN to_lower SQLUDF_VARCHAR value SQLUDF_VARCHAR result SQLUDF_NULLIND value_ind SQLUDF_NULLIND result_ind SQLUDF_TRAIL_ARGS int i len if value_ind 1 result_ind 1 returns len strlen value for i 0 i lt len i result i tolower value i result i 0 In Example 8 14 on page 448 we compile this UDF The first cc step compiles the program and the second cc step creates a dynamic object On 64 bit machines use the options m64 and 1ib64 instead Chapter 8 Application development 447 448 Example 8 14 Compiling a UDF db2inst1 puget gt SQLL home db2inst1 sqllib db2inst1 puget gt cc m32 fpic I SQLL include c tolower c D_REENTRANT db2instl puget gt cc m32 fpic shared o tolower tolower o W1 rpath SQLL 1ib32 L SQLL 1ib32 1db2 lpthread db2inst1 puget gt cp tolower SQLL function The resulting executable tolower was copied to the directory lt ins tance home gt sql1lib function From there the database manager will access the UDF after the function is registered by the CREATE FUNCTION command as shown in Example 8 15
85. contains setup and configuration information A response file specifies configuration and setup parameters and the products and components to install Response files have a file type of rsp for example db2wse rsp See Figure 2 2 on page 62 However you have the option to change the name and destination directory while using the DB2 Setup wizard Creating a response file You can run the DB2 Setup wizard in graphical mode one time to capture the values that you enter in a response file Chapter 2 Installation 63 You also can create the response file manually by using the templates provided The response files have a rsp extension and are located in the mnt dvd db2 linux samples or mnt dvd db2 inuxamd64 samples directory on the DB2 product DVD where mnt dvd represents the mount point of the CD or DVD Note On Linux platforms a response file created for a root installation might not be usable for a non root installation Certain response file keywords are valid for root installation only We do not recommend that you edit the sample response file for non root DB2 installation Creating a response file using the DB2 Setup wizard Near the beginning of the DB2 Setup wizard on the Select the installation response file creation or both window Figure 2 2 on page 62 select either Save my installation settings in a response file or Install DB2 Workgroup Server Edition Version 9 5 on this computer and save my settings ina resp
86. db2 create db itsorepl DB20000I1 The CREATE DATABASE command completed successfully db2inst1 mensa db2backup datamove gt db2move itsodb COPY sn DB2INST1 co target_db itsorep schema_map DB2INST1 DB2VS schema_map DB2INST1 DB2VS owner db2vs u db2inst1 p mypassword Application code page not determined using ANSI codepage 1208 kkkkk DB2MOVE kkkkk Action COPY Start time Mon Feb 11 10 15 44 2008 All schema names matching DB2INST1 Connecting to database ITSODB successful Server DB2 Common Server v9 5 0 Copy schema DB2INST1 to DB2VS on the target database ITSOREPL Create DMT SYSTOOLS DMT_47b090d571d8d Start Load Phase db2move finished successfully Files generated COPYSCHEMA 20080211101544 msg LOADTABLE 20080211101544 MSG Please delete these files when they are no longer needed Chapter 6 Administering databases 337 End time Mon Feb 11 10 18 35 2008 The files which were generated during the data move can be checked to see the details about the COPY and the LOAD In our case the following files were created COPYSCHEMA 20080211101544 msg LOADTABLE 20080211101544 MSG LOADTABLE 20080211101544 MSG load 000 LOADTABLE 20080211101544 MSG load 001 LOADTABLE 20080211101544 MSG part 001 YYYY Y In Example 6 61 we confirm that the schema name was changed Example 6 61 Confirm the changed schema name during db2move db2inst1 mensa db2backup datamove gt db2 connect to itsodb Dat
87. db2_a1l managing backup images can be difficult due to the timestamp difference in each database partition backup image The log files cannot be included in the backup image In Version 9 5 when you perform a backup operation from the catalog node of a partitioned database you can specify which database partitions to include in the backup or you can specify that all of the database partitions need to be included The specified database partitions will be backed up simultaneously and the backup timestamp associated with all specified database partitions will be the same Also you can include database logs with an SSV backup including logs in backup images is the default behavior for SSV backup that is if you specify the ON DBPARTITIONNUM parameter Finally when you restore from an SSV backup image you can specify to roll forward to the end of the logs which is the minimum recovery time calculated by the database manager Example 6 13 shows the command to back up all database partitions The ON DBPARTITIONNUMS option specifies the database partition to be backed up If you want to exclude the log files from the backup image use the EXCLUDE LOGS command parameter Example 6 13 SSV backup of all database partitions db2inst1 mensa gt db2 backup db itsodb on all dbpartitionnums online to db2backup compress Part Result 0000 DB20000I The BACKUP DATABASE command completed successfully 0001 DB20000I The BACKUP DATABASE command co
88. db2bp 131 0 NotSet ITSODB 0x000000020023C140 1056 000 01056 554 0 Coord Inst Active 9045 db2instl db2taskd 2 0 NotSet ITSODB 0x00000002007C0080 1057 000 01057 555 0 Coord Inst Active 9045 db2instl db2wlmd 0 0 NotSet ITSODB 0x000000020023AC80 1058 000 01058 556 0 Coord Inst Active 9045 db2instl db2evmg_ 0 0 3 ITSODB 0x00000002007C1540 0 000 00000 557 0 Coord Pooled n a n a n a 0 0 NotSet ITSODB 0x00000002007C2A00 0 000 00000 558 0 Coord Pooled n a n a n a 0 0 NotSet ITSODB Chapter 7 Monitoring and troubleshooting DB2 407 408 We have shown db2pd with options memsets osinfo and agents In the following list we provide more examples of using the tool and the type of information that you can retrieve gt All database and instance scope information db2pd inst alldbs Active transactions db2pd db itsodb transactions Locks db2pd db itsodb locks A specific application 1072 is an application handle db2pd db itsodb applications 1072 Database logs db2pd db itsodb logs Fenced vendor process db2pd db itsodb fvp laml This command applies to backup restore prune history load load copy roll forward and Log Manager where a vendor media device is being used Automatic storage paths defined for the database db2pd db itsodb storagepaths Table and data partition reorganization db2pd db itsodb reorgs Table and index statistics db2pd db itsodb tcbstats 7 4 In the previous example the c
89. dbpartition utility command db2inst1 mensa sqllib gt export DB2NODE 2 db2inst1 mensa sqllib gt db2 terminate db2inst1 mensa sqllib gt db2 add dbpartitionnum without tablespaces DB20000I1 The ADD NODE command completed successfully DB2 has now created the directory structure in database but with the keyword without tablespaces the existing table space in partitions O and 1 has not been created in the new partition The database partition node group for IBMTEMPGROUP is expanded to the new database partition 2 and we have to add a table space container for TEMPSPACE1 on the new partition See Example 3 28 Example 3 28 Add table space container for temp space db2instl mensa gt db2 alter tablespace tempspacel add db2temp db2inst1 NODE0002 ITSODB TEMPSPACE1 on dbpartitionnum 2 DB20000I The SQL command completed successfully All database partition groups that will benefit from the new partition have to be altered so that the new partition can be used First we create a table in the table space SAMPLE_SNG which is in the partition group SNG_01 Example 3 29 Example 3 29 Create table in SNG_01 connect to itsodb CREATE TABLE PART1 P_PARTKEY INTEGER NOT NULL P_NAME VARCHAR 55 NOT NULL P_MFGR CHAR 25 NOT NULL P BRAND CHAR 10 NOT NULL P TYPE VARCHAR 25 NOT NULL P SIZE INTEGER NOT NULL P CONTAINER CHAR 10 NOT NULL P_RETAILPRICE FLOAT NOT NULL P_COMMENT VARCHAR 23 NOT NULL IN SAMPLE_SNG AL
90. display For example you can toggle off or on the display of CPU states or sort the processes list by the memory occupancy percentage or cancel a process in the list Table 7 2 on page 416 shows several commonly used commands Chapter 7 Monitoring and troubleshooting DB2 415 Table 7 2 Frequently used interactive commands for top Immediately updates the display hor Displays a help window that gives a brief summary of the commands and the status of the secure and the cumulative modes nor Changes the number of processes to display You will be prompted to enter the number C Adds fields to display or removes fields from the display Toggles the display of the command name or the full command line Sorts tasks by age newest tasks first eo o Sorts tasks by CPU usage default IM Sorts tasks by the resident memory usage WwW Writes current setup to toprc This is the recommended way to write a top configuration file Example 7 27 shows an interactive display of top when using interactive commands For example press the M key to reorder the processes list by resident memory usage by default it is ordered by process ID press the c key to toggle to the full command line display and use n to control the number of tasks that will be displayed Example 7 27 Using top to monitor system resource usage top 16 58 23 up 9 days 16 12 6 users load average 0 05 0 04 0 01 Tasks 112 total 1 running 111 sle
91. each machine dasusr which is stored in the home directory DAS user considerations for a partitioned database We were not able to place the DAS user home directory in the shared folder because we have the same DAS user ID on each machine in the cluster You need to take note of the following DAS user considerations gt A DAS must be running on each physical machine in the partitioned database for the graphical administration tools for example Control Center to work gt You can only have one DAS on each machine If you have an existing DAS for the old DB2 version we recommend that you drop it and create a new DAS in DB2 9 5 gt Just like an instance each DAS must be created under a user ID It does not matter whether a different user ID is used for each DAS in the environment or whether the same user ID is used and that the user ID s home directory is not shared gt If an existing user is used as the DAS user this user must also exist on all the participating computers before installation gt For response file installs f your response file specifies to create a new DAS user on each machine in the cluster and that user already exists on any of the participating computers that user must have the same primary group as the new DAS user 2 2 7 Enabling ssh for a partitioned database environment installation From DB2 Version 8 2 2 Version 8 Fix Pack 9 forward you can use secure shell ssh as an alternative to
92. from the IBM Web site at http publib boulder ibm com infocenter db21uw v9r5 PDF documentation DVD Unlike the DB2 Information Center you do not need to install the PDF documentation This DVD provides PDF files that you can read directly from the DVD or copy onto your machine For the latest information about DB2 database product documentation refer to the Web site http www 1 ibm com support docview wss rs 7 1 amp uid swg27009474 Chapter 2 Installation 87 88 Installing DB2 Information Center using the DB2 Setup wizard Follow these steps 1 2 3 Log in to the system as a user with root authority Insert and mount the DB2 Information Center product DVD Change to the directory where the DB2 product DVD is mounted by entering the following command cd mnt dvd In this command mnt dvd represents the mount point of the DVD 4 Enter db2setup to launch the DB2 Setup wizard 5 After the launchpad opens you can view the installation prerequisites and the release notes or you can proceed directly to the installation 6 Click Install a Product and the Install a Product window displays 7 On the Install a Product page if you do not have an existing DB2 Information Center installed on your computer launch the installation by clicking Install New On the Welcome to the DB2 Setup wizard window click Next The DB2 Setup wizard will guide you through the program setup process To proceed with the i
93. fundamentals Performance tuning gt Tuning database performance Design Advisor Chapter 8 Application development 467 468 The db2advis command The db2advis command reads the workload from a file containing the SQL statements or from the command line directly The following command calls the Design Advisor for our sample query db2advis d sample s select count from empmdc where expltest TEST t 5 Example 8 43 shows an excerpt of the output of the db2advis command In this example the tool suggests an index on the column EXPLTEST which will improve the performance by 97 percent Example 8 43 Output of the db2advis command Recommending indexes total disk space needed for initial set 0 032 MB total disk space constrained to 21 722 MB Trying variations of the solution set Optimization finished 1 indexes in current solution 322 0000 timerons without recommendations 8 0000 timerons with current solution 97 52 improvement index 1 0 032MB CREATE INDEX DB2INST2 1IDX802051509060000 ON DB2INST2 EMPMDC EXPLTEST ASC ALLOW REVERSE SCANS COMMIT WORK RUNSTATS ON TABLE DB2INST2 EMPMDC FOR INDEX DB2INST2 IDX802051509060000 COMMIT WORK Design Advisor You can start the graphical version of the Design Advisor from the Control Center To start it from the Control Center in the explorer view right click the database that you want and select Design Advisor a
94. gt 3 CURRENT TIMESTAMP lt description gt lt name gt Jean lt name gt lt price gt 7 99 lt price gt lt description gt 4 CURRENT TIMESTAMP lt description gt lt name gt Shirt lt name gt lt price gt 3 99 lt price gt lt description gt Now we can start querying the data Example 8 28 retrieves the product names for all products where the price is less than 9 in XML format The query is specified in XQuery syntax Example 8 28 Retrieve columns in XML format by using XQuery xquery_example sql xquery for i in db2 fn xmlcolumn PRODUCT XDATA description name price lt 9 return i Example 8 29 shows the query execution and the result in XML format Note that for better readability we have stripped the blanks in the output using the cut command Example 8 29 Result of the XQuery db2instl puget gt db2 x tf xquery_example sq cut c1 30 lt name gt Jean lt name gt lt name gt Shirt lt name gt Chapter 8 Application development 457 458 You can also use SQL statements to retrieve data with the XQuery expression in the FROM clause as shown in Example 8 30 The function XMLEXISTS matches all records from the XQuery expression Example 8 30 Match XML records in the FROM clause select_xquery sq SELECT entityid FROM product WHERE XMLEXISTS i description price lt 9 PASSING xdata AS i 3 The output is shown in Example 8 31 Example 8 31 Result of the script select_
95. gt lt xsl template gt lt xsl template match name gt lt tr gt lt td gt lt xs l value of select gt lt td gt lt tr gt lt xsl template gt lt xsl stylesheet gt In Example 8 39 we use query for applying the transformation Example 8 39 Apply XSLT query_html sql VALUES SUBSTR XSLTRANS FORM XMLELEMENT NAME products XMLQUERY db2 fn xmlcolumn PRODUCT XDATA description name price lt 9 USING SELECT xslt FROM xslt WHERE doc_id 1 1 200 The function XMLQUERY retrieves the result set as XML documents The function XMLELEMENT places the lt product gt attribute around the individual XML documents Then XSETRANSFORM is used to transform the document into the HTML output by using the XSLT Example 8 40 shows the output which is an HTML and can be used directly by a browser Example 8 40 Result of the XML transformation as text db2instl puget gt db2 x tf select6 sql lt html gt lt body gt lt hl gt List of items lt h1 gt Chapter 8 Application development 461 lt table border 1 gt lt tr bgcolor cccccc gt lt th align left gt Product lt th gt lt tr gt lt tr gt lt td gt Jean lt td gt lt tr gt lt tr gt lt td gt Shirt lt td gt lt tr gt lt table gt lt body gt lt html gt Figure 8 4 shows the HTML in a browser File Edit View History Bookmarks 1 63 ol _ Authentic J IBMDB2V
96. gt db2 tf select_xq sql lt ul gt lt 1i gt Jean lt 1i gt lt 1i gt Shirt lt 1i gt lt ul gt 1 record s selected As you can see XML is seamlessly integrated into DB2 You can convert data between the relational and the XML structure The query in Example 8 34 can be embedded into PHP easily Chapter 8 Application development 459 460 In Example 8 36 we retrieve relational data into an XML structure Example 8 36 Extract XML structure from a table extract_xml sql SELECT XMLELEMENT NAME emp XMLELEMENT NAME emp loyee no empno tname lastname XMLELEMENT NAME firstname firstnme XMLELEMENT NAME Tas XMLELEMENT NAME sal FROM employee WHERE salary lt 37000 ary salary The function XVLELEMENT is used to construct the XML data structure You can see the output in Example 8 37 Example 8 37 Example for extracted XML db2instl puget gt db2 x tf extract_xml sql firstname gt lt salary gt 0036250 00 lt salary gt lt emp oyee gt cut cl 130 lt emp oyee gt lt empno gt 000280 lt empno gt lt 1 as tname gt SCHNEIDER lt 1astname gt lt firstname gt ETHEL lt s lt employee gt lt empno gt 000290 lt em tname gt lt salary gt 0035340 00 lt s lt employee gt lt empno gt 000310 lt em irstname gt lt salary gt 0035900 00 lt employee gt lt empno gt 200310 lt em irstname gt lt salary gt 0035900 lt employee gt lt empno gt 200330 lt em tname gt
97. host trust relationships Because we have not set up any host trust relationships the first time that ssh is issued to a new host you will be prompted with a message saying that the authenticity of the target host cannot be established To overcome this situation you can form a trust relationship with the other hosts in the partitioned database environment To achieve this trust relationship use the Up and Running with DB2 on Linux ssh keyscan utility to gather the public host key for each host in the partitioned database environment and save the keys in the known_hosts file Example 2 21 shows how to use the ssh keyscan utility to gather RSA keys to set up the host trust relationships Example 2 21 Gather the RSA public keys ssh keyscan t rsa mensa mensa itsosj sanjose ibm com 9 43 86 90 gt gt ssh known_hosts ssh keyscan t rsa gemini gemini itsosj sanjose ibm com 9 43 86 94 gt gt ssh known_hosts Example 2 22 shows how to use the ssh keyscan utility to gather DSA keys to set up the host trust relationships Example 2 22 Gather the DSA public keys ssh keyscan t dsa mensa mensa itsosj sanjose ibm com 9 43 86 90 gt gt ssh known_hosts ssh keyscan t dsa gemini gemini itsosj sanjose ibm com 9 43 86 94 gt gt ssh known_hosts Verify the ssh configuration To verify the ssh configuration log on to each machine as the DB2 partitioned instance owning user ID and type the following commands as shown in Example
98. if it has not already been enabled for your user in profile db2inst1 sqllib db2profile c Untar DBD DB2 1 1 by entering the following command tar xvzf DBD DB2 1 1 tar gz d In the DBD DB2 1 1 directory run the following commands to build and install the DBD DB2 driver perl Makefile PL make make test The command descriptions e The make command builds the software e The make test command executes self tests e Now log in as root user and run the following command from the same directory make install The make install command installs the DBI Enable the DBI module To enable Perl to load the DBI module you must include the following line in your Perl program use DBI The DBI module automatically loads the DBD DB2 driver when you create a database handle using the DBI gt connect statement using the following syntax my dbhandle DBI gt connect dbi DB2 dbalias userID password In the previous statement dbhandle represents the database handle returned by the connect statement Up and Running with DB2 on Linux dbalias represents a DB2 alias cataloged in your DB2 database directory userID represents the user ID that is used to connect to the database password represents the password for the user ID to connect to the database Example 8 7 shows a short Perl program that uses DBI It uses the SAMPLE database Before running the example you have to repl
99. in Example 7 7 after the Health Monitor executed this predefined command automatically the output of the db2 list tablespaces show detail command shows that the total pages of the table space TBSPDMS_0 have been extended to 20 MB 8 KB x 2 560 on each partition Example 7 7 The db2 list tablespaces show detail command output db2inst1 mensa db2home db2inst1 script gt db2_all echo DB2NODE db2 list tablespaces show detail DB2NODE 0 Tablespaces for Current Database essees Tablespace ID 8 Name TBSPDMS_0 Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Chapter 7 Monitoring and troubleshooting DB2 379 380 Normal Total pages 2560 Useable pages 2528 Used pages 1184 Free pages 1344 High water mark pages 1184 Page size bytes 8192 Extent size pages 32 Prefetch size pages 32 Number of containers 1 Minimum recovery time 2008 02 21 22 46 03 000000 DB210111 In a partitioned database server environment only the table spaces on the current node are listed mensa db2 list tablespaces completed ok DB2NODE 1 Tablespaces for Current Database sseo Tablespace ID 8 Name TBSPDMS_0 Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Normal Total pages 2560 Useable pages 2528 Used pages 1184 Free pages 1344 Hi
100. information For example if statistics information for the tables or indexes related to the package has been changed in general rebinding is required for better performance An example of using the rebind command is shown in Example 6 45 Example 6 45 Rebinding packages db2inst1l mensa gt db2 rebind MYTEST DB20000I The REBIND PACKAGE command completed successfully Important Be cautious when using the db2rbind utility especially when the ALL parameter is used By default db2rbind will rebind invalid packages only But when ALL is specified all of the packages inside the database both valid and invalid will be rebound If you Know exactly what packages are related to the tables or indexes and the statistics information for those tables or indexes has just been changed we recommend using the REBIND with a specific package name 302 Up and Running with DB2 on Linux 6 3 Moving data using EXPORT IMPORT LOAD and db2move In this section we discuss data movement using DB2 EXPORT IMPORT and LOAD commands EXPORT allows you to export data from database tables into files with different file formats IMPORT writes data into database tables from a source data file LOAD provides the capability to move a large volume of data into the database tables quickly We describe the usage of these utilities as well as the considerations when using the load utility under a multiple database partition environment The db2move utility can be he
101. instance db2icrt s client db2vs If you have already installed a DB2 server product on your machine that is DB2 Enterprise Server Edition you can use the db2icrt command with the s client option to create a separate client instance Now you need to configure the client to access a remote DB2 server To administer a DB2 database remotely you must connect to the server using TCP IP Both TCP IP V4 and TCP IP V6 are supported 3 8 2 Configuring the IBM Data Server Client 154 In order to accept connection requests from a Data Server Client using TCP IP you have to configure the database server On the DB2 server verify the following items gt The db2 services name and port are set in the etc services file for example db2c_db2inst1 50001 tcp gt The DB2COMM registry variable is set for TCP IP Use the db2set all command and look for DB2COMM TCPIP gt The TCP IP port name in the database manager configuration is already set db2instl mensa gt db2 get dbm cfg grep SVCE TCP IP Service name SVCENAME db2c_db2inst1 When the changes have been made you must restart the DB2 server instance Up and Running with DB2 on Linux Now you can configure the DB2 client There are two tools available for configuring client to server communications gt Configuration Assistant This is a graphical tool provided with Data Server Client and DB2 server products on Windows and Linux It is not provided with Data Server Runtime Cli
102. instance owning and fenced users as well as the tools catalog database if it was selected during the installation The second response file only installs the appropriate DB2 filesets specifies DAS properties and specifies languages to install Only use the db2ese_mpp_addpart rsp response file when installing database partition servers on the participating computers Example 2 27 shows the contents of the db2ese_mpp_addpart rsp file in our sample Example 2 27 The db2ese_mpp_addpart rsp file Generated response file used by the DB2 Setup wizard generation time 2 7 08 3 28 PM Product Installation LIC_AGREEMENT ACCEPT PROD ENTERPRISE_SERVER_EDITION FILE opt ibm db2 v9 5 INSTALL_TYPE TYPICAL F DAS_CONTACT_LIST REMOTE DAS_CONTACT_LIST_HOSTNAME mensa itsosj sanjose ibm com DAS_SMTP_SERVER smtp itsosj sanjose ibm com Chapter 2 Installation 83 84 DAS user DAS_USERNAME dasusrl DAS_UID 1003 DAS_GROUP_NAME dasadml DAS_HOME_DIRECTORY home dasusr1 Installed Languages INSTALL_TSAMP YES Use the db2setup command with the r option to install DB2 using the response file on the remaining machines in the cluster For example 1 Log in to the primary machine as the instance owner In our sample we logged in to mensa as db2inst1 2 Issue the db2stop command to stop the DB2 instance db2stop force 3 Remove the salllib directory rm rf sqllib 4 Log in to the other machi
103. later Here is a list of other useful views gt Navigator This view shows you the real file structure You can enable the filters to hide files Turn the filters off to see all files Up and Running with DB2 on Linux gt Servers You can run and debug J2EE applications within the debugging framework In this view you can manage the servers for running and deploying the applications gt Problems This view is usually already open in one of the tabs It shows you the compilation or syntax problems of the currently open projects gt Error Log This view is usually already open in one of the tabs It shows you the general error messages in your environment gt Console Here you can see console output from Java programs or from application servers while running or debugging applications In the console view you can switch between the outputs of the concurrently running programs gt Bookmarks Here you can bookmark sections in your code and quickly navigate through them gt Search This view contains a list of your search results and provides meanings to navigate through them Editors Editors are associated with the type of the file that you edit For instance in Figure 5 13 on page 212 the XML editor is used to edit the XML file For other file types there are other editors available If there is no editor for a particular file type the text editor is used The editor tool bar Figure 5 16 allows you t
104. level pricing for the small and medium business SMB market DB2 Express 9 5 includes the same autonomic manageability features of the more scalable editions You never have to change your application code to upgrade simply install the license certificate DB2 Express 9 5 can be deployed on systems with up to two processors The DB2 data server cannot use more than 4 GB of memory 8 Up and Running with DB2 on Linux DB2 Workgroup Server Edition DB2 Workgroup 9 5 is the data server of choice for deployment in a departmental workgroup or medium sized business environment DB2 Workgroup 9 5 can be deployed on systems with up to four processors and 16 GB of memory DB2 Enterprise Server Edition DB2 Enterprise 9 5 is designed to meet the data server needs of mid size to large size businesses It can be deployed on servers of any size from one processor to hundreds of processors DB2 Enterprise 9 5 is an ideal foundation for building on demand enterprise wide solutions such as high performing 24x7 available high volume transaction processing business solutions or Web based solutions It is the data server back end of choice for industry leading Independent Software Vendors ISVs building enterprise solutions such as business intelligence content management e commerce enterprise resource planning customer relationship management or supply chain management Additionally DB2 Enterprise 9 5 offers connectivity compatibility and integrat
105. log files NEWLOGPATH Path to log files db210g1 1TSODB NODEO000 Mirror log path MIRRORLOGPATH db210g2 1TSODB NODEO000 This action is also logged in db2diag log The logging parameters can also be changed in the Command Center Right click the database under All Databases select Configure Database Logging Here you can change the logging parameters apply the changes and save them Up and Running with DB2 on Linux 3 4 2 Change the archive log path By default circular logging is set for a new database With this type of logging only full and offline backups of the database are allowed For recovery the database can only be restored to the last offline backup not to the point of failure In order to enable full recovery of the database up to a specific point in time you must enable archive logging These archived logs are then used by the restore command to recover the database up to the current point in time Chapter 6 Administering databases on page 227 describes the setup of the archive logs path in detail 3 4 3 Change the path for db2diag log DB2 logs information such as an administrative event or errors in the diagnostic file db2diag log This is an instance level log file and is located in lt instance home gt sqllib db2dump by default It is a good practice to examine this file from time to time Frequently this file contains additional information about several DB2 commands especially commands tha
106. log on to each machine as the DB2 partitioned instance owning user ID and enter the commands as shown in Example 2 30 Example 2 30 Verify ssh configuration in DB2 environment ssh mensa echo hi ssh gemini echo hi db2_all echo hi db2_all db2_all echo hi These commands will complete successfully without prompting for additional verification Starting and stopping instance manager to verify installation You can issue the db2start command to verify the installation now If the installation is successful you can use the db2start and db2stop commands to start or stop the instance manager on the primary machine or any participating machine Example 2 31 shows the output of the db2start and db2stop commands on mensa Example 2 31 Using db2start and db2stop to verify installation db2inst1 mensa db2home db2inst1 gt db2start 02 07 2008 16 59 05 O 0 SQL1063N DB2START processing was successful 02 07 2008 16 59 06 1 0 SQL1063N DB2START processing was successful SQL1063N DB2START processing was successful db2inst1 mensa db2home db2inst1 gt db2stop 02 07 2008 17 05 02 0 0 SQL1064N DB2STOP processing was successful 02 07 2008 17 05 02 1 0 SQL1064N DB2STOP processing was successful SQL1064N DB2STOP processing was successful Up and Running with DB2 on Linux 2 3 4 Installing DB2 license files You must install a license key for each DB2 copy Therefore in a partitioned environment you must install a license key on each
107. looks similar to this output Shared Memory Limits max number of segments 4096 SHMMNI max seg size kbytes 32768 SHMMAX max total shared memory kbytes 8388608 SHMALL min seg size bytes 1 Semaphore Limits max number of arrays 1024 SEMMNI max semaphores per array 250 SEMMSL max semaphores system wide 256000 SEMMNS max ops per semop call 32 SEMOPM semaphore max value 32767 Messages Limits max queues system wide 1024 MSGMNI 1 For root installations if kernel shmmax is set to a low value you might encounter the memory allocation error while starting the instance and then you must update kernel shmmax manually Up and Running with DB2 on Linux max size of message bytes 65536 MSGMAX default max size of queue bytes 65536 MSGMNB We recommend that you set the SHMMAX value to be equal to the amount of physical memory on your system However the minimum required on x86 systems is 268435456 256 MB and for 64 bit systems it is 1073741824 1 GB In this example SHMALL is set to 8 GB 8388608 KB 8 GB If you have more physical memory than 8 GB for DB2 increase the value of this parameter to approximately 90 of your computer s physical memory The kernel parameter sem consists of four tokens SEMMSL SEMMNS SEMOPM and SEMMNI SEMMNS is the result of SEMMSL multiplied by SEMMNI The database manager requires that
108. must be set up as a recoverable database At the end of the restore operation the database will be in the rollforward pending state which gives you the capability to roll forward the database to a specific point in time or to the end of the log Note There are two steps involved in restoring and rolling forward the database by using the RESTORE and the ROLLFORWARD commands Or you can use the RECOVER command to restore and roll forward the database with only one command db2 recover database itsodb The RECOVER command reads the database history file to get all of the necessary information to restore and roll forward the database You can check the progress of the rollforward process with the command db2 rollforward db itsodb query status Using the rol1forward command you can specify a timestamp or end of logs which tells the database how far to roll forward There are two types of rollforward recovery to consider gt Database rollforward recovery This process applies transactions that were recorded in the database logs to the database The ro11 forward utility reads the needed log files either archived or active log files Already archived logs will be retrieved using the log archive method The simplest way to roll forward the database as far as possible is by using the command db2 rollforward db itsodb to end of logs and stop Chapter 6 Administering databases 257 If you need to roll forward the database to a specifi
109. on the first time that the packages are used 25 Migrate the DB2 Explain tables 26 Copy the customized codepage conversion tables to the proper directories 27 Back up the migrated databases 28 Check and reorganize the index or tables if required 29 Migrate the DB2 administration server 30 Migrate the DB2 clients 4 4 32 bit to 64 bit conversion 188 If you are running a DB2 Version 8 or Version 9 Enterprise edition under 32 bit Linux be aware that Version 9 5 is only supported on 64 bit architecture DB2 Workgroup Edition provides both 32 bit and 64 bit support For more details about recommended and validated environments for DB2 Version 9 5 on Linux refer to the Web site http www ibm com software data db2 1inux validate Even though you are running with a validated environment and a version of 32 bit DB2 9 5 such as the Workgroup edition consider migrating to DB2 9 5 64 bit instead to avoid any 32 bit kernel limitations There are two considerations regarding 32 bit virtual memory address limits and the new multi threaded architecture gt Agent private memory for all agent threads is now allocated within a single process The process memory space might not be large enough to allocate Up and Running with DB2 on Linux the aggregate of all private memory for all agents You might need to reduce the number of configured agents gt Support for multiple databases is limited because all database shared memory
110. overview we describe the following topics gt DB2 for Linux features and offerings Covers features supported platforms products and packages gt DB2 environment Covers deployment topologies and db2 database objects gt Parallelism with DB2 Covers SMP environments database clusters and partitioned databases Copyright IBM Corp 2008 All rights reserved 1 1 1 Overview 2 It was not too long ago that Linux servers were used primarily in the academic and scientific domain In just a few short years Linux has earned the designation of being one of the fastest growing server operating platforms and is becoming increasingly pervasive in the enterprise Its openness flexibility and ability to lower the cost of ownership are just a few of the factors that have contributed to this operating system s phenomenal success in the commercial arena of e business systems Once relegated to running infrastructure tasks such as file and Web serving Linux has now found its way into the enterprise datacenter Many companies have moved beyond the initial phases of experimentation and testing and are now reaping the benefits of deploying mission critical applications and databases with Linux and DB2 IBM DB2 has long been known for its technology leadership Therefore it was not surprising when IBM took the lead in bringing DB2 proven performance scalability and ease of use features to Linux Over the years DB2 has kept up its lead by
111. plan for the embedded SQL statements This package is dedicated to this particular compiled file If you compile the program file again you will get a new bind file Before you can runa program you need to bind the related packages to the database The advantage of using the package is that the access plans of the SQL statements have already been generated during the precompilation step The access plans of the SQL statements do not need to be generated at run time any more For complex SQL statements this feature can save a considerable amount of execution time Packages also allow you to grant permissions to the users or applications at the package level without the need to grant access to the individual tables In order to run embedded SQL programs you need at least a DB2 client installed on the local system Example 8 11 shows a simple C program using embedded SQL It reads records from the EMPLOYEE table and uses a cursor to cycle through the result set Before running the example you have to replace the lt passworda gt Example 8 11 Embedded SQL program test_emb sqc EXEC SQL INCLUDE SQLCA include lt stdio h gt include lt stdlib h gt include lt string h gt int main int argc char argv EXEC SQL BEGIN DECLARE SECTION 444 Up and Running with DB2 on Linux char empno 7 char database 20 char user 20 char password 20 EXEC SQL END DECLARE SECTION strcpy database SAMPLE strcpy user d
112. processed for each table space Note DB2 supports the recovery of a dropped table by using table space level restore if the table space where the table resides is enabled for dropped table recovery This dropped table recovery can be done during table space creation or by altering an existing table using the DROPPED TABLE RECOVERY ON option We show an example in 6 1 7 Recovering a dropped table sample scenario on page 269 Monitoring restore and rollforward utilities Similar to the backup utility the RESTORE and ROLLFORWARD utilities write entries into the database recovery history file for each backup You can query the database recovery history file for each backup by using the LIST HISTORY Up and Running with DB2 on Linux command During the run time of the utilities you can use the LIST UTILITY command to monitor the RESTORE and ROLLFORWARD utilities The same information can be retrieved using the administrative views SNAPUTIL and SNAPUTIL_PROGRESS or the table functions SNAP_GET_UTIL and SNAP_GET_UTIL_PROGRESS Example 6 23 shows the output for a table space restore on database partition 0 and a following rollforward Example 6 23 Monitor restore and rollforward db2instl mensa gt db2 list utilities ID 331 Type RESTORE Database Name ITSODB Partition Number 0 Description tablespace TSDATA2 Start Time 02 21 2008 15 23 01 033971 State Executing Invocation Type User db2instl mensa gt db2
113. program that selects from the EMPLOYEE table in the SAMPLE database Before running the example you have to replace the lt passwora gt Example 8 9 CLI program cli_test c include lt stdio h gt include lt sqlclil h gt main SQLRETURN cliRC SQL SUCCESS SQLHANDLE henv hdbc hstmt Variable which return the row data struct SQLINTEGER ind SQLCHAR val 7 empno Chapter 8 Application development 441 442 Allocate environment handle if cliRC SQLA1locHandle SQL_HANDLE_ENV SQL_NULL_HANDLE amp henv SQL_SUCCESS fprintf stderr CLI error d in SQLAllocHandle n cliRC exit cliRC Allocate database handle if cliRC SQLAllocHandle SQL_HANDLE DBC henv amp hdbc SQL SUCCESS fprintf stderr CLI error d in SQLAllocHandle n cliRC exit cliRC connect to the database if cliRC SQLConnect hdbc SQLCHAR SAMPLE SQL_NTS SQLCHAR db2inst1 SQL_NTS SQLCHAR lt password gt SQL_NTS SQL_SUCCESS fprintf stderr CLI error d in SQLConnect n cliRC exit cliRC 3 allocate a statement handle if cliRC SQLAllocHandle SQL_HANDLE STMT hdbc amp hstmt SQL SUCCESS fprintf stderr CLI error d in SQLAllocHandle n cliRC exit cliRC directly execute the statement cliRC SQLExecDirect hstmt SQLCHAR select empno from employee where salary lt 36000 SQL_NTS if cliRC SQL_SUCCESS fprintf s
114. puget gt db2 runstats on table db2inst2 empmdc and indexes all DB20000I1 The RUNSTATS command completed successfully This column is created without an index We populate it with sample data and perform a runstats so that the index statistics are up to date The new column is used to demonstrate the usage of explain and the design advisor As a second preparation step we create the explain tables by running the script db2 tvf lt instance dir gt sqllib misc EXPLAIN DDL 8 5 1 Explain facility Before DB2 executes an SQL statement it creates an access plan that describes how DB2 accesses the data in order to generate the result set For static SQL statements the access plan is stored in the related package For dynamic SQL statements the access plan is generated at run time If you want to tune a query you can use the explain facility to view the access plan to understand how DB2 accesses the tables to form the result set You can then decide if the query performance can be improved by adding indexes or rearranging the query There are two tools for creating a visual access path Visual Explain and the explain command Chapter 8 Application development 463 464 Note The explain facility is described in detail in Tuning Database Performance SC23 5867 in Visual Explain Tutorial SC23 5868 and in the Information Center by selecting Database fundamentals gt Performance tuning gt Tuning database application performan
115. remote shell rsh to execute commands on remote DB2 nodes in the DB2 partitioned database environments Because ssh is more secure than rsh or rhost based authentication we recommend that you configure DB2 to use ssh in the partitioned database environments To run DB2 Enterprise Server Edition successfully the ssh server and client must be available on all machines in the partitioned database system Prior to Chapter 2 Installation 53 54 enabling ssh ensure that the ssh sever and client packages are installed They are not installed by default in certain distributions This section shows you how to configure ssh for host based and public key based authentication on Linux You can choose to use either the host based authentication or the public key based authentication when setting up ssh You can also choose to use either the Rivest Shamir Adleman algorithm RSA or the digital signature algorithm DSA encryption as the form of encryption You need to base this decision on your organization s security requirements Setting up host based authentication Host based authentication allows any user ID from machineA to use ssh to log in as that same user ID on machineB assuming that the ssh client on machineA is configured to use host based authentication and the ssh server on machineB is configured to allow host based authentication In your partitioned database environment each partition server needs to be configured to use host based
116. section you can specify user ID mappings By default permissions are set to rw and root_squash The root_squash setting means that the root user on a client is not treated as root when accessing files on the NFS server Although this mode of operation is typically desirable in a production environment you need to turn it off in order to create users on each of the remaining machines in the cluster To turn off the root_squash setting specify no_root_squash in the permissions section Before deploying your environment on production consider changing permissions to the default setting that is rw root_squash For instance change the etc exports file to export db2home mensa rw sync gemini rw sync 5 Export the NFS directory by running usr sbin exportfs a This command initializes a file named var lib nfs xtab and exports all directories to this file Note If you make an update to efc exports run exportfs r to re export all directories This command synchronizes var lib nfs xtab with etc exports and removes entries in var lib nfs xtab that are deleted from etc exports 6 On each of the machines in the cluster including the NFS server first make a directory db2home using the mkdir command and then add an entry to the etc fstab file to NFS to mount the file system automatically at startup time We recommend that you configure the file system to be mounted at startup time to be read write to be mounted hard and
117. segments for all databases are allocated in a single process memory space You can reduce the memory usage for each database so that you can activate all databases successfully However the database server performance is impacted Note You cannot specify the bit size for the instance when you create or migrate an instance The bit size for new instances is determined by the operating system where DB2 9 5 is installed Table 4 5 shows important details about available support for 32 bit and 64 bit DB2 Table 4 5 Available support for 32 bit and 64 bit DB2 9 5 32 bit instances only 32 bit DB2 server client and GUI tools packages 32 bit IBM Software Development Kit SDK for Java 64 bit instances 32 bit and 64 bit DB2 libraries available 64 bit DB2 server and client 64 bit applications and routines 32 bit client side application support 32 bit fenced stored procedures user defined functions UDFs only non Java Java fenced Stored Procedures UDFs 64 bit IBM SDK for Java If you are running in a validated 64 bit environment converting from 32 bit to 64 bit is done automatically during the migration process Example 4 17 shows a few details of a migration from Version 8 2 32 bit to Version 9 5 64 bit DB2 9 5 Example 4 17 Migrating from DB2 Version 8 32 bit to DB2 Version 9 5 64 bit with db2 instance owner db2instl gemini gt db2level DB21085I Instance db2instl uses 32 bits and DB2 code release SQL08028
118. setup throughout this book Table 2 9 Database related file system partition setup sample db2log2 Used to store DB2 mirroring log files db2logarc Used to store the archived log files db2temp For storing DB2 temporary table spaces software Used for storing software For example we downloaded the DB2 install image into this directory a export db2home in the partitioned database environment Log space By default DB2 sets the log path to the default database path during database creation For example our default database path is database and our log path is database db2inst1 NODE0000 SQL00001 SQLOGDIR We recommend that you store both the primary copy of the logs and the mirror logs each on a physically separate disk preferably a disk that is also ona different disk controller Mirror logs are created using the MIRRORLOGPATH configuration parameter Log mirroring allows the database to write an identical second copy of log files to a different path Note Mirroring log files helps protect a database from accidental deletion of an active log and data corruption that is caused by disk error While this functionality increases the high availability of a system log mirroring can impact system performance because all log data will be written to both the log path and the mirror log path 44 Up and Running with DB2 on Linux In Example 2 3 we change the primary log path from the default to db2log1 ITSODB and set the mi
119. sqllib function dpfhome dpfusr1 routine_backup If you use distributed transactions involving DB2 databases ensure that the databases to be migrated do not contain any indoubt transactions by using the LIST INDOUBT TRANSACTIONS command to get a list of indoubt transactions and to interactively resolve any indoubt transactions During the database migration to DB2 Version 8 the EXECUTE privilege is granted to public for all existing functions methods and external stored procedures You can use the db2undgp command to revoke this privilege on all these routines The command db2undgp is no longer supported in DB2 9 5 If you want to revoke the EXECUTE privilege using this command you must revoke it before the migration to DB2 9 5 If you ran the db2undgp command after migrating your databases to DB2 UDB Version 8 or DB2 9 1 you do not have to run this command again after migrating to DB2 9 5 Example 4 4 shows a db2undgp execution In this example a file that contains all the REVOKE statements needed to remove the EXECUTE privilege from PUBLIC is created You can review or edit this file Example 4 4 db2undgp dpfusrl mensa gt db2undgp d dpfsamp o dpfhome dpfusrl revoke db2 db2undgp processing begins for database dpfsamp db2undgp has completed successfully db2undgp complete successfully for database dpfsamp Grant the EXECUTE privilege on all of your routines to specific users or a group only The following statement sho
120. statement with automatic storage off and manually defined table space containers Example 3 12 DDL to create the database with containers specified CREATE DATABASE ITSODB AUTOMATIC STORAGE NO ON database ALIAS ITSODB USING CODESET UTF 8 TERRITORY US COLLATE USING SYSTEM PAGESIZE 4096 CATALOG TABLESPACE MANAGED BY SYSTEM USING db2catalog USER TABLESPACE MANAGED BY DATABASE USING FILE db2user contl tbsp 89600 TEMPORARY TABLESPACE MANAGED BY SYSTEM USING db2temp WITH Lab database for ITSO Note The CREATE DATABASE command is explained in more detail in DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 3 3 2 Creating a multiple partitioned database You can also use the Create Database Wizard to create a multi partitioned database However for a multi partitioned environment we recommend that you use the DB2 command line instead of the Create Database wizard In this section we provide an example of setting up a partitioned database over two physical hosts with one logical partition on each host Before you create a multi partitioned database consider which partition will be the catalog partition In a partitioned database environment the create database command affects all database partitions that are listed in the db2nodes cfg file The database partition from which this command is issued becomes the catalog database partition for the new database 112 Up and Running with DB2 on Linux Tip On
121. statistics and check the table again 4 Run REORG TABLE and REORG INDEXES with different options 5 Use REORGCHK with the UPDATE STATISTICS option to update statistics and check the table again 6 Rebind packages if required Here are the details of each step 1 Use RUNSTATS to gather the current statistics information for the sample table ITEM Refer to Example 6 35 Example 6 35 Using RUNSTATS and REORGCHK to gather and check statistics db2instl mensa gt db2 runstats on table db2instl item with distribution on all columns and detailed indexes all allow read access DB20000I1 The RUNSTATS command completed successfully db2inst1 mensa gt db2 reorgchk current statistics on table db2instl item Table statistics Fl 100 OVERFLOW CARD lt 5 F2 100 Effective Space Utilization of Data Pages gt 70 F3 100 Required Pages Total Pages gt 80 SCHEMA NAME CARD OV NP FP ACTBLK TSIZE F1 F2 F3 REORG 3000728 0 7394 7394 60014560 0 99 100 Index statistics F4 CLUSTERRATIO or normalized CLUSTERFACTOR gt 80 F5 100 Space used on leaf pages Space available on non empty leaf pages gt MIN 50 100 PCTFREE Chapter 6 Administering databases 291 F6 100 PCTFREE Amount of space available in an index with one less level Amount of space required for all keys lt 100 F7 100 Number of pseudo deleted RIDs Total number of RIDs lt 20 F8 100 Number of pseudo empty leaf pa
122. table item inplace Table db2inst1 item will be reorganized online The INPLACE option of the REORG command specifies an online reorganization If this is not specified an offline REORG is run Offline classic reorganization The offline method provides the fastest table reorganization especially if you do not need to reorganize large object LOB or LONG data LOBs and LONG data are not reorganized unless specifically requested In addition indexes are rebuilt in order after the table is reorganized Read only applications can access the original copy of the table except during the last phases of the reorganization in which the shadow copy replaces the original copy and the indexes are rebuilt A simple command for an offline reorganization is db2 reorg table db2instl item You can also use the ADMIN_CMD procedure db2 call sysproc admin_cmd reorg table db2instl item Chapter 6 Administering databases 281 282 Note In general classic table reorganization is faster but it can be used only if your applications function without write access to tables during the reorganization In addition classic table reorganization will require the creation of a shadow copy of the table so approximately twice as much space as the original table will be required If your environment does not allow this the use of this additional space although inplace reorganization is slower it can occur in the background while normal data access c
123. table space utilization to configure the settings for this health indicator See Figure 7 13 on page 366 Chapter 7 Monitoring and troubleshooting DB2 365 Configure Health Indicator able Space Utilization ts ts_util Figure 7 13 Configuring a health indicator for table space utilization f You can click Show Command to get the command that is generated based on the options that you have chosen Refer to Figure 7 14 You can run the command in DB2 CLP to change the configuration for the health indicator or you can click OK to submit your changes Show Command PDATE ALERT CFG FOR TABLESPACE TBSPDMS_0 ON ITSODB USING ts ts_util SET ALARM 90 WARNING 80 SENSITIVITY 0 THRESHOLDSCHECKED YES ACTIONSENABLED NO Figure 7 14 Set health indicator value command g You can use the DB2 CLP command GET ALERT CFG to verify the setting as shown in Example 7 3 on page 367 366 Up and Running with DB2 on Linux Example 7 3 Using GET ALERT CFG to view health indicator status db2inst1 mensa db2home db2inst1 gt db2 get alert cfg for tablespace tbspdms_0 on itsodb Alert Configuration Indicator Name Default Type Warning Alarm Unit Sensitivity Formula ts ts_used_pages ts ts_usable_pages Actions Threshold or State checking Indicator Name Default Type Sensitivity Formula Actions Threshold or State checking Indicator Name Default Type Sensitivity Formula Actions Threshold or State checking Indicator
124. takes advantage of CIO on file systems where this feature exists This feature might help to reduce the memory requirements of the file system cache thus making more memory available for other uses Prior to Version 9 5 the keyword FILE SYSTEM CACHING was implied if neither NO FILE SYSTEM CACHING nor FILE SYSTEM CACHING was specified With Version 9 5 if neither keyword is specified the default NO FILE SYSTEM CACHING is used This change affects only newly created table spaces Existing table spaces that were created prior to Version 9 5 are not affected This Up and Running with DB2 on Linux change applies to Linux with the following exceptions where the default behavior remains FILE SYSTEM CACHING gt Linux for System z gt All SMS temporary table space files gt SMS permanent table space files except for long field LF data and large object LOB data files Table 2 8 shows the supported configuration for using table spaces without file system caching Table 2 8 Supported Linux platform and configuration for using table spaces without file system caching DIO or CIO requests submitted by the database manager when NO FILE SYSTEM CACHING is specified Default behavior when neither NO FILE SYSTEM CACHING nor FILE SYSTEM CACHING is specified File system type and minimum level required Linux distributions ext2 ext3 ReiserFS No file system caching SLES 9 and RHEL 4 x86 x86_64 IA64 and POWER Linux d
125. the Create Database wizard The DB2 instance has already been created during DB2 installation as described in 2 3 Installing DB2 on page 59 The steps to create a single partitioned database using the Create Database wizard are 1 Start the Create Database wizard from the Control Center Right click All Databases and then select Create Database Standard as shown in Figure 3 5 N S2 ew Control Center Control Center Selected Edit View Tools Help DBHSAs BOS Be 3 Control Center control Center W O All Systems hana 4 BIR EGE Ce O SAMPLE Open New Control Center All Systems Create Database M Standard Add With Automatic Maintenance Register with XSR From Backup Refresh T Figure 3 5 Start the Create Database wizard 108 Up and Running with DB2 on Linux 2 Specify a name for your new database Figure 3 6 Enter Database name ITSODB Database alias ITSODB Comment for the database Lab database for ITSO Check Let DB2 manage my storage automatic storage If you want to restrict user access to the system catalog tables check Restrict access to system catalogs Click Next database ITSODB Lab database for ITSO Figure 3 6 Specify the database name 3 The next panel allows you to show additional storage paths Figure 3 7 on page 110 Chapter 3 Post installation tasks 109 automatic storag
126. the background Or Runs the commands in parallel in the background and terminates the command after all remote commands have completed lt The commands are sent to all of the machines for running except this one lt lt nnn lt Commands are sent to all other database partitions but not the database partition nnn for running Commands are sent to only database partition nnn for running a Substitutes occurrences of lt gt with the machine name Substitutes occurrences of by the machine index and substitutes occurrences of by the node number Example A 1 shows how to connect and list all of the table spaces on all database partitions Example A 1 Using db2_all on a multiple partition environment db2instl gemini gt db2_al1 db2 CONNECT TO itsodb db2 LIST TABLESPACES Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias Tablespaces for Current Database Tablespace ID 1 Name TEMPSPACE1 Type System managed space Contents System Temporary data State 0x0000 Detailed explanation Normal Appendix A Issuing commands to multiple database partitions 495 Tablespace ID Name Type Contents State Detailed explanation Normal Tablespace ID Name Type Contents State Detailed explanation Normal DB210111 on the current node are listed 2 USERSPACE1 Database managed space All permanent dat
127. the number of arrays SEMMNI is increased as necessary Typically SEMMNI needs to be twice the maximum number of agents expected on the system multiplied by the number of logical partitions on the database server computer plus the number of local application connections on the database server computer MSGMAX needs to be changed to 64 KB that is 65536 bytes and MSGMNB needs to be increased to 65536 Modifying kernel parameters on SUSE and Red Hat In this example we explain how to update kernel parameters and set them after each reboot 1 Log in as root 2 Using a text editor add the following entries to etc sysctl conf Example shmmax for a 64 bit system kernel shmmax 1073741824 Example shmall for 90 percent of 16 GB memory The kernel requires this value as a number of pages kernel shmal 1 3774873 kernel sem 250 256000 32 1024 kernel msgmni 1024 kernel msgmax 65536 kernel msgmnb 65536 3 Load these entries into sysctl by using the following command sysctl p Now if you enter the command ipcs 1 you can see that the kernel parameters have been updated in sysctl To view all sysctl settings use the command sysctl a Chapter 2 Installation 31 4 If you want to update kernel parameters for run time only use the sysctl w command For example to change kernel msgmni to 1024 enter the following command sysctl w kernel msgmni 1024 However these settings will not remain after the next
128. the user IDs and groups that DB2 requires and the process of creating them Required users and groups Three users and groups are required for DB2 the instance owning user the DB2 fenced user and the Database Administration Server DAS user You can use the default names provided by DB2 Setup or specify your own user and group names In our setup we used the DB2 Setup wizard default user ID and group names which are shown in Table 2 10 on page 51 4 For non root installation because DAS is not available the DAS user is not required 50 Up and Running with DB2 on Linux Table 2 10 Example of required users for DB2 Pequod user Username Group name escipion db2inst1 db2iadm1 Administers the instance Fenced user db2fenc1 db2fadm1 Responsible for executing fenced user defined functions such as UDFs and stored procedures DAS user dasusr1 dasadm1 Administers the DB2 Administration Server Creating users Root authority is required to create users and groups For root installation there are three ways in which you can create DB2 users and groups gt Using the DB2 Setup wizard gt Using a response file installation gt Creating users and groups in the OS command line or in the OS administration tool For non root installation uses and groups must exist before the installation DB2 Setup wizard The DB2 Setup wizard creates all of the required users and groups for you during installation The default user
129. to include the background bg option and that setuid programs can be run properly Refer to the following example mensa export db2home db2home nfs rw timeo 7 hard intr bg suid lock In this example mensa is the NFS server machine name 7 After adding an entry to the etc fstab file on each machine NFS mount the exported file system on each of the remaining machines in the cluster by entering the following command mount db2home Chapter 2 Installation 49 If the mount command fails make sure that the NFS server is started To restart the NFS server run the following command as the root on the NFS Server workstation etc init d nfs restart You can also use the showmount command to check the status of the NFS server For example showmount e mensa Tips gt Itis considered a good convention to place all the directories that you want to export in the export hierarchy If you need the directory to also exist elsewhere in the directory tree use symbolic links or mount it as an NFS client For example if your server is exporting its db2home hierarchy you place the directory in export therefore creating export db2home Because the server will need access to the export db2home directory mount it on db2home gt If you have an error in your etc exports file the error is reported when NFS starts up in syslog You might find this debugging tool useful 2 2 6 User and group setup In this section we discuss
130. type AUTO_BACKUP AUTO_REORG AUTO_RUNSTATS or MAINTENANCE_WINDOW gt Configuration A binary large object BLOB type argument or an XML file specifying the configuration in XML format The procedure AUTOMAINT GET POLICYFILE allows you to obtain details about the policies in XML format The XML file can be edited as needed and the changes are reimported by using the AUTOMAINT SET POLICYFILE stored procedure In Example 6 20 we obtain the current settings from the database edit the file to define the duration to four hours and set settings for the database Example 6 20 Change the maintenance window db2instl mensa gt db2 call AUTOMAINT_GET_POLICYFILE MAINTENANCE_WINDOW window xml db2inst1 mensa gt cat db2home db2inst1 sql1ib tmp window xml lt xml version 1 0 encoding UTF 8 gt lt DB2MaintenanceWindows xmlns http www ibm com xmlns prod db2 autonomic config gt lt Online Maintenance Window gt lt OnlineWindow Occurrence During startTime 00 00 00 duration 24 gt lt DaysOfWeek gt All lt DaysOflWeek gt lt DaysOfMonth gt All lt DaysOfMonth gt lt MonthsOfYear gt All lt MonthsOf Year gt Chapter 6 Administering databases 253 lt OnlineWindow gt lt DB2MaintenanceWindows gt now edit the file db2home db2inst1 sqllib tmp window xm We will set the maintenance window with a duration of 4 hours only so we change duration 24 to duration 04 Now impor
131. usually runs in a separate process under the fenced user The fenced user is defined in the CREATE INSTANCE command db2icrt u lt fenced id gt lt instance id gt During the development of SPs and UDFs you need to change the database manager configuration parameter KEEPFENCED in the previous version the parameter was named KEEPDARI to NO so that every time that the procedure is invoked the actual version is loaded db2 update dbm cfg using KEEPFENCED NO Note You can obtain more information about stored procedures in Developing User defined Routines SQL and External SC23 5855 8 3 Programming languages In this section we introduce several of the programming languages that you can use on Linux and we explain how to set up the environment for each programming language We discuss the following languages in this section gt C C gt Java gt Hypertext Preprocessor PHP gt Perl In general the following steps are required to use these languages with DB2 1 Set up the application development environment for the language that you are using Build install and test the required programs modules and drivers and make any necessary changes to permissions and paths 2 Identify and include DB2 specific drivers in your code In order for your program to access DB2 you must copy or reference the required code into your program 3 Connect to a specific DB2 database Usually an identifier is generated from th
132. which will start the DB2 communications manager when the database manager is started Enter the following command as instance owner db2set DB2COMM tcpip Stop and restart the instance for these changes to take effect db2stop db2start Use the netstat utility to verify if the TCP IP communication port is listening for example in our sample we entered netstat an grep 50001 2 3 3 Installing a partitioned database environment There are several ways in which you can install DB2 on a multi partition environment gt Use the DB2 Setup wizard to install DB2 and create a new instance on the primary machine and then use a response file to install DB2 on the remaining machines participating in the partitioned database Edit a sample response file and use this file to install DB2 on each machine in the cluster Use db2_install or a combination of DB2 Setup wizard and db2_install to set up your environment The easiest method is to use the DB2 Setup wizard on the primary machine and then a response file on the remaining machines participating in the partitioned database system We discuss this method in this book Preparing the environment The first step of installing a partitioned database environment is preparing the environment including setting up NFS creating users and groups and enabling ssh Refer to 2 2 Installation considerations and planning on page 35 Chapter 2 Installation 79 80 Using DB
133. with level identifier 03090106 Informational tokens are DB2 v8 1 3 136 s070720 MI00194 and FixPak SLS Product is installed at opt IBM db2 V8 1 Chapter 4 Migration and fix packs 189 with root user gemini opt ibm db2 V9 5 instance db2imigr db2inst1l db2ckmig was successful Database s can be migrated DBI1070I Program db2imigr completed successfully with DB2 instance owner db2instl gemini gt db2level DB21085I Instance db2inst1 uses 64 bits and DB2 code release SQL09050 with level identifier 03010107 Informational tokens are DB2 v9 5 0 0 s071001 LINUXAMD6495 and Fix Pack 0 Product is installed at opt ibm db2 V9 5 4 5 Migrating to a new database 190 In this section we demonstrate by a simple example how to migrate to a new database to leverage the DB2 9 5 features and functions enabled at database creation time For example Unicode is set when a database is created You are required to create a new database to convert from a non Unicode database to a Unicode database The procedure to convert a DB2 Version 8 or Version 9 1 non Unicode database to a DB2 9 5 Unicode database is the same Be aware that the migration can take time and requires a large disk space if you have a huge database The following steps convert a non Unicode database to a Unicode database using db2move You can obtain more detail about how db2move works in 6 3 4 Using the db2move uti
134. work over many processes gt MAX_QUERYDEGREE Because parallelism in an OLTP system is undesirable set this value to 1 For DSS set this value to the number of CPUs of the database server to prevent users from setting an incorrect degree in their program which can slow down DB2 activities Note that in a static package if the query degree is set at the bind time the max_querydegree parameter is overridden by the query degree setting gt INSTANCE MEMORY which can be set to AUTOMATIC If this variable is set to AUTOMATIC it is calculated at the start of the instance Setting it to a value allows you to define the memory that is used by the instance gt JAVA_HEAP SZ This value defines the heap size which is used for Java user defined functions UDFs and stored procedures gt SVCENAME SVCENAME defines the TCP IP port number or name that is used by the instance If you use a port name you must define it in etc services Note For a complete and detailed description of all of the database manager configuration parameters refer to the Information Center at http publib boulder ibm com infocenter db21 uw v9r5 index jsp topic com ib m db2 1luw admin config doc doc c0004555 htm Monitor and update the DBM configuration You can configure the settings of a DB2 instance either through the Control Center or on the DB2 Command line Chapter 3 Post installation tasks 137 Control Center Use the following steps
135. you do not need the NFS exported file system for DB2 Example 2 1 df command Filesystem 1K blocks Used Available Use Mounted on dev sda2 50572564 21169652 29402912 42 udev 1921324 184 1921140 1 dev 3 ordered is the ext3 file system default mode Up and Running with DB2 on Linux dev sdb5 20641788 924912 19716876 5 export db2home dev sdb6 4822142 82420 4739722 2 database dev sdb7 1010865 41150 969715 5 db2temp dev sdb8 544166 41280 502886 8 db2logl dev sdb9 544166 41280 502886 8 db2log2 dev sdb10 1010863 41271 969592 5 db2logarc dev sdb11 5099266 2034030 3065236 40 software mensa export db2home 20641792 924896 19716896 5 db2home To show all NFS mounted file systems issue the following command on the host where the file system physically exists Example 2 2 showmount a Example 2 2 showmount command mensa showmount a All mount points on mensa 9 43 86 90 mensa itsosj sanjose ibm com mensa itsosj sanjose ibm com export dbZ2home File system configuration recommendations There are many ways to configure disk partitions and file systems depending on your environment We suggest that you follow these recommendations when configuring your system gt For single and partitioned database systems we recommend that you create a separate file system for the DB2 user home directories In our setup this file system is called db2home for a single partition environment For partitioned
136. 0 DB20000I1 The SET TABLESPACE CONTAINERS command completed successfully RESTORE DATABASE ITSODB CONTINUE DB20000I1 The RESTORE DATABASE command completed successfully We also run the script itsodb_node0001 clp against database partition 1 Because the database is enabled for rollforward recovery we have to perform the rollforward before connecting to the database Example 6 27 shows the steps and the new table space container definition Using the generated script we were able to redefine the table space container path and size easily Example 6 27 Roll forward after redirected restore db2inst1 mensa db2home db2inst1 gt db2 rollforward db itsodb stop Rollforward Status Input database alias itsodb Number of nodes have returned status 2 Node number Roll forward Next log Log files processed Last committed transaction status to be read 0 not pending 0000002 LOG S0000002 L0G 2008 02 07 01 32 41 000000 UTC 1 not pending 2008 02 07 01 36 12 000000 UTC DB20000I The ROLLFORWARD command completed successfully db2instl mensa db2home db2inst1 gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2inst1 mensa db2home db2inst1 gt db2 list tablespace containers for 4 Up and Running with DB2 on Linux Tablespace Containers for Tablespace 4 Container ID 0 Name tablespaces ITS00000 TSDATA1 000 Type Fil
137. 0 00 0 00 0 00 0 0 sdc 0 00 0 00 0 00 0 0 sdd 0 00 0 00 0 00 0 0 sde 0 00 0 00 0 00 0 0 sdf 0 00 0 00 0 00 0 0 avg cpu user nice system iowait steal idle 0 00 0 00 0 50 0 00 0 00 99 50 Device tps Blk_read s Blk_wrtn s Blk_read Blk_wrtn sda 17 50 0 00 240 00 0 480 sdb 0 00 0 00 0 00 0 0 sdc 0 00 0 00 0 00 0 0 sdd 0 00 0 00 0 00 0 0 sde 0 00 0 00 0 00 0 0 sdf 0 00 0 00 0 00 0 0 avg cpu user nice system iowait steal idle 0 00 0 00 0 00 0 00 0 00 100 00 Device tps Blk_read s Blk_wrtn s Blk_read Blk_wrtn sda 0 00 0 00 0 00 0 0 sdb 0 00 0 00 0 00 0 0 sdc 0 00 0 00 0 00 0 0 sdd 0 00 0 00 0 00 0 0 sde 0 00 0 00 0 00 0 0 sdf 0 00 0 00 0 00 0 0 7 6 4 The sar command The sar command is an integrated and powerful System Activity Report sar utility You can use it to collect and report CPU utilization memory and swap space utilization statistics and I O and transfer rate statistics as well as network statistics You can save the output of the sar command into a designated file and retrieve information from that file at a later time The general syntax to run the sar command is sar options interval count Table 7 3 on page 421 gives frequently used command options for sar that are extracted from sar s man pages 420 Up and Running with DB2 on Linux Table 7 3 Frequently used command options for sar opine paeme o o a FULL P ALL p eeo E fo emm Extracts records from the fil
138. 00000 Number of rows skipped 0 Number of rows loaded 3000000 Number of rows rejected 0 Number of rows deleted 0 Number of rows committed 3000000 db2inst1 mensa db2backup datamove gt db2 select count from itemload 3000000 1 record s selected Examples for ALLOW READ ACCESS when loading The ALLOW READ ACCESS option is useful when loading a large amount of data because it allows users to access table data when the load operation is in progress or after a load operation has failed The behavior of a load operation in ALLOW READ ACCESS mode is independent of the isolation level of the application That is readers with any isolation level can always read the pre existing data but they will not be able to read the newly loaded data until the load operation has finished Read access is provided throughout the load operation except at the very end Before data is committed the load utility acquires an exclusive lock Z lock on Up and Running with DB2 on Linux the table The load utility will wait until all of the locks held by all of the applications have been released which might cause a delay before the data can be committed The LOCK WITH FORCE option can be used to force off conflicting applications in order to allow the load operation to proceed without having to wait In Example 6 55 we create a table named ITEMLOAD and insert three rows as the pre existing data We then use ALLOW READ ACCESS to load additional
139. 000170 44680 00 55000 00 500 00 500 00 2008 01 29 03 06 17 353814 4 record s selected 8 2 2 User defined functions DB2 provides many functions called built in functions There are two types of built in functions scalar functions such as date length month and substr and column functions such as count sum max avg and min User defined functions UDFs are functions that can be added to the database They can include scalar function row function column function or table functions UDFs can be written in languages such as C Java or in pure DB2 SQL This section discusses UDFs written in SQL Developing a UDF using C and Java is provided in UDF in C on page 447 and Stored procedures in Java on page 453 separately Chapter 8 Application development 429 UDFs are extremely useful if you want to share business logic among applications The applications can run on different systems and on different architectures Use the CREATE FUNCTION DDL statement to register a function in the database Note The CREATE FUNCTION statement is explained in more detail in the Information Center in Database fundamentals SQL Statements gt CREATE FUNCTION and in SQL Reference Volume 2 SC10 4250 Example 8 3 creates an SQL UDF called salary_diff which receives an employee ID as input and calculates the difference between the old and new salary values from the EMPLOYEE_HIST which is populated through our trigger see
140. 02 13 2008 14 36 34 887245 Database name ITSODB Database path database db2inst1 NODE0000 SQL00002 Input database alias ITSODB Number of accessed tables 21 Table List Table Schema DB2INST1 Table Name ITEM Table Type User Data Object Pages 1851 Index Object Pages 3101 Rows Read Not Collected Rows Written 8251179 Overflows 0 Page Reorgs 8921 Table Reorg Information Node number 0 Reorg Type Reclustering Inplace Table Reorg Allow Write Access Reorg Index Reorg Tablespace 7 Start Time 02 13 2008 14 35 11 064496 300 Up and Running with DB2 on Linux Reorg Phase Max Phase Phase Start Time Status Completed Current Counter 1850 Max Counter 1850 Completion 0 End Time 02 13 2008 14 36 34 691349 Database Partition 0 Database ITSODB Active Up 0 days 05 03 36 Table Reorg Information Address TbspaceID TableID PartID MasterTbs MasterTab TableName Type IndexID TempSpaceID 0x00002B6A7E8F1B28 7 4 n a n a n a ITEM Online 1 7 Table Reorg Stats Address TableName Start End PhaseStart MaxPhase Phase CurCount MaxCount Status Completion 0x00002B6A7E8F1B28 ITEM 02 13 2008 14 35 11 02 13 2008 14 36 34 n a n a n a 1850 1850 Done 0 5 Use REORGCHK with the UPDATE STATISTICS option to obtain the new statistics after the index and table reorganization Example 6 44 Example 6 44 Using REORGCHK to update statistics after the table reorganization db2inst1 mensa g
141. 1 on page 364 expand the object tree until the desired object is shown then select the object and click OK Here we choose the DMS table space which we created earlier in Step 1 of this example Chapter 7 Monitoring and troubleshooting DB2 363 a Select a database object x j Instances s SS dbzinst1 Databases S ITS0DB E Table Spaces H A SYSCATSPACE ELA TEMPSPACEL E USERSPACE1 EL IBMDB2SAMPLEREL E TSDATAL HG SYSTOOLSPACE SYSTOOLSTMPSPAC HLA TSDATA2 2 TES H 2 ITSOREPL OK Cancel _ Help Figure 7 11 Select a database object d When the object is chosen you can modify the health indicator settings for the database objects Figure 7 12 on page 365 shows the default global setting from the table space level In our example a threshold value of 80 is set for a warning Likewise another threshold value 90 is set for alarm Both default values are expressed as a percentage 364 Up and Running with DB2 on Linux Object Health Indicator Configuration db2inst 1TSODB TBSPDMS 0 db2instl ITSODB TBSPDMS_0 Y Table Space Storage Automatic Resize Table Sp Yes Table Space Automatic Resi Yes Table Space Operational St Yes Table Space Utilization Figure 7 12 Health indicator settings in our sample e To configure a health indicator double click the health indicator that you want to change For example you can double click the health indicator for
142. 1m0 index jsp gt For general information about the Eclipse platform http www eclipse org 5 2 Installation This section provides the procedures to install IBM Data Studio There are three methods by which you can install IBM Data Studio on Linux gt Installing from the Launchpad program gt Using the IBM Installation Manager graphical interface gt Installing silently that is response file installation 5 2 1 Installing IBM Data Studio 200 You can download IBM Data Studio at no charge from http www ibm com software data studio In this section we show you how to install IBM Data Studio from an electronic image For installing Data Studio from other media refer to the Data Studio installation Guide Up and Running with DB2 on Linux The installation steps are 1 J5 IBM Data Studio Version 1 1 1 Mozilla Firefox Review the Preinstallation tasks in the IBM Data Studio Installation Guide to make sure that the installation requirements are met Unzip the Data Studio zip file unzip ibm_data_studio_v111_linux zip Run the setup executable provided setup Data Studio uses IBM Installation Manager to install the product If you have not installed the IBM Installation Manager yet the setup program will install the IBM Installation Manager for you Figure 5 2 shows the first panel presented You can browse the nstallation Guide and Release notes Select Install IBM Data Studio to install th
143. 2 Root installation Set up notifications 17 On the Specify a contact for Health Monitor notification window Figure 2 13 on page 73 you can add an Administration contact for this instance and then click Next By default a Health Monitor runs on the DB2 instance that you are setting up The DB2 Health Monitor will send a notification e mail to this person at the specified e mail address when a health indicator threshold is reached If you check E mail address is for a pager device the notification message will be sent to the contact s pager Note If you choose Defer this task until after installation is complete you can specify contacts after installation using the Task Center 72 Up and Running with DB2 on Linux db2inst1 itsosj sanjose iom com Figure 2 13 Root Installation Specify a contact for Health Monitor notification 18 The Start copying files and create response file window provides a summary of your installation and configuration settings as shown in Figure 2 14 Scroll through this window to verify that your settings are correct and then click Finish GID 1002 Home directory db2home db2tenci DB2 Administration server Instance user information User name dasusri UID Group name GID Home directory SMTP server Contact specification New contacts Name Instance E mail address E mail address is for a pager Response file name 997 dasadm1 1003 fhome dasusr1 smtp it
144. 2 Setup wizard to install DB2 on the primary machine When the environment is ready use the DB2 Setup wizard to install DB2 on the primary machine In our sample mensa is the primary machine of the partitioned database environment To install DB2 1 2 On the primary machine log in as root Go to the directory where the DB2 install image is located and run db2setup and select Install a Product on the first window Select Install New on the Welcome to the DB2 Setup wizard window and click Next On the Software License Agreement window read the license agreement then select Accept and click Next On the Select the installation type window you can choose a Typical Compact or Custom installation Typical installs most DB2 components except for the Base application development tools Click View Features to see what components will get installed Compact installs only the basic DB2 features and functionality Custom allows you to install whatever components that you want An advantage of the Custom option is that it allows you to install the Base application development tools with DB2 With the Typical option the Base application development tools require a separate installation On the Select installation response file creation or both window Figure 2 15 select Install DB2 Workgroup Server Edition Version 9 5 on this computer and save my settings in a response file We renam
145. 206173239 redirect generate script itsodb_node0001 clp DB20000I The RESTORE DATABASE command completed successfully gemini db2 restore db itsodb completed ok db2inst1 mensa db2home db2inst1 gt 1s clp itsodb_node0000 clp itsodb_node0001 clp Now we need to modify the two generated scripts one for each database partition In our case we change the table space container path and the size for TSDATA Example 6 25 on page 267 shows a part of the script which is related to table space TSDATA on database partition 0 with the changes that we make 266 Up and Running with DB2 on Linux Example 6 25 Part of the changed redirected restore script Tablespace name TSDATA1 Tablespace ID 4 Tablespace Type Database managed space Tablespace Content Type All permanent data Large table space Tablespace Page size bytes 8192 Tablespace Extent size pages 32 Using automatic storage No Auto resize enabled No Total number of pages 5120 Number of usable pages 5088 High water mark pages 96 kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk SET TABLESPACE CONTAINERS FOR 4 IGNORE ROLLFORWARD CONTAINER OPERATIONS USING FILE tablespaces db2inst1 itsodb NODE0000 TSDATA1 000 5120 FILE tablespaces ITS00000 TSDATA1 000 4000 After we change both scripts we create the new container directory on e
146. 2inst1 mensa gt db2_all db2 restore db itsodb tablespace tsdatal online from db2backup taken at 20080207090432 DB20000I The RESTORE DATABASE command completed successfully mensa db2 restore db itsodb completed ok DB20000I The RESTORE DATABASE command completed successfully gemini db2 restore db itsodb completed ok 2 Create a directory in a shared file system that is available for all database partitions or create the same directory on every physical database partition We need the directory for DB2 to export the data of the dropped table There needs to be sufficient space available in that file system for the exported table data db2_all mkdir db2backup rest_table 270 Up and Running with DB2 on Linux 3 Determine the backup ID by looking in the history file Example 6 30 Ina multi partitioned environment you look in the history file on the catalog partition Example 6 30 List history for dropped table db2inst1l mensa gt db2 list history dropped table all for itsodb List History File for itsodb Number of matching file entries 1 Op Obj Timestampt Sequence Type Dev Earliest Log Current Log Backup ID D T 20080207095643 000000000000350800040004 DB2INST1 TAB1 resides in 1 tablespace s 00001 TSDATA1 Comment DROP TABLE Start Time 20080207095643 End Time 20080207095643 Status A DDL CREATE TABLE DB2INST1 TAB1 ID INTEGER NOT NULL NAME CHAR 10 DISTRIBUTE BY HASH I
147. 384 0K 0 640 0K 18 8M apph 68339 apph 5231 apph 5230 apph 5229 apph 5227 appshrh 64 0K 64 0K 64 0K 64 0K 64 0K 128 0K db2inst1 mensa db2home db2inst1 gt db2 alter bufferpool ibmdefaultbp immediate size 10000 db2inst1 mensa db2home db2inst1 gt db2mtrk d Tracking Memory on 2008 02 12 at 14 29 20 Memory for database ITSODB utilh pckcacheh other catcacheh bph 1 bph S32K 64 0K 384 0K 192 0K 192 0K 80 0M 832 0K bph S16K bph S8K bph S4K shsorth lockh dbh 576 0K 448 0K 384 0K 0 640 0K 18 8M apph 68339 apph 5231 apph 5230 apph 5229 apph 5227 appshrh 64 0K 64 0K 64 0K 64 0K 64 0K 128 0K Chapter 7 Monitoring and troubleshooting DB2 385 Notes gt Ina partitioned database environment this command can be invoked from any database partition that is defined in the db2nodes cfg file It returns information only for the current partition gt You might have noticed that more than one bph is shown in the example for only one database which is because except for the buffer pools that are created by users there are four small hidden buffer pools created by DB2 to ensure that an appropriate buffer pool is available in all circumstances gt With Version 9 5 the p option which lists private agent memory heaps of the db2mtrk command is deprecated and has been replaced with the a option which lists all application memory consumption For a detailed explanation about command parameter
148. 4 34 AM PST 2 28 08 11 34 58 AM PST Mailing goela PO The task DB2INST 1 Runstats Task with status Successful ran on the DB2 Administrative Server on mensa itsosj sanjose ibm com and completed with return code 0 The task started on mensa O 1 at 2008 02 28 11 34 34 0 and completed at 2008 02 28 11 34 58 0 The task lasted 24 seconds Figure 6 55 Show result panel The task completed successfully The command script and running output of the commands that are specified in the task are shown in Figure 6 56 on page 351 350 Up and Running with DB2 on Linux connect to itsodb Database Connection Information Database server DB2 LINUX8664 9 5 0 SQL authorization ID DB2INST1 Local database alias ITSODB runstats on table db2instl item DB20000I The RUNSTATS command completed successfully connect reset DB20000I The SQL command completed successfully connect to itsodb Figure 6 56 DB2 command output You can modify the task further in the Task Center For example you can change the schedule or disable the follow up actions The scheduling function is also available for many other DB2 wizards or GUI tools such as export import load runstats reorg backup and restore You can take advantage of these useful functions for task automation purposes in your environment Chapter 6 Administering databases 351 352 Up and Running with DB2 on Linux Monitoring and troubleshooting DB2 In this chapter we discuss
149. 423 Chapter 8 Application development 0000 ea 425 8 1 Application configuration 0 2 2 0 ee ee 426 8 2 DB2 application objects 1 2 0 0 eee 428 821 THQGSIS fakes te dee sk odie da dle ed Pew te a pdet A 428 8 2 2 User defined functions 0 0 c eee ee 429 8 2 3 Stored procedures 0 00 431 8 3 Programming languageS saaa aaaea 433 8 9 1 Perl mesapiai aiden aaah witb ae ai iaa Gove ei 434 8 92 PAP Zarai ay a a eer e A ea te a Se et 438 8 9 3 Cand CEE siei Te a a eee aa a D ane ney ated 441 vi Up and Running with DB2 on Linux BSA AVA iss peg ia fgets Mate esate Man a ocala at AAA vay tts Neda ohh gence 449 SA PULOXMEE rren ane lacs aac gavedieedes Boldidvbn ys Wierda way 455 8 4 1 Storage model 2 0 cee 455 8 4 2 Using XML data 0 0 ae 456 8 5 Application development tools 00 0 eee 462 8 5 1 Explain facliy Tea ee t e a a eee 463 8 5 2 Design Advisor os csere ren tesua eked eae 467 8 5 3 Application development with the Data Studio 470 Appendix A Issuing commands to multiple database partitions 493 db2alland raie yind uea E EARE A a EEEN debe 494 OD 29S 65 ld yoya e Sale n NE A ES ER E a ae RRA ERA 497 e 7 ore 1l ES E e AR E E EE SA E A E 497 Appendix B DB2 Tools Catalog creation a u nananana 499 DB2 Tools Catalog creation unana uaaa aa 500 Related publications 0 0 00 ae 507 IBM R
150. 5 0 0 s071001 LINUXAMD6495 Fix Pack 0 DATA 2 System Info 440 bytes System Linux mensa 6 2 x86_64 Chapter 7 Monitoring and troubleshooting DB2 399 CPU total 2 online 2 Cores per socket 2 Threading degree per core 1 Physical Memory MB total 3753 free 263 Virtual Memory MB total 11951 free 8455 Swap Memory MB total 8198 free 8192 Kernel Params msgMaxMessageSize 65536 msgMsgMap 65536 msgMaxQueueIDs 1024 msgNumber0OfHeaders 65536 msgMaxQueueSi ze 65536 msgMaxSegmentSize 16 shmMax 9223372036854775807 shmMin 1 shmIDs 4096 shmSegments 4096 semMap 256000 semIDs 1024 semNum 256000 semUndo 256000 semNumPerID 250 sem0ps 32 semUndoSize 20 semMaxVal 32767 semAdjustOnExit 32767 Information in this record is only valid at the time when this file was created see this record s time stamp Every time that you use db2set to set or remove DB2 profile variables DB2 records a message in the db2diag log when DIAGLEVEL is 1 or higher As shown in Example 7 16 you will see a message after executing the following command db2set DB2COMM TCPIP Consider using this method to check when you doubt that the DB2 engine can write the db2diag log Example 7 16 Message about setting DB2 profile variables 2008 02 14 10 18 46 710519 480 11285E292 LEVEL Event PID 32098 TID 47944161495904PROC db2set INSTANCE db2inst1 NODE 000 FUNCTION DB2 UDB oper system services db2set_main probe 40 CHANGE CFG DB2SET DB2COMM From
151. 863 gt Quick Beginnings for DB2 Servers GC23 5864 gt Spatial Extender and Geodetic Data Management Feature User s Guide and Reference SC23 8508 gt SQL Reference Volume 1 SC23 5861 gt SQL Reference Volume 2 SC23 5862 gt System Monitor Guide and Reference SC23 5865 gt Troubleshooting Guide Gl11 7857 gt Tuning Database Performance SC23 5867 gt Visual Explain Tutorial SC23 5868 gt Workload Manager Guide and Reference SC23 5870 gt pureXML Guide SC23 5871 gt XQuery Reference SC23 5872 Online resources These Web sites and URLs are also relevant as further information sources 508 Up and Running with DB2 on Linux DB2 DB2 Information Center http publib boulder ibm com infocenter db21uw v9r5 Database and Information Management home page http www ibm com software data DB2 Technical Support http www ibm com software data db2 support db2_9 DB2 Product Family Library http www ibm com software data db2 library DB2 developerWorks http www ibm com developerworks db2 DB2 for Linux http www ibm com software data db2 1inux http www ibm com software data db2 1inux validate DB2 Universal Database V9 Application Development http www ibm com software data db2 ad Planet DB2 http www planetdb2 com Linux gt IBM Software for Linux http www ibm com software os 1inux software Other gt SAP Standard Application Benchmarks http www sap com s
152. A query is used in applications or by users to retrieve data from a database The query uses SQL to create a statement in the form of SELECT lt data_name gt FROM lt table_name gt Buffer pools A buffer pool is the amount of main memory allocated to cache table and index data pages as they are read from disk or as they are modified The purpose of the buffer pool is to improve system performance Data can be accessed much faster from memory than from disk therefore the fewer times that the database manager needs to read from or write to a disk I O the better the performance You can create more than one buffer pool although for most situations only one buffer pool is sufficient The configuration of the buffer pool is the single most important tuning area because you can reduce the delay that is caused by slow I O 1 4 Parallelism with DB2 16 A system with a single processor and disk has limitations for the amount of data users and applications that it can handle Parallel processing which is key for enterprise workloads involves spreading the load across several processors and disks and therefore allows for large volumes of data and high transaction rates Up and Running with DB2 on Linux to be processed In many environments the data volumes are growing at a phenomenal rate therefore a database management system needs to be able to easily scale to increased loads with the addition of more disks and CPUs DB2 para
153. AINT AUTO_TBL_MAINT AUTO_RUNSTATS for automatic statistics collection AUTO_REORG for automatic reorganization v Yv y Follow these steps to use the Configure Automatic Maintenance wizard 1 Open the wizard from the Control Center by right clicking a database object as shown in Figure 6 15 on page 276 Chapter 6 Administering databases 275 276 Systems Databases Figure 6 15 Select Configure Automatic Maintenance wizard 2 Select Configure Automatic Maintenance from the pop up panel You can also open the wizard from the detail panel of the Control Center To do so expand the All databases tree in the Control Center and select the database The detail panel is on the lower right side of the Control Center Connect to the database from the detail panel and you will see more details about the database Refer to Figure 6 16 O Database ITSODB Alias name ITSODB System MENSA Type Local Actions Application List f Design Advisor Activity Monitor B Query qh Create New Database Status as of DBM State Last Backup Size Capacity Health Maintenance 2 19 08 4 24 PM a Refresh Started fb Stop 2 18 08 3 50 PM 4 Backup Database 374 MB View Storage Unavailable i Unavailable Monitor DB Health Partially automated Maintenance N Figure 6 16 Database detail panel of the Control Center 3 Select Maintenance to start the wizard The wizard opens wit
154. AL_NODES 4 Fenced user inst1 FENCED_USERNAME db2fencl inst1 FENCED_UID 998 instl FENCED GID 1002 inst1 FENCED_GROUP_NAME db2fadml inst1 FENCED_HOME_DIRECTORY db2home db2fencl inst1 FENCED_PASSWORD z 7234413608936355365120643490665128227774547854466545365132477194452032722963741 33305018 ENCRYPTED inst1 FENCED_PASSWORD Contact properties CONTACT contactl contact1 CONTACT_NAME db2instl contact1 EMAIL db2instl itsosj sanjose ibm com contact1 PAGER false contact1 NEW_CONTACT YES contact1 INSTANCE instl Installed Languages Chapter 2 Installation 75 76 INSTALL_TSAMP YES Installing DB2 using the response file To install DB2 using the response file use the db2setup command with the r option For example db2setup r db2home db2inst1 db2ese rsp db2_ install utility For root installation the db2_insta11 utility installs the DB2 filesets but it does not create an instance or users or perform any other configuration tasks that are performed by the DB2 Setup wizard Many people prefer to use db2_instal1 when installing DB2 on a large complex database system that has special requirements Installing DB2 To install DB2 1 Log in as root 2 Change to the directory where the DB2 product DVD is mounted by entering the following command cd mnt dvd In this command mnt dvd represents the mount point of the DVD 3 Enter the db2_install command to start the db2_install scr
155. Application Server Edition for unlimited deployment throughout an organization The license fees for DB2 Connect Unlimited Edition for zSeries are based on the size of the DB2 System z server measured in millions of service units MSUs and are not affected by either the number of processors available to the DB2 Connect servers or the number of processors available to application servers where the application is running DB2 Connect Unlimited Edition for iSeries has the same specification as DB2 Connect Unlimited Edition for zSeries except that the license fees for DB2 Connect Unlimited Edition for iSeries are based on the number of processors allocated to the data source running on i5 OS or OS 400 operating systems Unlimited users are permitted DB2 for pervasive platforms The last but not the least DB2 offering is DB2 Everyplace DB2 Everyplace is a relational database and enterprise synchronization server that enables enterprise applications and enterprise data to be extended to mobile devices such as personal digital assistants PDAs and smart phones DB2 Everyplace can also be embedded in devices and appliances to increase their functionality and market appeal The product can be used as a local independent database on a mobile device or to query information on remote servers when a connection is available Up and Running with DB2 on Linux 1 3 DB2 environment This section describes the various DB2 application configurati
156. B2 features and functionality will 390 to 470 MB be installed and minimal configuration will be performed Custom This option allows you to select the 390 to 680 MB features that you want to install and to specify your configuration preferences Table 2 4 Required disk space root installation Typical The typical setup includes basic 630 to 760 MB database server function database administration tools and most product features and functionality Compact Basic DB2 features and functionality will 580 to 700 MB be installed and minimal configuration will be performed Custom This option allows you to select the 580 to 1020 MB features that you want to install and to specify your configuration preferences You must also allocate disk space for required software communication products DB2 documentation and databases In DB2 Version 9 5 DB2 Information Center and PDF documentation are now provided on separate DVDs Installing DB2 Information Center in English requires 131 MB of disk space Additional space is required for additional languages We recommend that you allocate two GB of free space in the tmp directory 2 1 4 Memory requirements We recommend that you allocate a minimum 256 MB of RAM for DB2 anda minimum of 512 MB of RAM for a system running just a DB2 product and the DB2 GUI tools Additional memory must be allocated for other software and communication products 28 Up and Running with DB2 on Linux Wh
157. C SQLFreeHandle SQL_HANDLE_ENV henv SQL SUCCESS fprintf stderr CLI error d in SQLFreeHandle n cliRC exit cliRC Example 8 10 shows the commands to build and run the program Example 8 10 Running the CLI program db2inst1l puget db2inst1l puget db2inst1l puget db2inst1l puget 000290 000310 200310 200330 200340 export LD_LIBRARY_PATH home db2inst1 sqllib lib cc c I home db2inst1 sqllib include cli_test c cc o cli_test L home db2inst1 sqllib lib 1db2 cli_test o cli_test vvvVvV Chapter 8 Application development 443 Note You can read a detailed introduction to the CLI functions in the Information Center by selecting Database application development gt Database Applications gt CLI You can obtain detailed reference information by selecting Reference gt APIs CLI The available manuals are Call Level Interface Guide and Reference Volume 1 SC23 5844 and Call Level Interface Guide and Reference Volume 2 SC23 5845 Embedded SQL Embedded SQL allows you to put SQL statements directly into the C C code You can embed them into the code Embedding SQL requires a precompilation step of the program before the program can be compiled with the native C C compiler The precompile step produces a bind file package and a program source file The package has the suffix bnd The program file can then further be compiled by the C C compiler The package contains the access
158. CATSPACE 00002 USERSPACE1 Comment DB2 BACKUP ITSODB OFFLINE Start Time 20080201170437 End Time 20080201170449 Status A EID 1 Location db2backup You can also retrieve the history entries for ROLLFORWARD REORG CREATE TABLESPACE ALTER TABLESPACE DROPPED TABLE LOAD RENAME TABLESPACE and ARCHIVE LOG To see the archived log files you have to use the command shown in Example 6 3 on page 237 Up and Running with DB2 on Linux Example 6 3 Archive log history db2instl mensa gt db2 list history archive log all for db itsodb Op Obj Timestamp Sequence Type Dev Earliest Log Current Log Backup ID Comment Start Time 20080207090530 End Time 20080207090543 Status A EID 25 Location db2archive db2inst1 ITSODB NODE0000 C0000001 S0000005 L0G In a multi partitioned database environment you have to run the list history command on each database partition You can use the DB_HISTORY administrative view or SYSPROC ADMIN_LIST_HIST function to get the information from the history file in all database partitions Sample commands are db2 select from sysibmadm DB_HISTORY db2 select from table SYSPROC ADMIN LIST _HIST Over time the recovery history file will increase in size So when an entry is no longer relevant because the associated recovery objects are no longer needed to recover the database you might want to remove or prune those entries from the recovery history file You can remove those entries by usin
159. Certain Linux kernels do not allow you to set the value of the DATABASE_MEMORY database parameter to AUTOMATIC The AUTOMATIC value is supported on RHEL5 and on SUSE 10 SP1 and newer All other validated Linux distributions will return to COMPUTED if the kernel does not support this feature Chapter 3 Post installation tasks 135 3 6 2 Database manager configuration parameters 136 The database manager configuration DBM cfg parameters are stored in a file named db2systm in INSTHOME sqllib To modify these parameters use the graphical interface Control Center or DB2 command line interface Important DBM cfg parameters Here are the important DBM cfg parameters gt DFTDBPATH By default this parameter is set to INSTHOME We recommend that you set it to your desired path INSTHOME is typically on an NFS file system in a partitioned environment but DB2 does not support NFS for the database path DFT_MONSWITCHES Set all monitor switches to ON to let DB2 gather statistical data Use the get snapshot command to show details about the behavior of DB2 DIAGLEVEL For problem determination set DIAGLEVEL to 4 DB2 will write all errors warnings and informational messages to the db2diag log into the path defined by DIAGPATH The default is 3 Note that log level 4 can have severe performance impacts MON_HEAP_SZ which can be set to AUTOMATIC The memory required for maintaining the private views of the database system
160. Connection identification Use default naming convention Connection Name SAMPLE Ei a JDBC driver IBM Data Server Driver for JDBC and SOLJ X YV DB2for Linux UNIX and Windows Connection URL details DB2 for iOS Datei SAMPLE DB2 for z OS P Derby sai localhost Informix Port number joo O Use client authentication JDBC driver class com ibm dbe joc DB2Driver Class location opt IBM SDP70Shared plugins com ibm data b b b b Connection URL jdbe db2 localhost 50000 E a SAMPLE retrieveMessagesFromServerOnGetMessage true z User information User ID fateinstt X Figure 8 14 Create the connection panel in the Data Studio 4 Then click Next At the schema selection panel you can specify which schemas are displayed in the Database Explorer We accept the default Figure 8 15 on page 476 Chapter 8 Application development 475 476 j 7 O 2 New Data Development Project a Specify Schema Filter Specify a filter by selecting a predicate and entering a value or by indicating whether to include or exclude a selection of items Expression Name Does not start with the characters v sys C Selection _ Disable filter Finish Figure 8 15 Schema selection panel 5 Now click Finish to create the connection and the project The newly created project DataProject is presented in the Data Pr
161. D Data Parti Table Spa joper ral ion F Figure 5 23 Add tables to a diagram Select Add to Overview Diagram Enter OverviewDiagram as the diagram name You get an ER diagram for the two tables Figure 5 24 E EMPLOYEE 5 EMPNO FIRSTNME E MIDINIT E LASTNAME amp WORKDEPT FK PHONENO HIREDATE Jos EDLEVEL B sex BIRTHDATE E SALARY BONUS comm fh EMP_RESUME EMPNO FK 5 RESUME_FORMAT RESUME Figure 5 24 ER diagram of the EMPLOYEE and the EMP_RESUME tables 5 3 5 Data and object management You can manage the data of your tables directly from the workbench of the Data Studio In order to do that open the tree Connections SAMPLE gt SAMPLE Schemas gt DB2INST1 Tables EMPLOYEE Right click the table and select Data Edit You get an editor panel that allows you to manipulate the data Figure 5 25 on page 222 Chapter 5 IBM Data Studio 221 BE Outline x An outline is not available CHRISTINE HAAS MICHAEL THOMPSON SALLY1 KWAN JOHN GEYER IRVING STERN EVA PULASKI EILEEN HENDERSON Properties Tasks Problems Error Log ode Report Gs Data Output xd Bookmarks Servers Status Action Object Name DB2INST1 EMPLOYEE Messages Parameters Results Profiling Data update DB2INST1 EMPLOYEE set FIRSTNME SALLY1 where EMPNO CAST 000000 AS CHAR 6 j Data successfully sav
162. D IN TSDATA1 4 Roll forward the database with the correct table ID The table ID is listed in the backup ID column Example 6 31 Example 6 31 Roll forward with the table ID db2 rollforward db itsodb to end of logs on all dbpartitionnums and complete tablespace tsdatal online recover dropped table 000000000000350800040004 to db2backup rest_table Rollforward Status Input database alias itsodb Number of nodes have returned status 2 Node number Roll forward Next log Log files processed Last committed transaction status to be read Chapter 6 Administering databases 271 272 0 not pending 2008 02 07 01 32 41 000000 UTC 1 not pending 2008 02 07 01 36 12 000000 UTC DB20000I1 The ROLLFORWARD command completed successfully 5 Upon finishing the roll forward DB2 restores the table data to the export directory in the subdirectory NODEnnnn in a file called data Now get DDL from the history file to create the table and load all of the data from the export file into the table The CREATE TABLE DDL was put into the recovery history file during the DROP TABLE command as seen in Example 6 30 on page 271 The commands that we need to run now to recover the table are shown in Example 6 32 Example 6 32 Recreate the table and Import the data db2inst1 mensa gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias
163. D Start Time State Invocation Type Progress Monitoring Phase Number Description 136 LOAD ITSODB 0 OFFLINE LOAD DEL AUTOMATIC INDEXING REPLACE 02 11 2008 15 57 02 886822 Executing User 1 SETUP 0 bytes 0 bytes 02 11 2008 15 57 02 886827 2 LOAD 1552469 rows 643221 rows 02 11 2008 15 57 04 189448 3 BUILD 1 indexes 0 indexes Not Started 88 LOAD ITSODB 1 OFFLINE LOAD DEL AUTOMATIC INDEXING REPLACE 02 11 2008 16 00 40 095780 Executing User SETUP Chapter 6 Administering databases 323 Total Work Completed Work 0 bytes 0 bytes Start Time 02 11 2008 16 00 40 095786 Phase Number Current 2 Description LOAD Total Work 1552469 rows Completed Work 174190 rows Start Time 02 11 2008 16 00 41 415394 Phase Number 3 Description BUILD Total Work 1 indexes Completed Work 0 indexes Start Time Not Started Using the SHOW DETAIL clause you get information about the LOAD phases and their progress Each LOAD writes an entry into the database recovery history file If you want to see the processed LOAD commands use the command shown in Example 6 59 The output shows the entries for a LOAD operation that we did in Example 6 53 on page 315 Note the two entries one for the LOAD 0p L and one for the COPY YES 0p C Example 6 59 List history for LOAD operation db2instl mensa gt db2 list history load all for itsodb Op Obj Timestampt Sequence Type Dev
164. ER Figure 8 26 Parameter panel 5 In the Deploy Options panel Figure 8 27 enter EMPSALARY in the Specific name field and check Enable debugging Click Next g a 2 New Stored Procedure Deploy Options Specify additional options for deploying and debugging the stored procedure JAR ID EMPSALARY Specific name MPSALAR Current schema DB2INST1 Enable debugging o coon mes cont _ Figure 8 27 Deploy options for the new stored procedure 6 In the Code Fragments panel Figure 8 28 on page 484 you can enter additional files with code fragments which are to be included in the procedure In our example we do not have an additional file to add Click Next Chapter 8 Application development 483 m 23 New Stored Procedure Code Fragments Specify files containing code fragments Header fragment Imports fragment Data fragment a E m Method fragment public class EMPSALARY public static void eMPSALARY int SALARY ResultSet rs1 throws SQLException Exception ii Get connection to the database Connection con DriverManager getConnection jdbe default connection co meee em com Figure 8 28 Code Fragments panel 7 Inthe Summary panel Figure 8 29 click Finish 3 New Stored Procedure Summary The stored procedure settings that you specified are summarized here Template option Resu
165. Every database partition writes their messages into the same file You can filter the output To display only logged records for database partition 2 db2diag n 002 To display all of the logged records that contain only errors for database partitions 0 and 2 db2diag node 0 2 1 Error warning Archive the db2diag log file If you want to archive the current db2diag log file and start a new log file enter db2inst1 mensa db2home db2inst1 gt db2diag A db2diag Moving db2home db2inst1 sq11ib db2dump db2diag 1log to db2home db2inst1 sql1lib db2dump db2diag 1log_2008 02 14 16 36 57 Format the db2diag output The following command formats the output of db2diag to only show the timestamp database partition number the message level and the message text db2diag fmt Time ts Partition node Message Level level n Message msg n DB2 internal error return codes To get the description about a DB2 internal error code 0x860FOO0A db2diag rc 0x860FO00A Chapter 7 Monitoring and troubleshooting DB2 403 404 To display a list of all of the DB2 ZRC return codes that are available enter db2diag rc zrc You can combine these options There are many more options available Use the command db2diag h to see all of the options of db2diag The output is shown in Example 7 18 To display more details and examples use the command db2diag h tutorial Example 7 18 Output of db2diag help db2inst1 men
166. Example 3 17 on page 116 lists the table space in node gemini The catalog table space exists only on mensa which is the catalog node Chapter 3 Post installation tasks 115 116 Example 3 17 List table spaces on gemini db2instl gemini gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2instl gemini gt db2 list tablespaces Tablespaces for Current Database Tablespace ID 1 Name TEMPSPACE1 Type System managed space Contents System Temporary data State 0x0000 Detailed explanation Normal Tablespace ID 2 Name USERSPACE1 Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Norma DB210111 In a partitioned database server environment only the table spaces on the current node are listed Create table spaces and tables The next step is to create tables for your application When a database is created DB2 creates three default table spaces The USERSPACE1 is used to place the data tables Based on the database design more table spaces can be created The tables usually will be placed in a particular table space based on the application and the database design It is common to create your own table spaces that are spread across all partitions or only a few of them Every table space has to be created in a database partition group Here
167. Example 3 8 db2nodes cfg file 0 mensa 0 1 gemini 0 To enable communications between the database partition servers that participate in your partitioned database system you have to reserve TCP IP ports in etc services for the Fast Communication Manager FCM If you install DB2 with the db2setup wizard a port range is automatically reserved on the primary instance owning computer Log on to each participating computer as root user and add the identical entries into etc services Example 3 9 shows four ports reserved for four local partitions on this host Example 3 9 Ports in etc services DB2_db2inst1 60000 tcp DB2_db2inst1_1 60001 tcp DB2_db2inst1_2 60002 tcp DB2_db2inst1_END 60003 tcp Now you are able to start DB2 in a multiple host multi partitioned environment To start DB2 in a multiple host multi partitioned environment enter the db2start command on any host Refer to Example 3 10 Example 3 10 Start of a DB2 instance with four partitions db2start 02 14 2008 16 30 20 O 0 SQL1063N DB2START processing was successful 02 14 2008 16 30 21 1 0 SQL1063N DB2START processing was successful SQL1063N DB2START processing was successful If you encounter any errors at startup you can check the db2diag log files in each instance of the cluster for more detailed information Up and Running with DB2 on Linux 3 3 Creating a database Now we show the creation of a database We are going to demonstrate two cases g
168. Example 8 1 on page 428 To get the detailed information from the EMPLOYEE table with history data stored in EMPLOYEE_HIST we can join EMPLOYEE and EMPLOYEE _HIST to calculate the column salary_diff or we can use an UDF to perform the function Example 8 3 UDF to calculate a salary difference from the audit table CONNECT TO sample CREATE FUNCTION salary_diff emp CHAR 6 RETURNS DECIMAL 9 2 LANGUAGE SQL READS SQL DATA NO EXTERNAL ACTION DETERMINISTIC RETURN SELECT salary_new salary_old AS salary_diff FROM employee_hist h employee o WHERE h empno emp AND h empno o empno AND h chg_date SELECT MAX chg_date FROM employee_hist WHERE empno h empno Note The statement SELECT MAX chg_date is required because for each empno there can exist more than one row in EMPLOYEE_HIST table However a UDF can return only one row In Example 8 4 on page 431 we can use the newly created function salary_diff in our query 430 Up and Running with DB2 on Linux Example 8 4 Use the UDF in a select statement db2inst1 puget gt db2 select empno firstnme lastname salary_diff empno as salary_diff from employee where empno in 000110 000070 EMPNO FIRSTNME LASTNAME SALARY_DIFF 000110 VINCENZO LUCCHESSI 25000 00 000070 EVA PULASKI 10000 00 2 record s selected Note You can obtain more information about UDFs in Developing User defined Routines SQL and External SC23 5855 8 2 3 Stored procedures A stor
169. Figure 7 30 on page 389 shows a sample buffer pool information window By default db2top issues global snapshots If you want to monitor a specific partition you can press the p key and then specify which partition you want to monitor Note that this capability applies to all of the monitoring not just monitoring the buffer pool utilization Up and Running with DB2 on Linux Figure 7 30 Monitoring buffer pool panel Monitoring dynamic SQL To monitor dynamic SQL press the d key In this panel Figure 7 31 on page 390 you can view the number of times that an SQL statement has been executed Num Execution the average execution time and the average CPU time for an SQL statement Chapter 7 Monitoring and troubleshooting DB2 389 jis Figure 7 31 Monitoring dynamic SQL window 390 Enter SOL refresh 2s t OL Linux part 2 2 eee ee ees N PALL Ip hash strin ag 7 7 7 To check the SQL statement in the Monitoring dynamic SQL panel obtain the hash value of the query from the first column press the I L key and input the hash value The SQL statement will be displayed as shown in Figure 7 32 on page 391 You can press the e key to get db2exp1n utility output or press the x key to get db2exfmt utility output to analyze a dynamic SQL execution plan In certain cases explain will fail if an object referenced by the query is not in the default schema In this case you can us
170. HAIN In our case we see the archived log files for the partitioned database under db2archive db2inst1 ITSODB NODE0000 C0000000 rw r 1 db2inst1 db2grp1 12288 2008 02 01 17 38 S0000000 L0G db2archive db2inst1 ITSODB NODE0001 C0000000 rw r 1 db2inst1 db2grp1 12288 2008 02 01 17 38 S0000000 L0G The database is now enabled to take database backups in online mode as well as to back up individual table spaces More parameters for log file management With the setup that we performed the log files were archived automatically by the DB2 log manager db2logmgr to another file system called db2archive Depending to your company s needs about log archiving you might consider setting other database configuration parameters For log archiving check the following parameters gt LOGARCHMETH2 This parameter specifies a second location or method to archive the log files This parameter can be set similar to LOGARCHMETH1 but it points to a different location such as another file system or Tivoli Storage Manager If both LOGARCHMETH1 and LOGARCHMETH2 are specified each log file is archived twice which means that you will have two copies of archived log files in two different locations Up and Running with DB2 on Linux gt ARCHRETRYDELAY NUMARCHRETRY and FAILARCHPATH The specified log archive method might fail such as the archive file system might be full or the Tivoli Server Manager server might not be available
171. HMETH2 database configuration parameters to a value other than OFF Active logs are still available for crash recovery but you also have the archived logs which contain committed transaction data After a successful restore you can roll the database forward that is past the time when the backup image was Up and Running with DB2 on Linux taken by using the active and archived logs to either a specific point in time or to the end of the active logs DB2 provides multiple backup mechanisms You need to decide between the following backup mechanisms Offline or online backup During an offline backup applications cannot connect to the database This is the default backup method when you do not specify any parameter in the BACKUP command After an offline backup you have a consistent image copy of the entire database Recoverable database backup operations can also be performed online Online mean that other applications can connect to the database during the backup operation During an online backup operation rollforward recovery ensures that all table changes are captured and reapplied if that backup is restored If you have a recoverable database you can back up restore and roll individual table spaces forward rather than the entire database When you back up a table space online it is still available for use and simultaneous updates are recorded in the logs When you perform an online restore or a roll forward operation on a table
172. ID is defined during the creation of the instance Authorities DB2 instance level authorities SYSADM SYSCTRL SYSMAINT and SYSMON are granted through operating system group Each DB2 instance level authority provides a certain level of access and permissions to the databases of the instance In the database manager configuration you can define which Linux groups are assigned to which authorities The authorized groups are specified in the database manager configuration as shown in Example 3 38 Example 3 38 Instance level authorities db2instl puget gt db2 get dbm config grep _GROUP SYSADM group name SYSADM GROUP DB2IADM1 SYSCTRL group name SYSCTRL_GROUP SYSMAINT group name SYSMAINT_ GROUP SYSMON group name SYSMON_GROUP Security on the network level If networking is enabled the database manager opens a TCP IP port which is used by DB2 clients to communicate with the server Firewalls must be opened for that port and you can use proxies such as SOCKS Version 4 By default all of the communication between the database server and the client is not encrypted If you need to protect the data transfer you can enable Secure Sockets Layer SSL support or you can configure the server for SERVER_ENCRYPT or DATA_ENCRYPT authentication The authentication type is defined in the database manager configuration as shown in Example 3 39 on page 151 Up and Running with DB2 on Linux Example 3 39 Authentication parame
173. ITSODB TEMPSPACE2 ON DBPARTITIONNUM 0 USING db2temp db2inst1 NODE0001 ITSODB TEMPSPACE2 ON DBPARTITIONNUM 1 EXTENTSIZE 8 PREFETCHSIZE 32 BUFFERPOOL ibmdefaul tbp DROP TABLESPACE tempspacel Chapter 2 Installation 45 2 2 4 Lab environment In this book we use the following systems to demonstrate DB2 installation configuration and management for the partitioned database environment gt Mensa Host name mensa Domain itsosj sanjose ibm com Host IP address 9 43 86 90 Linux distribution SUSE SLES 10 SP1 x86_64 Partitioned database setup e The partitioned instance has one logical partition node 0 initially on this physical node that is the coordinate node of the partitioned database environment We add more logical partitions later e The partitioned instance s home directory db2home is exported from this machine gt Gemini Host name gemini Domain itsosj sanjose ibm com Host IP Address 9 43 86 94 Linux Distribution SUSE SLES 10 SP1 x86_64 Partitioned database setup The partitioned instance has one logical partition node 1 on this physical node We add more logical partitions later 2 2 5 Setting up NFS for a partitioned database environment installation 46 If you have a configuration that uses more than one machine for a single database instance you must configure communications before installing DB2 In this section we discuss how to set up ssh and Network File System
174. In this case DB2 will retry the archive after the time specified by the ARCHRETRYDELAY parameter NUMARCHRETRY specifies the number of attempts that will be made to archive the log files before they are archived to the path that is specified by the FAILARCHPATH configuration parameter FAILARCHPATH is a temporary storage area for the log files until the log archive method that failed becomes available again At which time the log files will be moved from this directory to the log archive method By moving the log files to this temporary location log directory full situations might be avoided This parameter must be a fully qualified existing directory The log files are critical for database recovery You need to manage the log files and the log space carefully Note To monitor the current log file usage for a running database use the GET SNAPSHOT command or the LOG_UTILIZATION administrative view db2 SELECT FROM SYSIBMADM LOG UTILIZATION The LOG_UTILIZATION view shows the percentage of total log space used the percentage of available log space and the used log space for each database partition Starting with DB2 9 5 DB2 maintains two copies of the log control file SQLOGCTL LFH 1 and SQLOGCTL LFH 2 Also you can configure DB2 to mirror the database log files by setting the following database parameter MIRRORLOGPATH DB2 provides the capability to mirror the active log files to prevent log data loss in the case of a disk crash W
175. Linux distributions supported by DB2 26 Make sure that your Linux distribution level is supported by DB2 For the latest information about currently supported Linux distributions kernels and libraries refer to the DB2 for Linux validation Web site http www ibm com software data db2 1inux validate Up and Running with DB2 on Linux The following Linux distributions shown in Table 2 1 and Table 2 2 have been successfully validated for use with DB2 Table 2 1 Recommended environments for DB2 9 5 Kernel architecture x86_64 PPC64 s390x POWER BEN z Red Hat Enterprise Linux RHEL 5 SUSE Linux Enterprise Server SLES 10 Table 2 2 Validated environments for DB2 9 5 Kernel architecture x86_64 PPC64 390x POWER System z FA a a a Red Hat Enterprise Linux RHEL 4 Hat Enterprise Linux RHEL 4 e a SUSE Linux Enterprise Server SLES 9 2 1 3 Required disk spaces You must take into account the following disk requirements while configuring your system The DB2 Setup wizard provides dynamic size estimates based on the components selected during a typical compact or custom installation as shown in Table 2 3 on page 28 and Table 2 4 on page 28 Chapter 2 Installation 27 Table 2 3 Required disk space non root installation Typical The typical setup includes basic 400 to 490 MB database server function database administration tools and most product features and functionality Compact Basic D
176. M SYSCATSPACE Triggers E SYSBUFFERPOOLN SYSIBM SYSCATSPACE Fo Schemas E SYSBUFFERPOOLS SYSIBM SYSCATSPACE Figure 3 11 Start the Create Table Wizard Those steps start the Create Table Wizard Figure 3 12 on page 119 The Create Table Wizard guides you through many panels where you can create a new table by using the predefined column definitions or by defining your own column definitions Up and Running with DB2 on Linux WEN Create Table Wizard _ Identify the schema and name for the new table This wizard helps you create a new table for storing data Type a name below to describe the data that you want to store in this table Click Next to continue Task Overview Dimensi Table schema DB2INST 1 o Gorateci Table name A Shirnissicie y omment Mert Fidzi Cancel Figure 3 12 Create Table Wizard in the Control Center Table partitioning and row compression DB2 offers numerous features and functions to support your enterprise databases We describe two table related features here for you to consider when designing your tables The table partitioning feature provides you with the capability to divide table data across multiple storage objects called data partitions or ranges according to values in one or more table partitioning key columns of the table With table partitioning you are able to roll in and roll out of the table data efficiently detach or reattach a data partition for
177. MPNO DB2 hashing alogrithm rn 000120 9 Partitioning Map Index ate Sf Partitions 1 2 3 4 i 2 af 4 ij As 4 Figure 1 9 Intelligent data distribution across DB2 partitions The data while physically split is used and managed as a logical whole Users can choose how to partition their data by declaring partitioning keys Tables can be located in one or more database partitions As a result you can spread the workload across a partitioned database for large tables while allowing smaller tables to be stored on one or more database partitions Each database partition has local indexes on the data that it stores resulting in increased performance for local data access You are not restricted to having all tables divided across all database partitions in the database DB2 supports partial declustering which means that you can divide tables and their table spaces across a subset of database partitions in the system An alternative to consider when you want tables to be positioned on each database partition is to use materialized query tables and then replicate those tables You can create a materialized query table containing the information that you need and then replicate it to each node Partitioning on SMP clusters In the most simplistic scenario each physical machine in the cluster has a single database partition on it In this type of a configuration each partition is a physical database parti
178. Max MsgMap MsgMni MsgTql MsgMnb MsgSsz n a 65536 65536 1024 65536 65536 16 Shared Memory Information ShmMax ShmMin ShmIds ShmSeg 9223372036854775807 1 4096 4096 Semaphore Information SemMap SemMni SemMns SemMnu SemMs 1 Sem0pm SemUme SemUsz SemVmx SemAem 256000 1024 256000 256000 250 32 n a 20 32767 32767 CPU Load Information Short Medium Long 0 160000 0 140000 0 080000 Up and Running with DB2 on Linux CPU Usage Information Total Usr Sys Wait Idle 0 080000 n a n a 0 920000 n a You can set a default option for db2pd using the DB2PDOPT environment variable In Example 7 20 we set the default to agents to get information about running agents Example 7 20 Setting default option for db2pd db2inst1 mensa db2home db2inst1 gt db2pd db2pd gt You are running db2pd in interactive mode db2pd gt If you want command line mode rerun db2pd with valid options db2pd gt Type h or help for help db2pd gt Type q to quit db2pd gt q db2inst1 mensa db2home db2inst1 gt export DB2PDOPT agents db2inst1 mensa db2home db2inst1 gt db2pd Database Partition 0 Active Up 0 days 23 49 40 Agents Current agents 6 Idle agents 0 Active coord agents 4 Active agents total 4 Pooled coord agents 2 Pooled agents total 2 Address AppHand1 nod index AgentEDUID Priority Type State ClientPid Userid ClientNm Rowsread Rowswrtn LkTm0t DBName 0x000000020023D600 1054 000 01054 527 0 Coord Inst Active 9045 db2instl
179. Monitoring and troubleshooting DB2 397 398 You can use the database manager parameter NOTIFYLEVEL to specify the type of administration notification messages that are written to the administration notification log Valid values for this parameter are 0 No administration notification messages are captured We do not recommend this setting 1 Fatal or unrecoverable errors Only fatal and unrecoverable errors are logged 2 Immediate action required Conditions are logged that require immediate attention from the system administrator or the database administrator This level will capture Health Monitor alarms 3 Important information no immediate action required Conditions are logged that are non threatening and do not require immediate action but might indicate a non optimal system This level will capture Health Monitor alarms Health Monitor warnings and Health Monitor attentions 4 Informational messages Messages which are written to the notify log because you set a higher level include the messages that are applicable to lower levels For example setting the notify level to 3 will cause the administration notification log to include messages applicable to levels 1 and 2 Example 7 14 is an excerpt of the messages from the notify log when lock escalation happens The messages in the log tell you when the lock escalation occurs in which instance database and partition it takes place the process ID and thread ID assoc
180. ND T TABLES BACK_GROUND m MEMORY wait echo Done Make the following modifications to db2top txt Combine the BACK_GROUND definition to one line Use perl pi e s g DIR db2top csv amp to translate the delimiter of CSV files from a semicolon to a comma Note This step is only required if your Excel setting uses a semicolon as the delimiter Usually this Excel setting is determined by the Windows regional settings Example 7 11 shows an modified script Example 7 11 db2top sh bin sh export WAITTIME 1 5 export DIR tmp background BACK_GROUND software db2top 1inux_amd_64 db2top m WAITTIME b 1 o DIR db2top 2 csv amp rm fR DIR mkdir p DIR echo Running db2top for WAITTIME minute s BACK_GROUND d DBM BACK_GROUND 1 APPL Chapter 7 Monitoring and troubleshooting DB2 393 BACK_GROUND t TBS BACK_GROUND b BP BACK_GROUND T TABLES BACK_GROUND m MEMORY wait perl pi e s g DIR db2top csv amp echo Done 2 Rename db2top txt to db2top sh and upload db2top sh to a working directory on Linux Execute db2top sh as db2set DB2DBDFT ITSODB sh db2top sh In the previous commands ITSODB represents the database that we monitor in our sample 3 Use FTP to transmit all CSV formatted files that were generated in tmp background to the working directory where db2top xls exists 4 Click Build graphics to produce the graphical reports f
181. NPIE Documentation Label Database type DB2 for Linux UNIX and Windows Database version v95 Figure 8 17 Create a query in Data Studio 3 The Query Builder view shows From Database Explorer expand the tree Connections gt SAMPLE gt SAMPLE Schemas gt DB2INST1 gt Tables and drag and drop the EMPLOYEE and DEPARTMENT tables into the middle pane of the Query Builder The tables appear as boxes with the column names You can move them around or resize them Create the join Right click the EMPLOYEE table in the Query Builder and select Create Join A window appears where you can select the source and the target of the join The source table is EMPLOYEE the source column is WORKDEPT the target table is DEPARTMENT and the target column is DEPTNO Figure 8 18 on page 478 shows the Create Join panel After clicking OK you can see a line between the tables in the middle pane Chapter 8 Application development 477 478 m 22 Create Join O 2 Source Table alias EMPLOYEE Sf Column WORKDEPT v Source column type CHAR Target Table alias DEPARTMENT Column PEPTNO v Target column type CHAR Join type Inner join Left outer join Bight outer join Eull outer join cot Figure 8 18 Create a join in the Query Builder 5 Select the columns for the query Just check EMPNO LASTNAME in the EMPLOYEE box and DEPTNO and DEPTNAME in the DEPARTMENT box in the middle
182. NT ON Automatic database backup AUTO_DB BACKUP OFF Automatic table maintenance AUTO_TBL_MAINT ON Automatic runstats AUTO_RUNSTATS ON Automatic statement statistics AUTO _STMT_STATS OFF Automatic statistics profiling AUTO_STATS_PROF OFF Automatic profile updates AUTO_PROF_UPD OFF Automatic reorganization AUTO_REORG OFF To configure automatic backup using the command line processor CLP you have to set AUTO_MAINT and AUTO_DB_BACKUP to ON 252 Up and Running with DB2 on Linux Configure automatic backup using AUTOMAINT_SET_POLICY DB2 provides a stored procedure AUTOMAINT_SET_POLICY to specify your automated maintenance policy for automatic backup also for AUTO_REORG and AUTO_RUNSTATS as well as to set the days and times for the online and offline maintenance windows Note The DB2 built in administrative routine administrative views provide an easy to use programmatic interface for performing a variety of DB2 administrative tasks These routines and views can be invoked from an SQL based application a DB2 command line or a command script To configure automatic backup using the AUTOMAINT_SET_POLICY system stored procedure you have to create an Extensible Markup Language XML configuration input specifying details such as backup media whether the backup will be online or offline and the frequency of the backup The AUTOMAINT_ SET POLICY stored procedure takes two input parameters gt Maintenance
183. Name Default Type Warning Alarm Unit Sensitivity Formula ts ts_util No Threshold based 80 o oO 100 Disabled Enabled ts ts_op_status Yes State based 0 ts ts_status Disabled Enabled ts ts_auto_resize_ status Yes State based 0 ts ts_last_resize_fail Disabled Enabled ts ts_util_auto_resize Yes Threshold based 80 o oO ts ts_used_pages ts ts_ page _size ts ts_max_size 100 Actions Threshold or State checking Chapter 7 Monitoring and troubleshooting DB2 Disabled Enabled 367 368 3 Populate a desired amount of data into the table space We populate a certain amount of data into the table space to trigger the threshold DB2 common table expression is used in our example to generate the specified number of rows Example 7 4 In our example 280 000 rows are inserted into the table and the threshold value of table space utilization will be exceeded Example 7 4 Populating data to trigger the threshold for table space utilization db2inst1 mensa db2home db2inst1l script gt more ins_empinfo db2 INSERT INTO db2instl empinfo WITH tmpinfo ID AS VALUES 1 UNION ALL SELECT ID 1 FROM tmpinfo WHERE ID lt 250000 SELECT ID TRANSLATE CHAR INTEGER RAND 1000000 CASE MOD ID 4 WHEN O THEN aeiou bcdfg WHEN 1 THEN aeiou hjkim WHEN 2 THEN aeiou npqrs ELSE aeiou twxyz END 1234567890 AS LASTNAME CURRENT DATE RAND
184. OVa e Eaa software Up and Running with DB2 on Linux Experience the power of the integration of DB2 9 5 and Linux Make it easier to get DB2 for LUW up and running on Linux Leverage DB2 powerful autonomic technology Whei Jen Chen Christian Hideaki Kondo Helmut Riegler Lifang LF Liu Veiko Spranger edbooks ibm com redbooks International Technical Support Organization Up and Running with DB2 on Linux June 2008 SG24 6899 01 Note Before using this information and the product it supports read the information in Notices on page ix Second Edition June 2008 This edition applies to DB2 for Linux UNIX and Windows Version 9 5 Red Hat Enterprise Linux RHEL 5 SUSE Linux Enterprise Server SLES 10 and Ubuntu 7 10 Copyright International Business Machines Corporation 2008 All rights reserved Note to U S Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents Notices 20500 ed ee Se a ds ae de Se a ix Trademarks o oo ceete Pa ae e ae a enact eee cote Ade ape teed ee pi x Prelate e532 sce r AEn yan Saye RETA AREE A beaded Ma xiii The team that wrote this book 0 0 00 cee eee xiii Acknowledgements nananana nnana anaa XV Become a published author 2 0 0 xvi Comments welcome 000 00 e eee eee eee xvi Summary of changes 0 0000 cette ee xix June 2008 Second Ed
185. Only db2jcc jar is required to be in the CLASSPATH On 64 bit systems you have to replace the jdk32 path with the jdk64 path Example 8 17 on page 450 uses the driver db2jcc jar which is a Type 4 driver and is the suggested driver type The Type 2 driver is also available but it is deprecated The name of the class file for the Type 2 driver is db2java zip DB2 9 5 supports JDBC 3 0 and JDBC 4 0 If you want to use JDBC 4 0 you have to use the driver db2jcc4 jar SQLJ SQLJ allows you to embed SQL statements into the Java code Example 8 19 shows an SQLJ program You have to replace lt port gt and lt password gt with the actual values Example 8 19 SQLJ example program test_sqlj sqlj import sqlj runtime import java sql sql context EzSqljCtx sql iterator EzSqljNamelter String empno Double salary public class test_sqlj public static void main String args throws ClassNotFoundException try Class forName com ibm db2 jcc DB2Driver Connection con DriverManager getConnection jdbc db2 localhost lt port gt SAMPLE db2inst1 lt password gt EzSqljCtx ctx new EzSqljCtx con Chapter 8 Application development 451 452 EzSqljNameIter iter sql ctx iter select empno salary from employee where salary lt 36000 order by lastname while iter next System out printIn iter empno iter salary iter close ctx close catch SQLException e
186. PLE DB2INST1 USERSPACE1 DB2INST1 USERSPACE1 Views DB2INST1 USERSPACE1 G Aliases DB2INST1 USERSPACE1 Nicknames DB2INST1 USERSPACE1 Cache Objects Triggers Schemas G Indexes G Table Spaces Tables Event Monitors Database partition groups Actions Select an object from the list above to display mor Buffer Pools cp Create New Table G Application Objects User and Group Objects we Federated Database Objects G XML Schema Repository SR Figure 3 2 Main window of the Control Center 94 Up and Running with DB2 on Linux 3 2 Preparation for the database creation There are a few configuration tasks that need to be done on Linux and DB2 before creating the database Here we discuss Codepage considerations Table space consideration Linux specific configuration Multi partition specific configuration vvvy 3 2 1 Codepage considerations In DB2 9 5 the default database codepage is UTF 8 The codepage is specified during database creation time If you want to change the codepage afterwards the database must be recreated Figure 3 3 shows an example architecture We use this architecture to discuss the codepage conversion that has taken place between the database and the application Database tier Presentation tier Web browser of a ae i chinese user Application No conversion UTF 8 hosted in an application server UTF 8 No convers
187. Running with DB2 on Linux If your Red Hat distribution has X Window System software you can install these packages using system administration tool Package Manager For example to install pdksh on Red Hat Enterprise Linux RHEL 5 a Log on as root b Choose Applications Add Remove Software and then choose the appropriate packages If your SUSE distribution has X Window System software you can install these packages using YaST For example to install pdksh on SUSE Linux Enterprise Server SLES 10 a Log on as root b From the YaST2 Control Center select Software Install or Remove Software and then choose the appropriate packages Notes gt The RPM name might differ depending on the Linux distribution and the version that you use Check the latest Linux information for the RPM name that you require gt If the required package does not exist in the Linux distribution DVD CD you might need download it from the related Linux support Web site 2 2 Installation considerations and planning Now that you have verified that your system meets DB2 basic requirements it is time to prepare your system for DB2 installation In this section we discuss the following topics gt Considerations Multiple DB2 copies Non root installation Support changes for 32 bit and 64 bit DB2 servers gt Installation methods DB2 Setup db2_install and response file installation gt Storage planning File systems
188. SG24 6899 01 ISBN 0738485314 Iln ul TLL Redbooks INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization Experts from IBM Customers and Partners from around the world create timely technical information based on realistic scenarios Specific recommendations are provided to help you implement IT solutions more effectively in your environment For more information ibm com redbooks
189. STATS configuration parameter If this configuration parameter is set to ON table statistics are automatically compiled at statement compilation time whenever they are needed to optimize a query Optionally you can enable the automatic statistics profile generation by setting the following two configuration parameters to ON gt AUTO_STATS_PROF gt AUTO_PROF_UPD Automatic statistics profiling advises when and how to collect table statistics by detecting outdated missing or incorrect statistics and by generating statistical profiles based on query feedback Automatic reorganization After many changes to table data the table and indexes can become fragmented Logically sequential data can be on non sequential physical pages therefore the database manager has to perform additional read operations to access data Among other information the statistical information collected by RUNSTATS shows the data distribution within a table In particular analysis of these statistics can indicate when and what kind of reorganization is necessary Automatic reorganization determines the need for reorganization on tables and indexes by using the REORGCHK formulas It periodically evaluates tables and indexes that have had their statistics updated to see if reorganization is required If so it internally schedules an index reorganization or a classic table reorganization for the table A table reorganization requires that your applications function
190. Set up partitioning options for the DB2 instance 70 Up and Running with DB2 on Linux 13 On the Set user information for the DB2 instance owner window Figure 2 11 set user information for the DB2 instance owner By default DB2 Setup creates a new user db2inst1 in group db2adm1 You can change user and group names or configure an existing user to the new DB2 V9 5 instance by selecting Existing user Note that the default home directory is in home We recommend that you change the instance home directory to a DB2 specific directory such as db2home db2inst1 db2iadm1 1001 db2home db2inst1 WEETITEIE Figure 2 11 Root installation Set user information for the DB2 instance owner 14 On the Set user information for the fenced user window this user is responsible for executing fenced user defined functions such as UDFs and stored procedures Again note the home directory location We recommend that you change the fenced user home directory to a DB2 specific directory such as db2home 15 On the Prepare the DB2 Tools catalog window accept the default option Do not prepare the DB2 Tools catalog and click Next 16 On the Set up notifications window Figure 2 12 on page 72 if you choose Set up your DB2 server to send notifications specify a Notification SMTP server name here and then click Next Chapter 2 Installation 71 smtp itsosj sanjose im com amaia Us carar O Figure 2 1
191. State Normal 1 Instances view All Objects Figure 7 2 Using toggle buttons to filter the alerts The Configuration option in the Heath Center allows you to set up notification for the instance and to modify health indicator settings When you choose the Configure menu item a submenu with two items is displayed refer to Figure 7 3 You can view or change the health indicator settings by clicking Health Indicator Settings or you can use Alert Notification to set up the notification for the Health Monitor erts db2inst1 There are currently no ale M Configure Health Indicator Settings M Show Notification Log Alert Notification M Refresh TI Figure 7 3 Configure menu in the Health Center If you want to notify people by using e mail or a pager when an alert is generated you need to define a contact list first You can add a contact or contact group in the Contacts management panel or by using DB2 CLP commands For example to add a contact db2inst1 itsosj sanjose ibm com to the contact list execute the following command db2 add contact db2instl type email address db2instl itsosj sanjose ibm com Chapter 7 Monitoring and troubleshooting DB2 357 If you want to add the contact using the Contacts management GUI tool select Tools Contacts within the Health Center Figure 7 4 Figure 7 4 Starting Contacts management Within the Contacts panel you can add or change c
192. TATISTICS option to obtain the new statistics and check the table again Example 6 37 Example 6 37 Using REORGCHK to update the statistics for the table db2inst1 mensa gt db2 reorgchk update statistics on table db2instl item Doing RUNSTATS Table statistics Fl 100 OVERFLOW CARD lt 5 Chapter 6 Administering databases 293 F2 100 Effective Space Utilization of Data Pages gt 70 F3 100 Required Pages Total Pages gt 80 SCHEMA NAME CARD OV NP FP ACTBLK TSIZE F1 F2 F3 REORG 1502010 0 3714 7394 30040200 0 50 50 Index statistics F4 CLUSTERRATIO or normalized CLUSTERFACTOR gt 80 F5 100 Space used on leaf pages Space available on non empty leaf pages gt MIN 50 100 PCTFREE F6 100 PCTFREE Amount of space available in an index with one less level Amount of space required for all keys lt 100 F7 100 Number of pseudo deleted RIDs Total number of RIDs lt 20 F8 100 Number of pseudo empty leaf pages Total number of leaf pages lt 20 SCHEMA NAME INDCARD LEAF ELEAF LVLS NDEL KEYS LEAF_RECSIZE NLEAF_RECSIZE LEAF_PAGE_OVERHEAD NLEAF_PAGE_OVERHEAD F4 F5 F6 F7 F8 REORG Table DB2INST1 ITEM Index DB2INST1 PK_ITEM_ITEMID 1502010 3106 2 3 2912 1502010 4 4 1340 1340 100 91 12 0 0 From the output we can see that DB2 has recommended that we reorganize the table based on the output underneath REORG in the table statistics section The
193. TBSP32KTMP0000 5 record s selected 504 Up and Running with DB2 on Linux IBMCATGROUP IBMTEMPGROUP IBMDEFAULTGR IBMCATGROUP IBMTEMPGROUP 1 1 OUP 1 2 2 db2inst1 Mensa gt db2 select substr bpname 1 15 BPNAME bufferpoolid substr dbpgname 1 15 DBPG npages pagesize from syscat bufferpools BPNAME BUFFERPOOLID DBPG NPAGES PAGESIZE IBMDEFAULTBP 1 1000 4096 BP32K0000 2 250 32768 2 record s selected In Example B 4 on page 503 the table spaces TBSP32K0000 with table space ID 3 and TBSP32KTMP0000 with table space ID 4 were created automatically by the CREATE TOOLS CATALOG command each with a page size of 32 K The first table space is a regular table space that is used to store the task related tables and the second table space is a temporary table space In addition a new buffer pool named BP32K0000 is created with a page size of 32 K You need to recycle the database manager to have all of the new changes take effect Before you stop the instance if you use the LIST APPLICATIONS command you might discover that certain applications are connected to the Tools Catalog Database with the application name db2dastm as shown in Example B 5 Example B 5 Applications connected to Tools Catalog Database db2inst1 Mensa gt db2 list applications Auth Id Application Appl Application Id DB of Name Handle Name Agents DB2INST1 db2dasstm 271 NO db2inst1 080128234908 TOOLSCAT 1 To restart the database manager you
194. TER TABLE PART1 ADD PARTITIONING KEY P_PARTKEY Example 3 30 on page 127 shows the statement for SNG_01 in our database ITSODB 126 Up and Running with DB2 on Linux Example 3 30 Alter database partition group SNG_0O1 db2instl mensa gt db2 alter database partition group sng _01 add dbpartitionnum 2 without tablespaces SQL1759W Redistribute database partition group is required to change database partitioning for objects in nodegroup SNG_01 to include some added database partitions or exclude some dropped database partitions SQLSTATE 01618 The message SQL1759W is just a warning indicating that all tables in this database partition group have to be redistributed but all tables are still accessible Then we add the table space container for SNG_01 Example 3 31 Example 3 31 Att table space container for SNG_0O1 db2instl mensa gt db2 alter tablespace SAMPLE_SNG add db db2inst1 NODEO002 ITSODB SAMPLE_SNG on dbpartitionnum 2 SQL1759W Redistribute database partition group is required to change database partitioning for objects in nodegroup SNG_01 to include some added database partitions or exclude some dropped database partitions SQLSTATE 01618 The redistribute command affects all table spaces and tables in the given database partition group However the redistribution occurs online and all tables and indexes are still fully accessible To redistribute all data in database partition group SNG_01 log on to t
195. TURE_FOR_ESE N ESE NOT_USED HRESE IBM_HOMOGENEOUS_REPLICATION_FEATURE_FOR_ESE N ESE NOT_USED 8 record s selected Installing a license key To install a license key you must add the db2 ic license file using the db21 icm command To add a DB2 license file 1 Log in as the instance owner 2 Enter the following command db2licm a lt filename gt where filename is the full path name and file name of the license file db2ese lic The license file is available from either the DB2 product the feature image that you downloaded from Passport Advantage or from the Activation CD that you received in the physical media pack On Linux servers the license file is located in cd db2 license If you are setting up a multi partitioned database system perform this task on each machine To remove a license file use db2licm r For example db2licm r db2ese Up and Running with DB2 on Linux Setting up a license policy For DB2 Connect Enterprise Server Edition the license policy controls and monitors the number of users that can connect simultaneously to a DB2 Connect server For WebSphere Replication Server or WebSphere Federation Server the license policy controls and monitors the number of connectors to a non DB2 data source Perform the following task 1 Log in as the instance owner 2 If you purchased a DB2 Connect Server Concurrent User policy enter the following command db2licm p db2consv concurrent If you pu
196. This is also called version recovery Data that is easily recreated can be stored ina non recoverable database Data that cannot be easily recreated needs to be stored in a recoverable database For a recoverable database DB2 can restore the entire database or a part of the database to the point in time where the interrupt occurred to the end of the log or to a specific point in time We call this process rollforward recovery Database logging A key element of any high availability strategy is database logging DB2 is logging every transaction unless told not to or in the case of using the Load utility The database log files are important if they are needed to recover the database Recovery log files and the recovery history file are created automatically when a database is created DB2 has two types of logging mechanisms gt Circular logging Circular logging is the default logging method for a newly created database If both the LOGARCHMETH1 and LOGARCHMETH2 database configuration parameters are set to OFF the database is non recoverable and circular logging is used A set of log files is used in round robin fashion These log files are used by crash recovery if needed Crash recovery is the process where all uncommitted changes are rolled back to a consistent state of the data gt Archive logging By using archive logging the database is considered a recoverable database To enable archive logging set the LOGARCHMETH1 or LOGARC
197. Type element presents you with its definition as shown in Figure 5 20 E products ype productT ype pid int e product 1 productType ees e description 1 1 descriptionType Figure 5 20 Definition of the product element To see the definition of the descriptionType element double click it Figure 5 21 al productType f descriptionType pid int name 1 1 string price 1 1 double e description 1 1 descriptionType Figure 5 21 Definition of the description element The XML schema editor GUI navigates through the XML structure and allows you to add or modify definitions easily With this guidance you are able to avoid syntax errors You also have the choice of switching to the source and editing the file directly You can create an XML document from the XML schema definitions that you have created In the Data Project Explorer view right click XML Documents and select New gt XML At the Create XML File panel select Create XML file from an XML schema file Provide the name for the project the new XML file and the schema file After going through the rest of panels you get to the XML editor for that file Chapter 5 IBM Data Studio 219 The XML editor guides you based on the schema definition Figure 5 22 Just right click the elements and the XML editor provides you with only the valid options The options come fr
198. a Large table space 0x0000 3 IBMDB2SAMPLEREL Database managed space All permanent data Large table space 0x0000 In a partitioned database server environment only the table spaces Mensa db2 CONNECT TO itsodb completed ok Database Connection Information Database server SQL authorization ID Local database alias DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Tablespaces for Current Database Tablespace ID Name Type Contents Space State Detailed Normal Tablespace ID Name Type Contents State Detailed Normal Tablespace ID Up and Running with DB2 on Linux explanation explanation 0 SYSCATSPACE Database managed space All permanent data Regular table 0x0000 1 TEMPSPACE1 System managed space System Temporary data 0x0000 db2_ps Name USERSPACE1 Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Normal Tablespace ID 3 Name IBMDB2SAMPLEREL Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Normal DB210111 In a partitioned database server environment only the table spaces on the current node are listed gemini db2 CONNECT TO itsodb completed ok Note With DB2 Version 9 5 you do not need use db2_a11 to execute a database backup or to update database configurations any longer You can now back up and restore multiple database partitions at on
199. a host with more than one partition every command or SQL statement runs against the first database partition on this host by default To run the commands or SQL statements on the other database partitions you need to specify the database partition by setting the DB2NODE variable or by using the DB2 command SET CLIENT Log on as the instance owner or any user with sysadm or sysctrl authority to the host where the database catalog needs to be created Verify that you have initialized your DB2 environment as shown in Example 3 13 Example 3 13 Verify DB2 environment db2instl mensa gt echo DB2INSTANCE db2instl db2inst1 mensa gt The rah and db2_all command Before we start with the creation of the multi partitioned database we show you the db2_a11 and the rah commands Both commands are useful in order to execute commands on all partitions The db2_a1 command can be used to execute commands on all database partitions For instance if you want to create a directory on all partitions you can execute this command to create a directory on all nodes as shown in Example 3 14 Example 3 14 Example of the typeset command db2instl mensa gt db2_all typeset Z4 DB2NODE mkdir p database db2inst1 NODE DB2NODE ITSODB SAMPLE_MPL mensa itsosj sanjose ibm com typeset Z4 DB2NODE completed ok gemini itsosj sanjose ibm com typeset Z4 DB2NODE completed ok You can use the rah command to execute commands on all physical hosts The
200. a program test_java java import java sql Connection import import import import public pub java sql DriverManager java sql SQLException java sql ResultSet java sql Statement class test_java ic static void main String args try 450 Class forName com ibm db2 jcc DB2Driver Connection con DriverManager getConnection jdbc db2 localhost lt port gt SAMPLE db2inst1 lt password gt Statement stmt con createStatement ResultSet rs stmt executeQuery select empno salary from employee where salary lt 36000 order by lastname while rs next System out printIn rs getString empno rs getDouble salary con close catch SQLException e System out printIn e getMessage nSQLCode e getErrorCode SQLState e getSQLState catch ClassNotFoundException e System out printIn e getMessage Example 8 18 on page 451 shows the steps to compile and run this program Up and Running with DB2 on Linux Example 8 18 Compile and run the Java application test_java java db2inst1 puget gt DB2JAVA home db2inst1 sqllib java db2inst1 puget gt DB2JAVA jdk32 bin javac test_java java db2inst1 puget gt DB2JAVA jdk32 bin java classpath DB2JAVA db2jcc jar test_java class 200340 31840 0 000290 35340 0 000310 35900 0 200310 35900 0 200330 35370 0 Note that no DB2 client is needed for running this Java program
201. a that is included with the DB2 Database for Linux UNIX and Windows product is supported 1 2 3 DB2 products and packages DB2 for Linux UNIX and Windows offers industry leading performance scale and reliability through DB2 packages for the production environment Additional DB2 Enterprise features Additional DB2 Workgroup and Express features Products for accessing existing and host data DB2 for pervasive platforms vvvvy DB2 packages for the production environment DB2 for Linux UNIX and Windows provides a variety of packages for users based on the users business needs This section introduces the various DB2 packages DB2 Express C Edition DB2 Express C 9 5 is a fully functional edition of the DB2 data server and is available for download and deployment at no charge DB2 Express C helps developers midmarket partners and multibranch companies accelerate their time to value and reduce the total cost of ownership DB2 Express C 9 5 includes pureXML and the autonomic features available in the larger enterprise editions To upgrade to the other editions of DB2 9 5 you simply install the license certificate with no changes to your application code The no charge edition of DB2 Express C can utilize up to two processor cores and 2 GB of memory while a licensed support option can use four cores and 4 GB of memory DB2 Express Edition DB2 Express 9 5 is a full function DB2 data server which provides very attractive entry
202. abase Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2inst1 mensa db2backup datamove gt db2 select substr tabschema 1 10 substr tabname 1 10 substr tbspace 1 10 from syscat tables where tabname ITEM DB2INST1 ITEM TSDATA2 1 record s selected db2inst1 mensa db2backup datamove gt db2 connect to itsorepl Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSOREPL Database server SQL authorization ID Local database alias db2inst1 mensa db2backup datamove gt db2 select substr tabschema 1 10 substr tabname 1 10 substr tbspace 1 10 from syscat tables where tabname ITEM 1 2 3 338 Up and Running with DB2 on Linux DB2VS ITEM USERSPACE1 1 record s selected For details regarding this utility refer to DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 The ADMIN COPY SCHEMA stored procedure is another method to copy a schema You can use this stored procedure to copy a specific schema and all of the objects that are contained in it The new target schema objects will be created using the same object names as the objects in the source schema but with the target schema qualifier Note You can use the ADMIN_COPY_SCHEMA procedure for copying schemas within the same database while the db2move utility is used across databases In Example 6 62 we create a schema called db2vs1 Example 6 62 Usi
203. ace the lt password gt Example 8 7 Perl script using DBI peritest p usr bin per use DBI my dbhandle DBI gt connect dbi DB2 SAMPLE db2inst1 lt password gt my sth dbhandle gt prepare select empno lastname firstnme salary from employee where salary lt order by lastname or die Couldn t prepare statement dbh gt errstr sth gt execute 36000 while data sth gt fetchrow_array print data 0 data 1 data 2 data 3 n exit 0 Example 8 8 on page 438 shows the output of Example 8 7 Chapter 8 Application development 437 8 3 2 PHP Example 8 8 Output of the DBI Perl script db2inst1 puget redbook perl gt perltest pl 200340 ALONZO ROY 31840 00 000290 PARKER JOHN 35340 00 000310 SETRIGHT MAUDE 35900 00 200310 SPRINGER MICHELLE 35900 00 200330 WONG HELENA 35370 00 Note Red Hat Enterprise Linux RHEL 5 1 and SUSE Linux Enterprise Server SLES 10 1 include Perl and Perl DBI RPM packages Red Hat perl 5 8 8 10 and perl DBI 1 52 1 fc6 SUSE perl 5 8 8 14 2 and perl DBI 1 50 13 2 To create a DB2 application with Perl the Red Hat and SUSE users only have to install and compile the DBD DB2 package You can obtain more examples under lt instance home gt sqllib samples perl Here are several good references for Perl application development on DB2 gt Everything you need to know about mod_perl technology http perl apache
204. ach database partition and run each script against its associated database partition Example 6 26 shows the output for database partition 0 Example 6 26 Execute the script for database partition O db2inst1 mensa db2home db2inst1 gt mkdir tablespaces ITSO0000 db2inst1 mensa db2home db2inst1 gt export DB2NODE 0 db2inst1 mensa db2home db2inst1 gt db2 terminate DB20000I The TERMINATE command completed successfully db2inst1 mensa db2home db2inst1 gt db2 tvf itsodb_node0000 clp UPDATE COMMAND OPTIONS USING S ON Z ON ITSODB_NODE0000 out V ON DB20000I1 The UPDATE COMMAND OPTIONS command completed successfully SET CLIENT ATTACH _DBPARTITIONNUM 0 DB20000I1 The SET CLIENT command completed successfully SET CLIENT CONNECT _DBPARTITIONNUM 0 DB20000I1 The SET CLIENT command completed successfully RESTORE DATABASE ITSODB FROM db2backup TAKEN AT 20080206173239 INTO ITSODB REDIRECT SQL2539W Warning Restoring to an existing database that is the same as the backup image database The database files will be deleted Do you want to continue y n y SQL1277W A redirected restore operation is being performed Table space configuration can now be viewed and table spaces that do not use automatic Chapter 6 Administering databases 267 268 storage can have their containers reconfigured DB20000I The RESTORE DATABASE command completed successfully SET TABLESPACE CONTAINERS FOR 4 USING FILE tablespaces ITSO0000 TSDATA1 000 400
205. achine system allowing for example both production and development environments to run on the same machine under separate DB2 instances without interfering with each other Up and Running with DB2 on Linux instance s Databases Database partition group s og Q Table Space Tal Index es long data Figure 1 3 DB2 database objects Databases A relational database presents data as a collection of tables A table consists of a defined number of columns and any number of rows Each database includes a set of system catalog tables that describes the logical and physical structure of the data a configuration file containing the parameter values allocated for the database and a recovery log Database partition groups A database partition group is a set of one or more database partitions Before creating tables for the database you first need to create the database partition group where the table spaces will be stored and then create the table space where the tables will be stored If a partition group is not specified there is a default group where table spaces are allocated In earlier versions of DB2 database partition groups were known as node groups In a non partitioned environment all the data resides in a single partition therefore it is not necessary to worry about partition groups Table spaces A database is organized into parts called table spaces A table space is a place to store tables When c
206. active in your database environment If an object is considered to be in an unhealthy condition based on the threshold or an object state the notifications can be sent and actions can be taken automatically Configuring the Health Center You can use the toggle buttons 95 35 92 to filter the alerts according to their severity Figure 7 2 on page 357 The Health Center is opened with the Up and Running with DB2 on Linux Object in Any Alert State toggle button third toggle button selected by default which helps to identify those instances with current alerts that need to be addressed If the Health Center is opened for the first time you can choose the All Objects toggle button the fourth toggle button to display A Objects to view the navigation tree with all cataloged Linux UNIX and Windows LUW instances on the left pane of the panel bjects in Any Alert State E Welcome to the Health Center g Legend How to use the Health Center To view alerts within an instance or database select the object on the left hand side Databases are listed below their parent instance Filter the contents on the left by selecting the state toggle buttons at the top of the navigation view Current Instance Status Last refresh 2 18 08 4 26 PM Refresh Alarm 0 Instances View Objects in Alarm State Warning A 0 Instances A View Objects in Alarm or Warning State Attention 0 Instances View Objects in Any Alert
207. aking the longest processor time a percentage and the largest amount of memory a percentage plus how long the system has been up and the amount of free memory By default the utility will refresh the display every 3 0 seconds You can override the default refresh Up and Running with DB2 on Linux interval via the command option d The users need to be aware that the top command does not report the total memory that is used for DB2 correctly Top will overstate memory usage by counting shared memory segments multiple times Note In Linux DB2 will not free shared memory automatically To free the shared memory you need to recycle DB2 Table 7 1 lists several frequently used command line options for top Table 7 1 Frequently used command options for top fa Specifies the delay between display updates Monitor only processes with the given process id This flag can be given up to twenty times o Start top while ignoring any idle or zombie processes Displays the command line instead of the command name only Batch mode Useful for sending output from top to other programs or to a file In this mode top will not accept command line input It runs until it produces the number of iterations requested with the n option or until stopped Output is plain text that is suitable for display on a terminal If you are not using batch mode to run top when the output of top displays you can use the interactive command to control the
208. al information might be inaccurate here For example the CARD is 3 000 000 in reality but here it shows 3 000 728 the number of records on database partition 0 multiplied by the number of database partitions Another command INSPECT CHECK can be used to generate accurate information about the pages occupied by the table and index objects 2 Delete rows from the table ITEM Example 6 36 on page 293 292 Up and Running with DB2 on Linux Example 6 36 Delete rows from table db2instl mensa gt db2 select count from item 3000000 1 record s selected db2inst1 mensa gt db2 tvf tmp itemdel sql delete from item where itemid gt 250000 and itemid lt 500000 DB200001 The SQL command completed successfully delete from item where itemid gt 750000 and itemid lt 1000000 DB20000I The SQL command completed successfully delete from item where itemid gt 1250000 and itemid lt 1500000 DB20000I The SQL command completed successfully delete from item where itemid gt 1750000 and itemid lt 2000000 DB20000I1 The SQL command completed successfully delete from item where itemid gt 2250000 and itemid lt 2500000 DB20000I The SQL command completed successfully delete from item where itemid gt 2750000 and itemid lt 3000000 DB20000I The SQL command completed successfully db2instl mensa gt db2 select count from item 1500000 1 record s selected 3 Use REORGCHK with the UPDATE S
209. all sqlfLogUpdateCfgParam probe 20 NGE CFG DB ITSODB Newlogpath From To db21lo0g1 ITSODB 8 02 12 10 30 43 496729 480 13914746474 LEVEL Info Chapter 3 Post installation tasks 121 122 PID 10434 TID 2968513440 PROC db2sysc 0 INSTANCE db2inst1l NODE 000 DB ITSODB APPHDL 0 84 APPID LOCAL db2inst1 080212183043 AUTHID DB2INST1 EDUID 61 EDUNAME db2agent ITSODB 0 FUNCTION DB2 UDB data protection services sqlpgnip probe 1240 MESSAGE Active log path is moved to db210g1 ITSODB NODE0000 We also activate the mirrored logs in order to enhance the availability as shown in Example 3 24 Example 3 24 Activate the mirror logs db2instl puget gt db2 UPDATE DB CONFIG FOR itsodb USING MIRRORLOGPATH db210g2 1TSODB DB20000I1 The UPDATE DATABASE CONFIGURATION command completed successfully SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically For these configuration parameters al applications must disconnect from this database before the changes become effective db2instl puget gt db2 terminate DB20000I1 The TERMINATE command completed successfully db2instl puget gt db2 connect to itsodb Database Connection Information DB2 LINUX 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2instl puget gt db2 get db config for itsodb grep NEWLOGPATH MIRRORLOGPATH Path to log files Changed path to
210. an ideal language for writing programs that will run on multiple platforms Unlike languages such as C or C Java is completely specified and each Java enabled platform supports a known core of libraries One of these libraries is JDBC which you can think of as a Java version of ODBC Using Java in conjunctlon with JDBC allows you to write portable database applications Note You can obtain information about programming Java for DB2 in Developing Java Applications SC23 5853 JDBC Because of their portability you can develop Java applications on any system If you want to develop Java programs under Linux you can use tools such as Data Studio Eclipse Rational Developer Netbeans or just a plain Java Developer Kit JDK from Sun Example 8 17 on page 450 demonstrates the development of a small JDBC based Java program using the plain Software Developer Kit SDK and the Type 4 driver It selects data from the EMPLOYEE table in the SAMPLE database First the driver is loaded by the driver manager Then a connection is created based on the driver URL jdbc db2 lt hostname gt lt port gt lt database gt The application then performs a SELECT on the table and loops through the result set Before running the example you must replace the lt port gt by the port number of your instance and you must replace the lt password gt by the actual password Chapter 8 Application development 449 Example 8 17 Sample JDBC Jav
211. anges that occurred in Version 9 1 too such as these changes gt Alternate fix pack images are discontinued gt Type 3 Java Database Connectivity JDBC support is discontinued gt The Data Warehouse Center and the Information Catalog Center are no longer included gt Text Extender is no longer supported gt Audio Image and Video AIV Extenders are no longer supported gt The DB2_SCATTERED_IO registry variable is discontinued 4 1 3 Migration test consideration The entire migration process consists of two parts installing DB2 9 5 code and migrating instances and databases Installing DB2 9 5 code does not require system downtime Migrating instances and databases is the actual step that converts your DB2 system from Version 8 or 9 1 to Version 9 5 You need to stop DB2 to perform the migration of the instances and the databases We recommend that you install and test DB2 Version 9 5 before migrating any Version 8 or Version 9 1 instances to Version 9 5 If you have a test environment that mimics the production system you can install DB2 Version 9 5 migrate DB2 instances and databases test all your applications on the test system and then carry the same procedure to the production environment However if you have a limited test environment or no test environment you can utilize the DB2 features to test your applications under the new version Because multiple versions of DB2 can coexist on Linux you can install DB2
212. appear in the pop up window when you right click the instance name as shown in Figure 7 1 on page 356 Similarly the Stop Health Monitor menu item will appear if HEALTH_MON is set to ON and the Health Monitor is started Chapter 7 Monitoring and troubleshooting DB2 355 356 Health Center o mm Start Health Monitor Configure Show Notification Log Refresh Lof Litems 14 3 gt 4 MF y v i View Health monitor data is refreshed 2 18 08 3 56 PM Figure 7 1 Start Health Monitor for an instance using Health Center You can also use DB2 CLP commands to activate the Health Monitor by updating the HEALTH_MON parameter for DBM and to view the current setting of the HEALTH_MON parameter as shown in Example 7 1 Example 7 1 Check if Health Monitor is enabled for the instance db2inst1 mensa db2home db2inst1 gt db2 get dbm cfg grep i health Monitor health of instance and databases HEALTH MON OFF db2inst1 mensa db2home db2inst1 gt db2 update dbm cfg using HEALTH MON on DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully db2inst1 mensa db2home db2inst1 gt db2 get dbm cfg grep i health Monitor health of instance and databases HEALTH MON ON The HEALTH_MON parameter can be dynamically changed The update to the HEALTH_MON takes effect immediately When the HEALTH_MON is turned on the default an agent will collect information about the health of the objects that are
213. apter 6 Administering databases 325 Control Center 22 Control Center O All Systems All Databases a 0 Tsong DB2INST1 TSDATA2 T abies TA DB2INST1 IBMDB2SAMP Views ges ITEM Aliases G Nicknames Cache Objects 5 Triggers E Schemas 5 Indexes 5 Table Spaces O Event Monitors Database partition groups G Buffer Pools G Application Objects G User and Group Objects G Federated Database Objects G XML Schema Repository SR E O ITSOREPL E 0 SAMPLE A TooscaT Figure 6 34 Invoking Load Wizard from DB2 Control Center 2 Choose the load operation Figure 6 35 on page 327 326 Up and Running with DB2 on Linux Load Wizard ITEMLOAD Figure 6 35 Choose the load operation mode 3 Choose whether the original table data will be kept Figure 6 36 on page 328 Chapter 6 Administering databases 327 Load Wizard ITEMLOAD DATH paete cee 55 ellirinis eeteil s ejcte Figure 6 36 Choose if the original table data will be kept or replaced 4 Specify the input and output files Figure 6 37 on page 329 In this panel you can specify the input file format and that options that are specific for the selected format For example you can click DEL Options to set up your source DEL file related options You also can specify where the source resides Server or Remote host In addition you can specify the input file name and the output message file name manually or by browsing files using this ellipsis
214. arameter DBPARTITIONNUM lt number gt Up and Running with DB2 on Linux Important DB cfg parameters This section describes important database configuration parameters and the recommended settings Many of the parameters are handled by STMM We discuss STMM in 3 6 DB2 configuration on page 132 gt AVG_APPLS which can be set to AUTOMATIC This parameter lets DB2 know how many concurrent applications run in your system on average When set to 1 DB2 gives every application all of the current available memory in the buffer pool Changing this parameter can have a huge impact on the performance CATALOGCACHE_SZ This parameter holds database table space table and index information in memory DB2 looks first in this cache when it prepares an execution of a plan Sufficient memory avoids cost intensive disk I O Check with db2 get snapshot for database on db_name and compute the hit ratio with 100 Catalog cache inserts X100 Catalog cache lookups MAXFILOP This is the number of files that each application can open The default value is typically too low Opening files and closing files slow SQL response times and burn CPU cycles If files are being closed adjust the value of MAXFILOP until the opening and closing stops Use the command db2 get snapshot for database on db_name And look at the Number of files closed f the value is more than 0 increase the MAXFILOP value LOCKTIMEOUT The default is set to
215. ared to the Decision Support System You can distinguish between Online Transaction Processing OLTP and Decision Support Systems DSSs based on the type of their workload OLTP systems process the business related transactions DSS based systems typically have large and long running reports DB2 offers many features to tune both types of workload Figure 1 2 shows an example architecture Reporting Business Data mining applications Secialized datamart DSS ETL ETL A Specialized datamart M Replication Ad hoc reporting Production system OLTP General purpose data warehouse DSS Figure 1 2 Deployment based on workload Chapter 1 Introduction 13 Figure 1 2 on page 13 shows an example architecture based on the workload type The business transactions take place on the production systems OLTP Here you have many transactions that write to the database The types of queries and transactions are well defined The data model is usually highly normalized These systems usually require a very high availability In Figure 1 2 on page 13 there is a general purpose data warehouse that receives the majority of the data from the production system on a regular basis by replicating the data with the data propagator From this general purpose database users can perform ad hoc or as needed reports On this system the transactions are not well known because users are theore
216. as been running Chapter 6 Administering databases 297 Example 6 43 The snapshot and db2pd information for table reorganization Table Snapshot First database connect timestamp 02 13 2008 09 32 59 904159 Last reset timestamp Snapshot timestamp 02 13 2008 14 35 37 023048 Database name ITSODB Database path database db2inst1 NODE0000 SQL00002 Input database alias ITSODB Number of accessed tables 21 Table List Table Schema DB2INST1 Table Name ITEM Table Type User Data Object Pages 3697 Index Object Pages 3101 Rows Read Not Collected Rows Written 8251179 Overflows 0 Page Reorgs 8234 Table Reorg Information Node number 0 Reorg Type Reclustering Inplace Table Reorg Allow Write Access Reorg Index Reorg Tablespace 7 Start Time 02 13 2008 14 35 11 064496 Reorg Phase Max Phase Phase Start Time Status Started Current Counter 543 Max Counter 3696 Completion 0 End Time Database Partition 0 Database ITSODB Active Up 0 days 05 02 38 Table Reorg Information Address TbspaceID TableID PartID MasterTbs MasterTab TableName IndexID TempSpaceID 0x00002B6A7E8F1B28 7 4 n a n a n a ITEM 298 Up and Running with DB2 on Linux Type Online 1 7 Table Reorg Stats Address TableName MaxPhase Phase CurCount 0x00002B6A7E8F1B28 ITEM n a n a 550 Table Snapshot First database connect timestamp Last reset timestamp Snapshot times
217. ask to run if an alert is issued For example you can customize the alarm and warning thresholds for the amount of space that is used in a table space Health Monitor The Health Monitor is a server side tool that constantly monitors the health of the instance and all active database objects when DB2 is started The Health Monitor is enabled by default when a instance is created you can deactivate it by using the database manager configuration parameter HEALTH MON The Health Monitor gathers information about the health of the system using new interfaces that do not impose a performance penalty It does not turn on any snapshot monitor switches to collect information The Health Monitor automatically evaluates a set of health indicators even without user interaction If the Health Monitor discovers that a defined threshold has been exceeded for instance the available log space is insufficient or if it detects an abnormal state for an object for example an instance is down the Health Monitor raises an alert There are three types of alerts attention warning and alarm Any time that an alert is raised the Health Monitor might take any of the following actions to report it gt Record the alert information in the Journal all alarm alerts are written to the Journal Up and Running with DB2 on Linux gt Send alert notifications through e mail or a pager address to the person responsible for the system gt Carry out one or mor
218. assist 224 content management 2 context assist 470 control center 500 Control Center 94 CPU utilization 422 crash recovery 255 create function 430 create procedure 431 create trigger 428 cumulative backup 229 custom 28 61 66 80 512 Up and Running with DB2 on Linux D dasupdt 5 Data 199 data compression 5 data distribution viewer 199 data management 199 data management solution 198 data population 5 data server 6 data warehouse 14 database administration server das 39 50 database code page 171 database collating sequence 171 database level privileges 151 database managed space DMS 16 database managed storage DMS 40 database managed table spaces 98 database object health indicator setting 362 database partition group 15 database territory 171 DB2 Administration Server DAS 77 DB2 Database Partitioning Feature DPF 9 DB2 Enterprise Server Edition ESE 9 DB2 Everyplace 10 DB2 object 428 DB2 setup wizard 38 51 DB2 tools catalog 499 DB2 Workgroup Server Edition WSE 9 DB2 Workgroup Server Unlimited Edition WSUE 9 db2_all 113 241 494 db2_call_stack 493 db2_install 39 db2_ps 497 db2admin start 92 db2ca 147 db2ckmig 177 db2diag 402 db2dump directory 123 db2exmig 181 db2expIn 390 db2fs 425 db2imigr 178 db2iupdt 5 db2jcc4 jar 451 db2In 78 db2logmgr 234 db2look 96 db2move 96 db2mtrk 383 384 db2pd 405 408 db2rbind 181 db2relocatedb 176 db2rmin 78
219. atabase directory structure in the database path for example database on the partition where the new database partition has been created Without using the like dbpartitionnum parameter temporary table space definitions are retrieved from the catalog partition In our example we add a new logical database partition partition 2 on node 0 mensa therefore we have two logical partitions 0 and 2 on mensa and one partition 1 on gemini Check etc services to verify that sufficient ports are reserved for the fast communication manager FCM Shut down your DB2 instance db2stop so that you can modify the db2nodes cfg file Add a new partition in INSTHOME sqllib db2nodes cfg as shown in Example 3 26 Example 3 26 New db2nodes cfg file 0 mensa 0 1 gemini 0 2 mensa 1 Log on to the host as the instance owner where the new partition will reside and start the new partition with db2start dbpartitionnum 2 Alternatively if you start a new database partition with the following command DB2 will update the db2nodes cfg automatically after the next time that the instance stops db2start dbpartitionnum 2 add dbpartitionnum hostname mensa port 1 without tablespaces To create the directory structure used by DB2 we have to issue the add node command if it has not already been issued by starting the database manager Issue the commands shown in Example 3 27 on page 126 Chapter 3 Post installation tasks 125 Example 3 27 Add
220. atalog creation 501 502 Java Development Kit Installation Path DAS JDK _PATH AUTOMATIC db2home dasusr1 das java jdk Java Development Kit Installation Path DAS JDK_64 PATH AUTOMATIC db2home dasusr1 das java jdk DAS Code Page DAS_CODEPAGE 0 DAS Territory DAS_TERRITORY 0 Location of Contact List CONTACT_HOST Execute Expired Tasks EXEC_EXP_TASK NO Scheduler Mode SCHED ENABLE OFF SMTP Server SMTP_SERVER Tools Catalog Database TOOLSCAT_DB Tools Catalog Database Instance TOOLSCAT_INST Tools Catalog Database Schema TOOLSCAT_SCHEMA Scheduler User ID Diagnostic error capture level DIAGLEVEL 2 Now we create the Tools Catalog by CLP as in Example B 2 Example B 2 Creating Tools Catalog by using CLP db2inst1 Mensa gt db2 create database toolscat DB20000I1 The CREATE DATABASE command completed successfully db2inst1 Mensa gt db2 create tools catalog esecat0 use existing database toolscat DB20000I1 The CREATE TOOLS CATALOG command completed successfully Note In the preceding example if you want you can create the new database here it is TOOLSCAT by using the CREATE TOOLS CATALOG command with the CREATE NEW DATABASE clause directly For details regarding the command syntax refer to the DB2 Linux UNIX and Windows Command Reference SC23 5846 01 Then you can check the DAS configuration parameters again and you might discover that the parameters associated with the To
221. ation tasks that you need to perform to have a functional DB2 environment We discuss the following topics Control Center setup Preparation for database creation Creating a database Further configuration Adding a partition DB2 configuration Security Client configuration Configure licensing vvvvvvrvvy Copyright IBM Corp 2008 All rights reserved 91 3 1 Control Center setup 92 DB2 has a rich set of graphical tools that are used for database administrators to manage the database system and for application developers to develop stored procedures and user defined functions The Control Center is one of the general administration tools that is used to help you explore and administer your databases Other tools include the Command Center which can be used to generate SQL queries and the Configuration Assistant which is an excellent tool for configuring your database environment If you want to administer your database server with the Control Center you must start the DB2 Administrator Server on each host of your database server environment The DB2 Administrator service setup procedure is provided in Chapter 2 Installation on page 25 To start the DB2 Administrator Server log on to every host as DAS user and issue db2admin start If you are logged in as the instance owner or a privileged DB2 user and have an X Window started you can use the db2cc amp command to start Control Center If you started your X Windo
222. aw devices for database logs or table space containers you have to change them to block devices a Ensure that the backup taken at step 10 is successful b Shut down your database and consider putting the database in quiesce mode c Use the raw a Linux command to see which raw bindings you defined d Create a configuration file for the db2relocatedb command for each database partition that requires changes Use the clauses CONT_PATH and LOG_DIR to specify the old value with the new value Do not forget to include the NODENUM value in the configuration file e Execute the db2relocatedb command using your definition created in the previous step in each database partition that requires changes f Activate the database 12 As instance owner stop the instance by issuing db2stop Log in as root and issue ps ef grep db2 to check for any outstanding processes on the instance that you are migrating If any processes are still running such as db2bp cancel the process by using the following command kill 9 lt pid gt Up and Running with DB2 on Linux where pid represents the process ID number You must perform this process in all database partition servers Pay attention to whether there are other instances before you stop the processes 13 Run db2ckmig in each database partition to verify that a database can be migrated The db2ckmig command verifies that all of the following conditions are true A cataloged database
223. b2inst1 strcpy password lt password gt EXEC SQL CONNECT TO database USER user USING password if sqlca sqlcode 0 fprintf stderr Error connect d n sqlca sqlcode exit sqlca sqlcode EXEC SQL DECLARE EMP_CUR CURSOR FOR SELECT EMPNO FROM EMPLOYEE WHERE SALARY lt 36000 EXEC SQL OPEN EMP_CUR if sqlca sqlcode 0 fprintf stderr Error open cursor d n sqlca sqlcode exit sqlca sqlcode EXEC SQL FETCH EMP_CUR INTO empno if sqlca sqlcode 0 fprintf stderr Error fetch cursor d n sqlca sqlcode exit sqlca sqlcode while sqlca sqlcode 100 printf s n empno EXEC SQL FETCH EMP_CUR INTO empno if sqlca sqlcode 0 if sqlca sqlcode 100 fprintf stderr Error fetch cursor d n sqlca sqlcode exit sqlca sqlcode EXEC SQL CLOSE EMP_CUR if sqica sqlcode 0 fprintf stderr Error close cursor d n sqlca sqlcode exit sqlca sqlcode Chapter 8 Application development 445 446 In Example 8 12 we compile and run the program The precompile step generates the c and the bnd file The first cc step compiles the C program and the second cc step links it Example 8 12 Run the embedded SQL program db2instl puget gt db2 connect to SAMPLE Database Connection Information DB2 LINUX 9 5 0 DB2INST1 SAMPLE Database server SQL authorization ID Local database alias db2instl puget gt db2 precompile test_emb sqc bindf
224. c point in time use the following commands db2 rollforward db itsodb to 2008 02 06 20 15 30 using local time db2 rollforward db itsodb query status db2 rollforward db itsodb stop gt Table space rollforward recovery If the database is enabled for forward recovery you have the option of backing up restoring and rolling forward table spaces instead of the entire database You can either perform table space rollforward recovery to the end of the logs or to a certain point in time The point in time that you specify must be greater or equal to the minimum recovery time for that table space Example 6 22 shows you how to determine that time Example 6 22 Restore to a minimum point in time db2instl mensa gt db2 restore db itsodb tablespace userspacel online from db2backup taken at 20080206145105 DB20000I1 The RESTORE DATABASE command completed successfully From another login shell find Minimum recovery time db2inst1 mensa gt db2 connect to itsodb db2inst1l mensa gt db2 list tablespaces show detail Tablespaces for Current Database Tablespace ID Name Type Contents space State Detailed explanation Normal Total pages Usable pages Used pages Free pages High water mark pages Page size bytes Extent size pages Prefetch size pages Number of containers Tablespace ID Name Type Contents Up and Running with DB2 on Linux 0 SYSCATSPACE Database managed space All p
225. can t dsa gemini gemini itsosj sanjose ibm com 9 43 86 94 gt gt ssh_known_hosts 5 Restart the ssh daemon etc init d sshd restart SSH client configuration Perform the following steps to configure the SSH client 1 Edit the etc ssh ssh_config file Change the line HostbasedAuthentication from no to yes as shown in Example 2 12 Example 2 12 Edit the ssh_config file HostbasedAuthentication no HostbasedAuthentication yes Note that the ssh server configuration file is sshd_config Add a line to the ssh_config file to tell the ssh client to use the ssh keysign utility to read the host s private key as shown in Example 2 13 Example 2 13 Add a line to the ssh_config file EnableSSHKeysign yes 2 Ensure ssh keysign is an suid root executable Check the ssh keysign setting On SUSE ls 1 usr 1ib64 ssh ssh keysign rwsr xr x 1 root root 173952 2007 05 18 03 55 usr lib64 ssh ssh keysign On Red Hat ls 1 usr libexec openssh ssh keysign rwsr xr x 1 root root 175424 Jul 13 2007 usr libexec openssh ssh keysign If the permissions and owner do not resemble this sample output fix the permissions as shown in Example 2 14 on page 57 and Example 2 15 on page 57 Up and Running with DB2 on Linux Example 2 14 Fix permissions on ssh keysign on SUSE cd usr 1ib64 ssh chown root root ssh keysign chmod 4755 usr libexec openssh ssh keysign Example 2 15 Fix permissions on ssh keysign on Red Hat cd usr libexec openssh
226. cations at a specific time If you capture information at regular intervals snapshots are also useful for observing trends and foreseeing potential problems There are a number of snapshot request types available and each snapshot request type returns a specific type of monitoring data When using the command in a partitioned database environment the snapshots can be taken at any partition of the instance or globally A global snapshot aggregates the data collected at each partition and returns a single set of values Example 7 21 has two samples showing the difference Example 7 21 A global snapshot db2instl mensa gt db2_all db2 get snapshot for all on itsodb grep Locks held currently Locks held currently 1 mensa db2 get snapshot for completed ok Locks held currently 8 gemini db2 get snapshot for completed ok db2inst1l mensa s gt db2 get snapshot for all on itsodb global grep Locks held currently Locks held currently 9 db2instl mensa gt db2_all db2 get snapshot for all on itsodb grep Lock list Lock list memory in use Bytes 5888 mensa db2 get snapshot for completed ok Lock list memory in use Bytes 3392 Chapter 7 Monitoring and troubleshooting DB2 409 410 gemini db2 get snapshot for completed ok db2instl mensa gt db2 get snapshot for all on itsodb global l grep Lock list Lock list memory in use Bytes 9280 In 6 2 2 Manual table maintenance on
227. ccessfully Note The catalog partition must be available when you issue the MIGRATE DATABASE It does not matter from which database partition you issue this command Compare the database configuration settings after the migration with the configuration settings but before the database is migrated a Database manager configuration settings b Database configuration parameter settings c Table spaces information d Application packages information You do not need to check the package information for system generated packages 4 2 4 Post migration tasks After migrating your DB2 servers you need to perform several post migration tasks to ensure that your DB2 servers perform as expected and at their optimum level 180 1 If you set the DIAGLEVEL database manager configuration parameter to 3 or higher as recommended in the pre migration steps reset this parameter to the value set before the migration If you changed your log space setting as recommended in Migration requirements on page 169 reset the LOGFILSIZ LOGPRIMARY and LOGSECOND database configuration parameters to the values that they had before the migration Ensure that the amount of log space that you allocate is adequate for your DB2 server Up and Running with DB2 on Linux Start up your database with ACTIVATE DATABASE and review the administration notification log or the db2diag log file to verify that all database services are running properly a
228. ce DMS table spaces Database Managed DMS table spaces are managed by DB2 At the creation of the table space you specify the container files or raw devices and their sizes Although the size is defined at the table space creation it can be extended or reduced later DB2 can also extend table spaces automatically as described in Automatic resizing of table spaces on page 99 Considerations for choosing DMS table spaces include gt You can split index data and long data into separate table spaces for tables that reside in DMS table spaces gt The size of a table space can be increased by adding or extending containers using the ALTER TABLE SPACE statement Existing data can be automatically rebalanced across the new set of containers to retain optimal I O efficiency gt DMS table spaces require more administrative overhead Work has to be performed on both Linux and DB2 levels when creating or extending DMS table spaces gt In general a well tuned set of DMS table spaces will outperform SMS table spaces Up and Running with DB2 on Linux Automatic resizing of table spaces DMS table spaces can be created with the option AUTORESIZE YES in order to enable the automatic resize feature By default this option is set to VO You can turn this feature on and off after you have created the table space Table spaces with this feature enabled will increase their size automatically up to the file system limit as the space is
229. ce Explain facility Explain command Use the explain command from the command line to get an access plan The following statement explains a SELECT query on the non indexed column on the EMPMDC table db2 EXPLAIN ALL WITH SNAPSHOT FOR select count from empmdc where expltest TEST We then use the explain command to format the output db2exfmt d sample e db2inst1 g TIC o explain out w 1 n s 0 The output file explain out contains the access path for the statement as well as other detailed information about the query processing Example 8 42 on page 465 shows an excerpt from the file with the access plan Up and Running with DB2 on Linux Example 8 42 Access path for an SQL statement Access Plan Total Cost 322 112 Query Degree 1 Rows RETURN 1 Cost 1 0 1 GRPBY 2 322 112 320 1000 TBSCAN 3 322 029 320 10000 TABLE DB2INST2 EMPMDC You can see that DB2 performs a table scan which takes a longer amount of time Adding an index on the column EXPLTEST allows DB2 to scan on the index which can improve the query performance Visual Explain You can start Visual Explain from the DB2 Control Center Visual Explain offers a graphical view for the access path To start Visual Explain from the Control Center in the explorer view right click the database that you want and select Explain Query as shown in Figure 8 5 on page 466 Chapter 8 Application development 465
230. ce container that you want to modify with the SET TABLESPACE CONTAINER command or in the wizard With Version 9 5 alternatively you can generate a redirected restore script from a backup image and modify it as needed The steps are 1 Use the restore utility to generate the redirected restore script The RESTORE DATABASE command must be called with the REDIRECT option and the GENERATE SCRIPT option 2 Edit the generated redirected restore script as required You can modify Restore options Automatic storage paths Container layout and paths 3 Run the modified redirected restore script In a partitioned database environment you have to perform these steps for each database partition because the table space container definitions might differ For our sample database ITSODB we change the location and the size of a table space using a redirected restore with a generated script Example 6 24 shows you first how we generate the scripts for our partitioned database Example 6 24 Prepare database and generate scripts for the redirected restore db2instl mensa db2home db2inst1 gt db2 connect to itsodb Database Connection Information Database server DB2 LINUXX8664 9 5 0 SQL authorization ID DB2INST1 Local database alias ITSODB db2inst1 mensa db2home db2inst1 gt db2 tvf tscrt sql Chapter 6 Administering databases 265 create tablespace TSDATA1 in IBMDEFAULTGROUP managed by database using file tablespa
231. ces db2inst1 itsodb NODEO000 TSDATA1 000 40M on dbpartitionnum 0 using file tablespaces db2inst1 itsodb NODEO001 TSDATA1 000 40M on dbpartitionnum 1 DB200001 The SQL command completed successfully db2inst1 mensa db2home db2inst1 gt db2 create table TAB1 id int not null primary key name char 10 in tsdatal DB200001 The SQL command completed successfully db2inst1 mensa db2home db2inst1 gt db2 insert into tabl values 1 Tina DB200001 The SQL command completed successfully db2instl mensa db2home db2inst1 gt db2 insert into tabl values 2 Jonas DB20000I The SQL command completed successfully db2inst1 mensa db2home db2inst1 gt db2 connect reset DB200001 The SQL command completed successfully db2inst1 mensa db2home db2inst1 gt db2 backup db itsodb on all dbpartitionnums to db2backup Part Result 0000 DB20000I The BACKUP DATABASE command completed successfully 0001 DB20000I The BACKUP DATABASE command completed successfully Backup successful The timestamp for this backup image is 20080206173239 db2inst1 mensa db2home db2inst1 gt db2_all lt lt 0 lt db2 restore db itsodb from db2backup taken at 20080206173239 redirect generate script jitsodb_node0000 clp DB20000I The RESTORE DATABASE command completed successfully mensa db2 restore db itsodb completed ok db2inst1 mensa db2home db2inst1 gt db2_all lt lt 1 lt db2 restore db itsodb from db2backup taken at 20080
232. chive db2inst1 and set read write permissions for the instance owner user ID so that DB2 can access the directory mkdir db2archive db2instl chown db2instl db2iadml db2archive db2instl 3 Turn on log archiving by updating the database configuration db2 update db cfg for itsodb using logarchmethl disk db2archive Note The command applies to both a single and a multi partitioned database environment DB2 9 5 provides a single view of all database configuration elements across multiple partitions You can update the database configuration across all database partitions by invoking the UPDATE DATABASE CONFIGURATION command against one database partition You no longer need to use the db2_all command 4 To verify use the following command db2_all db2 get db cfg for itsodb grep LOGARCHMETH1 You can also perform these steps through the DB2 Control Center 1 Right clicking the database name shows you the context menu Figure 6 4 on page 232 Chapter 6 Administering databases 231 All Systems All Databases Figure 6 4 Database context menu 2 Choosing Configure Database Logging opens the Wizard as shown in Figure 6 5 Figure 6 5 Configure Database Logging Wizard 232 Up and Running with DB2 on Linux 3 Choose Archive Logging and on the next page let DB2 automatically archive the log files You need to update the primary archive log path as shown in Figure 6 6 Configure Database Logging Wizard db2a
233. chmarks 2 bio informatics 3 block device 99 Copyright IBM Corp 2008 All rights reserved block IO 417 bookmarks 215 buffer pool 16 97 buffer pool size 384 built in function 429 business intelligence 2 Cc cache 19 catalog table space 97 catalog tables 97 cataloged system 94 central processing unit CPU 419 centralized database 12 chown 400 circular logging 123 228 CLI 4 CLP 303 cluster 3 COBOL 434 code page 95 column function 429 columns 16 command df 42 iostat 414 ipcs 31 rpm 34 sar 414 showmount 47 sysctl 31 vmstat 414 Command Line Processor 303 500 command option 415 420 command line tool 439 commands ar 420 db2top 386 ssh 93 communication 46 requirements 29 compact 28 61 66 80 configuration file 140 511 configuration parameters 141 archretrydelay 235 blk_log_dsk_ful 235 catalogcache_sz 141 dbheap 141 dft_degree 142 dft_monswitches 136 dftdbpath 136 diaglevel 123 136 180 188 399 diagpath 179 397 399 failarchpath 235 health_mon 356 instance_memory 137 intra_parallel 137 java_heap_sz 137 keepdari 433 keepfenced 433 logarchmeth1 228 234 logarchmeth2 228 234 logbufsz 141 logfilsiz 170 171 180 188 logprimary 180 188 logsecond 170 180 188 max_querydegree 137 maxfilop 141 mirrorlogpath 235 mon_heap_sz 136 notifylevel 398 numarchretry 235 sheapthres 136 sortheap 141 configuration task 95 console 215 contact group 358 contact management 358 content
234. ck in versions of your files Check out a shared project If you want to use a project that is checked in to a code repository you have to check it out to your local workspace In order to check it out you can switch to the related perspective for that repository For instance if you want to check out a project from a CVS repository switch to the CVS perspective by selecting Window Open Perspective Other In the Open Perspective panel select CVS Repository Exploring This perspective allows you to specify a repository location and check out a project from there After a project is checked out to your local workspace it is connected with that repository location and you can check in or synchronize your content at any time with the repository In that way all of your work is shared among your team members too 5 3 3 XML editing The Data Studio contains a powerful graphical XML and XML Schema Definition XSD editor A GUI tool is provided to guide you through the creation steps if you are unfamiliar with the XML and XSD syntax which helps both experienced and inexperienced application developers to create error free XML and XSD documents Example 5 1 shows the source of an XSD document Example 5 1 Example XSD document lt xml version 1 0 encoding UTF 8 gt lt schema xmlns http www w3 org 2001 XMLSchema targetNamespace http www example org TestSchema xmlns tns http www example org TestSchema elementFo
235. configuration parameters can be quickly and conveniently entered by using the command line processor Use GET DATABASE MANAGER CONFIGURATION to show current values Use UPDATE DATABASE MANAGER CONFIGURATIONUSING lt parameter gt to change current values Use RESET DATABASE MANAGER CONFIGURATION to reset all database manager parameters to their default values Use AUTOCONFIGURE to let DB2 determine the values Example 3 35 shows examples of DBM parameter changes Example 3 35 Example for DBM configuration change db2 get dbm cfg db2 update dbm cfg using DFT_MON_BUFPOOL on automatic db2 get dbm cfg show detail db2 autoconfigure using mem_precent 60 apply db and dbm 3 6 3 Database configuration 140 For allocation and control of system resources DB2 uses a separate configuration file for every database in a DB2 instance This file is named SQLDBCON and is stored in database_path DB2INSTANCE NODE0000 SQL00001 In a partitioned environment the SQLDBCON file exists in every database partition Therefore it is possible to have different settings for each partition To modify these database configuration DB cfg parameters use the Control Center or use the DB2 command line db2 update db cfg for lt database gt using lt parameter gt In a partitioned environment you must issue this command on each partition The UPDATE DB CONFIG command applies to all partitions If you want to apply it on a particular partition use the p
236. connections If you are running in a single partition you still have to migrate DAS to use the Control Center If you do not want to keep your existing configuration you can just drop the DAS and create a new one If you do not have a DAS in any database partition server create a new one You can find more details about DAS creation in Chapter 2 Installation on page 25 DAS migration The following steps show how to migrate a DAS from Version 8 or 9 1 to DB2 9 5 1 Log in as root user 2 Go to DB2DIR instance 3 Enter the command dasmigr Example 4 13 shows a dasmigr execution Example 4 13 The dasmigr command mensa opt ibm db2 V9 5 instance dasmigr SQL4407W The DB2 Administration Server was stopped successfully SQL4406W The DB2 Administration Server was started successfully DBI10701 Program dasmigr completed successfully Tools catalog database migration If you want to use your existing scripts and schedules that were created in Version 8 or Version 9 you must perform the following steps 1 Obtain the name of the instance and the tools catalog database through the db2 get admin cfg command see Example 4 14 Example 4 14 Get tools catalog information dpfusr1l gemini gt db2 get admin cfg Admin Server Configuration Tools Catalog Database TOOLSCAT_DB TOOLSDB Tools Catalog Database Instance TOOLSCAT_INST dpfusr1 Tools Catalog Database Schema TOOLSCAT_SCHEMA CC Scheduler User ID
237. covery plan in case of failure This section discusses migration requirements Figure 4 1 illustrates the migration roadmap You need to consider the entire DB2 environment to determine an optimal migration strategy ad Migrate DB2 servers t Migrate clients Test application and routines Successful Not successful Migrate applications and routines Are DB2 servers and clients No D Yes Migration complete Figure 4 1 Migration roadmap 168 Up and Running with DB2 on Linux 4 1 1 Migration requirements Make sure that your system satisfies the following software and space requirements prior to Version 9 5 migration gt Migration is supported from DB2 UDB Version 8 and DB2 9 1 If you have DB2 UDB Version 7 or earlier you need to migrate to DB2 UDB Version 8 before migrating to DB2 9 5 If you are running DB2 UDB Version 8 1 we recommend that you upgrade to DB2 UDB Version 8 2 first You can only migrate to a root installation of DB2 9 5 DB2 9 5 Enterprise Server Edition is only supported on 64 bit architectures Check the recommended and validated environment for DB2 9 5 at the following Web site http www ibm com software data db2 1inux validate Restoring full database offline backups from DB2 UDB Version 8 or DB2 Version 9 1 is supported However You cannot roll the logs from a previous level forward Perform hardware and operati
238. ction we discuss storage planning for DB2 data servers File systems A popular method for configuring disk space for DB2 on Linux is to use separate file systems to store and run DB2 File systems can be used by DB2 either as system managed storage SMS or as database managed storage DMS File systems have many benefits File systems can be distributed across a network and have network oriented authentication and replication capabilities which make them essential for a partitioned database system The operating system by default caches file data that is read from and written to disk This behavior of caching data at the file system level is reflected in the FILE SYSTEM CACHING clause of the CREATE TABLESPACE statement Because the database manager manages its own data caching using buffer pools the caching at the file system level is not needed if the size of the buffer pool is tuned appropriately In certain cases caching at the file system level and in the buffer pools causes performance degradation because of the extra CPU cycles required for the double caching To avoid this double caching most file systems have a feature that disables caching at the file system level This feature is generically referred to as non buffered I O On Linux this feature is commonly known as Direct I O or DIO The database manager supports this feature with the NO FILE SYSTEM CACHING table space clause When this is set the database manager automatically
239. d Health Center 00000 eee eee 354 7 1 1 Health indicator and Health Monitor 0 00 354 7 1 2 Monitoring with the Health Center 0000054 355 7 2 Memory Visualizer and Memory Tracker 0 000 eee eae 381 TS AOZO aiid cee ten ete de ee he ME AS Arora Tell AA A acho 386 7 3 1 db2top installation 0 0 0 eee 386 7 3 2 Monitoring with db2top in interactive mode 387 7 3 3 Running db2top in the background mode 391 7 4 Log files for troubleshooting 0 000 eee eee eee 397 7 4 1 DB2 administration notification log 0 eee eee 397 7 4 2 DB2 diagnostic log db2diag log cee eee eee 399 7 4 3 Operating system log 0 00 eee 401 7 5 DB2 Tools for troubleshooting 00 c eee eee 401 To apd e nEn Ps Re chao D E tie be de Ra 402 Tae OD ADO tng ANSE SD Ah lea E a Ae Sete e DEA AS 405 7 5 3 DB2 snapshot command 00 eee ee 409 M DA ADIS 2 ds seins alte EMO a Ea ate See aaa 412 7 58 db2SUppOMe iy ottanta ante tulae es erin eth dba eine weaed 413 7 6 Linux system monitoring toolS 000 0 eee 414 7 61 THE top UUM es ene er dante erot pete dale ded eee Peers 414 7 6 2 The vmstat command 0 0 0 ee ee 417 7 013 Sta a iets is ae dilnd See ele th ted bee a ete ass 419 7 6 4 Thesar command osser vari oiei VEE OEE E EE eae 420 7 6 5 Other system monitoring tools 0000 aaa
240. d installation requirement details refer to Quick Beginnings for IBM Data Server Clients GC23 5863 3 8 1 Installing IBM Data Server Client After you have verified the prerequisites specified in 2 1 Basic requirements on page 26 perform the following tasks to install the IBM Data Server Client 1 ak oO NM Insert and mount the product DVD Change to the directory where the DVD is mounted or the install image resides Run the db2setup command to start the DB2 Setup wizard Choose Install a Product when the DB2 launchpad opens Select the client that you want to install Follow the DB2 Setup wizard s instructions to install the client Chapter 3 Post installation tasks 153 Note With DB2 Version 9 5 you can install the IBM Data Server Client without root privileges The DB2 installer automatically creates and configures a non root instance during the non root installation Non root installation includes most of the functionality of root installation however there are differences and limitations for example the DB2 Control Center and the Configuration Assistant are not available See 2 3 1 Non root installation on page 60 for more information If you have not already created a Data Server Client instance during the installation you must create a Data Server Client instance using the following command as the root user In our case we create a DB2 Data Server Client instance called db2vs opt ibm db2 V9 5
241. d to use buffered inserts which reduce the messaging that occurs when data is imported resulting in better performance However only enable this option if you are not concerned about error reporting because details about a failed buffered insert are not returned Up and Running with DB2 on Linux Use the DB2 bind utility to request the buffered inserts capability The import package db2uimpm bnd must be rebound against the database by using the INSERT BUF option Refer to Example 6 50 Example 6 50 Enable INSERT BUF for IMPORT in a partitioned database db2inst1 mensa db2home db2inst1 gt db2 connect to itsodb Database Connection Information Database server DB2 LINUXX8664 9 5 0 SQL authorization ID DB2INST1 Local database alias ITSODB db2inst1 mensa db2home db2inst1 gt db2 bind sqllib bnd db2uimpm bnd insert buf LINE MESSAGES FOR db2uimpm bnd SQLO061W The binder is in progress SQLOO91N Binding was ended with 0 errors and 0 warnings For more information regarding using IMPORT such as using IMPORT with Large Objects XML data or identity columns refer to Data Movement Utilities Guide and Reference SC23 5847 and DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 6 3 3 Load data from files into database tables The load utility provides an efficient way to move a large quantity of data into new or existing tables The utility can handle most data types including XML large objects LOBs and u
242. data2 DB200001 The SQL command completed successfully db2instl puget gt db2 get snapshot for database on itsodb grep i storage Number of automatic storage paths 2 Automatic storage path database datal Automatic storage path database data2 Note You can get more information about the automatic storage feature in the Information Center in the Automatic storage section http publib boulder ibm com infocenter db21 uw v9r5 topic com ibm db2 uw a dmin dbobj doc doc c0052484 htm1 3 2 3 Linux specific configuration In order to access DB2 each Linux user must set up their own Linux environment During the creation of an instance DB2 creates a subdirectory named sqllib in the instance home directory INSTHOME In this directory there are important files such as db2nodes cfg db2profile and userprofile These files are used to set up the DB2 environment To set up a user environment to use DB2 every time that the user logs in to the Linux system add the following command to the user profile under the user s home directory INSTHOME profile INSTHOME sq l1lib db2profile The parameter db2profile contains all of the settings that allow users to work with DB2 databases Do not modify this file because db2profile will be replaced after installing a fix pack If you want to make changes that are specific to your environment make changes in INSTHOME sqllib userprofile which is called by Chapter 3 Post installation tasks
243. database environments we recommend that you create a separate DB2 home file system on one of the machines in the cluster to be used as the instance home directory This file system is to be shared among all machines in the cluster via NFS that is NFS exported from the NFS server machine and NFS mounted on the remaining machines In our setup we created the file system export db2home with a mount point db2home gt We also recommend that you create a separate file system for storing databases For partitioned database systems there needs to be a separate database file system on each physical system that participates in the partitioned database In our setup we created a file system called database with mount point database gt For performance or availability reasons we recommend that you avoid putting user data on the catalog node When restoring the catalog node the restore is faster when there is no data on this node gt We also recommend that you create separate partitions for the primary copy of DB2 logs DB2 mirrored logs and DB2 temporary table spaces this design Chapter 2 Installation 43 is discussed in more detail later in this section In addition you might want to create a separate file system for user table spaces in order to separate them from the database files This configuration is commonly used in many production environments Table 2 9 is an example of one possible configuration We will use this system
244. database manager the DB2 product is ready to use immediately after the fix pack installation To apply a DB2 fix pack perform the following steps 1 Download the code of the latest fix pack from http www ibm com software data db2 udb support htm 2 Carefully read the readme file and release notes and perform all of the necessary tasks 3 Install the DB2 fix pack If you are running a non root installation and root based features are enabled you must rerun db2rfe command each time that a fix pack is applied in order to re enable those features For details about a non root installation see Chapter 2 Installation on page 25 Chapter 4 Migration and fix packs 195 196 Up and Running with DB2 on Linux IBM Data Studio IBM Data Studio is a comprehensive data management solution It empowers you to effectively design develop deploy and manage data databases and database applications throughout the data management life cycle by utilizing a consistent and integrated user interface In this chapter we briefly introduce IBM Data Studio We cover the following topics gt Introduction A short introduction about Data Studio gt Installation This section describes the installation steps for Data Studio We briefly discuss how to migrate projects from the Developer Workbench into Data Studio gt Features and functions In this section we briefly introduce the features and functions of Data Studio Copyright
245. db2inst1 mensa db2backup datamove gt db2 load query table itemload Tablestate Normal Another way to monitor the LOAD utility is by using the LIST UTILITY command Example 6 58 shows the output which was taken when loading the data into the table ITEMLOAD The table resides on two database partitions Example 6 58 Using LIST UTILITIES to monitor LOAD status db2inst1 mensa db2backup datamove gt db2 list utilities ID Type Database Name Partition Number Description COPY NO DB2INST1 ITEMLOAD Start Time State Invocation Type ID Type Database Name Partition Number 322 Up and Running with DB2 on Linux 136 LOAD ITSODB 0 OFFLINE LOAD DEL AUTOMATIC INDEXING REPLACE 02 11 2008 15 57 02 886822 Executing User 88 LOAD ITSODB 1 Description COPY NO DB2INST1 ITEMLOAD Start Time State Invocation Type OFFLINE LOAD DEL AUTOMATIC INDEXING REPLACE 02 11 2008 16 00 40 095780 Executing User db2inst1 mensa db2backup datamove gt db2 list utilities show detail ID Type Database Name Partition Number Description COPY NO DB2INST1 ITEMLOAD Start Time State Invocation Type Progress Monitoring Phase Number Description Total Work Completed Work Start Time Phase Number Current Description Total Work Completed Work Start Time Phase Number Description Total Work Completed Work Start Time ID Type Database Name Partition Number Description COPY NO DB2INST1 ITEMLOA
246. db2sampl 425 db2start 120 db2stop 120 db2undgp 175 DBI 435 debugger 470 delta backup 230 delta database backup 241 deploy 198 Design Advisor 468 Developer Workbench 210 diagnostic log file 402 digital signature algorithm 54 disable evaluation options 370 disk capacity 42 disk I O 16 414 disk requirements 27 distribution key 361 DMS 361 DMS table space 361 document ID 456 domain name server 29 DRDA 4 driver 433 driver type 451 DSA 54 DSS 13 dynamic size 27 dynamic SQL 389 E Eclipse 198 e commerce 438 editor tool bar 215 embedded SQL 441 engine processes 497 enterprise applications 2 ER diagram 199 220 errorlog 215 ESQL 441 evaluation option 370 EXECUTE privilege 175 explain 181 ext2 41 ext3 41 42 extension 439 external procedure 431 F failover 4 Fast Communication Manager 106 fast communication manager 6 FCM 106 FCP 41 fdisk command 99 fenced use 433 file system 48 file system caching 97 flexibility 2 Fortran 434 framework 224 front end 440 fstab file 46 full backup 229 full offline database backup 240 G gateway 2 12 29 global snapshot 388 gnome system monitor 424 H health indicator 354 360 health issues 354 health monitor 354 health monitor alarm 398 health_mon 354 355 heterogeneous environment 11 high availability 4 14 high performance computing applications 3 high SMP systems 24 host IP address 29 host trust relationship 58 host based a
247. de which log files are required to guarantee the consistency of an online backup Example 6 11 on page 241 provides a sample of a full online backup Example 6 9 Full online backup to disk with included logs db2instl mensa gt db2 backup db itsodb online to db2backup include logs Backup successful The timestamp for this backup image is 20080204090001 gt Table space A table space backup allows you to back up only the specified table spaces In Example 6 10 we back up only table space TBSPDMS_0 Example 6 10 Table space backup online TBSPDMS_0 db2inst1 mensa gt db2 backup db itsodb tablespace TBSPDMS 0 online to db2backup Backup successful The timestamp for this backup image is 20080204090637 Up and Running with DB2 on Linux gt Full incremental An incremental backup saves backup time and resources Example 6 11 provides an incremental backup example Example 6 11 Incremental backup to disk db2inst1 mensa gt db2 backup db itsodb online incremental to db2backup Backup successful The timestamp for this backup image is 20080204091101 gt Delta backup Example 6 12 shows the delta database backup after taking a full database backup Example 6 12 Delta backup to Tivoli Storage Manager db2inst1 mensa gt db2 backup db itsodb online incremental delta use tsm Backup successful The timestamp for this backup image is 20080204091912 Note To enable incremental or delta backup you need to set th
248. difference between the rah command and the db2_al1 command is that the specified commands in rah are executed only one time per physical host which is important if you have several logical partitions on one physical system Tip The command typeset Z4 DB2NODE returns a four digit number for every partition defined in db2nodes cfg for example O will be 0000 1 will be 0001 Chapter 3 Post installation tasks 113 Create database Example 3 15 shows the DDL to create multi partitioned database This DDL is almost identical to the DDL to create a single partitioned database that was shown in Example 3 12 on page 112 except that we have introduced the usage of the N variable which substitutes the partition number Example 3 15 Create a partitioned database crdb sql CREATE DATABASE ITSODB AUTOMATIC STORAGE NO ON database ALIAS ITSODB USING CODESET UTF 8 TERRITORY US COLLATE USING SYSTEM PAGESIZE 4096 TEMPORARY TABLESPACE MANAGED BY SYSTEM USING db2temp db2inst1 NODE000 N ITSODB TEMPSPACE1 WITH Lab database for ITSO The argument N blank N is a database partition expression that can be used anywhere in the storage path You can specify multiple database partition expressions The partition expression is terminated by a space character If there is no space character in the storage path after the database partition expression it is assumed that the rest of the string is part of the expression Table 3 1 sh
249. dit the shosts equiv file mensa mensa itsosj sanjose ibm com gemini gemini itsosj sanjose ibm com Edit the ssh_known_hosts file The ssh server host system needs to have access to the public key of the ssh client host For host based authentication the trust mechanism looks for public keys in the ssh_known_hosts file The ssh_known_hosts file is found in the etc ssh directory on Linux If this file does not yet exist create the file Ensure that it is owned by the root user and only allows user read write access and group other read access See Example 2 9 Example 2 9 Create ssh_known_hosts and modify the file properties cd etc ssh touch ssh_known_hosts chown root root ssh_known_hosts chmod 644 ssh_known_hosts Add unqualified host name fully qualified host name and IP address of the client machine to the ssh_known_hosts file as shown in Example 2 10 and Example 2 11 on page 56 You can use the ssh keyscan utility to populate this file Example 2 10 Update the ssh_known_hosts file for RSA encryption cd etc ssh ssh keyscan t rsa mensa mensa itsosj sanjose ibm com 9 43 86 90 gt gt ssh_known_hosts ssh keyscan t rsa gemini gemini itsosj sanjose ibm com 9 43 86 94 gt gt ssh_known_hosts Chapter 2 Installation 55 56 Example 2 11 Update the ssh_known_hosts file for DSA encryption cd etc ssh ssh keyscan t dsa mensa mensa itsosj sanjose ibm com 9 43 86 90 gt gt ssh_known_hosts ssh keys
250. do the version recovery Note In a partitioned database environment you must restore all database partitions and the backup images that you use for the restore database operation must all have been taken at the same time db2_all db2 restore db itsodb from db2backup taken at 20080201170437 Full database restore from an online backup Version recovery of a database using a backup that was taken online means that you restore the database to the point in time when the online backup was finished During the online backup transactions were still running against the database Therefore the log files that were written during the backup time need Chapter 6 Administering databases 255 to be applied After the restore command is run successfully you have to roll forward to the end of backup point in time You can use the following V9 5 command to roll forward db2 rollforward db itsodb to end of backup and stop If you used the backup command with the INCLUDE LOGS clause you can specify the LOGTARGET option within the restore command Example 6 21 shows how this works for a single partition database Example 6 21 Version recovery with online backup and included logs db2instl mensa gt db2 restore db itsodb from db2backup taken at 20080206143831 logtarget db2backup logs DB20000I The RESTORE DATABASE command completed successfully db2inst1 mensa gt db2 rollforward db itsodb to end of backup overflow log path db2backup lo
251. doce_install command To install the DB2 Information Center manually use the doce_install command 1 Log in as root 2 Decide where you want to install the documentation In our environment we created a directory called documentation which is located in the db2home directory for example db2home documentation 3 Insert and mount the DB2 Information Center DVD 4 Use the doce_install command to install DB2 Information Center The syntax of the doce_install command is doce_install b install_path p doce n L language b install path Specifies the path where the DB2 Information Center is to be installed The default installation path is opt ibm db2ic V9 5 This parameter is mandatory when the n parameter is specified n Specifies non interactive mode L language Specifies national language support The default is English To install multiple languages at the same time this parameter can be specified multiple times For example to install both English and Simplified Chinese specify L EN L CN For example enter the doce_install command using the following format doce_install b db2home documentation p doce n L EN L CN Note You can use the doce_uninstall command to uninstall the DB2 Information Center 90 Up and Running with DB2 on Linux Post installation tasks In the previous chapter we provided a detailed process of installing DB2 Version 9 5 on Linux In this chapter we discuss post install
252. dp7 O workspace metadata plugins com ibm datatools db2 routines deploy ui bid 1202419779153 DB2INST1 EMPSALARY Deploy for debug successful Figure 8 35 Output of the deployment action Now the code is deployed on the server 1 The procedure is ready to be run In the Data Project Explorer view select DataProject Stored Procedures EMPSALARY right click EMPSALARY and then select Run as shown in Figure 8 36 v SL Srp b gt EmpSalary sq Y Stored Procedures T4 EMPSALA 5 Open Deploy C User Defined SPY amp C3 Web Services P v XML Delete wWsSDL g Export 3 XML Doc Debug CI XML Schd Bun Figure 8 36 Run the procedure 2 You will be asked for the parameter as shown in Figure 8 37 on page 489 Enter the value 37000 488 Up and Running with DB2 on Linux m 22 Specify Parameter Values EMPSALARY Specify the parameter values that you want to use for running or debugging the stored procedure You can set selected strings or user defined types to null INTEGER Set to nun Figure 8 37 Enter the run parameter The output can be seen in the Data Output view Refer to Figure 8 38 Properties Tasks Problems Error Log Model Report Bg Data Output 2 Bookmarks m fale Gbest Nave SAMPLE DB2INST1 EMPSALARY IN SALARY INTEGER aje lt 2 Success Run EMPSALARY Messages
253. e DB2COMM tcpip Figure 3 28 Change registry variables Multi page file allocation For system managed table spaces SMS we recommend that you enable multi page file allocation It reduces the time needed for formatting new pages To enable this parameter issue the command db2empfa for every database Exclusive access is needed because in existing table spaces all empty pages will be filled up to the last extent 148 Up and Running with DB2 on Linux To check whether all empty pages are filled up to the last extent issue the command db2 get db cfg for lt dbname gt grep Multi page Multi page file allocation enabled YES In a multi partition environment issue db2empfa on every database partition 3 7 Security In this section we briefly discuss the security in DB2 We introduce security in the Linux instance database and network levels For detailed information about this subject refer to gt DB2 Security and Compliance Solutions for Linux UNIX and Windows SG24 7555 gt Database Security Guide SC23 5850 gt The Information Center under Database fundamentals Security Security on the Linux level On the Linux level the security is managed in terms of users and groups A user has one primary group and can be a member of several more groups The database instance is more or less a dedicated user ID which runs all DB2 processes that are part of this instance The database instance offers access f
254. e Note If you want to perform a redirected restore from one machine to another machine using db2adut1 and Tivoli Storage Manager you need to set the logarchopt1 and vendoropt database configuration parameters You can refer to a detailed sample under the section Recovering data using db2adutl in Chapter 11 Recover overview of the Data Recovery and High Availability Guide and Reference SC23 5848 6 1 7 Recovering a dropped table sample scenario It is possible that a user dropped a database table by mistake and that the table data needs to be recovered In this case DB2 provides a dropped table recovery feature In this section we demonstrate how to recover a dropped table through the table space restore The table space will be restored from an older backup image and during the roll forward of the database the dropped table data will be exported To set up the scenario environment we first alter the table space TSDATA1 to allow table space level recovery take a database backup and drop table tab1 which is in table space TSDATA1 Refer to Example 6 28 Example 6 28 Prepare for dropped table recovery db2inst1 mensa gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2instl mensa gt db2 alter tablespace TSDATA1 dropped table recovery on DB200001 The SQL command completed successfully db2inst1 mensa gt
255. e ssh directory generate a public key private key pair Example 2 17 shows how to generate a public key private key pair for RSA 5 Refer to Creating users on page 51 Chapter 2 Installation 57 58 Example 2 17 Generate an RSA encrypted key pair cd ssh ssh keygen t rsa You also can generate a DSA key pair Example 2 18 shows how to generate a public key private key pair for DSA Example 2 18 Generate a DSA encrypted key pair ssh keygen t dsa Whenever prompted for input press Enter to accept the default value You then are prompted to enter a passphrase In our environment we do not want a passphrase so we press Enter twice Two new files are generated in the ssh directory id_rsa the private key and id_rsa pub the public key for RSA encryption In a similar manner name files are generated for DSA encryption id_dsa the private key and id_dsa pub the public key Enable the key pair Example 2 19 shows the commands to enable the RSA key pair Example 2 19 Enable the RSA key pair cd ssh mv id_rsa identity chmod 600 identity cat id_rsa pub gt gt authorized_keys chmod 644 authorized_keys rm id_rsa pub Example 2 20 shows the commands to enable the DSA key pair Example 2 20 Enable the DSA key pair cd ssh mv id_dsa identity chmod 600 identity cat id_dsa pub gt gt authorized_keys chmod 644 authorized_keys rm id_dsa pub Set up the
256. e DB2 v9 5 0 0 s071001 LINUXAMD6495 and Fix Pack 0 Product is installed at opt ibm db2 vV9 5 Optionally you can rename the db2diag log using the db2diag A command to refresh the db2diag log for easy error identification later Move any existing dump files trap files and alert log files in the directory indicated by the DIAGPATH parameter to another directory Migrate all databases to Version 9 5 format Log in as the instance owner and start the instance using db2start as shown in Example 4 10 Example 4 10 Starting the instance dpfusr1 mensa sqllib db2dump gt db2start 01 30 2008 17 15 27 O 0 SQL1063N DB2START processing was successful 01 30 2008 17 15 28 1 0 SQL1063N DB2START processing was successful SQL1063N DB2START processing was successful Chapter 4 Migration and fix packs 179 Run the db2 migrate database command to migrate the database The command syntax is db2 migrate database lt database_alias gt user lt user_name gt using lt password gt The variable database_alias represents the database that you are migrating user_name represents the name under which the database is migrated and password is that user s password The user and password options are not required if you want to use the current user for the command See Example 4 11 Example 4 11 Migrating the database dpfusr1l gemini gt db2 migrate database dpfsamp DB20000I1 The MIGRATE DATABASE command completed su
257. e TRACKMOD database configuration parameter to ON db2 update db cfg for itsodb using TRACKMOD ON When the TRACKMOD database configuration parameter is set to ON you need to do a full database backup one time before starting an incremental or delta backup Backing up partitioned databases In a partitioned database environment there are three possible ways to back up the database gt Back up each database partition one at a time gt Use the db2_all command with the BACKUP DATABASE command to back up all the database partitions that you specify gt Runa single system view SSV backup to back up some or all of the database partitions simultaneously Backing up each database partition one at time is time consuming and error prone Using the db2_al1 command to issue the backup database command on all of the database partitions simplifies the process and saves time However because the database partition containing the catalog cannot be backed up simultaneously with the non catalog database partitions you still have to back up the catalog database partition first and then back up the rest of the database partitions Chapter 6 Administering databases 241 242 Assuming that database partition 0 is the catalog partition the commands are db2_all lt lt 0 lt db2 backup db itsodb to db2backup db2_all lt lt 0 lt db2 backup db itsodb to db2backup Whether you back up the database partitions one at a time or by using
258. e XML data natively as a column in a DB2 database This seamless integration of XML with relational data speeds application development improves search performance with highly optimized XML indexes and is flexible because both SQL and XQuery can be used to query XML data In DB2 9 5 enhancements including non unicode XML database support are added Data compression enhancements Data compression dictionaries can be automatically created during data population operations on tables for which you have defined the COMPRESS attribute which means that DB2 can automatically compress the data without DBA intervention Database backup enhancements DB2 9 5 can automatically delete backup images load copy images and old log files that are no longer needed for recovery There are new options for automated backup such as compression incremental and delta backups and log files in backup In addition rolling forward to minimum recovery time is possible now with the new TO END OF BACKUP parameter Workload Manager The workload management features help you to identify manage and monitor data server workloads These features provide the first workload management solution truly integrated into the DB2 data server Support for identity assertion enables you to provide workload management for individual users or groups in a multi tier application environment By associating workload definitions to service classes each unique workload can be prioritized usi
259. e ampersand character amp to run the command in the background By using method two only the user who uses the Xauthority file is allowed to access the X server If you connect from a remote client you can adjust the steps for method one or method two accordingly However in that case it is easier to use the ssh command as demonstrated in Example 3 3 Example 3 3 Use SSH for db2cc db2instl vmsuse gt ssh X db2inst1l puget Last login Thu Jan 31 16 55 09 2008 from 9 125 7 139 db2instl puget gt db2cc amp 1 28832 db2inst1l puget gt The option X instructs ssh to tunnel the X11 port to the local system set the DISPLAY correctly and to perform the Xauthority authentication If you have set up the SSH authentication properly you do not need to provide a password If you come from a Windows system and you use Exceed or Cygwin as a local X server you can use putty The putty program has an option which allows X forwarding After you start the Control Center you are asked first to specify the view options See Figure 3 1 on page 94 Select Advanced In this chapter we provide our demonstrations in that view Chapter 3 Post installation tasks 93 facli a Figure 3 1 Choose the view in db2cc Figure 3 2 shows the main window of the Control Center From this window you can view all the cataloged systems and databases AN Control Center 3 Control Center Ds All Systems O All Databases 0 SAM
260. e product Sie i mT iw Software Development Platform Language selection RA Ed IBM Data Studio The IBM Data Studio is a rich and robust desktop application that allows database professionals to perform database design development deployment and management tasks Using this application you can develop and test routines deploy data centric web services create and run SQL and XQuery queries and develop Java applications that access databases or in memory data In addition you can perform database administration tasks such as creating and altering database objects and managing privileges Install 1BM Data Studio Installation Guide Release Notes Figure 5 2 Installing IBM Data Studio 5 In the Install Packages panel Figure 5 3 on page 202 the IBM Installation Manager is also selected if it has not been installed in the system yet Chapter 5 IBM Data Studio 201 202 T IBM installation Manager Sle Install Packages Select the packages you want to install Installation Packages viv lt V IBM Data Studio Version 1 1 1 C Show all versions O Status Vendor IBM a License Key Type Check for Other Versions and Extensions Next gt Cancel Figure 5 3 Select install package 6 On the Licenses panel accept the license agreement 7 The Location tab is for specifying the locat
261. e DIAGPATH can also be changed from the Control Center From All Systems gt lt HOSTNAME gt Instances right click db2inst1 select Configure Parameters Change the DIAGPATH value in the DBM Configuration pane Figure 3 13 Note For a partitioned database use the same command The UPDATE DBM CONFIG command applies to all nodes because the home directory is shared by an NFS mount F DEN Configuration O m YMSUSE db2inst1 Select the value field of a parameter to change its value DIAGLEYEL INDEXREC During database restart NOTIFYLEVEL 3 YV Environment 78 of 78 items displayed gt gt a Default View 4 view Hint he fully qualified path for DB2 diagnostic information Range valid path sHomieommand Figure 3 13 Change DIAGPATH in the Control Center 3 5 Add database partition If the load on a partitioned database becomes too high you can add a partition to take advantage of the parallel processing This section describes these steps In a partitioned database environment you can use the add dbpartitionnum command line processor CLP command or use the db2start command with the option dbpartitionnum to add a logical database partition to a database that is 124 Up and Running with DB2 on Linux already populated with data The add dbpartitionnum command has two options gt LIKE DBPARTITIONNUM gt WITHOUT TABLESPACES The add dbpartitionnum command creates the d
262. e SNAP_GET_UTIL table function Used in conjunction with the SNAPUTIL_PROGRESS administrative view or the SNAP_GET_UTIL_PROGRESS table function you can retrieve the same information that you can retrieve with the LIST UTILITIES SHOW DETAIL command Example 6 15 on page 244 shows how to use the administrative views Chapter 6 Administering databases 243 244 Example 6 15 Administrative views to monitor the backup db2inst1l mensa gt db2 select UTILITY_TYPE substr UTILITY_DESCRIPTION 1 15 UTILITY_STATE DBPARTITIONNUM from SYSIBMADM SNAPUTIL UTILITY_TYPE 2 UTILITY_STATE DBPARTITIONNUM BACKUP online db EXECUTE BACKUP online db EXECUTE 1 2 record s selected db2inst1 mensa gt db2 select SNAPSHOT_TIMESTAMP UTILITY_STATE PROGRESS _START_TIME PROGRESS TOTAL_UNITS PROGRESS COMPLETED UNITS DBPARTITIONNUM from SYSTBMADM SNAPUTIL_PROGRESS SNAPSHOT_TIMESTAMP UTILITY_STATE PROGRESS_START_TIME PROGRESS _TOTAL_UNITS PROGRESS _COMPLETED_UNITS DBPARTITIONNUM 2008 02 21 14 28 43 442266 EXECUTE 2008 02 21 14 28 40 181510 304720105 88446673 0 2008 02 21 14 28 45 099408 EXECUTE 2008 02 21 14 28 41 835055 224002009 220510145 1 2 record s selected Check the backup image You can use db2ckbkp to test the integrity of a backup image and to determine whether the image can be restored Example 6 16 shows how to use the tool to verify a backup image Example 6 16 db2ckbkp output db2inst1 mensa db2backup gt db2ckbkp ITSODB
263. e Start menu Take the default or choose another location for the workspace as shown in Figure 8 11 on page 473 When you open a workspace for the first time the Data Studio shows a help window Closing the help window will lead you to the Select a workspace panel 472 Up and Running with DB2 on Linux a O 3 Workspace Launcher Select a workspace IBM Data Studio Developer stores your projects in a folder called a workspace Choose a workspace folder to use for this session home d b2inst1 1BM rationalsd p7 O workspace E Use this as the default and do not ask again Figure 8 11 Workspace selection in Data Studio To develop an application 1 Start by setting up a project Switch to the Data Perspective by selecting Window Open Perspective Data if you are not already there We create a Data Development Project by selecting File gt New Data Development Project We name it DataProject and take all of the default values as shown in Figure 8 12 Click Next F D 2 New Data Development Project Data Development Project Specify a basic definition for the new project Use the project to store a set of objects that can be deployed Project name l DataProject Use authorization ID as current schema Specify current schema in SQL format Current schema Omit current schema in generated SOL statements Figure 8 12 Create Project 2 Next we get to the connecti
264. e connect command which is used with the SQL requests in the program 4 Use SQL statements to manipulate and retrieve data in the database In most cases you need install at least the IBM Data Server Client to develop software Chapter 8 Application development 433 8 3 1 Perl In addition to the programming languages that are described in this section DB2 also supports application development for gt ADO NET support Refer to Developing ADO NET and OLE DB Applications SC23 5867 gt ODBC Refer to Call Level Interface Guide and Reference Volume 1 SC23 5844 and Call Level Interface Guide and Reference Volume 2 SC23 5845 gt OLD DB Refer to Developing ADO NET and OLE DB Applications SC23 5867 gt COBOL Refer to Developing Embedded SQL Applications SC23 5852 gt Fortran Refer to Developing Embedded SQL Applications SC23 5852 gt REXX Refer to Administrative API Reference SC23 5842 gt Ruby Ruby on Rails Refer to the Information Center by selecting Database application development Database applications Ruby on Rails Here we introduce Perl programming on DB2 and describe how to set up a Perl application development environment on DB2 for Linux Perl overview Perl is a popular general purpose programming language that is freely available on Linux It was originally developed for text manipulation but it is now used for a wide range of tasks including system administration Web development
265. e data into a multiple database partition table Example 6 53 on page 315 If you try to load a source file in IXF format to a database partitioned table directly it results in error SQL3004N This error means that the filetype parameter is invalid because IXF files cannot be used to load into a table spanning multiple database partitions Up and Running with DB2 on Linux Example 6 53 Load data from CURSOR into a database partitioned table db2inst1 mensa db2backup datamove gt db2 load from item ixf of ixf replace into itemload SQL3004N The filetype parameter is not valid db2inst1 mensa db2backup datamove gt db2 declare mycursor cursor for select from item db2inst1 mensa db2backup datamove gt db2 load from mycursor of cursor replace into itemload copy yes to db2backup datamove copydata Agent Type Node SQL Code Result LOAD 000 00000000 Success LOAD 001 00000000 Success PARTITION 001 00000000 Success RESULTS 2 of 2 LOADs completed successfully Summary of Partitioning Agents Rows Read 3000000 Rows Rejected 0 Rows Partitioned 3000000 Summary of LOAD Agents Number of rows read 3000000 Number of rows skipped 0 Number of rows loaded 3000000 Number of rows rejected 0 Number of rows deleted 0 Number of rows committed 3000000 Options for loading table data into partitioned databases In a multi partition database large amounts of data are located across many database partitions Distribu
266. e database GITAGEN Figure 3 7 Specify the storage path 4 Click Next and you see Figure 3 8 omea Wiaieiej tries Biss yaesicin 2 Figure 3 8 Specify the locale 110 Up and Running with DB2 on Linux 5 Click Next 6 Summary Figure 3 9 Here you can review your settings view or save the create database command Click Finish to finally create the database Figure 3 9 Database wizard summary page When you have created the database the Control Center window appears as shown in Figure 3 10 Expand the database to view the database objects such as table spaces containers tables and so on 3 Control Center E All Systems B All Databases O sample G All systems m a ITSODB All Databases Figure 3 10 Database created Command line The command that was used to create the database is shown in Example 3 11 on page 112 Chapter 3 Post installation tasks 111 Example 3 11 Create database statement with automated storage ON CREATE DATABASE ITSODB AUTOMATIC STORAGE YES ON database DBPATH ON database ALIAS ITSODB USING CODESET UTF 8 TERRITORY US COLLATE USING SYSTEM PAGESIZE 4096 WITH Lab database for ITSO The script in Example 3 11 is a direct output of the wizard and can be used instead of the Create Database Wizard to create the same database If you want to control where to place your container files for the table spaces Example 3 12 shows an example of a CREATE DATABASE
267. e eee 120 3 4 2 Change the archive log path n unana 0000 eee ee 123 3 4 3 Change the path for db2diag log 0000 0 eee eee 123 3 5 Add database partition 0 ee eee 124 3 6 DBZ confor atoes ie 4 08 2 04 ye ea eed hea ea Wee 132 3 6 1 STMM Self tuning memory management 133 3 6 2 Database manager configuration parameters 136 3 6 3 Database configuration 0 0 00 cece ee 140 3 6 4 DB2 registry and environment variables 146 37 SOCUMLY siete based t a Mo a Aled aed 2 gale lees ek Dee aed a 149 3 8 Client configuration 0 0 00 tee 152 3 8 1 Installing IBM Data Server Client 00 000 5 153 3 8 2 Configuring the IBM Data Server Client 154 3 9 Configuring licensing 0 00 eee 159 3 9 1 DB2 License Center 0000 c eee eee 160 39 2 dO2NCM 1OOM esii a ce ite een tp ie eee Ghee nie ete 163 Chapter 4 Migration and fix packs 0000000 2 euee 167 4 1 Migration planning saasaa aaaeeeaa 168 4 1 1 Migration requirements 0 0 00 cee ee eee 169 4 1 2 Planning considerations 2 00 0 eee 171 Up and Running with DB2 on Linux 4 1 3 Migration test consideration 0 000 eee eee 172 4 2 Migrating multi partitioned database 2 eee eee 173 4 2 1 Pre migration taskS 1 2 00 cece eee 173 4 2 2 Install DB2 Version 9 5 0 0 ee 178
268. e predefined actions for example running a task You can use DB2 commands or APIs to retrieve health information from the Health Monitor allowing you to integrate DB2 Health Monitoring with existing system wide monitoring solutions 7 1 2 Monitoring with the Health Center The Health Center provides the graphical interface to the Health Monitor You use it to configure the Health Monitor to define the threshold values for the desired health indicators and related activities when the threshold values are exceeded for example a notification to the database administrator DBA or the execution of a follow up task You can also use Health Center to view the rolled up alert state of your instances and database objects Using the Health Monitor s drill down capability you can access details about current alerts and obtain a list of recommended actions that describe how to resolve the alert You can start the Health Center by selecting Health Center from the Tools menu within any DB2 GUI tools where the Tools menu is available or by executing the command db2hc from the Command Line Processor CLP Activating the Health Monitor The Health Monitor is activated by default and if it is stopped for any reason you can reactivate it by using Health Center or using DB2 CLP commands When the Health Monitor is stopped because the HEALTH_MON parameter in the database manager configuration DBM CFG is OFF the Start Health Monitor menu item will
269. e recommend that you place the secondary log path on a physically separate disk Another related parameter is BLK_LOG_DSK_FUL This database configuration parameter can be set to prevent disk full errors for the transaction when DB2 cannot create a new log file in the active log path because of a file system full condition If the parameter is set to YES DB2 will attempt to create the log file every five minutes until it succeeds Note For a detailed overview of the configuration parameters for database logging refer to Data Recovery and High Availability Guide and Reference SC23 5848 Chapter 6 Administering databases 235 6 1 2 Recovery history file 236 DB2 log manager and the DB2 utilities such as BACKUP RESTORE LOAD EXPORT or REORG write detailed information into the recovery history file In a multi partitioned database this file exists in every database partition To see the entries in the recovery history file use the LIST HISTORY command Example 6 2 illustrates a sample output with the backup information It shows the backup timestamp and the log files that were active while the backup was taken Example 6 2 Backup history db2instl mensa gt db2 list history backup all for itsodb List History File for itsodb Number of matching file entries 2 Op Obj Timestamp Sequence Type Dev Earliest Log Current Log Backup ID B D 20080201170437001_ F D 0000000 L0G S0000000 LOG Contains 2 tablespace s 00001 SYS
270. e spaces requires more design implementation and maintenance work How many table spaces must be defined and how the table spaces are placed on the disks depends on the complexity and requirements of the application Chapter 3 Post installation tasks 97 98 SMS table spaces System Managed SMS table spaces are handled by the underlying operating system which is Linux in our case At the creation of the table space you specify directory names as containers Here are considerations for choosing SMS table space gt The disk space is not allocated until it is used gt It is easy to increase the SMS table spaces You only have to increase the underlying file system space DB2 will use it automatically gt Because of the previous two reasons it is a good practice to use an SMS table space for the temporary table space gt You cannot add or delete containers which can be an issue if you want to enhance the parallel I O performance by adding another container on a separate physical disk gt You might reach file system related limits with the file size of the files created by the database in the SMS managed file systems gt The table space is full if one of the containers is full gt Creating an SMS table space requires less initial work because you do not have to predefine the container sizes gt You cannot split table index and long data into separate table spaces for tables that reside within an SMS table spa
271. e the V option in the command line to specify a default schema for explains Up and Running with DB2 on Linux BMmOB2INST1 ITS Figure 7 32 Query text window 7 3 3 Running db2top in the background mode The db2top background mode provides you with an automatic performance analysis capability or data collection for analysis using Microsoft Excel Analyzing the db2top data using Microsoft Excel You can run db2top in background mode and analyze the data later using Microsoft Excel When using db2top with the b command option db2top will display information in comma separated value CSV format The db2top tool provides an Excel report tool called db2top Reports which is a macro for you to use to build graphical reports The db2top Reports macro is in the sample Excel file db2top x s that is located in the samples directory after unzipping db2top 2 0 bin zip To use db2top Reports copy db2top xls to a working directory on a Windows platform and double click it to open Select Enable Macros db2top Reports is presented for you to analyze db2top data refer to Figure 7 33 on page 392 Chapter 7 Monitoring and troubleshooting DB2 391 M db2top Reports V0 3 pB2 4 Generate Unix script to capture db2top data Generate Clear graphics Build graphics Save workbook Help Run db2top in background mode db2top b to capture data in csv format press the Generate button to genera
272. e time by using the new single system view SSV backup Refer to 6 1 DB2 database backup and recovery on page 228 for information about backups To update the database configuration just use the db2 update database command This command updates all database partitions by default except when you specify DBPARTITIONNUM to update only a certain database partition You can use the db2_ps command to list all of the DB2 engine processes on all logical partitions db2_ call stack The db2_call_stack command on UNIX based platforms causes all of the processes that are running on all database partition servers to write call traces back to the syslog In general you do not need to run this command unless it is required by the DB2 support staff Appendix A Issuing commands to multiple database partitions 497 498 Up and Running with DB2 on Linux DB2 Tools Catalog creation In this appendix we provide information related to the Tool Catalog creation and a sample to create the DB2 Tools Catalog Database manually Copyright IBM Corp 2008 All rights reserved 499 DB2 Tools Catalog creation If you did not create a tools catalog when you installed DB2 you can create it by using DB2 Control Center or by the Command Line Processor CLP If you are using the DB2 Control Center to create a tools catalog after invoking the DB2 Control Center you can select Tools gt Tools Settings Scheduler Settings Figure B 1
273. e various tasks You can concentrate on implementing and testing your business logic The Data Studio can dramatically decrease the amount of time that you need for development Chapter 8 Application development 491 492 Up and Running with DB2 on Linux Issuing commands to multiple database partitions In this appendix we discuss commonly used DB2 commands in a multiple partition environment MPE These commands are useful when you need to collect information from multiple database partitions or machines or run specific commands against multiple partitions or machines The commands that we discuss in this appendix include db2_ps db2_al11 rah db2_call_stack and so on Copyright IBM Corp 2008 All rights reserved 493 db2_ all and rah 494 In a multiple partition environment you might want to issue commands to run on more than one machine or partition in the instance and you do not want to repeat the same commands on every machine or partition involved For this purpose you can use the rah command or the db2_al1 command The rah command allows you to issue commands that you want to run on all machines across which the instance is spread If you want the commands to run at the database partition level in the instance you run the db2_al1 command To run a command on all machines with rah the general command syntax is rah commands To run the commands on all of the database partitions that you specify use the db2_al1
274. ealth notification contact list as shown in Figure 7 7 Configure Health Alert Notification db2inst1 itsosj sanjo Contact Figure 7 7 Configure health alert notification The people in the notification list will be informed if any alert is generated with a severity that is covered by the current notify level setting By default the notification information is written into the DB2 instance s notification log which is located under the directory HOME sqllib db2dump and the file name is lt instance name gt nfy For details regarding the notification log as well as its setting refer to 7 4 1 DB2 administration notification log on page 397 Usage sample In this section we demonstrate how to configure a health indicator in the Health Center or by DB2 CLP commands to monitor database managed space DMS 360 Up and Running with DB2 on Linux table space storage consumption In this example we expect when table space utilization which is measured as the percentage of space consumed exceeds the predefined threshold values for a warning or alarm the DB2 system will send notification to the administration notification log and the specified contacts by e mail You can get recommendations from the Health Center or by DB2 CLP commands for this type of situation and take actions accordingly Furthermore we also show you how to specify follow up actions for the occurrence of a warning or alarm for this specific health indicator
275. ec classes public class FMPSALARY T public static void eMPSALARY int SALARY Resultset rsl throws sQLException Exception Get connection to the database Connection con DriverManager getcConnection jdbce default connection PreparedStatement stmt null boolean brlag String sql sql SELECT PMPIOYER FMPNO FMPIOYEE LASTNAME DEPARIMENT DEPTNO DEPARTMENT DEP TNAME K i FROM EMPLOYEE JOIN DEPARTMENT ON FMPLOYEE WORKDEPT DEPARTMENT DEP TNO Bact WHERE FMPLOYEE SALARY lt SALARY stmt con prepareStatement sql brlag stmt execute rslL 0 stmt getResultset Figure 8 31 Java code of the stored procedure Chapter 8 Application development 485 486 10 Now we are ready to deploy the code to the database server Expand the project DataProject gt Stored Procedures EMPSALARY right click EMPSALARY and select Deploy Keep the Deploy option defaults as shown in Figure 8 32 Click Next m Deploy Routines O Deploy Options Specify options for the deployment Target database CO Use different database ae E v Connection Target schema for deploying an unqualified routine Schema DB2INST1 Duplicate handling Drop duplicates CO Treat duplicates as errors oO Ignore duplicates and continue to the next routine Deploy by building the source O Deploy using binaries if available in the database C Deploy source to the database Figure
276. ed Inserted O row s Updated 1 row s Deleted 0 row s Figure 5 25 Update table data in Data Studio The data distribution viewer can be selected by right clicking the EMPLOYEE table in the Database Explorer and selecting Value Distributions gt Multivariate You get the viewer panel where you can analyze your data Figure 5 26 Table statistics 42 rows Field name Datatype Values Nulls Minimur Maximur Range Total Mean Standard 1st Quart FIRSTNME Categorice MIDINIT Categorice LASTNAME Categorice WORKDEPT Categoric PHONENO Categorice HIREDATE Temporal Categorice Charts for selected fields Charts per page e gt C Show Frequencies in WORKDEPT Ee DESIGNER MANAGER CLERK FIELDREP OPERATOR SALESREP Figure 5 26 Data distribution viewer 222 Up and Running with DB2 on Linux If you double click any of the database objects in the Database Explorer view you get an editor panel which allows you to manipulate the related object For instance if you double click the EMPLOYEE table you get the panel shown in Figure 5 27 Data Object Editor Data Object Properties Specify additional properties to alter your data object Run DDL when you are done E lt Table gt DEPARTMENT a Preview DDL General Partition Key S R t g BunooL Data Partitions Table Spaces Name Dimensions DEPTNO m CHAR 3 i Privileges DEPTNAME VARCHAR 35 7 o
277. ed successfully and a Web address is given You can access the client console by pointing your Web browser to this address Click Done Chapter 5 IBM Data Studio 209 IBM Data Studio Administration Console 1 1 2 Introduction Start Up server has started successfully License Agreement Choose Install Directory Specify Server Details Setup Notification Select Start Up Options Configuration Options Setup Monitoring Pre iInstallation Summary Installing Install Complete Vv gt The client console can be launched from any machine by pointing your Web browser to the address below You should add it as a bookmark for future use and forward it to other console users Log in to the console using an operating system user ID that is valid on the server http cetus itsos sanjose ibm com sibm console y Launch client console Open Readme Verification Start Up Click Done to exit the installer L Figure 5 12 Start Up 5 2 3 Migration from the Developer Workbench Because IBM Data Studio is a full replacement for the Developer Workbench there is no direct migration path from the Developer Workbench to the Data Studio You can install the Data Studio as a separate package and import the existing projects from the Developer Workbench to the Data Studio 5 3 Features and functions In this section we introduce frequently used t
278. ed procedure helps to reduce unnecessary data transfer over the network between the client and the server The SQL statements and definitions are stored on the database server The client sends only the necessary data over the network to call the stored procedure and gets the results sent back which helps to improve the overall performance of client server applications Like UDFs stored procedures are extremely useful to put common business logic into a central place and to make it accessible to any client The CREATE PROCEDURE DDL statement defines a procedure within an application server There are two types of procedures external procedures which are written in a programming language and SQL procedures which are written in SQL Stored procedures written in other languages than SQL are handled similarly to UDF s written in other languages Refer to 8 3 3 C and C on page 441 and 8 3 4 Java on page 449 for a discussion of UDFs written in C and Java Example 8 5 on page 432 shows an SQL procedure that calculates the new salary and bonus for an employee The input is an employee number and rating and the result is to update the table EMPLOYEE The file basecase db2 is part of the DB2 samples and it can be found in lt instance home gt sqllib samples sqlproc Note The CREATE PROCEDURE statement is explained in more detail in the Information Center in Database fundamentals gt SQL Statements gt CREATE PROCEDURE
279. ed the response file to db2ese_mpp rsp Then click Next Select installation response file creation or both The DB2 Setup wizard can install DB2 Enterprise Server Edition Version 9 5 on this computer create a response file that you can use to install this product on a computer later or both If you are setting up a DB2 Enterprise Server Edition ESE partitioned database environment you can also create a response file to install DB2 on the other computers that will act as database partition servers _ Install DB2 Enterprise Server Edition Version 9 5 on this computer _ Save my installation settings in a response file No software will be installed on this computer c Install DB2 Enterprise Server Edition Version 9 5 on this computer and save my settings in a response file Response filename J troot db2ese_mpp rsp onl Figure 2 15 MPP Installation Select installation response file creation or both Up and Running with DB2 on Linux 7 On the next window you can choose whether to install IBM Tivoli System Automation or not and then click Next 8 Set user information for the DB2 Administration Server as shown in Figure 2 16 This user administers the Database Administration Server Choose the existing user dasusr1 and click Next Djar reuna OIE Sse clara Trog gees CEEE Tonina Jaare niora eliesecciny Jdasusrt Figure 2 16 MPP Installation Set user information for the DB2 Administration Server
280. edbooks publications 0 0 eee 507 Other publiGations 4 Tee bao 4 eee de Bee eelledee sh E SAANEN aad 507 Online r sS urceS unsin hated nde de ead ya Poe Oe AS 508 How to get IBM Redbooks publications 0 00 0 eee eee 510 INGOX tes a Bete SE aot te eee alate bles TN E oe ee 511 Contents vii viii Up and Running with DB2 on Linux Notices This information was developed for products and services offered in the U S A IBM may not offer the products services or features discussed in this document in other countries Consult your local IBM representative for information on the products and services currently available in your area Any reference to an IBM product program or service is not intended to state or imply that only that IBM product program or service may be used Any functionally equivalent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility to evaluate and verify the operation of any non IBM product program or service IBM may have patents or pending patent applications covering subject matter described in this document The furnishing of this document does not give you any license to these patents You can send license inquiries in writing to IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504 1785 U S A The following paragraph does not apply to the United Kingdom or a
281. efinition to a flat file using the Configuration Assistant Figure 3 32 on page 158 Transfer the configuration profile to each client machine and import the definition using the Configuration Assistant Chapter 3 Post installation tasks 157 158 Configuration Assistant NDE410D7 Figure 3 32 Export client configuration definition Configuring the client using the command line In addition to Configuration Assistant you can use the DB2 Command Line Processor CLP to configure DB2 clients Example 3 40 shows the commands for configuring a client called puget to access our sample database ITSODB on the server called mensa Example 3 40 Configure client using the command line db2vs puget gt db2 catalog tcpip node mensa remote mensa server 50001 ostype LINUX with DB Server MENSA DB20000I The CATALOG TCPIP NODE command completed successfully DB21056W Directory changes may not be effective until the directory cache is refreshed db2vs puget gt db2 catalog database ITSODB as ITSODB at node mensa authentication server with Test database for ITSO DB20000I The CATALOG DATABASE command completed successfully DB21056W Directory changes may not be effective until the directory cache is refreshed db2vs puget gt db2 list node directory Node Directory Number of entries in the directory 1 Node 1 entry Node name MENSA Up and Running with DB2 on Linux Comment DB Server MENSA Directory entry type
282. efore ensure that sufficient log space is available Redistributing is an extremely time consuming process and must be done when tables are not in use by applications DB2 packages which have a dependency on a table that was redistributed are set as invalid The DB2 packages are automatically rebound at the first SQL request but to save delay time rebind these packages manually with the rebind command We also recommend that you update statistics by issuing the runstats table command and rebind affected packages Note There is more information about adding a database partition in the Partitioning and Clustering Guide SC23 5860 An alternate method to add a logical database partition is to use the Add Database Partition wizard Figure 3 14 on page 129 Up and Running with DB2 on Linux 2 Control Center a all Systems KDEA DAS999A9 Linux inu Instances D YMSUSE Linux ef VMSUSE Figure 3 1 4 Add a partition to a database The wizard guides you through the process At the Container tab Figure 3 15 on page 130 you have to define the container locations on the new partitions Chapter 3 Post installation tasks 129 Set Containers MENSA ITSODB 2 V IBMTEMPGROUP vy TEMPSPACE1 db2temp db2inst1 NODEO002 ITSODB TEMPSPACE1 Directory wv SNG_O1 vy SAMPLE_SNG db db2inst1 NODEO002 ITSODB SAMPLE_SNG dit Figure 3 15 The Container tab In Figure 3 16 on page 131 you can see the generated com
283. en determining memory requirements be aware that gt We recommend that your SWAP space is at least twice as much as your RAM gt For IBM data server client support these memory requirements are for a base of five concurrent client connections We recommend that you allocate an additional 16 MB of RAM per five client connections gt Memory requirements are affected by the size and complexity of your database system as well as by the extent of database activity and the number of clients accessing your system For DB2 server products the self tuning memory feature simplifies the task of memory configuration by automatically setting values for several memory configuration parameters When enabled the memory tuner dynamically distributes available memory resources among several memory consumers including sort the package cache the lock list and buffer pools 2 1 5 Communication requirements TCP IP is required to access remote databases Your Linux distribution provides TCP IP connectivity if selected during the installation If your Linux machine is installed on an existing network and is required to use a static IP address information similar to Table 2 5 must be collected from the network administrators Table 2 5 Required network information Host IP address 192 168 1 3 The above information must be specified on the setup window during OS installation or as a post installation step using your distribution s setup ut
284. ename created by the o filename flag The default value of the filename parameter is the current daily data file the var log sa sadd file The f option is exclusive of the o option EN romos OOOO fa eoero raros ronen earem a Fere ne aue eran araa aoas o Sets the starting time of the data causing the sar command to extract records time tagged at or following the time specified We provide samples of using the sar command next In Example 7 31 on page 422 at first sar is started with the A command option and the output is saved in the sartest bin file sar A o sartest bin 5 60 gt dev null amp In the previous example sartest bin is the output file name and the interval is five seconds and repeats 1 000 times Chapter 7 Monitoring and troubleshooting DB2 421 To see the CPU utilization information since a specified starting time use the following command sar u s 14 34 00 f sartest bin more This command also can be used to see the CPU consumption of the data load when loading data into a DB2 database in a multi partitioned database environment You can use the following command to get process creation fork and system context switch information sar w C s 14 34 45 e 14 35 30 f sartest bin more You can use the following command to obtain network statistics for a specific network interface sar n DEV s 14 36 00 f sartest bin egrep eth0O IFACE Example 7 31 shows these commands and their ou
285. ent gt Command line tools The command line tools consist of the Command Line Processor CLP the configuration export command db2cfexp and the configuration import command db2cfimp Configuring the client using the Configuration Assistant First we show you how to configure the client using the graphical tool 1 Start the Configuration Assistant Figure 3 29 by running db2ca amp as a valid DB2 user or open it from the DB2 folder Configuration Assistant Figure 3 29 Add Database Using Wizard from the Configuration Assistant 2 In the next panel Figure 3 30 on page 156 select how you want to set up the connection to the database server Chapter 3 Post installation tasks 155 Figure 3 30 Add Database Wizard Select Search the network and click Next Expand the tree under Known systems until you see all of the databases on this system Select your desired database You can also choose to manually configure the connection if you know all of the information necessary to connect to the database After completing all of the required fields you can test a connection to this database Figure 3 31 on page 157 156 Up and Running with DB2 on Linux Add Database Confirmation ITSODB AA Test Connection ITSODB k Starts testing for te selected connections Figure 3 31 Test Connection panel To configure many client machines perform all of the configurations on one client machine and then export the d
286. eping 0 stopped 0 zombie Cpu s 0 0 us O 2 sy 0 0 ni 99 2 id 0 7 wa 0 0 hi 0 0 si 0 0 st Mem 3842648k total 3558428k used 284220k free 274856k buffers Swap 8393920k total 6184k used 8387736k free 2884176k cached PID USER PR NI VIRT RES SHR S CPU MEM TIME COMMAND 1785 db2instl 25 0 1255m 152m 118m S 0 4 1 0 07 46 db2sysc 0 2928 db2fencl 15 0 522m 56m 33m S 0 1 5 0 00 40 db2fmp 0 0 0 0 0 2921 db2fencl 15 0 532m 55m 33m S 0 1 5 0 00 30 db2fmp 1 0 0 0 0 1783 root 16 0 980m 44m 25m S 0 1 2 0 00 09 db2wdog 0 1803 db2instl 16 0 555m 36m 20m S 0 1 0 0 03 33 db2acd 0 0 0 0 1 0 29932 db2instl 16 0 739m 35m 13m S 0 0 9 0 01 33 db2home db2inst1 s 1786 root 16 0 724m 26m 8276 S 0 0 7 0 00 00 db2ckpwd 0 1787 root 16 0 724m 26m 8204 S 0 0 7 0 00 00 db2ckpwd 0 1788 root 16 0 724m 26m 8204 S 0 0 7 0 00 00 db2ckpwd 0 5420 gdm 15 0 94424 18m 10m S 0 0 5 0 00 42 opt gnome 1ib64 gd 416 Up and Running with DB2 on Linux 31914 db2instl 16 0 123m 14m 9012 S 0 0 4 0 00 04 db2home db2inst1 s 4462 db2instl 16 0 121m 13m 8036 S 0 0 3 0 00 02 db2home db2inst1 s 14531 root 16 0 110m 11m 7516 S 0 0 3 0 00 01 db2licd 4262 root 15 0 305m 8884 4336 S 0 0 2 0 00 66 usr X11R6 bin X 0 0 0 0 2 0 00 26450 dasusrl 20 136m 7644 5300 S 22 home dasusr1 das a Regarding the field descriptions for the output display of the top command refer to the man help pages for top or other Linux documentation Here is another example of using top to mo
287. er 0 Description Online Tablespace Rollforward Recovery 7 Start Time 02 21 2008 15 25 20 435220 State Executing Invocation Type User Progress Monitoring Estimated Percentage Complete 0 Phase Number 1 Description Forward Total Work 38614 bytes Completed Work 38614 bytes Start Time 02 21 2008 15 25 20 435226 Phase Number Current 2 Description Backward Total Work 5627893427 bytes Completed Work 0 bytes Start Time 02 21 2008 15 25 20 988645 262 Up and Running with DB2 on Linux db2inst1 mensa gt db2 select UTILITY_TYPE substr UTILITY_DESCRIPTION 1 15 UTILITY_STATE DBPARTITIONNUM from SYSIBMADM SNAPUTIL UTILITY_TYPE 2 UTILITY_STATE DBPARTITIONNUM ROLLFOWARD_RECOVERY Online Tablespa EXECUTE 0 1 record s selected db2inst1 mensa gt db2 select SNAPSHOT_TIMESTAMP UTILITY_STATE substr PROGRESS DESCRIPTION 1 10 desc PROGRESS START TIME PROGRESS _TOTAL_UNITS PROGRESS COMPLETED_UNITS DBPARTITIONNUM from SYSIBMADM SNAPUTIL_PROGRESS SNAPSHOT_TIMESTAMP UTILITY_STATE DESC PROGRESS_START_TIME PROGRESS _TOTAL_UNITS PROGRESS COMPLETED_UNITS DBPARTITIONNUM 2008 02 21 15 25 21 767401 EXECUTE Forward 2008 02 21 15 25 20 435226 38614 38614 0 2008 02 21 15 25 21 767401 EXECUTE Backward 2008 02 21 15 25 20 988645 5627893427 0 0 2 record s selected For the rollforward recovery there are two phases forward and backward During the forward phase log files are read and the l
288. er Yes No DAS and its associated Available Not available commands Control Center Yes No Available Not available Operating system based Yes No authentication You can lift this limitation by having a root user run the db2rfe command DB2 instance actions can A DB2 instance created by Anon rootinstance can be be performed a user with root authority updated or dropped using canbe updated or dropped the db2_deinstall only by a user with root command only by the authority non root user who owns the non root instance Support partitioned No database Only single partition databases are supported in non root installations Chapter 2 Installation 37 For the details about the limitations of non root installations refer to the IBM DB2 9 5 Information Center http publib boulder ibm com infocenter db2 uw v9r5 topic com ibm db2 1luw qb s erver doc doc c0050568 html Support changes for 32 bit and 64 bit DB2 servers In DB2 9 5 support changes for 32 bit and 64 bit servers are gt Only 64 bit instances were able to be created on a 64 bit Linux kernel on x86_64 POWER and System z gt No 32 bit DB2 Enterprise Server Edition DB2 9 5 Enterprise Server Edition ESE is only supported on 64 bit architectures 2 2 2 Installation methods 38 There are four methods in which you can install DB2 on Linux DB2 Setup wizard db2_install command Response file installation Payload file deployment vvvy Each m
289. er multi partition systems we recommend that the databases are stored in a separate file system for example database Performing manual configuration allows you to allocate your preferred default database directory in the first place The db2_install command installs all components for the DB2 product that you specify with the English interface support You can select additional languages to support with the L parameter Considering the higher number of manual configuration tasks this installation method can take longer It requires a higher level of skill and cannot create response files Response file installation A response file can be created using the DB2 Setup wizard or by editing a sample response file It allows you to install DB2 across multiple machines with consistent installation and configuration settings and can also be used to set up a DB2 cluster A response file installation is fast because it bypasses the graphical wizard and does the configuration for you Another advantage of using a response file is that it creates a Database Administration Server DAS on each machine while with db2_instal1 the DAS must be created manually after installation For more advanced users we recommend that you create a response file by editing a sample response file and then use this file to install DB2 The sample response file not only installs DB2 but it can also configure users create an instance set up notification create a tool
290. erated by the iostat command provides statistics concerning the time since the system was started Each subsequent report covers the time period since the previous report was generated There are several useful command options that you can use with the iostat command For example using k to display statistics in kilobytes instead of blocks using x to obtain extended statistics information for devices using t to print the time for each report displayed and so on For more details refer to the man help pages for iostat or other Linux documentation Example 7 30 shows using the iostat command to monitor CPU and device I O statistics The iostat 2 5 command displays the current CPU load average and disk I O information 5 times and the interval is 2 seconds Example 7 30 Using iostat to get CPU and I O statistics db2inst1 mensa db2home db2inst1 gt iostat 2 5 Linux 2 6 16 46 0 12 smp mensa 02 14 2008 avg cpu user nice system iowait steal idle 0 23 0 00 0 19 0 67 0 00 98 91 Device tps Blk_read s Blk_wrtn s Blk_read Blk_wrtn sda 2 83 23 70 87 41 19896080 73373644 sdb 0 72 0 05 15 74 37783 13215608 sdc 0 00 0 00 0 00 1816 0 sdd 0 00 0 00 0 00 1816 0 sde 0 00 0 00 0 00 1816 0 sdf 0 00 0 00 0 00 1816 0 avg cpu user nice system iowait steal idle Chapter 7 Monitoring and troubleshooting DB2 419 0 00 0 00 0 25 0 50 0 00 99 00 Device tps Blk_read s Blk_wrtn s Blk_read Blk_wrtn sda 1 49 0 00 43 78 0 88 sdb
291. ermanent data Regular table 0x0000 16384 16380 12288 4092 12288 4096 4 4 1 1 TEMPSPACE1 System managed space System Temporary data State 0x0000 Detailed explanation Normal Total pages 1 Usable pages 1 Used pages 1 Free pages Not applicable High water mark pages Not applicable Page size bytes 4096 Extent size pages 32 Prefetch size pages 32 Number of containers 1 Tablespace ID 2 Name USERSPACE1 Type Database managed space Contents All permanent data Large table space State 0x0080 Detailed explanation Roll forward pending Total pages 8192 Usable pages 8160 Used pages 0 Free pages 8160 High water mark pages 96 Page size bytes 4096 Extent size pages 32 Prefetch size pages 32 Number of containers 1 Minimum recovery time 2008 02 06 22 51 24 000000 Minimum recovery time UCT is 2008 02 06 22 51 24 so continue the roll forward db2inst1 mensa gt db2 rollforward db itsodb stop tablespace userspacel online SQL1275N The stoptime passed to roll forward must be greater than or equal to 2008 02 06 22 51 24 000000 UTC because database ITSODB on node s 0 contains information later than the specified time db2instl mensa gt db2 rollforward db itsodb to 2008 02 06 22 51 24 tablespace userspacel online Rollforward Status Input database alias itsodb Number of nodes have retu
292. erminology in Data Studio and briefly discuss the features and functions that support you in designing and developing your database and your database applications In 8 5 3 Application development with the Data Studio on page 470 we demonstrate the creation of a query using the Query Editor We also create a Java stored procedure and demonstrate how to debug it on the database server 210 Up and Running with DB2 on Linux 5 3 1 Terminology IBM Data Studio is an Eclipse based application It uses the same terminology as other Eclipse based applications such as workspace perspectives views and so on Workspace A workspace is a logical collection of projects that you define It contains all of the files of your current local working environment When you start the Data Studio it prompts you for a workspace location This Welcome panel contains several useful links for learning the Data Studio You can omit this prompt in the future by selecting the check box on that panel You can use as many workspaces as you want There is no direct relationship between them You can use workspaces to organize projects for different applications or different versions of a project Note You can always get back to the Welcome window by selecting Help gt Welcome If you want to share a workspace in your team use the Team functions that are described in 5 3 2 Team function on page 216 A workspace is presented through the views tha
293. erwise the static SQL application will not be able to utilize the new DB2 statistics Additionally you can use the db2rbind utility to rebind all invalid packages or all packages within the database Examples This section provides examples demonstrating the usage of the utilities discussed in this section REORG TABLE REORG INDEXES REORGCHK and RUNSTATS We have created a table named ITEM across two database partitions and populated it with 3 000 000 rows of data An unique index named PK_ITEM_ITEMID is associated with this table Example 6 34 shows details for the ITEM table Example 6 34 More details for sample table ITEM db2instl mensa gt db2 describe table item Data type Column Column name schema Data type name Length Scale Nulls ITEMID SYSIBM INTEGER 4 0 No AMOUNT SYSIBM DECIMAL 8 2 Yes 2 record s selected db2instl mensa gt db2 describe indexes for table item Index Index Unique Number of schema name rule columns DB2INST1 PK_ITEM_ITEMID P 1 1 record s selected db2inst1 mensa gt db2 select dbpartitionnum itemid as part_no count as Counter from item group by dbpartitionnum itemid Up and Running with DB2 on Linux PART_NO COUNTER 0 1500364 1 1499636 2 record s selected The steps performed in this example are 1 Run RUNSTATS to gather the current statistics information 2 Delete half of the total rows within the ITEM table 3 Use REORGCHK with the UPDATE STATISTICS option to update
294. es v 417 5 MB Unknow Undefined Heap _ 5 MB Unknown Undefined Heap _ 12 44 MB Unknow tee Lans L a Ann C SEA OA KAM tI bandea mee D meee EEEE TETTEST IAT EEATT EAT NAT A EATE EAT TA ATAT YEA AT TET EA TAT A EAE SAT EAT T TEAT a EAT Figure 7 28 Using Memory Visualizer to monitor DB2 memory usage Within this panel you can gt View memory usage for a specific memory heap or buffer or view memory usage at the overall level gt Specify which memory information to display and which information to hide for a DB2 instance and its databases in the Customize Columns panel which can be displayed by choosing View gt Customize Columns gt Update the configuration parameters for an individual memory component to prevent it from using too much memory or too little memory what you need to do is select the value in the Parameter Value field and then enter a new value 382 Up and Running with DB2 on Linux gt Toggle which memory component will be displayed in the Memory Usage Plot graph which is located at the bottom of the Memory Visualizer main window gt Save or load memory allocation data to or from a file for a Memory Visualizer window db2mirk DB2 also provides you with a command line tool to obtain memory usage information for a DB2 instance It is called Memory Tracker The command name is db2mtrk This command outputs the following memory pool allocation information Curren
295. et Show Command Cancel Help i Figure 6 30 Using EXPORT in the DB2 Control Center The export operation will fail if the data that you want to export exceeds the space available on the file system on which the exported file will be created To avoid this situation you can limit the amount of data that is selected by specifying conditions on the WHERE clause and invoking the export utility multiple times to export all of the data For information about using the ADMIN_CMD stored procedure or the EXPORT API and for more details regarding the EXPORT utility refer to Data Movement Utilities Guide and Reference SC23 5847 6 3 2 Import data from files into database tables or views The import utility inserts data from an input file into a table or updateable view If the table or view already has data you can either replace the existing data or append to the existing data You can also use import to create a new table if the format of the input file is Integrated eXchange Format IXF by using the IMPORT command options CREATE and REPLACE_CREATE Not all of the properties of the table are 306 Up and Running with DB2 on Linux re created when you use CREATE and REPLACE_CREATE Note that these options are deprecated and they might be removed in a future release Note Instead of using the IMPORT options to create the table use the db2100k command to capture the original table definitions and re create the table
296. ethod has its own advantages and disadvantages The preferred method often depends on your level of expertise and type of environment but in general if a graphical terminal is available using DB2 Setup wizard is recommended DB2 Setup wizard The DB2 Setup wizard is a Java based graphical tool that installs DB2 It lays down the DB2 file sets and the Java Developer Kit It allows you to create a new DB2 instance create new users and groups or configure DB2 to existing users configure communications create the tools catalog database and set up notification DB2 Setup also has an option that allows you to create a response file This is the best method for less experienced users because most of the configuration is performed for you db2_install command The db2_install script installs all DB2 packages on your Linux system and you cannot select or deselect components This method is reliable and commonly used by expert users for installing DB2 on larger more complex partitioned database environments Tasks such as users and group setup instance creation tools catalog database creation and notification setup have to be performed manually after the installation Up and Running with DB2 on Linux Certain people prefer this method because it bypasses the configuration performed by DB2 Setup It allows you to configure DB2 according to your preferences initially and gives you more control over database management Particularly for larg
297. f performance compatibility or any other claims related to non IBM products Questions on the capabilities of non IBM products should be addressed to the suppliers of those products This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the examples include the names of individuals companies brands and products All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrate programming techniques on various operating platforms You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written These examples have not been thoroughly tested under all conditions IBM therefore cannot guarantee or imply reliability serviceability or function of these programs Copyright IBM Corp 2008 All rights reserved ix Trademarks IBM the IBM logo and ibm com are trademarks or registered trademarks of International Business Machines Corporation in the United States other countries or both If these and other IBM trademarked terms are marked on the
298. f the file where the output will be stored To reset the license usage information use the db2licm x command 166 Up and Running with DB2 on Linux Migration and fix packs When migrating DB2 from Version 8 or Version 9 1 to Version 9 5 there are several important steps to perform before and after installation to ensure a safe and successful migration In this chapter we describe DB2 server migration from Version 8 2 and Version 9 1 to Version 9 5 as well as fix pack installation We discuss gt Migration planning Migrating multi partitioned database Migrating single partitioned database Post migration tasks Client and server compatibility Fix pack installation YYYY Y For complete information about migrating a DB2 server and other components such as clients and applications in your DB2 environment refer to the DB2 Information Center at http publib boulder ibm com infocenter db21 uw v9r5 index jsp topic com ibm d b2 uw qb migration doc doc c0023662 html DB2 also provides migration tools and services from other databases such as Oracle and Microsoft SQL Server For further information refer to this Web site http www ibm com db2 migration Copyright IBM Corp 2008 All rights reserved 167 4 1 Migration planning Prior to installing DB2 9 5 it is essential that you prepare your system and databases for the migration Additional table space and log space are required for migration as well as a re
299. f using db2adut1 is in DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 Chapter 6 Administering databases 239 6 1 4 Backup utility 240 We have completed all of the steps as described in 6 1 1 Enable rollforward recovery and log archiving on page 230 Now we describe several ways to back up databases Backing up databases DB2 provides several database backup options gt Full offline A full offline database backup allows you to restore the database image without applying any log records Example 6 8 shows the offline backup command Example 6 8 Full offline backup to disk db2instl mensa gt db2 backup db itsodb to db2backup Backup successful The timestamp for this backup image is 20080204081423 gt Full online During online backup the database is still accessible for applications Rollforward recovery has to be enabled To be able to recover the database from an online backup you need at least the range of active log files from the online backup time frame To make sure that these log files are available you can use the INCLUDE LOGS clause within the backup command the default behavior in V9 5 This function includes the required log files for recovery with the database backup image If you need to ship the backup images to a disaster recovery site you do not have to send the log files separately or package them together with database backup copy manually Furthermore you do not have to deci
300. finiBand and the InfiniBand design marks are trademarks and or service marks of the InfiniBand Trade Association AMD the AMD Arrow logo and combinations thereof are trademarks of Advanced Micro Devices Inc eXchange J2EE Java JDBC JDK JVM MySQL Solaris Sun and all Java based trademarks are trademarks of Sun Microsystems Inc in the United States other countries or both Excel Microsoft SQL Server Visual Studio Windows and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both Intel Xeon Intel Pentium Intel logo Intel Inside logo and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States other countries or both UNIX is a registered trademark of The Open Group in the United States and other countries x Up and Running with DB2 on Linux Linux is a trademark of Linus Torvalds in the United States other countries or both Other company product or service names may be trademarks or service marks of others Notices xi xii Up and Running with DB2 on Linux Preface Linux is one of the fastest growing server operating platforms within the past few years DB2 has long been known for its technology leadership This IBM Redbooks publication is an informative guide that describes how to effectively integrate DB2 for Linux UNIX and Windows LUW with SUSE and Red Hat Linux operating sy
301. for more details regarding the load operation within the DB2 Control Center The message files in our case are gt loadcc msg prep 000 for pre partitioning gt loadcc msg part 001 for partitioning gt loadcc msg load 000 and loadcc msg load 001 for loading All of these files are located under the directory db2backup datamove which was specified in the Specifying input and output files panel Figure 6 37 on page 329 For detailed information about using load refer to Data Movement Utilities Guide and Reference SC23 5847 and DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 6 3 4 Using the db2move utility This tool facilitates the movement of large numbers of tables between DB2 databases that are located on workstations It calls the DB2 export and import or 336 Up and Running with DB2 on Linux load APIs depending on the action requested by the user and operates the files in PC IXF format With the co COPY option you can also use db2move to copy one or more schemas from a source database to a target database In Example 6 60 we copy all of the tables from our ITSODB database into a new database called ITSOREPL During the copy the schema name is changed from db2inst1 to db2vs and all of the tables are placed into the default table space Note that you also can specify table space name mappings to use different table spaces Example 6 60 Change schema using d2move db2inst1 mensa db2backup datamove gt
302. form 1E The proper image file name would be ITSODB 0 db2inst1 NODE0000 CATNO000 20080205141153 001 1 Buffers processed H Image Verification Complete successful Chapter 6 Administering databases 245 246 For more options of the db2ckbkp utility see the DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 Back up the database with the DB2 Control Center The backup utility is fully integrated within the DB2 Control Center Figure 6 7 shows where you can invoke the backup utility All Systems All Databases Control Center ions Customize Control Center Figure 6 7 Backup in the Control Center Go through all of the panels and enter all of the necessary parameters At the end you can list the generated backup statements as shown in Figure 6 8 Show SQL The following commands may not run as expected in a multi database partition environment if executed from a single script Backup Database Partition Grouping 1 Run on database partitions 0 BACKUP DATABASE ITSODB ONLINE TO db2backup WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 COMPRESS WITHOUT PROMPTING Backup Database Partition Grouping 2 Run on database partition s 1 BACKUP DATABASE ITSODB ONLINE TQ db2backup WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 COMPRESS WITHOUT PROMPTING Figure 6 8 Generated backup statements You have two options either run this generated script immediately or let it run
303. functions and configure the Simple Mail Transfer Protocol SMTP server Click Next IBM Data Studio Administration Console 1 1 2 Introduction Setup e mail notification License Agreement ae When data server problems occur you can use the built in Choose Install Directory e mail function to forward alert details to other users Enter Specify Server Details the name of your outbound SMTP mail server to enable this Setup Notification e mail capability This function is not applicable to replication Select Start Up Options Configuration Options Enable e mail functions Setup Monitoring SMTP server name smtp itsosj sanjose ibt Pre Installation Summary Port number 25 Installing C This server requires authentication Install Complete eine neers Account name verification Password Start Up Do not enable e mail functions at this time Cancel Previous Next Figure 5 11 Setup Notification 8 On the Select Start Up Options panel select Start services automatically and then click Next 9 On the Configuration Options panel you can choose either Allow the sending of logs or Do not allow the sending of logs and then click Next 10 On the next panel enter the password for sysadmin which will be created automatically by the installer and then click Next 11 On the Pre Installation Summary panel click Next 12 On the Start Up Figure 5 12 on page 210 the DSAC server has start
304. g files are relocated Follow this procedure to change the online log path by commands 1 Create the directories For a single partitioned database environment enter mkdir p db210g1 ITSODB mkdir p db2log2 ITSODB For the multiple partitioned environment enter db2_all typeset Z4 DB2NODE mkdir p db2log1 ITSODB db2_all typeset Z4 DB2NODE mkdir p db2log2 ITSODB 2 Set the database configuration manager parameter NEWLOGPATH to the new path Example 3 21 shows the command Example 3 21 Set the NEWLOGPATH parameter db2instl puget gt db2 UPDATE DB CONFIG FOR itsodb USING NEWLOGPATH db210g1 1TSODB DB20000I1 The UPDATE DATABASE CONFIGURATION command completed successfully SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically For these configuration parameters al applications must disconnect from this database before the changes become effective For the partitioned database use the following command to set the NEWLOGPATH parameter in all database nodes db2_all db2 connect to itsodb db2 update db cfg for itsodb using NEWLOGPATH db210g1 itsodb Up and Running with DB2 on Linux 3 Thi Disconnect all of the users from the database You can use the command db2 list applications to see all of the applications that are currently connected You can then use the command db2 force application lt id gt to force individual users off Note that
305. g the prune history command or a call of the ADMIN_CMD procedure with the PRUNE_HISTORY parameter By setting the database configuration parameters NUM_DB_BACKUPS and REC_HIS_RETENTN the DB2 database manager automatically prunes the database history file Note In Version 9 5 if you set the new configuration parameter AUTO_DEL_REC_OBwJ to ON the database manager will also delete backup images load copy images and log files associated with any history file entries that it automatically prunes When AUTO_DEL_REC_OBu is enabled the system will only perform this maintenance when both the NUM_DB_BACKUPS and REC_HIS_RETENTN values are exceeded 6 1 3 Enable usage of Tivoli STorage Manager DB2 supports database backup and log archiving using Tivoli Storage Manager storage The Tivoli Storage Manager system consists of the Tivoli Storage Manager server and the Tivoli Storage Manager client The database server Chapter 6 Administering databases 237 238 uses the Tivoli Storage Manager client API to communicate with the Tivoli Storage Manager server Our test was based on Tivoli Storage Manager server version 5 5 0 and Tivoli Storage Manager client and client API version 5 4 0 After installing the Tivoli Storage Manager client and the Tivoli Storage Manager API on each database server we have to configure DB2 so that DB2 can communicate with the Tivoli Storage Manager server Edit the file INSTHOME sallib userprofile to add the Tivoli Stora
306. ge Manager variables as shown in Example 6 4 Example 6 4 Tivoli Storage Manager definition in the DB2 instance userprofile export DSMI_DIR opt tivoli tsm client api bin64 export DSMI_CONFIG opt tivoli tsm client api bin64 dsm opt export DSMI_LOG HOME sq11ib db2dump Note If the DSMI variables are changed you need to restart the DB2 instance To be sure that the correct values are used during the db2start time run the following commands db2stop export grep DSMI db2start If you want to verify the DSMI variables for a running DB2 use the ps command ps fu db2inst1 grep db2sysc ps eww lt PID of db2sysc gt The Tivoli Storage Manager client must be configured as well In the following file define the Tivoli Storage Manager server to be used opt tivoli tsm client api bin64 dsm sys Example 6 5 shows the file in our test environment Example 6 5 Sample dsm sys configuration file on the database server SErvername TSM_SERVER1 NodeName db2mensa passwordaccess generate COMMmethod TCPip TCPServeraddress 9 43 86 125 TCPPort 1500 Up and Running with DB2 on Linux The value specified for SErvername has to be specified in the dsm opt file as shown in Example 6 6 The location of the dsm opt file is specified with the DSMI CONFIG variable Example 6 6 dsm opt file SErvername TSM_SERVER1 tapeprompt no Each NodeName has to be registered at the Tivoli Storage Manager server The Tivoli Storage Manager server adminis
307. ges Total number of leaf pages lt 20 SCHEMA NAME INDCARD LEAF ELEAF LVLS NDEL KEYS LEAF_RECSIZE NLEAF_RECSIZE LEAF_PAGE_OVERHEAD NLEAF_PAGE_ OVERHEAD F4 F5 F6 F7 F8 REORG Table DB2INST1 ITEM Index DB2INST1 PK_ITEM_ITEMID 3000728 6176 0 3 0 3000728 4 4 1340 1340 100 92 6 0 0 CLUSTERRATIO or normalized CLUSTERFACTOR F4 will indicate REORG is necessary for indexes that are not in the same sequence as the base table When multiple indexes are defined on a table one or more indexes may be flagged as needing REORG Specify the most important index for REORG sequencing Tables defined using the ORGANIZE BY clause and the corresponding dimension indexes have a suffix to their names The cardinality of a dimension index is equal to the Active blocks statistic of the table The parameters in the RUNSTATS command can be modified based on your situation Here we use ALLOW READ ACCESS to allow read only access to the table from other users while statistics are calculated We use REORGCHK CURRENT STATISTICS to show the statistical information for the table ITEM You can also use the REORGCHK_TB_STATS and REORGCHK_IX_STATS procedures which retrieve table and index statistics for reorganization evaluation directly from the system catalog views for example SYSSTAT TABLES and SYSSTAT INDEXES Important The RUNSTATS utility is run against one database partition only due to performance considerations so certain global statistic
308. ggers Schemas G Indexes 5 Table Spaces G Event Monitors Database partition groups G Buffer Pools G Application Objects G User and Group Objects G Federated Database Objects XML Schema Repository SR H O ITSOREPL E O SAMPLE A TooscaT Figure 6 26 Table context menu In the Run Statistics panel you can select various options for the RUNSTATS command Figure 6 27 on page 289 288 Up and Running with DB2 on Linux Run Statistics ITEM Figure 6 27 Run Statistics panel You can schedule the RUNSTATS command as a task in the Task Center as well Figure 6 28 shows a sample of the generated commands CONNECT TO ITSODB RUNSTATS ON TABLE DB2INST 1 ITEM_ ON ALL COLUMNS WITH DISTRIBUTION ON ALL COLUMNS AND INDEXES ALL ALLOW WRITE ACCESS COMMIT WORK CONNECT RESET Figure 6 28 Generated RUNSTATS command Packages rebinding The command REBIND enables the user to take advantage of a change in the system without a need for the original bind file It is likely that a particular SQL Chapter 6 Administering databases 289 290 statement can take advantage of a newly created index The REBIND command can be used to recreate the package REBIND can also be used to recreate packages after RUNSTATS is executed thereby taking advantage of the new statistics Important After a RUNSTATS is executed you have to use the REBIND or BIND command to recreate the package that is stored in the database oth
309. gh water mark pages 1184 Page size bytes 8192 Extent size pages 32 Prefetch size pages 32 Number of containers 1 Minimum recovery time 2008 02 21 22 46 03 000000 DB210111 In a partitioned database server environment only the table spaces on the current node are listed gemini db2 list tablespaces completed ok Up and Running with DB2 on Linux After the corrective actions take effect the health indicator returns to the normal state and keeps monitoring the system 7 2 Memory Visualizer and Memory Tracker In this section we discuss two memory monitoring tools Memory Visualizer and Memory Tracker Memory Visualizer The Memory Visualizer can assist you in monitoring memory utilization for a DB2 instance It uses visual displays and plotted graphs to help you understand memory components and their relationships to each other and it helps you uncover and fix memory related problems on a DB2 instance You can start Memory Visualizer in the Control Center by right clicking an instance and selecting View memory usage To start the Memory Visualizer from the command line issue the db2memvis command The Memory Visualizer panel appears as shown in Figure 7 28 on page 382 Chapter 7 Monitoring and troubleshooting DB2 381 ta Backup Restore _ 82 _ 2 5 782 5 MB Package Cache _ 29 94 MB Unknow Catalog Cache H _ 12 5 MB Unknown a OtherMemory _ 7 5 MB Unknown Mit
310. gr instname In this command DB2HOME is the location where the DB2 9 5 client is installed and instname is the instance Instead of migrating your existing client instance you can create a new client instance by using the following command DB2HOME bin db2icrt s client instname Then import the configuration that you collected in step 2 186 Up and Running with DB2 on Linux 4 3 Migrating a single partitioned database This section describes the single partitioned database migration procedure In general single partitioned database migration steps are a subset of the procedure for migrating a multi partitioned database Here we provide the required steps and point out the differences For the details in each step refer to 4 2 Migrating multi partitioned database on page 173 Follow these single partitioned database server migration steps 1 Verify that you can migrate your instance to the Version 9 5 that you have installed Save the packages and table space information Back up the DB2 configuration and diagnostics information db2support Ensure that the database does not contain any indoubt transactions Or SR OOS Revoke the EXECUTE privilege on migrated routines from PUBLIC This step is an optional step Set the DIAGLEVEL parameter to 3 or higher Make the DB2 Version 8 or Version 9 1 databases inactive Archive all of the DB2 log files if replication is used Back up the databases We suggest a full off
311. grate DB2 Explain tables The migrate database command does not migrate explain tables Perform this task if you want to keep explain table information that you previously gathered If you do not want to keep this information you can later recreate the explain tables and gather new information To migrate explain tables use the db2exmig command as follows db2exmig d lt database_name gt e lt explain_schema gt u userid password In this command database_name is the name of the database where the explain tables are stored explain_schema represents the schema name of Chapter 4 Migration and fix packs 181 9 the explain tables to be migrated and userid and password are the current user s ID and password The user ID and password parameters are optional If you obtained customized codepage conversion tables from the DB2 support service copy all of the files for those tables from the DB2OLD conv to DB2DIR conv where DB2OLD is the location of your DB2 9 1 or DB2 UDB Version 8 copy and DB2DIR is the location of your DB2 9 5 copy You do not need to copy standard codepage conversion tables After all steps are completed back up all of your databases 10 You can now optionally check if the index or tables need to be reorganized using the REORGCHK command 4 2 5 Enabling new DB2 9 5 functionality After migrating databases and instances you might want to enable important new features to enhance the functionality and
312. gs Rollforward Status Input database alias itsodb Number of nodes have returned status 1 Node number 0 Rollforward status DB working 0000001 L0G 0000000 LOG S0000000 LOG 2008 02 06 22 38 32 000000 UTC Next log file to be read Log files processed Last committed transaction DB20000I The ROLLFORWARD command completed successfully db2instl mensa gt db2 rollforward db itsodb stop Rollforward Status Input database alias itsodb Number of nodes have returned status 1 Node number 0 Rollforward status Next log file to be read Log files processed Last committed transaction not pending 0000000 LOG S0000000 LOG 2008 02 06 22 38 32 000000 UTC DB20000I1 The ROLLFORWARD command completed successfully 256 Up and Running with DB2 on Linux Full database restore with incremental backup The best way to restore an incremental backup image is to use the AUTO option DB2 will collect the needed backup images full and incremental to restore the database db2 restore db itsodb incremental auto from db2backup taken at 20080204091912 If you want to know which backup images are required to restore an incremental backup you can use the db2ckrst command db2ckrst d itsodb t 20080204091912 The command queries the database history and generates a list of timestamps for the backup images and the suggested restore order Rollforward recovery To use the rollforward recovery method the database
313. gt IBMDEFAULTBP b Groups L b C Remote Servers b O Roles Description Resource _ GI IGE Figure 5 13 Sample perspective for a workspace Perspectives A perspective is a collection of views and editors grouped into a particular layout Perspectives reflect different roles or tasks within your workspace for instance the debug perspective the data perspective and the version control perspective You can switch to a different perspective by selecting Window gt Open Perspective and then selecting one of perspectives in the submenus You can also create your own perspectives or modify existing ones Figure 5 13 shows the Data perspective At the top right of the panel you can see the recently used perspectives Figure 5 14 on page 213 Clicking one of the recently used perspectives switches to the related perspective 212 Up and Running with DB2 on Linux FEY Data 2g CVS Repasitor Figure 5 14 Buttons to switch between recently used perspectives Here are several of the available perspectives gt Data This is the default perspective that you get if you enter the Data Studio It allows you to manipulate your database database objects and data Debug You are asked to switch to this perspective if you start debugging a Java program It supports you in debugging code J2EE Provides a layout that is more useful if you develop Java 2 Platform Enterprise Edit
314. guration Options gt Setup Monitoring gt Pre Installation Summary gt Installing gt Install Complete Verification Start Up Figure 5 9 Choose Install Directory 6 On the Specify Server Details panel Figure 5 10 specify the host name and ports for the Web server and then click Next IBM Data Studio Administration Console 1 1 2 v Introduction v License Agreement Specify the hostname and ports for the Web server Enter the fully qualified hostname of your server For V Choose Install Directory example server ipm com If the server is assigned a static IP gt Specify Server Details address you can use that instead of the hast name If you use a dynamic IP address monitoring services will not work when gt Setup Notification j F a new IP address is assigned select Start Up Options Configuration Options Server cetus itsosj sanjose ipm com gt Setup Monitoring The default port numbers for HTTP and HTTPS are 80 and 443 respectively You do not need to change these values unless these ports are being used by other applications Pre Installation Summary gt Installing gt Install Complete HTTP port 80 gt Verification HTTPS port 443 D gt Start Up Restore Defaults Cancel Previous Next Figure 5 10 Specify the host name and ports for the Web server 208 Up and Running with DB2 on Linux 7 On Setup Notification panel Figure 5 11 you can choose Enable e mail
315. h specific products or solutions while getting hands on experience with leading edge technologies You will have the opportunity to team with IBM technical professionals Business Partners and Clients Your efforts will help increase product acceptance and client satisfaction As a bonus you will develop a network of contacts in IBM development labs and increase your productivity and marketability Find out more about the residency program browse the residency index and apply online at ibm com redbooks residencies html Comments welcome xvi Your comments are important to us We want our books to be as helpful as possible Send us your comments about this book or other IBM Redbooks publications in one of the following ways gt Use the online Contact us review IBM Redbooks publications form found at ibm com redbooks gt Send your comments in an e mail to redbooks us ibm com gt Mail your comments to Up and Running with DB2 on Linux IBM Corporation International Technical Support Organization Dept HYTD Mail Station P099 2455 South Road Poughkeepsie NY 12601 5400 Preface xvii xviii Up and Running with DB2 on Linux Summary of changes This section describes the technical changes made in this edition of the book This edition might also include minor corrections and editorial changes that are not identified Summary of Changes for SG24 6899 01 for Up and Running with DB2 on Linux as created or updated
316. h general information Figure 6 17 on page 277 Up and Running with DB2 on Linux Figure 6 17 Configure Automatic Maintenance wizard 4 You can specify maintenance windows for the execution of the online activities such as the RUNSTATS utility and for the offline activities such as the REORG utility Figure 6 18 on page 278 shows a sample Chapter 6 Administering databases 277 Configure Automatic Maintenance Figure 6 18 Specify maintenance panel 5 To enable the automatic table maintenance activities you have to select the related check box on the activities page as shown in Figure 6 19 on page 279 278 Up and Running with DB2 on Linux Automatic maintenance includes the following set of activities Select a maintenance activity to view its current settings To enable and disable automation of the activity and notification select the Automate and Notify check boxes To update the settings select the Configure Settings button Select a maintenance activity to configure FA Maintenance activity Backup database BACKUP Defragment table and index data REORG Offline Y v Optimize data access RUNSTATS C a J J Maintenance activity settings The data access optimization maintenance activity automatically analyzes the data in tables to allow for applications to access the data as quickly as possible This activity will occur using the following settings Table scope
317. h status amp Completionstatus ran on the DB2 Administrative Server on amp Schedulersystem and completed with return code amp Returncode The task started on amp Runsystem at amp Start and completed at amp End The task lasted amp Duration seconds Figure 6 52 Notification setting for various results of running tasks Specify the follow up actions for different results of running tasks Figure 6 53 on page 348 In addition to the notification setting for the results of running tasks you can also specify follow up actions For example if the task failed for Task Failure condition you can specify running an alternative task to remedy the condition or disabling the scheduling of another task to avoid unnecessary damage Chapter 6 Administering databases 347 aelel a Snes z EYE Figure 6 53 Follow up actions setting for a task You can also specify access privileges to the task such as read run or execute for different users and groups under the Security tab Now you can submit the task to the Task Center by clicking OK If the task ran you can get the result information through the context menu of the task as shown in Figure 6 54 on page 349 348 Up and Running with DB2 on Linux Task Center Runst ats Task Figure 6 54 Context menu of a task The result of our sample task is shown in Figure 6 55 on page 350 Chapter 6 Administering databases 349 2 28 08 11 3
318. h the load operation is to be performed PARTITIONING_DBPARTNUMS A list of partition numbers that will be used in the partitioning process MODE The mode in which the load operation will take place when loading a partitioned database such as PARTITION_AND_LOAD PARTITION_ONLY LOAD_ONLY and so on PARTITIONED DB CONFIG Allows you to specify partitioned database specific configuration options in a LOAD command Example 6 54 on page 317 demonstrates how to use the PARTITIONED DB CONFIG parameter to specify partitioned database specific options for LOAD With the PARTITION_ONLY option the data is distributed to each database partition but not loaded The output is written to files in the specified location on 316 Up and Running with DB2 on Linux each of the database partitions The data can then be loaded at a later time We load the data from the files into the table ITEM using the LOAD_ONLY mode Example 6 54 Using PARTITIONED DB CONFIG parameter in LOAD command db2inst1 mensa db2backup datamove gt db2 load from item del of del replace into itemload partitioned db config mode partition_only part_file_location db2backup datamove load partitioning _dbpartnums 0 1 Agent Type Node SQL Code Result LOAD_TO_FILE 000 00000000 Success LOAD_TO_FILE 001 00000000 Success PARTITION 000 00000000 Success PARTITION 001 00000000 Success PRE_PARTITION 000 00000000 Success Summary of Partitioning Agents Rows Read 3000000 Row
319. hat s New SC23 5869 Administrative API Reference SC23 5842 Administrative Routines and Views SC23 5843 Call Level Interface Guide and Reference Volume 1 SC23 5844 Call Level Interface Guide and Reference Volume 2 SC23 5845 DB2 for Linux UNIX and Windows Command Reference SC23 5846 01 Data Movement Utilities Guide and Reference SC23 5847 Data Recovery and High Availability Guide and Reference SC23 5848 Data Servers Databases and Database Objects Guide SC23 5849 Database Security Guide SC23 5850 Copyright IBM Corp 2008 All rights reserved 507 gt Developing ADO NET and OLE DB Applications SC23 5851 gt Developing Embedded SQL Applications SC23 5852 gt Developing Java Applications SC23 5853 gt Developing Perl and PHP Applications SC23 5854 gt Developing User defined Routines SQL and External SC23 5855 gt Getting Started with Database Application Development GC23 5856 gt Getting Started with DB2 installation and administration on Linux and Windows GC23 5857 gt Internationalization Guide SC23 5858 gt Message Reference Volume 1 Gl11 7855 gt Message Reference Volume 2 Gl11 7856 gt DB2 for Linux UNIX and Windows Migration Guide GC23 5859 gt Net Search Extender Administration and User s Guide SC23 8509 gt Partitioning and Clustering Guide SC23 5860 gt Query Patroller Administration and User s Guide SC23 8507 gt Quick Beginnings for IBM Data Server Clients GC23 5
320. have installed the run times of the application server WebSphere Tomcat and so on you can debug and run them from within your workspace 5 3 7 Tips 224 Here are a few useful tips for using the Data Studio gt If you double click the title bar of a view or tab the related panel expands to full size Another double click resizes it back to the previous size You can rearrange your layout freely You can move any view into another part of the pane by just using drag and drop The keyboard shortcuts save key strokes and can increase your productivity Use Help gt Key Assist or Shift Ctrl L to show the available keyboard shortcuts In the editor view a helpful function called Content Assist the keyboard shortcut is Ctrl Space can help you complete the name of the object that you are currently typing Tips and Tricks provide useful information for working efficiently with the Data Developer Use Help Tips and Tricks to show the available tips and tricks Up and Running with DB2 on Linux gt If you select Help Tutorial Gallery you get to the tutorial sessions which introduce you to the various features of Data Studio in a guided tour Chapter 5 IBM Data Studio 225 226 Up and Running with DB2 on Linux Administering databases In this chapter we provide information regarding important database maintenance tasks for DB2 on Linux platforms such as database backup and recovery table and index reorganiza
321. he Data Studio offers the following additional features gt gt gt Integrated Query Editor for SQL and XQuery SQLJ Editor SQL Builder The Query Builder allows you to create your queries by using Drag amp Drop You can test the queries directly by running them and viewing the results SQL Routine Debugger The SQL Routine Debugger allows you to debug SQL stored procedures Java Routine Debugger You can create your Java procedures promote them to the server and even debug them remotely on the database server just as you have with stand alone Java applications XML Editor It allows you to edit your XML document in a tree structure You do not need to deal with the XML syntax XML Schema Editor It allows you to edit your XML schemas in a graphical way You do not need to deal with the XML syntax Visual Explain It shows the access plan of your query so that you can troubleshoot performance problems Entity Relationship ER Diagramming You can create your ER diagrams directly from the database schema The opposite is also true The diagrams and the database remain connected so that changes to one are reflected in the other one Data Web Services With a few clicks you can create a Web service based on a query deploy it to an application server or create a Web archive WAR file from it pureQuery for Java pureQuery offers an easy access level to the database In relationship to JDBC it simplifies ma
322. he automatic storage setting after a database has been created For an automatic storage enabled database you have the option to create table spaces to be managed automatically or not using the MANAGED BY clause MANAGED BY AUTOMATIC STORAGE specifies that the storage of a table space is to be managed by that database manager automatically MANAGED BY SYSTEM or MANAGED BY DATABASE defines the storage of a table space to be managed manually If you omit the MANAGED BY clause the table space is managed by automatic storage If you have not enabled your database for automatic storage you cannot specify the option MANAGED BY AUTOMATIC STORAGE In Example 3 7 on page 103 we create a database with automatic storage enabled and add one path for automatic storage The snapshot data shows the storage path for the database Up and Running with DB2 on Linux Example 3 7 Create a database with automatic storage enabled db2inst1 puget gt db2 create database itsodb on database datal DB20000I1 The CREATE DATABASE command completed successfully db2instl puget gt db2 connect to itsodb Database Connection Information DB2 LINUX 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2instl puget gt db2 get snapshot for database on itsodb grep i storage Number of automatic storage paths 1 Automatic storage path database data1 db2inst1 puget gt db2 alter database itsodb add storage on database
323. he default values The database configuration file is used to provide DB2 information such as how much memory it can use where the log has to be stored and DB2 optimizer relevant information gt Binding the database utilities to the database Programs which contain SQL statements have to be bound against the database This binding process is used for DB2 utilities such as import and load Embedded SQL on page 444 provides background information about the bind process Chapter 3 Post installation tasks 107 There are two methods to create databases in a existing instance gt DB2 Create Database Wizard which is a Java based graphical tool gt The create database command used from a command line processor window You must have sysadm or sysctrl authorization to create a new database Before creating a database set the right permissions on all file systems or directories where you want to store the database files By default the database will be created and cataloged in the path that is determined by the database manager configuration DBM cfg parameter DFTDBPATH You can change this path to your desired default path by entering following command db2 update dbm cfg using DFTDBPATH database We explain the creation of the file systems and mount points in 2 2 3 Storage planning on page 40 Create Database wizard If you have DB2 installed in a single partition node the easiest way to create a database is to use
324. he host where the catalog partition resides connect to the database and issue the redistribute command Example 3 32 Redistribute command for MPL_01 db2instl mensa gt db2 redistribute database partition group sng_01 uniform DB200001 The REDISTRIBUTE NODEGROUP command completed successfully Note You can also use the option ADD DBPARTITIONNUMS at the REDISTRIBUTE command which combines the commands ALTER DATABASE PARTITION GROUP and REDISTRIBUTE DATABASE PARTITION GROUP For each table that has already been processed the redistribution utility writes a message to file in INSTHOME sallib redist lt dbname gt lt part group gt lt time gt See Example 3 33 Example 3 33 Sample redistribution Data Redistribution Utility Chapter 3 Post installation tasks 127 128 The following options have been specified Database partition group name SNG_01 Data Redistribution option U Redistribute database partition group uniformly No of partitions to be added 1 List of partitions to be added 2 No of partitions to be dropped 0 List of partitions to be dropped Delete will be done in parallel with the insert The execution of the Data Redistribution operation on Begun at Ended at Table poolID objectID 18 19 49 DB2INST1 PART1 4 2 18 19 49 DB2INST1 PART1 4 2 All tables have been successfully redistributed Important The redistribute utility issues SQL insert and delete operations ther
325. he instance and database partitions on which the task will be running and so on If you choose Grouping task for the type you can add several tasks into a group and then specify scheduling and failure and success conditions as well as related actions to the group Chapter 6 Administering databases 343 344 Grete y Testing task for demonstration purpose only Not categorized T Figure 6 47 General information input for a new task 3 Enter the command script for the new task Here you can input the script for the task By default the semicolon character is used as the DB2 statement termination character If you want you can change it Our sample script is shown in Figure 6 48 connect to itsodb runstats on table db2inst1 item connect reset Figure 6 48 Command script input for the new task 4 Defining the running properties setting You can define the specific success code for your task and choose if DB2 stops execution when a failure occurs during the task execution In our example we choose Stop execution at first return code that is failure when failure happens Figure 6 49 on page 345 Up and Running with DB2 on Linux Edit Task Properties Runstats Task Gree RUNSUCCEED O O OO O O UUU Figure 6 49 Run properties for the task Schedule the task You can schedule the task to run at a designated time only once or repetitively depending on your actual situation Fig
326. he parent folder DataProject Eile name Empsalary sal e Figure 8 20 Save the query in the data project The query appears in the Data Project Explorer under the SQL Scripts folder The query can be tested by right clicking EmpSalary sql and selecting Run SQL The result is presented in the Data Output view as shown in Figure 8 21 on page 480 Chapter 8 Application development 479 Properties Tanks Problems Error Log Model Report Jer evel T deas Bookmarks EmpSalary sq EmpSalary sq Messages Parameters Results Profiling Data EMPNO LASTNAME DEPTNO DEPTNAME 000280 SCHNEIDER E11 OPERATIONS SPRINGER E11 OPERATIONS SETRIGHT E11 OPERATIONS PARKER Eli OPERATIONS WONG E21 SOFTWARE SUPPORT ALONZO E21 SOFTWARE SUPPORT Figure 8 21 Data Output view The Data Studio allows you to easily create and run queries However you are not limited to the graphical method to create queries You can also enter the SQL statement as text directly When creating your query manually you can get help by using Content Assist Figure 8 22 which can be invoked by pressing the shortcut keys Ctrl Space bar or right clicking the query and selecting Content Assist 7 j EmpSalary sql x m B Outline K SELECT DE INSTL EMPLOYEE FMPNO DE2 INSTL FMPLOYEE DE INSTL DEPARTMENT DEP TNO IE2INSTL DEPARTMENT DEP TNAME FRO FIRSTNME VARCHAR 12 MIDINIT CHAR 1
327. hical user interface You need this software if you want to use the DB2 Setup wizard a graphical installer to install DB2 or any DB2 graphical tools gt Table 2 6 provides additional package requirements for SUSE Linux and Red Hat distributions for DB2 9 5 For a single partition database only ibaio and compat libstdc packages are required Table 2 6 Package requirements for Linux SLES 10 SP1 x86_64 Contains the asynchronous libaio 0 3 104 14 2 x86_64 rpm library required for DB2 SLES 10 SP1 x86 servers libaio 0 3 104 14 2 i586 rpm RHEL 5 x86_64 libaio 0 3 106 3 2 x86_64 rpm RHEL 5 x86 libaio 0 3 106 3 2 i386 rpm compat libstdc SLES 10 SP1 x86_64 Contains libstdc so 5 compat libstdc 5 0 7 22 2 x86_ which is required for DB2 64 rpm servers and clients SLES 10 SP1 x86 compat libstdc 5 0 7 22 2 i586 rpm RHEL 5 x86_64 compat libstdc 33 3 2 3 61 x86 _64 rpm compat libstdc 33 3 2 3 61 i38 6 rpm RHEL 5 x86 compat libstdc 33 3 2 3 61 i38 6 rpm SLES 10 SP1 x86_64 Korn Shell This package is ksh 93r 12 28 x86_64 rpm required for partitioned RHEL 5 x86_64 database environments ksh 20060214 1 4 x86_64 rpm Chapter 2 Installation 33 openssh SLES 10 SP1 x86_64 This package contains a set openssh 4 2p1 18 25 x86_64 rpm of server and client RHEL 5 x86_64 programs that allows users openssh 4 3p2 24 el5 x86_64 rp to run commands on and m from remote computers via openssh clients 4 3p2 24 el5 x86
328. his command mnt dvd represents the mount point of the DVD 4 Enter the db2_install command to start the db2_install script 5 Enter the product keyword when db2_install prompts you for it For example to install DB2 Workgroup Server Edition enter WSE The installation directory for DB2 on Linux is INSTHOME sdllib Configuring TCP IP communications After installing DB2 using db2_install you must configure your instance with the TCP IP protocol in order for it to accept requests from remote DB2 clients Follow these steps 1 Update the database manager configuration file on the server To do so a Log in to the system as the instance owner b Update the SVCENAME parameter in the DBM configuration file You can specify the port number For example we entered db2 update dbm cfg using SVCENAME 50001 You can check your SVCENAME by entering db2 get dbm cfg grep SVC Chapter 2 Installation 65 2 Set the DB2COMM registry variable to tcp ip which will start the DB2 communications manager when the database manager is started Enter the following command as the instance owner db2set DB2COMM tcpip Stop and restart the instance in order for these changes to take effect db2stop db2start 2 3 2 Root installation For root installation you can use one of the following methods to install both single partition and multi partitioned database environments gt gt gt DB2 Setup wizard Response file installati
329. his entry includes the database partition server number node number the TCP IP host name of the server where the database partition server resides and a logical port number for the database partition server If you are installing a partitioned database environment with three machines and a logical database partition server on each machine the updated db2nodes cfg will appear similar to 0 ServerA 0 1 ServerB 0 2 ServerC 0 If you are installing a partitioned database environment with two machines and two logical database partition servers on each machine the updated db2nodes cfg will appear similar to 0 ServerA 0 1 ServerA 1 2 ServerB 0 3 ServerB 1 or 0 ServerA 0 1 ServerB 0 2 ServerA 1 3 ServerB 1 Example 2 28 shows the content of the db2nodes cfg in our sample Example 2 28 db2nodes cfg db2inst1 mensa db2home db2inst1 gt more sqllib db2nodes cfg 0 mensa 0 1 gemini 0 Chapter 2 Installation 85 86 Enabling ssh To configure DB2 to use ssh as the remote shell utility 1 Configure DB2 to use ssh To set up DB2 to start with ssh support you must enable the DB2 registry variable DB2RSHCMD and point it to the path of the ssh command shell Example 2 29 shows the db2set command The default is for DB2 to use rsh therefore you only need to set this variable if you plan to use ssh Example 2 29 Enable DB2 to use ssh db2set DB2RSHCMD usr bin ssh 2 To verify the ssh configuration in the DB2 environment
330. iated with the lock escalation and the application ID component and function of DB2 that were used when the problem happens In addition detailed information specific to this occurrence of lock escalation is also displayed Example 7 14 DB2 administration notification log 2008 02 07 15 34 44 809250 Instance db2inst1 Node 001 PID 10328 db2agntp ITSODB 1 TID 3506432320 Appid NO db2inst1 080207233036 data management sqldEscalateLocks Probe 2 Database ITSODB ADM5500W DB2 is performing lock escalation The total number of locks currently held is 816 and the target number of locks to hold is 408 2008 02 07 15 34 44 859382 Instance db2inst1 Node 001 PID 10328 db2agntp ITSODB 1 TID 3506432320 Appid N0 db2inst1 080207233036 data management sqldEscalateLocks Probe 3 Database ITSODB Up and Running with DB2 on Linux ADM5502W The escalation of 813 locks on table DB2INST1 ITEM to lock intent X was successful 7 4 2 DB2 diagnostic log db2diag log The Administration Notification log is the primary log file intended for use by database and system administrators Administration notification log messages plus other details based on the setting are also logged to the db2diag log using a standardized message format The db2diag log file is intended for use by DB2 Support for troubleshooting purposes and it is the most often used file for DB2 problem investigation The file db2diag log file also is located under the directo
331. ibuted data sources Figure 1 1 shows an example of the scalable three tier architecture Tier 1 Client application or Web browser Tier 2 Application server cluster Load balancer proxy Application Application Application Tier 3 Partitioned databases failover cluster Database cluster Failover cluster in standby mode Figure 1 1 Sample scalable three tier architecture Up and Running with DB2 on Linux Tier 1 represents clients that connect to the application through an intranet or Internet Tier 2 is the application hosted in an application server such as WebSphere A load balancer and a proxy component distribute the requests equally to the various application servers If the traffic increases new application servers can be added easily in order to increase the throughput Tier 3 is the database tier It consists of two partitioned database clusters If the load on one database cluster increases a partition can be added to the database cluster easily to adhere to the new load The standby cluster is a copy of the running cluster In case of an outage of the primary database cluster the application server requests will be transparently redirected to the standby cluster In Chapter 8 Application development on page 425 you can see a more detailed description of how applications can be configured to implement the various tiers OLTP comp
332. icator settings for the DMS table space 1 For test purposes we change the AUTORESIZE parameter for table space from the default YES to NO Chapter 7 Monitoring and troubleshooting DB2 361 a To configure the health indicator for DMS table spaces in the Health Center select Configure Health Indicator Settings to start the Health Indicator Configuration Launchpad panel as shown in Figure 7 8 There are current Bg db2inst1 Figure 7 9 Health indicator configuration launchpad b From the Health Indicator Configuration Launchpad Figure 7 9 you can view or change health indicator setting by clicking the appropriate button e Instance Settings apply to the instance e Global Settings apply to objects such as database table spaces and table space containers in the instance that do not have customized settings defined e Object Settings are customized settings that apply to individual objects such as databases table spaces and table space containers In our sample we set the health indicator for a specific table space by clicking Object Settings On the Object Health Indicator Configuration panel Figure 7 10 on page 363 click the ellipsis g on the Object field 362 Up and Running with DB2 on Linux Object Health Indicator Configuration lt Select an object to view its health indicators gt SEDET TIS ETENI Figure 7 10 Object health indicator configuration c On the pop up panel Figure 7 1
333. ile package LINE MESSAGES FOR test_emb sqc SQLOO60W The C precompiler is in progress SQLO091W Precompilation or binding was ended with 0 errors and 0 warnings db2inst1 puget gt cc c I home db2inst1 sqllib include test_emb c db2inst1 puget gt cc o test_emb L home db2inst1 sqllib lib 1db2 test_emb o db2instl puget gt test_emb 000290 000310 200310 200330 200340 If you want to run this program on another database you have to bind the package first by issuing the following command db2 bind test_emb bnd Otherwise you will receive a 805 SQL error Note You can obtain more documentation in Developing Embedded SQL Applications SC23 5852 Administrative API The administrative API offers an application interface for different programming languages It allows you to perform a variety of administrative commands on the database from your application For instance you can start the database or you can create table spaces Up and Running with DB2 on Linux You can obtain more details about the API in the Information Center by selecting Database administration Administrative interfaces Administrative APIs and in Administrative API Reference SC23 5842 UDF in C One of the supported programming languages for user defined functions UDFs is C UDFs are a good choice if you want to access the same business logic from multiple applications and if it is difficult to share a common API After the program
334. ile systems if you are using a volume manager gt Ensure that you have sufficient log file space prior to migration We recommend that you significantly increase the values of LOGFILSIZ LOGPRIMARY and LOGSECOND to prevent log file space from running out The amount of required space depends on your system setup Also on partitioned database environments you only need to increase the log space in the catalog database partition server 170 Up and Running with DB2 on Linux For instance if you want to change the size of LOGFILSIZ from 1000 to 2000 connect to the database and enter the following command db2 update db cfg using logfilsiz 2000 gt Ensure that you have enough free pages in the corresponding index table space to account for one additional page per index on populated tables before Populating tables in new databases created in DB2 9 5 real time statistics are enabled by default in these newly created databases Enabling deferred cleanup rollout by setting DB2_MDC_ROLLOUT to DEFER or when DB2WORKLOAD is set to SAP Reorganizing or recreating indexes on populated tables 4 1 2 Planning considerations DB2 9 5 brings new features to enhance performance and manageability Several features and certain functionality are also discontinued The default values for several configuration parameters and registry variables have changed and you need to check them Creating a database to enable new features Migra
335. ility Also certain communication software packages are required which are discussed in 2 1 7 Additional software requirements on page 32 Chapter 2 Installation 29 2 1 6 Kernel parameter values 30 You might be required to update several of the default kernel parameter settings for DB2 to run successfully on Linux The default values for particular kernel parameters on Linux are insufficient when running a DB2 database system Note You must have root authority to modify kernel parameters With Version 8 and later DB2 checks values of the kernel sem kernel msgmni and kernel shmmax parameters automatically at DB2 start time and changes them for you if the current values are not optimal The db2start command gt Changes SEMMNI kernel parameter to 1024 gt Changes MSGMNI kernel parameter to 1024 gt Changes SHMMAX kernel parameter to 268435456 32 bit or 1073741824 64 bit Manually updating the kernel shmmax kernel msgmni and kernel sem parameters prior to root installations is no longer required However for non root installations you must check these kernel parameters before installation and update them if needed Manually updating kernel parameters If any of the default kernel parameter settings do not meet the requirements of your particular system you can update them manually To check your current shared memory segment semaphore array and message queue limits use the ipcs 1 command Your output
336. improve the performance If you are migrating from Version 8 2 consider using the following features YYYY Y Self tuning memory Large record identifiers RIDs Data compression Label based access control Trusted context If you are migrating from Version 9 and already use the previous features now you might want to enable the new DB2 9 5 features If you were migrating from Version 8 gt gt gt Enable the automatic agent configuration for your databases Enable the use of non buffered I O operations Enable automatic statistics collection that uses real time statistics Enable the use of the Workload Manager functionality In partitioned database environments take advantage of single system view backups by issuing the BACKUP DB command with the ON ALL DBPARTITIONNUMS clause You can read more details in Chapter 6 Administering databases on page 227 4 2 6 Migrating the DB2 Administration Server In a partitioned database system a separate DB2 Administration Server DAS service typically runs on each machine in the cluster A separate DAS service on each machine allows each machine to act as a coordinator node for requests 182 Up and Running with DB2 on Linux issued to the instance from the Control Center or the Configuration Assistant This design reduces the overhead that exists when one administrative coordinator node is spread across multiple partitions in an instance and helps to balance incoming
337. in Example 8 25 on page 455 D products xml E lt products gt E lt product gt A pid E lt product gt E por lt description gt E lt description gt Legend D document node E element nodes A attribute nodes T text nodes Figure 8 3 Storage layout for products xml 8 4 2 Using XML data 456 In this section we demonstrate by examples how you can use XML data in DB2 Example 8 26 on page 457 shows the Data Definition Language DDL to create a simple XML table PRODUCTS for storing the document ID the timestamp and the XML document Up and Running with DB2 on Linux Example 8 26 Create a table with an XML column CREATE TABLE product entityid INTEGER NOT NULL lastchange TIMESTAMP NOT NULL xdata XML PRIMARY KEY entityid J3 We insert a few records into the PRODUCT table as shown in Example 8 27 Example 8 27 Insert XML data into the product table insert dml INSERT INTO product entityid lastchange xdata VALUES 0 CURRENT TIMESTAMP lt description gt lt name gt Fleece jacket lt name gt lt price gt 19 99 lt price gt lt description gt 1 CURRENT TIMESTAMP lt description gt lt name gt Nylon pants lt name gt lt price gt 9 99 lt price gt lt description gt 2 CURRENT TIMESTAMP lt description gt lt name gt Si1k pants lt name gt lt price gt 9 99 lt price gt lt description
338. ind the Tables folder 2 Click Tables Any existing tables are displayed in the pane on the right side of the panel the contents pane 3 Right click the table that you want in the contents pane and select Import from the pop up menu The Import notebook opens Refer to Figure 6 31 which is a sample for using IMPORT from the Control Center Import table ITEMIMP db2backup datamove itemimp2 msg e OK Cancel snow Command _ Herp Figure 6 31 Using IMPORT within the DB2 Control Center Within the Control Center we set the Commit frequency number of records value COMMITCOUNT parameter to AUTOMATIC 1 as shown in Figure 6 32 on page 310 Chapter 6 Administering databases 309 310 Import table ITEMIMP E E E E j Figure 6 32 Import options in the Control Center When AUTOMATIC is specified import internally determines when a commit needs to be performed The utility will commit for either one of two reasons gt To avoid running out of active log space gt To avoid lock escalation from the row level to the table level Figure 6 33 shows the SQL command that was generated by the Control Center CONNECT TO ITSODB IMPORT FROM db2backup datamove item ixf OF IXF COMMITCOUNT AUTOMATIC MESSAGES db2backup datamove itemimp2 msg REPLACE INTO DB2INST 1 ITEMIMP CONNECT RESET Figure 6 33 Generated IMPORT command In a partitioned database environment the import utility can be enable
339. ing DB2 clients 4 2 1 Pre migration tasks Perform the following steps to prepare for a safe and successful migration 1 The first step to migrate your environment is to determine if you can migrate your existing instances to a DB2 9 5 copy that you have a Determine the node type by using the following command db2 get dbm cfg grep Node type Example 4 1 on page 174 shows the node type of an Enterprise Server Edition DB2 system Chapter 4 Migration and fix packs 173 Example 4 1 Node type dpfusrl gemini gt db2 get dbm cfg grep Node type Node type clients Enterprise Server Edition with local and remote b Review Table 4 2 to determine the instance type and whether the instance migration is supported Table 4 2 Node types Node type Migration support client Default type Client gt Migration to a client a stand alone a for DB2 clients wse or an ese instance is supported stand alone Default type for DB2 Personal Edition PE wse Default type for DB2 Workgroup Server Edition WSE ese Default type for DB2 Enterprise Server Edition ESE Database server with local clients Database server with local and remote clients Partitioned database server with local and remote clients or Enterprise Server Edition with local and remote clients gt Migration to a stand alone a wse or an ese instance is supported Migration to a client instance is unsupported Migrati
340. ings is listed to the right of the equal sign Refer to Quick Beginnings for DB2 Servers GC23 5864 for guidance about configuring these parameters You can tailor your custom response file To give you an idea of the final product Example 2 25 shows a response file db2ese rsp that is generated by the DB2 Setup wizard Example 2 25 Sample response file db2ese rsp Generated response file used by the DB2 Setup wizard generation time 2 7 08 11 15 AM Product Installation LIC_AGREEMENT ACCEPT PROD ENTERPRISE_SERVER_EDITION FILE opt ibm db2 vV9 5 INSTALL_TYPE TYPICAL F E DAS_CONTACT_LIST LOCAL DAS_SMTP_SERVER smtp itsosj sanjose ibm com Up and Running with DB2 on Linux DAS user DAS_USERNAME dasusrl DAS_UID 997 DAS_GID 1003 DAS_GROUP_NAME dasadml DAS_HOME_DIRECTORY home dasusr1 DAS_PASSWORD 3463322748282905151779356453226535001322719040555913873342519614033763535200416 25453423 ENCRYPTED DAS_PASSWORD Instance properties INSTANCE instl inst1 TYPE ese Instance owning user inst1 NAME db2inst1l inst1 UID 999 inst1 GID 1001 inst1 GROUP_NAME db2iadml inst1 HOME DIRECTORY db2home db2inst1l inst1 PASSWORD 3463322748282905151779356453226535001322719040555913873342519614033763535200416 25453423 ENCRYPTED inst1 PASSWORD inst1 AUTOSTART YES inst1 SVCENAME db2c_db2inst1 inst1 PORT_NUMBER 50001 inst1 FCM_PORT_NUMBER 60001 inst1 MAX_LOGIC
341. ion 7 H Conversion t i oY LA Web browser of Onon Batch application an US user TR running in a o ISO8859 1 single byte Database UTF 8 i codepage environment ISO8859 1 No conversion Interface file Figure 3 3 Codepage conversion scenario Chapter 3 Post installation tasks 95 This is a typical application architecture with one database which is accessed by a Java 2 Platform Enterprise Edition J2EE application from an application server and a batch application which extracts data The J2EE application is accessed by the users using Web browsers The database is created in UTF 8 format The J2EE application also uses the data in UTF 8 format The batch application runs on a single byte environment and converts the data into IS08859 1 format Because this application is a worldwide application the user community uses different codepage setups in their Web browsers DB2 automatically converts the codepage between the client and the server For applications this conversion probably needs to be implemented in the code In Figure 3 3 on page 95 we note where a codepage conversion of the transferred data is necessary Depending on your architecture you can have many places where a codepage conversion might be necessary You must decide before the database creation what codepage you want to use for your database
342. ion J2EE applications You might use it if you create Web services that access your data Java This perspective is for developing Java applications Team Synchronizing This perspective offers you the tools for synchronizing your code with the code repository Views A view is a representation of a resource in a project A resource can be a certain type of file or an object in the database All views of a certain resource are synchronized between each other automatically which means that if you change anything in one view you can see the result immediately in all other views that represent the same resource The sample perspective shown in Figure 5 13 on page 212 has the following views gt gt gt Data Project Explorer This view lists the projects on which you are working in a hierarchical structure Database Explorer This view shows the defined database connections It shows the database objects of the related connection in a hierarchical structure Editor Located in the center the Editor is the main working pane In our example you see an Extensible Markup Language XML editor which Chapter 5 IBM Data Studio 213 214 currently has an XML file opened It shows the XML file as a tree structure and allows you to modify it At the top of the editor view you can see several tabs where you can switch between various editors gt Outline The outline view shows the current object in the editor pane in an
343. ion to fix the errors before the migration Chapter 4 Migration and fix packs 177 Example 4 6 db2ckmig output dpfusr1 mensa opt ibm db2 V9 5 bin gt more dpfhome dpfusr1 db2ckmig 1log Version of DB2CKMIG being run VERSION 9 5 4 2 2 Install DB2 Version 9 5 Install DB2 in all of the machines of the partitioned environment We provide the installation details in Chapter 2 Installation on page 25 4 2 3 Migrating instances and databases 178 All of the steps that we have performed up to now are to prepare for the instances and databases migration The db2imigr command is used to migrate the instances to the Version 9 5 format The db2 migrate database command is used to migrate the databases The db2imigr command performs these tasks gt Check cataloged databases to make sure that they are ready for migration through db2ckmig gt Migrate your instance to a Version 9 5 instance gt Update the system and local database directories to the Version 9 5 format gt Merge the prior 9 5 version DBM configuration settings presented in your environment with new Version 9 5 DBM configuration settings In the rest of this section we guide you through a procedure to complete the migration The steps are 1 Log in as the instance owner to the database partition server that owns the instance The first entry of the db2node cfg file shows the database partition server that owns the instance Example 4 7 shows a db2nodes cfg
344. ion with other enterprise DB2 and Informix data sources DB2 Enterprise 9 5 includes table partitioning high availability disaster recovery HADR online reorganization materialized query tables MQTs multidimensional clustering MDC query parallelism connection concentrator the governor and Tivoli System Automation for Multiplatforms DB2 Database Partitioning Feature DPF is available as part of the DB2 warehouse products This feature allows DB2 Enterprise 9 5 clients to partition a database within a single system or across a cluster of systems The DPF capability provides the client with multiple benefits including scalability to support extremely large databases or complex workloads and increased parallelism for administration tasks Products for accessing existing and host data With the following DB2 products you can extend your enterprise system to access the existing system DB2 Connect Personal Edition provides the application programming interface API drivers and connectivity infrastructure to enable direct connectivity from Windows and Linux desktop applications to System z and System i database servers This product is specifically designed and licensed for enabling two tier client server applications running on individual workstations and therefore is not appropriate for use on servers DB2 Connect Enterprise Edition is a combination of DB2 Connect server and Data Server Client software designed to address the
345. ions for shared resources IBM Installation Manager and package groups On the first panel of the Location tab Figure 5 4 on page 203 specify the paths for the shared resources directory and the IBM Installation Manager The shared resources directory contains resources that can be shared by one or more package groups We use the default locations Note You can specify the shared resources directory only at the first time that you install a package You cannot change the directory location unless you uninstall all packages Up and Running with DB2 on Linux TT IBM Installation Manager Got Install Packages Select a location for the shared resources directory and a location for Installation Manager a Install License Location Feature Summary When you install packages files are stored in two locations 1 The shared resources directory resources that can be shared by multiple packages A 2 The installation directory any resources that are unique to the package that you are installing Important You can only select the shared resources directory the first time you install a package with the IBM Installation Manager For best results select the drive with the most available space because it must have adequate space for the shared resources of future packages Shared Resources Directory opt IBM SDP70Shared Browse once installed IBM Installation Manager will be used to install update modify manage
346. iple partitions during your Linux OS installation It has become customary for certain basic directories such as db2home or software in our example to be placed in separate file systems or partitions for several reasons gt Disk capacity There is a limited amount of space on each disk and you might run out of space if you use a single disk for multiple purposes gt Performance The root directory has to be searched linearly every time any path name in Linux is accessed If the root directory is cluttered this clutter will impair the performance of the entire system gt Backup It is better to separate important and frequently changing data from massive and seldom changing data This way you can save system resources by backing up certain file systems more frequently than other file systems gt User convenience It is easier to find things if the naming convention is well organized File system configuration or partitioning is typically performed by using the fdisk tool For SUSE you can also use the graphical YaST tool Linux provides several journal file system formats such as ext3 JFS VxFS and ReiserFS In our example for database related file systems we use the ext3 format with the journal mode to create a journal file system To show all defined file systems issue the df command as shown in Example 2 1 This command shows the output for a partitioned database environment For a single partition environment
347. ipse IDE instead of installing a new one See Figure 5 6 on page 205 204 Up and Running with DB2 on Linux EJ IBM Installation Manager Woks Install Packages Select the check box only if you want the packages you are installing to extend an existing version of Eclipse N nstal License Location Feature immar Packages are bundled with a version of the Eclipse integrated development environment IDE or workbench Click Next for this default installation However if you already have a compatible version of the Eclipse IDE on your system you can extend that version of Eclipse instead of installing a new one When you extend Eclipse the package functions are available in your Eclipse IDE but the package files are still installed in their own directory For more information see the installation guide for a package that you are installing Extend an existing Eclipse Eclipse IDE Eclipse JVM Figure 5 6 Eclipse version 8 Under the Feature tab you can select the Data Studio features to be installed The first panel is for selecting the language Other features are listed in the second panel for your selection See Figure 5 7 on page 206 Chapter 5 IBM Data Studio 205 IBM Installation Manager Sjm x Install Packages ra Select the features you want to install S Insta License cat Features umm gt Features M s IBM Installation Manager
348. ipt 4 When db2_install prompts you for the installation path enter no if you do not want to change the default directory The default installation directory for the DB2 copy on Linux is optiibm db2 V9 5 5 When db2_install prompts you for the product keyword enter ESE Post installation tasks After installing DB2 using db2_install Create group and user IDs if you have not already created them Create a DB2 Administration Server DAS Create a DB2 instance Create links for the DB2 files optional Configure TCP IP communications for the DB2 instance aorRoNns Up and Running with DB2 on Linux Create group and user IDs Refer to 2 2 6 User and group setup on page 50 Create a DB2 Administration Server DAS The DAS is required if you plan to use the DB2 graphical tools such as the Control Center and the Task Center You need to have a DAS user created before creating the DAS Here is the procedure 1 2 Log in as root Issue the following command to create the DAS DB2DIR instance dascrt u DASuser where DB2DIR is the instance directory where the DB2 copy is installed For the u parameter enter the DAS user that you created for this machine For example opt ibm db2 V9 5 dascrt u dasusrl Create a DB2 instance Use the db2icrt command to create a new instance 1 2 Log in as root Enter the following command DB2DIR instance db2icrt a AuthType u FencedID InstNme In this comma
349. ir first occurrence in this information with a trademark symbol or these symbols indicate U S registered or common law trademarks owned by IBM at the time this information was published Such trademarks may also be registered or common law trademarks in other countries A current list of IBM trademarks is available on the Web at Copyright and trademark information at http www ibm com 1legal copytrade shtml The following terms are trademarks of the International Business Machines Corporation in the United States other countries or both Redbooks logo AIX AS 400 Blox ClearCase DataStage DB2 Connect DB2 developerWorks Distributed Relational Database Architecture DRDA eServer Everyplace i5 OS IBM Informix iSeries OpenPower OS 390 OS 400 Passport Advantage POWER PowerPC pSeries purexXML The following terms are trademarks of other companies Rational Redbooks REXX System i System p System z System z9 Tivoli WebSphere z OS Z9 zSeries SAP and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries Oracle JD Edwards PeopleSoft Siebel and TopLink are registered trademarks of Oracle Corporation and or its affiliates Snapshot and the NetApp logo are trademarks or registered trademarks of NetApp Inc in the U S and other countries In
350. istering DB2 systems and developing applications with DB2 This client also includes add ins for Eclipse and Microsoft Visual Studio 2005 development environments Up and Running with DB2 on Linux Use this client if you need database administration support and application development using an application programming interface API IBM Data Server Runtime Client The Runtime Client is a lightweight non graphical client that provides the functionality required for your application to access DB2 servers It provides application support to run applications that use embedded SQL CLI Java Database Connectivity JDBC SQLJ ODBC Object Linking and Embedding OLE DB NET and Hypertext Preprocessor PHP interfaces Use this client if you need Command Line Processor CLP support and basic client functionality for application runtime and deployment support IBM Data Server Driver for ODBC CLI and NET This driver is a lightweight deployment solution for Windows applications Use it if you need runtime support for the DB2 CLI API ODBC API and NET API for Windows applications without needing to install the Data Server Client or the Data Server Runtime Client The client selection depends on your application environment Only the IBM Data Server Client provides the BIND support All client versions are available on the AIX HP UX Linux Solaris and Windows platforms For more information about the IBM Data Server clients an
351. istributions SLES 9 and RHEL 4 x86 x86_64 IA64 and POWER Linux distributions SLES 9 and RHEL 4 on this architecture VERITAS Storage Foundation 4 1 VxFS ext2 ext3 or ReiserFS on small computer system interface SCSI No file system caching File system caching System 2 disks using Fibre Channel protocol FCP Raw devices Raw devices can only be used for DMS storage DMS table spaces require more administration but they provide superior performance Raw device containers generally provide the best performance because the database accesses the disk directly bypassing all of the operating system cache and locking However as mentioned in File systems on page 40 Direct I O file systems DIO reduce the gap between DMS files and raw devices For a detailed procedure of how to set up raw I O on your Linux machine refer to Linux documentation Chapter 2 Installation 41 42 Note Since DB2 Version 9 1 the previous raw I O method that required binding the block device to a character device using the raw utility is deprecated This raw I O method is also deprecated in the Linux operating system and will be removed in a future release of Linux You can use the block device as a DB2 DMS table space container now The block device method uses Direct I O to achieve an equivalent performance compared to using the character device method File system configuration We recommend that you create mult
352. ition rerai anit E eee xix Chapter 1 Introduction 00 0000 c cee ee 1 1 1 Overvia Wis iiei Fate tects Gated Gutta aie S ea bed hearin 2 1 2 DB2 for Linux features and offerings 00 0 eee 3 t21 10 lt ee a aaa a a ia E a rE 3 1 2 2 Supported platforms auauua 7 1 2 3 DB2 products and packageS naaa auaa 8 1 3 DB2 environment eirca seii s ar aia E eee 11 1 3 1 Deployment topologies 2 0 0 ee eee 11 1 3 2 DB2 database objects 2 0 cee eee 14 1 4 Parallelism with DB2 0 0 cee eee 16 1 4 1 SMP environments 000 0c eee eee 17 1 4 2 Database clusters 0 0 cee eee 18 1 4 3 Partitioned database 1 2 ee 20 Chapter 2 Installation 000000 ee 25 2 1 Basic requirements uau cicca rane Ea tees 26 2 1 1 Hardware supported by DB2 0 00 eee ee 26 2 1 2 Linux distributions supported by DB2 006 26 2 1 3 Required disk spaces 0 cece tt ee 27 2 1 4 Memory requirements 2 0 0 0 cee ees 28 2 1 5 Communication requirements 0000 0c eee eee ee 29 2 1 6 Kernel parameter values 1 0 0 eee es 30 2 1 7 Additional software requirements 00 e eee eee 32 2 2 Installation considerations and planning 00e eae 35 2 2 1 Considerations 0 00 eee 36 2 2 2 Installation methods e cernens ne a e E ee 38 2 2 3 Storage planning sssaaa aaan 40
353. itted 2 Disconnecting from database End time Wed Feb 6 17 07 20 2008 successful home db2inst1 sqllib bnd db2move bnd db2instl gemini temp gt db2 get db cfg for itso grep Database Database Configuration for Database itso Database configuration release level 0x0c00 Database release level 0x0c00 Database territory BR Database code page 1208 Database code set UTF 8 Database country region code 55 Database collating sequence SYSTEM_819 Database page size 4096 Database is consistent YES 194 Up and Running with DB2 on Linux 4 6 Fix pack installation A DB2 fix pack is a collection of updates and fixes for Authorized Program Analysis Reports APARs We recommend that you keep your environment running up to date at the latest fix pack level Note Fix packs are cumulative Cumulative means that the latest fix pack for any given version of DB2 contains all of the updates from the previous fix packs for the same version of DB2 You can have multiple DB2 copies on the same system and those copies can be at different version and fix pack levels If you want to apply a fix pack to one or more DB2 copies you must install the fix pack on those DB2 copies one by one DB2 9 5 enhanced the procedure for applying DB2 fix packs Now updating the DB2 instance and DAS running db2iupdt and dasupdt are automated In addition binding occurs automatically at the first connection which means that after you start the
354. izer determines the degree of intra partition parallelism based on the number of processors and the type of query On OLTP systems turn intra partition parallelism off On OLAP systems consider turning intra partition parallelism on so that large queries can take advantage of several CPUs in a multiprocessor system Note For a complete and detailed description of all of the Database configuration parameters refer to the Information Center at http publib boulder ibm com infocenter db21 uw v9r5 index jsp topic com ib m db2 1luw admin config doc doc c0004555 htm Monitor and update DB configuration You can configure DB2 database settings either through the Control Center or the DB2 command line Control Center Use these steps to update database configuration parameters 1 Start the Control Center and expand the tree to the desired database 2 Right click the desired database name to open the pop up window and choose Configure Parameters Figure 3 23 on page 143 Up and Running with DB2 on Linux config Figure 3 23 Change database parameter from the Control Center There are two options to modify database configuration parameters gt Configure Parameters option Use this option to change specific parameters gt Configuration Advisor option This option is comparable to the autoconfigure command Using the Configure Parameters option By selecting the Configure Parameters option in the Control Center the f
355. l He has seven years of experience in DB2 and Informix He holds a degree in computer science from Universidade Estadual Paulista UNESP His areas of expertise include DB2 Engine and Business Intelligence Bl solutions including migrations and performance and tuning services He also is an IBM Certified Advanced Database Administrator for DB2 9 Copyright IBM Corp 2008 All rights reserved xiii Xiv Helmut Riegler is an IT Specialist working for the World Wide Learning Applications Development organization in Vienna He is the technical lead for the ongoing support of the learning applications He has been with IBM since 1998 and has broad experience in software development and database administration Before he joined IBM he developed CAD software He holds an Engineering degree in Electrical Engineering Lifang LF Liu is a Senior IT Specialist of the IBM Software Group IBM China His major job responsibilities are solution design and proposal delivery technical support at the presale stage and helping clients finish the Proof of Concept Proof of Technology PoC PoT part of their projects Lifang focuses on supporting DB2 online transaction processing OLTP business supporting large ISV OEM clients and selling DB2 SAP Prior to this position he was a DB2 worldwide L2 support engineer working in the Technical Support Center IBM China He is an IBM Certified Advanced Database Administrator of DB2 His areas of expertise incl
356. l command The general command syntax is db2_all commands If the command that you want to use does not follow the rah or db2_al1 command you will be prompted to enter a command by rah and db2_al11 In general if you specify the command that you want as a parameter on the command line you must enclose the command in double quotation marks if it contains any of the following special characters amp lt gt unsubstituted To obtain help information about the db2_a11 or rah syntax type either db2_all 2 or rah nou There are certain command prefix sequences in this context a prefix sequence is one or more special characters for db2_a11 and rah that can be used to control the command running mode such as gt Running commands in sequence or in parallel on all involved machines or partitions gt Running commands in the foreground or background gt Whether to execute an environment setting script before executing specific commands Table A 1 on page 495 shows several commonly used command prefix sequences Up and Running with DB2 on Linux Table A 1 Commonly used command prefix sequences for db2_all and rah D Runs the commands in sequence in the background Runs the commands in sequence in the background and terminates the command after all remote commands have completed Runs the commands in parallel in the background the commands in Runs the commands in parallel in the background in
357. lation Prior to Version 9 5 you were able to install products apply and roll back fix packs configure instances add features or uninstall products only if you had root authority Now you can install and service a non root DB2 on Linux platforms The DB2 installer automatically creates and configures a non root instance during a non root installation As a non root user you can customize the configuration of the non root instance during the installation You can also use and maintain the installed DB2 product without root authority Although non root Up and Running with DB2 on Linux installations have most of the functionality of root installations there are certain differences and limitations Table 2 7 shows several of them Table 2 7 Differences and limitations between root and non root installations Root installations Non root installations User can select installation directory noe products are installed under the user s home directory Instance creation Can create instances A single instance is during installation This is automatically created and the recommended configured Further method instances cannot be created in non root installations Number of DB2 instances Multiple One allowed Files deployed during Program files only Program files and instance installation Instances are created after files The DB2 product is installation ready for use immediately after installation DB2 Administration Serv
358. le 8 21 shows a simple Java UDF that receives one string as input and sends back a concatenated string to the output Example 8 21 Java UDF sample hello java public class hello public static String hello String paraml return Hello to paraml Chapter 8 Application development 453 454 Example 8 22 shows how to compile and install the program hello java You must replace lt path gt with the path name of the jar file Example 8 22 Compile and install hello java as UDF db2inst1 puget gt JRE home db2inst1 sqllib java jdk32 db2inst1 puget gt JRE bin javac hello java db2inst1 puget gt JRE bin jar cvf hello jar hello class added manifest adding hello class in 443 out 274 deflated 38 db2inst1 puget gt db2 CALL sqlj install_jar file lt path gt hello jar HELLOJAR DB20000I The CALL command completed successfully On 64 bit systems you have to use jdk64 instead of jdk32 Next we create a UDF in DB2 to use this Java routine as shown in Example 8 23 Example 8 23 Create the UDF in DB2 CREATE FUNCTION hello VARCHAR 40 RETURNS VARCHAR 60 FENCED EXTERNAL NAME HELLOJAR hello hello NOT VARIANT NO SQL PARAMETER STYLE java LANGUAGE java NO EXTERNAL ACTION The external name references the jar file HELLOJAR which was registered by the call sqij install_jar The first hello refers to the class name and the second hello refers to the method name Now we can run the UDF as shown in
359. lib java sqlj zip Browse coos uate e Figure 8 23 Create a new stored procedure Name and Language 2 Inthe SQL Statements panel we use all of the default values as shown in Figure 8 24 on page 482 Click Next Chapter 8 Application development 481 m 22 New Stored Procedur SQL Statements Create a new SQL statement or import an SAL statement that is saved in your project H7 O Statements Statement details Statement1 g SELECT EMPLOYEE EMPNO EMPLOYEE LASTNAME DEPARTMENT DEPTNO DEPARTMENT DEPTNAME FROM EMPLOYEE JOIN DEPARTMENT ON EMPLOYEE WORKDEPT amp DEPARTMENT DEPTNO WHERE EMPLOYEE SALARY lt 37000 Reute pe Create SOL Validate Figure 8 24 Create a stored procedure SQL Statements 3 In the Add Parameter panel Figure 8 25 we add an integer parameter with the name SALARY and leave the rest of values on the panel unchanged Click OK g EGGE O Add Parameter Parameter mode In O Out O Int Name SALARY SaL type INTEGER Length 0 Unit Byte Precision fo Scale 0 For bit data Figure 8 25 Add a parameter 482 Up and Running with DB2 on Linux 4 We are finished now with the Parameter panel in Figure 8 26 Click Next 3 New Stored Procedure O Parameters Specify parameters for the stored procedure SOL error handling code sa Exception v Parameters INTEG
360. line backup for each database a Os OA OD 0 If you are still using raw devices for database logging or table space containers you must change them to block devices 11 Install DB2 9 5 Server 12 Stop the instance 13 Make sure that there are no outstanding processes on the instance to be migrated 14 Verify that the databases in the instance can be migrated using db2ckmig and if necessary take actions to fix any problems 15 Migrate the instance to DB2 9 5 16 Preserve the db2diag log by renaming the file 17 Preserve the files indicated in the DIAGPATH parameter including dump files trap files and alert log files 18 Start the DB2 instance 19 Migrate the databases in the instance 20 Compare the database configuration settings after migration with the configuration settings before the migration and adjust them if required Chapter 4 Migration and fix packs 187 2 _ Reset the following configuration parameters to the value before the migration DIAGLEVEL LOGFILSIZ LOGPRIMARY LOGSECOND 22 Start up your database and review the administration notification log or the db2diag log file to verify that all database services are running properly and all buffer pools are activated 23 Update the statistics for system catalog tables and user tables particularly those tables that are critical to the performance of your SQL queries 24 Rebind the application packages to avoid implicit rebound overhead
361. list utilities show detail ID 331 Type RESTORE Database Name ITSODB Partition Number 0 Description tablespace TSDATA2 Start Time 02 21 2008 15 23 01 033971 State Executing Invocation Type User Progress Monitoring Completed Work 54837248 bytes Start Time 02 21 2008 15 23 01 033976 db2inst1 mensa gt db2 select UTILITY_TYPE substr UTILITY_DESCRIPTION 1 15 UTILITY_STATE DBPARTITIONNUM from SYSIBMADM SNAPUTIL UTILITY_TYPE 2 UTILITY_STATE DBPARTITIONNUM RESTORE tablespace TSDA EXECUTE 0 0 1 record s selected db2inst1 mensa gt db2 select SNAPSHOT_TIMESTAMP UTILITY_STATE PROGRESS _START_TIME PROGRESS _TOTAL_UNITS PROGRESS COMPLETED UNITS DBPARTITIONNUM from SYSTBMADM SNAPUTIL_PROGRESS Chapter 6 Administering databases 261 SNAPSHOT_TIMESTAMP UTILITY_STATE PROGRESS_START_TIME PROGRESS _TOTAL_UNITS PROGRESS COMPLETED_UNITS DBPARTITIONNUM 2008 02 21 15 23 03 523409 EXECUTE 2008 02 21 15 23 01 033976 54837248 0 1 record s selected db2instl mensa gt db2 list utilities ID 332 Type ROLLFORWARD RECOVERY Database Name ITSODB Partition Number 0 Description Online Tablespace Rollforward Recovery 7 Start Time 02 21 2008 15 25 20 435220 State Executing Invocation Type User Progress Monitoring Estimated Percentage Complete 0 db2instl mensa gt db2 list utilities show detail ID 332 Type ROLLFORWARD RECOVERY Database Name ITSODB Partition Numb
362. lity on page 336 1 Export data using the db2move command to a directory with enough space db2move ITSO export 2 Generate a Data Definition Language DDL script for your existing database using the db2100k command db2look d itso e o unicode ddl 1 x f 3 Create a Unicode database which is the default in DB2 9 5 db2 create database unidb automatic storage yes on database db2inst1 collate using SYSTEM_819_BR Up and Running with DB2 on Linux 4 Edit the DDL script unicode ddl which was created by db21ook for the new DB name Replace all occurrences of the database name to the new Unicode database name For example change connect to itso to connect to unidb Increase the column lengths for character columns in your tables because characters converted to Unicode can be expanded If you want to keep your existing database you must also change the file name specification for table spaces in the unicode ddl file Otherwise you can drop the existing database and use the same table space files 5 Recreate the database structure by running the edited DDL script db2 tvf unicode dd 6 Import data into the new Unicode database using the db2move command db2move unidb import Note The maximum large object LOB column size that the db2move command moves is 32 KB The db2move command will truncate LOBs over 32 KB Example 4 18 shows a conversion from a non Unicode database in DB2 UDB Ve
363. llel technology enables highly scalable performance on large databases by breaking the processing into separate execution components that can be run concurrently on multiple processors Elapsed times for queries can be dramatically reduced by processing the individual queries in parallel DB2 supports a scalable growth path to easily add more processing power to an existing system by either scaling up SMP scaling out massively parallel processing MPP or both 1 4 1 SMP environments In the past complex enterprise workloads have typically run on high end SMP symmetric multiprocessor machines A large number of processors running within the same machine and connected with a high bandwidth bus can deliver excellent performance Because DB2 for Linux shares much of its code with DB2 running on high end UNIX systems it inherits the ability to exploit SMP architectures The DB2 capability to run on SMP systems is only restricted by today s Linux SMP scalability DB2 can take advantage of multiple processors easily without setting up a clustered system This is called intra parallelism Very Large Database Figure 1 4 Database on a large SMP system Chapter 1 Introduction 17 1 4 2 Database clusters 18 The driving force behind using Linux clusters is that by distributing the load over several low cost servers running an open source operating system a larger task can be accomplished faster more reliably a
364. located in cdrom db2 license where cdrom is the root directory of your CD ROM Click OK To remove a license file select Remove from the License menu Setting up a license policy For DB2 Connect Enterprise Server Edition the license policy controls and monitors the number of users that can connect simultaneously to a DB2 Connect server For WebSphere Replication Server or WebSphere Federation Server the license policy controls and monitors the number of connectors to a non DB2 data source To set up the license policy using the License Center 1 Select Change from the License menu Chapter 3 Post installation tasks 161 162 2 In the Change License window select the type of license that you have purchased for your product Changing the enforcement policy The default enforcement policy is Soft Stop which means that all connections to DB2 databases are allowed to connect even when the license policy is violated When a violation occurs a license violation message is written to db2diag log The Hard Stop enforcement policy does not permit any connections that violate the license policy To specify the enforcement policy type 1 Select Change from the License menu 2 Select the appropriate radio button under Enforcement policy Generating a compliance report To verify the license compliance of DB2 features you can generate a compliance report It lists DB2 features out of compliance with your current product entitleme
365. lowing set of activities Select a maintenance activity to view its 3 Timing current settings To enable and disable automation of the activity and notification select the 4 Notification Automate and Notify check boxes To update the settings select the Configure Settings button 5 Activities 6 Summary Maintenance activity Maintenance window used Automate 4 Backup databa KUP Online Defragment table and index data REORG Offline Optimize data access RUNSTATS Online Maintenance activity settings The backup maintenance activity automatically backs up your database using the following settin Criteria Balance database recoverability with performance Media File system Location database db2inst1 NODE0000 SQL00002 DB2AUTOBACKUPS A NOTE Backup images will be automatically pruned from this i gt directory Please do not put any non automatic backup images in this directory as they will also be pruned Config J 4 Back Next gt Finish Cancel Figure 6 12 Select maintenance activity Configure automatic backup using the command line processor Enabling the automatic maintenance features is controlled by the automatic maintenance database configuration parameters as shown in Example 6 19 Example 6 19 Automatic maintenance parameters db2inst1 mensa db2home db2inst1 gt db2 get db cfg for itsodb grep Automatic Automatic maintenance AUTO_MAI
366. lpful if you work with many tables 6 3 1 Export data to files from database tables and views You can use the DB2 export utility to write data from a DB2 database to one or more files stored outside of the database You can then import or load the exported data into another DB2 database using the DB2 import or the DB2 load utility respectively Or you can import the data into another application such as a spreadsheet You specify the data to be exported by supplying a SELECT statement or by providing hierarchical information for typed tables Before invoking EXPORT you need to establish a connection to the database explicitly or implicitly You can invoke the export utility through the DB2 Command Line Processor CLP the DB2 Control Center by calling the ADMIN_CMD stored procedure or through an Application Programming Interface API Export table data through the CLP Example 6 46 is a sample to export data from a table named ITEM which is spread across two database partitions by using the DB2 CLP Example 6 46 Export all data from table ITEM db2inst1 mensa db2backup datamove gt db2 export to item ixf of ixf select from item SQL3104N The Export utility is beginning to export data to file item ixf SQL3105N The Export utility has finished exporting 3000000 rows Number of rows exported 3000000 The data across both database partitions has been exported You can export data for only one database partition such as
367. lt Set Template option Errors SOL Exception Parameters Java Type INTEGER Figure 8 29 Summary page 8 The procedure will be created It appears in the Data Project Explorer view under Stored Procedures and the code is displayed See Figure 8 30 on page 485 484 Up and Running with DB2 on Linux m Data Project Explorer X D EmpSalary sq 6 EMPSALARY sN H DataProject SAMPLE jdbe db2 localhost 50001 SAMPLE retrieve CREATE PROCEDURE EPSAILARY IN SALARY INTEGER SPECIFIC FMPSALARY A SAL Scripts DYNAMIC RESULT SETS l b gt EmpSalary sq NOT DETERMINISTIC LANGUAGE Java v C Stored Procedures EXTERNAL NAME FMPSALARY db2instl FMPSALARY eMP SALARY v 0EMPSALARY FENCED v Java Source THREADGAF E PARAMETER STYLE JAVA By EMPSALARY java 5 User Defined Functions C3 Web Services v XML G wsoL C XML Documents XML Schema Figure 8 30 The new procedure has been created 9 If you double click the Java program EMPSALARY java in the Data Project Explorer view the Data Studio opens the Java program In the Java code change this line WHERE EMPLOYEE SALARY lt 37000 to WHERE EMPLOYEE SALARY lt SALARY Then save the file You can see the change in the editor window as shown in Figure 8 31 0 EmpSalary sql B0 EMPSALARY f EMPSALARY java x grec stored Procedure mrsatary Package db2instl import java sql gr
368. lt salary gt 0035370 00 lt s p lt employee gt lt empno gt 200340 lt em name gt lt salary gt 0031840 00 lt sa pno gt lt lastname gt PARKER lt lastname gt lt firstname gt JOHN lt firs alary gt lt employee gt pno gt lt lastname gt SETRIGHT lt 1lastname gt lt firstname gt MAUDE lt f lt salary gt lt employee gt pno gt lt lastname gt SPRINGER lt lastname gt lt firstname gt MICHELLE 00 lt salary gt lt employee gt pno gt lt lastname gt WONG lt 1astname gt lt firstname gt HELENA lt firs alary gt lt employee gt pno gt lt lastname gt ALONZ0 lt lastname gt lt firstname gt R0OY lt first lary gt lt employee gt As a last example we demonstrate the usage of XSLT In Example 8 38 we create an auxiliary table for storing the XSLT document The record containing the XSLT document is used later for the transformation Example 8 38 Store the XSLT document create_xslt ddl CREATE TABLE xslt doc_id INTEGER NOT N xslt XML NOT N PRIMARY KEY doc_id J INSERT INTO xslt VALUES 1 Up and Running with DB2 on Linux ULL ULL lt xsl stylesheet version 1 0 xmins xsl http www w3 org 1999 XSL Transform gt lt xsl template match products gt lt html gt lt body gt lt h1 gt List of items lt h1 gt lt table border 1 gt lt tr bgcolor cccccc gt lt th align left gt Product lt th gt lt tr gt lt xsl apply templates gt lt table gt lt body gt lt html
369. machine participating in the partitioned database system You install a license key by adding a DB2 license file using the db21 icm command 1 Log in as root user or instance owner For a non root installation log in as the instance owner Enter the following command db2licm a lt filename gt where filename is the filename that contains the valid license information For example if you want to install the license key with the DB2 Workgroup Server Edition Authorized User Option enter the following command db2licm a db2wse_u lic On Linux the DB2 license keys are located in the DB2D Rilicense in a file called nodelock where DB2DIR is the instance directory where the DB2 copy is installed 2 3 5 Installing DB2 documentation DB2 Version 9 5 provides the DB2 Information Center and PDF documentation on separate DVDs These DVDs ship with your client and server DVDs gt DB2 Information Center DVD The DB2 Information Center gives you access to all of the information that you need to take full advantage of DB2 products It is installed separately from other DB2 products from its own DVD which means that you can install DB2 Information Center immediately after installing DB2 or at a later time You can install the DB2 Information Center on a machine that does not have DB2 installed such as your company s internal Web server which will save space on individual machines You can also access the DB2 Information Center
370. mands to add a database partition and the result of the command 130 Up and Running with DB2 on Linux db2start dbpartitiannum 2 ADD DBPARTITIONNUM HOSTNAME cetus itsosj sanjose ibm com PORT 1 WITH db2stop force db2star connect to ITSODB ALTER TABLESPACE TEMPSPACE1 ADD db2temp db2inst1 NODEOO02 ITSODB TEMPSPACE1 ON DBF ALTER DATABASE PARTITION GROUP SNG_O1 ADD DBPARTITIONNUM 2 WITHOUT TABLESPACES ALTER TABLESPACE SAMPLE_SNG ADD db db2inst1 NODEO002 ITSODB SAMPLE_SNG ON DBPARTITI connect reset he command completed successfully Explanation No errors were encountered during the execution of this command User response No action required Figure 3 16 Messages after the partition has been created After executing these commands all tables within the affected table spaces have to be redistributed Then click Redistribute in Figure 3 17 SN Add Database Partitions Launchpad arigis Figure 3 17 Redistribute partition Chapter 3 Post installation tasks 131 Then you get to the panel in Figure 3 18 ee Redistribute Database Partition Group Data KD Database instance name MENSA NDEASS9EE db2inst1 Select a database partition group then click redistribute to redistribute the data in that database partition group amongst its database partitions You may run the redistributions in parallel by specifying overlapping schedules in each redistribute wizard Database Partition Group
371. mber of active applications MAXAPPLS AUTOMATIC Average number of active applications AVG_APPLS AUTOMATIC To turn off STMM for a particular area use this command UPDATE DATABASE CONFIGURATION USING lt parameter gt MANUAL You can turn off STMM in general by executing this command UPDATE DATABASE CONFIGURATION USING SELF_TUNING_MEM OFF Buffer pools can be enabled or disabled for STMM individually by using the option SIZE AUTOMATIC ALTER BUFFERPOOL ibmdefaultbp SIZE AUTOMATIC Or use this command CREATE BUFFERPOOL lt bpname gt SIZE AUTOMATIC STMM can run in two modes gt You can limit the available size for memory tuning on the database level with the parameter DATABASE_MEMORY Then STMM will not increase the memory used by the database higher than this value If one area needs to be increased because it has more demand another area with less memory demand will be decreased accordingly gt You can leave the available memory size for tuning unlimited by setting the DATABASE_MEMORY parameter to AUTOMATIC In this case the available memory in the operating system limits the available memory for tuning STMM leaves a buffer for the operating system processes so that no paging occurs You can also limit the memory used by the instance by setting the value of the database manager configuration parameter INSTANCE_MEMORY to a particular value If you do not want to limit it you can leave the value at AUTOMATIC Note
372. md_64 gt db2top f collect file b 1 A Analyzing objects doing the most Cpu Total in function Sessions End of input stream reached size was 8514313 Top twenty performance report for Sessions between 01 17 40 and 01 22 26 Sort criteria Cpu _Total Rank Application_Handle Stat Percentage fromTime toTime sum Cpu _ Total 1 44930 35 4578 01 17 40 01 22 26 673060 2 44947 64 5422 01 17 40 01 22 26 1225140 3 65595 0 0000 01 17 40 01 22 26 0 4 44934 0 0000 01 17 40 01 22 26 0 5 83 0 0000 01 17 40 01 22 26 0 6 82 0 0000 01 17 40 01 22 26 0 7 81 0 0000 01 17 40 01 22 26 0 Performance report breakdown by 300 seconds fromTime sum Cpu Total Percentage Top Five in 300 seconds interval 5 et 01 17 40 1898200 100 0000 Rank Percentage Application_Handle Stat l 1 35 4578 44930 l 2 64 5422 44947 3 0 0000 65595 l 4 0 0000 44934 5 0 0000 83 Performance report breakdown by 0 5 hour 396 Up and Running with DB2 on Linux fromTime 01 17 40 Exiting sum Cpu Total Percentage Top Five in 0 5 hour interval 1898200 100 0000 Rank Percentage Application_Handle Stat 1 35 4578 44930 2 64 5422 44947 3 0 0000 65595 4 0 0000 44934 5 0 0000 83 7 4 Log files for troubleshooting This section discusses DB2 a
373. monitor data is allocated from the monitor heap Its size is controlled by the MON_HEAP_SZ configuration parameter The amount of memory required for monitoring activity varies widely depending on the number of monitoring applications and event monitors the switches set and the level of database activity SHEAPTHRES For private sorts this parameter is an instance wide soft limit on the total amount of memory that can be consumed by private sorts at any given time For shared sorts this parameter is a database wide hard limit on the total amount of memory consumed by shared sorts at any given time By reaching this limit no more shared sorts are allowed NUM_POOLAGENTS which can be set to AUTOMATIC For a Decision Support System DSS environment with which few applications connect concurrently set this value small For Online Transaction Processing OLTP with many concurrent connected Up and Running with DB2 on Linux applications set this value larger to prevent creating extra db2agents which is time consuming gt INTRA_PARALLEL For an OLTP environment set this value to NO because transaction throughput is more important than parallel work OLTP queries read update or insert only one or a few rows and therefore it does not make sense to split this work over more processes In a DSS environment typically most queries join many tables at one time We recommend that you set this value to YES so that DB2 can split the
374. mples are Concurrent Versions System CVS Subversion SVN Configuration Management Version Control CMVC and Rational ClearCase Share a project A project can be shared by right clicking the project name in the Project Explorer view and selecting Team Share Project Figure 5 17 x m Gy sta ne Y 72 gt pr ma New b SQL Sc Close Project Stored Copy GD User Di a Ca Webs P Delete a v XML i A F a E Impol Qe A Export f LA Expo b Ga xm gt oxm Refresh xsi Validate F ith 4j Compara WI Share Project Restore from Local History J 4 Database Expl PDE Tools O 4 Design a Properties i izi Dranart Figure 5 17 Share a project Data Studio asks for certain information such as the repository location about the source control application that you use and then synchronizes the resources from the workspace with the repository Up and Running with DB2 on Linux Note To use the team functions a code repository such as SVN or CVS is required You need to install and configure SVN or CVS separately because these repositories are not part of the Data Studio Linux provides packages for SVN and CVS When a workspace is shared you can synchronize it with the repository at any time and you can check in the code at certain checkpoints and perform all of the operations that are supported by your repository You have access to all previous che
375. mpleted successfully Backup successful The timestamp for this backup image is 20080201170437 Monitoring the backup database utility The backup database utility writes an entry into the database recovery history file for each backup You can query it using the LIST HISTORY command When the database backup is running you can use the LIST UTILITY command to monitor the progress of the backup utility as shown in Example 6 14 on page 243 The option WITH DETAILS is used in this example Up and Running with DB2 on Linux Example 6 14 LIST UTILITIES to monitor the backup db2instl mensa gt db2 list utilities show detail ID Type Database Name Partition Number Description Start Time State Invocation Type Throttling Priority Progress Monitoring Estimated Percentage Complete Total Work Completed Work Start Time ID Type Database Name Partition Number Description Start Time State Invocation Type Throttling Priority Progress Monitoring Estimated Percentage Complete Total Work Completed Work Start Time 327 BACKUP ITSODB 0 online db 02 21 2008 14 28 40 181501 Executing User Unthrottled 29 304720105 bytes 87135441 bytes 02 21 2008 14 28 40 181510 135 BACKUP ITSODB 1 online db 02 21 2008 14 28 41 835045 Executing User Unthrottled 98 224002009 bytes 220510145 bytes 02 21 2008 14 28 41 835055 The same information can be retrieved using the SNAPUTIL administrative view or th
376. nd DB2DIR is the location where the current version of the DB2 database product is installed AuthType represents the authentication type SERVER CLIENT or SERVER_ENCRYPT for the instance If you do not specify this parameter the default authentication type SERVER is assigned FencedID represents the name of the DB2 fenced user InstNme represents the name of the instance that you are creating The name of the instance must be the same as the name of the instance owning user This instance will be created in the home directory of the instance owning user For example we entered opt ibm db2 V9 5 instance db2icrt u db2fencl db2instl Create links for DB2 files optional If you are developing or running applications you might want to create links for the DB2 files to the usr lib directory and links for the include files to the Chapter 2 Installation 77 78 usr include directory Creating these links will help you avoid having to specify the full path to the product libraries and to the include files If you create links on one version of DB2 the links on the other version will be overwritten To create links 1 Log in as root 2 Enter the following command opt ibm db2 v9 5 cfg db21n Assume that DB2 is installed to the default installation directory Note If multiple versions or copies of DB2 coexist we recommend that you do not use the db21n command to create links for DB2 files Consider using
377. nd all buffer pools are activated There are new registry variables new configuration parameters and new default values for the registry variables and the configuration parameters introduced in DB2 9 5 that can impact the behavior of the DB2 server Also there are several deprecated and discontinued variables For more information refer to http publib boulder ibm com infocenter db21uw v9r5 topic com ibm db2 1uw qb migration doc doc t0050543 html Update statistics You must update the statistics for system catalog tables using the RUNSTATS command You might want to run the runstats command on tables particularly those tables that are critical to the performance of your SQL queries The runstats command updates statistics about the physical characteristics of a table and its associated indexes The optimizer uses these statistics to find the best access path to the data Rebind packages Any packages that are stored in a database are invalidated during migration but packages will be implicitly rebound the first time that an application uses them after migrating your database To avoid this overhead during the user execution time after migration you can run the db2rbind command to rebind these packages as Example 4 12 shows Review the log file to ensure that everything is satisfactory Example 4 12 db2rbind dpfusr1l gemini gt db2rbind sample 1 db2rbind log all Rebind done successfully for database SAMPLE Mi
378. nd much more economically And if the load increases the cluster can be extended for managing the additional demand without compromising on performance DB2 was the first commercial database on Linux to provide built in capabilities for clusters That is DB2 can be deployed across a Linux cluster immediately without the need for additional clustering software DB2 clusters on Linux are ideal for running demanding transactional applications and warehouses that involve large volumes of data while providing the following benefits Faster processing time Very large databases Excellent scalability Increased availability Reduced cost YYYY Y Combining the clustered approach with DB2 support for 64 bit Linux environments provides additional performance and scalability advantages For the clustering feature of DB2 you have to set up a partitioned environment This is called inter parallelism Database clustering architectures There are two primary database clustering architectures shared disk and shared nothing Shared disk is used by Oracle RAC DB2 for Linux employs shared nothing Up and Running with DB2 on Linux Shared disk Shared Storage Figure 1 5 Shared disk architecture Shared disk In a shared disk environment each database node has its own processors but shares the disks with other nodes Therefore all the processors can access all the disks in the cluster which introduces additional overhead for coo
379. nd nfs server packages installed on each machine gt NFS operations The commands for starting stopping and checking the status of NFS are different in each Linux distribution For SUSE SLES 10 uses the kernel based NFS server The command to configure the NFS server is rcnfsserver e To start NFS use renfsserver start e To stop NFS use renfsserver stop e To check the NFS status use rcnfsserver status Make sure that NFS is started during startup time You can check it with the command chkconfig nfsserver If NFS is not on enable it through chkconfig nfsserver on Chapter 2 Installation 47 48 For Red Hat e To start NFS use sbin service nfs start e To stop NFS use sbin service nfs stop For more details about configuring NFS on Red Hat refer to http www redhat com docs manuals enterprise RHEL 5 manual Deployment_G uide en US ch nfs html After you have verified that NFS is running on each system check for the rpc statd process using the ps ef grep rpc statd command rpc statd is a NFS process required by DB2 Note that rpc statd is not required in SLES when using the kernel based NFS server Create and configure the DB2 home file system to NFS You need to create a DB2 instance home directory that is shared across all machines that will participate in your partitioned database system In our example we allocate a file system export db2home on mensa NFS is used to share this file system
380. nd operating system log files which might provide more detailed information to help you find a problem or to further determine the root cause of a problem Afterwards you can take corrective actions based on the collected information 7 4 1 DB2 administration notification log The DB2 administration notification log contains user friendly and national language enabled messages that can help database administrators to obtain more information associated to specific issues for example information Which is supplemental to an SQLCODE From Health Monitor for health indicators From task executions From the applications that were written by the application developers vvvy This information can be very beneficial to the database administrators for resolving database or system related problems quickly and easily For the Linux platform the notify log is a text file located in the directory specified by the database manager configuration parameter DIAGPATH which is the same directory where db2diag log resides The name for the notify log is lt instance owner gt nfy In the example db2home db2inst1 sqllib db2dump db2inst1 nfy the instance owner is db2inst1 and DIAGPATH is db2home db2inst1 sqllib db2dump 2 Consider changing DIAGPATH to a directory on another file system than the instance home s file system Then the file system full problem of the diagnostic data directory will not impact your instance home Chapter 7
381. nd the interval is 2 seconds Example 7 29 Using vmstat to observe virtual memory statistics pdb2inst1l mensa db2home db2inst1 gt vmstat 2 10 procs memory swap jo system cpu r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0 6184 285668 274036 2883968 0 0 6 24 3 14 0099 1 0 0 0 6184 285668 274036 2883968 0 0 0 38 628 310 0 099 1 0 0 0 6184 285668 274036 2883968 0 0 0 12 612 291 0 0100 0 0 0 0 6184 285668 274036 2883968 0 0 0 36 616 301 0 0100 0 0 0 0 6184 285684 274036 2883968 0 0 0 50 792 529 0 098 2 0 0 0 6184 285684 274036 2883968 0 0 0 24 613 293 0 0100 0 0 0 0 6184 285700 274036 2883968 0 0 0 24 624 310 0 099 1 0 0 0 6184 285700 274036 2883968 0 0 0 36 614 301 0 0100 0 0 Up and Running with DB2 on Linux 6184 285700 274036 2883968 0 0 0 24 614 296 0 0100 0 0 0 0 0 0 6184 285700 274036 2883968 0 0 0 32 786 521 0 099 1 0 7 6 3 iostat You use the iostat command for reporting Central Processing Unit CPU statistics and for monitoring system I O device statistics for devices and partitions You can use the report that is generated by the iostat command to assist you in changing the system configuration to better balance the I O load between physical disks Note The iostat command is contained in the sysstat package the sar command is also included in this package Before you can use these commands you need to install this package The first report that is gen
382. ne as root In our sample we logged in to gemini as root 5 Transfer the db2ese_mpp_addpart rsp file from the primary machine and place it on the root directory 6 Mount the DB2 product DVD 7 Run the db2setup command for example mnt dvd db2setup r root db2ese_mpp_addpart rsp where mnt dvd represents the mount point of the DVD After the installation has finished check the installation log tmp db2setup log to ensure that no errors have occurred 8 Copy the instance related TCP IP service entries in the etc services file on the primary machine to the etc services file on the current server In our sample we added the following entries in etc services on gemini db2c_db2inst1 50001 tcp DB2_db2inst1 60000 tcp DB2_db2inst1_1 60001 tcp DB2_db2inst1_2 60002 tcp DB2_db2inst1_END 60003 tcp Up and Running with DB2 on Linux 9 Issue the following command to create a physical node on the current server opt ibm db2 V9 5 instance db2icrt p db2c_db2inst1l u db2fencl db2inst1 10 If there is another participating DB2 server physical node in the partitioned i database environment repeat step 3 to step 9 in this section In our sample we only had two DB2 servers mensa and gemini Modify sqllib db2nodes cfg by adding an entry to the db2nodes cfg file for each participating logical database partition server When you first view the db2nodes cfg file it will contain an entry similar to 0 ServerA 0 T
383. needs of organizations that require robust connectivity from a variety of desktop systems to System z and System i database servers Data Server Client software is deployed on desktop systems and provides API drivers that connect client server applications running on these desktop systems to a DB2 Connect server Designed to provide Chapter 1 Introduction 9 10 connectivity for client server applications in large scale demanding environments DB2 Connect server provides connection pooling and connection concentrator functions to maximize application availability while minimizing System z and System i resources DB2 Connect Application Server Edition is identical to the DB2 Connect Enterprise Server in its technology Just like the DB2 Connect Enterprise Edition it is designed for large scale demanding environments However its licensing terms and conditions are meant to address specific needs of multi tier client server applications as well as applications that utilize Web technologies DB2 Connect Application Server Edition license charges are based on the size or the number of processors available to the application servers where the application is running DB2 Connect Unlimited Edition for zSeries is ideal for organizations with extensive usage of DB2 Connect especially where multiple applications are involved This product provides program code of the DB2 Connect Personal Edition as well as program code identical to the DB2 Connect
384. ner The Define Container dialog closes returning focus to the Containers page of the Alter Table pace notebook Click OK to alter the table space Figure 7 23 Reviewing the required actions and taking action v On the Summary panel click Close to quit the Recommendation Advisor utility Chapter 7 Monitoring and troubleshooting DB2 373 374 b Another way to get recommendations is by using the DB2 CLP command GET RECOMMENDATIONS with the specified health indicator The following command can be used to get the recommendation details for our example db2 get recommendations for health indicator ts ts_util Then the details of the recommendations associated with the specified health indicator will be shown You can get the indicator name from the Health Center where you define properties for the health indicator In general the name such as s ts_ util is listed in the Description field For details about the indicators refer to System Monitor Guide and Reference SC23 5865 6 Set up additional follow up actions There are situations when you need a proactive action plan for the error condition This plan can be accomplished by using a predefined script or task a To enable the predefined script or task on the Object Health Indicator Configuration panel Figure 7 12 on page 365 double click a specific health indicator The Configure Health Indicator panel is shown Figure 7 13 on page 366 Selec
385. network programming and GUI development It has also become the premier scripting language of the Web According to Larry Wall its creator he included in Perl all the cool features found in other languages and left out those features that weren t so cool Perl is typically provided by the Linux distributions but you can also download it from http www cpan org 434 Up and Running with DB2 on Linux Perl and DB2 You can create DB2 applications using Perl by using the DBD DB2 driver with the Perl Database Interface DBI Module Both of these components are freely available on the Internet Currently DB2 supports the following versions gt gt Perl 5 8 or later DBI 1 41 or later Perl is an ideal language to use with DB2 gt It is an interpreted language and has a DBI Module that uses dynamic SQL which is ideal for quickly creating and revising prototypes of DB2 applications The Perl DBI module uses an interface that is quite similar to the call level interface CLI and Java Database Connectivity JDBC interface which makes it easy for you to port your Perl prototypes to CLI and JDBC Perl offers very powerful functions for formatting text and handling strings which allow you to generate reports very quickly Setting up a Perl application development environment In order to set up a Perl application development environment for DB2 on Linux you must install and configure the following components on you
386. ng RUNSTATS Table statistics Index statistics SCHEMA NAME INDCARD LEAF ELEAF LVLS NDEL KEYS LEAF_RECSIZE NLEAF_RECSIZE Table DB2INST1 ITEM Index DB2INST1 PK_ITEM_ITEMID 1502010 3096 0 3 0 1502010 4 4 ELEAF and NDEL go back to 0 as the pseudo deleted pages are physically removed Now we reorganize the table as recommended We demonstrate both classic and inplace table reorganization In Example 6 39 on page 296 we use the classic table reorganization method with the ALLOW READ ACCESS option Chapter 6 Administering databases 295 296 Example 6 39 REORG TABLE with the ALLOW READ ACCESS option db2inst1 mensa gt db2 reorg table item index PK_ITEM_ITEMID allow read access on all dbpartitionnums DB20000I The REORG command completed successfully For the inplace table reorganization we use the ALLOW WRITE ACCESS option If you want more information about running REORG you can monitor the REORG process using various methods GET SNAPSHOT command db2pd tool SNAPTAB_REORG administrative view and SNAP_GET_TAB_REORG table function You can monitor the REORG process either manually or with a shell script To monitor the progress of the REORG job we run the monitor commands to collect the information in another terminal session while the REORG job is running The amount of time that is needed to collect the REORG information will depend on the data volume against which you are operating and your system
387. ng either a predictive or reactive model which allows businesses to align their business goals with their IT applications Multithreaded architecture extensions DB2 uses a multithreaded architecture which improves performance and simplifies configuration and optimization Also simplifications to memory management eliminate most agent level configuration parameters and automate the rest Deployment improvements Deployment improvements simplify the process of installing and maintaining your DB2 data server Two previously manual steps that were required after applying fix packs running the db2iupdt command and running the dasupdt command are now automated In addition binding occurs automatically at the first connection Non root users can perform installing applying or rolling back fix packs configuring instances adding new features and uninstalling Chapter 1 Introduction 5 gt Easier management of partitioned database systems There is a single view of all database configuration elements across multiple partitions With this new functionality you can update or reset a database configuration across all database partitions by issuing a single SQL statement or a single administration command from any partition on which the database resides The BACKUP DATABASE command can now back up all partitions of a multi partition database at once with the same timestamp gt Automatic storage management enhancement
388. ng system upgrades prior to DB2 database product migration If you migrate DB2 server you might also need to migrate your database applications and routines to support changes for 64 bit instances SQL stored procedures Java Virtual Machine JVM and development software Migrate all of your DB2 servers to Version 9 5 before you migrate any of your DB2 clients to Version 9 5 Certain problems can occur if you migrate your clients first If you have 32 bit instances and you migrate to DB2 9 5 on a 64 bit system you need to manage the incompatibilities due to the shared library path specification and discontinued features in order to run your applications and routines successfully The files SQLSPCS 1 and SQLSPCS 2 contain table space information During migration from DB2 UDB Version 8 to DB2 9 5 these files grow to four times their previous size but the total data size on disk does not exceed the new size of the SQLSPCS 1 and SQLSPCS 2 files Ensure that you have sufficient free space in the tmp directory on the machine to which you will be migrating an instance The instance migration trace file is written to tmp The minimum size required is 20 MB Ensure that you have sufficient space in the file system where the table spaces of the databases that you are migrating are located Additional space is required for both old and new database catalogs during migration The Chapter 4 Migration and fix packs 169 amount of required
389. ng the ADMIN_COPY_SCHEMA procedure db2inst1 mensa db2backup datamove gt db2 call sysproc admin_copy_schema DB2VS DB2VS1 COPY NULL USERSPACE1 USERSPACE1 SYS_ANY DB2VS2 ERRORTAB Value of output parameters Parameter Name ERRORTABSCHEMA Parameter Value Parameter Name ERRORTABNAME Parameter Value Return Status 0 db2inst1 mensa db2backup datamove gt db2 select substr tabschema 1 10 substr tabname 1 10 substr tbspace 1 10 from syscat tables where tabname ITEM 1 2 3 DB2VS ITEM USERSPACE1 DB2VS1 ITEM USERSPACE1 2 record s selected Chapter 6 Administering databases 339 db2inst1 mensa db2backup datamove gt db2 select count from db2vs1 item 3000000 1 record s selected 6 4 Task Center Scheduler and DB2 Tools Catalog In this section we discuss how to use the DB2 Task Center to create and schedule a task to run on Linux The DB2 Administration Server and Tools Catalog database are the prerequisites for using the Task Center and most GUI tools We discuss the DB2 Administration Server and Tools Catalog database first in preparation for enabling the Task Center and Scheduler 6 4 1 DB2 Administration Server and Tools Catalog Database 340 The DB2 Administration Server DAS is a control point that is used only to assist with tasks on DB2 servers You must have a running DAS if you want to use available tools such as the Task Center the Control Center or the C
390. nitor specific processes top d 1 p pgrep db2sampl p 1785 p 2928 You can specify up to 20 processes for top to monitor by using the p command option You also can utilize the Linux shell function to obtain the process ID directly in the top command In our example we use the Linux command pgrep db2samp1 with top to obtain the process ID for the db2samp1 process and add it into the top monitor process list In addition to the p command option the d command option is also specified in the command The d command option refreshes the output display of top every second Example 7 28 shows the output Example 7 28 Using top to monitor the specified processes top 17 11 13 up 9 days 16 25 7 users load average 0 49 0 22 0 07 Tasks 3 total 0 running 3 sleeping 0 stopped 0 zombie Cpu s 0 0 us 0 5 sy 0 0 ni 50 0 id 49 5 wa 0 0 hi 0 0 si 0 0 st Mem 3842648k total 3577476k used 265172k free 276224k buffers Swap 8393920k total 6184k used 8387736k free 2890004k cached PID USER PR NI VIRT RES SHR S CPU MEM TIME COMMAND 1785 db2inst1 25 0 1252m 154m 122m S 1 4 1 0 21 29 db2sysc 2928 db2fencl 15 0 528m 58m 34m S 0 1 6 0 00 50 db2fmp 5092 db2instl 16 0 119m 12m 8308 S 0 0 3 0 00 03 db2samp 7 6 2 The vmstat command You can use the vmstat command to report virtual memory statistics as well as information about processes paging block I O and CPU activities The vmstat command is contained in the procps package f
391. nsa has table spaces SYSCATSPACE TEMPSPACE1 USERSPACE1 and SAMPLE_MPL and node 1 gemini has table spaces TEMPSPACE1 USERSPACE1 SAMPLE_MPL and SAMPLE_SNG To create tables in the newly created table space use the command line to execute DDL scripts as shown in Example 3 20 on page 118 using the db2 tvf command Chapter 3 Post installation tasks 117 118 Example 3 20 Create table DDL connect to itsodb CREATE TABLE PART P_PARTKEY INTEGER NOT NULL P_NAME VARCHAR 55 NOT NULL P_MFGR CHAR 25 NOT NULL P_ BRAND CHAR 10 NOT NULL P TYPE VARCHAR 25 NOT NULL P SIZE INTEGER NOT NULL P CONTAINER CHAR 10 NOT NULL P_RETAILPRICE FLOAT NOT NULL P_COMMENT VARCHAR 23 NOT NULL IN SAMPLE MPL If you prefer to use graphical tools start the Control Center and expand the tree under the database until the Tables folder appears Right click Tables and select Create See Figure 3 11 lt OJ a IF Control Center Control Center Selected Edit View Tools Help DHSAsS BIZ aE O 3 Control Center ai O All Systems MSUSE db2inst1 ITSODB Tables Table space ma a es EB HMON_ATM_INFO SYSTOOLS SYSTOOLSPACE mr EB HMON_COLLECTI SYSTOOLS SYSTOOLSPACE C View AERE E Pouicy SYSTOOLS SYSTOOLSPACE Aliase Create From Import GB SYSATTRIBUTES SYSIBM SYSCATSPACE Nickr_Ellter EB SYSAUDITPOLICIES SYSIBM SYSCATSPACE C Cachi Refresh E SYSAUDITUSE SYSIB
392. nstallation you must accept the license agreement On the Software License Agreement page select Accept and click Next 10 On the Select installation response file creation or both window select Install DB2 Information Center on this computer and save my settings in a response file if you want to use a response file to install the DB2 Information Center on this computer or other computers at a later time You can specify where the response file will be saved Click Next 11 On the Select the languages to install window Figure 2 18 on page 89 select the languages that the DB2 Information Center will install By default the DB2 Information Center is installed in the opt ipm db2ic V9 5 directory However you can specify your own installation path Click Next Up and Running with DB2 on Linux DB2 Setup DB2 Information Center Version 9 5 2 gt ER English EA AENA Chinese Simplified Chinese Traditional Croatian Czech jopt ibm db2ic Y9 5 e Figure 2 18 Select the languages to install 12 As shown in Figure 2 19 configure the DB2 Information Center for incoming communication on the Specify the DB2 Information Center port window Click Next to continue the installation ab2icv95 51001 Ganev Figure 2 19 Specify the DB2 Information Center port 13 Start copying files Check settings and then click Finish Chapter 2 Installation 89 Installing DB2 Information Center using the
393. nt Each DB2 feature status is listed as either gt In compliance The feature has been used and is properly licensed gt Violation The feature is not licensed and has been used You can generate a compliance report using the License Center by selecting Generate Compliance Report from the License menu Figure 3 34 shows the report License Compliance Report License Compliance Report Last license compliance reset date 01 31 2008 DB2 Enterprise Server Edition In compliance DB2 Database Partitioning Violation Not used Violation Not used Not used Not used IBM Homogeneous Federation ESE Not used IBM Homogeneous Replication ESE Not used Figure 3 34 License Compliance Report The License Center can also be used to reset the license usage information by selecting Reset Compliance Report from the License menu Up and Running with DB2 on Linux 3 9 2 db2licm tool The db21 icm tool is a command line tool that manages licensing It is used to display license information add and remove license keys and specify user and enforcement policies It can also generate usage statistics and display connection information for current users To view all of your licensing information enter db2licm 1 as shown in Example 3 41 Example 3 41 View DB2 licensing information using the db2licm command db2inst1l mensa gt db2licm 1 Product name DB2 Enterprise Server Edition License type A
394. nter or by using DB2 CLP commands refer to Appendix B DB2 Tools Catalog creation on page 499 The Tools Catalog database contains task information that is created by the Task Center and Control Center These tasks are run by the Scheduler on the DB2 Administration Server Figure 6 45 shows the relationships among DB2 Tools DB2 instances DAS the Scheduler and the Tools Catalog database Tool Set DB2 Control Center DB2 Task Center DB2 Warehouse Center Configuration Assistant TCP IP TTS EE TA VE EET veurne Systems Linux Unix and Windows DB2 Instances DB2 administration server Scns nora eenas Scheduler ee Tools Catalog Database Figure 6 45 How DAS and Tools Catalog Database relate to other parts of DB2 6 4 2 Task Center and Scheduler After the DAS has started and the Tools Catalog is ready you can start the Task Center within the DB2 Control Center or other tools where the Tools menu is available You can use the Task Center to run tasks either immediately or according to a schedule and to notify people about the status of the completed tasks The Task Center includes functionality from the Script Center in previous versions of DB2 plus additional functionality Chapter 6 Administering databases 341 342 A task is a script together with the associated success conditions schedules and notifications You can create a task within the Task Center c
395. nts Number of rows read 3000000 Number of rows skipped 0 Number of rows loaded 3000000 Number of rows rejected 0 Number of rows deleted 0 Number of rows committed 3000000 db2inst1 mensa db2backup datamove gt db2 select dbpartitionnum itemid as Partitionnumber count as Counter from db2instl itemload group by dbpartitionnum itemid NODENUMBER COUNTER 0 1500364 1 1499636 2 record s selected As seen in Example 6 51 on page 312 the data was loaded into table itemload which is spread across two database partitions To verify the load result and distribution within the same example we use an SQL statement to count the number of rows distributed on different database partitions From the output of the SQL execution we learn that the rows are distributed to the database partitions evenly Note When the COPY NO option is specified for a recoverable database the table space will be placed in the backup pending state when the load operation begins Placing the table space in the backup pending state ensures that you can recreate your database with all of the data because the load is not logged in the database log files The default COPY NO is used because we set up log archiving for our database and we did not specify COPY YES with the LOAD command The table space of Chapter 6 Administering databases 313 314 table itemload is now in backup pending state To remove the table space state we have to run
396. nts shown in Example B 4 to verify the newly created table spaces and related buffer pool Example B 4 New table spaces and buffer pool created automatically db2inst1 Mensa gt db2 list tablespaces Tablespaces for Current Database Tablespace ID 0 Name SYSCATSPACE Type Database managed space Contents All permanent data Regular table space State 0x0000 Detailed explanation Normal Appendix B DB2 Tools Catalog creation 503 Tablespace Name Type Contents State Detailed Normal Tablespace Name Type Contents State Detailed Normal Tablespace Name Type Contents Space State Detailed Normal Tablespace Name Type Contents State Detailed Normal ID explanation ID explanation ID explanation ID explanation 1 TEMPSPACE1 System managed space System Temporary data 0x0000 2 USERSPACE1 Database managed space All permanent data Large table space 0x0000 3 TBSP32K0000 System managed space All permanent data Regular table 0x0000 4 TBSP32KTMP0000 System managed space System Temporary data 0x0000 DB210111 In a partitioned database server environment only the table spaces on the current node are listed db2inst1 Mensa gt db2 select substr tbspace 1 15 TBSPACE tbspaceid substr dbpgname 1 15 DBPGNAME bufferpoolid from syscat tablespaces TBSPACE TBSPACEID DBPGNAME BUFFERPOOLID SYSCATSPACE TEMPSPACE1 USERSPACE1 TBSP32K0000
397. ny other country where such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of express or implied warranties in certain transactions therefore this statement may not apply to you This information could include technical inaccuracies or typographical errors Changes are periodically made to the information herein these changes will be incorporated in new editions of the publication IBM may make improvements and or changes in the product s and or the program s described in this publication at any time without notice Any references in this information to non IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you Information concerning non IBM products was obtained from the suppliers of those products their published announcements or other publicly available sources IBM has not tested those products and cannot confirm the accuracy o
398. ny tasks The editor GUI supports all of the features that you know from Java program editing You can create edit context assist and run queries directly by selecting them within the program code Chapter 8 Application development 471 In this section we implement and debug a simple Java stored procedure to demonstrate several of the Data Studio s powerful features We provide a general introduction of the Data Studio in Chapter 5 IBM Data Studio on page 197 Setting up a project You can start the Data Studio with the command opt 1BM SDP70 eclipse Alternatively you can start it by selecting Start menu gt Development gt IBM Data Studio Developer or Start menu gt IBM Software Development Platform as shown in Figure 8 10 All Applications E gt I Development T IBM Dat Studio Developer A Games a IBM Installation Manager Graphics gt Uninet IBM Installation Manager IBM Installation Manager a e amp Internet gt Multimedia gt amp Otice Q System Noid Utilities gt g Find Files Folders a Home Personal Files 8 IBM Sotware Development Platiorm La Personal Settings SUSE Help Genter m Actions l Recent Documents d Wi My System gt 9 Run Command A Switch User d B Lock Session O Log Oui 2 A P y mj IE db2instt vmsus Shell Ki jan Bae gt ke a Eq 2 E db2insti vmsuse Shell Figure 8 10 Start Data Studio from th
399. o move around between the annotations in your file Q Y T Y to er a gt Figure 5 16 Editor tool bar Projects Projects are used to organize your resources For instance a Java project contains the source files all built files and meta information files for your Java application A Data Project is related to a database connection and stores all of the information about this project In the file system a project is represented as a subdirectory in your workspace Chapter 5 IBM Data Studio 215 You can create a new project by selecting File gt New Project A panel lists wizards for creating the various types of projects that are shown Select the wizard suitable for your application The Data Studio will ask you a couple of project specific questions and switch to a particular perspective that is useful for that project type You can create as many projects as you want in your workspace Projects can be opened or closed as you need to work on them If you want to share projects between multiple workspaces or between multiple members in your team use the Team functions as described in 5 3 2 Team function on page 216 Just copying the project subdirectory is not supported 5 3 2 Team function 216 The team function introduces a powerful facility to share projects among team members or workspaces This function supports all version control applications that are available as plug ins for the Eclipse framework Exa
400. o not respond to this message as it was generated by DB2 software Additional help is provided in the following paragraphs Figure 7 16 Notification for health indicator by e mail In addition to the notifications to the administration notification log and contact there is more information regarding the alert available within the Health Center The Health Center GUI has red yellow orange and green Chapter 7 Monitoring and troubleshooting DB2 369 state indicator icons prefixed to the DB2 objects The state icon provides you with a quick view of the system s health conditions In Figure 7 17 you learn that the red circle icon is prefixed to the instance name and the database name in the left pane within the Health Center is displayed This icon means that alarm conditions happened within the instance or any of its databases or their table spaces and containers On the right pane of the window the Health Center lists all of the alerts Health Center Table Space Utilizati Table Space Stora 0 Table Space Utilizati Table Space Stora 1 Figure 7 17 Monitor health indicators in the Health Center You can work on the alert directly from here Select one of the alerts that corresponds to your desired health indicator and then right click the alert entry It provides you with the Show Details and Disable Evaluation options To get detailed information choose Show Details to get the recommendation for this aler
401. of a load operation during processing and to return the state of the table You can connect to individual database partitions during a load operation and issue the LOAD QUERY command against the target table When issued from the CLP this command displays the contents of all of the message files that currently reside on that database partition for the table that is specified in the LOAD QUERY command The output of the LOAD QUERY command in Example 6 57 is gathered when Example 6 55 on page 319 is running If a load job has finished the command returns the table state as shown in the last command in the example Example 6 57 Using LOAD QUERY to monitor LOAD status db2inst1 mensa db2backup datamove gt db2 load query table itemload SQL3530I The Load Query utility is monitoring LOAD progress on partition 1g SQL3109N The utility is beginning to load data from file db2backup datamove item del Chapter 6 Administering databases 321 SQL3500W The utility is beginning the LOAD phase at time 02 11 2008 15 25 41 102272 SQL3519W Begin Load Consistency Point Input record count 0 SQL3520W Load Consistency Point was successful SQL3532I1 The Load utility is currently in the LOAD phase Number of rows read Number of rows skipped Number of rows loaded Number of rows rejected Number of rows deleted Number of rows committed Number of warnings Tablestate Load in Progress 1467592 0 1467592 0 ooo
402. og records are applied to the database During the backward phase any uncommitted changes applied during the forward phase are rolled back Database recovery using the Control Center Restore and rollforward are fully integrated into the DB2 Control Center You can access the wizard from the context menu of the database as shown in Figure 6 13 on page 264 Chapter 6 Administering databases 263 o All Syste ontrol Center Figure 6 13 Database context menu The Restore Data Wizard Figure 6 14 guides you through the steps and options to recover your data level of recovery ARENOR EE TEA Figure 6 14 Restore Data Wizard You can choose for instance if you want to perform a full or table space restore which backup image to restore and how far to roll forward 264 Up and Running with DB2 on Linux Note For a detailed explanation of the database recovery options refer to Part 2 Data recovery in Data Recovery and High Availability Guide and Reference SC23 5848 6 1 6 Redirected restore sample scenario Using a redirected restore you can change the physical location of the table space containers that are stored in the backup image when restoring the database into the same database or into another database Redirected restore is performed by using the RESTORE DATABASE command with the REDIRECT parameter or by using the Restore Database wizard in the Control Center You have to redefine each table spa
403. oject Explorer view Refer to Figure 8 16 Data Project Explorer X v 0 DataProject SAMPLE jdbe db2 localhost 50001 5AMPLE ri SOL Scripts C Stored Procedures C User Defined Functions C3 Web Services v OXML QWSDL C XML Documents C XML Schema GXxs_t Figure 8 16 Data Explorer Creating an SQL statement With the SQL builder in Data Studio you can easily create complicated SQL queries and XQuery scripts without knowing the syntax details To create a query follow these steps 1 In the Database Explorer view expand the Connections right click the SAMPLE database and select New SQL or XQuery Script Up and Running with DB2 on Linux 2 In the pop up panel enter a name for the query and select SQL builder as shown in Figure 8 17 We enter the name EmpSalary for the query Click OK m Database Explorer f z TA E E E O 8 0 u i 4H oY l v E Connections vas Emsa S vV SAMPLE DB2 for Linux UNIX and Wind j lt SAMPLE 1 Ed it usi ng a gt C Butter Pools O SQL editor for scripts that contain one or more SQL and XQuery statements gt C Groups SQL builder for single SOL SELECT INSERT UPDATE or DELETE statement b C Partition Groups Statement type Serer tt s sS E b C Remote Servers b O Roles b Schemas b Table Spaces Cancel b O Users E Properties 53 Tasks Problems Error Log Model Report Data Output Bookmarks General 0 lt Database gt SAMPLE Privileges Name SA
404. ollowing window appears Figure 3 24 on page 144 After selecting a parameter a brief description of the parameter is displayed at the bottom of the window under Hint Chapter 3 Post installation tasks 143 Database Configuration ITSODB o x COUNTRY DATABASE_LEVEL Oxc00 DB_MEM_THRESH DFT_MTTB_TYPES S DFT_QUERYOPT 5i DFT_REFRESH_AGE 0 E m Figure 3 24 Change database parameter After you have made all of the changes that you want to make click OK and all of the changes will be applied to the database Figure 3 25 he Database configuration settings were updated successfully Figure 3 25 Confirmation window after you update the database configuration Using the Configuration Advisor option The Configuration Advisor is a smart tool that will help you configure your databases easily With the Configuration Advisor you can tune the database without an in depth knowledge of DB2 Simply provide the advisor with the requested information about your system such as planned workload and 144 Up and Running with DB2 on Linux connection information and the wizard will recommend the changes to make Figure 3 26 shows the Configure Advisor window m W Configuration Advisor Figure 3 26 Configuration Advisor window After finishing all sections the wizard provides suggestions of what to change After you make the changes you can choose to apply the change immediately or save the SQL to
405. ols Catalog were changed automatically See Example B 3 Example B 3 DAS Tools Catalog parameters changed automatically db2inst1 Mensa gt db2 get admin cfg Admin Server Configuration Authentication Type DAS AUTHENTICATION SERVER_ENCRYPT Up and Running with DB2 on Linux DAS Administration Authority Group Name DASADM GROUP dasadml DAS Discovery Mode DISCOVER SEARCH Name of the DB2 Server System DB2SYSTEM MENSA Java Development Kit Installation Path DAS JDK _PATH AUTOMATIC db2home db2inst1 sqllib java jdk64 Java Development Kit Installation Path DAS JDK_64 PATH AUTOMATIC db2home db2inst1 sqllib java jdk64 DAS Code Page DAS_CODEPAGE 0 DAS Territory DAS_TERRITORY 0 Location of Contact List CONTACT_HOST Execute Expired Tasks EXEC_EXP_TASK NO Scheduler Mode SCHED ENABLE ON SMTP Server SMTP_SERVER Tools Catalog Database TOOLSCAT_DB TOOLSCAT Tools Catalog Database Instance TOOLSCAT_INST db2inst1 Tools Catalog Database Schema TOOLSCAT_SCHEMA ESECATO Scheduler User ID 7 Diagnostic error capture level DIAGLEVEL 2 In addition to the automatic DAS parameter changes within the Tools Catalog Database a series of new tables are created with the schema name specified by TOOLSCAT_SCHEMA Here the schema name is ESECATO Also two new table spaces and a related buffer pool with page size of 32 K are created within the database You can use the commands and SQL stateme
406. olutions benchmark index epx DBI perl org http dbi perl org DB2 Perl Database Interface http www ibm com software data db2 perl Comprehensive Perl Archive Network http www cpan org http www cpan org modules by category 07_Database_Interfaces DBI Apache HTTP Server Project http httpd apache org Related publications 509 gt Perl apache org http perl apache org docs 1 0 guide gt PHP scripting language http www php net How to get IBM Redbooks publications You can search for view or download IBM Redbooks publications Redpapers Technotes draft publications and Additional materials as well as order hardcopy IBM Redbooks publications or CD ROMs at this Web site ibm com redbooks 510 Up and Running with DB2 on Linux Index Symbols nfy 397 Xauthority 93 etc 401 Numerics 2 tier 11 64 bit 2 A access path 181 access plan 444 active log file 234 admin_cmd stored procedure 303 administration notification log 188 369 administration server 36 ADO NET 434 AMD 2 analysis tool 402 APIs 354 application client 12 archive logging 123 228 archive storage pool 239 AS 400 12 automatic backup 249 automatic statistics collection 182 automatic storage 171 automatic storage paths 265 availability 18 availability monitoring 200 availability requirement 230 B backup 42 backup image 5 backup image file 255 backup pending state 177 backup storage pool 239 backup strategy 230 ben
407. om the previously defined XSD document 5 ProductsSchema xsd X NewFile xm Eil x m 2xml version 1 0 encoding UTF 8 V e tns products xmins tns http www example org TestSchema xmins xsi http www w3 org 2001 XMLSchema instance xsi schemaLocation http www example org TestSchema ProductsSchema xsd Add DTD Information Edit Namespaces Add Attribute Add Child Add Before gt e tns product 2 Comment Add Processing Instruction Figure 5 22 Sample in the XML editor 5 3 4 Entity Relationship ER Diagramming 220 The Data Studio allows you to easily create Entity Relationship ER diagrams from the database schema In the Database Explorer open the tree Connections gt SAMPLE SAMPLE Schemas gt DB2INST1 Tables for the list of tables Select the tables for which you want to create the ER diagram In our example we select the EMP_RESUME and the EMPLOYEE tables and right click each of them Figure 5 23 on page 221 Up and Running with DB2 on Linux xg a L M s C Nicknames C Packages C Sequences C Stored Proces Tables FR AcT s CL_SCHE E DEPART qvevvvy wm 7 vV vV Vv Hi EMP_RE b ES EMPMDC 3 EMPLOYEE Data X Alter Dor BB Add to Overview Diagram g Generate DDL 25 Update Statistics Ghee x ae seg e NET W Refresh Value Distributions FR EMP PH
408. ommand returns the information for table ID 4 in table space ID 7 The total number of updates on the table the UPDATE INSERT DELETE UDI and the real time statistics UDI counters RTSUDI are returned as well UDI is a counter to measure how much data has been changed since the last RUNSTATS was run The value is used by DB2 to determine if the statistics for a table need to be updated List all engine dispatchable units EDUs in the instance db2pd edus In DB2 Version 9 5 the implementation of the DB2 engine has evolved from a process based model to a thread based model that is based on Linux and UNIX systems When invoking the ps command with the fu instancename option the output lists only two DB2 processes db2sysc and db2acd To Up and Running with DB2 on Linux display the individual threads associated with the db2sysc process you must use the applicable thread options on the ps command On Linux you can use the 1Lfp option or use the db2pd command with the new edus option As you can see from our examples the db2pd command is an extremely powerful tool for problem determination To list all of the options use db2pd h Many more examples and information are in the Troubleshooting Guide Gl11 7857 and the DB2 Linux UNIX and Windows Command Reference SC23 5846 01 7 5 3 DB2 snapshot command Like the db2pd command you can use the snapshot monitor to capture information about the database and any connected appli
409. on Import saves the changes made and releases the locks on the target table You can also specify that commit takes place periodically during the import The import utility can be invoked through the command line processor CLP the Import notebook in the Control Center by calling the ADMIN_CMD stored procedure or by calling the API db2Import You can specify the MESSAGES parameter for the IMPORT utility to record errors warnings and informational messages that are associated with the IMPORT operation Chapter 6 Administering databases 307 308 Important If the volume of output messages generated by an import operation against a remote database exceeds 60 KB the utility will keep the first 30 KB and the last 30 KB Import table data through the CLP Example 6 48 shows the IMPORT command issued through the CLP Example 6 48 Using IMPORT through the DB2 CLP db2inst1 mensa db2backup datamove gt db2 create table itemimp like item DB20000I The SQL command completed successfully db2inst1 mensa db2backup datamove gt db2 import from from item ixf of ixf commitcount 100000 messages itemimp msg insert into itemimp Number of rows read 3000000 Number of rows skipped 0 Number of rows inserted 3000000 Number of rows updated 0 Number of rows rejected 0 Number of rows committed 3000000 In Example 6 48 we use the COMMITCOUNT parameter which means that DB2 will perform a COMMIT after every n records are imp
410. on db2setup command with a response file silent install db2_insta11 utility DB2 Setup wizard For root installation you can use the DB2 Setup wizard in the following way 1 2 Log in as root Mount the DB2 product CD or DVD using the following command mount t iso9660 o ro dev dvd mnt dvd where mnt dvd represents the mount point of the CD or DVD 3 As root run db2setup and select Install a Product on the first window 4 Select Install New On the Welcome to the DB2 Setup wizard window click Next On the Software License Agreement window read the license agreement then select Accept and click Next Select the installation type as shown in Figure 2 5 on page 67 You can choose a Typical Compact or Custom installation Typical installs most DB2 components except for the Base application development tools Click View Features to see what components will get installed Compact installs only the basic DB2 features and functionality Custom allows you to install whatever components that you want An advantage of the Custom option is that it allows you to install the Base 7 You can use db2setup i lt anguage gt to run the DB2 Setup wizard in another language 66 Up and Running with DB2 on Linux application development tools with DB2 With the Typical option the Base application development tools require a separate installation DB2 Setup DB2 Enterprise Server Edition Version 9 5
411. on June 25 2008 June 2008 Second Edition This revision reflects the addition deletion or modification of new and changed information described next New information gt DB2 9 5 features and functions Changed information DB2 installation Post installation tasks Migration Database administration Monitoring Application development vvvvvy Copyright IBM Corp 2008 All rights reserved xix XX Up and Running with DB2 on Linux Introduction With a wide spectrum of offerings and capabilities DB2 for Linux allows you to access manage and analyze all forms of information across the enterprise DB2 gives you a robust easy to manage database that offers high performance complementing the stability and reliability of Linux Industry leading parallel technologies in DB2 make it one of the most scalable and powerful databases in production today and when combined with Linux clusters it allows you to manage mission critical data at a cost lower than other enterprise class databases You can download DB2 for Linux test drive from these Web sites gt http www ibm com software data db2 9 download html gt http www ibm com software data db2 9 edition express c html Visit the following Web site for more information http www ibm com db2 1inux In this chapter we introduce DB2 Version 9 5 and its offerings for Linux and provide an overview of the DB2 environment and its parallelism with Linux Along with an
412. on panel You can either select an existing connection or create a new one Figure 8 13 on page 474 Chapter 8 Application development 473 474 _ ee 2 New Data Development Project A Select Connection Choose to use a new connection or select an existing connection Create a new connection Figure 8 13 Select a new connection We are going to select a new connection for the SAMPLE database Then Figure 8 14 on page 475 is displayed If you have not had a database connection established yet the Connection Parameters panel appears automatically In the Connection Parameters panel Figure 8 14 on page 475 enter the connection information We use the SAMPLE database for the demonstration Test Connection allows you to test the connection before creating it If the database connection test succeeds click Finish The new database connection displays in the Database Explorer In the explorer tree you can view the database structure or perform database maintenance tasks If you already have a database connection established select Use an existing connection select the desired connection and click Next Then your project is created and Figure 8 16 on page 476 is displayed In our example we continue with Figure 8 14 on page 475 Up and Running with DB2 on Linux 2 New Connection Connection Parameters Select the database manager JDBC driver and required connection parameters m
413. on programming interface API db2Load Data for load can be in the form of a file a tape or a named pipe Data can also be loaded from a cursor that is defined from a query running against the currently connected database or a different database under the same instance or data can be loaded by using a user written script or application You can use the LIST UTILITIES or LOAD QUERY command to monitor the progress of the load operation Load table data through CLP Example 6 51 shows a simple LOAD command that is issued through the CLP Example 6 51 LOAD from command line db2inst1 mensa db2backup datamove gt db2 create table itemload like item in TSDATA2 DB20000I The SQL command completed successfully db2inst1 mensa db2backup datamove gt db2 export to item del of del select from item SQL3104N The Export utility is beginning to export data to file item del SQL3105N The Export utility has finished exporting 3000000 rows Number of rows exported 3000000 db2inst1 mensa db2backup datamove gt db2 load from item del of del insert into itemload Agent Type Node SQL Code Result LOAD 000 00000000 Success LOAD 001 00000000 Success PARTITION 001 00000000 Success 312 Up and Running with DB2 on Linux PRE_PARTITION 000 00000000 Success RESULTS 2 of 2 LOADs completed successfully Summary of Partitioning Agents Rows Read 3000000 Rows Rejected 0 Rows Partitioned 3000000 Summary of LOAD Age
414. on to a wse or an ese instance is supported Migration to a stand alone instance creates a stand alone instance Migration to a client instance is unsupported Migration to an ese instance is supported Migration to a stand alone or a wse instance from single database partition environments creates a stand alone or wse instance Migration to a client instance is unsupported 2 Save DBM and DB configuration settings Compare these settings before and after migration to check for any migration errors Save the DB configuration for each database partition because the DB configuration might be different Save table space and package information using the db2 list tablespaces show detail and db2 list packages show detail commands You might also want to compare this information before and after migration Up and Running with DB2 on Linux 4 Back up DB2 server configuration and diagnostic information 5 a Run the db2support command for all the databases that you are going to migrate in all of your instances See Example 4 2 Example 4 2 db2support dpfusrl gemini gt db2support dpfhome dpfusrl d dpfsamp cl 0 b Because external routine libraries are not backed up with other database objects when a database backup is performed back up all of your external routines Example 4 3 shows how to back up all external routines created using the default path Example 4 3 External routines backup cp R dpfhome dpfusr1
415. onfiguration Assistant The DAS supports the Control Center and the Configuration Assistant when working on the following administrative tasks gt Enabling remote administration of DB2 servers gt Providing the facility for job management including the ability to schedule running both DB2 and operating system command scripts gt Defining the scheduling of jobs viewing the results of completed jobs and performing other administrative tasks against jobs located either remotely or locally to the DAS using the Task Center gt Providing a means for discovering information about the configuration of DB2 instances databases and other DB2 administration servers in conjunction with the DB2 Discovery utility The DAS on Linux plus UNIX and Windows includes a scheduler to run tasks such as DB2 and operating system command scripts that are defined using the Task Center Task information includes commands to be run schedules notifications and completion actions that are associated with the task The run results are stored in a DB2 database called the Tools Catalog database The Tools Catalog database is created as part of the general setup If you did not create the Tools Catalog database when installing DB2 you can create it and activate it through the Control Center or through the CLP using the CREATE TOOLS CATALOG command For information regarding how to create the Tools Up and Running with DB2 on Linux Catalog in the DB2 Control Ce
416. ons on Linux It also discusses the parallelism on SMP and clusters and describes DB2 architecture 1 3 1 Deployment topologies DB2 for Linux can be used with a wide range of applications whether they are developed in house or pre packaged The applications can be deployed with DB2 using a number of configurations Single tier In this configuration the application and the database reside on the same system In enterprise environments it can be rare to see such a configuration because remote access to a database server is typically required Nonetheless this is quite common for developing applications that can later be deployed transparently in a multi tier DB2 environment without any changes Client Server or two tier The application and the database reside on separate systems The machines where the application runs typically have a DB2 client installed which communicates over the network to a database server For the application the physical location of the data is transparent The application communicates with the DB2 client using a standard interface for example ODBC and the DB2 client takes over the task of accessing the data over the network In certain cases such as browser or Java based access it is not necessary to for the DB2 client to run on the same machine where the application executes DB2 provides exceptional flexibility for mixing and matching client and server platforms in a heterogeneous environment DB2 client
417. onse file In the Response file name field enter the path where you want the DB2 Setup wizard to place the generated response file In our sample we save all installation settings to a file called db2wse rsp Example 2 24 shows the db2wse rsp file content Example 2 24 Sample response file db2wse rsp Product Installation LIC_AGREEMENT ACCEPT PROD WORKGROUP_SERVER_EDITION FILE db2home db2inst1 sql1ib INSTALL_TYPE TYPICAL Instance properties INSTANCE instl inst1 TYPE wse Instance owning user inst1 NAME db2instl inst1 AUTOSTART YES inst1 PORT_NUMBER 48786 Installed Languages 64 Up and Running with DB2 on Linux Installing DB2 using the response file To install DB2 using the response file use the db2setup command with the r option For example db2setup r db2home db2inst1 db2wse rsp db2_ install utility The db2_instal11 utility installs the DB2 filesets and creates a non root instance during a non root installation Many people prefer to use db2_install when installing DB2 on a large complex database system that has special requirements Installing DB2 The steps to install DB2 using db2_install are 1 Ask the Linux system administrator who has root authority to mount the DB2 product CD or DVD 2 Log in with the user ID that owns the non root installation 3 Change to the directory where the DB2 product DVD is mounted by entering the following command cd mnt dvd In t
418. ontacts or contact groups or you can remove unwanted contacts or contact groups In addition you can also verify if the e mail address specified for the contact is reachable by clicking Test as shown in Figure 7 5 on page 359 358 Up and Running with DB2 on Linux F dbzinst1 db2inst1 itsosj sanjose ibrr Change Contact db2inst1 itsosj sanjose ibm com w ee Figure 7 5 Contacts management After clicking Test if the DB2 message returned shows that the test message was sent successfully an e mail will be sent to the specified e mail account Figure 7 6 Subject Test message from the DB2 Admin Server on MENSA From db2inst mensa To db2inst itsos sanjose ibm com This message is being sent to you as a test of the DB2 Tools notification system It indicates that your E mail address has been entered as a candidate for notification of various events managed by the DB2 Tools Thank you Figure 7 6 The testing e mail that is sent by DB2 automatically Chapter 7 Monitoring and troubleshooting DB2 359 Note Before using the e mail notification function you need to make sure that the e mail system which resides on the mail server specified by SMTP_SERVER in the administration configuration is up and running normally After your contact list is added you can select Configure Alert Notification from the pop up panel Figure 7 3 on page 357 Then add the available contacts to the H
419. ontinues Consider the features of each method and decide which method is more appropriate for your environment For both online and offline reorganization you can reorganize all database partitions only one database partition or a set of database partitions You can use the DB2 Control Center for table reorganization Expand the object tree in the Control Center until you find the Tables folder Existing tables are displayed in the contents pane on the right side of the panel Right click the table or view and select Reorganize Refer to Figure 6 20 Control Center 2 Control Center Ho All Systems All Databases Fj iTsope gt a G Views G Aliases G Nicknames Cache Objects Triggers E Schemas G Indexes Table Spaces Event Monitors amp Table 17 Database partition groups Schema Buffer Pools Creator Application Objects Colurnns G User and Group Objects Actions G Federated Database Objects amp Open XML Schema Repository SR E3 Query C ITsorePL 2 Show Related te SAMPLE 9 Tootscat dp Create New T Figure 6 20 Table context menu Up and Running with DB2 on Linux In the Reorganize Table panel you can select the REORG method and various options Figure 6 21 Reorganize Table ITEM MO ininread anc writesat UGE Syeteny tet Figure 6 21 Reorganize Table panel Note that you can also schedule the REORG as a task Figure 6 22 shows you the generated command Show
420. or analysis Figure 7 34 shows sample reports DB2INST1 ITSODB Bufferpools from 12 06 53 to 12 11 52 DB2INST1 ITSODB Tables from 12 07 17 to 12 11 52 E pReads OTenporary E lReads oe OUser DB2INST1 ITSODB Sessions from 12 06 53 to 12 11 53 DB2INST1 ITSODB Memory from 12 06 53 to 12 11 53 OCpu Usage OuUtilities BActiveSessions GD Sessions OLockList E SortHeap GaAppl_menory Figure 7 34 ALL_Reports in db2top xlsb 394 Up and Running with DB2 on Linux Running db2top in snapshot collector mode Another useful function of db2top is to run db2top in snapshot collector mode and to have the system performance analyzed automatically You can use db2top with the A option to enable automatic performance analysis The db2top tool produces a report showing the top five performers Automatic performance analysis is available for any functions that are supported in background mode It is best to use this option in replay and background mode b option Valid sub options for b are gt d database I sessions t tablespaces b bufferpools T Tables D Dynamic SQL s Statements U Locks u Utilities F Federation m Memory pools vvvvvvvvvy A typical usage of automatic performance analysis is gt Running db2top in collection mode for a period of time Example 7 12 shows running db2top in collector mode for 5 minutes in the first terminal session
421. or runs on the DB2 instance that you are setting up The DB2 Health Monitor will send a notification e mail to this person at the specified e mail address when a health indicator threshold is reached If you check E mail address is for a pager device the notification message will be sent to the contact s pager Up and Running with DB2 on Linux 16 The Start copying files and create response files window provides a summary of your installation and configuration settings Scroll through this window to verify that your settings are correct and then click Finish 17 After installation read the status report tab and check for any errors If there are no errors click Finish Note Install logs are located in tmp db2setup log and tmp db2setup err 18 Because we selected Create a DB2 instance in our sample and we created an instance owner db2inst1 who uses Korn Shell ksh before running DB2 Setup wizard check if the Korn Shell profile file contains the following lines The following three lines have been added by IBM DB2 instance utilities if f db2home db2inst1 sqllib db2profile then db2home db2inst1 sq l1lib db2profile fi Using response file to install DB2 on the remaining machines After performing a partitioned installation on the primary machine the DB2 Setup wizard creates two response files db2ese_mpp rsp and db2ese_mpp_addpart rsp The db2ese_mpp rsp response file contains instructions to create an instance
422. or the Linux platform The first report that vmstats produces gives averages since the last startup Additional reports give information about a sampling period of length delay The process and memory reports are instantaneous in either case Chapter 7 Monitoring and troubleshooting DB2 417 418 The following list shows field descriptions for the output report that is generated by vmstat To acquire more information regarding this command refer to man help pages for vmstat or other Linux documentation gt Procs r The number of processes waiting for run time b The number of processes in Uninterruptible sleep w The number of processes swapped out but otherwise runnable gt Memory swpd The amount of virtual memory that is used kB free The amount of idle memory kB buff The amount of memory that is used as buffers kB gt Swap si Amount of memory that is swapped in from disk kB s so Amount of memory that is swapped to disk kB s gt 1 0 bi Blocks sent to a block device blocks s bo Blocks received from a block device blocks s gt System in The number of interrupts per second including the clock cs The number of context switches per second gt CPU us User time sy System time id Idle time Example 7 29 shows a sample report that is generated by vmstat The vmstat 2 10 command reports virtual memory statistics 10 times a
423. org gt PEAR is a framework and distribution system for reusable PHP components http pear php net gt The project development team PDT project provides a PHP Development Tools framework for the Eclipse platform http www eclipse org pdt Up and Running with DB2 on Linux 8 3 3 C and C C and C are popular and powerful programming languages under Linux Currently DB2 for Linux supports the C C programming languages and compilers that are shown in Table 8 1 Table 8 1 Supported C and C compilers Linux on x86 GNU Linux gcc versions 3 3 and 3 4 32 bit DB2 instances and compilers only Intel C Compiler Version 9 0 Linux on AMD64 EM64T x86 64 x64 GNU Linux gcc versions 3 3 and 3 4 Intel C Compiler Version 9 0 Linux on IPF IA64 GNU Linux gcc versions 3 3 and 3 4 64 bit DB2 instances and compilers only Intel C Compiler Version 9 0 Linux on POWER GNU Linux gcc versions 3 3 and 3 4 PowerPC System i and System p IBM XL C C Advanced Edition Version 7 0 for Linux Linux on System z s 390x GNU Linux gcc versions 3 3 and 3 4 In order to develop C C code you need the DB2 client installed on your system The CLI interface The Call Level Interface CLI is a C C application programming interface API to access DB2 It uses function calls to pass dynamic SQL statements It is an alternative to Embedded SOL ESQL CLI does not require host variables or a precompiler Example 8 9 shows a CLI
424. org docs 1 0 guide gt Useful information about DBI http dbi perl org gt The IBM DB2 Perl database interface Web site http www ibm com software data db2 per1 Note You can obtain more information about Perl development in Developing Perl and PHP Applications SC23 5854 If your requirements call for a Web application consider using DB2 for Linux with Hypertext Preprocessor PHP PHP excels when chosen to develop applications that need to be up and running very quickly without a large commitment of staff or budget resources You might use PHP to provide department access to DB2 data over the LAN through a Web browser or you can build an e commerce store which demands high transactional integrity on the Internet PHP is very flexible and can leverage your investment in DB2 in many innovative ways 438 Up and Running with DB2 on Linux PHP overview PHP is a scripting language that is most often embedded in HTML documents and executed on the server before output is sent to the Web browser You can also use it as a command line tool outside of the Web server environment Learning PHP is easy but developing and managing applications properly takes care Fortunately there is a large community of users and a myriad of libraries to make your job easier In particular the Zend Framework and CakePHP provide Web application foundations and database abstraction facilities which ease migration to DB2 from another data server such a
425. ormance and recoverability DB2 offers the configurable automatic table maintenance function If you are unsure about when and how to reorganize your tables and indexes and when and how to collect statistics information you can incorporate automatic reorganization as part of your overall database maintenance plan If you want to manually reorganize the tables and indexes DB2 provides a REORG utility for this purpose After finishing the reorganization tasks use the RUNSTATS utility to gather information about the physical data storage characteristics of a table and the associated indexes This information includes for example the number of records in the table how many pages are occupied by the table and the associated indexes the cluster ratio of the associated clustering index and so forth The DB2 optimizer will take advantage of these statistics when determining the access path to the data to gain better performance for subsequent database operations If you create a database in Version 9 1 or 9 5 automatic statistics collection is enabled by default With automatic statistics collection enabled the DB2 database manager automatically runs the RUNSTATS utility in the background to ensure that the correct statistics are collected and maintained Up and Running with DB2 on Linux 6 2 1 Automatic table maintenance Starting with Version 8 2 DB2 provides automatic maintenance capabilities for performing database backup keeping statis
426. ormat tool s output using a format string output 0 save output into a file follow f continuously display appended records as the file grows archive A archive a diagnostic log file Up and Running with DB2 on Linux readfile read from a file ignoring terminal input used in scripts rc display descriptions of DB2 error return codes ZRC or ECF ecfid display function info extracted from the numeric ECF ID facility fac display messages from a particular facility db2diag h lt optionl option2 option3 gt displays additional help and usage examples for one or more options specified in the options list db2diag h brief displays help for all options without examples db2diag h examples displays a few typical examples to get started db2diag h tutorial displays more advanced examples covering all features db2diag h notes displays usage notes and restrictions that apply db2diag h all displays help in the most complete form with detailed information about all options and usage examples You can obtain more information in Troubleshooting Guide Gl11 7857 and the DB2 Linux UNIX and Windows Command Reference SC23 5846 01 7 5 2 db2pd you can use the db2pd tool for monitoring and troubleshooting DB2 problems It collects information from the DB2 database system memory sets without acquiring any latches or using any engine resources and it returns the result quickly If you use
427. orted With the COMMITCOUNT option if the import is interrupted for any reason the committed rows will remain in the target table despite the failure of the import procedure You can continue the import with the option INSERT with the RESTARTCOUNT parameter to import the rest of the data Another choice is to use the REPLACE or REPLACE_CREATE option The messages file is a convenient way of monitoring the progress of an import because you can access it during the import In the event of a failed import operation you can use the message files which indicate the last row that was successfully imported to determine a point at which to restart the import operation Example 6 49 shows a part of the messages file during our import Example 6 49 Monitor IMPORT progress with the messages file db2inst1 mensa db2backup datamove gt tail 10 itemimp msg SQL3222W COMMIT of any database changes was successful SQL3221W Begin COMMIT WORK Input Record Count 2500000 SQL3222W COMMIT of any database changes was successful Up and Running with DB2 on Linux SQL3221W Begin COMMIT WORK Input Record Count 2600000 SQL3222W COMMIT of any database changes was successful Import table data using the Control Center Similar to EXPORT you also can use the DB2 Control Center to invoke the import utility Use these steps to perform the import from the Control Center 1 From the Control Center expand the object tree until you f
428. otification log for the instance is shown in the bottom pane of the panel Use the Notification Log Filter to set up a filter to Up and Running with DB2 on Linux show Health Monitor notifications only Figure 7 15 shows the notification log of our example It shows that the value of the current table space utilization is 95 percent and the severity level is Alarm The timestamp at the time that the alarm condition was triggered is also shown Journal gt Database Backup Required gt Monitor Heap Utilization gt Statistics Collection Required gt Table Space Operational State Table Space Utilization Alarm Feb 20 2008 3 30 31 db2inst1 1 ITSOD table space Alarm Feb 20 2008 3 26 51 db2inst1 0 ITSOD table space Figure 7 15 Administration notification log for Health Monitor indicator An e mail is sent to the designated contact with the content that is shown in Figure 7 16 Subject Alarm alert for ts ts_util for table space db2inst1 0 1ITSODB TBSPDMS_0 on system men From db2inst1 mensa itsosj sanjose ibm com To db2inst1 itsos sanjose ibm com ADM1O500R Health indicator Table Space Utilization ts ts_util breached the upper alarm threshold of 90 with value 95 on table space db2inst1 O ITSODB TBSPDMS_O Calculation ts ts_used_pages ts ts_usable_pages 100 1184 1248 100 95 History Timestamp Value Formula Please d
429. ou accept this license agreement for Early Release of Programs upload db2top 2 0 bin tar gz to your Linux system 4 Enter the following commands to extract db2top executable files on Linux gunzip db2top 2 0 bin tar gz tar xvf db2top 2 0 bin tar For DB2 9 5 the 32 bit db2top executable file is placed in the inux_amd_32 directory and the 64 bit db2top executable file is placed in the Jinux_amd_64 directory 7 3 2 Monitoring with db2top in interactive mode The db2top User Manual pdf is the documentation for db2top usage You also can obtain detailed online help by entering the following command in a Linux terminal db2top h A simple syntax of the db2top is db2top d dbname To start db2top issue the following command in a Linux terminal db2top d ITSODB In the previous command ITSODB is the database name in this book The db2top starting window shows in Figure 7 29 on page 388 You can press the h key to enter the help panel To get back to the original page from the help panel press Enter We provide two samples in this section Chapter 7 Monitoring and troubleshooting DB2 387 388 Figure 7 29 db2top starting window Monitoring buffer pool utilization To monitor the buffer pool utilization press the b key By default this utility refreshes the display every two seconds You can override the default refresh interval by using the command option i or by pressing i after starting db2top
430. out the data management life cycle by utilizing a consistent and integrated user interface Figure 5 1 on page 199 illustrates the life cycle of data management IBM Data Studio provides the capability for architects developers and administrators to gt Increase productivity for all roles throughout the data life cycle Cut development time up to 50 with an integrated data management environment Promote collaboration across roles to optimize data server and application performance gt Simplify and speed up the development of new skills Learn once and use with all supported data servers Extend an existing version of Eclipse plug ins to customize the environment for each team member gt Accelerate data as a service for service oriented architecture SOA Develop and publish data as a Web service without programming Info 2 0 Ready support for Web 2 0 protocols and format Up and Running with DB2 on Linux Data Modeling Data access Data Server Administration Secure Data Development Logical Modeling sa SOL Configuration Archiving COBOL PHI Physical Modeling XQuery Performance Data Privacy User Defined Recovery Encryption Functions Design Develop Deploy Manage Govern Security Access Figure 5 1 Data management life cycle IBM Data Studio supports DB2 and Informix Dynamic Server IDS on all platforms including i5 OS It is a full replacement for DB2 Developer Workbench
431. overy A crash recovery might be needed after a severe error or condition that causes the database or the database manager to end abnormally Units of work UOW that have not been flushed to disk at the time of failure leave the database in an inconsistent state The database needs to be recovered By default DB2 starts crash recovery automatically to attempt to recover the database If you do not want the automatic restart behavior set the AUTORESTART database configuration parameter to OFF You will need to issue the db2 restart database command manually when a database failure occurs The administration notification log records information about crash recovery Version recovery Version recovery means to restore the database to the point in time when the database backup was taken The database backup image file used was created during a backup operation Every unit of work after the time of the backup is lost Version recovery can be used with non recoverable databases databases without archived logs It also can be used with recoverable databases by using the WITHOUT ROLLING FORWARD option on the RESTORE DATABASE command Full database restore from an offline backup A full database restore example from an offline backup is db2 restore db itsodb from db2backup taken at 20080204081423 If the offline database backup was taken from a recoverable database you have to use the WITHOUT ROLLING FORWARD clause within the restore command to
432. ows you how N is used for the calculation of the path name Table 3 1 Calculation of N assuming the partition number is 10 ne ee a blank 9n bank N number blank N number number N 1 5 blank N number number N 4 2 el is the modulo function Use the following command to run the create database script db2 tvf crdb sql After the database is created you can connect to the database as shown in Example 3 16 on page 115 We also list the table spaces in the catalog node mensa 114 Up and Running with DB2 on Linux Example 3 16 List table spaces on mensa db2instl mensa gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2instl mensa gt db2 list tablespaces Tablespaces for Current Database Tablespace ID 0 Name SYSCATSPACE Type System managed space Contents All permanent data Regular table space State 0x0000 Detailed explanation Normal Tablespace ID 1 Name TEMPSPACE1 Type System managed space Contents System Temporary data State 0x0000 Detailed explanation Normal Tablespace ID 2 Name USERSPACE1 Type Database managed space Contents All permanent data Large table space State 0x0000 Detailed explanation Normal DB210111 In a partitioned database server environment only the table spaces on the current node are listed
433. paces Event Monitors G Database partition groups Creator Buffer Pools Columns 5 Application Objects Actions User and Group Objects Open G Federated Database Objects E Query XML Schema Repository SR 2 Show Related Obje O ITSOREPL O SAMPLE q Create New Table A TooiscaT Figure 6 29 Table context menu You can choose EXPORT to open the export table notebook Refer to Figure 6 30 on page 306 You can choose the output file format of export under the File Format options or you can input the SQL statement manually or by SQL Assist Wizard under the SELECT statement area In the Messages file field you can specify the messages file to be created for the error warning and informational messages associated with the EXPORT operation In addition if you want to know the command that DB2 generated for this task click Show Command A pop up panel appears showing the generated command Furthermore you can use the Schedule function that is provided by DB2 to schedule a time to run this export task by choosing the Schedule tab on the panel Chapter 6 Administering databases 305 E Export Table ITEM x 7 db2backup datamove itemcc del e CONNECT TO ITSODB EXPORT TO db2backup datamove itemcc del OF DEL MESSAGES db2backup datamove expcc msg SELECT FROM DB2INST1 ITEM WHERE ITEMID lt 100 CONNECT RESET SELECT FROM DB2INST1 ITEM WHERE ITEMID lt 100 db2backup datamove expcc msg e 0K Res
434. page 280 we used the GET SNAPSHOT command from the DB2 command line CLP to monitor the inplace table reorganization You can also capture a snapshot from administrative views SQL table functions or by using the snapshot monitor APIs in a C or C application There are several snapshot administrative views available for you to query the snapshot information Example 7 22 shows the list Example 7 22 Snapshot administrative views db2instl mensa db2 select substr tabschema 1 10 tabschema substr tabname 1 30 tabname from syscat tables where tabname like SNAP TABSCHEMA TABNAME SYSIBMADM SNAPAGENT SYSIBMADM SNAPAGENT_MEMORY_POOL SYSIBMADM SNAPAPPL SYSIBMADM SNAPAPPL_INFO SYSIBMADM SNAPBP SYSIBMADM SNAPBP_PART SYSIBMADM SNAPCONTAINER SYSIBMADM SNAPDB SYSIBMADM SNAPDBM SYSIBMADM SNAPDBM_MEMORY_POOL SYSIBMADM SNAPDB_MEMORY_POOL SYSIBMADM SNAPDETAILLOG SYSIBMADM SNAPDYN_SQL SYSIBMADM SNAPFCM SYSIBMADM SNAPFCM_PART SYSIBMADM SNAPHADR SYSIBMADM SNAPLOCK SYSIBMADM SNAPLOCKWAIT SYSIBMADM SNAPSTMT SYSIBMADM SNAPSTORAGE_PATHS SYSIBMADM SNAPSUBSECTION SYSIBMADM SNAPSWITCHES SYSIBMADM SNAPTAB SYSIBMADM SNAPTAB_REORG SYSIBMADM SNAPTBSP SYSIBMADM SNAPTBSP_PART SYSIBMADM SNAPTBSP_QUIESCER Up and Running with DB2 on Linux SYSIBMADM SNAPTBSP_RANGE SYSIBMADM SNAPUTIL SYSIBMADM SNAPUTIL_PROGRESS 30 record s selected Each snapshot view returns a table with one row per monitored object per database partition
435. pages 52160 Accessible Yes If you create your table space with a size that is smaller than the highest possible size for that device you will see a message in the file db2diag log as shown in Example 3 6 on page 102 Chapter 3 Post installation tasks 101 102 Example 3 6 db2diag log message if the table space is too small 2008 02 11 11 07 25 876502 480 E288662G688 LEVEL Warning PID 4185 TID 2976902048 PROC db2sysc 0 INSTANCE db2inst1 NODE 000 DB ITSODB APPHDL 0 21 APPID LOCAL db2inst1 080211185714 AUTHID DB2INST1 EDUID 25 EDUNAME db2agent ITSODB 0 FUNCTION DB2 UDB buffer pool services sqlbDMSAddContainerRequest probe 105 MESSAGE ADM6037W Container dev sdb5 was created to be 208840 KB in size on a device that is 208864 KB in size Extra storage will be wasted The container can be extended to use the wasted space by using ALTER TABLE SPACE Automatic storage for databases Automatic storage is a new feature introduced in DB2 9 1 It simplifies storage management for table spaces When you create a database you specify the storage paths where the database manager will place your table space data The database manager will manage the container and space allocation for the table spaces as you create and populate them Databases are created with automatic storage on by default If you do not want to enable it create the database with the option AUTOMATIC STORAGE NO Note You cannot change t
436. pane At each of these actions you can watch as the query is constructed according to your actions in the upper pane 6 As the last step we add a condition on the SALARY column Select Conditions on the bottom pane Double clicking a field opens the field for you to enter a value or use the drop down list box to choose a value We select EMPLOYEE SALARY in the Column field choose lt for the operator and enter the value 37000 in the value column Now we have finished the steps Figure 8 19 on page 479 shows the complete Query Builder window after our changes Up and Running with DB2 on Linux m j EmpSalary X SELECT IE2INSTL EMPLOYEE FMPNO DE2 INSTL FMPLOYEE LASTNAME DE2INSTL DEPARTMENT DEP TNO TE2INSTL DEPARTMENT DEP TNAME TROM IE2INSTL FMPIOYEE JOIN DE2INSTL DEPARTMENT ON DE2INSTL FMPLOYEE WORKDEPT DE2INSTL DEPARTMENI WHERE IDB2INSTL FMPILOYEE SALARY lt 37000 Z EMPNO Z DEPTNO 7 FIRSTNME Z DEPTNAME T MIDINIT 4 amp 0 MGRNO H Z LASTNAME C ADMRDEPT DEPARTMENT WORKDEPT C LOCATION PHONENO HIREDATE JOB Statement EmpSalary E DISTINCT Columns Conditions Groups Group Conditions DB2INST1 EMPLOYEE SALARY lt Figure 8 19 Query Builder We can save our query Select File Save In the panel select our DataProject project as shown in Figure 8 20 m i3 Save As Save As Save file to another location Enter or select t
437. parameter 37000 and click Debug The Data Studio will switch to the Debug Perspective Depending on your settings the Data Studio asks you to confirm the switch In the Debug Perspective Figure 8 40 you can step through the code view variables change values and do everything you need to debug your code 0 EmpSalary sql 80 EMPSALARY J EMPSALARY java xa _ ip ClassLoader class srec stored Procedure MMPSALARY Package db2instl import java sql grec classes public class FMPSALARY public static void eMPSALARY int SALARY Resultset rsl throws SQLException Exception Get connection to the database Connection con DriverManager getconnection jdbc default connection PreparedStatement stmt null boolean brlag FROM EMPLOYEE JOIN DEPARTMENT ON FMPLOYEE WORKDEPT DEPARTMENT DEP TNO a WHERE PMPLOYEE SALARY lt SALARY stmt con prepareStatement sql brlag stmt execute rsL 0 stmt getResultset 1 String sql sql SELECT PMPIOYER EMPNO FMPIOYER LASTNAME DEPARTMENT DEPTNO DEPARTMENT DEP TNAME li l a Figure 8 40 Debug stored procedure 490 Up and Running with DB2 on Linux The Data Studio is a powerful tool to perform application development with DB2 It takes many error prone tasks away from you It supports you in developing application code makes entering table and column names easy and provides intelligent defaults for th
438. path Example 7 25 shows you the output of the db21s command from our environment Example 7 25 Output of the db2Is command db2inst1 mensa db2home db2inst1 gt db21s Install Path Level Fix Pack Special Install Number Install Date Installer UID opt ibm db2 V9 5 0 0 Fri Jan 25 15 52 16 2008 PST 0 opt ibm db2 V9 1 3 3 Tue Jan 29 09 35 07 2008 PST 0 412 Up and Running with DB2 on Linux The db21s command lists the path where DB2 products are installed on our system and the DB2 product level To get more information for each DB2 product that is installed on the system you can use the commands that are shown in Example 7 26 Example 7 26 List product information db2inst1 mensa db2home db2inst1 gt db21s q p b opt ibm db2 V9 5 Install Path opt ibm db2 V9 5 Product Response File ID Level ENTERPRISE_SERVER_EDITION 9 5 0 0 Install Path opt ibm db2 V9 5 Fix Pack Product Description 0 DB2 Enterprise Server Edition db2inst1 mensa db2home db2inst1 gt db21s q b opt ibm db2 V9 5 Fix Pack Feature Description Feature Response File ID Level BASE_CLIENT 9 5 0 0 JAVA_SUPPORT 9 5 0 0 SQL_PROCEDURES 9 5 0 0 BASE_DB2_ENGINE 9 5 0 0 JDK 9 5 0 0 CONNECT_SUPPORT 9 5 0 0 COMMUNICATION SUPPORT_TCPIP 9 5 0 0 REPL_CLIENT 9 5 0 0 CONTROL_CENTER 9 5 0 0 DB2_DATA_SOURCE_SUPPORT 9 5 0 0 LDAP_EXPLOITATION 9 5 0 0 INSTANCE_SETUP_SUPPORT 9 5 0 0 XML_EXTENDER 9 5 0 0 APPLICATION _DEVELOPMENT_TOOLS 9 5 0 0 FIRST_STEPS 9 5 0
439. pical option the Base application development tools require a separate installation 1 Introduction 2 Software License Agreement 3 Installation type 4 Installation action J retell anor rectory Select the installation type C Typical 400 490 MB Compact 390 470 MB AE _ Custom 390 680 MB Information about the installation type f Q OF Typical em The typical setup includes basic database server function database administration tools and most product features and functionality B To add features for application development and other optional functionality later in the setup process click Custom pa To view all available features and those selected for a typical installation press the View Features button p View Features z 4 Back Next gt sh Cancel Help Figure 2 1 Non root installation Select the installation type Chapter 2 Installation 61 6 On the Select installation response file creation or both window as shown in Figure 2 2 we recommend that you select Install DB2 Workgroup Server Edition Version 9 5 on this computer and save my settings in a response file Then click Next fdb2home db2inst1 db2wse rsp Figure 2 2 Non root installation Select installation response file creation or both 7 On the Installation directory window as shown in Figure 2 3 click Next db2home db2inst1 sqiliby B
440. ploying the product in the enterprise 1 2 DB2 for Linux features and offerings This section provides a description of DB2 Version 9 5 features supported platforms and product offerings 1 2 1 Features DB2 is an open standards multi platform relational database system that is strong enough to meet the demands of large corporations and flexible enough to serve medium sized and small businesses Its features include gt Exploitation of symmetric multiprocessing SMP and cluster based parallelism gt Federated support for a variety of data sources Chapter 1 Introduction 3 gt Advanced built in online analytical processing OLAP and business intelligence functions Ability to manage multiple data types including Binary Large Objects Built on open industry standards SQL Distributed Relational Database Architecture DRDA command line interface CLI Open Database Connectivity ODBC Java Database Connectivity JDBC and more Leader in query optimization technology and performance Stored procedures user defined functions UDFs data encryption and globalization Fully Web enabled and certified for leading enterprise applications High Availability features and Failover support high availability disaster recovery HADR Tivoli System Automation TSA and more Java 2 Platform Enterprise Edition J2EE certified and Java application interfaces for JDBC and SQLJ Support for open source inte
441. ports stored procedures SPs user defined functions UDFs and triggers all of which are used to develop applications You can develop the applications from the command line or you can use the Data Studio 8 2 1 Triggers 428 A trigger is a defined set of SQL statements that is stored as a DB2 object ina DB2 database This set of SQL statements executes when a certain event occurs against a DB2 table Types of events that might invoke triggers are Insert Update or Delete to a given DB2 table You can set up triggers to execute before after or instead of an insert update or delete event gt No cascade before The defined action will be executed before the triggering action is performed gt After All triggered actions will be applied when the triggering action is done gt Instead of The original action will be replaced by the action defined in the trigger Triggers are defined by using the create trigger Data Definition Language DDL statement Note The CREATE TRIGGER statement is explained in more detail in the Information Center in Database fundamentals SQL Statements gt CREATE TRIGGER and in SQL Reference Volume 2 SC10 4250 Triggers are useful to implement business logic in a central place A trigger becomes part of the transaction that fires it Example 8 1 demonstrates how to create a trigger to audit changes on either the SALARY or the BONUS column in the EMPLOYEE table of our SAMPLE database
442. provides greater control while using restricted sensitive privileges and allows middle tier servers or applications to assert the identity of the user to the database server gt Self tuning memory allocation Self tuning memory provides a configuration that is dynamic and responsive to significant changes in workload characteristics including dynamic fast communication manager 6 Up and Running with DB2 on Linux FCM buffers and new configuration parameters that can be tuned automatically by the DB2 database manager Label based access control LBAC This feature increases the control you have over who can access your data LBAC lets you decide exactly who has write access and who has read access to individual rows and individual columns Automatic statistics DB2 automatically runs the RUNSTATS utility in the background to ensure that the correct statistics are collected and maintained by default when you create databases Product licenses DB2 provides easier management of product licenses using the License Center and the db21icm command Licensing changes for the DB2 Runtime Client allow you to freely distribute it Multiple DB2 versions DB2 provides the ability to install multiple DB2 versions and fix packs on the same computer Administrative SQL routines and views The administrative routines and views provide a primary easy to use programmatic interface to administer the DB2 database product through SQL DB2 9 5 provides mo
443. r 44 mirrored logs 43 mobile devices 10 module 433 monitoring memory 381 multiple partition environment MPE 493 multithreaded architecture 5 multi tier 11 multi tier application 5 N Navigator 214 netstat 423 network 414 Network File System NFS 47 48 NFS 47 423 NFS server machine 43 nfsstat 423 No cascade before 428 no_root_squash 49 nodegroups 15 non root 36 normal state 177 notification 38 39 355 357 360 368 NUM_POOLAGENTS 136 O object setting 362 ODBC 4 434 offline backup 229 offline reorganization 281 OLAP 4 OLD DB 434 OLTP 13 online backup 240 online table reorganization 281 Oracle RAC 18 OS 390 12 outline view 214 P package cache 133 package group 202 paging 417 parallel O 98 parallel processing 16 parallelism 3 parameter 30 partial declustering 23 partition group 15 22 partitioned database environment 45 PDO_IBM 439 PDO_ODBC 439 performance 2 42 Perl 4 433 434 Perl Database Interface 435 personal digital assistants PDAs 10 perspective 212 pgrep 423 PHP 4 physical partition 22 physical storage devices 16 pkill 423 point in time 230 pop up window 360 processor time 414 processors 19 procps 417 programming laguage 434 project explorer 216 Project Management 199 protocol 65 78 198 proxy component 13 pstree 423 public key based authentication 54 Python 4 Q query 14 R rah 494 raw device 35 40 99 real time statistics 182
444. r workstation v Yv y DB2 client or server Perl 5 8 or later DBI 1 41 or later DBD DB2 driver Here is the installation procedure 1 Install DB2 on your workstation Refer to Chapter 2 Installation on page 25 for the instructions to install DB2 on Linux Install Perl 5 Perl is typically provided by the Linux distributions but you can download it from http www cpan org Build test and install the DBI module DBI is an open standard application programming interface API that provides database access for client applications that are written in Perl Usually the Perl DBI module is shipped with your Linux distribution If you want to install it you can download it from the CPAN Web site at http www cpan org modules by category 07_Database_Interfaces DBI Refer to the readme file on this Web site for installation instructions Chapter 8 Application development 435 436 4 Build test and install the DBD DB2 driver The DBD DB2 driver works with DBI and a DB2 client to access databases The latest DB2 Perl DBI driver can be downloaded from http www ibm com software data db2 per1 At the time of writing the latest available driver was DBD DB2 1 1 a Ensure that the C compiler is installed which is needed for compiling the Perl module In order to compile the module you need the DB2 client installed on your system b Before installing the DBD DB2 driver enable the DB2 environment
445. ral tools that can help you monitor and troubleshoot the DB2 system We introduce several of these helpful tools and provide examples of their usage Chapter 7 Monitoring and troubleshooting DB2 401 7 5 1 db2diag The db2diag log file contains information about the DB2 system as it runs You need to view this log periodically You can use the db2diag analysis tool to filter and format the db2diag log file As an alternative to using db2diag you can use a text editor to view the diagnostic log file on the machine where you suspect a problem has occurred The most recent events that were recorded are at the end of the file Note The administration and diagnostic logs grow continuously When they get too large back them up and then erase the files A new set of files is generated automatically the next time that they are required by the system Here we illustrate examples of using db2diag gt Run the db2diag command without any option db2instl mensa gt db2diag If you use the db2diag command without any parameter the tool processes the db2diag log file from the current directory and prints it to the display If the file is not found in the current directory the directory that was set by the DIAGPATH variable is searched Observe the db2diag log file during run time in console mode To view the growth of the db2diag log file use db2diag f This command displays all of the records that were written to the db2diag log file
446. rchased a WebSphere Replication Server or WebSphere Federation Server Concurrent Connector policy enter the following command db2licm c wsfs concurrent or db2licm c wsrs concurrent If you are unsure about the product identifier wsfs or wsrs use the following command to discover the product identifier db2licm 1 Changing the enforcement policy The default enforcement policy is Soft Stop This means that all connections to DB2 databases are permitted to connect even when the license policy is violated When a violation occurs a license violation message is written to db2diag log The Hard Stop enforcement policy does not permit any connections that violate the license policy To change the enforcement policy from Soft Stop to Hard Stop enter the following command db2licm e db2ese HARD To change the enforcement policy from Hard Stop to Soft Stop enter db2licm e db2ese SOFT Generating a compliance report To verify the license compliance of DB2 features you can generate a compliance report It lists DB2 features out of compliance with your current product entitlement Each DB2 feature status is listed as either gt In compliance The feature has been used and is properly licensed gt Violation The feature is not licensed and has been used Chapter 3 Post installation tasks 165 To generate a compliance report use the following command db2licm g lt filename gt where lt filename gt specifies the name o
447. rchive Figure 6 6 Primary archive log path You can go through all the pages to configure all of the related database logging parameters After enabling log archiving DB2 sets the database into the backup pending state to ensure that a full offline backup is taken before starting with log archiving To perform the backup in a single database partition environment use the following command db2 backup db itsodb to db2backup In a partitioned database environment there are different ways to take the backup We explain taking the backup in more detail in 6 1 4 Backup utility on page 240 For now Example 6 1 on page 234 shows one way of backing up a partitioned database Chapter 6 Administering databases 233 234 Example 6 1 Back up all database partitions db2inst1 mensa gt db2 backup db itsodb on all dbpartitionnums to db2backup Part Result 0000 DB20000I The BACKUP DATABASE command completed successfully 0001 DB20000I The BACKUP DATABASE command completed successfully Backup successful The timestamp for this backup image is 20080201170437 Now the database is ready for log archiving To verify that the database is ready for log archiving use the following commana db2 archive log for itsodb The active log files will be archived from the log directory to the db2archive directory DB2 uses the following subdirectory structure for the archived log files lt logarchpath gt instance DBNAME PARTITION C
448. rdinating resources and locks between nodes For example if Node 1 wants to access data on a certain disk that has been locked for update by another node in the cluster Node 1 must wait for other nodes to complete their operations While this works well when there are few nodes in the cluster for example mainframe environments the overhead for distributed lock management and cache coherency issues can severely limit scalability and introduce performance degradation for four or more nodes making it impractical to exploit the economies of large clusters on Linux Furthermore this approach involves specialized hardware and software for shared disk and cache management making it much more expensive than shared nothing Shared nothing As the name implies partitions nodes in a shared nothing environment do not share processors memory or disks with partitions on other machines Each partition acts on its own subset of data Because each partition has its own private resources this approach does not involve any resource contention with other servers lending itself to virtually unlimited scalability This is one reason DB2 for Linux can support up to 1 000 partitions And because there is no coordination overhead for accessing resources additional machines can easily be added to the cluster with linearly scalable performance which implies if doubling of the data volume is matched by the doubling of the cluster resources Chapter 1 Introduc
449. re views 1 2 2 Supported platforms IBM is committed to Linux and supports it on a variety of hardware platforms Nowadays DB2 products are supported on the following hardware v gt x86 Intel Pentium Intel Xeon and AMD 32 bit Intel and AMD processors x64 64 bit AMD64 and Intel EM64T processors POWER IBM OpenPower System i or System p systems that support Linux System z or System z9 The supported operating systems for Linux include vvvvy Red Hat Enterprise Linux RHEL 4 Update 4 Red Hat Enterprise Linux RHEL 5 SUSE Linux Enterprise Server SLES 9 Service Pack 3 SUSE Linux Enterprise Server SLES 10 Service Pack 1 Ubuntu 7 10 For the latest information about supported Linux distributions refer to http www 306 ibm com software data db2 1inux validate To create and run Java applications and Java based tools IBM JDK is required For convenience the IBM SDK 5 SR5 is shipped on DB2 9 5 CDs and Chapter 1 Introduction 7 in most cases is automatically installed with the DB2 installation Refer to the validation Web site for the most up to date list of supported products because the list of supported products is updated frequently Note Non IBM versions of the Software Developers Kit SDK for Java are supported only for building and running stand alone Java applications For building and running Java stored procedures and user defined functions only the IBM SDK for Jav
450. reate a script within another tool and save it to the Task Center import an existing script or save the options from a DB2 dialog or wizard such as the Load wizard A script can contain DB2 commands SQL or operating system commands For each task by using the Task Center you can gt Schedule the task gt Specify success and failure conditions gt Specify actions that must be performed when this task completes successfully or when it fails gt Specify e mail addresses including pagers that need to be notified when this task completes successfully or when it fails You can specify conditional coding by creating task actions Each task action consists of a task and the action that is performed by the task For example task one can have the following task actions gt If task one is successful task action A enables the schedule for task two gt f task one fails task action B runs task three The following sample with detailed steps creates a task within the Task Center Task scheduling is also included The steps are 1 Start the Task Center and create a new task Figure 6 46 on page 343 Up and Running with DB2 on Linux Task Center ommand Testing task for demonstrat mensa Figure 6 46 Task Center main panel 2 Provide general information input for a new task Figure 6 47 on page 344 You can input general information for a task in this panel for example the name and type of the task t
451. reating a table you can decide to have certain objects such Chapter 1 Introduction 15 as indexes and large object LOB data kept separately from the rest of the table data A table space can also be spread over one or more physical storage devices Table spaces reside in database partition groups Table space definitions and attributes are recorded in the database system catalog Containers are assigned to table spaces A container is an allocation of physical storage such as a file or a device A table space can be either system managed space SMS or database managed space DMS For an SMS table space each container is a directory in the file space of the operating system and the operating system s file manager controls the storage space For a DMS table space each container is either a fixed size pre allocated file or a physical device such as a disk and the database manager controls the storage space Tables A relational database presents data as a collection of tables A table consists of data logically arranged in columns and rows All database and table data is assigned to table spaces The data in the table is logically related and relationships can be defined between tables Data can be viewed and manipulated based on mathematical principles and operations called relations Table data is accessed through Structured Query Language SQL a standardized language for defining and manipulating data in a relational database
452. reating is required This approach works for simpler XML structures For more complex and more nested XML structures you have to create a much more complex relational data model DB2 pureXML supports the native storage of XML data in the DB2 database It allows you to work on the XML attributes using SQL statements or XQuery directly You can create indexes on particular XML attributes based on XQuery expressions Example 8 25 shows a simple XML document Example 8 25 Simple XML document products xml lt products gt lt product xmlns http posample org pid 10 gt lt description gt lt name gt Fleece jacket lt name gt lt price gt 19 99 lt price gt lt description gt lt product gt lt product xmIns http posample org pid 11 gt lt description gt lt name gt Nylon pants lt name gt lt price gt 9 99 lt price gt lt description gt Chapter 8 Application development 455 lt product gt lt products gt DB2 pureXML stores the XML data in the database in a tree structure DB2 pureXML does not store the XML document in text format but it parses the document and stores the attribute values in a tree The attribute names are not stored in the tree but in a lookup table This storage model provides efficient data retrieval The DB2 components such as indexes explain the programming languages and the optimizer support this XML data model too Figure 8 3 shows the storage layout for the XML document
453. rebind package 181 reboot 417 recommendation 170 recoverable database 229 recovery history file 236 recovery log 15 recovery time 5 Redbooks Web site 510 Contact us xvi redirected restore 265 redistribute command 127 registry 132 registry variable 181 registry variables db2rshcmd 86 ReiserFS 41 relational database 15 relations 16 response file 39 51 restore pending state 177 revoke statements 175 REXX 434 Rivest Shamir Adleman algorithm 54 rollforward pending state 177 root_squash 49 row function 429 rows 16 RSA 54 runtimes 224 Index 515 S sartest bin 421 scalability 2 18 scalar function 429 scaling out 17 scaling up 17 Schema Management 199 scp 93 SCSI 41 secondary logs 44 security access control 199 security control 97 Self Managing and Resource Tuning SMART 3 self tuning memory 6 semaphore array 30 semicolon 432 several ways to install DB2 79 shared 18 shared memory segment 30 shared resources directory 202 shared disk 18 19 shared nothing 18 19 single processor 16 single system view 241 single tier 11 Small Computer System Interface 41 SMP architectures 17 SMTP_SERVER_ 360 sortmemory 133 SQL 4 SQL Builder 199 SQL procedure 431 SQL Routine Debugger 199 SQL statement 433 ssh_known_hosts 55 sshd_config 54 SSV 241 SSV backup 242 standby cluster 13 starschemas 14 stored procedure 4 428 431 489 Structured Query Language SQL 16 subnet mask 29
454. reboot unless they are saved in the etc sysctl conf file To make the changes effective after every reboot SUSE Linux Make boot sysctl active su root chkconfig boot sysctl boot sysctl off chkconfig boot sysctl on chkconfig boot sysctl boot sysctl on Red Hat The rc sysinit initialization script will read the etc sysctl conf file automatically 2 1 7 Additional software requirements Depending on your DB2 requirements you might be required to install additional software packages for DB2 to function properly Make sure that the following software is installed prior to using DB2 gt IBM Software Development Kit SDK for Java is required to run DB2 graphical tools and to create and run Java applications including stored procedures and user defined functions If the correct version of SDK is not already installed IBM SDK 5 Service Release 5 will be installed for you during the installation process if you use either the DB2 Setup wizard db2_install or a response file to install the product IBM SDK 1 4 2 to SDK 5 is also supported Note On Linux DB2 GUI tools only run on x86 and x86_64 AMD64 EM64T One of the following browsers is required to view online help and to run First Steps db2fs Mozilla 1 4 and up Firefox 1 0 and up 2 The db2_install utility does install the JDK for you 32 Up and Running with DB2 on Linux gt X Window System software capable of rendering a grap
455. releasing the first database for clustered environments on Linux showcasing the first commercial database for Intel and AMD powered 64 bit platforms and continually being first to announce industry leading benchmarks on Linux The IBM commitment to Linux is further reflected through its ongoing efforts to exploit and enhance the Linux kernel for database workloads IBM is the market leader in Linux for relational database systems The reasons why major companies and governments around the globe choose to deploy DB2 for Linux in the enterprise setting are quite simple The DB2 rich set of features has been running on Linux almost four years and during this time while the Linux kernel matured through the efforts of thousands of programmers and volunteers the IBM teams were busy further hardening the kernel and DB2 on Linux for enterprise workloads Today DB2 is the most versatile and powerful database on Linux and capable of effectively handling terabytes of data in both decision support and transactional environments The combination of DB2 and Linux is a robust database platform for a variety of solutions and vertical applications including gt Back end for Web and application servers gt Business Intelligence and Data Warehousing gt Transactional enterprise systems gt Enterprise applications such as Enterprise Resource Planning ERP Customer Relationship Management CRM and Supply Chain Management SCM gt Information In
456. required You can specify the initial size the maximum size and the increase size Raw devices You can create DMS table space containers on block devices directly This approach offers superior performance but also requires more administration Note Prior to Version 9 direct disk access using a raw controller utility on Linux was used This method is now deprecated and its use is discouraged The database manager will still allow you to use this method if the Linux operating system still supports it however there will be a message in the db2diag log indicating that its use is deprecated DB2 also allows you to create normal SMS and DMS table spaces in the file system with the option NO FILE SYSTEM CACHING The term normal means that they are created in the file system and not as raw devices This option which is the same for raw devices will bypass the double buffering caused by the file system buffer and the buffer pools However device files still have a slight performance advantage over table spaces created with the NO FILE SYSTEM CACHING option because device files do not have any file system administration overhead Device files also offer slightly better availability because they are not dependent on file system failures Because long data bypasses the buffer pools we do not recommended placing long table spaces in raw devices For the same reason we do not recommend that you place the catalog table space on raw device
457. rfaces such as Hypertext Preprocessor PHP Python and Perl Native XML support A graphical integrated toolset for managing local and remote databases Productivity tools for visual development and migration Support for the InfiniBand I O high speed interconnect Exploitation of the latest Linux Kernel capabilities Innovative self managing technologies to reduce DBA intervention Tools and wizards for monitoring and performance tuning Simplified management of large scale databases on clusters Federated Web Services for Information Integration Connection Concentrator for high user scalability Dynamic configuration without the need for restarting database Online tools and utilities such as REORG LOAD and storage and memory management Multidimensional clustering for improved performance of complex queries DB2 has been commercially available on Linux since Version 6 DB2 for Linux UNIX and Windows LUW continuously offers industry leading performance scale and reliability database features and functions XML is supported natively in DB2 9 1 DB2 9 5 extends its innovative abilities as a hybrid data server and 4 Up and Running with DB2 on Linux cost savings of deep compression to enable rapid use of data staying ahead of threats and extracting the full value of XML data in operational processes The new and enhanced DB2 9 5 features include gt pureXML Introduced in DB2 9 1 pureXML provides the capability to stor
458. ring databases 0020005 227 6 1 DB2 database backup and recovery 0 0c eee eee eee 228 6 1 1 Enable rollforward recovery and log archiving 230 6 1 2 Recovery history file 0 0 0 e eee ee eee 236 6 1 3 Enable usage of Tivoli STorage Manager 237 6 1 4 Backup utility siekis sda Pua t ba te Le yee tae dewey 240 6 1 5 DB2 database recovery 0 cece te eee 254 6 1 6 Redirected restore sample scenario eee eae 265 6 1 7 Recovering a dropped table sample scenario 269 6 2 Table index reorganization and statistics collection 274 6 2 1 Automatic table maintenance 0 00 cee eee eee 275 6 2 2 Manual table maintenance 0 000 eee eee 280 6 3 Moving data using EXPORT IMPORT LOAD and db2move 303 6 3 1 Export data to files from database tables and views 303 Contents v 6 3 2 Import data from files into database tables or views 306 6 3 3 Load data from files into database tables 311 6 3 4 Using the db2move utility 0 0 cee ee eee 336 6 4 Task Center Scheduler and DB2 Tools Catalog 340 6 4 1 DB2 Administration Server and Tools Catalog Database 340 6 4 2 Task Center and Scheduler 0 00 0c ee ee eeee 341 Chapter 7 Monitoring and troubleshooting DB2 353 7 1 Health Monitor an
459. rmDefaul t qualified gt lt element name products type tns productsType gt lt el ement gt Chapter 5 IBM Data Studio 217 218 lt complexType name descriptionType gt lt sequence gt lt element name name type string gt lt element gt lt element name price type double gt lt element gt lt sequence gt lt complexType gt lt complexType name productType gt lt sequence gt lt element name description type tns descriptionType minOccurs 1 maxOccurs 1 gt lt element gt lt sequence gt lt attribute name pid type int gt lt attribute gt lt complexType gt lt complexType name productsType gt lt sequence gt lt element name product type tns productType minOccurs 1 maxOccurs unbounded gt lt element gt lt sequence gt lt complexType gt lt schema gt Figure 5 18 shows how the XSD document looks in the XML schema editor ema http example org ema Directives i Elements e products productsType E descriptionType E productsType i productType Figure 5 18 Top view of the XSD If you double click the products element on the left side of the panel shown in Figure 5 18 you can see its definition Figure 5 19 on page 219 Up and Running with DB2 on Linux productsT ype eos e product 1 productT ype Figure 5 19 Definition of the products element Double clicking the title bar of the products
460. rned status 1 Node number 0 Chapter 6 Administering databases 259 260 Rollforward status TBS working Next log file to be read S0000003 LOG Log files processed Last committed transaction 2008 02 06 22 52 06 000000 UTC DB20000I The ROLLFORWARD command completed successfully db2inst1 mensa gt db2 rollforward db itsodb stop tablespace userspacel online Rollforward Status Input database alias itsodb Number of nodes have returned status 1 Node number 0 Rollforward status not pending Next log file to be read Log files processed Last committed transaction 2008 02 06 22 52 06 000000 UTC DB200001 The ROLLFORWARD command completed successfully The minimum recovery time is updated by DB2 when data definition language DDL statements are run against the table space or against tables in the table space The table space must be rolled forward to at least the minimum recovery time so that it is synchronized with the information in the system catalog tables During a table space rollforward each log file needs to be read even if the log file does not contain log records that affect that table space This phase can be time consuming To skip those log files that are known not to contain any log records that affect the specific table space set the DB2_COLLECT_TS_REC_INFO registry variable to ON the default value The table space change history file db2tschg his keeps track of which logs need to be
461. rom the network through a TCP IP port Security considerations for DB2 on the Linux level are done based on that assumption File system permissions When an instance is created DB2 places all DB2 under the home directory of the instance user ID These files must be accessible by users who want to use this instance All further files that you create such as table space containers transaction logs archive logs backups diagnostics log and so on do not need to be accessible by the users directly Therefore you can restrict their permission to only the instance user Many Linux systems have set the umask to 0022 by default which makes all newly created files readable by everyone If security is a concern consider setting the umask to 0027 for the instance user Chapter 3 Post installation tasks 149 150 Fenced user ID UDFs and stored procedures can be configured so that they run under the fenced user ID to shield the UDFs from the core of the database manager So a crashing UDF cannot bring down the database manager Running UDFs and stored procedures under the fenced user ID adds communication overhead to the call of the UDF though The use of fenced user IDs can serve also another purpose It allows them to run under a different user ID than the database manager So they cannot access the files of the database instance directly It also prevents buffer overflows from taking excessive database resources The fenced user
462. rows from a source file in DEL format While the load runs we try to access the table from another session Example 6 55 Load data with ALLOW READ ACCESS db2inst1 mensa db2backup datamove gt db2 drop table itemload DB20000I The SQL command completed successfully db2inst1 mensa db2backup datamove gt db2 create table itemload itemid integer not null primary key amount decimal 8 2 in TSDATA2 DB200001 The SQL command completed successfully db2inst1 mensa db2backup datamove gt db2 insert into itemload values 4000001 1 1 4000002 2 2 4000003 3 3 DB20000I The SQL command completed successfully db2inst1 mensa db2backup datamove gt db2 load from item del of del insert into itemload allow read access Agent Type Node SQL Code Result LOAD 000 00000000 Success LOAD 001 00000000 Success PARTITION 001 00000000 Success PRE_PARTITION 000 00000000 Success RESULTS 2 of 2 LOADs completed successfully Summary of Partitioning Agents Rows Read 3000000 Rows Rejected 0 Rows Partitioned 3000000 Summary of LOAD Agents Number of rows read 3000000 Number of rows skipped 0 Number of rows loaded 3000000 Number of rows rejected 0 Number of rows deleted 0 Number of rows committed 3000000 Chapter 6 Administering databases 319 320 When the load command is issued and the load is running we can access the same table with a read only operation from another terminal session Before the end of
463. rror log path to db2log2 ITSODB for the database ITSODB Example 2 3 db2 logs configuration db2 update db cfg for ITSODB using NEWLOGPATH db210g1 ITSODB db2 update db cfg for ITSODB using MIRRORLOGPATH db21log2 ITSODB We discuss the procedure of changing the log path in 3 4 1 Change the online log path on page 120 Note These changes will only take place after you deactivate and activate your database Temp space DB2 uses system temporary table spaces for many SQL operations such as JOIN and SORT The DB2 temporary table space TEMPSPACE1 is one of the three default table spaces SYSCATSPACE TEMPSPACE1 and USERSPACE1 that are created during database creation By default TEMPSPACE1 is placed in the database path For larger systems we recommend that your temporary table spaces are located on a separate file system and disk For example in our system we created the file system db2temp with mount point db2temp to store our temporary table spaces In a partitioned database environment the catalog node needs to contain all three default table spaces and the other database partitions need to each contain only TEMPSPACE1 and USERSPACE1 Example 2 4 shows how to create a system temporary table space on multiple nodes in the db2temp file system Example 2 4 Create temp table space in a different file system CREATE TEMPORARY TABLESPACE tempspace2 IN ibmtempgroup MANAGED BY SYSTEM USING db2temp db2inst1 NODE0000
464. rsion 8 2 to a Version 9 5 Unicode database Example 4 18 Converting a DB2 Version 8 non unicode database to Version 9 5 unicode The steps bellow create a DB in DB2 UDB V8 db2instl gemini gt export LANG en_US is088591 db2inst1l gemini gt db2 CREATE DATABASE itso ON database db2inst1 USING CODESET 1252 TERRITORY BR COLLATE USING SYSTEM DB20000I1 The CREATE DATABASE command completed successfully db2instl gemini gt db2 get db cfg for itso grep Database Database Configuration for Database itso Database configuration release level 0x0a00 Database release level 0x0a00 Database territory BR Database code page 1252 Database code set 1252 Database country region code 55 Database collating sequence UNIQUE Database page size 4096 Database is consistent YES Chapter 4 Migration and fix packs 191 192 db2instl gemini gt db2 tvf create_tables sql This script creates tables and inserts db2instl gemini gt db2level DB21085I Instance db2inst1 uses 32 bits with level identifier 03090106 some lines and DB2 code release SQL08028 Informational tokens are DB2 v8 1 3 136 s070720 MI00194 and FixPak upp Product is installed at opt IBM db2 V8 1 Here starts the steps to the non Unicode db2instl gemini gt cd temp db2inst1 gemini temp gt db2move ITSO export kkkkk DB2MOVE kkkkk Action EXPORT Start time Wed Feb 6 16 51 37 2008 Connecting to da
465. run later Any parameter can require a reactivation of the database Command line You can quickly and conveniently enter commands by using the command line processor to change the settings that were entered gt Use GET DATABASE CONFIGURATION FOR lt db_name gt to show current values gt Use UPDATE DATABASE CONFIGURATION FOR db_name USING lt parameter gt to change the current values gt Use RESET DATABASE CONFIGURATION FOR db_name to reset all database parameters to their default values Example 3 36 on page 146 shows examples of the database configuration update command Chapter 3 Post installation tasks 145 Example 3 36 Examples for the database configuration change db2 get db cfg for itsodb db2 update db cfg for itsodb using DBHEAP 1200 db2 get db cfg for itsodb show detail 3 6 4 DB2 registry and environment variables 146 All configuration settings in DB2 are stored as either environment variables or registry variables On UNIX based systems all environment variables such as DB2INSTANCE DB2NODE DB2PATH and DB2INSTPROF are set by using the export command and are usually in the file do2profile located in INSTHOME sallib Registry variables are set through the db2set command and require a DB2 restart If a registry variable requires a Boolean argument the values YES 1 and ON are all equivalent and the values NO 0 and OFF are also equivalent To set registry values for an instance level profile issue
466. ry that is specified by the database manager configuration parameter DIAGPATH Another instance level parameter DIAGLEVEL is used to specify which type of diagnostic errors will be recorded in the db2diag log These values are valid No diagnostic data captured Severe errors only All errors All errors and warnings All errors warnings and informational messages PON You might want to increase the value of this parameter to gather additional problem determination data to help resolve a problem The default value of DIAGLEVEL is 3 If you change it to 4 for any reason remember to change it back to 3 or a lower value after the problem is resolved or the required information has been captured Otherwise keeping DIAGLEVEL at a level of 4 will impact the system performance to a certain extent and the file system can fill up quickly As shown in Example 7 15 the system information is always recorded at the beginning of the db2diag log file Similar information is recorded while starting a instance Example 7 15 The beginning of the db2diag log 2008 02 14 10 18 46 776339 480 11E1283 LEVEL Event PID 32098 TID 47944161495904PROC db2set INSTANCE db2instl NODE 000 FUNCTION DB2 UDB RAS PD component pdLogInternal probe 120 START New Diagnostic Log file DATA 1 Build Level 152 bytes Instance db2instl uses 64 bits and DB2 code release SQL09050 with level identifier 03010107 Informational tokens are DB2 v9
467. s Now we demonstrate how to create a table space on a block device In Example 3 4 on page 100 we use the fdisk command to create new disk partition on an empty disk with the name sdb We then create one new extended disk partition called sdb1 After that we create a logical disk partition called sdb5 within the extended disk partition sdb1 Note under Linux extended disk partitions are containers that can contain several logical disk partitions Chapter 3 Post installation tasks 99 Example 3 4 Use fdisk to create a block device puget fdisk dev sdb Command m for help p Disk dev sdb 214 MB 214748160 bytes 64 heads 32 sectors track 204 cylinders Units cylinders of 2048 512 1048576 bytes Device Boot Start End Blocks Id System Command m for help n Command action e extended p primary partition 1 4 e Partition number 1 4 1 First cylinder 1 204 default 1 Using default value 1 Last cylinder or size or sizeM or sizeK 1 204 default 204 Using default value 204 Command m for help p Disk dev sdb 214 MB 214748160 bytes 64 heads 32 sectors track 204 cylinders Units cylinders of 2048 512 1048576 bytes Device Boot Start End Blocks Id System dev sdbl 1 204 208880 5 Extended Command m for help n Command action 1 logical 5 or over p primary partition 1 4 First cylinder 1 204 default 1 Using default value 1 Last cylinder or size or sizeM or sizeK 1 204 defaul
468. s Automatic storage automatically grows the size of your database across disk and file systems It eliminates the need to manage storage containers while taking advantage of the performance and flexibility of database managed space Starting with DB2 9 1 this feature is enabled by default DB2 9 5 provides further enhancements including free unused space at the end of a table space the ability to set the maximum size for automatic storage database containers and support for the multi partitioned environment gt Additional automatic configuration parameters There are more tuning parameters that the data server automatically handles without requiring you to stop and restart your instance or database gt Automated maintenance improvements You can use new DB2 stored procedures to configure and collect information about automated maintenance for the following areas Maintenance windows Automatic backups Automatic table and index reorganizations Automatic table RUNSTATS operations The DB2 stored procedures for collecting information are SYSPROC AUTOMAINT_GET_POLICY SYSPROC AUTOMAINT_GET_POLICYFILE To configure automated maintenance use SYSPROC AUTOMAINT_SET_POLICY SYSPROC AUTOMAINT_SET_POLICYFILE gt Trusted context A Trusted context is a database object that describes a trust relationship between the database and an external entity such as a middle tier application server Trusted context
469. s MySQL The PEAR project also provides many high quality components that are written in PHP and that are intended for reuse Tip You can learn more about PHP at IBM developerWorks Refer to the Recommended PHP reading list at http www ibm com devel operworks opensource 1library os php read PHP and DB2 There are four extensions that you can use to write PHP applications with DB2 All of the PHP interfaces ultimately communicate with DB2 using the call level interface CLI The interfaces are PHP extensions which are written in C and compiled with the DB2 libraries when you install PHP gt ibm_db2 provides the db2_ functions gt PDO_IBM provides the Product Delivery Option PDO object for CLI gt PDO_ODBC provides the PDO object for Open Database Connectivity ODBC gt Unified ODBC provides the odbc_ functions IBM recommends using ibm_db2 or PDO_IBM to get the best performance and features out of DB2 Which interface you choose is dependent on the type of application that you are writing and the version of PHP 4 or 5 Refer to chapter 4 of Developing PHP Applications for IBM Data Servers SG24 7218 to learn more about choosing and installing a PHP extension for DB2 Tip The Zend Core for IBM provides all of the DB2 interfaces for PHP in an easily installed and supported package http www zend com en products core for ibm Chapter 8 Application development 439 440 PHP and the Web server
470. s Rejected 0 Rows Partitioned 3000000 db2inst1 mensa db2backup datamove gt db2 select count from db2instl itemload 1 record s selected db2inst1 mensa db2backup datamove load gt 1s la total 27348 drwxr xr x 2 db2inst1 db2iadml 4096 2008 02 11 11 32 drwxr xr x 4 db2inst1 db2iadml 4096 2008 02 11 11 30 YWw r 1 db2instl db2iadml 27959550 2008 02 11 11 32 item del 000 db2inst1 mensa db2backup datamove gt db2_all ls la db2backup datamove load total 27348 drwxr xr x 2 db2instl db2iadml 4096 2008 02 11 11 32 drwxr xr x 4 db2instl db2iadml 4096 2008 02 11 11 30 Yw r 1 db2inst1 db2iadml 27959550 2008 02 11 11 32 item del 000 mensa 1s la db2backup datamove load completed ok Chapter 6 Administering databases 317 318 total 27332 drwxr xr x 2 db2instl db2iadml 4096 2008 02 11 11 36 drwxr xr x 4 db2instl db2iadml 4096 2008 02 11 11 35 Yw Yr 1 db2inst1 db2iadml 27946236 2008 02 11 11 36 item del 001 gemini 1s la db2backup datamove load completed ok db2inst1 mensa db2backup datamoved gt db2 load from item del of del replace into itemload copy yes to db2backup datamove copydata partitioned db config mode load_only part_file_location db2backup datamove load partitioning dbpartnums 0 1 Agent Type Node SQL Code Result LOAD 000 00000000 Success LOAD 001 00000000 Success RESULTS 2 of 2 LOADs completed successfully Summary of LOAD Agents Number of rows read 30
471. s and a field description of the output of db2mtrk refer to DB2 Linux UNIX and Windows Command Reference SC23 5846 01 7 3 db2top The db2top monitoring utility also known as IBM single system monitor view for DB2 monitors a DB2 environment on Linux platforms quickly and efficiently At the time of writing this book the db2top version is 2 0 and the information about db2top is available on the IBM AlphaWorks Web site http www alphaworks ibm com tech db2top You can download the zipped file for db2top db2top 2 0 bin zip from the following Web site http www alphaworks ibm com tech db2top download 7 3 1 db2top installation Use these steps to install db2top 386 1 Unzip db2top 2 0 bin zip The directory content of the unzipped file looks like 2007 06 06 2007 06 07 2007 07 19 2007 06 06 2007 06 06 Up and Running with DB2 on Linux 22 13 00 00 14 43 21 11 21 13 lt DIR gt lt DIR gt lt DIR gt 202 153 db2top User Manual pdf 2 995 973 db2top 2 0 bin tar gz license man samples The db2top User Manual pdf is the user manual and the db2top 2 0 bin tar gz contains executable files for all supported platforms 2 Read the license agreement HTML format in the icense directory Note This license agreement indicates that this program is still at the Early Release of Programs stage at the time of writing this book We recommend that you use db2top in an development environment only 3 If y
472. s and groups that are created are listed in Table 2 10 DB2 Setup also gives you an option to specify your own user and group names Response file Users can also be created during a response file installation if you specify that user and group information is in the response file Example 2 5 shows the entries in our response file to create the three required users and groups for DB2 Example 2 5 Using a response file to create users and groups Instance Creation Settings db2inst1 NAME db2instl db2inst1 UID 1001 db2inst1 GROUP_NAME db2iadml db2inst1 GID 999 db2inst1 HOME_ DIRECTORY db2home db2inst1l db2inst1 PASSWORD XXXXXXXXXX eee eee Fenced User Creation Settings Chapter 2 Installation 51 db2inst1 FENCED_ USERNAME db2fencl db2inst1 FENCED UID 1002 db2inst1 FENCED_GROUP_NAME db2fadml db2inst1 FENCED HOME_DIRECTORY db2home db2fenc1 db2inst1 FENCED_PASSWORD xxxxxxxxxx oe eee Administration Server Creation Settings DAS_USERNAME dasusrl DAS_UID 1003 DAS_GROUP_NAME dasadml DAS_GID 997 DAS_HOME_DIRECTORY home dasusrl DAS_PASSWORD XXXXXXXXXX oe eee Creating users and groups in the OS command line To use this method follow these steps 1 2 Log on as root Create groups for the instance owner the fenced user and the DAS user by using the following commands groupadd g 999 db2iadml groupadd g 998 db2fadml groupadd g 997 dasadml In our setup we u
473. s catalog and configure a large number of database manager configuration parameters This is the quickest installation method if you already have all the information that you need Unlike the DB2 Setup wizard the response file installation is not interactive and it takes slightly longer to prepare the response file However you only have to take that longer way one time and it can be used to install the same configuration on multiple machines Payload file deployment This method is an advanced installation method that is not recommended for most users It requires the user to physically install payload files A payload file is a compressed tarball that contains all of the files and metadata for an installable component Like db2_insta11 this installation method requires manual configuration after the product files are deployed Chapter 2 Installation 39 Note DB2 product installations are no longer operating system packages on Linux platforms You can no longer use the rpm command for installation 2 2 3 Storage planning 40 Both DB2 and data to be stored in the database require disk space DB2 uses both raw device and file systems It also requires log space In this section we discuss storage planning for DB2 data server File systems compared to raw devices The DB2 program the data to be stored in the databases and the DB2 logs need disk space This can be achieved with either raw devices or file systems In this se
474. s shown in Figure 8 8 on page 469 Up and Running with DB2 on Linux 0g Figure 8 8 Select Design Advisor from the Command Center The Design Advisor leads you through the process panel by panel At the Workload panel you can enter our test query select count from empmdc where expltest TEST After you click Next at the Recommendations panel the tool creates the suggestions for the provided workload Figure 8 9 on page 470 shows the recommendation to create an index Chapter 8 Application development 469 l Sig DOE vy EMPMDC row oria V Index Index IDX80205 15 gt Figure 8 9 Recommendations in the Design Advisor The Unused Objects page shows indexes that are not needed for the evaluated workload 8 5 3 Application development with the Data Studio Data Studio an Eclipse based tool offers the features that are provided by Eclipse such as 470 gt gt gt Context dependent help Context assist Software Configuration Management with all compatible systems Concurrent Versions System CVS Configuration Management Version Control CMVC Subversion SVN and so on Debugger For general information about Eclipse use the following Web site http www eclipse org Up and Running with DB2 on Linux The Data Studio is a replacement for the Development Center and offers functions and features beyond application development In regard to application development t
475. sa gt db2diag help db2diag The db2diag log Analysis Tool db2diag is a tool for filtering and formatting the db2diag log file Command syntax V gt gt db2diag Le I option filename Command parameters filename one or more space separated path names of diagnostic logs help h help information To get help on help try db2diag h h filter g case sensitive search for a list of field pattern pairs gi case insensitive search for a list of field pattern pairs gv case sensitive invert matching gvi gt giv case insensitive invert matching invert v invert the sense of matching for all filtering options exist record field must exist in order to be processed pid find all records for a list of process IDs tid find all records for a list of thread IDs eduid find all records for a list of EDU IDs node gt n find all records for a list of nodes error e find all records for a list of errors level 1 find all records for a list of severity levels history H display the history of logged records for a time interval time t display all the records within a particular time interval count C display a count of matching records verbose V display all record fields whether they contain data or not strict display records using one field value pair per line cbe display records in the Common Base Event CBE format fmt f
476. se ITSODB appshrh 128 0K Memory for application 5230 apph other 64 0K 192 0K Memory for application 5229 apph other 64 0K 192 0K Memory for application 5227 apph other 64 0K 576 0K Memory for application 5231 apph other 64 0K 320 0K In the next example as shown in Example 7 9 on page 385 the buffer pool size of IBMDEFAULTBP is changed from the default 1 000 8 K pages to 10 000 8 K pages dynamically You can monitor the change made by DB2 through db2mtrk very clearly The first db2mtrk d command can be used to obtain the buffer pool Up and Running with DB2 on Linux size for IBMDEFAULTBP before the change which is highlighted in bold font in our example the value of the bph 1 is 8 2 MB Then you can use the ALTER BUFFERPOOL command to dynamically change the size of the buffer pool IBMDEFAULTBP with the immediate parameter specified After you make that change the second db2mtrk d command shown in the example can be used to obtain the current buffer pool size for IBMDEFAULTBP It shows the size of the buffer pool is changed to 80 0 M highlighted in bold now Example 7 9 Using db2mirk to monitor database memory usage db2inst1 mensa db2home db2inst1 gt db2mtrk d Tracking Memory on 2008 02 12 at 14 28 38 Memory for database ITSODB utilh pckcacheh other catcacheh bph 1 bph S32K 64 0K 384 0K 192 0K 192 0K 8 2M 832 0K bph S16K bph S8K bph S4K shsorth lockh dbh 576 0K 448 0K
477. se that these records are spread evenly over 20 database partitions each partition only has to scan 5 000 000 records If each database partition server scans in parallel with the same speed the time required to do the scan is approximately 20 times faster than a single partition system handling the entire task Up and Running with DB2 on Linux The fact that databases are partitioned across several database partitions is transparent to the users and applications User interaction occurs through one database partition which is known as the coordinator node for that user Any database partition can be used as a coordinator node The database partition to which a client or application connects becomes the coordinator node You need to consider spreading out users across database partition servers to distribute the coordinator function Figure 1 7 shows you a partitioned database _ Coordinator Load Unload Queries Figure 1 7 DB2 MPP environment Figure 1 8 on page 22 shows you the relationship of the database objects in a partitioned environment Chapter 1 Introduction 21 22 System 1 System 2 Instance 1 Instance 2 Partition 1 Partition 2 Partition 3 logical partition logical partition physical partition Partition group 1 i Index 1 Table 1 Table space 1 Partition group 2 Table space 2 Index 3 Index 2
478. sed the numbers 997 998 and 999 Make sure that the numbers that you choose do not already exist on your machine by checking the etc group file Create a user that belongs to each group and specify the home directory useradd u 1001 g db2iadml m d db2home db2inst1 s bin ksh db2instl useradd u 1002 g db2fadml m d db2home db2fencl s bin ksh db2fencl useradd u 1003 g dasadml m d home dasusr1 s bin ksh dasusrl In our setup we used the numbers 1001 1002 and 1003 Make sure that the numbers that you choose do not already exist on your machine by checking the etc passwd file As root user set a password for each user that you created by entering the following commands passwd db2instl passwd db2fencl passwd dasusrl Creating users Multiple partition considerations In a partitioned database environment you only need to create one shared home directory for the instance owner and fenced user but remember to create users Up and Running with DB2 on Linux on each machine When creating users in a partitioned environment make sure that the user IDs and group IDs are the same on each machine In our setup we used gt A shared home directory db2home on the instance owning machine which is NFS mounted on the remaining machines in the cluster In this directory we have the home directories for the instance owning user and fenced user db2instl and db2fenc gt A local home directory for the DAS user on
479. ser defined types UDTs In general the load utility is faster than the import utility because it writes formatted pages directly into the database while the import utility performs SQL INSERTs The load utility does not fire triggers and does not perform referential checking or table constraint checking other than validating the uniqueness of the indexes The load process consists of four distinct phases gt Load During which the data is written to the table gt Build During which indexes are produced gt Delete During which the rows that caused a unique or primary key violation are removed from the table and stored in the load exception table if one was specified gt Index copy During which the index data is copied from a system temporary table space to the original table space This copy will only occur if a system Chapter 6 Administering databases 311 temporary table space was specified for index creation during a load operation with the READ ACCESS option specified To use the LOAD utility you must have SYSADM authority DBADM authority or LOAD authority on the database together with the needed privilege depending on the load mode that you choose For example for REPLACE mode you need INSERT and DELETE privilege on the table The load utility can be invoked through the command line processor CLP through the Load wizard in the Control Center by calling the ADMIN_CMD stored procedure or by using an applicati
480. sosj sanjose i db2inst1 db2inst1 db2insti itsosj sanjo No froot db2ese rsp Figure 2 14 Root installation Installation summary window Chapter 2 Installation 74 19 After installation read the status report tab and check for any errors If there are no errors click Finish Note Install logs are located in tmp db2setup log and tmp db2setup err Response file install For root installation you also can use a response file to install DB2 as discussed in Response file install on page 63 The response file can be generated by DB2 Setup wizard or by editing the samples that are provided by DB2 Creating a response file using the sample response file You can create the response file manually by editing the templates that are provided The response files have a rsp extension and are located in the mnt dvd db2 linux samples or mnt dvd db2 inuxamd64 samples directory on the DB2 product DVD In the directory name mni dvd represents the mount point of the CD or DVD For example you can find a sample response file for DB2 Enterprise Server Edition in the mnt dvd db2 inuxamd64 samples directory that is named db2ese rsp To create your own response file from the sample you must copy the sample response file to a local file system and edit it Activate items in the response file by removing the asterisk to the left of the keyword and then overwrite the default setting with the new setting The range of possible sett
481. space the table space itself is not available for use until the operation completes but users are not prevented from accessing tables in other table spaces Full or Incremental backup A full backup is a image copy of the entire database Figure 6 1 In a partitioned environment each database partition backup is written in a separate output file Sunday Mon Tue Wed Thu Fri Sat Sunday tele Figure 6 1 Full backup An incremental backup takes an image copy of changed data since the most recent successful full backup This is a cumulative backup as shown in Figure 6 2 on page 230 The TRACKMOD parameter Track modified pages in the database configuration must be set to ON Chapter 6 Administering databases 229 Sunday Mon Tue Wed Thu Fri Sat Sunday Full Full TOEL Figure 6 2 Incremental backup A delta backup is fundamentally an incremental backup It creates a copy of all data pages that have changed since the last successful backup of any type The delta backup is also known as a non cumulative backup Figure 6 3 Sunday Mon Tue Wed Thu Fri Sat Sunday ms NASI NA NA NAI NASI Figure 6 3 Incremental delta backup The backup strategy depends on your environment The database workload availability and recovery level are all decision factors A good backup strategy might be a daily offline backup if the database does not have a 24x7 availability requirement Another strategy can
482. space depends on your system but we provide several general recommendations in Table 4 1 Table 4 1 Space recommendations for migration Table space Space recommendation System catalog space gt For SMS table spaces allocate 2x the SYSCATSPACE space currently occupied For DMS table spaces free pages must be equal to or greater than used pages Temporary table space The total pages for the system temporary TEMPSPACE1 by default table space must be twice the amount of total pages for the system catalog table space If you are upgrading from Version 8 check the row size in your result sets If it is close to the maximum row length limit for your existing system temporary table spaces you might need to create a system temporary table space with a larger page size This additional space is necessary because DB2 Version 9 1 and Version 9 5 use larger record identifiers RID that increase the row size in the result sets from queries or positioned updates To check the size of your DMS table spaces use the following commands as the instance owner db2 list database directory db2 connect to dbname db2 list tablespaces show detail To increase space in a DMS table space you can add additional containers or increase the size of your existing containers To increase space in an system managed storage SMS table space you can free sufficient disk space on the corresponding file systems or increase the size of your f
483. split the data into more table spaces and to create your own layout Here are the main reasons for doing that gt The caching of the data in the table spaces can be tuned by the related buffer pools Buffer pools are caching areas and are assigned to one or more table spaces Having different table spaces allows you to tune the caching areas separately for them You can separate rarely used tables from heavily used tables You can also tune the I O performance of a table space by putting the containers of one table space on different physical disks You can perform backup at the table space level Separate table spaces allow you to implement multiple backup strategies You can grant permission to create objects to users in table spaces which allows you to implement more granular security control At the table creation you can specify that table data will go into one table space index data into another table space and also long data into another table space We especially recommend that you put long data into a different table space because long data is not cached in the buffer pool and requires file system caching After you have defined the table spaces for a table you can change the table spaces only by recreating the table Storage usage of a table is limited within the table space If one table in a table space takes up the entire disk space of the table space tables in other table spaces are not affected Defining more tabl
484. stallation Manager Y IBM Data Studio Data Studio Core Features Ps SQL Routine Development Environment Disk Space Information English Total Available Space 916GB Total Download Size 357 1 MB Total Installation Size 439 0 MB 4 Figure 5 8 Summary of features to be installed 10 When the update process completes a message confirms the success of the process Click View Log File if you want to open the update log file or click Finish 5 2 2 Installing IBM Data Studio Administration Console You can install IBM Data Studio Administration Console DSAC using the following steps 1 2 Log in as root Enter the following command to start the DSAC installation program sh IBM_DSAC_V1 1 2_1 0 0 0 b199_Linux_x86_32_64 bin 3 On the Introduction panel click Next 4 On the license agreement panel read the license agreement and then select accept the terms in the license agreement and click Next On the Choose Install Directory panel Figure 5 9 on page 208 specify the directory where you want to install DSAC or accept the default setting Click Next Chapter 5 IBM Data Studio 207 IBM Data Studio Administration Console 1 1 2 Introduction Where Would You Like to Install License Agreement fopt IBM DataStudioAdministrationConsole AEE BE Restore Default Directory Choose yer Details up Notification gt Select Start Up Options gt Confi
485. stems This book provides both introductory and detailed information about installing configuring managing and monitoring DB2 ina Linux environment We describe the DB2 product family and features for Linux and we provide step by step instructions for a single as well as for a multiple partition DB2 system installation and configuration We discuss how to migrate single and multiple partition DB2 to DB2 Version 9 5 and discuss in detail DB2 database administration in a Linux environment procedures and tools for database backup and recovery online maintenance and system monitoring We cover DB2 integrated tools and their features and use We discuss aspects of DB2 application development in the Linux environment and provide general tips about building and running DB2 applications on Linux and the use of DB2 application development tools The team that wrote this book This book was produced by a team of specialists from around the world working at the International Technical Support Organization San Jose Center Whei Jen Chen is a Project Leader at the International Technical Support Organization San Jose Center She has extensive experience in database design and modeling DB2 system administration and application development Whei Jen is an IBM Certified Solutions Expert in Database Administration and Application Development as well as an IBM Certified IT Specialist Christian Hideaki Kondo is a DB2 Systems Support member in Brazi
486. sysibmadm snaptab_reorg TAB_NAME REORG_TYPE REORG_STATUS REORG_COMPLETION DBPARTITIONNUM ITEM RECLUSTER ONLINE ALLOW WRITE STARTED SUCCESS ITEM RECLUSTER ONLINE ALLOW WRITE STARTED SUCCESS 1 2 record s selected db2inst1 mensa gt db2 select substr tabname 1 10 as tab_name substr reorg_ type 1 30 as reorg_type reorg_status reorg_completion dbpartitionnum from sysibmadm snaptab_reorg TAB_NAME REORG_TYPE REORG_STATUS REORG_COMPLETION DBPARTITIONNUM ITEM RECLUSTER ONLINE ALLOW WRITE STARTED SUCCESS ITEM RECLUSTER ONLINE ALLOW WRITE COMPLETED SUCCESS 1 2 record s selected db2inst1 mensa gt db2 select substr tabname 1 10 as tab_name substr reorg type 1 30 as reorg_type reorg_status reorg_completion dbpartitionnum from sysibmadm snaptab_reorg TAB_NAME REORG_TYPE REORG_STATUS REORG_COMPLETION DBPARTITIONNUM ITEM RECLUSTER ONLINE ALLOW WRITE COMPLETED SUCCESS ITEM RECLUSTER ONLINE ALLOW WRITE COMPLETED SUCCESS 1 2 record s selected After both database partitions completed we stop our monitoring script Example 6 43 on page 298 is the output collected by the monitor program which was started prior to REORG TABLE The output contains table reorganization information such as Reorg Type Start Time Status Started Truncate or Completed and so forth This information can be useful to detect performance problems or to see if a REORG is still in progress on a specific database partition and how long it h
487. t A single partitioned database We guide you through the steps to create a simple database by using the Create Database Wizard We also provide you with the scripts to create a database from the command line gt A multiple partitioned database We provide you with the scripts and commands to set up a partitioned database with two physical partitions 3 3 1 Creating a single partitioned database When you create a database the following tasks are done for you gt Setting up all of the system catalog tables that are required by the database During the creation of a new database DB2 allocates three table spaces SYSCATSPACE USERSPACE1 and TEMPSPACE1 The table space SYSCATSPACE holds all system catalog tables These catalog tables are actually repositories that keep information and statistics about all objects within the database USERSPACE1 contains the user created tables their indexes and their long data A system temporary table space TEMPSPACE1 is required by DB2 to support activities such as sorting data joining tables and creating indexes If you do not specify them at the CREATE DATABASE command DB2 will choose defaults for them gt Allocating the database recovery log The DB2 recovery log tracks all of the changes made against your database It is also called the transaction log It is used with the recovery history file to recover data in case of a failure gt Creating the database configuration file and setting t
488. t choose Recommendation Advisor to disable the health indicator choose Disable Evaluation Figure 7 18 shows these options Figure 7 18 Choosing the options to handle an alert If you chose Show Details the following panel Figure 7 19 on page 371 appears 370 Up and Running with DB2 on Linux Figure 7 19 Detailed information for an alert within Health Center 5 Take the corresponding action to resolve current health alerts a Use the Recommendation Advisor utility i If you clicked Recommendation Advisor at the previous panel to get the recommendation for this alert the Recommendation Advisor utility will be launched See Figure 7 20 on page 372 The first panel is an introduction You can review health alert details here After reviewing the health alert details click Next Chapter 7 Monitoring and troubleshooting DB2 371 Recommendation Advisor Figure 7 20 Recommendation Advisor introduction ii On the Specify your database requirements panel Figure 7 21 specify your database requirement In our sample we choose I would like an immediate solution to the problem Click Next Figure 7 21 Specifying your database requirements iii On the Select a recommendation panel Figure 7 22 on page 373 select a recommendation from the Preferred recommendations list We choose Add new table space containers Click Next 372 Up and Running with DB2 on Linux Select a recommendation The follo
489. t db2 reorgchk update statistics on table db2instl item Doing RUNSTATS Table statistics Fl 100 OVERFLOW CARD lt 5 F2 100 Effective Space Utilization of Data Pages gt 70 F3 100 Required Pages Total Pages gt 80 SCHEMA NAME CARD OV NP FP ACTBLK TSIZE F1 F2 F3 REORG 1502010 0 3702 3702 30040200 0 100 100 Index statistics Chapter 6 Administering databases 301 F4 CLUSTERRATIO or normalized CLUSTERFACTOR gt 80 F5 100 Space used on leaf pages Space available on non empty leaf pages gt MIN 50 100 PCTFREE F6 100 PCTFREE Amount of space available in an index with one less level Amount of space required for all keys lt 100 F7 100 Number of pseudo deleted RIDs Total number of RIDs lt 20 F8 100 Number of pseudo empty leaf pages Total number of leaf pages lt 20 SCHEMA NAME INDCARD LEAF ELEAF LVLS NDEL KEYS LEAF_RECSIZE NLEAF_RECSIZE LEAF_PAGE_OVERHEAD NLEAF_PAGE OVERHEAD F4 F5 F6 F7 F8 REORG Table DB2INST1 ITEM Index DB2INST1 PK_ITEM_ITEMID 1502010 3128 0 3 0 1502010 4 4 1340 1340 100 91 12 0 0 Here you might discover that the File Pages FP for the table and Leaf Pages LEAF for the index have been lowered if the data was fragmented For table statistics you might discover that is reported which means that no REORG is required at present 6 Rebinding packages Rebinding is required to take advantage of the new statistics
490. t 204 Using default value 204 Command m for help p Disk dev sdb 214 MB 214748160 bytes 64 heads 32 sectors track 204 cylinders Units cylinders of 2048 512 1048576 bytes Device Boot Start End Blocks Id System 100 Up and Running with DB2 on Linux dev sdbl 1 204 208880 5 Extended dev sdb5 1 204 208864 83 Linux Command m for help w The partition table has been altered Calling ioctl to re read partition table Syncing disks The instance owner must have the write access to the device file for the disk partition The instance owner can get write access to the device file for the disk partition by executing the following command from the root user chown lt instance user gt lt instance group gt dev sdb5 Now we can use this disk partition for the table space First we need to calculate the size which we have to specify at the CREATE TABLE SPACE command by using this formula num_pages floor blocks 1024 4096 In our example num_pages floor 208864 1024 4096 52216 This number can now be used to create the table space CREATE TABLE SPACE dms1 MANAGED BY DATABASE USING DEVICE dev sdb5 52216 Example 3 5 shows the result Example 3 5 List table space container for a raw device db2instl puget gt db2 list tablespace containers for 3 show detail Table Space Containers for Table Space 3 Container ID 0 Name dev sdb5 Type Disk Total pages 52216 Useable
491. t are laid out within a perspective When you close the Welcome panel a perspective that has information from the workspace is presented Refer to Figure 5 13 on page 212 Chapter 5 IBM Data Studio 211 m 22 Data NewFile xmi IBM Data Studio Developer File Edit Source Navigate Search Project Data Bun XML Window Help noi malta B 9 a B woo B Ale s Data Eacvs Repair 85 Data Project Explorer 3 A Gi Statementt sql A B outline 38 sae a veq Ee 22 xml version 1 0 encoding UTF 8 22xml J f DataProject SAMPLE jdbe db2 localhost 50001 SAMPLE Y LE Products Y E products b CSAL Scripts Y E product Y E product xmins http posample org C Stored Procedures xmins http posample org YV E description 10 C User Defined Functions pid E name C3 Web Services e description E price v OOXML E name Fleece jacket Y E product xmins http posample org Sweor si os gt C XML Documents E product b C XML Schema xmins http posample org W xsit pid O description Nylon pants ET nT aD e ylon pal 9 9 34 Database Explorer 53 Design Source BS Oo a amp gt Connections m Properties Al Tasks X Problems Error Log Model Report Data Output Bookmarks ITSODB DB2 Alias a MENSA DB2 Alias yd SAMPLE DB2 for Linux UNIX and Windows V9 L eee Ma AML documant v 0 SAMPLE v 0 Buffer Pools
492. t interact with the operating system such as creating table spaces In the db2diag log file you see information about wrong path names permission problems error codes and so on The level of detail that is logged in db2diag log is specified in the DIAGLEVEL DBM configuration parameter and ranges from 0 to 4 The default is 3 The higher the number is the more information is logged Setting it to 4 can have a performance impact on the database You need to maintain the db2dump directory as the db2diag log file keeps growing and other dump files can be added to the directory by DB2 which means that you have to purge old files and roll over files or compress them You need to consider relocating this directory to a separate file system so that it will not impact the instance if it fills up Example 3 25 shows how to change the location for db2diag log Example 3 25 Relocate db2diag log db2inst1l puget gt db2 get dbm config grep DIAGPATH Diagnostic data directory path DIAGPATH home db2inst1 sq11ib db2dump db2inst1l puget gt db2 update dbm config using DIAGPATH db2diag DB20000I1 The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully db2inst1l puget gt db2 get dbm config grep DIAGPATH Diagnostic data directory path DIAGPATH db2diag Chapter 3 Post installation tasks 123 Note This is a configuration change at the instance level You only need to perform it one time for the whole instance Th
493. t size Maximum size hard limit Largest size high water mark Type identifier indicating the function for which the memory will be used Agent who allocated pool only if the pool is private Application vvvvvy You can obtain a detailed help message for this tool by entering the following command in a Linux terminal db2mtrk h Example 7 8 shows you how to use db2mirk to monitor memory usage by DB2 instances databases and applications Example 7 8 Using db2mirk to monitor DB2 memory usage db2inst1 mensa db2home db2inst1 gt db2mtrk i d a Tracking Memory on 2008 02 12 at 14 19 24 Memory for instance other monh fcmbp 32 1M 192 0K 10 9M No active databases No active applications db2instl mensa db2home db2inst1 gt db2 connect to itsodb Database Connection Information DB2 LINUXX8664 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias Chapter 7 Monitoring and troubleshooting DB2 383 384 db2inst1 mensa db2home db2inst1 gt db2mtrk i d a Tracking Memory on 2008 02 12 at 14 20 38 Memory for instance other monh fcmbp 32 1M 320 0K 10 9M Memory for database ITSODB utilh pckcacheh other catcacheh bph 1 bph S32K 64 0K 192 0K 192 0K 192 0K 8 2M 832 0K bph S16K bph S8K bph S4K shsorth lockh dbh 576 0K 448 0K 384 0K 0 640 0K 18 8M apph 5231 apph 5230 apph 5229 apph 5227 appshrh 64 0K 64 0K 64 0K 64 0K 128 0K Application Memory for databa
494. t the Actions tab Inthe Actions tab Figure 7 24 on page 375 select the Enable actions check box to enable running the actions automatically and then click Add Up and Running with DB2 on Linux Configure Health Indicator able Space Utilization ts ts_util cga REMOVE KEMPER Figure 7 24 Enable actions in Configure Health Indicator panel On the pop up panel as shown in Figure 7 25 on page 376 select the condition on which to run the action In our sample we choose Alarm the threshold breach On the Script tab choose the system name a predefined script name and the type of script Chapter 7 Monitoring and troubleshooting DB2 375 Add Script Action dlo2home db2inst1 script alt tbsp db2 DB2 command script o Figure 7 25 Add script action d On the Run properties tab as shown in Figure 7 26 on page 377 enter the runtime authorization user ID and the password 376 Up and Running with DB2 on Linux Add Script Action Figure 7 26 Runtime authorization e On the Command tab review the content of the predefined script and specify the script statement termination character and working directory Click OK Chapter 7 Monitoring and troubleshooting DB2 377 378 Add Script Action ALTER TABLESPACE tbspdms_O EXTEND FILE database db2inst1 NODEO fdb2home db2inst1 script OK Cancel Help Figure 7 27 Review the content of the predefined script Example 7 5 shows the con
495. t the new settings db2instl mensa gt db2 CALL AUTOMAINT_SET_POLICYFILE MAINTENANCE _WINDOW window xm Hy Return Status 0 You can also use these procedures to configure automatic backup reorg and runstats by replacing MAINTENANCE_WINDOW in the commands in Example 6 20 on page 253 with one of gt AUTO_BACKUP gt AUTO_REORG gt AUTO_RUNSTATS There are four sample policy files one for each type shipped with DB2 under the directory HOME sqllib samples automaintcfg Note For more information refer to the topic Configuring an automated maintenance policy using SYSPROC AUTOMAINT_SET_POLICY or SYSPROC AUTOMAINT_SET_POLICYFILE in Data Recovery and High Availability Guide and Reference SC23 5848 00 6 1 5 DB2 database recovery 254 Database recovery means rebuilding a database or table space after a problem such as media or storage failure or to rebuild the database on another system There are three types of recovery gt Crash recovery protects a database from being left in an inconsistent or unusable state when transactions also called units of work are interrupted unexpectedly gt Version recovery is the restoration of a previous version of the database using an image that was created during a backup operation gt Rollforward recovery can be used to reapply changes that were made by transactions that were committed after a backup was made Up and Running with DB2 on Linux Crash rec
496. t3 Package cache Bufferpool f Locklist Sort area DATABASE_MEMORY INSTANCE_MEMORY INSTANCE_MEMORY N Database 2 DS F Database 1 Database 4 Database 6 Figure 3 19 STMM For newly created databases the self tuning feature is turned on by default You can see that from the database configuration parameters that are shown in Example 3 34 Example 3 34 Parameters turned on for STMM db2inst2 puget gt db2 get db config for itsodb grep i automatic Size of database shared memory 4KB DATABASE MEMORY AUTOMATIC Max storage for lock list 4KB LOCKLIST AUTOMATIC Percent of lock lists per application MAXLOCKS AUTOMATIC Package cache size 4KB PCKCACHESZ AUTOMATIC Sort heap thres for shared sorts 4KB SHEAPTHRES SHR AUTOMATIC Sort list heap 4KB SORTHEAP AUTOMATIC Database heap 4KB DBHEAP AUTOMATIC SQL statement heap 4KB STMTHEAP AUTOMATIC Default application heap 4KB APPLHEAPSZ AUTOMATIC Application Memory Size 4KB APPL_MEMORY AUTOMATIC Statistics heap size 4KB STAT_HEAP_SZ AUTOMATIC Number of asynchronous page cleaners NUM _IOCLEANERS AUTOMATIC Number of I 0 servers NUM_IOSERVERS AUTOMATIC Default prefetch size pages DFT_PREFETCH SZ AUTOMATIC 134 Up and Running with DB2 on Linux Max nu
497. ta before loading the new data there is no pre existing data to query until after the load operation is complete Up and Running with DB2 on Linux For a partitioned database the message files will not be displayed to the console or retained for the load operations that are initiated from the CLP To save or view the contents of these files after a partitioned database load has completed you must specify the MESSAGES option of the LOAD command We recommend that you use a fully qualified file name for the MESSAGES file such as db2backup datamove myload msg If you use the MESSAGES option after the load operation has completed the message files on each database partition are transferred to the client machine and stored in files with the base name that is indicated by the MESSAGES option For partitioned database load operations Table 6 1 lists the name of the file corresponding to the load process type that produced it Table 6 1 Message file types that are generated by the partitioned LOAD operation Load Agent lt message file name gt load lt partitionnumber gt Partitioning Agent lt message file name gt part lt partitionnumber gt Pre partitioning Agent lt message file name gt prep lt partitionnumber gt Note We strongly recommend that you use the MESSAGES option for partitioned database load operations that are initiated from the CLP Monitoring the LOAD utility You can use the LOAD QUERY command to check the status
498. tabase ITSO successful Binding package automatically Bind file home db2inst1 sqllib bnd db2move Bind was successful EXPORT 2 rows from table DB2INST1 RA EXPORT 2 rows from table DB2INST1 a EXPORT 2 rows from table DB2INST1 E Disconnecting from database successful End time Wed Feb 6 16 51 38 2008 to Unicode conversion Server DB2 Common Server V8 2 8 bnd LOCATION BRAND CUSTOMER db2inst1 gemini temp gt db2look d itso e o unidb ddl 1 x f No userid was specified db2look tries to USER is DB2INST1 Creating DDL for table s Output is sent to file unidb ddl Binding package automatically Bind is successful Binding package automatically Bind is successful db2inst1 gemini temp gt vi unidb dd Up and Running with DB2 on Linux use Environment variable USER gt This point we did the step 4 lt db2instl gemini temp gt db2 terminate DB200001 The TERMINATE command completed successfully db2inst1 gemini temp gt db2 drop db itso DB20000I The DROP DATABASE command completed successfully db2instl gemini temp gt db2stop 02 06 2008 16 55 00 0 0 SQL1064N DB2STOP processing was successful SQL1064N DB2STOP processing was successful gemini opt ibm db2 V9 5 instance db2imigr db2instl System Database Directory is empty No database has been processed DBI10701 Program db2imigr completed successfully db2instl gemini
499. tamp Database name Database path Input database alias Number of accessed tables Table List Table Schema DB2INST1 Table Name ITEM Table Type User Data Object Pages 3697 Index Object Pages 3101 Rows Read Not Collected Rows Written 8251179 Overflows 0 Page Reorgs 8921 Table Reorg Information Node number 0 Reorg Type Reclustering Inplace Table Reorg Allow Write Access Reorg Index Reorg Tablespace 7 Start Time Reorg Phase Max Phase z Phase Start Time Status Truncate Current Counter 1850 Max Counter 3696 MaxCount Start End PhaseStart Status Completion 02 13 2008 14 35 11 n a n a Started 0 02 13 2008 09 32 59 904159 02 13 2008 14 36 33 595307 ITSODB database db2inst1 NODE0000 SQL00002 ITSODB 21 02 13 2008 14 35 11 064496 Chapter 6 Administering databases 299 Completion 0 End Time Database Partition 0 Database ITSODB Active Up 0 days 05 03 34 Table Reorg Information Address TbspaceID TableID PartID MasterTbs MasterTab TableName Type IndexID TempSpaceID 0x00002B6A7E8F1B28 7 4 n a n a n a ITEM Online 1 7 Table Reorg Stats Address TableName Start End PhaseStart MaxPhase Phase CurCount MaxCount Status Completion 0x00002B6A7E8F1B28 ITEM 02 13 2008 14 35 11 n a n a n a n a 1850 3696 Truncat 0 Table Snapshot First database connect timestamp 02 13 2008 09 32 59 904159 Last reset timestamp Snapshot timestamp
500. tderr CLI error d in SQLExecDirect n cliRC exit cliRC bind columns to variables if cliRC SQLBindCol hstmt 1 SQL_C_CHAR empno val sizeof empno val amp empno ind SQL_SUCCESS fprintf stderr CLI error d in SQLBindCol 1 n cliRC exit cliRC fetch each row and display if cliRC SQLFetch hstmt SQL SUCCESS fprintf stderr CLI error d in SQLFetch n cliRC exit cliRC while cliRC SQL_NO DATA FOUND bind columns to variables if cliRC SQLGetData hstmt 1 SQL_C_CHAR empno val sizeof empno val amp empno ind SQL_SUCCESS fprintf stderr CLI error d in SQLGetData 1 n cliRC exit cliRC Up and Running with DB2 on Linux printf 6 6s n empno val if cliRC SQLFetch hstmt SQL_SUCCESS if cliRC SQL_NO DATA FOUND fprintf stderr CLI error d in SQLFetch n cliRC exit cliRC Free statement handle if cliRC SQLFreeHandle SQL_HANDLE STMT hstmt SQL_SUCCESS fprintf stderr CLI error d in SQLFreeHandle n cliRC exit cliRC disconnect from the database if cliRC SQLDisconnect hdbc SQL_SUCCESS fprintf stderr CLI error d in SQLConnect n cliRC exit cliRC 3 Free database handle if cliRC SQLFreeHandle SQL_HANDLE DBC hdbc SQL SUCCESS fprintf stderr CLI error d in SQLFreeHandle n cliRC exit cliRC Free environment handle if cliR
501. te If you use X Window System software you might need to set the DISPLAY variable for non root user to starting a Java based graphical tool You can get the DISPLAY variable setting from root user For example as root enter the following command echo DISPLAY 127 0 0 1 1 0 This command shows that the DISPLAY variable for root user is 127 0 0 1 1 0 You need to run the xhost command to allow clients access at first For example as root enter the following command xhost 127 0 0 1 Then as the non root user enter the following command export DISPLAY 127 0 0 1 1 0 6 You can use db2setup i lt language gt to run the DB2 Setup wizard in another language 60 Up and Running with DB2 on Linux 3 Select Install New On the Welcome to the DB2 Setup wizard window click Next 4 On the Software License Agreement window read the license agreement then select Accept and click Next 5 Select the installation type as shown in Figure 2 1 on page 61 You can choose either a Typical Compact or Custom installation Typical installs most DB2 components except for the Base application development tools Click View Features to see what components will get installed Compact installs only the basic DB2 features and functionality Custom allows you install whatever components you want An advantage of the Custom option is that it allows you to install the Base application development tools with DB2 With the Ty
502. te a unix script that will capture db2top data either from an active database or from a collection file Then copy all generate csv files and this macro in a windows directory Then press Build graphics button to generate graphics Figure 7 33 db2top Reports tool Follow these steps to create graphical reports 1 Generate a UNIX script to capture db2top data This is an one time task db2top Reports uses a specific file format You are required to use the script to produce the data files Click Generate on the db2top Results tool panel Example 7 10 shows the generated script Example 7 10 db2top txt This script generates data for the db2top Excel macro It will create a directory called tmp background Copy this directory under Windows Copy the db2top Excel macro in the directory Open the Excel document and run full report SR SR SR OS OSE ORO SHER export WAITTIME 1 5 in minutes 392 Up and Running with DB2 on Linux export COLLECTFILE 2 in case there is a collection file export DIR tmp background Run db2top and exit after WAITTIME minutes BACK_GROUND db2top m WAITTIME b 1 o DIR db2top 2 csv amp db2top f COLLECTFILE m WAITTIME b 1 o DIR db2top 2 csv amp Start here rm fR DIR mkdir p DIR echo Running db2top for WAITTIME minute s BACK_GROUND d DBM BACK_GROUND 1 APPL BACK_GROUND t TBS BACK_GROUND b BP BACK_GROU
503. tect sensitive data such as credit card information you can use the built in functions ENCRYPT DECRYPT_BIN and DECRYPT_CHAR Encryption allows you to protect sensitive data from access by even the database administrator Defaults When a database is initially created the following permissions are granted to PUBLIC CREATETAB BINDADD CONNECT IMPLSCHEMA BIND on all packages created in the NULLID schema EXECUTE on all packages created in the NULLID schema CREATEIN on schema SQLJ CREATEIN on schema NULLID USE on table space USERSPACE1 SELECT access to the SYSIBM catalog tables SELECT access to the SYSCAT catalog views SELECT access to the SYSSTAT catalog views UPDATE access to the SYSSTAT catalog views EXECUTE with GRANT on all procedures in schema SQLJ EXECUTE with GRANT on all functions and procedures in schema SYSPROC vvvvvvvvvvvvv vy yv If you do not want these permissions you can specify the option RESTRICTIVE on the CREATE DATABASE command 3 8 Client configuration 152 In this section we discuss how to install and configure DB2 clients using the graphical tool Configuration Assistant or the DB2 command line processor DB2 clients provide access to the DB2 database server In DB2 Version 9 5 there are three types of DB2 data server clients available gt IBM Data Server Client This is a full installation client It includes all of the components as well as graphical and non graphical tools for admin
504. tegration and Content Management gt Gateway to mainframe and host data Up and Running with DB2 on Linux gt Retail financial public sector and manufacturing applications gt Life sciences and bio informatics solutions gt Store for spatial and geographical systems gt High Performance Computing applications including Financial modeling Oil and gas exploration Research and scientific Despite implementing a wide array of solutions in different industries clients of DB2 for Linux generally talk about a few common themes regarding the benefits that they derive Foremost among them is the exceptional value that DB2 for Linux delivers DB2 is renowned for critical self tuning and self healing features The Self tuning Memory Manager STMM automatic storage and other autonomic maintenance features make DB2 easy to use and maintain while spending less time managing it IBM alliances with all the major Linux distributors and the ability to get 24x7 support for both DB2 and Linux directly from IBM provide added peace of mind DB2 Version 9 5 extends its innovative abilities as a hybrid data server and cost savings of deep compression to enable the rapid use of data staying ahead of threats and extracting the full value of Extensible Markup Language XML data in operational processes The following sections provide an overview of DB2 features and product offerings available on Linux as well as the architectures for de
505. tent of the predefined script in our sample The action is triggered by the alarm condition of the health indicator ts ts_util for table space tbspdms_0 Example 7 5 Extend table space container size ALTER TABLESPACE tbspdms_0 EXTEND FILE database db2inst1 NODE000 N I1TSODB T0000008 C0000000 LRG 10M On the Configuring health indicator panel Figure 7 24 on page 375 click OK to finish enabling actions As shown in Example 7 6 you can use the DB2 CLP command GET ALERT CFG to verify the current setting Example 7 6 Using GET ALERT CFG to check the current health indicator setting db2inst1 mensa db2home db2inst1 gt db2 get alert cfg for tablespace tbspdms_0 on itsodb Up and Running with DB2 on Linux Alert Configuration Indicator Name ts ts_util Default No Type Threshold based Warning 80 Alarm 90 Unit Sensitivity 0 Formula ts ts_used_pages ts ts usable pages 100 Actions Enabled Threshold or State checking Enabled Script pathname db2home db2inst1 script alt_tbsp db2 Condition Alarm Script type DB2 System MENSA Working directory Termination character Userid db2home db2inst1 script db2instl eee eee If we set up the action plan from the beginning this script will be executed when we have populated the data and when the alarm for the table space is triggered The follow up corrective action is executed automatically without user intervention As shown
506. ter in the database manager configuration db2inst1l puget gt db2 get dbm config grep AUTHENTICATION Database manager authentication AUTHENTICATION SERVER Security on the database level On the database level you can control data access using the authorities and privileges that DB2 provides The data access can be controlled even in the row and column The security mechanism offered by DB2 includes gt gt gt Authorities for the administrators Views for restricting access to a subset of the data Privileges to restrict access to the DB2 objects Packages to restrict access to certain functions UDFs and stored procedures to restrict access to certain functions Roles that offer a more detailed way to implement security roles than the methods that are offered by the Linux groups Encryption to even protect data from access by the DBA Label based access control LBAC to restrict the access by users to data to the column and the row level Trusted context to address the typical problems introduced in a multiple tier architecture Privileges On the database level privileges can be granted on the following object types vvvvvvy Schemas Table spaces Tables and views Packages Indexes Sequences Routines Privileges can be granted to vvvy Linux users Linux groups DB2 roles PUBLIC To grant privileges use the GRANT statement Chapter 3 Post installation tasks 151 Encryption If you need to pro
507. the data residing on the current database partition as shown in Example 6 47 on page 304 Chapter 6 Administering databases 303 304 Example 6 47 Export data for current database partition from table ITEM db2inst1 mensa db2backup datamove gt db2 export to itempart0 del of del messages exppart0 msg select from item where dbpartitionnum itemid current dbpartitionnum Number of rows exported 1500364 We specified a messages file called exppartO msg The export utility writes error warning and informational messages into this file For all interfaces except the CLP you must specify the name of the messages file in advance with the MESSAGES parameter If you want to export data in parallel across multiple database partitions you can use the db2_a11 tool Export table data using the Control Center You can also use the DB2 Control Center to invoke EXPORT on a Linux platform Expand the object tree in the Control Center until you find the Tables or the Views folder Any existing tables or views are displayed in the contents pane on the right side of the panel Right click the table or view that you want and a menu listing all of the activities for the table or view shows Refer to Figure 6 29 on page 305 Up and Running with DB2 on Linux Control Center 22 Control Center 4 O All Systems All Databases itsops a 5 Views Aliases E Nicknames Cache Objects Triggers Schemas G Indexes Table S
508. the db2pd command without any option db2pd starts in interactive mode and then you can enter options You also can run db2pd with the option directly Example 7 19 shows both methods Example 7 19 The db2pd command prompt db2inst1 mensa db2home db2inst1 gt db2pd db2pd gt You are running db2pd in interactive mode db2pd gt If you want command line mode rerun db2pd with valid options db2pd gt Type h or help for help db2pd gt Type q to quit db2pd gt memsets Database Partition 0 Active Up 0 days 23 19 41 Memory Sets Name Address Id Size Kb Key DBP Type Unrsv Kb Used Kb Cmt Kb Uncmt Kb Chapter 7 Monitoring and troubleshooting DB2 405 406 DBMS 0x0000000200000000 412352519 29568 OxF197AE61 0 1280 7360 8000 21568 FMP 0x0000000210000000 412385288 22592 0x0 2 0 320 22592 0 Trace 0x0000000000000000 412319750 39227 OxF197AE74 1 0 39227 39227 0 FCM 0x0000000220000000 412418057 238592 OxF197AE62 11 204032 34560 34560 204032 db2pd gt q db2inst1 mensa db2home db2inst1 gt db2pd osinfo Operating System Information OSName Linux NodeName mensa Version 2 Release 6 Machine x86 64 CPU Information Total CPU OnlineCPU ConfigCPU Speed MHz HMTDegree 2 2 2 600 1 2 Physical Memory and Swap Megabytes TotalMem FreeMem AvailMem TotalSwap FreeSwap 3753 209 n a 8198 8192 Virtual Memory Megabytes Total Reserved Available Free 11951 n a n a 8401 Message Queue Information MsgSeg Msg
509. the load operation the SELECT statement returns the answer set quickly But at the last stage of the load operation until the job is finished the SELECT statement cannot succeed due to resource contention with the load operation At this time the load utility has to acquire an exclusive lock Z lock on the table before the data is committed After the load operation is finished the newly loaded data is visible to other applications Example 6 56 shows the SELECT output while LOAD is running and then after the data is committed Example 6 56 Concurrent access to the table where load is taking place LOAD is running we can access the data db2inst1 mensa db2backup datamove gt db2 select from itemload head 10 ITEMID AMOUNT 4000001 1 10 4000002 2 20 4000003 3 30 3 record s selected after the LOAD finished and committed the data db2inst1 mensa db2backup datamove gt db2 select from itemload head 10 ITEMID AMOUNT 5 954 25 7 534 75 10 417 87 11 313 62 14 419 25 15 679 75 16 347 25 The LOCK WITH FORCE option can be used to force off conflicting applications with the load operation in order to allow the load operation to proceed without waiting The forced application will receive an error SQL1224N The ALLOW READ ACCESS option is not supported if the REPLACE option is specified otherwise error code SQL3340N with reason code 1 will be returned Because a load replace operation deletes the existing table da
510. the server and the client accept communication to S 390 systems On Linux TCP IP is the only supported protocol for client server communications gt DB2INSTANCE set by the DB2 profile After you have enabled your user for DB2 by executing the db2profile script this environment variable is set to the name of the current instance Note Details of all of the registry variables are described in the Information Center at http publib boulder ibm com infocenter db21 uw v9r5 index jsp topic com ib m db2 1luw admin regvars doc doc c0007340 html db2set on the command line db2set is the command to set the registry variables You can execute the command by using the command prompt Example 3 37 Example 3 37 Setting and deleting a registry variable db2instl puget gt db2set db2instl puget gt db2set DB2COMM tcpip db2instl puget gt db2set DB2COMM tcpip db2instl puget gt db2set DB2COMM db2instl puget gt db2ca graphical tool To start the graphical tool issue the command db2ca amp In the main window select Configure DB2 Registry as shown in Figure 3 27 on page 148 Chapter 3 Post installation tasks 147 Pee G5 Configuration Assistant Tela jhomejdb2inst4 Indirect Figure 3 27 Change registry from db2ca You will get to the panel that is shown in Figure 3 28 where you can change the registry variables m ES DB2 Registry DB2ADMINSERVER dasusr1 DB2SYSTEM vmsuse Instanc
511. ther partition of the same database Up and Running with DB2 on Linux Installation in this chapter we guide you through the process of installing DB2 on Linux systems We describe both single and multiple partition environments and provide instructions for three installation methods DB2 Setup db2_install and response file installation In this chapter we describe the following topics Basic requirements Installation considerations and planning Multi partition installation considerations User and group setup Installing DB2 vvvvy Copyright IBM Corp 2008 All rights reserved 25 2 1 Basic requirements Prior to installing DB2 it is important that you have the required hardware and software You might be required to configure communications and install additional software packages in order for DB2 to run successfully In this section we cover the following installation prerequisites Hardware supported by DB2 Linux distributions supported by DB2 Required disk space Memory requirements Communication requirements Kernel parameter values Additional software requirements vvvvvvy 2 1 1 Hardware supported by DB2 DB2 products are supported on the following hardware gt x86 Intel Pentium Intel Xeon and AMD 32 bit Intel and AMD processors gt x64 64 bit AMD64 and Intel EM64T processors gt POWER IBM OpenPower System i or System p systems that support Linux gt System z or System z9 2 1 2
512. tically able to execute any query The availability of this warehouse can be lower than the database from the production system The data model can be normalized at the same level as the production system or can already be slightly denormalized It depends on the needs Data marts are highly specialized data warehouses They are designed to run a well defined set of reports The data is mostly denormalized and transformed into a CUBE or into star schemas Cubes and star schemas are data models designed to support the queries running on these systems You have ETL Export Transform Load processes to transfer the data from the production system to the data marts on a regular basis by tools such as WebSphere DataStage or WebSphere QualityStage The availability of a data mart is usually lower than for the production systems 1 3 2 DB2 database objects 14 In this section we introduce DB2 objects and their relationships to each other Instances An instance sometimes called a database manager is DB2 code that manages data It controls what can be done to the data and manages system resources assigned to it Each instance is a complete environment It contains all the database partitions defined for a given parallel database system An instance has its own databases which other instances cannot access directly and all its database partitions share the same system directories It also has separate security from other instances on the same m
513. tics current and reorganizing tables and indexes as necessary It can be time consuming to determine whether and when to run maintenance activities and automatic maintenance removes the burden from you You can manage the enablement of the automatic maintenance features simply and flexibly by using the automatic maintenance database configuration parameters The default values for a DB2 Version 9 5 database are shown in Example 6 33 Example 6 33 Automatic maintenance database configuration parameters db2instl mensa gt db2 get db cfg for itsodb grep Automatic Automatic maintenance AUTO_MAINT ON Automatic database backup AUTO_DB BACKUP OFF Automatic table maintenance AUTO_TBL_MAINT ON Automatic runstats AUTO_RUNSTATS ON Automatic statement statistics AUTO _STMT_STATS OFF Automatic statistics profiling AUTO_STATS_PROF OFF Automatic profile updates AUTO_PROF_UPD OFF Automatic reorganization AUTO_REORG OFF The hierarchy of the parameters allows you to turn all automatic maintenance on or off without affecting the respective activity settings For instance if the AUTO_TBL_MAINT parameter is set to OFF the parameter AUTO_RUNSTATS is not of interest Enable automatic table maintenance Automatic table maintenance can be enabled by using the command line or the Configure Automatic Maintenance wizard To use the command line you have to set each of the following configuration parameters to ON AUTO_M
514. tion and data movement via utilities such as EXPORT IMPORT LOAD and so on We discuss these topics gt Database backup and recovery Considerations for choosing database and table space recovery methods How to enable the automatic backup feature Basic usage of the utilities BACKUP RESTORE and ROLLFORWARD gt Table and index reorganization and statistics collection Automatic table maintenance feature Table reorganization Statistic collection Package rebinding gt Data movement using EXPORT IMPORT and LOAD gt Job scheduling using the Task Center Copyright IBM Corp 2008 All rights reserved 227 6 1 DB2 database backup and recovery 228 A database can become unusable or corrupted in certain situations such as hardware failure power interruption or application mistakes To protect your database from losing any of your data it is important to have a good recovery strategy A good recovery strategy includes a regular schedule for backing up the entire database as well as saving the recovery log files Your overall strategy also needs to include procedures for recovering command scripts applications user defined functions UDFs stored procedure code in operating system libraries and load copies DB2 distinguishes between two types of databases non recoverable and recoverable Non recoverable means that DB2 can only restore the entire database to the point in time when the backup was taken
515. tion 19 the high performance of the database will be maintained at the same level If one partition in a cluster fails its resources can dynamically be transferred to another machine ensuring high availability Another benefit of the shared nothing approach used by DB2 for Linux is that it does not require specialized hardware making the solution much simpler less expensive and suitable for Linux based commodity hardware High Speed Interconnect Figure 1 6 Shared nothing architecture 1 4 3 Partitioned database 20 DB2 exploits the power of Linux clusters by employing database partitioning In a partitioned environment a database is distributed across multiple partitions usually residing on different machines Each partition is responsible for a portion of a database s total data A database partition is sometimes also called a node or a database node Because data is divided across database partitions you can use the power of multiple processors on multiple physical nodes to satisfy requests for information Data retrieval and update requests are decomposed automatically into sub requests and executed in parallel among the applicable database partitions As an illustration of the power of processing in a partitioned database system assume that you have 100 000 000 records that you want to scan in a single partition database This scan requires that a single database manager search 100 000 000 records Now suppo
516. tion and has access to all of the resources in the machine One partition per machine is typical for systems having one or two processors When using SMP machines with several processors it is possible to create more than one partition on the same system These are called logical database partitions A logical database partition differs from a physical partition in that it is not given control of an entire machine Although the machine has shared resources database partitions do not share all resources Processors are shared but disks and memory are not See Figure 1 10 on page 24 Chapter 1 Introduction 23 24 Communication Facility SMP SMP Machine Machine Communication Facility Partition 2 Partition 3 Partition 4 Figure 1 10 A partitioned database across a cluster of SMP machines There are advantages to using logical partitions on high SMP systems in both clustered and non clustered environments Logical database partitions can provide better scalability Multiple database managers running on multiple logical partitions can make fuller use of available resources than a single database manager can The ability to have two or more partitions coexist on the same machine regardless of the number of processors allows greater flexibility in designing high availability configurations and failover strategies Upon machine failure a database partition can be automatically moved and restarted ona second machine that already contains ano
517. tion keys are used to determine on which database partition each portion of the data resides The data must be distributed before it can be loaded at the correct database partition Chapter 6 Administering databases 315 We have demonstrated using the LOAD command with default settings to load data into a partitioned database table When loading data into a multi partition database you can also use one of the following modes gt PARTITION_AND_LOAD Data is distributed and loaded to all database partitions in parallel This mode is the default for the LOAD command PARTITION_ONLY Data is distributed and the output is written to files in a specified location on each loading database partition These files can be loaded into the database using the LOAD_ONLY mode LOAD_ONLY The distribution process is skipped and the data is loaded simultaneously on the corresponding database partitions LOAD_ONLY VERIFY PART As with LOAD_ONLY each additional row is checked to verify that it is on the correct database partition ANALYZE ANALYZE generates an optimal distribution map with even distribution across all database partitions To use these modes there are options that are specific for loading in a partitioned database environment such as gt gt PART_FILE_LOCATION The fully qualified location of the partitioned files OUTPUT_DBPARTNUMS A list of partition numbers which represents the database partitions on whic
518. tion time is a good opportunity to consider creating a new database to leverage the full advantages of DB2 9 5 features and functions or change the database settings which can only be done in a new database The considerations include gt Automatic storage This feature can only be enabled at database creation time gt Database codepage The database codepage determines which characters you can store in the database You cannot change the codepage after the database is created In DB2 9 5 the default codepage is Unicode gt Database territory This setting determines the date and time formats You must define this option during database creation gt Database collating sequence The order in which character data is sorted in a database depends on the structure of the data and the collating sequence that is defined for the database The database collating sequence is specified during database creation time and it cannot be changed afterward Chapter 4 Migration and fix packs 171 Discontinued and deprecated functionality Here are several discontinued and deprecated functions in Version 9 5 gt The w option for db2icrt db2ilist and db2iupdt gt The db2undgp command gt Several registry and environment variables such as DB2LINUXAIO and DB2_LGPAGE_BP gt The IMPORT command options CREATE and REPLACE_CREATE are deprecated gt XML Extender is deprecated When you migrate DB2 UDB Version 8 you have to review the ch
519. to load data from file db2backup rest_table NODE0001 data SQL3110N The utility has completed processing 2 rows were read from the input file SQL3221W Begin COMMIT WORK Input Record Count 2 SQL3222W COMMIT of any database changes was successful SQL3149N 2 rows were processed from the input file 2 rows were successfully inserted into the table 0 rows were rejected Number of rows read Number of rows skipped Number of rows inserted Number of rows updated Number of rows rejected Number of rows committed iT NOON Oh gemini db2 connect to itsodb completed ok db2instl mensa gt db2 select from tab1 ID NAME Chapter 6 Administering databases 273 1 Tina 2 Jonas 2 record s selected The table was recreated and the table data is available 6 2 Table index reorganization and statistics collection 274 When considerable changes have been made to a table the physical data pages for the table and its indexes will become discontinuous or fragmented If a clustering index exists for a specific table it can become badly clustered after many changes have been made against the table and the index key entries Additional costs such as CPU time and I O operations will be required to manage a similar workload under these conditions which can lead to obvious performance degradation Performing maintenance activities on your databases is essential in ensuring that they are optimized for perf
520. to set the DBM configuration 1 Start the Control Center and expand the tree to the desired instance 2 Right click the instance name to open the pop up window and choose Configure Parameters Figure 3 20 Ea Control Center 23 Control Center O All Systems ef vususe Bo Instances EQ Figure 3 20 Configure the DBM parameter in the Control Center 3 Make your updates and check Update when available Dynamic for every parameter that you want to change if the option is available on the window At the bottom of the window is a brief description about the selected parameter Figure 3 21 on page 139 138 Up and Running with DB2 on Linux r MAX_CONNRETRIES 5 MAX_TIME_DIFF 60 wm Change DBM Configuration Parameter DF _MON_BUFPOOL START_STOP_TIME 10 V Monitor DFT_MON_LOCK DFT_MON_SORT DFT_MON_STMT DFT_MON_TABLE DFT_MON_TIMES DFT_MON_UOW OK Joi Corine Figure 3 21 Change parameter 4 After all of the desired changes have been made click OK and these changes will be applied Figure 3 22 he DBM configuration settings were updated successfully Figure 3 22 DBM configuration changes finished Chapter 3 Post installation tasks 139 The default behavior of the UPDATE DBM CFG command is to apply the change immediately If you do not want the change to be applied immediately use the DEFERRED option on the UPDATE DBM CFG command Command line Commands to change the setting of the DBM
521. topics Installing a license key Setting up a license policy Changing the enforcement policy Generating a compliance report vvvy If you installed a DB2 product with a Try and Buy license and now you want to upgrade to a full license you do not need to reinstall the DB2 product You simply upgrade your license 3 9 1 DB2 License Center 160 The DB2 License Center is a graphical tool within the Control Center that manages licensing You can use this tool to view license status and usage information for DB2 products installed on your system add and remove license keys and specify user and enforcement policies The DB2 License Center can also generate usage statistics and display connection information for current users To access the License Center 1 Log in as the instance owner 2 From the Control Center select Tools gt License Center 3 Select the system and product on which you want to configure licensing You can configure a local or remote system Select DB2 Enterprise Server Edition from the Installed products list box as shown in Figure 3 33 on page 161 Up and Running with DB2 on Linux Figure 3 33 DB2 License Center Installing a license key To install a license key using the License Center you must add a db2 lic license file 1 Select Add from the License menu 2 Select From a file and choose the appropriate directory If you purchased a fully licensed DB2 product the db2ese lic license file is
522. tput Example 7 31 Using sar to monitor system activities mensa tmp sar A o sartest bin 5 60 gt dev null amp 1 11457 mensa tmp sar u s 14 34 00 f sartest bin more Linux 2 6 16 46 0 12 smp mensa 02 15 08 14 34 01 CPU user nice system iowait idle 14 34 06 all 1 00 0 00 1 10 19 58 78 32 14 34 11 all 2 30 0 00 1 40 17 78 78 52 14 34 16 all 0 20 0 00 0 80 18 92 80 08 14 34 21 all 2 30 0 00 0 90 23 42 73 37 14 34 26 all 0 50 0 00 0 70 17 68 81 12 14 34 31 all 1 80 0 00 0 90 23 90 73 40 14 34 36 all 1 20 0 00 0 80 14 70 83 30 14 34 41 all 1 00 0 00 0 90 19 48 78 62 14 34 46 all 2 10 0 00 0 90 15 30 81 70 Average all 1 38 0 00 0 93 18 97 78 72 mensa tmp sar w c s 14 34 45 e 14 35 30 f sartest bin more Linux 2 6 16 46 0 12 smp mensa 02 15 08 14 34 46 proc s 14 34 51 0 60 14 34 56 1 20 14 35 01 0 40 14 35 06 1 00 14 35 11 0 40 14 35 16 1 40 14 35 21 0 40 422 Up and Running with DB2 on Linux 14 35 26 Average 14 14 14 14 14 14 14 14 14 234 34 34 235 35 35 35 235 35 46 51 56 01 06 11 16 21 26 Average tmp sar n DEV s 14 36 00 f sartest bin egrep eth0 IFACE IFACE rxpck s txpck s rxbyt s txbyt s rxcmp s txcmp s rxmcst s mensa 14 36 14 36 14 36 14 36 14 36 14 36 01 06 11 16 21 26 Average cswch s 787 1479 617 1562 600 1559 627 1510 1092 03 36 80 20 60 92 29 82 50 eth0 883
523. trator can register each node name by using the register node command Tivoli requires certain storage pools to store the archived log files and the database backup copy By default an archive storage pool ARCHIVEPOOL is used for storing DB2 archive logs sent by the DB2 log manager and a backup storage pool BACKUPPOOL is used to store all DB2 backup files The Tivoli Storage Manager admin user will also set up a password for the node We need to save this Tivoli Storage Manager password at our database server which is the Tivoli Storage Manager client Change to the directory INSTHOME sqllib adsm and perform the steps shown in Example 6 7 Example 6 7 Set the password at the Tivoli Storage Manager client db2inst1 mensa db2home db2inst1 sqllib adsm gt su root root s Password db2inst1 mensa db2home db2inst1 sqllib adsm gt dsmapipw kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Tivoli Storage Manager f API Version 5 4 0 5 kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Enter your current password Enter your new password Enter your new password again Your new password has been accepted and updated DB2 provides the db2adutl tool to manage the backup files in Tivoli Storage Manager You can view and delete DB2 backup files as well as bring backup files from Tivoli Storage Manager storage to the database server All options are shown if you type db2adut1 Note A complete description o
524. ude DB2 troubleshooting database performance management and database maintenance Veiko Spranger is an Advisory IT Specialist in it Services and Solutions GmbH an IBM subsidiary with 14 years of experience in DB2 focusing on DB2 Distributed and Business Intelligence Veiko is a member of the Central Region Frontoffice support team and the EMEA BI VFE virtual front end and an IBM Certified Advanced Database Administrator He is an SAP Support Backoffice Specialist for DB2 for LUW focusing primarily on DB2 backup restore and recovery Up and Running with DB2 on Linux y Figure 1 Left to right LiFang Helmut Veiko and Christian Acknowledgements Thanks to the following people for their contributions to this project Boris Bialek lan Hakes Jeff Shantz Martin Schlegel Rav Ahuja Grant Hutchison Yvonne Chan Amy Tang Budi Surjanto Paul Zikopoulos IBM Toronto Laboratory Canada George Lapis Gary Lazzotti Tom Cheung IBM Silicon Laboratory USA Daniel Krook IBM Sales and Distribution USA Preface XV Emma Jacobs Sangam Racherla Deanna Polm International Technical Support Organization Thanks to the authors of the previous editions of this book gt Authors of the first edition Up and Running with DB2 on Linux published in March 2003 were Rav Ahuja Louisa Ford Paul Jud Kang Yong Ying Become a published author Join us for a two to six week residency program Help write a book dealing wit
525. ued from any database partition in the db2nodes cfg file It can be used to update the catalogs on the catalog database partition In a partitioned database the RUNSTATS command collects the statistics on only a single node If the database partition from which the RUNSTATS command is executed has a part of the table the command will execute on that database partition directly Otherwise the command executes on the first database partition in the database partition group across which the table is partitioned It is possible to perform read or write operations to the table where RUNSTATS is taking place by using different RUNSTATS command parameters For example ALLOW READ ACCESS specifies that other users can have read only access to the table while statistics are calculated and ALLOW WRITE ACCESS specifies that other users can read from and write to the table while statistics are calculated Note Because reorganizing a table usually takes more time than running statistics you might execute RUNSTATS to refresh the current statistics for your data and rebind your applications If refreshed statistics do not improve performance reorganization might help The RUNSTATS utility is also available in the DB2 Control Center as shown in Figure 6 26 on page 288 Chapter 6 Administering databases 287 Control Center 2 control Center E All Systems 5 All Databases L F itsops arenes G Views Aliases E Nicknames Cache Objects 5 Tri
526. up job in the next available maintenance window a user defined time period for running the automatic maintenance activities Note You can still perform manual backup operations when automatic maintenance is configured DB2 will perform the automatic backup operations only if they are required You can configure automatic backup using the graphical user interface tools the command line interface or the AUTOMAINT_SET_POLICY stored procedure Chapter 6 Administering databases 249 Configure automatic backup using the wizard In this section we demonstrate how to enable automatic database backup for the ITSODB database using the Configure Automatic Maintenance wizard The wizard can be launched from the DB2 Control Center as shown in Figure 6 10 Systems Databases Figure 6 10 Configure Automatic Maintenance in Control Center Figure 6 11 on page 251 shows the panel where you can specify the time frame in which the automatic maintenance can be performed 250 Up and Running with DB2 on Linux Configure Automatic Maintenance Figure 6 11 Specify maintenance panel At the activities page you have to select the check box for automatic backup refer to Figure 6 12 on page 252 Click Configure Settings to specify policy setting details such as the backup location Chapter 6 Administering databases 251 Introduction Select a maintenance activity to configure al 2 Type Automatic maintenance includes the fol
527. up to now and the display continues to show records until you press Ctrl C to stop it View logs within a certain time interval To display all of the messages that were logged after the timestamp 2008 02 14 10 00 inclusively enter this command db2diag t 2008 02 14 10 00 To put all entries between 2008 02 14 12 00 30 and 2008 02 14 at 3 PM to an output file called db2diag_082014noon log enter db2diag t 2008 02 14 12 00 30 2008 02 14 15 o db2diag 082014 log The format for the date and time is YYYY MM DD hh mm ss nnnnnn however you do not need to use the full timestamp To display the entries of the last three days enter db2diag H 3d 402 Up and Running with DB2 on Linux View logs for a specific database If you have several databases in your DB2 instance and you want to see the db2diag log entries only for one database use db2diag g db ITSODB The g option is a grep like filtering capability for a comma separated list of field pattern pairs Another example is db2diag g db SAMPLE level Event pid 5971 This command shows all events for process ID 5971 that are unrelated to the SAMPLE database The field names are case insensitive while search patterns input fields are case sensitive To get a list of all of the available field names use the db2diag h command Partitioned database In a partitioned database environment the db2diag log file contain the entries for all of the database partitions
528. ure 6 50 provides a sample to specify running a weekly task and setting an end date February 29 2008 Sl UES caved aenach ay Figure 6 50 Scheduling tasks to run repetitively Chapter 6 Administering databases 345 Figure 6 51 is another example that is used to run a task once Edit Task Properties Runstats Task February 7 2008 e 12 10 00 a Run every Thursday at 11 34 29 AM starting Run once on 2 7 08 at 12 10 00 PM m db2inst1 Figure 6 51 Scheduling tasks for running once Furthermore if you want to apply the scheduling pattern for other tasks you can save the schedule list by clicking Save List of Schedules in the right pane of the panel When saved the next time that you schedule a task you can choose Use saved schedule with the desired name to schedule a task 6 Specify the condition on which to send a notification You can specify under which condition a notification will be sent and the notification can be sent to a contact or contact group by e mail or pager or sent to the DB2 Journal as a message entry Conditions can be success failure or both You also can specify multiple notifications for different conditions for only one task In Figure 6 52 on page 347 the notification will be sent to the DB2 Journal as a message entry 346 Up and Running with DB2 on Linux Poles Create journal Torii Create journal message The task amp O0wner amp Name wit
529. uring online index reorganization using the REORG INDEXES command with the ALLOW WRITE ACCESS option all indexes on the specified table are rebuilt while read and write access to the table is allowed Any changes made to the underlying table that affect indexes while the reorganization is in progress are logged in the database logs The reorganization will process the logged changes while rebuilding the index Note The default behavior of the REORG INDEXES command is ALLOW NO ACCESS which places an exclusive lock on the table during the reorganization process You can specify ALLOW READ ACCESS or ALLOW WRITE ACCESS to permit other transactions to read from or update the table As with table reorganization index reorganization is also integrated into the DB2 Control Center Refer to Figure 6 23 on page 285 Up and Running with DB2 on Linux Control Center 2 Control Center Ho All Systems All Databases L J itsops views 5 Aliases Nicknames Cache Objects Triggers Schemas Indexes Table Spaces Event Monitors Database partition groups Buffer Pools Creator 0 Application Objects goumis eo User and Group Objects F va Federated Database Objects a Open G XML Schema Repository SR Actions O ITSOREPL O SAMPLE A TooiscatT dp Create New Tak Figure 6 23 Table context menu In the Reorganize Indexes panel you can configure the REORG method and various options Figure 6 24 on page 286 Chapter 6
530. uthentication 54 HTML 87 HTML document 439 l I O operations 182 ibm_db2 439 Index 513 IBMDEFAULTBP 384 inconsistent state 177 incremental backup 230 index 16 index reorganization 6 Information Integration application 2 inplace table reorganization 281 ins 198 instance 14 instance owning machine 53 instant level authority SYSADM 150 SYSCTRL 150 SYSMAINT 150 SYSMON 150 Integrated Query Editor 199 interactive mode 405 intra parallelism 17 iostat 419 ipcs 30 ISO8859 1 96 J Java 433 Java Routine Debugger 199 JDBC 4 jdk32 453 jdk64 453 journal filesystem 42 K kernel 26 kernel parameter 26 kernel parameters sem 31 keyboard shortcut 224 kilobytes 419 ksysguard 424 L large object LOB 16 layout 224 libaio 33 license status 160 life cycle 198 life sciences 3 Linux distribution 26 514 Up and Running with DB2 on Linux load balancer 13 load copy image 5 local workspace 217 Locking memory 133 LOCKTIMEOUT 141 log 44 log directory 234 log file manager 230 log manager 234 log mirroring 44 log path 44 120 log space 35 logical database partition 23 logical partition 22 497 logical_port 105 logprimary 170 M memory 26 memory component 381 382 memory consumption 414 Memory Tracker 383 memory usage 383 Memory Visualizer 381 message queue limit 30 migrate database 181 migration 167 169 migration roadmap 168 migration strategy 168 minimum recovery time 260 mirro
531. uthorized User Option Expiry date Permanent Product identifier db2ese Version information g 5 Number of licensed authorized users 25 Features DB2 Database Partitioning Not licensed DB2 Performance Optimization ESE Not licensed DB2 Storage Optimization Not licensed DB2 Advanced Access Control Not licensed DB2 Geodetic Data Management Not licensed DB2 pureXML ESE Not licensed IBM Homogeneous Federation ESE Not licensed IBM Homogeneous Replication ESE Not licensed The ENV_FEATURE_INFO administrative view and the ENV_GET_FEATURE_INFO table function also return information about all available features for which a license is required For each feature there is information about whether a valid license for the feature is installed A sample output is shown in Example 3 42 on page 164 Chapter 3 Post installation tasks 163 164 Example 3 42 Using the ENV_FEATURE_INFO view db2inst1 mensa gt db2 select from sysibmadm env_feature_info FEATURE_NAME FEATURE_FULLNAME LICENSE_INSTALLED PRODUCT_NAME FEATURE_USE_STATUS DPF DB2_DATABASE_PARTITIONING FEATURE N ESE NOT_USED POESE DB2_PERFORMANCE_OPTIMIZATION FEATURE_FOR_ESE N ESE NOT_USED s0 DB2_STORAGE_OPTIMIZATION FEATURE N ESE NOT_USED AAC DB2_ADVANCED_ACCESS_CONTROL_FEATURE N ESE NOT_USED GEO DB2_GEODETIC_DATA_MANAGEMENT FEATURE N ESE NOT_USED XMLESE DB2_PUREXML_FEATURE_FOR_ESE N ESE NOT_USED HFESE IBM_HOMOGENEOUS FEDERATION FEA
532. velopment which provides the flexibility in application design Figure 8 1 illustrates three database connection configurations Scenario 1 Application and database server Application Scenario 2 Application server Application Locally cataloged DB2 for the remote database Scenario 3 Application server Application Database server SA Database server Figure 8 1 Connection scenarios for applications gt Scenario 1 A local client connects to a local database This configuration requires a locally installed database server In this scenario the application and the database run on the same server which is useful for small systems or for test and development systems gt Scenario 2 A local client connects to a remote database by using a locally cataloged node This configuration requires only a locally installed DB2 client The database is hosted on another system that has a DB2 data server installed After cataloging the database node the remote database looks like a local database from the application s point of view gt Scenario 3 A local client connects to a remote database directly This configuration does not require any DB2 software installed on the local system Instead you use a driver that supports the direct connection to the Up and Running with DB2 on Linux remote database such as a Type
533. w as the root user you need to switch to the DB2 instance owner ID and set up the display before you can start the Control Center You have two ways to set up the environment for running Control Center Example 3 1 shows the simpler way Example 3 1 Start Control Center method one puget xhost puget su db2instl db2instl puget gt export DISPLAY 0 0 db2instl puget gt db2cc amp 1 6051 db2inst1l puget gt The ampersand character amp after the command returns the shell prompt which allows you to use this shell for other commands We do not suggest that you use method one for security critical production systems because it allows everybody to access your X server The more secure method is to use Xauthority as demonstrated in Example 3 2 Example 3 2 Start Control Center method two puget su db2instl db2instl puget gt scp root localhost Xauthority tmp xauth tmp Password Xauthority 100 161 0 2KB s 00 00 db2instl puget gt export DISPLAY 0 0 db2inst1 puget gt xauth merge tmp xauth tmp Up and Running with DB2 on Linux db2instl puget gt db2cc amp 1 6052 db2inst1 puget gt In method two we copy the file Xauthority from the server root user to the client db2inst1 user and merge it with the existing one We chose the scp command for convenience This command allows the user db2inst1 to access the root owned X server We also set the DISPLAY to the same host and use th
534. we demonstrate the creation of a table space over all partitions defined in db2nodes cfg using the default database partition group IBMDEFAULTGROUP Up and Running with DB2 on Linux First we create the directory for the table space container on both systems using the following command db2_all typeset Z4 DB2NODE mkdir p db db2inst1 NODE DB2NODE ITSODB SAMPLE_MPL Example 3 18 shows the creation of table space SAMPLE_MPL We use the variable V in the create tablespace statement It will be replaced by the partition number during run time Example 3 18 Create multi partition table space connect to itsodb create tablespace sample_mpl in IBMDEFAULTGROUP pagesize 4k MANAGED BY SYSTEM using db db2inst1 NODE000 N ITSODB SAMPLE_MPL on dbpartitionnum 0 using db db2inst1 NODE000 N ITSODB SAMPLE_MPL on dbpartitionnum 1 extentsize 8 prefetchsize 32 Example 3 19 shows the creation of a database partition group sng_01 anda single partition table space on partition 1 We create a container on gemini partition 1 before creating the table space mkdir db db2inst1 NODE0001 ITSODB SAMPLE_SNG Example 3 19 Create single partition table space connect to itsodb create database partition group sng_01 on dbpartitionnum 1 create tablespace sample_sng in sng_01 pagesize 4k MANAGED BY SYSTEM using db db2inst1 NODE0001 ITSODB SAMPLE_SNG on dbpartitionnum 1 extentsize 8 prefetchsize 32 Now node 0 me
535. wing recommendations satisfy all of the requirements that you have specified Select a recommendation from the list to view its details in the Details field To view the full set of recommendations click Show All Recommendations To accept the recommendation you have selecteg and to review the actions associated with it click Next Recommendations 2 Rank Description Properties V Preferred recommendations 2 Add a new stripe set The recommendation w B fa d new table space containers The recommendation w Figure 7 22 Selecting a recommendation iv The Review the required actions panel appears Figure 7 23 In our sample we need to add containers in the DB2 Control Center Click Launch and follow the Usage instruction to add containers in the Control Center After taking the corresponding action click Next Review the required actions The recommended tool can help to resolve the current health alert To learn more about this tool click Details To launch this tool click Launch For a tool that the advisor cannot launch directly follow the directions in the tool description Recommendation Add new table space containers Details Recommended tool Control Center Alter Table Space Notebook Usage instruction Click the Containers page Select Add to open the Define Container dialog Complete the required fields on the Define Container dialog and click OK to add the new contai
536. with each column representing a monitor element In Example 7 23 we capture a snapshot of the database information for the ITSODB database using the SNAPDB administrative view Example 7 23 Database snapshot using SNAPDB administrative view db2inst1 mensa gt db2 select snapshot_timestamp db status substr db_name 1 10 dbname dbpartitionnum from sysibmadm SNAPDB dbpartitionnum from sysibmadm SNAPDB lt SNAPSHOT_TIMESTAMP DB_STATUS DBNAME DBPARTITIONNUM 2008 02 15 17 42 32 773025 ACTIVE ITSODB 2008 02 15 17 42 29 024832 ACTIVE ITSODB 1 2 record s selected You can capture the same information using table functions Each table function returns a table with one row per monitored object for the specified database partition The column names of the returned table correlate with the monitor element names In Example 7 24 we capture the same snapshot of database information that we captured in Example 7 23 by using the SNAPDB administrative view but this time we use the table function SNAP_GET_DB_V95 Example 7 24 Getting the snapshot by using the table function db2inst1 mensa gt db2 SELECT SNAPSHOT TIMESTAMP DB STATUS substr DB_NAME 1 10 DBNAME DBPARTITIONNUM FROM TABLE SNAP_GET_DB_V95 ITSODB SNAPSHOT_TIMESTAMP DB_STATUS DBNAME DBPARTITIONNUM 2008 02 15 17 58 26 933775 ACTIVE ITSODB 2008 02 15 17 58 25 915850 ACTIVE ITSODB 1 2 record s selected Chapter 7 Monitoring and troubleshooting DB2 411 To list
537. without write access to the tables while the table is being reorganized In a partitioned database environment determining whether to carry out automatic reorganization and whether to initiate automatic reorganization is done on the catalog partition The reorganization runs on all of the database partitions on which the target tables reside 6 2 2 Manual table maintenance If you are not using the automatic table maintenance feature you need to be sure that your table statistics are up to date and the tables are reorganized from time to time so that the performance of your applications can be kept optimal 280 Up and Running with DB2 on Linux DB2 provides the following utilities to perform this job manually gt gt gt REORG RUNSTATS REBIND Table reorganization The REORG TABLE option reorganizes a table to match its index and to reclaim space You can reorganize the system catalog tables as well as user tables DB2 provides two methods for reorganizing tables gt Inplace online reorganization Inplace table reorganization allows applications to access the table during the reorganization In addition online table reorganization can be paused and resumed later by anyone with the appropriate authority by using the schema and table name A simple command for an online reorganization is db2 reorg table db2instl item inplace You can also use the ADMIN_CMD procedure to do the reorg db2 call sysproc admin_cmd reorg
538. ws how to grant this privilege on all functions under a specific schema db2 grant execute on function lt schema name gt to lt user gt If the DIAGLEVEL parameter is set to 2 or less set this parameter to 3 or higher before the migration Issue the following command db2 update dbm cfg using diaglevel 3 Chapter 4 Migration and fix packs 175 176 8 Disconnect all of the connections in Version 8 or Version 9 1 databases a Stop the DB2 license service using db2licd end b Stop all command line processor sessions by issuing db2 terminate on each session window c Disconnect all applications and users For a list of all database connections enter the db2 list applications command You can disconnect applications and users by entering db2 force applications all 9 If you use replication archive all of your DB2 log files using the archive log command This command closes and truncates the active log file for your database The command syntax is as follows db2 archive log for database lt database_alias gt user lt user_name gt using lt password gt 10 Back up databases We suggest that you do a full offline backup from each local database You can use the DB2_ALL command with the BACKUP DATABASE command to back up a database in a partitioned database environment See Chapter 6 Administering databases on page 227 for more details about this option and others ways to perform a backup 11 If you are using r
539. xquery sq db2instl puget gt db2 tf select_xquery sql ENTITYID 2 record s selected In Example 8 32 we retrieve the result of the XQuery as a table and join it to the other relational tables directly Example 8 32 Retrieve XML data as a table select_table sql SELECT p entityid XIN FROM product p XMLTABLE i description price lt 9 PASSING p xdata AS i COLUMNS name CHAR 30 PATH name price DECIMAL 9 2 PATH price AS x The function XMLTABLE converts the XML document into a table You can see the result in Example 8 33 on page 459 The column ENTITYID comes from the relational table and the column s name and price come from the XML data Up and Running with DB2 on Linux Example 8 33 Retrieve the XML data as a table db2instl puget gt db2 tf select_table sql ENTITYID name price 3 Jean 7 99 4 Shirt 3 99 2 record s selected Example 8 34 shows an enhanced XQuery example which retrieves an HTML list Example 8 34 XQuery example with a loop select_xq sq VALUES XMLSERIALIZE XMLQUERY lt ul gt for x in db2 fn xmlcolumn PRODUCT XDATA description name price lt 9 return lt 1i gt data x lt li gt lt ul gt AS CLOB 70 We use the function XMLSERIALIZE to convert the data into a CLOB The function XMLQUERY retrieves the result of the XQuery expression The result is shown in Example 8 35 Example 8 35 Result of XQuery example db2instl puget
540. you only need to force off users who are connected to the database where we want to change the log path Connect to the database During the connection the log will be relocated Example 3 22 shows that the log path has been changed Example 3 22 Change the online log path db2instl puget gt db2 terminate DB20000I1 The TERMINATE command completed successfully db2instl puget gt db2 connect to itsodb Database Connection Information DB2 LINUX 9 5 0 DB2INST1 ITSODB Database server SQL authorization ID Local database alias db2inst1l puget gt db2 get db config for itsodb grep NEWLOGPATH MIRRORLOGPATH Path to log files Changed path to log files NEWLOGPATH Path to log files db210g1 1TSODB NODEO000 Mirror log path MIRRORLOGPATH For the partitioned database use the following command to check the path to the log files entry db2_all db2 connect to itsodb db2 get db cfg for itsodb grep Path s change is logged in db2diag log as shown in Example 3 23 If you receive error messages during the change you will see additional information here Example 3 23 Entry in db2diag log for LOG change 200 PID INS APP AUT EDU FUN CHA 200 8 02 12 10 30 16 368903 480 13909906483 LEVEL Event 10434 TID 2968513440 PROC db2sysc 0 TANCE db2instl NODE 000 DB ITSODB HDL 0 41 APPID LOCAL db2inst1 080212175506 HID DB2INST1 ID 61 EDUNAME db2agent ITSODB 0 CTION DB2 UDB config inst

Up and Running with DB2 on Linux

Contents

Download Pdf Manuals

Related Search

Related Contents