This content has been marked as final. Show 2 replies
. . . .** For the DisableVersioning errors, try bulldozing. Call DisableVersioning( <TABLE_NAME>, force=>true, ignore_last_error=>true) repeatedly within a PL/SQL loop. I suspect those error messages have to do with different tables, so be sure to try this on each of the problematic tables.
. . . .** For the "missing BEFORE, AFTER..." and "DECLARE" errors, check the syntax of triggers associated to the tables that have the DisableVersioning error. Oracle Enterprise Manager can be used to identify dependancies such as triggers. It is possible to drop or replace a trigger without first DisableVersioning the table.
ORA-20230: This error is most likely occurring during UndoEnableVersioning. So some other error is causing EnableVerisoning to fail. This then becomes the same error as the ORA-20231 error that you listed. Would need to know the exact original trigger definition to be able to know why.
ORA-20229: Would also need to know the trigger definitions for this one. If one of the triggers(or procedures) created by OWM are the cause, would need to see a trace of the EnableVersioning process, and the results from the all_errors view for the specific trigger.
ORA-20228: The table is currently being DisableVersioned, and until that process completes EnableVerisoning cannot be called on the table. ignore_last_error set to true can be used to accommodate this, or fix the cause of the error so that no SQL statements get skipped.
ORA-20104: This error will occur when you are trying to disable a child table in a foreign key relationship, without first dsableversioning the parent table. You can specify both tables in a single call to DisableVersioning, or be sure to do them in order starting with the parent tables.