Actually, that response is not quite correct. Oracle 10g introduced new entity, so called bigfile tablespace. Normally, rowid has 3 bytes for the relative file#, 3 bytes for row number within the block and 6 bytes for the block# within the file. If you decide that big is beautiful, then the block# within the file will be 9 bytes long. Also, there will be no relative file# as BF tablespaces can contain only a single file. The only utility that you can use to extract rowid components is DBMS_ROWID. Everything is described in the note 262472.1. BFT (Big File Tablespace) should not be mistaken for the BFG from the Wolfenstein game. -- Mladen Gogala Ext. 121 -----Original Message----- From: Deepak Sharma [mailto:sharmakdeep_oracle@xxxxxxxxx] Sent: Friday, September 09, 2005 12:41 PM To: Ric Van Dyke; oracle-l@xxxxxxxxxxxxx Subject: RE: Oracle 10g Rowid Question Thanks. One of the concerns someone raised is "All old rows in database will have slowness the first time they are read or updated due to conversion to 10g.". I am trying to find out if this indeed is true, and one of the things came to mind was if rowid format changed, which doesn't seem to be the case. - Deepak --- Ric Van Dyke <Ric.Van.Dyke@xxxxxxxxxx> wrote: > If you are asking "has the rowid format changed in > 10g?" then the answer is no. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- //www.freelists.org/webpage/oracle-l