Upgrading to DB2 9.5 for Linux, UNIX, and Windows

Transcription

1 Upgrading to DB2 9.5 for Linux, UNIX, and Windows Bob Harbus Worldwide DB2 Evangelist Team IBM Toronto Lab May 20, 2010

2 Agenda Recommended reading Overview of the upgrade process Upgrading a data server 3 stages of successful upgrades Considerations DB2 Connect Clients Applications and routines Best practices Additional Material 2

3 Recommended Reading DB2 Migration Portal One-stop-shop for essential information DB2 Upgrade Home Page Links to webcasts, videos, wikis, etc. DB2 9.5 Migration Guide Comprehensive, step-by-step documentation Available in DB2 Information Center ic=/com.ibm.db2.luw.qb.migration.doc/doc/c html Downloadable PDF 3

4 Recommended Reading (cont.) DB2 9.5 What s New Outlines new and changed functionality Available in the DB2 Information Center ic=/com.ibm.db2.luw.wn.doc/doc/r html Downloadable PDF Estimating database upgrade time and disk space requirements 4

5 Upgrading to DB2 9.5 DB2 9.5 is the next-generation hybrid data server Optimized management of XML and relational data Component Data Server Client Upgrade Required? Yes, instance & database Optional Upgrading not required when installing fixpacks Applications and routines may require changes (rare) 5

6 DB2 9.5 Simplifies Server and Client Upgrades Coexistence supported on all DB2 Linux, UNIX, and Windows operating platforms Install multiple DB2 server and client versions Upgrading is no longer forced onto Windows users Install provides migrate option Windows only Automatically upgrades existing DB2 UDB V8 instances and DAS Database upgrade still required 6

7 Benefits of Coexistence Each installation can be serviced independently Enables the creation of upgrade test environment Provides fallback capability Instead of upgrading, do a backup and restore DB2 UDB V8 instance and database remains intact and unaltered Note: You can restore a backup of a 32-bit DB2 UDB V8 database into a 64-bit DB2 9.5 instance Endianness (byte order) must match on Linux/UNIX 7

8 Operating System Support OS Software Hardware AIX HP-UX Linux Solaris Windows AIX Version 5.3 TL6 SP2 + APAR IZ03063 AIX Version 6.1 (64-bit kernel required) HP-UX 11iv2 ( ) HP-UX 11iv3 (11.31) Red Hat Enterprise Linux 4 Update 4 Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 9 SP3 SUSE Linux Enterprise Server 10 SP1 Solaris 9 Solaris 10 (64-bit kernel required) XP Professional Vista Ultimate/Business/Enterprise Server 2003 Standard/Enterprise/Datacenter Server 2008 Standard/Enterprise/Datacenter (32-bit and 64-bit) POWER3 processors and higher Itanium based HP Integrity Series Systems x86, 32-bit Intel & AMD processors x64, 64-bit AMD64 & Intel EM64T POWER eserver System z, System z9, or System z10 UltraSPARC Solaris x64 (Intel 64 or AMD64) All Intel and AMD processors capable of running the supported Windows operating systems For most recent detailed requirements see and Specific OS patches are also in requirements, review and apply these prior to installing new release! 8

9 Let s Upgrade to DB2 9.5 May 20, 2010

10 Data Server Upgrade (in 1 Page) Install DB2 9.5 Perform pre-migration tasks Verify the databases using the db2ckmig tool db2ckmig tool (run on all partitions in data partitioned environments) In-Place Upgrade Upgrade instance (db2imigr) Upgrade databases (MIGRATE DATABASE command) Side-by-Side Upgrade Create DB2 9.5 instance (db2icrt) Restore database offline backup (RESTORE DATABASE command) Database upgrade does not alter your data Converts system catalog format, modifies select disk structures For all the details ic=/com.ibm.db2.luw.qb.migration.doc/doc/c html 10

11 Follow the Path DB2 9.1 DB2 UDB V8.x Recommendation Upgrade to latest available DB2 9.5 fixpack Upgrade from any version of DB2 UDB V8.x or DB2 9 DB2 9.5 Pre-DB2 UDB V8.1 must upgrade to DB2 UDB V8.2.2 first 11

12 Upgrade Hiccups DB2 UDB V8 APAR IY85495 Database configuration reports incorrect rollforward pending state (fixed in FP14) db2ckmig will report an error AIX DNS lookup may cause commands to hang DB2 supports IPv4 and IPv6 as of DB2 9 db2icrt, db2start, db2stop commands appear to hang Double-check hosts setting in /etc/netsvc.conf Technote # , APAR # IZ ibm.com/support/docview.wss?rs=0&q1= &uid=swg &loc= en_us&cs=utf-8&cc=us&lang=en 12

