Predefined Roles Evolution From 8i to 10g R2: CONNECT Role Change in 10gR2
(Doc ID 317258.1)
Last updated on DECEMBER 01, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 3-Apr-2013***
This bulletin describes the evolution of the predefined roles in an Oracle database from 8i to 10g R2.
7 : predefined roles : CONNECT, DBA, RESOURCE, EXP_FUL_DATABASE, IMP_FUL_DATABASE
8i : new roles : SELECT_CATALOG ROLE, EXECUTE_CATALOG_ROLE, DELETE_CATALOG_ROLE
(ref <Note 1060417.6> ORACLE_8 ROLES)
10.2 : CONNECT role changes
Oracle Database 10g Release 2 provides additional security in deploying secure configurations by helping enforce the least privilege principle: the much used CONNECT role has been modified to include only those privileges required to connect to the database, namely the CREATE SESSION privilege.
For all DBAs and Security DBAs using the CONNECT role in many scripts and assigning this highly used role to users.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Approach 1 - Create a new application role|
|Approach 2 - Restore CONNECT privileges|