INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10

If symbolic links are used such that ROOTPATH in the $ONCONFIG
file can be modified so the server comes up and then an archive
is taken; if that archive is restored it's possible to hit 1 of
2 different problems.

If the above is done, you end up with a server that has ROOTPATH
in the $ONCONFIG file to be something like this
/tmp/dir2/rootchunk but the server was really initialized with a
ROOTPATH of /tmp/dir1/rootchunk, but a symbolic link gets
created in /tmp such that dir2 -> dir1 so then
/tmp/dir2/rootchunk and /tmp/dir1/rootchunk are the same file.
When this happens, the server will come online, but onstat -d
will report the path for chunk #1 as /tmp/dir1/rootchunk, but
$ONCONFIG ROOTPATH is set to /tmp/dir2/rootchunk.

So then after taking the archive, if you go to restore this
archive you may hit 1 of the following 2 issues.

Issue 1)

If you lost your $ONCONFIG file so you didn't know what ROOTPATH
was supposed to be, you can start to run the restore and ontape
will report the chunk paths to you.  So to encounter problem 1,
modify the ROOTPATH in the $ONCONFIG file back to
/tmp/dir1/rootchunk.  If you do this, ontape will fail
immediately with this sort of error:

Physical restore failed - ONCONFIG ROOTPATH:ROOTOFFSET
'/tmp/dir1/root:0' differs from archive '/tmp/dir2/root:0'

Issue 2)

Modify ROOTPATH in $ONCONFIG back to /tmp/dir2/rootchunk, but
now do a restore where you want to change the path for the
rootchunk.  Again, lets assume you didn't know the paths so you
build your chunk path rename file using the chunk path listed
from ontape (which is /tmp/dir1/rootchunk).
So you run ontape -r -rename -f renamefile

Now the following assertion failures will be in MSGPATH file:

08:16:43  Assert Failed: Page Check Error in clr_resrv_pg(): Bad
reserved page
08:16:43  IBM Informix Dynamic Server Version 12.10.FC1
08:16:43   Who: Session(9, informix@server, 30232, 0x4b912e88)
                Thread(23, ontape, 4b8d2808, 1)
                File: rsdebug.c Line: 1103
08:16:43   Results: Possible inconsistencies in '(null)'
08:16:43  stack trace for pid 30679 written to
/usr3/pmrs/22020/test/af.3ffd9cb
08:16:43   See Also: /usr3/pmrs/22020/test/af.3ffd9cb,
shmem.3ffd9cb.0
08:16:44  Page Check Error in clr_resrv_pg(): Bad reserved page
08:16:44  Assert Failed: Page Check Error in clr_resrv_pg(): Bad
reserved page
08:16:44  IBM Informix Dynamic Server Version 12.10.FC1
08:16:44   Who: Session(9, informix@server, 30232, 0x4b912e88)
                Thread(23, ontape, 4b8d2808, 1)
                File: rsdebug.c Line: 1103
08:16:44   Results: Possible inconsistencies in '(null)'
08:16:44  stack trace for pid 30679 written to
/usr3/pmrs/22020/test/af.3ffd9cb
08:16:44   See Also: /usr3/pmrs/22020/test/af.3ffd9cb
08:16:46  Page Check Error in clr_resrv_pg(): Bad reserved page

Contents of AF file:

08:16:43  bfcheck: bad page: pg_addr 0:0 != bp->bf_pagenum 1:8
...
08:16:43  Stack for thread: 23 ontape

afstack
afhandler
affail_interface
bffail
clr_resrv_pg
rsclose_phr
tbj_phys_close_restore
sqmain
spawn_thread
startup

****************************************************************
* USERS AFFECTED:                                              *
* All users                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to IBM Informix Server 12.10.xC7                      *
****************************************************************

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

20.11.2015
28.06.2016
28.06.2016

12.10.xC7