13 Changes in DB2 9.5 The following pages highlight some changes in Process and memory model Configuration parameters Registry and environment variables Behaviour More details in Migration Guide =/com.ibm.db2.luw.qb.migration.doc/doc/r html Refer to What s New documentation in the online (or local!) Information Centre 13

14 Multi-threaded Architecture on Linux and UNIX Benefits Simplified and more dynamic configuration Self-Tuning Memory Manager (STMM) database memory tuning now available on all platforms Streamlined problem determination Improved performance Less system and memory resources Fewer DB2 server processes Modify scripts to replace ps with db2pd edus More details ic=/com.ibm.db2.luw.wn.doc/doc/i html Unfenced routines, unfenced wrapper libraries, and security plug-ins must be thread-safe 14

15 DB2 9.5 Simplified Memory Model Database Manager Memory (instance_memory) Per Database Memory Database Global Memory (database_memory) Buffer pools, database heap, utility heap, lock list, etc. Application Global Memory (appl_memory) Application heap, statement heap, etc. Agent Private Memory DBMS Shared Memory 15

16 Instance Configuration Changes (DB2 9.5) Changes under new memory model New behavior for instance_memory Max. memory that a single database partition can allocate Max. increased to 256 TB (64-bit platforms) New value is AUTOMATIC, approx 75-95% of physical RAM mon_heap_sz changes to AUTOMATIC If max_coordagents was -1 Upgrade changes it to the value of maxagents If num_poolagents was -1 Upgrade changes it to the value of maxagents 16

17 Instance Configuration Changes (DB2 9.5) (cont.) Default for new instance is AUTOMATIC for fenced_pool, max_connections, mon_heap_sz, and num_poolagents New maximum values max_coordagents, num_initagents, and num_initfenced (64K) federated_async (32K) Deprecated agentpri, maxagents, maxcagents, and query_heap_sz Discontinued priv_mem_thresh 17

18 Instance Configuration Changes (DB2 9) Fast Communication Manager (FCM) Performs inter-partition communication in DPF Re-architected to enhance performance and simplify tuning New fcm_num_channels parameter Replaces the following deprecated parameters fcm_num_rqb fcm_num_anchors fcm_num_connect Upgrade calculates a new value to approximate the previous configuration 18

19 Database Configuration Changes (DB2 9.5) New behavior applheapsz Max memory that can be consumed per application Bound by appl_memory (db) or instance_memory (db partition) New value is AUTOMATIC New behavior maxfilop Max file handles that can be concurrently open for each database New value is AIX, HP, Sun 61,440 Linux 30,720 (32-bit) 61,440 (64-bit) Windows 32,768 (32-bit) 65,335 (64-bit) dbheap changes to AUTOMATIC stat_heap_sz changes to AUTOMATIC 19

20 Database Configuration Changes (DB2 9.5) (cont.) New parameter appl_memory Max memory that can be allocated by all agents to service all applications requests Bound by instance_memory (db partition) Default value is AUTOMATIC New database default value is now AUTOMATIC applheapsz dbheap stat_heap_sz stmtheap 20

21 Database Configuration Changes (DB2 9.5) (cont.) Deprecated app_ctl_heap_sz, appgroup_mem_sz, and groupheap_ratio replaced by appl_memory logretain and userexit replaced by logarchmeth1 Numsegs Discontinued estore_seg_sz and num_estore_segs 21

22 Database Configuration Changes (DB2 9) Parameter values that change during upgrade database_memory New name, same DB2 UDB V8 behavior DB2 UDB V8 s AUTOMATIC becomes COMPUTED in DB2 9 dyn_query_mgmt Query Patroller If ENABLE, upgrade changes to DISABLE Re-enable once Query Patroller is installed Parameters with new default values auto_maint, auto_tbl_maint, and auto_runstats ON avg_appls, fcm_num_buffers, num_iocleaners, and num_ioservers AUTOMATIC Upgrade retains the original DB2 UDB V8 settings 22

23 Database Configuration Changes (DB2 9) (cont.) New Self-Tuning Memory Management feature Disabled in upgraded database Controlled by the self_tuning_mem parameter Following parameters support AUTOMATIC setting database_memory sheapthres_shr sortheap pckcachesz locklist maxlocks Upgrade retains the original settings the above parameters 23

