RE: corrupt index dbspace on IDS 9.4
On IDS 9.40.UC5 under 32-bit RHEL3, all chunks of a cooked-file index dbspace (indxdbs) were marked down/corrupt while other spaces stayed fine, and 'onspaces -s ... -o 0' failed with "Cannot change chunk status / ISAM error: illegal argument to ISAM function." Suggestions were limited: Art Kagel had never seen it, and Rogers asked whether another instance or overlapping raw devices might be hitting the same volumes, and said that if the data really is corrupt a restore/recovery is required. The poster said he'd check for overlaps; no actual cause or fix is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
On-Line -- Up 01:12:42 -- 1279064 Kbytes
The server is 32 bit RHEL3
---
[informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02
EST 2004 i686 i686 i386 GNU/Linux
LSB_VERSION="1.3"
Red Hat Enterprise Linux AS release 3 (Taroon)
======================================================
The issue is that all the chunks in the indxdbs tablespace are coming up
corrupt.
It is strange that only files in indxdbs are affected, other tablespaces are
fine.
---
[informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
56df82b8 6 0x40005 6 40 ND B informix indxdbs
[informix@efklpdcfel backup2]$ onstat -d | grep indx
56df82b8 6 0x40005 6 40 ND B informix indxdbs
56de8018 6 6 0 4000000 0 PD-B
/home/informix/dblinks/indx01
56de84b0 9 6 0 4000000 0 PD-B
/home/informix/dblinks/indx02
56de87c0 11 6 0 4000000 0 PD-B
/home/informix/dblinks/indx03
56de8ad0 13 6 0 4000000 0 PD-B
/home/informix/dblinks/indx04
56de8de0 15 6 0 4000000 0 PD-B
/home/informix/dblinks/indx05
56de91a0 17 6 0 4000000 0 PD-B
/home/informix/dblinks/indx06
56de94b0 19 6 0 4000000 0 PD-B
/home/informix/dblinks/indx07
Somehow the informix engine "thinks" that all the chunks (& associated data
files) for the indxdbs
tablespace are corrupt and is taking them off-line. I do not believe this is
the case.
We have a mixture of data and index data files in various directories and
mount points on the server. It is very
suspicious that ONLY the index data files are affected and that ALL index
data files are affected.
So, is there a way to get the Informix Engine to turn this tablespace back
on??
I tried "onspaces -s indxdbs -p ........." but it gave me an error
---
[informix@efklpdcfel ~]$ onspaces -s indxdbs -p
/home/informix/dblinks/indx40 -o 0
Warning: Bringing chunk back online.
Do you really want to continue? (y/n)y
Verifying physical disk space, please wait ...
Cannot change chunk status.
ISAM error: illegal argument to ISAM function.
So- how can we get this tablespace back on-line???
Thanks,
So, has no one ever run across an index dbspace going offline for no apparent
reason?
> To: ids@iiug.org
> From: lsorensen25@msn.com
> Subject: RE: corrupt index dbspace on IDS 9.4 [19107]
> Date: Tue, 23 Feb 2010 20:30:36 -0500
>
> Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
> On-Line -- Up 01:12:42 -- 1279064 Kbytes
>
> The server is 32 bit RHEL3
> ---
> [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
> Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02
> EST 2004 i686 i686 i386 GNU/Linux
> LSB_VERSION="1.3"
> Red Hat Enterprise Linux AS release 3 (Taroon)
>
> ======================================================
> The issue is that all the chunks in the indxdbs tablespace are coming up
> corrupt.
> It is strange that only files in indxdbs are affected, other tablespaces are
> fine.
> ---
> [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
> 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> [informix@efklpdcfel backup2]$ onstat -d | grep indx
> 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> 56de8018 6 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx01
> 56de84b0 9 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx02
> 56de87c0 11 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx03
> 56de8ad0 13 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx04
> 56de8de0 15 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx05
> 56de91a0 17 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx06
> 56de94b0 19 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx07
>
> Somehow the informix engine "thinks" that all the chunks (& associated data
> files) for the indxdbs
> tablespace are corrupt and is taking them off-line. I do not believe this is
> the case.
> We have a mixture of data and index data files in various directories and
> mount points on the server. It is very
> suspicious that ONLY the index data files are affected and that ALL index
> data files are affected.
>
> So, is there a way to get the Informix Engine to turn this tablespace back
> on??
> I tried "onspaces -s indxdbs -p ........." but it gave me an error
> ---
> [informix@efklpdcfel ~]$ onspaces -s indxdbs -p
> /home/informix/dblinks/indx40 -o 0
> Warning: Bringing chunk back online.
> Do you really want to continue? (y/n)y
> Verifying physical disk space, please wait ...
> Cannot change chunk status.
> ISAM error: illegal argument to ISAM function.>
> So- how can we get this tablespace back on-line???
>
> Thanks,
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
I've never seen that, no.
Art=20
-----Original Message-----
From: LARRY SORENSEN <lsorensen25@msn.com>
Sent: Wednesday, February 24, 2010 3:17 PM
To: ids@iiug.org
Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19119]
So, has no one ever run across an index dbspace going offline for no appare=
nt=20
reason?=20
> To: ids@iiug.org=20
> From: lsorensen25@msn.com=20
> Subject: RE: corrupt index dbspace on IDS 9.4 [19107]=20
> Date: Tue, 23 Feb 2010 20:30:36 -0500=20
>=20
> Base information : IBM Informix Dynamic Server Version 9.40.UC5 --=20
> On-Line -- Up 01:12:42 -- 1279064 Kbytes=20
>=20
> The server is 32 bit RHEL3=20
> ---=20
> [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*=20
> Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:=
02=20
> EST 2004 i686 i686 i386 GNU/Linux=20
> LSB_VERSION=3D"1.3"=20
> Red Hat Enterprise Linux AS release 3 (Taroon)=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=20
> The issue is that all the chunks in the indxdbs tablespace are coming up=
=20
> corrupt.=20
> It is strange that only files in indxdbs are affected, other tablespaces =
are=20
> fine.=20
> ---=20
> [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs=20
[The entire original message is not included]=
Do you have another instance running on the box that could be addressing the
same volumes?
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LARRY
SORENSEN
Sent: Wednesday, February 24, 2010 3:17 PM
To: ids@iiug.org
Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19119]
So, has no one ever run across an index dbspace going offline for no apparent
reason?
> To: ids@iiug.org
> From: lsorensen25@msn.com
> Subject: RE: corrupt index dbspace on IDS 9.4 [19107]
> Date: Tue, 23 Feb 2010 20:30:36 -0500
>
> Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
> On-Line -- Up 01:12:42 -- 1279064 Kbytes
>
> The server is 32 bit RHEL3
> ---
> [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
> Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02
> EST 2004 i686 i686 i386 GNU/Linux
> LSB_VERSION="1.3"
> Red Hat Enterprise Linux AS release 3 (Taroon)
>
> ======================================================
> The issue is that all the chunks in the indxdbs tablespace are coming up
> corrupt.
> It is strange that only files in indxdbs are affected, other tablespaces are
> fine.
> ---
> [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
> 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> [informix@efklpdcfel backup2]$ onstat -d | grep indx
> 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> 56de8018 6 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx01
> 56de84b0 9 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx02
> 56de87c0 11 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx03
> 56de8ad0 13 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx04
> 56de8de0 15 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx05
> 56de91a0 17 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx06
> 56de94b0 19 6 0 4000000 0 PD-B
> /home/informix/dblinks/indx07
>
> Somehow the informix engine "thinks" that all the chunks (& associated data
> files) for the indxdbs
> tablespace are corrupt and is taking them off-line. I do not believe this is
> the case.
> We have a mixture of data and index data files in various directories and
> mount points on the server. It is very
> suspicious that ONLY the index data files are affected and that ALL index
> data files are affected.
>
> So, is there a way to get the Informix Engine to turn this tablespace back
> on??
> I tried "onspaces -s indxdbs -p ........." but it gave me an error
> ---
> [informix@efklpdcfel ~]$ onspaces -s indxdbs -p
> /home/informix/dblinks/indx40 -o 0
> Warning: Bringing chunk back online.
> Do you really want to continue? (y/n)y
> Verifying physical disk space, please wait ...
> Cannot change chunk status.
> ISAM error: illegal argument to ISAM function.>
> So- how can we get this tablespace back on-line???
>
> Thanks,
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I am reviewing the server and also making sure that I don't have any raw
spaces that overlap. I will let you know what I find. Thank you for responding.
> To: ids@iiug.org
> From: rogers.patterson@arkansas.gov
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19121]
> Date: Wed, 24 Feb 2010 17:21:02 -0500
>
> Do you have another instance running on the box that could be addressing the
> same volumes?
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LARRY
> SORENSEN
> Sent: Wednesday, February 24, 2010 3:17 PM
> To: ids@iiug.org
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19119]
>
> So, has no one ever run across an index dbspace going offline for no apparent
> reason?
>
> > To: ids@iiug.org
> > From: lsorensen25@msn.com
> > Subject: RE: corrupt index dbspace on IDS 9.4 [19107]
> > Date: Tue, 23 Feb 2010 20:30:36 -0500
> >
> > Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
> > On-Line -- Up 01:12:42 -- 1279064 Kbytes
> >
> > The server is 32 bit RHEL3
> > ---
> > [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
> > Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02
> > EST 2004 i686 i686 i386 GNU/Linux
> > LSB_VERSION="1.3"
> > Red Hat Enterprise Linux AS release 3 (Taroon)
> >
> > ======================================================
> > The issue is that all the chunks in the indxdbs tablespace are coming up
> > corrupt.
> > It is strange that only files in indxdbs are affected, other tablespaces
are
> > fine.
> > ---
> > [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > [informix@efklpdcfel backup2]$ onstat -d | grep indx
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > 56de8018 6 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx01
> > 56de84b0 9 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx02
> > 56de87c0 11 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx03
> > 56de8ad0 13 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx04
> > 56de8de0 15 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx05
> > 56de91a0 17 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx06
> > 56de94b0 19 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx07
> >
> > Somehow the informix engine "thinks" that all the chunks (& associated data
> > files) for the indxdbs
> > tablespace are corrupt and is taking them off-line. I do not believe this
is
> > the case.
> > We have a mixture of data and index data files in various directories and
> > mount points on the server. It is very
> > suspicious that ONLY the index data files are affected and that ALL index
> > data files are affected.
> >
> > So, is there a way to get the Informix Engine to turn this tablespace back
> > on??
> > I tried "onspaces -s indxdbs -p ........." but it gave me an error
> > ---
> > [informix@efklpdcfel ~]$ onspaces -s indxdbs -p
> > /home/informix/dblinks/indx40 -o 0
> > Warning: Bringing chunk back online.
> > Do you really want to continue? (y/n)y
> > Verifying physical disk space, please wait ...
> > Cannot change chunk status.
> > ISAM error: illegal argument to ISAM function.> >
> > So- how can we get this tablespace back on-line???
> >
> > Thanks,
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Is there an easy way to try and bring a dbspace back online? I see that
onspaces can be used, but do I have to run this for each one of the chunks in
the dbspace or is this for the original chunk in the dbspace? Does onmonitor
do the same thing? What are my other options in trying to bring this back
online with a restore of the dbspace?
Thanks
> To: ids@iiug.org
> From: rogers.patterson@arkansas.gov
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19121]
> Date: Wed, 24 Feb 2010 17:21:02 -0500
>
> Do you have another instance running on the box that could be addressing the
> same volumes?
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LARRY
> SORENSEN
> Sent: Wednesday, February 24, 2010 3:17 PM
> To: ids@iiug.org
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19119]
>
> So, has no one ever run across an index dbspace going offline for no apparent
> reason?
>
> > To: ids@iiug.org
> > From: lsorensen25@msn.com
> > Subject: RE: corrupt index dbspace on IDS 9.4 [19107]
> > Date: Tue, 23 Feb 2010 20:30:36 -0500
> >
> > Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
> > On-Line -- Up 01:12:42 -- 1279064 Kbytes
> >
> > The server is 32 bit RHEL3
> > ---
> > [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
> > Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02
> > EST 2004 i686 i686 i386 GNU/Linux
> > LSB_VERSION="1.3"
> > Red Hat Enterprise Linux AS release 3 (Taroon)
> >
> > ======================================================
> > The issue is that all the chunks in the indxdbs tablespace are coming up
> > corrupt.
> > It is strange that only files in indxdbs are affected, other tablespaces
are
> > fine.
> > ---
> > [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > [informix@efklpdcfel backup2]$ onstat -d | grep indx
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > 56de8018 6 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx01
> > 56de84b0 9 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx02
> > 56de87c0 11 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx03
> > 56de8ad0 13 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx04
> > 56de8de0 15 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx05
> > 56de91a0 17 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx06
> > 56de94b0 19 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx07
> >
> > Somehow the informix engine "thinks" that all the chunks (& associated data
> > files) for the indxdbs
> > tablespace are corrupt and is taking them off-line. I do not believe this
is
> > the case.
> > We have a mixture of data and index data files in various directories and
> > mount points on the server. It is very
> > suspicious that ONLY the index data files are affected and that ALL index
> > data files are affected.
> >
> > So, is there a way to get the Informix Engine to turn this tablespace back
> > on??
> > I tried "onspaces -s indxdbs -p ........." but it gave me an error
> > ---
> > [informix@efklpdcfel ~]$ onspaces -s indxdbs -p
> > /home/informix/dblinks/indx40 -o 0
> > Warning: Bringing chunk back online.
> > Do you really want to continue? (y/n)y
> > Verifying physical disk space, please wait ...
> > Cannot change chunk status.
> > ISAM error: illegal argument to ISAM function.> >
> > So- how can we get this tablespace back on-line???
> >
> > Thanks,
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
If the data is corrupted you will need to do a recovery or a restore.
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LARRY
SORENSEN
Sent: Thursday, February 25, 2010 3:13 PM
To: ids@iiug.org
Subject: RE: corrupt/dbspace down index dbspace on IDS 9.4 [19134]
Is there an easy way to try and bring a dbspace back online? I see that
onspaces can be used, but do I have to run this for each one of the chunks in
the dbspace or is this for the original chunk in the dbspace? Does onmonitor
do the same thing? What are my other options in trying to bring this back
online with a restore of the dbspace?
Thanks
> To: ids@iiug.org
> From: rogers.patterson@arkansas.gov
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19121]
> Date: Wed, 24 Feb 2010 17:21:02 -0500
>
> Do you have another instance running on the box that could be addressing the
> same volumes?
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LARRY
> SORENSEN
> Sent: Wednesday, February 24, 2010 3:17 PM
> To: ids@iiug.org
> Subject: RE: corrupt/space down index dbspace on IDS 9.4 [19119]
>
> So, has no one ever run across an index dbspace going offline for no
apparent
> reason?
>
> > To: ids@iiug.org
> > From: lsorensen25@msn.com
> > Subject: RE: corrupt index dbspace on IDS 9.4 [19107]
> > Date: Tue, 23 Feb 2010 20:30:36 -0500
> >
> > Base information : IBM Informix Dynamic Server Version 9.40.UC5 --
> > On-Line -- Up 01:12:42 -- 1279064 Kbytes
> >
> > The server is 32 bit RHEL3
> > ---
> > [informix@efklpdcfel backup2]$ uname -a && cat /etc/*release*
> > Linux efklpdcfel.fishkill.ibm.com 2.4.21-27.ELsmp #1 SMP Wed Dec 1
21:59:02
> > EST 2004 i686 i686 i386 GNU/Linux
> > LSB_VERSION="1.3"
> > Red Hat Enterprise Linux AS release 3 (Taroon)
> >
> > ======================================================
> > The issue is that all the chunks in the indxdbs tablespace are coming up
> > corrupt.
> > It is strange that only files in indxdbs are affected, other tablespaces
are
> > fine.
> > ---
> > [informix@efklpdcfel backup2]$ onstat -d | grep indxdbs
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > [informix@efklpdcfel backup2]$ onstat -d | grep indx
> > 56df82b8 6 0x40005 6 40 ND B informix indxdbs
> > 56de8018 6 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx01
> > 56de84b0 9 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx02
> > 56de87c0 11 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx03
> > 56de8ad0 13 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx04
> > 56de8de0 15 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx05
> > 56de91a0 17 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx06
> > 56de94b0 19 6 0 4000000 0 PD-B
> > /home/informix/dblinks/indx07
> >
> > Somehow the informix engine "thinks" that all the chunks (& associated
data
> > files) for the indxdbs
> > tablespace are corrupt and is taking them off-line. I do not believe this
is
> > the case.
> > We have a mixture of data and index data files in various directories and
> > mount points on the server. It is very
> > suspicious that ONLY the index data files are affected and that ALL index
> > data files are affected.
> >
> > So, is there a way to get the Informix Engine to turn this tablespace back
> > on??
> > I tried "onspaces -s indxdbs -p ........." but it gave me an error
> > ---
> > [informix@efklpdcfel ~]$ onspaces -s indxdbs -p
> > /home/informix/dblinks/indx40 -o 0
> > Warning: Bringing chunk back online.
> > Do you really want to continue? (y/n)y
> > Verifying physical disk space, please wait ...
> > Cannot change chunk status.
> > ISAM error: illegal argument to ISAM function.> >
> > So- how can we get this tablespace back on-line???
> >
> > Thanks,
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Related threads
- IDS 10 table-level restore
- Informix Development Webinar December 11, 2007
- ontape -p/r with changed ROOTPATH
- Migrate from HP PA-RISC to HP ITANIUM by ontape