I'm seeing a rather unusual output from dba_segments. I've just migrated from Oracle7.3 to Oracle8.0.6. I got an error while running cat8000.sql that the table SYS.SOURCE$ has reached its max extents.
So I run this query to make sure I'vent reached my max_extents and I get 2 rows. could anyone tell me why i've two entries for the same table in dba_segments view????
You have reached maxextents for one of your system objects. While not the greatest thing to happen, it's not that big of a deal either. Just alter the object in question and set it's maxextents to unlimited. For example:
alter table sys.source$ storage (maxextents unlimited).
I get two entries for the same object in the all_objects view. One is owned by "migrate" and other one bu "sys". A question, since i've completed my migration is it appropriate to delete the user "migrate" and delete all the objects owned by this user???
SVRMGR> select owner from all_objects where object_name='SOURCE$';
2 rows selected.
Or is there a serious problem that "migrate" user owning objects that should be owned only by sys?
when I count the number of objects owned by "migrate" result is 136
SVRMGR> select count(*) from all_objects where owner = 'MIGRATE';
1 row selected.
Of course nobody else should be the owner of sys's objects.
It'd be curious to know how you have an user with the same objects as sys user has.
Howevere if your sys user work properly you can try to delete your user MIGRATE payinh attention if the DB work correctly.
But it's not a nice situation.