Delete Obsolete - Operate Networker Privilege ?

Question

Hello,

I wanted to get your valuable help for a problem we are facing in one of our Networker server. We have been backing up Oracle database using NMO module by not using a rman catalog with 5 days of retention. Current redundancy value in rman configuration is 5 and NSR browse and retention values are all 5days and we are backing this database daily full. We tried a restore test and get restore errors about not finding one of the needed saveset. We quaried this saveset (with piece name) and noticed that it is listed as expired in networker index. We wanted to check backup saveset list in control file and noticed that even backups that has succesfully finished 3 weeks ago are listed there. We wanted to clear this by using "delete obsolete" command.

When we run this command we get the below error.

ORA-19509: failed to delete sequential file, handle="c-697904151-20121116-05", parms=""

ORA-27027: sbtremove2 returned error

ORA-19511: Error received from media manager layer, error text:

Permission denied, user 'oracle' on 'mhrsdb2' does not have 'Operate NetWorker' privilege to perform this operation - NSR.

When we quary this saveset in networker it is listed as browsable. Today is 21.11.2012 19:22, it needs to be expired?

mhrsdb2 126 MB full RMAN:c-697904151-20121116-05 16.11.2012 02:34:25 21.11.2012 21.11.20120 cb

Networker Server: Windows 2003 R2, Networker 7.6.3.5

Networker Client: Linux x64, Networker 7.6.3.1, NMO 5.0

Why are we getting this error? I think this privilege is needed because it tries to expire a browsable backup. Why nsr retention and catalog file does not match?

ble1 · Answer

I believe your issue is that oracle user does not have permission to browse index and in return on client side this is seen as backup set does not exist or it is gone. As you probably know, Oracle highly recommends to use catalog database (actually, I believe for production they require it now) and switching to catalog instead of control files makes restores much easier.

ble1 · Answer

For index management, user will require additional permissions - that's normal (though bit of a pain for certain view). Simply add oracle user at that host to admin list and you are done.

The reason why mentioned permissions is because you say restore didn't work and mminfo confirms that backup set is there. That is typical situation where oracle user is not able to browse index. You easily check that by going to the host mhrsdb2 and from there, as oracle user, do "nsrinfo -s -n oracle mhrsdb2" (without quotes). This is actually similar to what restore is doing (except restore uses also -N to track faster backup set it looks for).

Sturm3 · Answer

Hello Hrvoje,

Oracle has the required permissions to browse/restore/backup local data. As you can notice 'Operate NetWorker' privilege is asked, which I think is administrator rights.

You are right with switching to catalog, I have also gave advice to customer, but it will take a while and we need to perform their restore need.

Bebo2k · Answer

Hi Sturm,

You have to add the oracle user as an administrator not only with Operate NetWorker privilege specially for the index operations, from the backup server run the following:

nsraddadmin -u oracle@mhrsdb2

It should works correctly after that.

Hope this helps,

Ahmed Bahaa

Sturm3 · Answer

Hello,

Thanks for your replies, I didnt want to give administrator rights but I will try your solutions.

So administrator rights is required for oracle backup/restores? Why isnt browse/restore/backup local data is not enough?

_x_x · Answer

good !

NetWorker

Delete Obsolete - Operate Networker Privilege ?

Was this post helpful?