The tasks involved in setting up and using the Oracle Autonomous Database dedicated Exadata infrastructure feature can be grouped into three logical roles: a few people act as fleet administrators, more act as database administrators, and even more act as database users. A given person can assume one or more of these roles, depending on how you decide to isolate and distribute duties.
Fleet Administrator. Fleet administrators create, monitor and manage the core (Autonomous Exadata Infrastructure, Exadata Infrastructure and Autonomous Exadata VM Cluster) and Autonomous Container Database resources.
To perform these duties, a fleet administrator must be an Oracle Cloud user whose permissions permit the management of these resources and permit the use of the networking resources that need to be specified when creating these resources.
Database Administrator. Database administrators create, monitor and manage Autonomous Databases. Additionally, they create and manage Oracle Database users within these databases, and provide others the information necessary access the database.
To perform these duties, a database administrator must be an Oracle Cloud user whose permissions permit the management of Autonomous Database and Autonomous Backup resources and permit the use of the Autonomous Container Database and networking resources that need to be specified when creating an Autonomous Database. When creating an Autonomous Database resource, the database administrator defines and gains access to the ADMIN administrative user account for the database.
Database User. Database users are the developers who write applications that connect to and use an Autonomous Database to store and access the data. Database users do not need Oracle Cloud accounts: they gain network connectivity to and connection authorization information for the database from the database administrator.