>What is weird about Oracle instances is the fact that you can't really host multiple databases in an instance. My definition of a database is a collection of related tables/triggers/SPs/views/RI.

My definition as well.

>In VFP, I can have n databases open, and tables can have the same names, same SP names, etc and I can feel that they function independently; I can even have multiple VFP .exes opening the same multiple databases.
>
>In Oracle (at least in 7.3.4 which is what I deal with), I can't have a generic SP named "auditrow" and use it over and over, since everything is lumped into the same Oracle instance.
>
>Or is this just a sign of lazy DBA work? Is there a way to "compartmentalize" databases in a single instance, or should I look to create multiple instances?

You can have as many databases [my definition] in 1 instance of Oracle as well. Whenever I create a new app that will use Oracle as the data source, I [the Oracle DBA actually] create a special UserID in Oracle that reflects the name of the App I am developing [e.g., UserID called Permits]. Under that ID I place all the tables, views, triggers, RI, etc. I never create all this under a specific [real] user's ID because if that user quits or is fired, I am stuck with either keeping the User's ID [bad practice] or moving all the objects to another idea [PITA].

Keep in mind Oracle's definition of a database encompases all objects under all user IDs while our definition is usually specific to all the tables, views, indexes, etc., for 1 app.