The 'DV' state means that dbms_wm.DisableVerisoning was executed on the table. It looks like whoever executed the procedure, tried to stop it. However, once this procedure starts, typically there is no way to revert it back as the majority of the operations performed are destructive to the table. The only way to get the table to be versioned again is to finish the DisableVersioning procedure by executing it again, and then executing EnableVersioning. However, by doing this all of the remaining history would be lost. If you don't necessarily need that history, you can perform those operations and skip the remaining part of this post.
If you do need the history, I would recommend filing a SR. Based on the delete statement listed in the all_wm_vt_errors view, the only statement that has already been run is the delete from the base table of any row that is not in the LIVE workspace. You can determine if there had been rows in any such workspace by using the all_wm_modified_tables view. The metadata for this view is likely to still exist at this point. If this lists a non-LIVE workspace for the table, that does mean that the metadata of the remaining rows would be invalid. In either case, it should be possible to maintain the remaining history, if needed.
Thanks. We're considering our options, and will possibly end up going down the SR route.