Comparison between DB2 Universal and DB2 Server_t images on v10.5 Fix Central
Introduction to IBM Support Fix Central
Below is the homepage for IBM Support Fix Central which provides fixes and updates for all DB2 versions and releases.
Step 1: Go to Select product tab and select the required product, version and platform for which you are looking for fixes and updates. Press continue.
Step 2. If you are looking for all the available fix pack updates then select “Browse for fixes' Else select the relevant option for specific APAR or fix Ids.
Step 3. Below page shows all the available Fix Pack downloadable for DB2 v10.5 fix pack 4 for linuxamd64 platform. Select the required image and download.
Comparison between Universal and Server_t image
Universal image: DB2-linuxx64-universal_fixpack-10.5.0.4-FP004
Above DB2 Universal image is used to update binaries in cases where user have more than one product installed on one installation path. For example if you have DB2 Server product and IIRW (IBM InfoSphere Federation Server Relational Wrappers) installed on the same installation path then you have to use Universal image for fixpack update.
User do not remember what product/products are installed on a location and wants to do fixpack update then Universal image is the only solution. Universal image automatically detects the product or products installed on the location and updates the binaries accordingly.
Starting v10.5 FP3 Universal image is capable of doing fresh installation. From this level user can install the fixpack image to a new location.
Server_t image: DB2-linuxx64-server_t-10.5.0.4-FP004
Above DB2 Server_t image is used to update binaries in cases where user have only one product installed. For example server_t image can be used to update products like: DB2 Server Edition, DB2 Connect Server Edition, DB2 Express Edition, DB2 Client and DB2 Runtime Client.
Can not be used to update when more than one products are installed on the same location.
Can be used to test the fixpack images by installing to new location without impacting product ion databases.