That's where you pay IBM for software maintenance. The Database or storage
management person you will be put into contact with will understand the
ramifications of killing the job and be able to do some diagnostics to
figure out what's going on. And advise you how to recover if needed.
My own thought would be you would need the physical (table) and any logical
files (which consists of an index and a view), but also any independent
index and view objects, as well as triggers. In short, potentially quite
a bit.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Maassel, John R.
Sent: Monday, October 17, 2016 7:47 AM
To: Midrange Systems Technical Discussion
Subject: RE: [EXTERNAL] Re: reorg not finishing
First question is can we kill that job? The reorg does not allow cancel.
Second, if we did, which objects would we have to restore? The logical file,
for sure, but what of the physical and the other indexes?
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Richard Reeve
Sent: Monday, October 17, 2016 8:41 AM
To: Midrange Systems Technical Discussion
Subject: [EXTERNAL] Re: reorg not finishing
John
If you have a good backup, you may want to kill the job. A faster way
to complete the reorg would be to delete all depended on files (LF's and
indexes) prior to the reorg then simply recreate them after the physical
file has been reorganized.
Best of luck!
Rich
On Mon, Oct 17, 2016 at 8:31 AM, Maassel, John R. <John_Maassel@xxxxxxxxxxxx
wrote:
There is a reorg job on our dev box (i 7.2) that's been running for a
5 days. It's been on the IDX- stage on one index for almost 4 days.
This is a rather large file, containing a billion records and 11
access paths. It's stuck on #4.
It doesn't appear that the system is working on it. This is the only
task the machine had all weekend and it's still right where it was
when I left on Friday. CPU utilization for this job is 0.7% and
overall CPU is 2-3%. I checked disk stats and they're only 3% busy, so I
don't see a bottleneck.
Unfortunately, it was submitted with "Allow Cancel = NO" so I don't
think we can stop it.
I reorganized it last month on 6.1 and it only took 3 days.
Is there a way we can make it hurry up? What should I check into?
________________________________
Notice from Bob Evans Farms: This e-mail message, including any
attachments, may contain confidential information that is intended
only for the person or entity to which it is addressed. Any
unauthorized review, use, disclosure or distribution is strictly
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message and
any attachments.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com
_mailman_listinfo_midrange-2Dl&d=DQICAg&c=3crv0V5Gxwbo5hXTsiQI6g&r=Pkb
fvkKxtcDeNvEOH5BjJL4QM0EQmj0cLL71lzl405I&m=iylblp5ylrhyABM8dyRpJcLBAy-
CmJw1kciaGA-jm5E&s=lNQEsv_S4r-n1yufj757NyVGhV41lFgCPPa8BOBvuaA&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_mid
range-2Dl&d=DQICAg&c=3crv0V5Gxwbo5hXTsiQI6g&r=PkbfvkKxtcDeNvEOH5BjJL4QM0EQmj
0cLL71lzl405I&m=iylblp5ylrhyABM8dyRpJcLBAy-CmJw1kciaGA-jm5E&s=3IdfgUoh8goGKC
0HT-Ksw5kDHBoJAZhU_Z-R6rVyQ8A&e= .
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com_mailm
an_listinfo_midrange-2Dl&d=DQICAg&c=3crv0V5Gxwbo5hXTsiQI6g&r=PkbfvkKxtcDeNvE
OH5BjJL4QM0EQmj0cLL71lzl405I&m=iylblp5ylrhyABM8dyRpJcLBAy-CmJw1kciaGA-jm5E&s
=lNQEsv_S4r-n1yufj757NyVGhV41lFgCPPa8BOBvuaA&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_mid
range-2Dl&d=DQICAg&c=3crv0V5Gxwbo5hXTsiQI6g&r=PkbfvkKxtcDeNvEOH5BjJL4QM0EQmj
0cLL71lzl405I&m=iylblp5ylrhyABM8dyRpJcLBAy-CmJw1kciaGA-jm5E&s=3IdfgUoh8goGKC
0HT-Ksw5kDHBoJAZhU_Z-R6rVyQ8A&e= .
Please contact support@xxxxxxxxxxxx for any subscription related questions.
________________________________
Notice from Bob Evans Farms: This e-mail message, including any attachments,
may contain confidential information that is intended only for the person or
entity to which it is addressed. Any unauthorized review, use, disclosure or
distribution is strictly prohibited. If you are not the intended recipient,
please contact the sender by reply e-mail and destroy all copies of the
original message and any attachments.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
