StarQuest: keeping data in motion

 

StarQuest Technical Documents

Updating to Db2 11.5.7 & later

Last Update: 2 May 2022
Product: SQDR Plus
Version: 4.2 & later
Article ID: SQV00PL070

Abstract

In the four tier StarQuest Data Replication architecture, SQDR Plus runs on Tier 2 and uses a local IBM Db2 for Linux, UNIX & Windows (aka Db2 LUW) database as the control and staging database for each Staging Agent.

As of the time of this writing, StarQuest currently recommends using Db2 11.5.5fp1, as SQDR Plus ships with Db2 templates that were created by 11.5.5fp1.

However, later versions of Db2 (e.g. 11.5.7 and 11.5.7 special builds) can be used with SQDR Plus with the considerations and special actions noted below. Note that Db2 11.5.6 should not be used.

These instructions assume that the system is already running some version of Db2 11.5.x and thus there is no need to run the db2 upgrade database command. If you are upgrading from a version earlier than 11.5.0, see Updating to 11.5.5.

Solution

  • If you are performing a fresh installation of 11.5.7, be sure to change the TCP/IP port from 25000 to 50000 on the Configure DB2 Instances panel. See Installing Db2 LUW for details.
  • Run db2updv115 from a Db2 command window to update the system catalog of any existing control and staging databases. You do not need to stop Db2 operations or run this from an elevated command window.

db2updv115 -d SQDRP0
db2updv115 -d SQDRC
etc

  • Also run db2updv115 on any new staging databases created as part of creating a new agent, as these databases are created by restoring from backup images created on 11.5.5fp1. Note that you can avoid this step by specifying the use of an existing staging database when creating a new agent.

 

Failure to run db2updv115 may result in this message appearing in db2diag.log:

2021-12-12-16.43.09.036000-480 I1129379F1302 LEVEL: Severe
PID : 2620 TID : 6348 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQDRP0
APPHDL : 0-73 APPID: *LOCAL.DB2.211213004320
AUTHID : SQDR HOSTNAME: sqdrprod
EDUID : 6348 EDUNAME: db2pkgrb (SQDRP0) 0
FUNCTION: DB2 UDB, access plan manager, sqlraFindInvalidPackagesAndRebindThemFunc, probe:12988
DATA #1 : String, 24 bytes
Package failed to rebind
DATA #2 : Object Name, PD_TYPE_OBJECT_NAME, 10 bytes
P487540748
DATA #3 : Schema Name, PD_TYPE_SCHEMA_NAME, 9 bytes
SYSIBMADM
DATA #4 : Hexdump, 8 bytes
0x0000009D02A47B35 : 6A41 6836 5058 4B63 jAh6PXKc
DATA #5 : ASCII Char, 1 bytes
X
DATA #6 : signed integer, 8 bytes
1
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2453 sqlerrml: 37
sqlerrmc: SYSIBMADM.DBMS_ALERT_REGISTER ROUTINE
sqlerrp : SQLRA157
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFF92 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

 

DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.