Tablespace status AREST

Joop Ammerlaan

Tablespace status AREST
Can anyone tell me how i can get rid of the AREST status for a tablespace?

regards, Joop Ammerlaan



[login to unmask email]

Re: Tablespace status AREST
(in response to Joop Ammerlaan)
DB2 V6 Command Reference manual indicates the following:

AREST indicates that the object ( a table space , index space or a physical
partition of a table space or index space ) is
in a Advisory Restart Pending State. If backout activity against the object is
not already underway, it should be
initiated either by issuing the RECOVER POSTPONED command or by recycling the
system with
the system parameter LBACKOUT=AUTO

HTH

Shan




[login to unmask email] on 11/13/2000 06:39:15 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Tablespace status AREST



Can anyone tell me how i can get rid of the AREST status for a tablespace?

regards, Joop Ammerlaan








Sanjay (Exchange) Jain

Re: Tablespace status AREST
(in response to Shan_Leatherman/MO/americancentury@americancentury.com)
AREST implies that a pageset has some recovery task pending against it. Try
the -RECOVER POSTPONED command. It would initiate back out processing for
any UR pending against the tablespace in question.

HTH

Sanjay Jain

> -----Original Message-----
> From: [login to unmask email] [SMTP:[login to unmask email]
> Sent: Monday, November 13, 2000 7:39 AM
> To: [login to unmask email]
> Subject: Tablespace status AREST
>
> Can anyone tell me how i can get rid of the AREST status for a tablespace?
>
> regards, Joop Ammerlaan
>
>
>
>
>


**********************************************************************
Please be aware that, notwithstanding the fact that the person sending
this communication has an address in Bear Stearns' e-mail system, this
person is not an employee, agent or representative of Bear Stearns.
Accordingly, this person has no power or authority to represent, make
any recommendation, solicitation, offer or statements or disclose
information on behalf of or in any way bind Bear Stearns or any of its
affiliates.
**********************************************************************



Robert Jans

Re: Tablespace status AREST
(in response to Sanjay (Exchange) Jain)
Shan and Joop;
Yes, Shan, you are correct with what SHOULD happen.

However, we have encountered a problem on our Aceptance system where DB2
crashed and then crashed again on restart before recover was complete. However
it ahppenned,DB2 left the AREST flag set and DID NOT!!! finish
backour/recovery. We have been partly successful in re-creating this. We can't
make the AREST stick around but we can make DB2 crash ansd burn on the
recover/backout.It's pretty simple on our system (DB2 V6.1,Fix tape from Oct
/00 applied and hipers up till last Monday) , parallel jobs updating/inserting
a partitioned table at the same time and have DB2 fail. We caused the first
failure by cancelling the IRLM. DB2 will fail every time on the restart until
you do a conditional restart which sorta leaves the apps twisting in the
wind...............

We do have an open problem with IBM.

HTH,

Robert Jans
Albertsons, Inc
155 North 400 West
Mail Drop 4427
Salt Lake City, UT
84103
(801) 961-3212
[login to unmask email]
<Standard Disclaimers Apply>

------------------( Forwarded letter 1 follows )---------------------
Date: Mon, 13 Nov 2000 09:32:32 -0600
To: [login to unmask email]
From: [login to unmask email]
Sender: [login to unmask email]
Reply-To: DB2.Data.Base.Discussion.List[DB2-L]@RYCI.COM
Subject: Re: Tablespace status AREST

DB2 V6 Command Reference manual indicates the following:

AREST indicates that the object ( a table space , index space or a physical
partition of a table space or index space ) is
in a Advisory Restart Pending State. If backout activity against the object is
not already underway, it should be
initiated either by issuing the RECOVER POSTPONED command or by recycling the
system with
the system parameter LBACKOUT=AUTO

HTH

Shan




[login to unmask email] on 11/13/2000 06:39:15 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Tablespace status AREST



Can anyone tell me how i can get rid of the AREST status for a tablespace?

regards, Joop Ammerlaan











Richard Cotterill

Re: Tablespace status AREST
(in response to Robert Jans)
Hi,
We had this problem some time ago where POSTPONED RECOVERY option did not work (a bug).

A DB2 COLD START (drastic)
or CRCR with BACKOUT=NO (need to confirm this as not at work)

If want details email me on [login to unmask email]
Richard



[login to unmask email] wrote:

> Can anyone tell me how i can get rid of the AREST status for a tablespace?
>
> regards, Joop Ammerlaan
>
>
>

--
-----------------------------------------------------
Click here for Free Video!!
http://www.gohip.com/freevideo/



[login to unmask email]

Re: Tablespace status AREST
(in response to Richard Cotterill)
Sounds like your in good hands if IBM is working on it. It almost sounds like
DB2 gets confused if it encounters
multiple crashes and didn't get objects recovered from the first crash, before
it crashes again.

I imagine you've checked all the obvious things like having all the logs and
image copies necessary to perform
the recovery and that no objects were altered in the mean time.

Good luck. Hopefully you don't experience this problem in your production
environment.





Robert Jans <[login to unmask email]> on 11/13/2000 09:55:00 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Re: Tablespace status AREST