24 Registry and Environment Variable Changes DB2_MDC_ROLLOUT Variable Name DB2_USE_DB2JCCT2_JROUTINE Old Default OFF (DB2 UDB V8) ON (DB2 9) Legacy JDBC type 2 driver New Default IMMEDIATE IBM Data Server Driver for JDBC and SQLJ DB2_COLLECT_TS_REC_INFO DB2_EXTENDED_IO_FEATURES DB2_FORCE_FCM_BP DB2MEMMAXFREE DB2_ALLOCATION_SIZE OFF ONLINE_BACKUP_IOPRIORITY setting is discontinued Deprecated Deprecated Deprecated ON 24

25 Registry and Environment Variable Changes (cont.) Instance profile registry variables are upgraded and retain the original settings Global profile registry variables set by the user are not automatically upgraded Complete lists Changed ic=/com.ibm.db2.luw.wn.doc/doc/i html Deprecated ic=/com.ibm.db2.luw.wn.doc/doc/i html Discontinued ic=/com.ibm.db2.luw.wn.doc/doc/r html 25

26 New Database Defaults Automatic storage enabled Introduced in DB2 UDB V8.2.2, simplifies storage management To disable Specify AUTOMATIC STORAGE NO in CREATE DATABASE command Concurrent I/O and Direct I/O enabled Provides I/O performance similar to raw devices To disable Specify FILE SYSTEM CACHING in CREATE DATABASE command Default code page is Unicode 26

27 New Table Space Defaults DMS table spaces are LARGE by default Increases the maximum table size to 16 TB To disable Specify REGULAR in CREATE TABLESPACE statement New default table space settings Updated to reflect current disk technology Use ALTER TABLESPACE statement to update your upgraded databases Concurrent I/O and Direct I/O are enabled To disable Specify FILE SYSTEM CACHING in CREATE TABLESPACE statement 27

28 Other Behavior Changes Reverse scans enabled for new indexes, primary keys, and unique keys Database level auditing requires SECADM authority Backup image file mode changed to 600 Restricts read and write access to instance owner Linux and UNIX only Logs are included by default in the following backup scenarios Online backup of a single-partitioned database Online or offline single system view (SSV) backup of a multi-partitioned database Online or offline snapshot backup 28

29 Additional Memory Requirements Lock structure size changes 32-bit: 48 bytes (was 40 bytes in DB2 UDB V8) 64-bit HP-UX/PA-RISC: 80 bytes (was 64 bytes in DB2 UDB V8) Increase lock list size by <= 1.7% to accommodate metadata overhead On 64-bit HP-UX/PA-RISC, increase by <= 2.5% 29

30 DB2 Connect 9.5 Considerations May 20, 2010

31 DB2 Connect Upgrade Considerations If upgrading from pre DB2 Connect V8.2.2 Authentication type specified in the database directory at the DB2 Connect server overrides the authentication type catalogued at a client If there is no authentication type specified at a client, the default authentication is SERVER Review all considerations in Quick Beginnings for DB2 Connect Servers ftp://ftp.software.ibm.com/ps/products/db2/info/vr95/pdf/en_us/db2c 6e950.pdf 31

32 IBM Data Server Client 9.5 Considerations May 20, 2010

33 Simplified DB2 Client Packages New Package Equivalent Client Package IBM Data Server Client 9.5 DB2 9 Client DB2 UDB V8 Administration Client DB2 UDB V8 App. Development Client IBM Data Server Runtime Client 9.5 DB2 9 Runtime Client DB2 UDB V8 Run-Time Client DB2 UDB V8 Run-Time Client Lite 33

34 DB2 Client Upgrade Considerations DB2 9.5 clients can connect to 32- and 64-bit servers NetBIOS and SNA support discontinued in DB2 9 Catalog using TCP/IP or named pipes Client upgrade is optional Preserves the existing client configuration Multiple client installations supported Install the same or different versions 34

35 Connectivity Support for Clients to DB2 9.5 Servers COMPATIBLE (Full functionality) DB2 9.5 client DB2 9.5 server DB2 9.1 client COMPATIBLE (Limited to DB2 9.1 function) DB2 9.5 server DB2 UDB V8.x client COMPATIBLE (Limited to DB2 UDB V8.x function) DB2 9.5 server 35

36 Connectivity Support for DB2 9.5 Clients DB2 9.5 client DB2 9.5 server DB2 9.1 server DB2 UDB V8.x server Multiple clients can be installed on a single machine 36

37 Connectivity Support Matrix for Clients DB2 Client (32- or 64-bit) DB2 9.5 DB2 9.1 DB2 UDB V8.x DB2 Server (32- or 64-bit) DB2 UDB V8.x DB2 9.1 DB2 9.5 Functionality Limited to DB2 UDB V8.x Limited to DB2 9.1 Full Limited to DB2 9.1 Limited to DB2 UDB V8.x 37

