× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You'll expose yourself to level checks by deleting the LF's. Better to
remove the LF members first, then add them back after the reorg.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Richard Reeve
Sent: Monday, October 17, 2016 7:41 AM
To: Midrange Systems Technical Discussion
Subject: 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: 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.