|
Problem IC65151
|
Status: Closed |
Turning logarchmeth off will cause log file not to be reused. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
Turning logarchmeth off will cause log files not to be reused if
at the time database was activated
and it found that at least one of the tablespaces is in either
- Load pending
- Delete pending
- Restore pending
- Recovery pending
- Disable pending
- Reorg in progress
- storage must be defined
- restore in progress
- offline and not accessible
- only action is drop
- redistribute in progress
- storeage may be defined
- storage Definition is in finla
- storage Deffinition was chaged prior to rollforward
- Tablespace in progression in progress
- tablespace creating in progress |
| Problem Summary: |
Turning logarchmeth off will cause log files not to be reused if
at the time database was activated
and it found that at least one of the tablespaces is in either
- Load pending
- Delete pending
- Restore pending
- Recovery pending
- Disable pending
- Reorg in progress
- storage must be defined
- restore in progress
- offline and not accessible
- only action is drop
- redistribute in progress
- storeage may be defined
- storage Definition is in finla
- storage Deffinition was chaged prior to rollforward
- Tablespace in progression in progress
- tablespace creating in progress
It is available in build level 100106 for project db2_v91fp9 |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65699 IC65723
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.12.2009
07.01.2010
07.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
