Restarting a failed Load Resume

Raymond Bell

Restarting a failed Load Resume
Colleagues, no pressure on this; it hasn't happened, I'm just wondering what
would.

If I'm running a Load Resume Log No into a tablespace with existing data and
the load fails with a B37 on the tablespace, where do I stand? Assume I
have all necessary workfiles (sysut1, sortout, etc). Do I have to recover,
after altering priqty and secqty? Would a stop-DF/DSS move-start job (to
reduce extents) be enough to enable a successful restart(commit)? Could I
even stop it with a utility pending? As you can tell, I haven't had a
failed load resume for awhile.

Cheers,


Raymond



Sanjeev (CTS) S

Re: Restarting a failed Load Resume
(in response to Raymond Bell)
Hi Raymond,

I assume you are talking about full underlying VSAM dataset for the
tablespace.

I think the load job will fail with Resource Unavailable and DB2 will put
the tablespace in RECP status. If you need the data which was existing, you
need to recover the tablespace with previous image copy + log ,after
altering the priqty and secqty. After this recovery you will loose the data
which was loaded because of LOG NO, so question of restrting the utility
doesn't look logical. I did face this situation a lot in my previous work
and if i am correct then you will be left with no other options other than
terminating the utility and starting it again after recovering the
tablespace (if DF/DSS is not used).

I do not have much idea about using DF/DSS but it is documented in the
Utility Guide -- Monitoring and Controlling Online Utilities.

I am not sure if this is the sufficient idea about your questions but still
HTH.

Regards,
Sanjeev



