|
Problem IT26765
|
Status: Closed |
AFTER SYSPURGE() EXECUTES, THE NEXT NEW FRAGMENT IN A ROLLING WINDOW IS CREATED IN THE FIRST DBSPACE OF THE STORE IN() CLAUSE
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
In general, the expected behavior of a Rolling window
fragmentation strategy is that the next fragment should be
created in the next available dbspace in line following the most
recent fragment.
In 12.10.xC10 a fix was added to ensure after an instance stop
and restart that the next fragment would go to the next dbspace
in line. However, syspurge() does not behave as should be
expected after that fix.
After syspurge() successfully destroys old fragments outside the
range of the rolling window in 12.10.xC12, the next fragment
gets created in the very first dbspace listed in the STORE IN()
clause, when it should be created in the next dbspace in line
following the most recent previous fragment. This results in
uneven fragmentation distribution and storage issues that may
require creation of new chunks to handle the extra, unplanned,
data in a given dbspace. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of IDS versions prior to 12.10.xC14. *
****************************************************************
* PROBLEM DESCRIPTION: *
* After syspurge() executes in 12.10.xC12, the next new *
* fragment in a Rolling window is created in the first dbspace *
* of the STORE IN() clause. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2018
24.09.2019
24.09.2019 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC14
|
| Problem solved according to the fixlist(s) of the following version(s) |