38 Application Considerations May 20, 2010

39 Java and JDBC Changes IBM Data Server Driver for JDBC and SQLJ replaces IBM DB2 Universal JDBC Driver IBM DB2 Driver for JDBC and SQLJ Support for IBM Software Developer Kit for Java 5.x AIX, Windows, Linux (x86, POWER, zseries, and x86_64) Two versions of IBM Data Server Driver for JDBC and SQLJ db2jcc.jar: JDBC 3.0 and earlier db2jcc4.jar: JDBC 4.0 and earlier 64-bit JVM is provided with 64-bit database servers 39

40 Java and JDBC Changes (cont.) DB2 JDBC Type 3 driver was discontinued in DB2 9 Use IBM Data Server Driver for JDBC and SQLJ (Type 4) DB2 JDBC Type 2 driver is deprecated Routines now use IBM Data Server Driver (Type 4) by default To override db2set DB2_USE_DB2JCCT2_JROUTINE = OFF More details in Migration Guide Upgrading Java applications that use IBM Data Server Driver for JDBC and SQLJ ic=/com.ibm.db2.luw.qb.migration.doc/doc/t html Upgrading Java applications that use DB2 JDBC Type 2 driver ic=/com.ibm.db2.luw.qb.migration.doc/doc/t html 40

41 SQL Administrative Views and Routines Changes Some DB2 UDB V8 and DB2 9 administrative routines have been replaced with more comprehensive functions or views Deprecated Function GET_DBM_CONFIG table function (DB2 UDB V8) ADMIN_GET_TAB_INFO table function (DB2 9) New View DBMCFG administrative view ADMINTABINFO administrative view Complete list is available in the Information Center ic=/com.ibm.db2.luw.sql.rtn.doc/doc/r html Applications should switch the new functions or views Versioned table functions have a _V91 or _V95 suffix Administrative views are always based on latest table function version 41

42 Larger Identifiers in DB2 9.5 Package Attribute Constraint Cursor Database partition group Event monitor Specific name Statement Trigger User-defined type Authorization ID (authid) Column Group Schema Identifier Name SQL path (specified by the FUNCPATH BIND option and CURRENT PATH special register) Old Length New Length

43 Using 32-bit Applications and Routines with 64-bit Instances 64-bit DB2 9.5 instances support 32-bit applications (except Linux IPF (Itanium)) 32-bit shared libraries provided Application 32-bit 32-bit Instance 32-bit 64-bit (except Linux on IPF) Embedded shared library path $INSTHOME/sqllib/lib $INSTHOME/sqllib/lib32 $INSTHOME/sqllib/lib $INSTHOME/sqllib/lib32 64-bit 64-bit $INSTHOME/sqllib/lib $INSTHOME/sqllib/lib64 43

44 Using 32-bit Applications and Routines with 64-bit Instances (cont.) Restrictions on 32-bit external stored procedures and UDFs Unfenced 32-bit external routines not supported in 64-bit Support for default function entry points in external routine libraries is deprecated (32-bit AIX and Windows) 32-bit SQL procedures created prior to DB2 UDB V8.2 and upgraded to 64-bit, must be dropped and re-created =/com.ibm.db2.luw.qb.migration.doc/doc/t html 44

45 Best Practices PLAN VALIDATE DEPLOY 45

46 Stage 1 Successful Planning Review Migration Guide and What s New Identify dependencies and requirements Create an inventory of impacted applications Draft a step-by-step upgrade plan Review with impacted stakeholders Receive approval to move forward 46

47 Stage 2 Successful Validation Establish user acceptance criteria and a test plan Setup a test environment Execute the upgrade plan Perform prerequisite upgrades (hardware, OS, etc.) Migrate the DB2 server and/or clients Upgrade applications Perform the validation testing Revise the upgrade plan as necessary Review and approve the final upgrade plan 47

48 Stage 3 Successful Deployment Define and execute a system sanity test Upgrade the production system (deploy) Execute sanity test 48

49 Summary DB2 9.5 provides a best of breed database solution Upgrading to DB2 9.5 is easier than ever 3-stages of a successful upgrade 49

50 Additional Material May 20, 2010

51 Upgrade Related APARs May 20, 2010

52 DB2 9.1 and DB2 9.5 Upgrade Specific APARs For the latest information on APARs relating to upgrading to DB2 9.1 from DB2 UDB V8.x please refer to For the latest information on APARs relating to upgrading to DB2 9.5 from DB2 UDB V8.x or DB2 9.1, please refer to 52

