Oracle recommends that you grant each user just enough privileges to perform his job, and no more. For example, a database application developer needs privileges to create and modify tables, indexes, views, and stored procedures, but does not need (and should not be granted) privileges to drop (delete) tablespaces or recover the can create user accounts for database administration, and grant only a subset of administrative privileges to those accounts.
Oracle recommends that you grant each user just enough privileges to perform his job, and no more. For example, a database application developer needs privileges to create and modify tables, indexes, views, and stored procedures, but does not need (and should not be granted) privileges to drop (delete) tablespaces or recover the can create user accounts for database administration, and grant only a subset of administrative privileges to those accounts. In addition, you may want to create user accounts that are used by applications only. That is, nobody logs in with these accounts; instead, applications use these accounts to connect to the database, and users log in to the avoids giving application users the ability to log in to the database directly, where they could unintentionally cause damage. See "About User Privileges and Roles" for more information.
Suppose you want to create a user account for a database application developer named Nick, who has requested the password "firesign007." Because Nick is a developer, you want to grant him the database privileges and roles that he requires to build and test his also want to give Nick a 10 megabyte (MB) quota on his default tablespace so that he can create schema objects in that tablespace.
Suppose you are creating or modifying a user named Nick. Because Nick is a database application developer, you want to grant him the APPDEV role, which enables him to create database objects in his own schema. (You created the APPDEV role in "Example: Creating a Role".) Because you want Nick to be able to create tables and views in other schemas besides his own, you want to grant him the CREATE ANY TABLE and CREATE ANY VIEW system privileges. In addition, because he is developing a human resources application, you want him to be able to view the tables in the HR sample schema and use them as examples. You therefore want to grant him the SELECT object privilege on the those tables. Finally, you want Nick to be able to log in to Database Control so that he can use the graphical user interface to create and manage his database objects. You therefore want to grant him the SELECT ANY DICTIONARY system privilege. The following table summarizes the privileges and roles that you want to grant to Nick.
Nickという名前のユーザーの作成および変更を行うと想定します。Nickはデータベース・アプリケーション開発者であり、自身のスキーマでデータベース・オブジェクトを作成できるように、APPDEVロールを付与する必要があります(例: ロールの作成でAPPDEVロールを作成済です)。また、自身のスキーマ以外のスキーマで表やビューを作成できるようにする場合は、CREATE ANY TABLEおよびCREATE ANY VIEWのシステム権限を付与します。さらに、Nickが人事管理アプリケーションの開発者である場合、HRサンプル・スキーマにある表を例として使用できるように、これらの表のSELECTオブジェクト権限を付与する必要もあります。最後に、データベース・オブジェクトの作成および管理用のグラフィカル・ユーザー・インタフェースを使用できるDatabase Controlへのログインを可能にするため、SELECT ANY DICTIONARYシステム権限を付与する必要があります。次の表は、Nickに付与する権限およびロールを示しています。
Oracle Database Application Developer's Guide - Large Objects
Oracle Databaseアプリケーション開発者ガイド-ラージ・オブジェクト
Oracle Database Application Developer's Guide - Object-Relational Features for complete descriptions of object types
Extensive Oracle documentation is available for broadening your knowledge of database concepts and objects. For example, to learn more about primary keys and constraints, see Oracle Database Concepts or Oracle Database Application Developer's Guide - Fundamentals, which you can download from
Oracle Database Application Developer's Guide - Fundamentals and Oracle Database PL/SQL User's Guide and Reference for more information about the uses for and creation of triggers
Examples are used only to help you translate the word or expression searched in various contexts. They are not selected or validated by us and can contain inappropriate terms or ideas. Please report examples to be edited or not to be displayed. Potentially sensitive, inappropriate or colloquial translations are usually marked in red or in orange.