Skip to main content
Question

Oracle RMAN Backup Failure via Veeam Plug-in: ORA-19511, ORA-27191, and ORA-01012


Hi everyone,

I am currently encountering a recurring issue during our Oracle database backups  using the Veeam Plug-in for Oracle RMAN. The backup job fails with the following sequence of errors

 

3 comments

Chris.Childerhose
Forum|alt.badge.img+23

What version of Veeam are you using?  Did you check the logs here - C:\ProgramData\Veeam\Backup?

I would suggest opening a support ticket to get assistance with this one.  The community itself is not technical support, but if anyone uses this plugin, they may chime in.


  • Author
  • New Here
  • October 16, 2026

Hi Chris, thanks for the reply.

We’re on Veeam B&R 12.1.1.56 (Oracle plug-in 12.1.0.2131). I checked the logs in C:\ProgramData\Veeam\Backup, and the main finding is this:

The RMAN errors (ORA-19506 / ORA-27028 / ORA-19511) are only the SBT/Media Manager layer reporting a failure. The “configuration database is currently unavailable” message is misleading, because the VBR logs show the configuration database was reachable the whole time. Other jobs started normally at 22:00, and the Oracle hosts authenticated successfully.

The actual lead is in the plug-in logs:

  • Backup is not in user's control scope
  • dataBase.FindBackupByJobIdThrowIfWrongOwner
  • Unable to find backup by job id

This points to a backup ownership / job ID mismatch in the plug-in workflow. The main job and the separate “Oracle DB Redo Logs Backup” job may also be overlapping, since the log shows “job is already running, starting second time cancelled” right before the failure.

I’m not able to open a support ticket on my side, so if anyone has seen the “WrongOwner” / “not in user’s control scope” error with the Oracle RMAN plug-in, I’d appreciate hearing how you resolved it. Could the job ownership or the Oracle credentials used for the job be the cause?


coolsport00
Forum|alt.badge.img+23

Hi ​@emnaa - Welcome to the Community!

As Chris shared...you should first open a Veeam Support ticket and further troubleshoot with them. One option you can try, depending on the version of Veeam you use, is to either look at the logs and go from there, or plug in your errors into Veeam Intelligence in the Veeam Console and see what it suggests you to look at to further troubleshoot & resolve. Your error...at least the 1st one… points to some kind of authorization/non-access permission type error.