How to use this upgrade guide



IBM PureData System for Operational Analytics V1.1Upgrading to DB2 Advanced Enterprise Server Edition V11.1Contents TOC \o "1-3" \h \z \u How to use this upgrade guide PAGEREF _Toc523324995 \h 3Change History PAGEREF _Toc523324996 \h 4Introduction PAGEREF _Toc523324997 \h 5What is included in the upgrade? PAGEREF _Toc523324998 \h 5Which editions are validated for the upgrade? PAGEREF _Toc523324999 \h 5High Level Steps PAGEREF _Toc523325000 \h 6Important Notes about the upgrade? PAGEREF _Toc523325001 \h 7DB2 11.1 PAGEREF _Toc523325002 \h 7AIX must be at 7.1 TL3 SP5 or higher. PAGEREF _Toc523325003 \h 9IBM XLC Runtime must be at 13.1.3.1 or higher. PAGEREF _Toc523325004 \h 9DB2 Warehouse and de-branded interfaces. PAGEREF _Toc523325005 \h 9Is it necessary to update DB2 Warehouse? PAGEREF _Toc523325006 \h 10Impact on future IBM PureData System for Operational Analytics fixpacks. PAGEREF _Toc523325007 \h 10Downloading and staging all the requisite software. PAGEREF _Toc523325008 \h 11Staging PAGEREF _Toc523325009 \h 13Image File Staging Area PAGEREF _Toc523325010 \h 13IBM XLC Runtime [ PDOA V1.1.0.0/V1.1.0.1 Customers Only. V1.1.0.1 IF01 or higher customers may skip this step. ] PAGEREF _Toc523325011 \h 13IBM? DB2? Advanced Enterprise Server Edition Server - PVU PAGEREF _Toc523325012 \h 14IBM PureData System for Operational Analytics A1801 with DB2 11.1 - Activation PAGEREF _Toc523325013 \h 15Creating Response Files PAGEREF _Toc523325014 \h 16DB2 V11.1 Server Copy RSP File PAGEREF _Toc523325015 \h 17Backup Up Your Database PAGEREF _Toc523325016 \h 18Backup Recommendations PAGEREF _Toc523325017 \h 18Verifying your system is healthy PAGEREF _Toc523325018 \h 19Update xlC runtime. [ PDOA V1.1.0.1+IF01 customers can skip this step.] PAGEREF _Toc523325019 \h 20Installing DB2 V11.1 on the core hosts PAGEREF _Toc523325020 \h 22Installing DB2 V11.1 Server Copies On the core hosts. PAGEREF _Toc523325021 \h 22Migrating the core instance to DB2 V11.1 PAGEREF _Toc523325022 \h 25Remove the DB2 10.5 copies. PAGEREF _Toc523325023 \h 32How to use this upgrade guideThis guide is provided as a convenience document for you to upgrade the DB2? software to Version 11.1 and the warehouse tools software to Version 11.1 on an IBM? PureData? System for Operational Analytics environment.This guide is available via the URL . Change HistoryDateChange Description2016-10-01Initial Draft2016-10-27OPM does not support DB2 V11.1 instances to use for the performance database. Management hosts will continue to use DB2 10.5 until OPM is removed. Updating document to remove management node updates to DB2 V11.1.Updated filename for the IBM PureData System for Operational Analytics Activation CD2016-11-16Updated typos where BCUGLSALL was used in place of BCUDB2ALL.Updated some typos.Added removal topic for DB2 V10.5.2016-12-16Updated typos in Introduction.Updated download section with some clarifying statements.Update order of backups.2017-03-24Updates include some examples from DB2 V11.1.1.1.Updates AIX updates with the 2 DSH commands to apply the bos.install.rte update and then to run the rest of the update in the background.Added more information about DB2 Instance and Database MigrationAdded missing instructions for removing the DB2 Warehouse 10.5 installation copies.2018-08-15Updated document to account for post V1.1.0.1 and IF01 upgrades.Introduction What is included in the upgrade?At the end of this upgrade procedure, the IBM PureData System for Operational Analytics environment will be upgraded to DB2 Advanced Enterprise Server Edition Version 11.1. The database instances supporting warehouse tools (dweadmin), database performance monitor (db2opm) and the IBM PureData System for Operational Analytics console (db2psc) will not be migrated to DB2 V11.1. This is due to an issue with OPM that does not support using DB2 V11.1 instance to contain the performance database.Which editions are validated for the upgrade?IBM PureData System for Operational Analytics V1.1 customers are allowed to upgrade. IBM PureData System for Operational Analytics V1.0 customers should contact IBM for eligibility and also must be on IBM PureData System for Operational Analytics V1.0.0.5 or higher.Customers are encouraged to update the appliance level to V1.1.0.1 and apply IF01 (Interim Fix 01) prior to upgrading to DB2 11.1. This updates the AIX level to 7.1 TL5 as AIX 7.1 TL3 is now end of fixpack support.This removes IBM Systems Director which is end of support since April 2018.V1.0 customers who have upgraded from DB2 10.1 to DB2 10.5 experienced some unexpected issues with fixpack 5 when they had mixed DB2 and Infosphere Warehouse (Warehouse Tools) levels. Updating to V1.1.0.1 before the upgrade will avoid the same scenario with this DB2 upgrade.After updating to IF01 (Interim Fix 01) it is no longer necessary to update Warehouse Tools or to re-install intelligent miner on DB2 V11.1.High Level StepsReview this document completely as well as the Knowledge Center links listed in Table 1.Downloading and staging all the requisite software.Creating Response FilesBack up your system.Verifying your system is healthy.Upgrading the xlC runtime levels.Installing DB2 V11.1 on the core hosts.Migrating the core instance to DB2 V11.1Migrating the core database to DB2 V11.1Important Notes about the upgrade?DB2 11.1 DocumentationPrior to this upgrade it is recommended to review the DB2 documentation regarding best practices, important changes in behavior, and pre-update steps. The following table has a sampling of important links in the Knowledge Center related to those topics.Links to important DB2 V11.1 TopicsTopicLinkNew Features’s Changed to DB2 V11.1 Essential For DB2 Servers Restrictions for DB2 Servers Practices for upgrading DB2 Servers server behavior changes Organized TablesColumn Organized Tables are now supported for DB2 DFP environments.The default table organization will be to use row based organization even after migration. Customers who want to take advantage of column organized tables will need to make some significant changes to database environment variables, instance configuration and database configurations. Making these changes could impact the existing row based performance adversely, so careful planning is required to further utilize the column organization or Blu features, primarily using test environments. The changes to add column-organized tables to an IBM PureData System for Operational Analytics environment are beyond the scope of this document.External TablesExternal Tables are a new feature in DB2 V11.1, however this feature has not been tested for compatibility with the appliance’s hardware or high availability design. AIX must be at 7.1 TL3 SP5 or higher.PDOA Customers must be at PDOA V1.1.0.1 or higher to meet the AIX requirement for DB2 V11.1. All customers however are heavily encouraged to be at V1.1.0.1 IF01 or higher as this updates AIX beyond the 7.1 TL3 level which went end of fixpack support at the end of 2017.IBM XLC Runtime must be at 13.1.3.1 or higher.PDOA Customers using V1.1.0.1 will need to update the XLC level.PDOA Customers using V1.1.0.1 IF01 or higher will meet this requirement as part of that update.DB2 Warehouse and de-branded interfaces.DB2 Warehouse is known as Warehouse Tools in the appliance and does not support the de-branded interfaces in version 11.1. Therefore, the documentation related to Warehouse Tools in the IBM PureData System for Operational Analytics may show different text on panels that exposes the DB2 Warehouse vocabulary instead of the de-branded vocabulary. This will not affect the function of those tools.UPDATE:Warehouse Tools has been deprecated and will be removed in the V1.0.0.6 and V1.1.0.2 fixpacks. It is no longer necessary or recommended to update Warehouse Tools as part of this update.Is it necessary to update DB2 Warehouse? Customers who are still using the V1.1.0.0 GA level should apply V1.1.0.1 prior to upgrading their appliance to DB2 V11.1. This is recommended to avoid potential issues with the application of PDOA V1.1.0.1 (FP1). Since this document was originally produced the Warehouse Tools component of the appliance is being removed as part of the fixpack V1.1.0.2. Customers on V1.1.0.1 or V1.1.0.1 w/ IF01 will not be required to update the Warehouse Tools component of PDOA to the corresponding DB2 V11.1 level of DB2 Warehouse.Impact on future IBM PureData System for Operational Analytics fixpacks.PDOA V1.1.0.1 (FP1) was released on April 2017. It did not include any updates for DB2 11.1.PDOA V1.1.0.1 IF01 (Interim Fix 01) was released in April 2018. This fixpack did not include updates for DB2 V11.1.PDOA V1.1.0.2 (FP2) will include a DB2 V11.1 update. 11.1.3.3b.Database Performance Manager (DPM)DPM is the debranded name for Optim Performance Managemer (OPM) which is shipped with all PDOA appliances. There are some important restrictions that OPM imposes as part of this upgrade in the appliance.OPM does not support DB2 V11.1 for its performance database. OPM does not officially support DB2 V11.1 as a target database outside of this appliance. It will tolerate DB2 V11.1 but it is not updated or optimized to work with DB2 V11.1. The official IBM replacement for OPM is IBM Data Server Manager (DSM). While DSM is not currently allowed (without a CCB request) to exist on the appliance, it is allowed to use DSM from a remote server to take the place of OPM. Currently the appliance authors are not aware of any migration from OPM to DSM. DSM documentation is available at this link.OPM’s WLM editor feature will no longer work to manage WLM on DB2 V11.1 databases. One possible replacement of this feature is the IBM Graphical Workload Management (GWLM) Tool available from developer works at this link.Downloading and staging all the requisite software.Downloading the software and accessing instructions. The following images were used to generate these instructions. Over time newer images will be released. Table 2 Required downloadsOperating System ImagesPDOA V1.1.0.0 CustomersWhile AIX can be updated to 7.1 TL3 SP6 or SP7 manually, it is highly recommended to apply PDOA V1.1.0.1 and then to apply PDOA V1.1.0.1 IF01 before updating DB2.Customers at V1.1.0.1 will meet the OS requirement but must apply the XL C/C++ Runtime update.Customers at IF01 meet all OS and XL C /C++ Pre-requisites to DB2 V11.1.IBM XL C/C++ Runtime for AIX 13.1.2 (Minimum Level)XL C/C++ Runtime for AIX Fix Pack 1 (March 2016 PTF) for 13.1.3File: 13.1.3.1-IBM-xlC-AIX-FP001.tar.ZDB2 11.1 for Linux, UNIX, and Windows Advanced Enterprise Server EditionIBM? DB2? Advanced Enterprise Server Edition Server - PVUDB2 Fixpack Download LinkFile: DB2_AESE_PVU_11.1_Server_aix.tgzUPDATE: PDOA has tested DB2 V11.1 FP1 for migration.v11.1.1fp1_aix64_server_t.tar.gzPDOA V1.1.0.2 DB2 V11.1 Fixpack Level of DB2v11.1.3fp3b_aix64_universal_fixpack.tar.gzIBM PureData System for Operational Analytics A1801 with DB2 11.1 - ActivationFile: PureData_Analytics_A1801_11.1_Activa.zipPassport Advantage Label: IBM PureData System for Operational Analytics A1801 v1.1 with DB2 11.1 - Activation Multiplatform Multilingual CNG6KML ~ 2mb. "Table 3 download descriptionsOperating System ImagesIBM XL C/C++ Runtime for AIX 13.1.2 or higherThis is a minimum requirement DB2 V11.1.DB2 11.1 for Linux, UNIX, and Windows Advanced Enterprise Server EditionIBM? DB2? Advanced Enterprise Server Edition Server - PVURetrieved from Passport Advantage. May also retrieve the AIX 64 bit server fixpack.DB2 IBM? DB2? Warehouse ServerRetrieved from Passport Advantage.IBM PureData System for Operational Analytics A1801 with DB2 11.1 - ActivationRetrieved from Passport AdvantageStagingImage File Staging AreaCreate the directory structure on /stage. This will be the base location for the uplift images. This will be located on the management node. Verify that the ‘/stage’ filesystem is mounted and has adequate space. The ‘/stage’ filesystem is available on all hosts in the environment via GPFS.mkdir /stage/blue_upliftIBM XLC Runtime [ PDOA V1.1.0.0/V1.1.0.1 Customers Only. V1.1.0.1 IF01 or higher customers may skip this step. ]To stage the xlC runtime update do the following.Create the directory /stage/blue_uplift/AIXmkdir -p /stage/blue_uplift/AIXCopy the 13.1.3.1-IBM-xlC-AIX-FP001.tar.Z file to this location. It is not necessary to unpack at this time./stage/blue_uplift/AIXIf you have not done so already, create a new filesystem /usr/sys/inst.images on all hosts in the environment. The following commands will create the logical volume on rootvg with the requisite two copies with 10 GB of space. It then creates the filesystem on top of that logical volume and mounts the filesystem. dsh -n ${ALL} 'mklv -c 2 -L /usr/sys/inst.images -t jfs2 -y instimages rootvg 10'dsh -n ${ALL} 'crfs -v jfs2 -d /dev/instimages -m /usr/sys/inst.images -A yes -p rw'dsh -n ${ALL} 'mount /usr/sys/inst.images'Create the new location in /usr/sys/inst.imagesdsh -n ${ALL} 'mkdir /usr/sys/inst.images/13.1.3.1-IBM-xlC-AIX-FP001'Unpack the XLC updates to /usr/sys/inst.images.dsh -n ${ALL} 'cd /usr/sys/inst.images/13.1.3.1-IBM-xlC-AIX-FP001;uncompress < /stage/blue_uplift/AIX/13.1.3.1-IBM-xlC-AIX-FP001.tar.Z | tar -xf -'Check the number of files extracted.dsh -n ${ALL} 'find /usr/sys/inst.images/13.1.3.1-IBM-xlC-AIX-FP001 | wc -l'hostname01: 23hostname02: 23hostname03: 23hostname04: 23hostname05: 23hostname06: 23hostname07: 23IBM? DB2? Advanced Enterprise Server Edition Server - PVU The DB2 software can be staged on the /stage filesystem. Create the directory /stage/blue_uplift/DB2 on the management host.mkdir /stage/blue_uplift/DB2Copy the file ‘v11.1.3fp3b_aix64_universal_fixpack.tar.gz’ this directory.Unpack the file.cd /stage/blue_uplift/DB2gzip -d < v11.1.3fp3b_aix64_universal_fixpack.tar.gz | tar -xvf -Verify the number of files in the universal directory using the find command to list out all directories and files and the wc command to count the number of lines. This may vary if a fixpack image was used. Below shows the output for V11.1 Mod 3 FP3b.$ find universal | wc -l 1210IBM PureData System for Operational Analytics A1801 with DB2 11.1 - ActivationThis Activation CD is required to apply the DB2 V11.1 AESE license to all of the DB2 V11.1 copies that will be installed in the environment. The PureData System for Operational Analytics activation cd contains the same license file in the DB2 V11.1 Advanced Enterprise Server Edition PVU license with specific license terms.Create the directory /stage/blue_uplift/activationCopy the activation zip image to /stage/blue_uplift/activationUnpack the imagecd /stage/blue_uplift/activationjar -xvf PureData_Analytics_A1801_11.1_Activa.zipVerify the extraction:$ find PDS | wc -l 48Verify the following files and directories were extracted:$ ls PDS/warehouse/LA db2aese_c.lic profile.rsp redist.txt tags warehouse_prereq_client.xml warehouse_prereq_server.xmlCreating Response FilesThe PDOA installation model for DB2 uses the db2setup command and response files. This is important to control some of the default behaviors when using the installdb2 command which are not always compatible with PDOA environments.Create the response files directory.mkdir -p /stage/blue_uplift/rspfilesDB2 V11.1 Server Copy RSP FileThe file variable below has been updated to reflect the VRMF, interim fix and special build properties of the DB2 version being installed which is 11.1 Mod 3 FP3 Interim b. All the other variables are consistent with the PDOA model to install DB2 copies for DB2 V11.1. ======= RSP FILE START /stage/blue_uplift/rspfiles/db2aese_addpart.rsp ===========*-----------------------------------------------------* Generated response file used by the DB2 Setup wizard* generation time: 8/20/09 3:40 PM*-----------------------------------------------------* Product InstallationLIC_AGREEMENT = ACCEPTPROD = DB2_SERVER_EDITIONFILE = /usr/IBM/dwe/db2/V11.1.3.3.b.0INSTALL_TYPE = CUSTOMCOMP = APPLICATION_DEVELOPMENT_TOOLSCOMP = DB2_UPDATE_SERVICECOMP = COMMUNICATION_SUPPORT_TCPIPCOMP = JDKCOMP = JAVA_SUPPORTCOMP = FIRST_STEPSCOMP = BASE_DB2_ENGINECOMP = REPL_CLIENTCOMP = LDAP_EXPLOITATIONCOMP = INSTANCE_SETUP_SUPPORTCOMP = DB2_SAMPLE_DATABASECOMP = SQL_PROCEDURESCOMP = DB2_DATA_SOURCE_SUPPORTCOMP = INFORMIX_DATA_SOURCE_SUPPORTCOMP = BASE_CLIENTCOMP = CONNECT_SUPPORTCOMP = ORACLE_DATA_SOURCE_SUPPORTCOMP = SPATIAL_EXTENDER_CLIENT_SUPPORTCOMP = SPATIAL_EXTENDER_SERVER_SUPPORTCOMP = SQL_SERVER_DATA_SOURCE_SUPPORTCOMP = ODBC_DATA_SOURCE_SUPPORTCOMP = SYBASE_DATA_SOURCE_SUPPORTCOMP = TERADATA_DATA_SOURCE_SUPPORTCOMP = JDBC_DATA_SOURCE_SUPPORTCOMP = ORACLE_DATA_SOURCE_SUPPORT*-----------------------------------------------* Installed Languages*-----------------------------------------------LANG = ESLANG = CNLANG = JPLANG = DELANG = ITLANG = PLLANG = ENLANG = KRLANG = TWLANG = CZLANG = FRLANG = RULANG = BR*-----------------------------------------------* SA MP Base Component*-----------------------------------------------INSTALL_TSAMP = NO================ RSP FILE END ==================Backup Up Your DatabaseBackup RecommendationsBackup the core instance settings, core instance configuration and core instance database configuration and instance owner’s profile.env file. These will be used for comparison later. Login to the admin node as the instance owner. Determine the admin host using ‘hals’.$ hals -core | grep '0-5'| 0-5 | pdoa102 | pdoa104 | bcudomain01 | Online | Normal | - |db2set > db2set_v10.5.outdb2 get dbm cfg > db2dbmcfg_v10.5.outdb2 get db cfg for bcudb > db2dbcfg_v10.5.outcp ~/sqllib/profile.env ~/sqllib/profile.env.$(date +%s)Backup the core database using appropriate backup procedures. If it is necessary to revert to a previous database version.Verifying your system is healthyOther checks. If there are any questions regarding the findings in these or other areas of the system contact IBM support.Login to the HMC and look for any hardware alerts in the system.Examine the errpt for any recurring hardware issues. Update xlC runtime. [ PDOA V1.1.0.1+IF01 customers can skip this step.]With all of the hosts started perform the following steps.Login to the management host as root.Verify /stage is mounted on the management host. If not mount /stage on the management host.Create a log directory to contain the hostname.log files.mkdir /stage/blue_uplift/xlcupdateRun the following command which will create a log file in /stage/blue_uplift/xlcupdate for each host as well as print all output to stdout and stderr.dsh -F /stage/blue_uplift/xlcupdate -n ${ALL} "install_all_updates -xYvcd /usr/sys/inst.images/13.1.3.1-IBM-xlC-AIX-FP001" 2>&1 | dshbak -c Check the logs to verify that all updates were successful.Installing DB2 V11.1 on the core hostsInstalling DB2 V11.1 Server Copies On the core hosts.Follow the guidelines for staging the DB2 image and the DB2 V11.1 Server Copy RSP File earlier in the guide.Installation notes.This installation method will install a new copy of DB2 V11.1 on each of the core hosts. This installation method will not stop any instances, migrate any instances, stop any databases or migrate any databases.This installation will update files in /usr/sbin/rsct/sapolicies/db2, however the IBM PureData System for Operational Analytics ha policies are not impacted as they follow a different naming convention.Pay close attention to the command lines which make reference to paths. The paths may be different depending on the version of DB2 used to run the install.Verify that the stage filesystem is mounted on all the hosts.Run the following command as root on the management host to install the new copy on all core hosts. Note this is a one line command and the use of single quotes required. Installation should take approximately 10 minutes on each host.dsh -n ${BCUDB2ALL} '/stage/blue_uplift/DB2/universal/db2setup -l /stage/blue_uplift/$(hostname)_V11.1_db2setup.log -r /stage/blue_uplift/rspfiles/db2aese_addpart.rsp'Verify the *db2setup.log files for each host to look for errors.Verify the installation paths. The example below shows DB2 V11.1.1.1 and a path to match. There should be two paths, one for DB2 V10.5 and one for DB2 V11.1.$ dsh -n ${BCUDB2ALL} '/usr/local/bin/db2ls -c | cut -d: -f 1,2' | dshbak -c HOSTS -------------------------------------------------------------------------host02, host04-------------------------------------------------------------------------------#PATH:VRMF/usr/IBM/dwe/db2/V10.5.0.5..1:10.5.0.5/usr/IBM/dwe/db2/V11.1.1.1..0:11.1.1.1Verify the new copy is on all the hosts. Use the path listed for DB2 V11.1 above. There should be. dsh -n ${BCUDB2ALL} /usr/local/bin/db2ls -p -q -b /usr/IBM/dwe/db2/V11.1.3.3.b.0 2>&1 | dshbak -cApply the appropriate license to each db2 copy from the activation cd.dsh -n ${BCUDB2ALL} '/usr/IBM/dwe/db2/V11.1.3.3.b.0/adm/db2licm -a /stage/blue_uplift/activation/PDS/warehouse/db2aese_c.lic'Verify the license was applied to each copy on all of the core nodes.$ dsh -n ${BCUDB2ALL} '/usr/IBM/dwe/db2/V11.1.3.3.b.0/adm/db2licm -l' 2>&1 | dshbak -cHOSTS -------------------------------------------------------------------------host01, host02, host03-------------------------------------------------------------------------------Product name:???????????????????? "DB2 Advanced Enterprise Server Edition"License type:???????????????????? "CPU Option"Expiry date:????????????????????? "Permanent"Product identifier:?????????????? "db2aese"Version information:????????????? "11.1"Enforcement policy:?????????????? "Soft Stop"Migrating the core instance to DB2 V11.1This step will require taking an outage to the core warehouse. Note that the V1.1 level of the appliance does not configure the DB2 Administration Server instances on the core hosts. If the DAS was created after deployment then it too will need to be migrated before the old DB2 copy can be removed. See the DB2 Knowledge Center for information regarding DAS migration if necessary. It is recommended to review the DB2 Knowledge Center topic called ‘Upgrade Db2 Servers’ for more information about upgrading DB2 from version 10.5 to 11.1.Stopping the servicesStop all applications accessing the core database.Stop the IBM PureData System for Operational Analytics services managed by Tivoli System Automation (TSA)Login to the management host as root.hastopapphastopdpmVerify with ‘hals’ that all management applications are offline.Migrating the instanceSee the following Knowledge Center documentation regarding instance migration with db2iupgrade: the current host associated with partition 0 in db2nodes.cfg. An example follows where the instance owner is bcuaix. It shows that ‘host02’ is associated with partition 0 and is the instance owning partition.$ head -1 /db2home/bcuaix/sqllib/db2nodes.cfg 0 host02 0Deactivate all databases in the instance. The database must be deactivated in order to check that the database can be upgraded.Login as the instance owner on the coordinator (admin) host.Run the db2ckupgrade command associated with the new DB2 11.1 copy./usr/IBM/dwe/db2/V11.1.3.3.b.0/bin/db2ckupgrade -e -allChecks -l db2ckupgrade_$(date +%s).logOutput. The following output indicates it is possible to proceed.DBT5508I The db2ckupgrade utility completed successfully. The database or databases can be upgraded.The following output indicates a problem.DBT5529N The db2ckupgrade utility did not complete successfully. The database cannot be upgraded. The output log file is named "db2ckupgrade_1490402442.log".Examine the log. The following indicates the database was not deactivated at the time of invocation. There may be other indicators as well.DBT5549N No upgrade verification tests were performed because the db2ckupgrade utility failed to get an exclusive database connection.Exit the instance owner session. Login as root on the admin host.Deactivate the database. Do this to ensure the database is cleanly stopped before running hastopdb2.Stop the instance.hastopdb2Put the domain in manual mode.hadomain -core manualRun the following as the root user on the current administration host. Replace bcuaix with the core warehouse instance owner and the path with the appropriate db2 copy path.cd /usr/IBM/dwe/db2/V11.1.3.3.b.0/instance./db2iupgrade bcuaixDBI1446I? The db2iupgrade command is running.DB2 installation is being initialized.Total number of tasks to be performed: 4Total estimated time for all tasks to be performed: 309 second(s)Task #1 startDescription: Setting default global profile registry variablesEstimated time 1 second(s)Task #1 endTask #2 startDescription: Initializing instance listEstimated time 5 second(s)Task #2 endTask #3 startDescription: Configuring DB2 instancesEstimated time 300 second(s)Task #3 endTask #4 startDescription: Updating global profile registryEstimated time 3 second(s)Task #4 endThe execution completed successfully.For more information see the DB2 installation log at"/tmp/db2iupgrade.log.3670766".DBI1070I? Program db2iupgrade completed successfully.Backup the profile.env file in the sqllib directory. In later steps it is possible for this file to be removed. This step is necessary to ensure that the db2 environment variables are not lost.Login as the instance owner for the core warehouse instance on the admin node.cp ~/sqllib/profile.env ~/sqllib/profile.env.$(date +%s)In a root session. Restore the core domain to automatic mode.hadomain -core autoCheck the instance settings on all nodes. Replace bcuaix with the core warehouse instance owner. This will show the instance records for all the hosts in the core warehouse. The db2iupgrade may not update all the instance records to reflect the instance migration. For any host that is not updated, remove the existing relationship and add back the new relationship as part of the next step. Verfiy the installation path matches what was used in the RSP file. The example below shows a different version and installation path.$ dsh -n ${BCUDB2ALL} 'su - bcuaix -c "db2greg -dump" | grep "^I"' | dshbak -cHOSTS -------------------------------------------------------------------------hostname05, hostname06, hostname07-------------------------------------------------------------------------------I,DB2,11.1.0.0,bcuaix,/db2home/bcuaix/sqllib,,1,0,/usr/IBM/dwe/db2/V11.1.0.0..0,,Handling incorrect or missing instance records.Removing the previous instance relationship on a host that is not correct. Replace host1,host2 with the comma separate list of hosts with incorrect values. Replace /usr/IBM/dwe/db2/V10.5.0.5..1/ with the previous path. Using the ‘-di’ option should preserve the ~bcuaix/sqllib/profile.env file. In previous document versions using ‘-d’ would remove the profile.env file unnecessarily.dsh -n host1,host2 '/usr/IBM/dwe/db2/V10.5.0.5..1/instance/db2iset -di bcuaix'Rerun the db2greg check. This should reveal that the instance record is either missing or is correct.For hosts with a missing entry run the following.dsh -n host1,host2 /usr/IBM/dwe/db2/V11.1.3.3.b.0/instance/db2iset -a bcuaixRerun the db2greg check. All core hosts should be represented now.Run the following check for the current db2 copy. Any hosts that are missing the instance owner’s name should be addressed.dsh -n ${BCUDB2ALL} 'echo 1;/usr/IBM/dwe/db2/V11.1.3.3.b.0/instance/db2iset -l' 2>&1 | dshbak -cHOSTS -------------------------------------------------------------------------hostname05, hostname06, hostname07-------------------------------------------------------------------------------1bcuaixVerify that the ~/sqllib/profile.env still exists. If not, restore the file from backup make in step b above. If the profile.env file does not exist the database instance will not start. Restore the file using the bcuaix instance owner account to ensure the file permissions are correct.Migrating the databaseStart the instance. As root on management run.hastartdb2Verify that the database instance has started with hals.Migrate the database. Login as the instance owner on the admin host.$ db2 upgrade database bcudbDB20000I? The UPGRADE DATABASE command completed successfully.Verify that the database works as expected and consider backing up the database.Obtain the db2set, db2 dbm and db parameters after migration.db2set > db2set_v11.1.outdb2 get dbm cfg > db2dbmcfg_v11.1.outdb2 get db cfg for bcudb > db2dbcfg_v11.1.outCompare db2set, db2 dbm and db parameters with the previous settings that were checked during the backup. The following shows an example comparison of an uplift that takes place after an initial appliance deployment to DB2 V11.1.1.1.DB2 set$ diff db2set_v11.1.out db2set_v10.5.out1d0< DB2_DATABASE_CF_MEMORY=100DB2 dbm$ diff db2dbmcfg_v11.1.out db2dbmcfg_v10.5.out6c6< Database manager configuration release level = 0x1400---> Database manager configuration release level = 0x100064,65c64,65< Global instance memory (% or 4KB) (INSTANCE_MEMORY) = AUTOMATIC(7339369)< Member instance memory (% or 4KB) = GLOBAL---> Global instance memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC(7339369)> Member instance memory (4KB) = GLOBAL113,116c113,115< Number of FCM buffers (FCM_NUM_BUFFERS) = AUTOMATIC(16384)< FCM buffer size (FCM_BUFFER_SIZE) = 4096< Number of FCM channels (FCM_NUM_CHANNELS) = AUTOMATIC(2048)< FCM parallelism (FCM_PARALLELISM) = 1---> No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = AUTOMATIC(16384)> No. of int. communication channels (FCM_NUM_CHANNELS) = AUTOMATIC(2048)> Inter-node comm. parallelism (FCM_PARALLELISM) = 1129,130c128,129< Current effective arch level (CUR_EFF_ARCH_LVL) = V:11 R:1 M:1 F:1 I:0 SB:0< Current effective code level (CUR_EFF_CODE_LVL) = V:11 R:1 M:1 F:1 I:0 SB:0---> Current effective arch level (CUR_EFF_ARCH_LVL) = V:10 R:5 M:0 F:5 I:0 SB:0> Current effective code level (CUR_EFF_CODE_LVL) = V:10 R:5 M:0 F:5 I:0 SB:33706DB2 DB$ diff db2dbcfg_v11.1.out db2dbcfg_v10.5.out4,5c4,5< Database configuration release level = 0x1400< Database release level = 0x1400---> Database configuration release level = 0x1000> Database release level = 0x100035c35< All committed transactions have been written to disk = YES---> All committed transactions have been written to disk = NO39,40d38< Upgrade pending = NO<47c45< Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC(2173600)---> Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC(2167040)148a147> WLM Collection Interval (minutes) (WLM_COLLECT_INT) = 20173,174d171< Strict I/O for EXTBL_LOCATION (EXTBL_STRICT_IO) = NO< Allowed paths for external tables (EXTBL_LOCATION) = /db2home/bcuaix182,188d178<< WLM Collection Interval (minutes) (WLM_COLLECT_INT) = 20< Target agent load per CPU core (WLM_AGENT_LOAD_TRGT) = AUTOMATIC(17)< WLM admission control enabled (WLM_ADMISSION_CTRL) = NO< Allocated share of CPU resources (WLM_CPU_SHARES) = 1000< CPU share behavior (hard/soft) (WLM_CPU_SHARE_MODE) = HARD< Maximum allowable CPU utilization (%) (WLM_CPU_LIMIT) = 0190,191d179< Procedural language stack trace (PL_STACK_TRACE) = NONE< HADR SSL certificate label (HADR_SSL_LABEL) =After database migration refer to the Post-upgrade tasks link in the DB2 Knowledge Center as it will be necessary to migrate explain tables and perform various rebind steps. The following steps were required as part of the internal testing.Revalidated and rebind objects. db2rbind should return without any errors.db2 connect to bcudbdb2 "CALL SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS(NULL, NULL, NULL)"db2 connect resetdb2rbind bcudb -l ~/db2rbind_$(date +%s).logMigrate Explain Tables.db2exmig -d bcudb -e BCUAIX | db2exmig -d bcudb -e SYSTOOLS$ db2exmig -d bcudb -e BCUAIXDB2 Universal Database Version 11.1, 5622-044 (c) Copyright IBM Corp. 1999, 2015Licensed Material - Program Property of IBMIBM DATABASE 2 Explain Table Migration ToolConnecting to the Database.Connect to Database Successful.Binding package - Bind was SuccessfulMigrating Explain Tables from v10.2 or later to current release.Found table BCUAIX.EXPLAIN_INSTANCE. No changes required for this migration.Found table BCUAIX.EXPLAIN_STATEMENT. No changes required for this migration.Found table BCUAIX.EXPLAIN_ARGUMENT. No changes required for this migration.Found table BCUAIX.EXPLAIN_OBJECT. No changes required for this migration.Found table BCUAIX.EXPLAIN_OPERATOR. No changes required for this migration.Found table BCUAIX.EXPLAIN_PREDICATE. No changes required for this migration.Found table BCUAIX.EXPLAIN_STREAM. No changes required for this migration.Found table BCUAIX.EXPLAIN_DIAGNOSTIC. No changes required for this migration.Found table BCUAIX.EXPLAIN_DIAGNOSTIC_DATA. No changes required for this migration.Found table BCUAIX.EXPLAIN_ACTUALS. No changes required for this migration.Examining the columns for table BCUAIX.OBJECT_METRICSFound table BCUAIX.ADVISE_INSTANCE. No changes required for this migration.Found table BCUAIX.ADVISE_INDEX. No changes required for this migration.Found table BCUAIX.ADVISE_WORKLOAD. No changes required for this migration.Found table BCUAIX.ADVISE_MQT. No changes required for this migration.Found table BCUAIX.ADVISE_PARTITION. No changes required for this migration.Found table BCUAIX.ADVISE_TABLE. No changes required for this migration.Found all tables OK. Start migration.Altering Explain table BCUAIX.OBJECT_METRICSMigration of the explain tables to Version 11.01.1 format has succeeded.Check the db2 fault monitor. This is enabled after a fixpack install. Below eamples show DB2 10.5, your system may vary.$ dsh -n ${BCUDB2ALL} 'grep db2 /etc/inittab'kf5hostname02: fmc:2:respawn:/usr/IBM/dwe/db2/V10.5.0.8..0/bin/db2fmcd #DB2 Fault Monitor Coordinatorkf5hostname06: fmc:2:respawn:/usr/IBM/dwe/db2/V10.5.0.8..0/bin/db2fmcd #DB2 Fault Monitor Coordinatorkf5hostname05: fmc:2:respawn:/usr/IBM/dwe/db2/V10.5.0.8..0/bin/db2fmcd #DB2 Fault Monitor Coordinatorkf5hostname07: fmc:2:respawn:/usr/IBM/dwe/db2/V10.5.0.8..0/bin/db2fmcd #DB2 Fault Monitor CoordinatorDisable the fault monitor on startup. Below example shows DB2 10.5 paths, update as appropriate.$ dsh -n ${BCUDB2ALL} "/usr/IBM/dwe/db2/V10.5.0.10..0/bin/db2fmcu -d" | dshbak -c Recheck. Output should be blank.$ dsh -n ${BCUDB2ALL} 'grep db2 /etc/inittab'Stop any fault monitor daemons that are currently running. Output shows DB2 10.5, update the db2 copy path as appropriate.$ dsh -n ${BCUDB2ALL} "/usr/IBM/dwe/db2/V10.5.0.10..0/bin/db2fm -i bcuaix -d" | dshbak -ckf5hostname02: /usr/IBM/dwe/db2/V10.5.0.10..0/bin/db2fm return non-zero rc, please see log file '/db2home/bcuaix/sqllib/db2dump/DIAG-0001/db2diag.log'kf5hostname06: /usr/IBM/dwe/db2/V10.5.0.10..0/bin/db2fm return non-zero rc, please see log file '/db2home/bcuaix/sqllib/db2dump/DIAG-0001/db2diag.log'kf5hostname04: ksh: 4326272 Killedkf5hostname07: ksh: 4980864 Killedkf5hostname05: /usr/IBM/dwe/db2/V10.5.0.10..0/bin/db2fm return non-zero rc, please see log file '/db2home/bcuaix/sqllib/db2dump/DIAG0016/db2diag.log'Backup the newly migrated database. Verify failover using the ‘hafailover’ command such that all core hosts will host database partitions.Remove the DB2 10.5 copies.The IBM PureData System for Operational Analytics environment can operate with multiple DB2 copies for a short time, however, prior to any appliance fixpack application only one DB2 copy is allowed on the core nodes and only two DB2 copies (one for System Director and one for the other components) are allowed on the management host and only one DB2 copy is allowed on the management standby host. Additional copies can lead to fixpack failures or other undesirable behaviors. Once the system is committed to moving to DB2 V11.1 then the previous copy can be removed. Please note that the only way to revert the database back to the 10.5 level is to restore the database from a DB2 V10.5 based backup. UPDATE: Customers who have upgraded their appliance to V1.0.0.5 or V1.1.0.1 or higher may continue to maintain multiple copies of DB2 due to changes in how future appliance fixpacks are applied. This step is therefore optional.Determine the db2 copy paths for DB2 10.5.$ dsh -n ${BCUDB2ALL} '/usr/local/bin/db2ls -c | cut -d: -f 1,2' | dshbak -cHOSTS -------------------------------------------------------------------------host02, host04-------------------------------------------------------------------------------#PATH:VRMF/usr/IBM/dwe/db2/V10.5.0.5..1:10.5.0.5/usr/IBM/dwe/db2/V11.1.1.1..0:11.1.1.1Determine the Warehouse copy paths for DB2 10.5.dsh -n ${BCUDB2ALL} 'grep dwe /usr/IBM/dwe/db2/V10.5.0.5..1/warehouse.ast' | dshbak -cHOSTS -------------------------------------------------------------------------host02, host04-------------------------------------------------------------------------------warehouse.installLocation=/usr/IBM/dwe/warehouse_10.5.0.5..1Verify that the database copy does not have any associated instances. This command should return no results.dsh -n ${BCUDB2ALL} '/usr/IBM/dwe/db2/V10.5.0.5..1/instance/db2ilist' | dshbak -cRun the Warehouse uninstaller associated with the old DB2 copy. Use the Warehouse path determined in b.dsh -n ${BCUDB2ALL} '/usr/IBM/dwe/warehouse_10.5.0.5..1/uninstall/uninstall'Verify the directory is empty except for logs.$ dsh -n ${BCUDB2ALL} 'ls -l /usr/IBM/dwe/warehouse_10.5*/' | dshbak -cHOSTS -------------------------------------------------------------------------host02, host04-------------------------------------------------------------------------------total 0drwxrwxr-x 2 root system 256 Mar 24 15:03 logsRun the DB2 uninstaller. Use the DB2 path found in b.dsh -n ${BCUDB2ALL} '/usr/IBM/dwe/db2/V10.5.0.5..1/install/db2_deinstall -a' | dshbak -cVerify the copy is uninstalled.$ dsh -n ${BCUDB2ALL} '/usr/local/bin/db2ls -c | cut -d: -f 1,2' | dshbak -cHOSTS -------------------------------------------------------------------------host02, host04-------------------------------------------------------------------------------#PATH:VRMF/usr/IBM/dwe/db2/V11.1.1.1..0:11.1.1.1 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download