home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT00297 Status: Closed

ONSMSYNC IS ELIMINATING ROOTDBS OBJECTS ON EXPIRATION IF A BACKUP WAS
EXPORTED INTO EXTERNAL POOL

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
You have set up your Informix instance to be able to make 
backups with use of OnBar and PSM. You have created several 
generations of backup and exported one of them into an external 
pool. Then you ran 'onsmsync -g' command to expire older 
generations, but found that in the generations some critical 
objects (like rootdbs) are missing. 
 
Example. Before the backups are expired: 
 
$ onpsm -O list 
Informix PSM Object List 
 
Object ID            Date Created         Size (MB) Logical path 
(name.version) 
1                    2014-03-13 11:24:36       13.5 
/ids1210fc3/rootdbs/0/ids1210fc3.1 
2                    2014-03-13 11:24:37        0.1 
/ids1210fc3/datdbs/0/ids1210fc3.1 
3                    2014-03-13 11:24:38        0.1 
/ids1210fc3/testdbs/0/ids1210fc3.1 
4                    2014-03-13 11:24:38        9.8 
/ids1210fc3/114/5/ids1210fc3.1 
5                    2014-03-13 11:24:38        0.4 
/ids1210fc3/114/6/ids1210fc3.1 
6                    2014-03-13 11:24:38        0.0 
/ids1210fc3/critical_files/ixbar/ids1210fc3.1 
7                    2014-03-13 11:24:38        0.0 
/ids1210fc3/critical_files/oncfg/ids1210fc3.1 
8                    2014-03-13 11:24:38        0.1 
/ids1210fc3/critical_files/onconfig/ids1210fc3.1 
9                    2014-03-13 11:24:38        0.0 
/ids1210fc3/critical_files/sqlhosts/ids1210fc3.1 
10                   2014-03-13 11:24:39       13.2 
/ids1210fc3/rootdbs/0/ids1210fc3.2 
11                   2014-03-13 11:24:39        0.1 
/ids1210fc3/testdbs/0/ids1210fc3.2 
12                   2014-03-13 11:24:40        0.1 
/ids1210fc3/datdbs/0/ids1210fc3.2 
13                   2014-03-13 11:24:40        0.1 
/ids1210fc3/114/7/ids1210fc3.1 
14                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/ixbar/ids1210fc3.2 
15                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/oncfg/ids1210fc3.2 
16                   2014-03-13 11:24:41        0.1 
/ids1210fc3/critical_files/onconfig/ids1210fc3.2 
17                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/sqlhosts/ids1210fc3.2 
18                   2014-03-13 11:24:42       13.2 
/ids1210fc3/rootdbs/0/ids1210fc3.3 
19                   2014-03-13 11:24:42        0.1 
/ids1210fc3/testdbs/0/ids1210fc3.3 
20                   2014-03-13 11:24:42        0.1 
/ids1210fc3/datdbs/0/ids1210fc3.3 
21                   2014-03-13 11:24:42        0.1 
/ids1210fc3/114/8/ids1210fc3.1 
22                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/ixbar/ids1210fc3.3 
23                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/oncfg/ids1210fc3.3 
24                   2014-03-13 11:24:43        0.1 
/ids1210fc3/critical_files/onconfig/ids1210fc3.3 
25                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/sqlhosts/ids1210fc3.3 
 
A command is executed to expire one generation (note the missing 
rootdbs objects): 
 
$ onsmsync -g 2 -cf yes 
 
Object ID            Date Created         Size (MB) Logical path 
(name.version) 
11                   2014-03-13 11:24:39        0.1 
/ids1210fc3/testdbs/0/ids1210fc3.2 
12                   2014-03-13 11:24:40        0.1 
/ids1210fc3/datdbs/0/ids1210fc3.2 
14                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/ixbar/ids1210fc3.2 
15                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/oncfg/ids1210fc3.2 
16                   2014-03-13 11:24:41        0.1 
/ids1210fc3/critical_files/onconfig/ids1210fc3.2 
17                   2014-03-13 11:24:41        0.0 
/ids1210fc3/critical_files/sqlhosts/ids1210fc3.2 
19                   2014-03-13 11:24:42        0.1 
/ids1210fc3/testdbs/0/ids1210fc3.3 
20                   2014-03-13 11:24:42        0.1 
/ids1210fc3/datdbs/0/ids1210fc3.3 
22                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/ixbar/ids1210fc3.3 
23                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/oncfg/ids1210fc3.3 
24                   2014-03-13 11:24:43        0.1 
/ids1210fc3/critical_files/onconfig/ids1210fc3.3 
25                   2014-03-13 11:24:43        0.0 
/ids1210fc3/critical_files/sqlhosts/ids1210fc3.3
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using onbar and PSM storage manager (or another        * 
* storage manager which allows BSADeleteObject calls to        * 
* delete/expire objects in the storage manager ).              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The problem description is due to a user error where the     * 
* storage manager and the Informix sysutils catalog have       * 
* become out-of-sync and incompatible due to an imported       * 
* restore scenario (backups being imported into an entirely    * 
* new storage manager) and subsequent backups causing          * 
* duplicate copyId's in the Informix sysutils catalog.   When  * 
* onsmsync expiration commands are run, a check for duplicate  * 
* copyId's in sysutils to warn users of this situation has     * 
* been introduced.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IDS-12.10.xC5                                      * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IDS-12.10.xC5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.03.2014
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC4.W1 FixList
12.10.xC5 FixList
12.10.xC5.W1 FixList