I believe this is a bug in this release, even if I couldn’t find any relevantīEGIN dbms_wm. It seems we have an issue in 11.2.0.3, the commitddl command, does not remove the constraints. SQL> exec dbms_wm.commitddl(‘X_SECTION’) īut I ran into the same situation again, after tried begginddl a second time. Oracle Workspace Director (OWM) Clean Up in Orphan Database 11.2-19c is not complicated both straight forward. SQL> alter table X_SECTION_lts drop constraint SYS_C00106482_LTS SQL> alter table X_SECTION_lts drop constraint NEW1_C00106482_LTS_LTS Next step is to drop the constraints, both of them. Now we have two constraints, the one we renamed earlier and the new one created when we did the beginddl call. SQL> exec dbms_wm.alterVersionedTable(‘X_SECTION’, ‘RENAME_CONSTRAINT’, ‘constraint_owner=NETBAS01, constraint_name=SYS_C00106482_LTS, new_constraint_name=NEW1_C00106482_LTS’) ![]() Now we need to change the name of that constraint, so we can do beginddl. SQL> select constraint_name from user_constraints where table_name=’X_SECTION_LTS’ and constraint_type=’C’ So when I execute beginddl, it tries to create a new constraint with the same name. In my case I still have the following constraint on my table, note that all work is done against the _lts table, which is a table created when you enable versioning. The constraint should be dropped when you issue: ![]() The problem relates to constraints, not 100% sure why it happens but it seems that constraints are created when you enable ddl. ORA-02264: name already used by an existing constraint SQL> exec dbms_wm.beginddl(‘X_SECTION’) īEGIN dbms_wm.beginddl(‘X_SECTION’) END Possibly can this be experienced after an import. I got ORA-02264: name already used by an existing constraint. Working with Oracle Workspace manager (OWM) in an 11.2.0.3 database I ran into an issue when trying to do dbms_wm.begin_ddl on a table.
0 Comments
Leave a Reply. |