DB2 image have product specification file in the CD image. This file contains few basic details about the DB2 image that would be useful for customer.
This product file is located in the following directory in DB2 image :
[root directory on the CD /server]# ls
db2 db2checkCOL_readme.txt db2checkCOL.tar.gz db2ckupgrade db2_deinstall db2_install db2ls db2prereqcheck db2setup ibm_im installFixPack
[image root directory on the CD / server] # cd db2
[image root directory on the CD/ server / db2]# ls
common license linuxamd64 samples spec
From DB2 version 10.5 on wards there are few new information added to this file which are specific to pureScale on Linux and AIX platform. These information are really useful and helpful for the customer and DBA to take a decision on the method of applying fixpack. Let us look at the meaning of each row and how it will be helpful in this tutorial.
Looking at the image, you can decide what type fixpack update (online or offline ) is possible when you want to apply the image in the DB2 fixpack CD. This would help to decide on whether you need a maintenance window to take an outage of the cluster or it does not need an outage to your pureScale instance at all.
The content of the file looks like :
[image root directory on CD /server / db2]# cat spec
From the above list,
The architecture level is a new tag that is associated with every level of shipped DB2 code starting from DB2 10.5 ( including special builds and fixpack). This field lists architecture of db2 engine , and this number gets changed between version to version only when there are some fixes related online fixpack updates are made on the db2 server code.
Indicates the code version of the DB2 in the CD image
This number get changed between version to version only when there are changes on “how DB2 creates the static sections in the catalog”.
This flag indicates whether this fixpack can be applied online on top of the existing DB2 pureScale version directly or not. The value 'Y' indicates online fixpack update is possible.
This field indicates minimum version of DB2 on top of which this particular DB2 version in the CD can be used for an online fixpack update. Basically it indicates the minimum required base version, on top which this image can be used for an online fixpack update.
In the example show in the image , the DB2 code level is 10.5.0.5. This fixpack image can be applied online to the existing DB2 pureScale version 10.5.0.3 or 10.5.0.4 only.
This field indicates whether any pervious level of version is need to apply this fixpack online. If the value is “Y” , it indicates that there was a fix in this particular version that requires two level of codes to be installed completely. The first level of code is the toleration level (and is marked as Toleration Yes), and must be installed before the second level of code. If the value of the field is “N” means, there is no fixes in this version needs another level.
This field indicates the minimum version of DB2 on top of which this DB2 version in the CD can be used for traditional manual method of fixpack update or an offline method.
This indicate the efix level of GPFS that is bundled with the DB2 version in CD image.
GPFS version that is bundled in the CD image.
TSA level that is shipped with the DB2 in this CD image
Efix level of the TSA that is bundled along with DB2 in CD image.
Looking at gpfs_level, gpfs_efix , tsa_level and tsa_efix_build level fields, DBA can decide whether there will be an impact to the other products that are using the same TSA or GPFS. User can compare the current version of TSA and GPFS in their system and version mentioned this spec file. If there are difference, it means applying this fixpack will need GPFS and TSA in to maintenance mode apart from DB2.
For customers who are having “user managed GPFS” for their DB2 pureScale instance, these fields indicate the required version of GPFS and its efix level one needs to have before applying the DB2 fixpack.