IDS Forum

Re: Backup is Blocked:ARCHIVE when temp space bein

Posted By: Fernando Nunes
Date: Tuesday, 19 April 2016, at 11:45 a.m.

In Response To: Backup is Blocked:ARCHIVE when temp space being us (Malc P)

The backup doesn't shift transaction activity to DBSPACETEMP. It just saves
the before image of all the changed pages (first time each page is changed)
in DBSPACETEMP.
But it does this after the backup effectively starts and it seems that your
system got hang at the checkpoint which is triggered by the backup start.

A possible reason for that would be that some task got stuck into an
exclusive section (X flag in onstat -u). When you kiiled some things it may
have released the checkpoint and the backup probably started.

It's impossible to tell without further data... If the backup has not free
space in DBSPACETEMP to save the before image of the pages being changed it
should exit with an error.

Furthermore.... there are good reasons to be on supported versions.
It's not clear if you mean you're paying support but can't have it because
the version is not supported (that would be even worse) or if you're not
paying support.

Regards.

On Tue, Apr 19, 2016 at 3:50 PM, Malc P <malcrp@gmail.com> wrote:

> IDS 9.30HC5 on HP 11i therefore no support :-(
>
> We had a weird hang on our live system last night.
> There was a 4gl running which was doing a high volume of writes to a temp
> table (created explicitly, so would have been in DBSPACETEMP) and had been
> running for several hours, expected to run at least overnight; our instance
> backup (ontape -s -L 0, nothing special) started under cron control at 8pm.
> NB DBSPACETEMP lists only one dbspace; the relevant database uses Buffered
> logging.
>
> We came in this morning and the whole system was hung. The backup had done
> nothing (although ps -ef showed 'ontape -s -L 0' was running) but onstats
> showed "Blocked:ARCHIVE" in the info line. A simple 4GL running a
> single-table query (a high-cost sequential scan, unfortunately, that can't
> really be optimised as it mainly filters on fields with only two or three
> values in a table of 49,000,000 rows, and also has an OR clause...) under
> our job scheduler had hung, as also had the big 4GL.
>
> After killing a couple of processes it all burst back into life, but the
> system has been incredibly sluggish all day (we're doing an instance
> restart this evening).
>
> I know that a backup switches all transaction activity into DBSPACETEMP for
> the duration; would this have been somehow affected by the 4GL which was
> already running and using DBSPACETEMP?
>
> --94eb2c1246bac7882f0530d798af
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

--001a113f2d2af830bd0530d856b3

Messages In This Thread

• Backup is Blocked:ARCHIVE when temp space being us
  Malc P -- Tuesday, 19 April 2016, at 10:50 a.m.
  • Re: Backup is Blocked:ARCHIVE when temp space bein
    Marcus Haarmann -- Tuesday, 19 April 2016, at 11:39 a.m.
    • Re: Backup is Blocked:ARCHIVE when temp space ....
      Malc P -- Tuesday, 19 April 2016, at 12:01 p.m.
  • Re: Backup is Blocked:ARCHIVE when temp space bein
    Fernando Nunes -- Tuesday, 19 April 2016, at 11:45 a.m.
    • Re: Backup is Blocked:ARCHIVE when temp space ....
      Malc P -- Tuesday, 19 April 2016, at 3:08 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.