> -----Original Message-----
> From: Bell, Raymond W [SMTP:[login to unmask email]
> Sent: Tuesday, January 09, 2001 8:05 AM
> To: [login to unmask email]
> Subject: Restarting a failed Load Resume
>
> Colleagues, no pressure on this; it hasn't happened, I'm just wondering
> what
> would.
>
> If I'm running a Load Resume Log No into a tablespace with existing data
> and
> the load fails with a B37 on the tablespace, where do I stand? Assume I
> have all necessary workfiles (sysut1, sortout, etc). Do I have to
> recover,
> after altering priqty and secqty? Would a stop-DF/DSS move-start job (to
> reduce extents) be enough to enable a successful restart(commit)? Could I
> even stop it with a utility pending? As you can tell, I haven't had a
> failed load resume for awhile.
>
> Cheers,
>
>
> Raymond
>
>
>
>
>
-----------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------
This e-mail and any files transmitted with it are for the sole use
of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message. Any unauthorised review, use, disclosure,
dissemination, forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and may be unlawful.

Visit us at http://www.cognizant.com
----------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------



Raymond Bell

Re: Restarting a failed Load Resume
(in response to Sanjeev (CTS) S)
Hi Sanjeev,

I guess I knew what you're saying; I just wanted someone to confirm it.
Basically TSs involved in failed Load Resumes (when they fail 'cause the TS
is full) have to be recovered to before the start of the load. Not what I
wanted to hear, but, hey, it's a tough world out there.

Cheers,


Raymond


> -----Original Message-----
> From: S, Sanjeev (CTS) [SMTP:[login to unmask email]
> Sent: Tuesday, 9 January 2001 4:54 pm
> To: [login to unmask email]
> Subject: Re: Restarting a failed Load Resume
>
> Hi Raymond,
>
> I assume you are talking about full underlying VSAM dataset for the
> tablespace.
>
> I think the load job will fail with Resource Unavailable and DB2 will
> put
> the tablespace in RECP status. If you need the data which was existing,
> you
> need to recover the tablespace with previous image copy + log ,after
> altering the priqty and secqty. After this recovery you will loose the
> data
> which was loaded because of LOG NO, so question of restrting the utility
> doesn't look logical. I did face this situation a lot in my previous work
> and if i am correct then you will be left with no other options other than
> terminating the utility and starting it again after recovering the
> tablespace (if DF/DSS is not used).
>
> I do not have much idea about using DF/DSS but it is documented in the
> Utility Guide -- Monitoring and Controlling Online Utilities.
>
> I am not sure if this is the sufficient idea about your questions but
> still
> HTH.
>
> Regards,
> Sanjeev



[login to unmask email]

Re: Restarting a failed Load Resume
(in response to Raymond Bell)
Raymond,

I missed the initial note you sent out, but if it died in the build phase
for the indexes then just reset the pending flags and rebuild your indexes.
If it was in the load phase then recovery is basically it unless you have
an unload to load back in and then rerun the load resume.

Cheers,
Jay


Jay Reavill
[login to unmask email]
IBM Global Services
Tampa, Florida
Tel: (813) 801-7303, Tie Line 8-427-7303
-----------------------------------------------------
Happiness is not around the corner.
Happiness is the corner.
- Bavarian Motor Works
-----------------------------------------------------


"Bell, Raymond W" <[login to unmask email]>@RYCI.COM> on 01/09/2001
05:44:35 PM

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

Sent by: DB2 Data Base Discussion List <[login to unmask email]>


To: [login to unmask email]
cc:
Subject: Re: Restarting a failed Load Resume



Hi Sanjeev,

I guess I knew what you're saying; I just wanted someone to confirm it.
Basically TSs involved in failed Load Resumes (when they fail 'cause the TS
is full) have to be recovered to before the start of the load. Not what I
wanted to hear, but, hey, it's a tough world out there.

Cheers,


Raymond


> -----Original Message-----
> From: S, Sanjeev (CTS) [SMTP:[login to unmask email]
> Sent: Tuesday, 9 January 2001 4:54 pm
> To: [login to unmask email]
> Subject: Re: Restarting a failed Load Resume
>
> Hi Raymond,
>
> I assume you are talking about full underlying VSAM dataset for the
> tablespace.
>
> I think the load job will fail with Resource Unavailable and DB2 will
> put
> the tablespace in RECP status. If you need the data which was existing,
> you
> need to recover the tablespace with previous image copy + log ,after
> altering the priqty and secqty. After this recovery you will loose the
> data
> which was loaded because of LOG NO, so question of restrting the utility
> doesn't look logical. I did face this situation a lot in my previous work
> and if i am correct then you will be left with no other options other
than
> terminating the utility and starting it again after recovering the
> tablespace (if DF/DSS is not used).
>
> I do not have much idea about using DF/DSS but it is documented in the
> Utility Guide -- Monitoring and Controlling Online Utilities.
>
> I am not sure if this is the sufficient idea about your questions but
> still
> HTH.
>
> Regards,
> Sanjeev








Raymond Bell

Re: Restarting a failed Load Resume
(in response to damcon2@US.IBM.COM)
Jay,

Thanks for the depressing confirmation. I was specifically interested in
failed Load Resume jobs that fail in the load phase. Looks like I'd be up
for a recovery. Although someone out there suggested as an alternative to
basically rebuild (gee, I'm SO getting the hang of the new V6 terminology)
the indexes at the point of load phase failure and rerun the Load Resume,
ignoring the resultant duplicates and SYSERR file. Depends on how far into
the load you were, I guess, and whether or not you can go back.

Cheers,


Raymond
PS. I'm an Audi man myself...


> -----Original Message-----
> From: Jackson Reavill [SMTP:[login to unmask email]
> Sent: Thursday, 11 January 2001 1:34 am
> To: [login to unmask email]
> Subject: Re: Restarting a failed Load Resume
>
> Raymond,
>
> I missed the initial note you sent out, but if it died in the build phase
> for the indexes then just reset the pending flags and rebuild your
> indexes.
> If it was in the load phase then recovery is basically it unless you have
> an unload to load back in and then rerun the load resume.
>
> Cheers,
> Jay
>
>
> Jay Reavill
> [login to unmask email]
> IBM Global Services
> Tampa, Florida
> Tel: (813) 801-7303, Tie Line 8-427-7303
> -----------------------------------------------------
> Happiness is not around the corner.
> Happiness is the corner.
> - Bavarian Motor Works
> -----------------------------------------------------