After installing the agent, you must grant privileges to the Oracle user account that is used by the Oracle Database Extended agent.
You can grant privileges for the following users:
For RDBMS instances, the Oracle user ID that the Oracle Database Extended agent uses must have select privileges on the dynamic performance views, tables, and data dictionary views that are required by the agent, and must have other Oracle object privileges and system privileges that are necessary to run Take Action commands.
The procedure for granting privileges includes the following actions:
If you do not have Oracle authorized select privileges on some dynamic performance views, tables, and data dictionary views in the krzgrant.sql script, you can customize the krzgrant.sql script before running it.
Edit the krzgrant.sql file in a plain text editor to remove or add the '--' prefix at the beginning of grant statements to skip the granting execution for those unauthorized Oracle tables or views.
execute immediate 'grant select on DBA_HIST_SNAPSHOT to '||userName; execute immediate 'grant select on DBA_HIST_SQLSTAT to '||userName; execute immediate 'grant select on DBA_HIST_SQLTEXT to '||userName; execute immediate 'grant select on DBA_HIST_SQL_PLAN to '||userName; execute immediate 'grant select on DBA_HIST_SYSMETRIC_SUMMARY to '||userName;to these lines:
-- execute immediate 'grant select on DBA_HIST_SNAPSHOT to '||userName; -- execute immediate 'grant select on DBA_HIST_SQLSTAT to '||userName; -- execute immediate 'grant select on DBA_HIST_SQLTEXT to '||userName; -- execute immediate 'grant select on DBA_HIST_SQL_PLAN to '||userName; -- execute immediate 'grant select on DBA_HIST_SYSMETRIC_SUMMARY to '||userName;
The krzgrant.sql script has the following usage: krzgrant.sql user_ID temporary_directory
You must have the Oracle database administrator (DBA) authorization role and write permission to the temporary directory to perform the following procedure.
For logical standby databases, grant permissions on the primary database, and the permissions are replicated to standby databases. For instructions on granting permissions for the primary database, see Granting privileges to users for RDBMS instances.
The physical standby database is a read-only database, and cannot be modified. You can use only the SYS user to monitor the physical standby database.