Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: drop user

Re: drop user

From: Nitin Goyal <Nitin.X.Goyal_at_oracle.com>
Date: Fri, 04 Oct 2002 15:19:26 +0530
Message-ID: <3D9D6426.96A8DC51@oracle.com>



Hi,

Maybe this is not what you are looking for, but it is possible to have a schema-less user, that is a user with no database objects as well as no entry in dba_users table.   This is of particular use in cases where the application that you are designing (say a Financial Application) has all the logic implemented in a schema (say FINANCE) and all the users who access this application just use the tables in the FINANCE schema only.  Thus the users of FINANCE application dont ever need to create their own database objects, and it may be desired not to clutter the database with dummy users (who in reality are just Financial Application users).

To Quote from Oracle Advanced Security Administrator's Guide Release 8.1.7 Chapter 17:

"Users do not necessarily require individual accounts or schemas set up in a database they wish to access. Alternatively, they can be granted access to common, shared schemas (also called user/schema separation) associated with target applications. For example, suppose that users Tom, Dick, and Harriet require access to the Payroll application on the Finance database. They do not need to create unique objects in the database, and therefore do not need their own schemas--they do need access to the Payroll schema.

Oracle8i Release 8.1.7 supports mapping multiple users stored in an enterprise directory to shared schema on an individual database. This separation of users from schemas reduces administration costs by reducing the number of user accounts. It means that you do not need to create an account for each user--a user schema--in multiple databases, in addition to creating the user in the directory. Instead, you can create a user in one location, the enterprise directory, and map the user to a shared schema that other enterprise users can also be mapped to. For example, if Tom, Dick and Harriet all access both the Sales and the Finance databases, you do not need to create an account for each user on each of these databases. Instead, you can create a single shared schema on each database, such as SALES_APPLICATION and FINANCE_APPLICATION, respectively, that all three users can access. A typical environment might have some 5,000 enterprise users mapped to just one of three or four shared schemas. "

Metalink Note:77268.1 may be of interest too.

Thanks,
Nitin
 
 
 

xx32 wrote:

is it possible to have a schema without a user?

Received on Fri Oct 04 2002 - 04:49:26 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US