"BR0253W errno 13: Permission denied"

[Former Member]

Hi,

NW2004s under windows 2003 server, Oracle 10g

I done backup sucessfully through DB13 schedule job, using sidadm username and password, Whole online backup and archived

now i am trying to restore same backup...

1 - Goto Remote Desktop of server using User: sidadm and password

2 - Stop SAP instance and database

3 - Goto command prompt which is backup store and run

4 - Brrestore -b (backup log file) -m all -p initBIQ.sap

While Restoreing I got an error "BR0253W errno 13: Permission denied" Restore done with warring

I have found several links in the internet but haven't found the right approach.

Thank in advance

Regards

[former_member204746 · Accepted solution]

what are:

1. your Source SID

2. your destination SID

3. which user are you logged on with on your destination system.

[Former Member · Accepted solution]

Hi Eric,

here is summary:

C:=installed OS

D:\SAP application

E:\Archived logs

F:\database

all is one hdd with partitions

backup store in extrinal or network HDD

I login sidadm and goto network HDD and run restore command

[Former Member]

Hi Angeline,

Check the permissions of brrestore in /sapmnt/<SID>/exe directory.

chown <SID>adm:sapsys brrestore

chmod 775 brrestore.

Check the permission of backup file (.anf file). and try to re-run the restore.

Thanks,

Nick S

[Former Member]

Hi,

I am getting backup data to restore from extrinal drive... and I already give full permission and add user in extrinal drive... user sidadm

Restore again but I got same messages "BR0253W errno 13: Permission denied"

Remember I have windows 2003 server

any other clue

Here is error screenshot

http://www.flickr.com/photos/38842895@N04/4558463080/sizes/o/

Regards

Edited by: AngelinePurnama on Apr 27, 2010 7:57 PM

[volker_borowski2]

Hi,

actually it is not an error allthough it should not occur.

The message clearly says that the file is still in use and can not been overwritten.

It then waits a couple tries for oracle to release it, because it assumes a still runnning

database holding a lock on a meanwhile non existing file.

Those messages where quite common in the old

"sapdba reorg tablespace with datafiles" actions when the old TS was dropped.

But they should not occur for restore, if the instance is really down

How did you stop the system?

Just MMC -> stopsap ? That wil NOT shut down the database !

You'd need to do

brconnect -c -u / -f dbshut

in addition!

Volker

[Former Member]

Thanks for reply

I wasn't shutdown database from sql

Now I shutdown

sqlplus /as sysdba

shutdown /abort;

exit

and run restore again... lets see if does works... also I give permission to oracleservie_SID in widnows services...

right click on OracleServieBIQ and login TAB and add sidadm user in it...

let see

Thanks for you time

[kishore_soma]

hi

correct the log also shows that the datafile is being locked and usd by database, so unable to delete the file. So stop the database either by sql prompt or from services.msc, then u start restoring.

But better would be delete all the files

> - datafiles

> - origlog files (online redolog files)

> take the backup of existing controlfiles and delete it.

> then try restoring it would be easy

Regards,

Kishore Soma