"create user" not same as creating user from Administration?

Question

I have created users both from scripts and from the Administration pages and am getting different results.
I created a user from a command line script (e.g., "create user <name> identified by <password>"), and then later granted the user all the privileges from the Administration -> Database users -> Manage Users page.
I created a second user from within the Admin pages - this user has all the privileges and works fine.
The user I created from the command line and then granted all privileges (including "DBA" and all explicit privileges) is NOT working correctly.
Specifically:
1. "select ... from ALL_OBJECTS" returns no records. (ALL_TABLES, ALL_INDEXES, and everything else that I try seem to work ok, but in order to see "ALL_OBJECTS", I have to explicitly qualify it with "SYS.ALL_OBJECTS".)
2. When compiling PL/SQL procedures, etc. in that user schema, the built-in packages are not visible unless I explicitly GRANT EXECUTE on each package to the user (from a system account). At that point, they are accessible.
I tried searching the forums for similar topics and didn't find any. I apologize if this is a redundant post, but it is driving me crazy.
Can someone tell me how to make sure the script-created users get all the appropriate rights, and why when they are granted rights from the Admin screens, they still don't appear to have all the rights?
I would strongly prefer not to drop the user account and rebuild it, as there are already 2200 existing objects (tables, procedures, indexes, etc.) in the user account.

Answer 1

Please disregard this post. While investigating another issue, I discovered that the user account from which I had migrated 600+ tables had (for some unknown reason) empty copies of ALL_OBJECTS, USER_INDEXES, and USER_IND_COLUMNS in the user tablespace, so these got copied over with the other valid tables. Having "local" (and empty) copies was causing most of the issues.