I need to make a copy of production database for development. For some reason I can't use RMAN. My question is: can I copy standby database while its in mounted state and recovery is canceled? Of course I can shut it down to make a "cold backup", but I do not want to lose time for manually copying new archive logs (and I don't have enough space on primary for keeping them for a long time).

The procedure was fine until today. After a few hours I got this:

/usr/sfw/bin/gtar: owfin_d/owfin_d06.dbf: file changed as we read it.

It is strange because timestamps on all db files shows the time when I canceled standby recovery.

UPD After a long time I found the problem. For some reason a scrip on cron schedule changes file permissions and tar responds with "file changed as we read it".

  • You can't afford the normal begin backup/end backup procedure?
    – Mat
    Aug 8, 2014 at 9:30
  • Yep. I can't do it on primary and standby throws error "Database not opened".
    – elfcheg
    Aug 8, 2014 at 10:35
  • why cant you use rman on primary? backup prohibited by policy?
    – Raj
    Aug 8, 2014 at 15:37
  • Interesting. I'm quite sure that nothing at all should write to datafiles in your situation. How did you make sure "recovery is canceled"?
    – kubanczyk
    Aug 8, 2014 at 17:40
  • @Raj I must do backups on standby because of disk performance.
    – elfcheg
    Aug 11, 2014 at 18:46

1 Answer 1


If you change file's permissions during copy operation, tar will throw "file changes as we read it".

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.