|
Problem IT01126
|
Status: Closed |
COMPRESSED ARCHIVED LOGS HAVE DIFFERENT PERMISSIONS THAN NON-COMPRESSED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Below is an example of some compressed archived logs and some
uncompressed archived logs.
-rwx------ 1 db2lco dblcoadm 15759358 Mar 5 14:16 S0000267.LOG
-rwx------ 1 db2lco dblcoadm 15541947 Mar 5 14:19 S0000268.LOG
-rwx------ 1 db2lco dblcoadm 15651254 Mar 5 14:21 S0000269.LOG
-rw-r----- 1 db2lco dblcoadm 67100672 Mar 5 14:23 S0000270.LOG
-rw-r----- 1 db2lco dblcoadm 67100672 Mar 5 14:24 S0000271.LOG
-rw-r----- 1 db2lco dblcoadm 67100672 Mar 5 14:26 S0000272.LOG
Permissions for the compressed archived logs are: -rwx------
But the ermissions for the non-compressed archived logs are:
-rw-r-----
All archived logs should have permissions: -rw-r----- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Applies to customers that use log archive compression. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 v10.5 Fixpack 4. *
**************************************************************** |
| Local Fix: |
Manually alter the permissions. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Apply DB2 v10.5 Fixpack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.04.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
