Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: can not identify file when Rman duplicate standby database

Re: can not identify file when Rman duplicate standby database

From: Jesse <jesjdavis_at_gmail.com>
Date: 12 Apr 2005 09:23:35 -0700
Message-ID: <1113323015.793634.134950@o13g2000cwo.googlegroups.com>


Be nice now... ;-) Having just gone through this, I can understand Yoke's confusion, even if he had read the manual (he doesn't state whether or not he has, but given the detail of his post, he must have read something). As Holger's quote from the manual states, "make sure that all backups...are remotely accessible from the duplicate host." This leads me to believe that simply mapping/mounting the drive/path from the duplicate would be sufficient (i.e. make backup path look the same as it does on target DB). This isn't always the case.

I know that Yoke isn't using Windows for his target DB, but we do (Win2k3 Server EE) and trying to duplicate using a mapped drive (on our target DB, the backups are stored on R:\....) fails in RMAN (similar message to what Yoke received; i.e. couldn't find file). Instead it requires that you change the RMAN config for the target DB to use UNC paths instead of drive letters. This is only necessary if you use a remote drive though (meaning, remote to the duplicate host). I was able to get around this by installing a second HD on the duplicate node, assigning it R:, and copying the backup sets (and archive logs) as needed to the duplicate node's R: drive. Note: This was preferable over changing the RMAN config for the target DB for two reasons. First, the target DB was in production and we were just setting up a duplicate node for development/testing (couldn't afford the restart). Second, UNC can often-times be slower than using drive letters in Windows. Anyway, I have various scripts/jobs running to copy and cleanup the backup sets as needed.

Again, I know Yoke isn't using Windows for his target DB, but my point is that there are often undocumented "features" that may cause unexpected results (even when you believe that you've understood/followed the docs). In short, copying the files to standby node may be his best bet (it''ll work easiest if he can mimic the path used by the target DB).

Jesse Received on Tue Apr 12 2005 - 11:23:35 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US