Shan and Joop;
Yes, Shan, you are correct with what SHOULD happen.

However, we have encountered a problem on our Aceptance system where DB2
crashed and then crashed again on restart before recover was complete. However
it ahppenned,DB2 left the AREST flag set and DID NOT!!! finish
backour/recovery. We have been partly successful in re-creating this. We can't
make the AREST stick around but we can make DB2 crash ansd burn on the
recover/backout.It's pretty simple on our system (DB2 V6.1,Fix tape from Oct
/00 applied and hipers up till last Monday) , parallel jobs updating/inserting
a partitioned table at the same time and have DB2 fail. We caused the first
failure by cancelling the IRLM. DB2 will fail every time on the restart until
you do a conditional restart which sorta leaves the apps twisting in the
wind...............

We do have an open problem with IBM.

HTH,

Robert Jans
Albertsons, Inc
155 North 400 West
Mail Drop 4427
Salt Lake City, UT
84103
(801) 961-3212
[login to unmask email]
<Standard Disclaimers Apply>

------------------( Forwarded letter 1 follows )---------------------
Date: Mon, 13 Nov 2000 09:32:32 -0600
To: [login to unmask email]
From: [login to unmask email]
Sender: [login to unmask email]
Reply-To: DB2.Data.Base.Discussion.List[DB2-L]@RYCI.COM
Subject: Re: Tablespace status AREST

DB2 V6 Command Reference manual indicates the following:

AREST indicates that the object ( a table space , index space or a physical
partition of a table space or index space ) is
in a Advisory Restart Pending State. If backout activity against the object is
not already underway, it should be
initiated either by issuing the RECOVER POSTPONED command or by recycling the
system with
the system parameter LBACKOUT=AUTO

HTH

Shan




[login to unmask email] on 11/13/2000 06:39:15 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Tablespace status AREST



Can anyone tell me how i can get rid of the AREST status for a tablespace?

regards, Joop Ammerlaan


















Kirk Hampton

Re: Tablespace status AREST
(in response to Shan_Leatherman/MO/americancentury@americancentury.com)
We also encountered this problem after an Abend involving parallelism.
We still have an open problem with IBM on it. I am the Sysprog, but the DBA's
here chose to work around the AREST by Dropping/ReCreating the tablespace
and restoring with DSN1COPY from Image Copies. Fortunately, this happened
on our Development DB2, not Production.





"Shan_Leatherman/MO/americancentury"@AMERICANCENTURY.COM on 11/14/2000 07:50:19
AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Kirk Hampton/Texas Utilities)
Subject: Re: Tablespace status AREST



Sounds like your in good hands if IBM is working on it. It almost sounds like
DB2 gets confused if it encounters
multiple crashes and didn't get objects recovered from the first crash, before
it crashes again.

I imagine you've checked all the obvious things like having all the logs and
image copies necessary to perform
the recovery and that no objects were altered in the mean time.

Good luck. Hopefully you don't experience this problem in your production
environment.





Robert Jans <[login to unmask email]> on 11/13/2000 09:55:00 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Re: Tablespace status AREST



Shan and Joop;
Yes, Shan, you are correct with what SHOULD happen.

However, we have encountered a problem on our Aceptance system where DB2
crashed and then crashed again on restart before recover was complete. However
it ahppenned,DB2 left the AREST flag set and DID NOT!!! finish
backour/recovery. We have been partly successful in re-creating this. We can't
make the AREST stick around but we can make DB2 crash ansd burn on the
recover/backout.It's pretty simple on our system (DB2 V6.1,Fix tape from Oct
/00 applied and hipers up till last Monday) , parallel jobs updating/inserting
a partitioned table at the same time and have DB2 fail. We caused the first
failure by cancelling the IRLM. DB2 will fail every time on the restart until
you do a conditional restart which sorta leaves the apps twisting in the
wind...............

We do have an open problem with IBM.

HTH,

Robert Jans
Albertsons, Inc
155 North 400 West
Mail Drop 4427
Salt Lake City, UT
84103
(801) 961-3212
[login to unmask email]
<Standard Disclaimers Apply>

------------------( Forwarded letter 1 follows )---------------------
Date: Mon, 13 Nov 2000 09:32:32 -0600
To: [login to unmask email]
From: [login to unmask email]
Sender: [login to unmask email]
Reply-To: DB2.Data.Base.Discussion.List[DB2-L]@RYCI.COM
Subject: Re: Tablespace status AREST

DB2 V6 Command Reference manual indicates the following:

AREST indicates that the object ( a table space , index space or a physical
partition of a table space or index space ) is
in a Advisory Restart Pending State. If backout activity against the object is
not already underway, it should be
initiated either by issuing the RECOVER POSTPONED command or by recycling the
system with
the system parameter LBACKOUT=AUTO

HTH

Shan




[login to unmask email] on 11/13/2000 06:39:15 AM



Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Shan Leatherman/MO/americancentury)
Subject: Tablespace status AREST



Can anyone tell me how i can get rid of the AREST status for a tablespace?

regards, Joop Ammerlaan