1. Switch to root user rights by running the Su-root command.
2. Run the following command for each instance:
Su-iname
. $HOME/sqllib/db2profile
DB2 Force applications All
DB2 Terminate
Db2stop
Db2licd-end # Run at each physical node
Exit
Where Iname represents the instance owner name.
If you are a hacmp user, you must use the Ha_db2stop command to stop DB2 instead of using the
Db2stop command. Otherwise, the Db2stop command will trigger the failed event.
================= above successful execution =========
3. Run the following command:
Su-aname
. $HOME/das/dasprofile
Db2admin stop
Exit
Where Aname represents the DAS owner name.
====================3 This section does not deal with, whether about do not do ======
1. Extract (Untar) and unzip the following compressed. tar file:
* Fp5_ for AIX 4.3.3 and Solaris Operating Environment
$PTF _ese_mfp.tar.z
* for AIX 5 fp5_$ptf_ese_mfp_sbcs.tar.z or
Fp5_$ptf_ese_mfp_dbcs.tar.z
To install DB2 version 8 Revision Pack 5:
1. Switch to the directory where the installation image resides.
2. Enter the./installfixpak command to start the Setup program.
Note: By default, the Installfixpak command will implement all the updated file sets on AIX.
On AIX, if you do not want to implement the update, you should issue the with-a option as follows (for app
Rather than "implement") The Installfixpak command:
./installfixpak
============ unzip the file to root installation, I did not use the-a option =====
1.15 After the installation
1.15.1 updating instances to use the new DB2 level
This action must be performed. All instances must be updated after the new level of DB2 is installed.
You need to be logged in as the root user to update the instance. For each instance, issue the following command:
INSTHOME/INSTANCE/DB2IUPDT Iname
Insthome/instance/dasupdt
Where Iname represents the instance name and Insthome represents the installation directory 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, run
DASUPDT command. To update the DAS instance, issue the following command:
INSTHOME/INSTANCE/DASUPDT Dasname
Where Dasname represents the DAS owner name and Insthome represents the installation directory for the operating system.
For more information about the DB2IUPDT or DASUPDT commands, run these commands using the-H option.
======= did not deal with ==========
1.15.2 restarting an instance
To restart an instance:
1. Log in as the instance owner and enter the Db2start command.
2. Repeat this procedure for each instance.
To restart the Management Server, log in as the DAS owner and run the db2admin start command.
===== boot is not up, there is no other operation =========
$ ipclean
Ipclean:removing DB2 engine and client ' s IPC resources for Db2inst1.
1, for DB2 Management Server instance, you also need to stop before installing the patch, and then update the management Service
Restart the service instance.
2. You need to rebind the package.
rebind to DB2 UDB database
After you apply the revision, you must execute one of the following command sequences:
At the command prompt, enter:
DB2 Terminate
DB2 CONNECT to
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 to
bind/@db2ubind. LST BLOCKING all GRANT public
bind/@db2cli. LST BLOCKING all GRANT public
TERMINATE
which represents the name of the database to which the utility should be bound, indicating that the binding file
The full pathname of the directory, such as $HOME/sqllib/bnd, where $HOME represents the database server
The home directory of the instance. Db2ubind.lst and db2cli.lst contain the necessary bindings for DB2 UDB usage
A list of files.
For the partition server side, there is no special attention to the place, but also follow the same steps to install, more
The new instance, start, rebind package is ready.
If the partition server spans multiple machines, it is necessary to perform the same steps on each physical machine to install the patch
Ding. Before you start the instance, you need to ensure that all machines
Patches are on the same patch level.
Installing DB2 Fixpack
