Logical log backup aborted (during ontape -r)
A user restoring a production ontape backup into a test instance on IDS 9.40/AIX saw "I/O chunk is inconsistent chunk 19" and "Logical Log Backup Aborted" in online.log. Suggestions included disk failure, a full filesystem, and running oncheck, but Art Kagel explained that "inconsistent" (as opposed to "down") chunks mean a restore was aborted or the engine was shut down before fast recovery/log rollforward completed; the fix is to redo the full restore and then run onmode -m and wait until onstat reports On-Line. The user had indeed killed the first attempt with onmode -k; rerunning ontape -r and letting it reach quiescent mode before onmode -m brought the instance online successfully.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
I have the following message in online.log during 'ontape -r'
14:50:01 Logical Log 223793 - Backup Started
14:50:01 I/O chunk is inconsistent chunk 19, pagenum 452853, pagecnt 7
14:50:01 Logical Log 223793 - Backup Aborted
Error reading from the disk, Error No. = 0.
The instance version is IDS 940FC6 running on AIX box
Can someone help ? Please
I'm confused. "ontape -r" is a restore not a backup! Did you mean "onstat
-s..."?
Inconsistent chunks are the result of a restore that was aborted or if the
engine was shutdown after a restore completed but before the engine was
brought to full online mode to complete the fast recovery and logical log
rollforward/rollback processing. If either of these is the case, then you
will have to start the restore again, make sure that it completes and that
you have restored any level 1 or level 2 archives and any logical logs that
you also want to restore, and then after the ontape completes, you MUST run
"onmode -m" and WAIT until the engine comes to full online mode before
shutting it down at all (the engine is online when the "onstat -" headline
reports that the mode is "On-Line".
You should note that Informix version 9.40 went out-of-support in September
2009. You should upgrade to the latest 11.50 or 11.70 release and
reestablish support for your site. IBM will continue/reestablish your 9.40
support (down system and critical bugs only IB) for 12 months if you agree
to upgrade to 11.xx before the end of the year.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Fri, Nov 5, 2010 at 11:00 AM, GILLES TCHAPPI <ntgilfr@voila.fr> wrote:
> Hi,
>
> I have the following message in online.log during 'ontape -r'
>
> 14:50:01 Logical Log 223793 - Backup Started
> 14:50:01 I/O chunk is inconsistent chunk 19, pagenum 452853, pagecnt 7
> 14:50:01 Logical Log 223793 - Backup Aborted
>
> Error reading from the disk, Error No. = 0.
>
> The instance version is IDS 940FC6 running on AIX box
>
> Can someone help ? Please
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0016364ec7a4fb673904944fa187
It sounds like the disk that chunk 19 is on might be having problems. If so,
you could verify with the server's syslog file.
Bob
----- Original Message -----
From: "GILLES TCHAPPI" <ntgilfr@voila.fr>
To: ids@iiug.org
Sent: Friday, November 5, 2010 11:00:12 AM
Subject: Logical log backup aborted (during ontape -r) [21868]
Hi,
I have the following message in online.log during 'ontape -r'
14:50:01 Logical Log 223793 - Backup Started
14:50:01 I/O chunk is inconsistent chunk 19, pagenum 452853, pagecnt 7
14:50:01 Logical Log 223793 - Backup Aborted
Error reading from the disk, Error No. = 0.
The instance version is IDS 940FC6 running on AIX box
Can someone help ? Please
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Hello, it seems you have some troubles, really:
start checking your data consistency using the following commands:
oncheck -cR
oncheck -ce
oncheck -cc [database_name] -> run this for every db on your instance, ok?
oncheck -cD [database_name] -> " " "
oncheck -cI [database_name] -> " " "
and look for some message on the output incating any kind of error ok?
If nothing wrong is found, report us and maybe some other check can be done.
Best regards.
Em 05/11/2010 11:00, GILLES TCHAPPI escreveu:
> Hi,
>
> I have the following message in online.log during 'ontape -r'
>
> 14:50:01 Logical Log 223793 - Backup Started
> 14:50:01 I/O chunk is inconsistent chunk 19, pagenum 452853, pagecnt 7
> 14:50:01 Logical Log 223793 - Backup Aborted
>
> Error reading from the disk, Error No. = 0.
>
> The instance version is IDS 940FC6 running on AIX box
>
> Can someone help ? Please
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Alexandre Marini
Tecnologia da Informação - DBA
SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix
Cert-Info-Mgmt_color <Cert-Info-Mgmt_color.jpg>
IBM Informix Dynamic Server Certified Professional V10 / V11
Art,
I'm trying to restore an production database (backup done with ontape), in a
test database (using ontape -r) and I've the messages in the online log
Regards
So, as I already said, i t looks like the restore aborted, or someone killed
it, or it completed but the instance was shutdown (onmode -ky) before the
engine was brought to full online status. Those are the ONLY reasons that I
am aware of that the chunks would be reported to be "inconsistent". The
chunk state for a chunk that is not functioning correctly or has been
corrupted is 'down' not 'inconsistent'. Inconsistent is reserved for a
chunk that was restored but for which fast recovery was not completed. In
any case, regardless of the reason for the inconsistency, you will have to
repeat the entire restore and when it finishes bring the engine to fully
online status with "onmode -m" and wait for the engine to report that it is
"On-Line" in the onstat header line (also the onstat return code will be '5'
at that time) as I stated in my first response.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Fri, Nov 5, 2010 at 11:45 AM, GILLES TCHAPPI <ntgilfr@voila.fr> wrote:
> Art,
>
> I'm trying to restore an production database (backup done with ontape), in
> a
> test database (using ontape -r) and I've the messages in the online log
>
> Regards
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--00163630f041402dd6049450483f
or possibly because the restore is being done to a file system and the file
system got full..
From: "Art Kagel" <art.kagel@gmail.com>
To: ids@iiug.org
Date: 11/05/2010 10:54 AM
Subject: Re: Logical log backup aborted (during ontape -r) [21875]
Sent by: ids-bounces@iiug.org
So, as I already said, i t looks like the restore aborted, or someone
killed
it, or it completed but the instance was shutdown (onmode -ky) before the
engine was brought to full online status. Those are the ONLY reasons that I
am aware of that the chunks would be reported to be "inconsistent". The
chunk state for a chunk that is not functioning correctly or has been
corrupted is 'down' not 'inconsistent'. Inconsistent is reserved for a
chunk that was restored but for which fast recovery was not completed. In
any case, regardless of the reason for the inconsistency, you will have to
repeat the entire restore and when it finishes bring the engine to fully
online status with "onmode -m" and wait for the engine to report that it is
"On-Line" in the onstat header line (also the onstat return code will be
'5'
at that time) as I stated in my first response.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or
by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Fri, Nov 5, 2010 at 11:45 AM, GILLES TCHAPPI <ntgilfr@voila.fr> wrote:
> Art,
>
> I'm trying to restore an production database (backup done with ontape),
in
> a
> test database (using ontape -r) and I've the messages in the online log
>
> Regards
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--00163630f041402dd6049450483f
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
And so the restore aborted....
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Fri, Nov 5, 2010 at 12:00 PM, Madison Pruet <mpruet@us.ibm.com> wrote:
> or possibly because the restore is being done to a file system and the file
> system got full..
>
> From: "Art Kagel" <art.kagel@gmail.com>
>
> To: ids@iiug.org
>
> Date: 11/05/2010 10:54 AM
>
> Subject: Re: Logical log backup aborted (during ontape -r) [21875]
>
> Sent by: ids-bounces@iiug.org
>
> So, as I already said, i t looks like the restore aborted, or someone
> killed
> it, or it completed but the instance was shutdown (onmode -ky) before the
> engine was brought to full online status. Those are the ONLY reasons that I
>
> am aware of that the chunks would be reported to be "inconsistent". The
> chunk state for a chunk that is not functioning correctly or has been
> corrupted is 'down' not 'inconsistent'. Inconsistent is reserved for a
> chunk that was restored but for which fast recovery was not completed. In
> any case, regardless of the reason for the inconsistency, you will have to
> repeat the entire restore and when it finishes bring the engine to fully
> online status with "onmode -m" and wait for the engine to report that it is
>
> "On-Line" in the onstat header line (also the onstat return code will be
> '5'
> at that time) as I stated in my first response.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> IIUG Board of Directors (art@iiug.org)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and
> do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
> organization with which I am associated either explicitly, implicitly, or
> by
> inference. Neither do those opinions reflect those of other individuals
> affiliated with any entity with which I am affiliated nor those of the
> entities themselves.
>
> On Fri, Nov 5, 2010 at 11:45 AM, GILLES TCHAPPI <ntgilfr@voila.fr> wrote:
>
> > Art,
> >
> > I'm trying to restore an production database (backup done with ontape),
> in
> > a
> > test database (using ontape -r) and I've the messages in the online log
> >
> > Regards
> >
> >
> >
> >
>
>
>
*******************************************************************************
>
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --00163630f041402dd6049450483f
>
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0016361e7c68bc21f00494506e58
Hi,
The restore did not abort. When I saw the message for the first time, I shut
down the database using 'onmode 'k'.
I ran the 'ontape -r' again, I although I have the messages in the online.log,
I did not stop the database and let the 'ontape -r' run until it brings the
database on Quiescent Mode and then launched 'onmode -m'
The database is now running on 'On Line' mode
Thanks to all
Special thanks to Art
Best Regards,
Gilles