| Team Fly | |
Often it makes sense to group similar users together somehow to streamline the organization of people who use the Oracle Database 10g. Using roles, the DBA can logically lump personnel together and give out object privileges to roles rather than individual users. Roles can be password protected, though in most implementations they do not have this level of complexity.
As accounts are created by the DBA, users are given a default environment to use unless some specifics are coded as they interact with the Oracle Database 10g. Users are commonly set up with the following default environment settings:
The default tablespace is where tables are placed unless the create table statement explicitly points at a nondefault tablespace upon which the user has a quota.
Temporary tablespaces are the tablespaces where users perform sort and merge operations while the Oracle Database 10g engine is processing queries.
Users can be given membership in one or more roles and have their default profile changed as well. As users are created, they do not automatically inherit a default tablespace; one must be manually given out during or following the user creation statement. Users do automatically point at a temporary tablespace, as discussed in the ''Default Temporary Tablespace" section of this chapter, unless manually pointed elsewhere.
1. Name at least four tasks handled by the Oracle Database 10g administrator?
2. What is the difference between public and private synonyms?
3. What is meant by a user's default tablespace?
4. What two units of measurement are commonly used to specify a tablespace quota?
5. Where do DBAs go to create iTARs where assistance is requested from Oracle's support organization?
6. Which of the following—procedures, packages, and triggers—cannot exist independent of a table to which they belong?
| Team Fly | |