rman recover table

[PeterMichalica]

Oracle rman has a feature since 12.1 to recover one or more tables from a certain timestamp or SCN from a standard database backup.
The command in it's simplest form is:
recover table <tablename> until <time> remap <original name>:<new name>;
When started it creates an auxiliary database with a random SID but with the original db_name in the background and tries to restore the minimum necessary database files to retrieve the table.
The problem now is that the Veeam Plug-in for Oracle RMAN throws an error and the restore fails:
"The database <random SID> must be added to a backup policy."
For Veeam this is an unknown database and therefor it denies the restore of database files from a known SID.
Other backup software do support this kind of restore.
Has anyone else experienced this behaviour and maybe found a solution?
The workaround is of course to restore the database (full or partly) to another server and manually extract the table(s).

[PetrM]

Hi Peter,

The error itself is thrown by our code: it is intended to inform users that we can only back up databases that are added to a policy. This error appears only when you use the plug-in in managed mode. However, this situation is different: you are restoring a table. My guess is that RMAN performs an auxiliary backup activity, such as a control file backup, before running the restore.

Here’s what I propose at the moment:
1. Please rerun the test in standalone mode.
2. Open a support case and share the case ID.
3. I will discuss this issue with my colleagues from QA.

Thanks!