Yes and no: it goes to 10,758 - just once more again now after updating E1LOCAL's F9860 as I mentioned above.Does it always insert the same # of F98760R records? So, could the next record from F9860 be corrupt in some way that causes the process to fail, leaving you with 10758?
But if I check out F00165 in DEP920 (one of the missing objects), it adds 1 more, etc. It's just that there are so many missing ones, that I cannot possibly check them out one by one like this. I don't think it's a corruption.
I can try debuglog'ging it next and see where it's getting that list from - it happens within a minute from the build start...