Monitoring IDS 11.50.FC6 in Fast Recovery mode
Good morning,
I have a situation where my development database IDS 11.50.FC6 went down last
night. I've restarted the DB engine with oninit. The Informix state is in Fast
Recovery mode after for a very large transaction (inserting a few million rows
into a table).
Can you recommend any onstat command for monitoring status / progress? I'm
being asked to report on "how long will this take?!?"
Thanks for any suggestions.
Sincerely,
Jonathan Smaby
Pomona College
-------------------------------------------------------------
This message has been scanned by Postini anti-virus software.
On 05/12/11 19:02, Jonathan Smaby wrote:
> Good morning,
>
> I have a situation where my development database IDS 11.50.FC6 went down last
> night. I've restarted the DB engine with oninit. The Informix state is in
Fast
> Recovery mode after for a very large transaction (inserting a few million
rows
> into a table).
>
> Can you recommend any onstat command for monitoring status / progress? I'm
> being asked to report on "how long will this take?!?"
>
> Thanks for any suggestions.
>
> Sincerely,
>
> Jonathan Smaby
> Pomona College
>
I'm expecting that the time is being take rolling back the transaction as
opposed to replaying it. Onstat -x tells you where that transaction started,
ie where you have to go back to. Let's call this logpos S.
Do an onstat -l and get the current log uniqid and current number of used
pages. This gives you the current logpos, let's call it C.
Now do an onlog -n <current log uniqid>. You should see CLR records. isolate
the one for logpos C: it will point to another logical log record. This is the
one that has been rolled back, let's call it R.
You now have two pieces of information:
- C-R is how much you have rolled back
- R-S is how much you have still to roll back.
--
HTH,
Marco
______________________________________________________________________________
Marco Greco /UK /IBM Standard disclaimers apply!
Structured Query Scripting Language http://www.4glworks.com/sqsl.htm
4glworks http://www.4glworks.com
Informix on Linux http://www.4glworks.com/ifmxlinux.htm
It will take about as long to unwind the huge transaction as it did to
create it in the first place. So, if the transaction was running for 8
hours at the time the engine crashed, an 8 hour recovery wouldn't be
impossible. Good argument for breaking that huge transaction up into
smaller logical transactions!
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
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 Mon, Dec 5, 2011 at 2:02 PM, Jonathan Smaby
<Jonathan.Smaby@pomona.edu>wrote:
> Good morning,
>
> I have a situation where my development database IDS 11.50.FC6 went down
> last
> night. I've restarted the DB engine with oninit. The Informix state is in
> Fast
> Recovery mode after for a very large transaction (inserting a few million
> rows
> into a table).
>
> Can you recommend any onstat command for monitoring status / progress? I'm
> being asked to report on "how long will this take?!?"
>
> Thanks for any suggestions.
>
> Sincerely,
>
> Jonathan Smaby
> Pomona College
>
> -------------------------------------------------------------
> This message has been scanned by Postini anti-virus software.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--14dae93408af428b0804b35e52d4