The geodatabase administrator account in Oracle is the account that owns the schema where the geodatabase repository resides. The geodatabase administrator for the sde geodatabase must be named sde. This account owns and manages the following:
- The system tables, triggers, and procedures that make up the sde geodatabase
- The SQL types and functions
- The Default geodatabase version in the sde geodatabase
In addition to the main, sde geodatabase, you may have geodatabases in the schemas of other users. The administrator for those geodatabases is the schema owner. That user owns and manages the following:
- The geodatabase system tables, triggers, and procedures in the user's geodatabase
- The Default geodatabase version within the user's geodatabase
Keep in mind that the geodatabase administrator user is not the same as the database administrator. Although conditions at your site may necessitate that the geodatabase administrator have database administrator-level permissions, this is not required for day-to-day operation of a geodatabase.
Geodatabase administrator's schema
It is recommended that the sde user's schema only be used to manage and store the sde geodatabase repository. Create separate users to create datasets, such as feature classes and raster datasets.
If the database contains user-schema geodatabases, the owners of the user-schema geodatabase can only own data in that geodatabase; the user-schema geodatabase owner cannot own data in the sde geodatabase or any other user's schema geodatabase. Users who do not own a user-schema geodatabase can only own data in the sde geodatabase. See The relationship between the sde and user-schema geodatabases in Oracle for more information.