we're running a homogeneous system copy as part of a unicode upgrade of our R/3 (4.7ext200) system. We've kicked off the SAPinst portion, and we're running the table size scans using R3szchk.
Unfortunatley this is really taking a long time....we killed it after 30 hours to further performance tune our database - but that hasn't made much of a difference. We'd really be expecting a complete run-time in the region of 10 - 12 hours at absolute worst.
Our hardware isn't being particularly well utilised - CPUs running at <40% and not much swapping in/out of physical memory going on.
Has anyone got any ideas as to why this might be happening - and what the problem might be?
All help appreciated.