Comments on: Oracle: How to move a table to another schema?

By: Christo Kutrovsky

Christo Kutrovsky — Fri, 30 Nov 2007 18:10:23 +0000

Hi Matt,

Based on your error I think the indexes are not the same. Probably not on the same columns, not the same compression. Check that you have the exact same indexes on both tables.

By: Matt Tordoff

Matt Tordoff — Fri, 30 Nov 2007 16:38:34 +0000

Hi Christo,

I followed your article with some interest, thankyou for providing this ingenious approach. I have attempted to mimic the situation shown here, but with a slightly more complicated example. I am trying to move a table from one schema to another, and at the stage where i issue the following command:

> alter table t1_temp exchange partition dummy with table t1 including indexes without validation;

I receive the following error from Oracle:

> ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

The table I am trying to move has both primary key and foreign key constraints. I have created these constraints for the temporary table t1_temp, however, am still getting the above complaint. Is the only solution to drop all constraints, move the table, and then recreate the constraints once moved?

Any help would be greatly appreciated.

Matt

By: Christo Kutrovsky

Christo Kutrovsky — Tue, 28 Aug 2007 14:45:56 +0000

Marco,

You forgot “including indexes”. You must have a primary key. Look at my example move in the post.

By: Marco

Marco — Tue, 28 Aug 2007 14:01:06 +0000

Hi, is great to found what a look specifically, but when run this, sqlplus give the next error message:

SQL> alter table prodinsumo_temp exchange partition dummy with table dbasit.prodinsumo without validation;
alter table prodinsumo_temp exchange partition dummy with table dbasit.prodinsumo without validation
*
ERROR at line 1:
ORA-28653: tables must both be index-organized

By: Misha

Misha — Tue, 28 Aug 2007 09:50:04 +0000

Yes, this method is unsupported. But a bit alike thing is about outlines : exchanging them is done by directly updating data dictionary tables that is not documented in official Oracle documentation, but has a metalink note.

By: Alex Fatkulin

Alex Fatkulin — Tue, 28 Aug 2007 00:43:34 +0000

Misha, you should probably be aware that it’s a big no-no to hack the data dictionary with your bare hands?

Never ever do like that, unless you are planing to use that database for practicing your restore and recovery skills.

By: Misha

Misha — Mon, 27 Aug 2007 16:52:03 +0000

Hi,

I have tested another method :

update obj$ set OWNER#=x where name=’y';
commit;
alter system flush shared_pool;

this works !

By: Tahir

Tahir — Sat, 12 May 2007 18:04:49 +0000

How to import tables from one owner abc/xyz to another owner kee/nee with all constraints.

By: fielding

fielding — Wed, 25 Oct 2006 01:24:52 +0000

joytao,
SYS.I_OBJ2 is the index on object owner/name, so it looks like the clone is erroring out due to a duplicate destination object name. Might there have already been objects in SAPTST prior to the clone?

By: joytao

joytao — Sun, 15 Oct 2006 04:43:55 +0000

Dan,
when run this procedures,display infomatin folllow,can you help ?
BEGIN
dbms_schema_copy.clone(’SAPDEV’, ‘SAPTST’,2,FALSE);
dbms_schema_copy.clean_up(’SAPDEV’, ‘SAPTST’);
END;
/

ERROR at line 1:
ORA-00001: unique constraint (SYS.I_OBJ2) violated
ORA-06512: at “SYS.DBMS_UPGRADE_INTERNAL”, line 2481
ORA-06512: at “SYS.DBMS_UPGRADE_INTERNAL”, line 3909
ORA-06512: at “SYS.DBMS_UPGRADE_INTERNAL”, line 4150
ORA-06512: at “SYS.DBMS_UPGRADE_INTERNAL”, line 2168
ORA-06512: at “SYS.DBMS_UPGRADE_INTERNAL”, line 2236
ORA-06512: at “SYS.DBMS_SCHEMA_COPY”, line 628
ORA-06512: at “SYS.DBMS_SCHEMA_COPY”, line 743
ORA-06512: at line 2