Modifying DB2 Archive, Retrieve and Audit Error Paths

You can modifying DB2 archive, retrieve and audit error paths.

Before You Begin

Ensure the following before proceeding:

• All files are completely copied.

• File timestamps and permissions are preserved.

• No DB2 processes are writing to the old directories during the copy operation.

• Use the correct Additional setting if it is available.

Procedure

1. Create New Directories

   Create directories for archive, audit error, and retrieve logs.

   mkdir -p /home/<db2_instance>/new_path/db2Archive/
   
   mkdir -p /home/<db2_instance>/new_path/db2AuditError/
   
   mkdir -p /home/<db2_instance>/new_path/db2Retrieve/
   

2. Set Directory Permissions

   Assign appropriate permissions and group ownership.

   chmod -R 775 /home/<db2_instance>/new_path
   
   chgrp -R <db2_group> /home/<db2_instance>/new_path
   

3. Change the Additional Setting to the New Directory Path

   Update the DB2 Agent properties file with the new directory paths.

   vi /etc/CommvaultRegistry/Galaxy/Instance001/Db2Agent/.properties
   

4. Restart DB2 Log Archive Process

   Restart the DB2 log archive process. Optionally, stop log archival during this operation.

   db2stop
   
   db2start
   

5. Copy Existing Log Files

   Copy existing files from the old directories to the new locations.

   cp -rp /home/<db2_instance>/old_path/db2Archive/* /home/<db2_instance>/new_path/db2Archive/
   
   cp -rp /home/<db2_instance>/old_path/db2AuditError/* /home/<db2_instance>/new_path/db2AuditError/
   
   cp -rp /home/<db2_instance>/old_path/db2Retrieve/* /home/<db2_instance>/new_path/db2Retrieve/