53 Additional Upgrade Resources and Information May 20, 2010

54 Additional DB2 9.5 Resources Information Center Documentation in PDF format Product Support developerworks Forum 54

55 The Upgrade Process 55

56 DB2 9 Successful Customer Upgrades Telecommunications Retail Financial Services Insurance Health Care Upgrade to DB2 9 is very very simple, only minutes. It s a no brainer folks; do it! DB2 LUW customer presentation, Information on Demand 2007 conference 56

57 DB2 9 Successful SAP Customer Upgrade INTER Versicherungen INTER upgraded its SAP DB2 environment to IBM DB2 9 on its existing IBM System p 650 platform. The company has exploited new features of DB2 9 like self-tuning memory management (STMM) and data compression technologies, which are fully supported by the SAP software Public customer case study ibm.com/software/success/cssdb.nsf/CS/STRD6Z2KE3?OpenDocument&Si te=gicss67sap&cty=en_us 57

58 Enabling New Features May 20, 2010

59 Enabling New Features Converting an existing tablespace to large record identifiers (RIDs) Enabling data row compression on an existing table Enabling the Self-Tuning Memory Manager Converting a Union All View to a data partitioned table 59

60 Converting to Large Record Identifiers (RIDs) Convert DMS table spaces only using ALTER TABLESPACE CONVERT TO LARGE COMMIT Increase the table space s storage capacity If auto-resize enabled, increase the MAXSIZE attribute Otherwise Enable auto-resize (ALTER TABLESPACE AUTORESIZE YES) or Add more storage (add stripe set, extend container, etc.) Increase log space, memory, and system temporary table space b2.udb.rn.doc/doc/c htm 60

61 Converting to Large Record Identifiers (RIDs) (cont.) To support large RIDs, indexes on tables in a converted table space must be reorganized or rebuilt Use REORG INDEXES ALL (without CLEANUP ONLY) Specify ALLOW NO ACCESS option for partitioned tables To support >255 rows per page, tables must be reorganized Cannot use INPLACE Reorganization will rebuild all indexes Automatically converts Type 1 indexes to Type 2 Use RUNSTATS after reorganizing the tables 61

62 Convert Type-1 Indexes to Type-2 Indexes in Upgraded Databases Convert type-1 indexes to take advantage of type-2 index benefits Improved concurrency Online table reorganization and online table load commands can be used against the table XML columns allowed only on tables with type-2 indexes Type-1 indexes are deprecated since DB2 9.1; you should convert them before they are no longer supported Further details can be found here b2.luw.qb.migration.doc/doc/t html 62

63 Enabling Data Row Compression ALTER TABLE COMPRESS YES Use INSPECT command to estimate the compression savings Ways to build the compression dictionary INSPECT ROWCOMPESTIMATE always builds the dictionary It is only inserted into the table if compression is enabled Offline REORG TABLE builds the dictionary and compresses the existing data 63

64 Enabling Data Row Compression (cont.) Time saving alternatives to performing a table reorg on a large table Alternative #1 Unload & reload Enable compression on the table Use INSPECT ROWCOMPESTIMATE to build the dictionary Unload the existing data Reload the data Alternative #2 Small data set Unload the existing data Load a small representative data set Enable compression on the table Reorg the table to build the dictionary and compress the small data set Load the remaining data Do not forget automatic dictionary creation too! 64

65 Enabling the Self-Tuning Memory Manager STMM trades memory between different memory areas Two or more areas must be tunable An area is tunable if the configuration parameter is AUTOMATIC To tune the buffer pool, its size must be set to AUTOMATIC Approaches to enabling STMM Manual enablement Set the self_tuning_mem DB parameter to ON Set two (or more) memory area configuration parameters to AUTOMATIC Use the Configuration Advisor. It will enable STMM AUTOCONFIGURE APPLY NONE will generate recommendations Review the recommendations and apply as necessary Complete details at ic=/com.ibm.db2.luw.admin.perf.doc/doc/t html 65

66 From Union All View to Data Partitioned Table Create an empty data partitioned table with one dummy range Avoid creating any indexes (yet) Attach the existing arms of the Union All View one by one ALTER TABLE ATTACH PARTITION Drop the dummy range using ALTER TABLE DETACH PARTITION DROP TABLE Set up any constraints and MQTs 66

67 From Union All View to Data Partitioned Table (cont.) Run SET INTEGRITY Create indexes on the data partitioned table as necessary Other approaches to upgrading existing tables and views to partitioned tables =/com.ibm.db2.luw.admin.partition.doc/doc/t html 67