This action might not be possible to undo. Are you sure you want to continue?
• • • • • Database Components Memory Structures Processes Oracle Instance Shared Server ( Multi –threaded Server)
An oracle database consists of Physical Components
• • • Data file Control Files Redo log files
• Tablespace , segments , extent , block. • Schema Objects
A database consists of a set of operating system files. Types of information is stored in an oracle database
• User Data
Actual Application Data
• System Data
Data that the database needs to manage itself
• Overhead Data
Indexes , Integrity etc.
An ORACLE database consists of one or more physical operating system files, called database files. These files contain all the database data. One or more physical files form a logical unit on database storage called a tablespace A database file can be associated with one and only one tablespace.
A database’s overall physical architecture is maintained by its control files. A control file contains information about all the files associated with an oracle database files -- Name of Physical database files -- Redo Log files -- Time stamp
12/1/2010 Control File A control file is associated with a single database. Control file is automatically modified by ORACLE. A Redo log contains all the committed transaction that have occurred against the database . 4 . Redo logs are also called transaction logs. a user cannot edit them They are used to maintain internal consistency and guide recovery operations Redo Log file The Redo Log files are set of files external to the database that records changes made to the database during transactions.
Redo Log file An online Redo log file is one to which transactions are written each time a transaction occurs.12/1/2010 Redo Log File No activity in the database can take place without being recorded in Redo Logs The redo Logs are necessary to protect against data loss due to various kinds of failures. 5 . Every database requires a minimum two Redo Logs Redo logs work in circular fashion A Log switch occurs when a log file is filled.
A copy of current log is made before a log switch occurs.Default mode -. Redo Log File NOARCHIVELOG Mode -.All transaction redo logs are kept -.12/1/2010 Redo Log File Database operates in two modes : --NOARCHIVELOG --ARCHIVELOG The mode determines whether the redo logs are overwritten or not before creating copy of filled redo log file. This ensures the database protection against all types of failure. 6 .The transactions are overwritten each time a log switch occurs ARCHIVELOG Mode -.
A database may have one or more tablespaces Each logical tablespace corresponds to one or more physical files. Tablespace The typical tablespace present in an ORACLE database are : SYSTEM SYSAUX TEMPORARY UNDO USER BIGFILE INDEX 7 .12/1/2010 Tablespace A database is divided into logical divisions called tablespaces.
UNDO : -. BIGFILE : -.the system tablespace always contain the data dictionary for the entire database objects.An auxiliary tablespace to the SYSTEM tablespace -.12/1/2010 Tablespace SYSTEM -.Where all the information about the user is stored.where ORACLE stores all its temporary tables.Consists of only one datafile -. USER : -.Used for rolling back transactions.where ORACLE stores all the information it needs to manage itself.Used by oracle components like Enterprise Manager Repository . Tablespace TEMPORARY : -. 8 .Single data file can be upto 8EB. log Miner etc. -. SYSAUX -.
The storage parameters of segment determines how a database object will obtain database space. made up of logical (oracle) blocks Segments and Extents Types of segments can be : Data segments Index segments Undo segments Temporary segments Bootstrap segments 9 .12/1/2010 Segments and Extents All data in a tablespace is stored in allocations of database space called segments A segment is a set of extents allocated for storage of database data. An extent is an allocation of contigious database space .
Indexes -. UNDO : where all undo information is stored. 10 .12/1/2010 Segments and Extents DATA and INDEX which holds the actual data and the indexes. TEMPORARY : Used to store intermediate results of various operations BOOTSTRAP : Helps to initialize data dictionary cache when the database is opened by an instance Schema Objects A schema can have one or more logical database objects -.Tables -.Views etc.
12/1/2010 Oracle Memory Structures Oracle uses memory to store : -.The System Global Area (SGA) -.Data needed during program execution -. Oracle Memory Structures The basic memory structures associated with ORACLE includes : -.The Program Global Areas (PGA) 11 .Caching information.Information which is shared and communicated among ORACLE processes -.Information about connected session -.Program code being executed -.
12/1/2010 The System Global Area A group of shared memory structures that contains data and control information for one database instance Multiple users connected to the same instance share the data from instance’s SGA Also referred as Shared Global Area The System Global Area The information stored within an SGA is divided into several areas of memory : The database Buffer Cache The Redo log Buffer The Shared Pool Java Pool Streams pool 12 .
The Redo Log Buffer The redo log buffer in the SGA holds changes made to the database. Redo entries from the Redo Buffer are written to the online Redo Log Files 13 .12/1/2010 Database Buffer Cache A portion of SGA that holds database information The buffers are shared by all ORACLE user processes concurrently connected to the instance.
14 .12/1/2010 The Shared Pool It consists of -. – Use Least Recently used (LRU) algorithm – Consist of two areas shared SQL are Shared PL/SQL area.Data Dictionary Cache Shared pool Library Cache – stores information about the most recently used SQL and PL/SQL statements.Library Cache -.
Privileges of all Oracle users.SQL work area.Private SQL area -. The Program Global Area Contains data and control information for single process Also referred as ‘Process Global Area’ PGA contains -.Session memory -. its structure and its users – Contents of the data dictionary Names of all tables and views Names and data types of the columns in database tables.12/1/2010 Shared Pool The Data Dictionary Cache – Contains reference information about the database . 15 .
Oracle Processes System Processes -.Optional Processes User Processes 16 .Mandatory Processes -. SGA is allocated and one or more Oracle processes are started. An ORACLE Instance -.12/1/2010 Oracle Processes Every time a database is strated on a database server . not all are always present.The combination of SGA and the ORACLE processes is called an Oracle Database instance -.An Oracle instance may have number of background processes.
Oracle System Processes
Database Writer (DBWn) Log Writer(LGWR) System Monitor(SMON) Process Monitor (PMON) Checkpoint (CKPT) Archiver (ARCH) Recoverer (RECO) Lock (LCKn) Server(Snn)
All the writing of buffers of a data files is performed by the database writer Process. DBWR also manages the buffer cache so that user processes can always find free buffers DBWR is responsible for buffer cache management
-- when a buffer in the buffer cache is modified , it is marked as ‘Dirty’. -- DBWR keeps buffer cache ‘Clean’ by writing ‘Dirty’ buffers on the Disk
Database writer writes to database when -- Checkpoints occur -- Dirty buffers reach threshold -- There are no free buffers -- Time out occurs
The redo log buffer is written to a Redo log on disk by the log writer process(LGWR) LGWR is the only process that writes to the on line Redo log and reads the redo log buffers Log Writer writes to log files when
-- A transaction commits -- The redo log buffer is one third full -- More than 1MB of changes recorded in the Redo Log Buffers -- Before DBWn writes modified blocks in the database buffer Cache to the data files -- Every three seconds
The system Monitor Process performance instance recovery at instance start up. SMON is also responsible for cleaning up temporary segments It merges contiguous free extents in the data file
Performs process recovery when a user process fails. PMON -- Rolls back the transaction -- Releases the locks -- Releases other resources used by failed process
Updates all of the data files header and control file with checkpoint information.12/1/2010 Checkpoint (CKPT) Signals DBWR at checkpoints Records information in control file . to identify the place in the online redo log file from where recovery is to begin. Managing Oracle Instance 20 .
ora -.ora -.Binary file -.12/1/2010 Parameter File Static parameter file (PFILE) -.Changes to parameter can be persistent across shutdown and startup -.Maintained by Oracle Server -.SHOW PARAMETERS [parameter_name] 21 .Default Location ORACLE_Home\Database Persistent server parameter file (SPFILE) -.Default name in the format of spfileSID.ALTER SYSTEM SET undo_tablespace=undo3 SCOPE=BOTH.To create spfile first . .g.Text File -.Default name in the format of initSID.Default location ORACLE_HOME\Database Changing parameter values Syntax : -ALTER SYSTEM SET parameter_name= value [SCOPE= MEMORY|SPFILE|BOTH] E. To see parameters value . pfile must exit -.
-.STARTUP [ FORCE ] [ RESTRICT ] [ PFILE=pfile_name] [ MOUNT | NOMOUNT] E.STARTUP PFILE = ORACLE_HOME\database\init<sid>.DB_NAME -.DB_CACHE_SIZE -.SHARED_POOL_SIZE -.COMPATIBLE -.STARTUP -.12/1/2010 Parameters in Initialization Some common Parameters -.BACKGROUND_DUMP_DEST -.g.CONTROL_FILES -.USER_DUMP_DEST Starting Up a Database SYNTAX -.ora 22 .
12/1/2010 Starting Up a Database Database can be started in three stages : -.MOUNT -.NOMOUNT -. SYNTAX: ALTER DATABASE <MOUNT | OPEN [READ WRITE | READ ONLY ]>. 23 .OPEN ALTER DATABASE command Used for moving database from NOMOUNT to MOUNT or MOUNT to OPEN stage.
log Location decided by BACKGROUND_DUMP_DEST -.12/1/2010 Shutting down the database SYNTAX SHUTDOWN [ NORMAL | TRANSACTIONAL | IMMEDIATE | ABORT ] .alert_SID.User trace files Location decided by USER_DUMP_DEST Size defined by MAX_DUMP_FILE_SIZE 24 . Diagnostic Files The files contains information about significant events. Types of the files : -.Background trace files Location decided by BACKGROUND_DUMP_DEST -.
-.sid (session id) and Serial# (serial number) from v$SESSION view are used to uniquely identify a session Data Dictionary and Dynamic Performance views 25 . serial#’` .12/1/2010 Terminating Session Syntax ALTER SYSTEM KILL SESSION `sid .
Definitions and space allocation of all objects such as table .12/1/2010 Data Dictionary Contains read only tables and views. -. views.Logical and Physical database structure -.Integrity constraint information -. Provides information about -. synonyms etc.Auditing information 26 . Stored in the SYSTEM tablespace Owned by the user SYS Maintained automatically by the Oracle server Oracle server modifies it when a DDL statement is executed Available as read only to users and DBA Data dictionary Contents Data dictionary views are static views.Names of Oracle users -.Privileges and roles granted to users -.
12/1/2010 Data dictionary view categories Distinguish and prefixed by their scope -. DICT_COLUMNS Schema objects -. query the DICTIONARY view or its synonym DICT General Overview -.DBA All objects in the database -.ALL Objects accessible by the current user --USER Objects owned by the current user Data Dictionary To get overview of the data dictionary views .DBA_TABLES -.DICTIONARY .DBA_TAB_CONSTRAINTS 27 .DBA_INDEXES -.DBA_TAB_COLUMNS -.
DBA_EXTENTS Database structure -.DBA_DATA_FILES Dynamic Performance Views These virtual table exists in memory only when the database is running Reflect real-time conditions of the database operation Points to actual sources of information in memory and the control file Also called as fixed views Owned by SYS and begin with V_$ Accessed through public synonyms starting with V$ Listed in V$FIXED_TABLE 28 .12/1/2010 Data Dictionary Space allocation -.DBA_SEGMENTS -.DBA_TABLESPACES -.
Session information Dynamic Performance Views V$SGA -.Contents of the SPFILE V$TABLESPACE -.Version numbers of core library components 29 .Data file information from the control file V$INSTANCE -.Names of the control file V$DATABASE -.Tablespace information from the control file V$VERSION -.State of the current instance V$PARAMETER -.List parameters and values currently in effect V$SESSION -.Database information from the control file V$DATAFILE -.12/1/2010 Dynamic Performance Views V$CONTROLFILE -.Summary information of the SGA V$SPPARAMETER -.
12/1/2010 Managing tablespace Tablespace A database is divided into logical divisions called tablespace A database may have one or more tablespaces Each logical tablespace corresponds to one or more physical database files 30 .
Created with the database -.SYSTEM USER TEMP TOOLS Tablespace SYSTEM tablespace -.Should not contain user data 31 .SYSTEM SYSTEM SYSAUX -.Contains the data Dictionary .12/1/2010 Tablespace The original tablespace is named as SYSTEM The typical tablespace present in an ORACLE database are : -. including stored programs -.Contains the system undo segments -.Non.
Created according to data backup requirements -.Created to separate undo . temporary .12/1/2010 Tablespace Non. application data and application index segments -.Created for flexibility in database administration -.SYSTEM tablespace -.Control the amount of space allocated to the user’s objects Tablespace Syntax CREATE TABLESPACE ts_name [ DATAFILE ‘file_name’ [ SIZE integer [ K|M ]] [ MINIMUM EXTENT integer [ K|M ]] [ LOGGING | NOLOGGING ] [ extent_management_clause ] [ extent_management_clause ] 32 .
direct loads Space management Locally Managed -.Prior to Oracle9i Release 2 .Each bit corresponds to a block or group of blocks -.g.Affects only DML and DDL Commands .12/1/2010 Tablespace NOLOGGING -. e.Free extents are managed within the tablespace using bitmaps -.Default beginning with Oracle9i -. the system tablespace was not locally managed 33 .
dbf` SIZE 400M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K 34 .When space is allocated or deallocated . so coalescing is not required -.Tracks adjacent free space . undo not generated -.The size of locally managed extents can be determined automatically by system -.12/1/2010 Space management Advantages of locally managed tablespaces -.Avoids recursive space management operation Space management Syntax of extent_management_clause [ EXTENT MANAGEMENT [ DITIONARY | LOCAL [ AUTOALLOCATE | UNIFORM [ SIZE integer [ K | M] ] ] ] Example CREATE TABLESPACE mydata DATAFILE `c:\oradata\mydata01.Reduced contention on data dictionary tables -.
Coalescing is required 35 . MINIMUM EXTENT or TEMPORARY clauses can not be specified -.Data dictionary is updated appropriately when extents are allocated or deallocated -.LOCAL Default clause specifies that the tablespace is locally managed using bitmaps With this clause DEFAULT storage_clause .Each segment stored in the tablespace can have a different storage clause .Free extents are managed in the data dictionary -.AUTOALLOCATE Specified that the tablespace is SYSTEM managed Users can not specify an extent size Space management Dictionary managed -. so more flexible than locally managed but much less efficient -.12/1/2010 Space management extent_management_clause -.
CREATE UNDO TABLESPACE ts_name [DATAFILE clause] [ EXTENT MANAGEMENT clause] E .dbf` EXTENT MANAGEMENT DICTIONARY DEFAULT STORAGE ( INITIAL 1M NEXT 1M PCTINCREASE 0) Undo Tablespace Used to store undo segments Extents are locally managed EXTENT MANAGEMENT LOCAL and DATAFILE clauses can only be specified Syntax : -.12/1/2010 Space management Dictionary Managed example CREATE TABLESPACE mydata DATAFILE `c:\oradata\mydata01.CREATE UNDO TABLESPACE undo1 DATAFILE ‘c:\oradata\undo. -. G.dbf’ SIZE 20M 36 .
12/1/2010 Temporary Tablespace Temporary tablespace -.dbf` SIZE 30M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M. use the CREATE TEMPORARY TABLESPACE statement Temporary Tablespace The extents once allocated can be only freed when the instance is shut down e.g CREATE TEMPORARY TABLESPACE temp1 TEMPFILE ` c:\oradata\temp1.To create a locally managed temporary tablespace . 37 .g segments used by implicit sorts caused by an ORDER BY clause -.It is always with standard blocksize -.Used to hold temporary objects e.
Default Temporary Tablespace Default temporary tablespace is created to eliminate the use of System tablespace for storing temporary data Default temporary tablespace can be created • At the time of database creation • After database creation By creating temporary tablespace and setting it to Default temporay tablespace E.12/1/2010 Temporary Tablespace Points to remember about temporary data files in locally managed temporary tablespace • • • • • Non standard block sizes cannot be specified Temporary files are always set to NOLOGGING mode It cannot be made read only Temporary files are required for read only databases Media recovery does not recover tempfiles. ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp1. 38 .g.
12/1/2010 Default Temporary Tablespace When Default temporay tablespace is changed.all users assigned the Default temporay tablespace are assigned to new default To find Default temporary tablesapce for the database query DATABASE_PROPERTIES view Default Temporary Tablespace Restrictions on default temporary tablespace • Can not be dropped until new default is available • Cannot be taken offline 39 .
12/1/2010 Taking Tablespace offline Syntax: ALTER TABLESPACE ts_name<ONLINE | OFFLINE [NORMAL|IMMEDIATE]>.Tablespaces with active undo segments .Default temporary tablespace 40 . Example : ALTER TABLESPACE user OFFLINE ALTER TABLESPACE user ONLINE Taking Tablespace offline Following tablespace cannot be taken offline .System tablespace .
dbf’ SIZE 4M AUTOEXTEND ON NEXT 2M MAXSIZE 100M – ALTER DATABASE DATAFILE ‘C:\oradata\user1. ADD DATAFILE Changing Size of Tablespace Examples : – CREATE TABLESPACE user1 DATAFILE ‘C:\oradata\user1. – ALTER DATABASE DATAFILE ‘C:\oradata\user1.ALTER TABLESPACE….dbf’ SIZE 10M. 41 .12/1/2010 Changing Size of Tablespace Size of the tablespace can be changed automatically by specifying AUTOEXTEND clause with . – ALTER TABLESPACE user2 ADD DATAFILE ‘C:\oradata\user3.CREATE TABLESPACE .dbf’ AUTOEXTEND ON NEXT 2M.CREATE DATABASE .dbf’ RESIZE 5M.
To drop files of tablespace use AND DATAFILES clause 42 . Example .12/1/2010 DROPPING TABLESPACES SYNTAX .Tablespace can not be dropped if it Is a system tablespace Contain active segments .DROP TABLESPACE user1 INCLUDING CONTENTS AND DATAFILES.Tablespace that still contains data can be only dropped by specifying INCLUDING CONTENTS option. DROPPING TABLESPACES Guidelines .DROP TABLESPACE ts_name [INCLUDING CONTENTS[AND DATAFILES][CASCADE CONSTRAINTS]]. .
Transaction recovery Possible because changes made to the undo segment are also protected by the online redo log files.DBA_TABLESPACES . .V$TABLESPACE Data file information -DBA_DATA_FILES .V$DATAFILE Temp file information .Read consistency Does not allow other transactions to see any uncommitted changes 43 .12/1/2010 TABLESPACE INFORMATION Tablespace Information .V$TEMPFILE UNDO SEGMENT • Purpose of Undo segments .Transaction rollback Used to record old values of data that were changed by a transaction Restores these values if transaction is rolled back .DBA_TEMP_FILES .
SWITCHING UNDO TABLESPACE Multiple undo tablespace can exists. 44 .12/1/2010 CREATING UNDO SEGMENT By adding clause in the CREATE DATABSE . however only one tablespace can be active at a time.CREATE UNDO TABLESPACE undo2 DATAFILE ‘C:\oradata\undo2.CREATE DATABASE trydb…… UNDO TABLESPACE undo1 DATAFILE ‘C:\oradata\undo1.dbf’ SIZE 30M AUTOEXTEND ON.ALTER SYSTEM SET UNDO_TABLESPACE= undotbs2.dbf’ SIZE 30M AUTOEXTEND ON. By creating undo tablespace later on . To switch between undo tablespaces dynamically .
45 . CREATING UNDO SEGMENT Specifying Retention Guarantee .CREATE UNDO TABLESPACE undo2 DATAFILE ‘C:\oradata\undo2.ALTER SYSTEM SET UNDO_RETENTION=600.12/1/2010 AUTOMATIC UNDO MANAGEMENT Undo tablespace may need to be increased to support long running queries that needs consistent reads UNDO_RETENTION parameter detarmines how long to retain undo data for consistent reads Can be modified dynamically .dbf’ SIZE 30M AUTOEXTEND ON RETENTION GUARANTEE.
Password Privileges .12/1/2010 PRIVILAGES AND ROLES CONTROLLING USERS AND SECURITY Control over security .Oracle server provide tools by which the DBA can ensure security of the data . Roles 46 .Use of User name.
Assign a default and temporary tablespaces -Decide privileges and roles 47 . CREATING USER Consider following when creating User .Identify table space . a schema with the same name is created for that user.12/1/2010 DATABASE SCHEMA A schema is a named collection of database objects that are associated with particular user When a database user is created .Decide quota on each tablespaces .
12/1/2010 CREATING USER DATA DICTIONARY AUTHENTICATION Syntax CREATE USER username IDENTIFIED BY <password>[DEFAULT TABLESPACE ts_name][TEMPORARY TABLESPACE ts_name][QUOTA<integer[K|M]| UNLIMITED > ON ts_name][PASSWORD EXPIRE][ACCOUNT<LOCK|UNLOCK>][PROFILE< profile_name|DEFAULT>]. CREATING USER DATA DICTIONARY AUTHENTICATION Example CREATE USER Anil IDENTIFIED BY xxyyzz DEFAULT TABLESPACE user1 TEMPORARY TABLESPACE temp QUOTA 10M ON user1 QUOTA 10M ON data PASSWORD EXPIRE ACCOUNT UNLOCK 48 .
user will be prompted to change his password at the first log in CHANGING USER QUOTA Syntax: ALTER USER user_name [DEFAULT TABLESPACE ts_name] [TEMPORARY TABLESPACE ts_name][QUOTA<integer[K|M|UNLIMITED>O N ts_name].If default tablespace is not assigned then system tablespace is assigned as the default . .12/1/2010 CREATING USER Points to remember . E.ALTER USER Anil QUOTA 0 ON user1. 49 .g.If PASSWORD EXPIRE is specified then.
ALTER USER user_name IDENTIFIED BY new_password.ALTER USER Anil IDENTIFIED BY anil87.DROP USER Anil CASCADE.g. The CASCADE option drops all objects in the schema before dropping the user.g .e.12/1/2010 CHANGING PASSWORD Syntax: . . . 50 .DROP USER user_name [CASCADE]. E. DROPPING A USER Syntax: .
51 .DBA_USERS .DBA_TS_QUOTAS PRIVILEGES Privileges .Data confidentiality Only relevant personnel have access to confidential data .Efficient system management Users are allowed to perform limited operations that they need.are rights to execute particular SQL statement Need to grant privileges .12/1/2010 USER INFORMATION Information about users can be obtained from the following views .
System privileges . new users etc.Object privileges SYSTEM PRIVILEGES System privileges allows users to perform particular actions in the database e.Creating public synonyms.Database backup These privileges are normally granted only to DBAs 52 . tables etc.Removing users . .g . .12/1/2010 PRIVILEGES Categories of privileges .
53 .To truncate table of another schema DROP ANY TABLE privilege is required.To connect database CREATE SESSION privilege is required .12/1/2010 SYSTEM PRIVILEGES Category Index Privileges CREATE ANY INDEX ALTER ANY INDEX DROP ANY INDEX CREATE TABLE CREATE ANY TABLE ALTER ANY TABLE DROP ANY TABLE SELECT ANY TABLE UPDATE ANY TABLE DELETE ANY TABLE CREATE ANY SESSION ALTER SESSION RESTRICTED SESSION CREATE TABLESPACE ALTER TABLESPACE DROP TABLESPACE Table Session Tablespace SYSTEM PRIVILEGES Points to remember .CREATE privilege include dropping these objects .
12/1/2010 GRANT-SYSTEM PRIVILEGES Syntax : GRANT privilege1[. GRANT create session .REVOKE CREATE TABLE FROM Anil. . privilege2.user_name2. create table TO Anil. WITH ADMIN OPTION -Enables the grantee to further grant the privilege or role to other users or roles. E.g.REVOKE <system_priv | role> FROM <user_name | role | PUBLIC>.g.] TO USER <[user_name1. REVOKING SYSTEM PRIVILEGE Syntax: .] |role| PUBLIC> [WITH ADMIN OPTION].…. Users with ADMIN OPTION for system privileges can revoke system privileges There are no cascading effect when system privilege is revoked. E.…. 54 .
INDEX REFERENCES .Sub-program SELECT.View . ALTER EXECUTE OBJECT PRIVILEGES Owner has all privilege on objects available in his schema Owner can give privileges on objects owned by him to other users or roles Syntax: GRANT <obj_priv1[(col_names)][. 55 .REFERENCE SELECT .DELETE.….UPDATE.obj_priv2.Sequence .] | ALL > ON object_name TO <user_name|role|PUBLIC>[WITH GRANT OPTION].ALTER SELECT.INSERT.12/1/2010 OBJECT PRIVILEGES Enables users to access and manipulate a specific object Each object has a particular set of grantable privileges .DELETE.UPDATE.INSERT.Table .
]|ALL>ON object_name FROM <[user_name1.privilege2. - REVOKE OBJECT PRIVILEGES Revoke command is used to remove privileges assigned to different users Cascading effects can be observed when revoking a system privilege Syntax: REVOKE <[privilege1.user_name2.12/1/2010 OBJECT PRIVILEGES WITH GRANT OPTION Allows grantee to grant objects privileges to other users or roles Not valid when granting an object privilege to a role Example : Grant select ON emp TO Amit WITH GRANT OPTION. GRANT update (job.deptno) ON emp TO miller. Example: -REVOKE select ON emp FROM Amit 56 .]|role|PUBLIC>.….….
Lists all grants on all objects in the database DBA_COL_PRIVS .Lists system privileges granted to users and roles DBA_TAB_PRIVS .Lists the privileges that are currently available to the user ALL_TAB_PRIVS_MADE .Lists the grants made on the objects owned by the current user ROLE Role is a named group of related privileges that can be granted to users Role provides easy and controlled privilege management Role can consists of both system and object privileges It can granted to any database user or role 57 .12/1/2010 PRIVILEGES INFORMATION DBA_SYS_PRIVS .Lists column privileges SESSION_PRIVS .
synonym. e. create view. functions.Privileges to create programmatic objects such as procedure.types. create table. PREDEFINED ROLE CONNECT . TO engineer. GRANT engineer TO Amol.packages. database link.Privileges to connect to the database and create various objects as cluster . GRANT create session .g CREATE ROLE engineer. Anamika WITH ADMIN OPTION.table.sequence.12/1/2010 CREATE ROLE Syntax: CREATE ROLE role_name.triggers.view RESUORCE . DBA All system privileges with ADMIN option SELECT_CATALOG_ROLE-Select privilege on data dictionary tables 58 .
g. . 59 . Any user with ADMIN option for a role can revoke the role from any other database user or role.role2] FROM <user|role|PUBLIC>. Example: .role2.GRANT engineer TO scott WITH ADMIN OPTION. REVOKING ROLES Syntax: REVOKE role1.[.REVOKE engineer FROM scott.…… TO <user|role|PUBLIC>[WITH ADMIN OPTION] E.12/1/2010 ASSIGNING ROLES Syntax: GRANT role1.
12/1/2010 REMOVING ROLE DROP ROLE command .DROP ROLE role.Removes it from database ADMIN OPTION or DROP ANY ROLE privileges are required Syntax: .Lists system privileges granted to users and roles 60 .Lists the roles defined in the database DBA_ROLE_PRIVS .Lists all the roles granted to users and roles ROLE_ROLE_PRIVS .Lists roles granted to the roles DBA_SYS_PRIVS . ROLE INFORMATION DBA_ROLES .Removes it from all users and roles it was granted .