When do I need to restart DB2 Services?
Windows
You must restart the DB2 services on Windows after you perform an upgrade or service pack upgrade.
Select the Restart Oracle/DB2 Services (if applicable) check box in Install Software Options or Upgrade Software Options dialog box for Windows clients.
UNIX
Restart the DB2 services on UNIX to clear the API information cached by the db2logmgr process after an upgrade or service pack upgrade on the DB2 client.
This will prevent the following error from occurring during an online full backup job.
SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved
When upgrading from older service packs (such as prior to SP 16) on Linux, you must stop or start log manager process only, without restarting all DB2 services.
For example, db2pd -db hrr -fvp lam1 term
For more information, see IBM KB article 1140214.
Do we need to reboot the DB2 client after installing the latest updates on it?
Yes. You must reboot the Windows DB2 client computer after installing the latest DB2 updates. Select Reboot Machine option in Update Installer dialog box. Commvault installer verifies and if required restarts the computer.
Can we modify the archive, retrieve and audit error paths after the installation?
Yes, you can modify the archive, retrieve, and audit error paths after the DB2 Data Agent installation. You can use additional settings in the CommCell Console to specify the new directory paths. For more information, see Modifying the Archive Path, Modifying the Audit Error Path and Modifying the Retrieve Path.
These additional settings can also be set in the etc/CommVaultRegistry/Galaxy/Instance001/Db2Agent/.properties file. Add an entry for each directory path that you want to modify.
sDB2_ARCHIVE_PATH new_archive_path sDB2_AUDIT_ERROR_PATH new_audit_error_path sDB2_RETRIEVE_PATH new_retrieve_path
Example
sDB2_ARCHIVE_PATH /database/db2/GDB2ARCHIVE
sDB2_AUDIT_ERROR_PATH /database/db2/GDB2ERROR
sDB2_RETRIEVE_PATH /database/db2/GDB2RETRIEVENote: Set the permissions for the archive, audit error and retrieve paths with the following permissions
|
Configuration |
Permissions |
|---|---|
|
No UNIX groups used in the Commvault installation |
Read, write and execute permissions (777) for everybody |
|
UNIX groups used in the Commvault installation |
Read, write and execute permissions (775) for the UNIX group Note: The DB2 instance users must be part of the UNIX group |
Before you create the new path, move all logs files in the old log directory to the new log directory.
A log at the following location:
/db2inst3/DBNOAUTO/NODE0000/C0000007/S0000011.LOG
is moved to
/db2inst3/DBNOAUTO/NODE0000/C0000036/S0000011.LOG
Are there additional steps to take when the DB2 Agent is installed on an existing client?
If you install the agent on an existing client, you must run the cvpkgchg command to update the group permissions after you install the agent. You can use this command to set the group permissions to the correct level, which prevents the backup job from failing. For information on how to change the group permissions, see Changing UNIX Groups and Permissions on UNIX Clients.
Do I need to update the DB2 database configuration parameters if client display name is changed?
Yes, you need to update the DB2 database configuration parameters if client display name is changed.
For more information, see Configuring the DB2 Database Parameters.