RMAN Question

From: Scott Canaan <srcdco_at_rit.edu>
Date: Wed, 06 Mar 2013 09:24:24 -0500
Message-id: <A9F069F06B325049A1D90D1F8EBEB8B6C134807902_at_ex02mail02.ad.rit.edu>



I am running Oracle 11.2.0.3 on Linux, 64-bit. I am trying to create a physical standby database. Both databases are on the same physical server - this is just to work out the procedure. Normally we clone databases to make copies, but that just ends up making another Primary database and I can't get it to change to standby, so I'm trying to follow the directions for creating a standby via RMAN. I am following the directions online (found in two places), using the script found online, modified for our environment, and keep getting an ORA-19505. Normally, I would not have any problem with this, but unlike the examples online, it doesn't tell me which file it can't access, so I don't know how to fix the problem. The end of the run looks like: Starting backup at 06-MAR-13
channel prmy1: starting datafile copy
copying standby control file
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stby
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/06/2013 09:19:11
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script RMAN-03009: failure of backup command on prmy1 channel at 03/06/2013 09:19:11 ORA-17628: Oracle error 19505 returned by remote Oracle server

RMAN> **end-of-file**

RMAN> How do I figure out what file is causing the ORA-19505?

Scott Canaan '88 (srcdco_at_rit.edu<mailto:Scott.Canaan_at_rit.edu>) (585) 475-7886 - work (585) 339-8659 - cell "Life is like a sewer, what you get out of it depends on what you put into it." - Tom Lehrer.

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Mar 06 2013 - 15:24:24 CET

Original text of this message