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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
