ORA-01031 when running Intellisnap Backup of RAC

Badge +2

Dear all,


we currently see the ORA-01031 “Insufficient privileges” error in the Oracle alertlog when running an intellisnap backup of a RAC database. The comands to run are 

alter database begin backup


alter database end backup


Each command results in an ORA-01031.


User used to backup has SYSBACKUP privileges.


Any ideas to solve this issue are welcome!





Best answer by westwood71 8 April 2021, 14:25

Hi all,

The issue was that sysbackup role was granted on current container only.

Granting sysbackup to user with “container=all” resolves the issue.



View original

10 replies

Userlevel 6
Badge +14

Hey @westwood71 , thanks for your first post!

Checking our incidents for this error, I have some documentation for you here.

Are you using an Administrator or non-administrator account?

Oracle Connect String for Oracle RAC Instances

The Oracle connect string is a user account that has database administrator privileges that you use to access the standard and recovery catalog databases.

Note: If you want to use a user account other than ‘sys’, you must grant the SYSDBA or SYSBACKUP (in Oracle version 12 or more recent versions) privilege to the user account.

The account information is provided as a connect string with the following information:

  • The Oracle database user ID
  • The password for the user ID
  • The Oracle service name

You can use separate accounts to access the standard database and the recovery catalog database. The recovery catalog database user account must have recovery catalog owner privileges.

By default, the user account for the standard database has administration privileges. If you want to use a different account, use the following table for the user account requirements to access the database:

Account type

The user account must have:


  • Oracle database administration privileges
  • SYSDBA or SYSBACKUP (in Oracle version 12 or more recent versions), ALTER SYSTEM, and SELECT ANY TABLE system privileges.


Access to specific objects (as opposed to the admin account with the SELECT ANY TABLE privilege)

For example:


The Oracle database administrator can establish all other accounts except an Impersonate User account.

Copied from:


Badge +2

Thanks Mike

That is what we did. The user got the SYSBACKUP privilege.

Using RMAN on the commandline everything works fine.



Userlevel 6
Badge +14

@westwood71 , to confirm, are you saying this is resolved and working fine now, or that this works via command line, but not via the GUI?

Want to be sure you’re getting what you need :grinning:

Badge +2

It is working on the RMANcommandline but not in the Commvault GUI

Userlevel 6
Badge +14

Appreciate the confirmation.

Which user do you have in the console configuration as per this doc in step 5d?

Generally if something works on Command line but not in the GUI, it’s a right of the user specified in the configuration, or if there’s a script involved, the user specified has no rights to access the script location (or run the script).

Badge +2


the user configured in the GUI is the same as I used on the CLI. On the CLI I set the environment variables for ORACLE_HOME and ORACLE_SID to the same values as configured in the GUI. 

So my intention is to have a look to the connection string configured in the GUI. Does this makes sense?

Userlevel 6
Badge +14

It makes sense for sure.  I’m going to loop in some other folks on this thread for feedback.

Userlevel 3
Badge +5

Hey @westwood71 ,

It’s quite tricky to troubleshoot this without a review of the configuration + logs - can you confirm the following please?

  • How many nodes in the RAC
  • Inter-connectivity between the RAC nodes using the same account + connection string (Can you connect from Node1 → Node2 in SQL*Plus as the account and issue that command without a privilege error)
  • Does a normal traditional backup (Not IntelliSnap) work ?



Badge +2

Hi Edd,

there are two nodes in the RAC.

Using the connections string I am able to connect from node1 → node2 but the command fails with the same error.

Does that mean we have to change database parameter (e.g. remote_os_roles=true)?



Badge +2

Hi all,

The issue was that sysbackup role was granted on current container only.

Granting sysbackup to user with “container=all” resolves the issue.