The administration database user has DBA rights to the database, including the ability to run DDL and access system-level objects.
The administration user typically resides on both the source and target databases. During the archive process, the administration user queries the catalog tables. You can use the administration user to create and drop the public database link if the database link to the repository does not exist.
The administration user requires the following user privileges for the installation:
GRANT CONNECT
ALTER SESSION
CREATE SESSION
SELECT_CATALOG_ROLE
CREATE USER
ALTER USER
CREATE TABLESPACE
grant any privilege TO
user_name
with admin option
The administration user typically requires the following user privileges for archive processes:
SELECT DBA_SEGMENTS. Required for the generate candidates row count report.
SELECT ANY TABLE. Not required if the administration user has access to application user tables.
CREATE PUBLIC DATABASE LINK. Not required if the archive connection definition includes the database link name.
DROP PUBLIC DATABASE LINK. Not required if the archive connection definition includes the database link name.
The administration user requires the following user privilege for smart partitioning:
GRANT ANY OBJECT PRIVILEGE
The administration user requires select privileges on the following views in order for the DGA Data Collection job to run successfully:
DBA_DATA_FILES
DBA_FREE_SPACE
DBA_INDEXES
DBA_SEGMENTS
DBA_TABLES
DBA_TABLESPACES
Microsoft SQL Server Requirements
On Microsoft SQL Server, the Administration user must have the serveradmin role.