How to install fixpack on DB2
steps to install fixpack on DB2
Follow the steps below to upgrade your DB2 Databases installing the next fixpack:
1 - Download the appropriate fixpack
Use the link below to donwload your fixpack
2 -backup instance and databases
db2support . -d sample -cl 0
db2 list packages for all show detail > packages.txt
db2look -d sample -e -l -x -o sample.ddl
db2 backup database sample
3 - Stop all DB2 Process
Do the steps below to all instances
db2 force applications all db2 terminate db2stop db2licd -end # run at each physical partition . $HOME/das/dasprofile db2admin stop
4 - Disable the fault monitor processes:
Log on as root.
Locate where the db2fmcu command runs from by issuing the command:
ps -ef
For example, on AIX the db2fmcu command is run from DB2DIR/bin directory, where DB2DIR is the location where the DB2 copy is installed.
Switch to the directory indicated by the ps command.
- Disable the Fault Monitor Coordinator (FMC) by issuing the command:
db2fmcu -d
Note:
1. Since there is only one Fault Monitor Coordinator, this step affects all DB2 copies on the system.
2. After you apply the fix pack, the Fault Monitor Coordinator is reset so that the system‘s inittab file is again configured to include the FMC. If you do not want to use the FMC, you must reissue the above command after you have applied the fix pack.
- To stop the Fault Monitor Daemon, issue the command:
db2fm -i iname -D
5 - Clean up all DB2 interprocess
Ensure all DB2 interprocess communications are cleaned for the instance to be updated. As the instance owner, run the following command at each physical partition:
$HOME/sqllib/bin/ipclean
6 - Install the fix pack:
- Log on as root.
- Change to the directory that contains the fix pack image.
- Launch the installation by issuing the installFixPack command. For example,
./installFixPack -b DB2DIR
where DB2DIR
is the location of the DB2 products that you want to update.
7 - Updating the instance
- For each instance, issue the command:
DB2DIR/instance/db2iupdt iname
where iname represents the instance name and DB2DIR represents the location where the DB2 copy is installed.
- If the DB2 Administration Server (DAS) belongs to the DB2 copy where you installed the fix pack, issue the command:
DB2DIR/instance/dasupdt
where DB2DIR is the location where the DB2 copy is installed. If this DB2 copy is now running at a more recent fix pack level than all of the other DB2 copies, consider updating the DAS to belong to this DB2 copy.
8 - Bind the bind file
- Start the instance
db2start
- Binding
db2 terminate
db2 CONNECT TO dbname
db2 BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 terminate
where dbname represents the name of a database to which the files should be bound, and where path is the full path name of the directory where the bind files are located, such as INSTHOME\sqllib\bnd where INSTHOME represents the home directory of the instance where you are issuing the commands. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 database products. Packages that are already bound will return an SQL0719N error. This is expected.
9 - Check the db2diag.log
If you don see any errors, you can start to use your database upgraded!!!
10 - back-off scheme
./installFixPack -f level -b DB2DIR