We ran into this problem recently. Big thanks for the references to the specific lock. And that script! More than handling the NULLs, what causes the NULLs? We've dug in and found the cause... at least in our case. Our Compress was failing. Worse, these orphaned locks did not exist before, but did exist after. And it also orphaned some version information, so we began losing edits. We've had 2 items to cause this. First, an orphaned editing service. It was leaving locks across many feature classes. Second, our developers that create the services would sometimes forget to uncheck the schema lock (checked by default) when creating a service. Especially for the orphaned edit service... there are no lock references in the locks tables. When the Compress runs, it only partially completes. Not a partial Compress. It broke in the middle (FAILURE -51) due to a lock it did not foresee (to skip). Data was changed in some locks tables and failed when attempting in others, thereby creating the NULLs at hand. So now my question: is the BUG fix going to simply not error and show NULLs? What is BUG-000110574 going to implement?
... View more