Privileges for Oracle

To automatically create schemas, tables, and views during model deployment, the user-specified authentication alias for Monitor_Admin_Database must be granted the privileges listed in this topic. If the authentication alias that is associated with the Monitor_Admin_Database does not have these privileges, you must manually create the database schema for monitor model deployment, undeployment and data movement services (DMS) enablement.

Note: Although a model schema can be automatically created for an Oracle database during model deployment, it is generally recommended that you manually create the schema. The reason for this recommendation is that the automated database scripts include commands that create and drop tables and views and these commands are not transactional with Oracle. If the scripts fail to complete successfully, any resulting problems must be manually fixed because rollback is not supported for Oracle databases. However, if you fully understand the potential problems of having model schema automatically created for an Oracle database and you can arrange for any problems to be manually fixed, there may be situations where you can tolerate the risk for the sake of productivity. For example, in a development environment where problems are more easily tolerated and fixed, you may choose to have the schemas automatically created to save you time. However, in a production environment, problems cannot be tolerated and any problems that are encountered must be rapidly resolved by the database administrator. For this reason, it is strongly recommended that you manually create the model schemas for any production environment.

To automatically create schemas, tables, and views during model deployment, the user-specified authentication alias for Monitor_Admin_Database must be granted the following privileges:

The following table describes the database grants that are required for the user specified in the Monitor_Database authentication alias.

Database privilege Scope
SELECT All tables and views in the MONITOR schema and all tables and views in the monitor model schema
INSERT All tables and views in the MONITOR schema and all tables and views in the monitor model schema
UPDATE All tables and views in the MONITOR schema and all tables and views in the monitor model schema
DELETE All tables and views in the MONITOR schema and all tables and views in the monitor model schema
EXECUTE All stored procedures in the monitor model schema