|
Problem IT44734
|
Status: Closed |
TASK 'MODIFY CHUNK EXTENDABLE' MAY RETURN ERROR 'FAILED: STORAGE PROVISIONING - INVALID ARGUMENT' FOR VALID CHUNK NUMBER
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
when calling execute function task('modify chunk extendable',
'n'); where n is the valid chunk number may fail
with error FAILED: Storage Provisioning - Invalid argument
> execute function task('modify chunk extendable', '3');
(expression) FAILED: Storage Provisioning - Invalid argument
1 row(s) retrieved.
Chunks
address chunk/dbs offset size free
bpages flags pathname
45bc2270 1 1 0 398000 285206
PO-B-- /work1/developer1/rootdbs
4dc9f028 2 1 0 72500 71773
PO-B-- /work1/developer1/datadbs1
4dca0028 3 1 0 72500 72497
PO-B-- /work1/developer1/datadbs2
4dca1028 4 1 0 72500 72497
PO-B-- /work1/developer1/datadbs3 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC11. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.10.2023
03.06.2024
03.06.2024 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
