Install DB2 FIXPACK and db2fixpack

Install DB2 FIXPACK and db2fixpack
1. Run the su-root command to switch to the root user permission.
2. Run the following command on each instance:
Su-iname
. $ HOME/sqllib/db2profile
Db2 force applications all
Db2 terminate
Db2stop
Db2licd-end # run at each physical node
Exit
Iname indicates the name of the Instance owner.
If you are a hacmp user, you must use the ha_db2stop command to stop DB2, instead of using
Db2stop command. Otherwise, the db2stop command triggers a failure event.
=========================== The above execution succeeded ==========
3. Run the following command:
Su-aname
. $ HOME/das/dasprofile
Db2admin stop
Exit
Aname indicates the name of the DAS owner.
=============================== 3 this part is not processed, whether or not to do so ========
1. Extract (untar) and decompress the following compressed. tar file:
* FP5 _ for AIX 4.3.3 and Solaris Operating Environment _
Export ptf_ese_mfp.tar. Z
* Fp5_rjptf_ese_mfp_sbcs.tar. Z or
FP5_$PTF_ESE_MFP_DBCS.tar. Z
To install DB2 version 8 revision package 5:
1. Switch to the directory where the installation image is located.
2. Enter the./installFixPak command to start the installer.

Note: by default, the installFixPak command will implement all updated file sets on AIX.

On AIX, if you do not want updates to be implemented, issue the "-a" option as shown below (for "application"
Instead of "Implementing") The installFixPak command:
./InstallFixPak
============== Unzip the file and install it as root. I didn't use the-a option ======
1.15 after installation
1.15.1 update an instance to use the new DB2 level
This operation is required. After installing a new level of DB2, all instances must be updated.
You must log on as the root user to update the instance. Run the following command for each instance:
INSTHOME/instance/db2iupdt iname
INSTHOME/instance/dasupdt
Iname indicates the Instance name and INSTHOME indicates the installation directory suitable for the operating system.
========== 1.15.1 operation OK ========
If the Database Management Server (DAS) instance exists and is a DB2 version 8 DAS instance, it runs
Dasupdt command. To update the DAS instance, run the following command:
INSTHOME/instance/dasupdt dasname
Dasname indicates the name of the DAS owner, and INSTHOME indicates the installation directory suitable for the operating system.
For more information about db2iupdt or dasupdt commands, run these commands using the-h option.
============================
1.15.2 restart an instance
To restart an instance:
1. Log On As the instance owner and enter the db2start command.
2. repeat this process for each instance.
To restart the Management Server, log on as the DAS owner and run the db2admin start command.
===== If the startup fails, no other operations will be performed ========
$ Ipclean
Ipclean: Removing DB2 engine and client's IPC resources for db2inst1.
1. For the DB2 management server instance, you also need to stop it before installing the patch, and then update the Management Server
Server instance, restart.
2. You need to re-bind the package.
Rebind to the DB2 UDB Database
After the application revision, you must execute one of the following command sequences:
At the command prompt, enter:
Db2 terminate
Db2 CONNECT
Db2 BIND/@ db2ubind. lst BLOCKING ALL GRANT PUBLIC
Db2 BIND/@ db2cli. lst BLOCKING ALL GRANT PUBLIC
Db2 terminate
Or,
On the DB2 command line, enter:
TERMINATE CONNECT
BIND/@ db2ubind. lst BLOCKING ALL GRANT PUBLIC
BIND/@ db2cli. lst BLOCKING ALL GRANT PUBLIC
TERMINATE
Indicates the name of the database to which the utility is bound, indicating the bound File
The full path name of the directory, for example, $ HOME/sqllib/bnd. $ HOME indicates the database server.
The main directory of the instance. Db2ubind. lst and db2cli. lst contain the binding required by DB2 UDB
File List.
For partition servers, There is nothing special to pay attention to, but also follow the same steps to install, more
New instance, start, and re-bind the package.
If the partition server is deployed across multiple machines, perform the same steps on each physical machine to install and complete
Ding. Before starting an instance, make sure that
All patches are at the same patch level.