That is messed up dude! You have three event tables which are currently set to “1”. You might have other issues, like a corrupt DB, or this just might be a symptom of a bigger issue. I’d recommend opening a case with Microsoft on this. It depends greatly if the number of current tables is a symptom of something bigger being broken, or if this is the root cause for why your partitioning and grooming is failing. For instance, if you run partitioning and grooming sproc – does this just add another “iscurrent” table?
If so, I’d recommend restoring from a known good backup. This is, of course, assuming you have ample free space in the database (50%) and a properly sized transaction log (50%), and in a supported configuration otherwise.
Similar above discussed issue is in our SCOM 2012 R2 environment also. We must open case with Microsoft to fix this issue or anything else we can perform before take it to Microsoft. Kindly assist.
Manually grooming P_grooming is working fine and we are doing manual grooming to avoid opeartionsmanager database filling. But P_partitioning is not working it is throwing “Error in p_PartitionObject”.
Note: We did not do any recent change in our environment. There is no error in event log also.