dmw (7/29/2009)
At first, I thought that the 'schema' would be the key. In other words each 'database' would be in a separate schema.This seems to have the following snags
(a) One-to-one correspondence between user and schema.
(b) The schema contains tables and views but not stored procedures. So stored procedures must handle 'variable' schema.
Your solution would actually be to consider each schema a database.
Contrary to statement (b) code e.g. storedprocs, packages and functions do are stored at schema level.
In regards to statement (a) each Oracle account actually defines a schema but you can grant privileges to a specific account so to have rights on different schemas - in case a single "user" owns several "databases".
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.