AFAIK you can update the partition key as long as the new key still fits in the partition range of it's current partition. If I'm not mistaken, even this limitation is no longer valid in 8i if you enabled row movement between partitions
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
The database is set like this.
The database consists of 47 tables. The application which we use is designed such a way that each client will have a specific userid to login and enter their data in the 47 tables through their views(47). So each user is given their own views, as data can be edited through the dedicated view.
All the 47 tables will have the userid as one of their columns in it. That way its easy to partition by range.
For each userid 47 tables are partitioned, views are created and stored in a different tablespace. So actually the data is partitioned by the client id (userid in oracle terms).
The userid is dropped accidently from the dba user. So the objects which are owned by the users are deleted. So we did a point in time recovery and thinking of creating the new user and updating the partition key with the new userid.
Hope this explains the situation.