RBAC roles for the Oracle administrator
To protect and restore Oracle assets, workload administrators must have permissions to access those assets, and to assign credentials to those assets. The RBAC role named Default Oracle Administrator provides the permissions that an Oracle administrator needs. These permissions include all Oracle assets, credentials, storage, and other applicable permissions. Or, that user must have the equivalent permissions in a custom RBAC role.
In addition, you may need other custom roles to give additional access to your Oracle administrators. For example, you may need a role that gives specific privileges to clone a source Oracle database or a pluggable database. This way the user doesn't have access to all the available Oracle backup and recovery operations.
For some environments, you may want to limit the permissions that some RBAC roles have for specific Oracle assets. You can apply specific permissions to the following types of Oracle assets: databases, RMAN catalogs, and Oracle credentials.
See Create a custom RBAC role for Oracle cloning.
Note the following requirements for creating roles and credentials:
To create an RBAC role, you must have the RBAC Administrator role or the permissions to create roles.
To create a credential, you must have the role or a similar role that has permissions to create credentials. The can manage all credentials.
Contact your NetBackup administrator for assistance with creating roles and credentials.
For information on the RBAC permissions and default roles, see the NetBackup API documentation at https://sort.veritas.com/cohesity/.