|
Problem IT35875
|
Status: Closed |
EXTERNAL RESTORE CAN FAIL DURING CHECK OF SECOND CHUNK OF THE ROOTDBS
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
An external restore will fail if the following conditions are
met
a) the backup was done while there was at least one open
transaction spawning some logical logs
b) there is more than one chunk in the rootdbs.
In this case when trying to use this external restore you will
see the following message:
12:11:59 Recovery Mode
12:12:01 External restore started.
12:12:01 The chunk number 3 comes from a different external
backup than dbspace 'rootdbs',
or the chunk was not externally backed up.
12:12:01 External restore of critical dbspace 'rootdbs' failed.
the chunk number will be the second chunk of the rootdbs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix server prior to 14.10.xC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC6 (when available). *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix server prior to 14.10.xC6. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC6 (when available). *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC6. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.02.2021
12.05.2021
12.05.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
