Transportable tablespace issue

As known, a transportable tablespace that is plugged in target database brings table's ROWIDs containing that table's object ID (first 6 characters) from source database to the target so that object got "attached" to target with its original ID. Since there is no guarantee that there wasn't data object with the same ID in the target database before it seems database object number uniqueness is no longer guaranteed as soon as a tablespace from another database got plugged in.

Q: Does it make any conflicts in database? How does Oracle resolve that situation when it encounters two objects (tables) with same object ID?

Thanks,
Eugene. Received on Mon Jun 05 2000 - 00:00:00 CEST