Not exactly, because row_number() is query specific, I want to store the rowids in a temporary table and want to use them in another query.
So it is imperative that the rowid should reflect the absoulte position in the table like ROWID does in ORACLE.
Sorry for the delay in reply,
The problem is my production table has a composite primary key and I have some 2 crores of records in the table. so generating the additional identity key means
4 bytes per int field multiplied by 2 crores record = 80 MB of additional memory requirement for an additional column which is at best can be averted by using some other means of SQL.