1 Rookie
•
49 Posts
0
614
November 18th, 2021 06:00
nmda unable to verify caller privileges: Timed out
Hello all,
we are facing errors like this from time to time on different Oracle servers. The backup itself succeds, but the workflow fails with this error. It happens during Oracle backup with NMDA. The backup runs hourly. Once it fails, the next time it succeedes. There are about 70 clients in the group. I can't believe that this only a time out issue on NetWorker site, but I can't explain the behaviour. Additionally there are no helpful entries in other logs. Any ideas for this?
Recovery Manager complete.
RMAN returned success.
WARNING: The savegrp summary could not be obtained.Unable to query save sets by range: Unable to query save sets by range: Unable to verify caller privileges: Timed out
--- Job Indications ---
Unable to query save sets by range: Unable to query save sets by range: Unable to verify caller privileges: Timed out
NW 19.3.0.2 and primarly Oracle 12 and 19
Thanks a lot in advance
onestoned
1 Rookie
•
49 Posts
0
December 3rd, 2021 06:00
I found a possible reason for this behaviour. The success treshold in the action details was set to success. This setting causes NetWorker to report a backup that ends with warnings as failed. As there was a warning for the save set after finishing this workflow was reported as failed. I ensured with the Oracle admins, that all backups are ok. So I set the success treshold to warning and the issue didn't reappear. Thanks all.
Here an explanation of this two settings:
Warning - Save sets that complete with warnings are reported as successful.
Success Threshold - Save sets that complete with warnings are reported as failed. The default value is Success.
barry_beckers
393 Posts
0
November 28th, 2021 13:00
So you make a nmda module based backup every hour for 70 clients in one workflow? I assume it is the redolog backup based on the frequency?
We - up until now - for 2 decades always used a one on one relation when databases are involved, to have a clear separation what is done for what. Also wrg to recognisability (as we reference the DB name in the configuration naming) and freedom to change the start time and frequency for each system/DB involved.
Might be running too much towards too many systems at the same time possibly?
Does it also occur if you use a dedicated worlflow for a DB?