John, Glad to be of assistance. Hope to see you soon. Regards, Phil
----- Original Message -----
From: "John Lantz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 25, 2003 9:59 AM
Subject: Re: [DB2EUG] REORGs on DB2 UDB


>
> Phil - great tip on the "GET SNAPSHOT FOR TABLES...".  I never realized
> that information would be here while a reorg was going on.  FYI - I just
> did a reorg this morning, and the "ROWS READ" appears to be double the
> number of rows in the table.
>
> Thanks.
>
>
> Phil Gunning <[EMAIL PROTECTED]>@Lugwash.org on 02/24/2003 04:26:02 PM
>
> Please respond to Phil Gunning <[EMAIL PROTECTED]>
>
> Sent by:    [EMAIL PROTECTED]
>
>
> To:    [EMAIL PROTECTED]
> cc:    [EMAIL PROTECTED]
>
> Subject:    Re: [DB2EUG] REORGs on DB2 UDB
>
>
> Tim, you can use the db2 list history command, and table snapshots to
> monitor and check on status of a reorg. You can use load query to obtain
> the
> state of a table (v8) , and any reorg errors are written to the
db2diag.log
> and administration notification event log, and SQLCA is written to the
> history file. You will want to take a backup of the tablespace after
reorg,
> if you don't  and you end up doing a roll forward, DB2 will roll forward
> through the reorg. The temporary files will be created along the
TEMPSPACE1
> path or tablespace path involved if using in-place. Cheers, Phil
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: "Phil Gunning" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, February 24, 2003 2:43 PM
> Subject: Re: [DB2EUG] REORGs on DB2 UDB
>
>
> >
> > I looked at this manual first.  It mentions to not delete temporary
files
> > if a REORG abends.  It doesn't however mention where these temporary
> files
> > are, how to use them in a restart situation, or how to display what step
> > the utility is in.  That is the information that I am particularly
> > interested in.  According to the Performance Administration guide, it
> > states :
> >
> > "If a REORG utility does not complete successfully, do NOT delete the
> > temporary files, tables or tablespaces.  These files are used by the
> > Database Manager to roll back the changes made by the REORG utility, or
> to
> > complete the reorganization, depending on how far the reorganization had
> > progressed before the failure."
> >
> > Does this mean that DB2 will cleanup after itself if a REORG fails for
> some
> > reason and that there is no manual intervention necessary?
> >
> > Tim
> >
> >
> >
> >                       Phil Gunning
> >                       <[EMAIL PROTECTED]        To:
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> >                       .net>                    cc:
> >                                                Subject:  Re: [DB2EUG]
> REORGs on DB2 UDB
> >                       02/24/2003 12:51
> >                       PM
> >
> >
> >
> >
> >
> >
> > Tim, The DB2 UDB Command Reference is a good reference. Phil
> >
> >
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, February 24, 2003 1:37 PM
> > Subject: [DB2EUG] REORGs on DB2 UDB
> >
> >
> > > Hello List,
> > >
> > > I am wondering if there is documentation on the actual steps involved
> > with
> > > a REORG (or any other utility) on DB2 UDB and what the restart options
> > are
> > > should a REORG (or any other utility) abend.  For S/390, there is very
> > > detailed documentation in the utility guide on the steps of a REORG
and
> > how
> > > to restart a REORG should one fail.  Are there ways to display the
> > utility
> > > to see what steps they are in, what the status of the utility is, etc?
> > >
> > > Any help and direction is appreciated.
> > >
> > > Thanks,
> > > Tim
> > >
> > >
> > >
> > >
> > > -
> > > :::  When replying to the list, please use 'Reply-All' and make sure
> > > :::  a copy goes to the list ([EMAIL PROTECTED]).
> > > ***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> > > ***  For more information, check http://www.db2eug.uni.cc
> > >
> >
> >
> >
> >
> >
> >
> >
> > -
> > :::  When replying to the list, please use 'Reply-All' and make sure
> > :::  a copy goes to the list ([EMAIL PROTECTED]).
> > ***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> > ***  For more information, check http://www.db2eug.uni.cc
>
> -
> :::  When replying to the list, please use 'Reply-All' and make sure
> :::  a copy goes to the list ([EMAIL PROTECTED]).
> ***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
>  ***  For more information, check http://www.db2eug.uni.cc
>
>
>
>
>  ******************* PLEASE NOTE *******************
>  This E-Mail/telefax message and any documents accompanying this
>  transmission may contain privileged and/or confidential information and
is
>  intended solely for the addressee(s) named above.  If you are not the
>  intended addressee/recipient, you are hereby notified that any use of,
>  disclosure, copying, distribution, or reliance on the contents of this
>  E-Mail/telefax information is strictly prohibited and may result in legal
>  action against you. Please reply to the sender advising of the error in
>  transmission and immediately delete/destroy the message and any
>  accompanying documents.  Thank you.
>
>
> -
> :::  When replying to the list, please use 'Reply-All' and make sure
> :::  a copy goes to the list ([EMAIL PROTECTED]).
> ***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> ***  For more information, check http://www.db2eug.uni.cc
>


-
:::  When replying to the list, please use 'Reply-All' and make sure
:::  a copy goes to the list ([EMAIL PROTECTED]).
***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
***  For more information, check http://www.db2eug.uni.cc

Reply via email to