Also this might be of interest (including the comments section) - there are some interesting details when using transportable databases / partitioning: http://blog.tanelpoder.com/2008/10/21/transportable-tablespaces-and-rowid-uniqueness/ -- *Tanel Poder* Enkitec (The Exadata Experts) Training <http://blog.tanelpoder.com/seminar/> | Troubleshooting<http://blog.tanelpoder.com/> | Exadata<http://www.amazon.com/Expert-Oracle-Exadata-Apress/dp/1430233923> | Voicee App <http://voic.ee/> On Fri, Jul 12, 2013 at 9:02 PM, Brady, Mark <mbrady@xxxxxxxxxxxxxxxx>wrote: > As people here have pointed out ROWID is unique within a table but not > between them (when not an IOT). But what's the goal of adding that column? > > I know you're trying to simplify the example to give us the gist of the > issue but you've over-simplified. > > In other words, the addition of the ROWID column to the query in the > example has no tangible effect. It seems like the -- //www.freelists.org/webpage/oracle-l
