Re: RMAN Point in Time DUPLICATE fails with RMAN-20201 RMAN-06010
Date: Wed, 22 Feb 2012 18:55:26 -0800 (PST)
Message-ID: <1329965726.76546.YahooMailNeo_at_web36806.mail.mud.yahoo.com>
can you also try with a different date format? I have come across some strange rman behaviour while using date format anything other than the one noted below.
set until time "to_date('02-17-2012 11:10:00', 'MM-DD-YYYY HH24:MI:SS')";
From: "Mandal, Ashoke" <ashoke.k.mandal_at_medtronic.com> To: Antony Raj <ca_raj_at_yahoo.com>; "oracle-l-bounce_at_freelists.org" <oracle-l-bounce_at_freelists.org>; "oracle-l_at_freelists.org" <oracle-l_at_freelists.org> Sent: Wednesday, February 22, 2012 7:54 PM Subject: RE: RMAN Point in Time DUPLICATE fails with RMAN-20201 RMAN-06010
I was able to duplicate another database by following the similar steps and don't know why I am running into issues with this database.
Following is the set commands as you asked.
Thanks,
Ashoke
set until time "to_date('Feb 17 2012 11:10:00', 'Mon DD YYYY HH24:MI:SS')"; ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1 ENV=(NB_ ORA_SERV=phx00bs2, NB_ORA_CLIENT=phx11db1.tmp.medtronic.com, NB_ORA_POLICY=ora_phx11db1)'; ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1 ENV=(NB_ ORA_SERV=phx00bs2, NB_ORA_CLIENT=phx11db1.tmp.medtronic.com, NB_ORA_POLICY=ora_phx11db1)';
# Set newnames for datafiles
set newname for datafile 1 to '/phx11dbt1/u02/oradata/thdmas/thdmas_system01.dbf'; set newname for datafile 2 to '/phx11dbt1/u02/oradata/thdmas/thdmas_tools01.dbf'; set newname for datafile 3 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_2011_Q1.dbf'; set newname for datafile 4 to '/phx11dbt1/u02/partition/thdmas/unit_test_index_2011_Q1.dbf'; set newname for datafile 5 to '/phx11dbt1/u02/partition/thdmas/thdmas_test_data_2011_Q1.dbf'; set newname for datafile 6 to '/phx11dbt1/u02/oradata/thdmas/thdmas_users01.dbf'; set newname for datafile 7 to '/phx11dbt1/u02/oradata/thdmas/thdmas_general1.dbf'; set newname for datafile 8 to '/phx11dbt1/u02/oradata/thdmas/thdmas_general_index1.dbf'; set newname for datafile 9 to '/phx11dbt1/u02/oradata/thdmas/thdmas_message_log1.dbf'; set newname for datafile 10 to '/phx11dbt1/u02/oradata/thdmas/thdmas_message_log_index1.dbf'; set newname for datafile 11 to '/phx11dbt1/u02/oradata/thdmas/thdmas_test_id1.dbf'; set newname for datafile 12 to '/phx11dbt1/u02/oradata/thdmas/thdmas_test_id_index1.dbf'; set newname for datafile 13 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_correlation1.dbf'; set newname for datafile 14 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_correlation_index1.dbf'; set newname for datafile 15 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_test_archive1.dbf'; set newname for datafile 16 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_test_archive_index1.dbf'; set newname for datafile 17 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_test_change1.dbf'; set newname for datafile 18 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_test_change_index1.dbf'; set newname for datafile 19 to '/phx11dbt1/u02/oradata/thdmas/thdmas_warehouse_transfer1.dbf'; set newname for datafile 20 to '/phx11dbt1/u02/oradata/thdmas/thdmas_test_note.dbf'; set newname for datafile 21 to '/phx11dbt1/u02/oradata/thdmas/thdmas_test_data.dbf'; set newname for datafile 22 to '/phx11dbt1/u02/oradata/thdmas/thdmas_unit_test.dbf'; set newname for datafile 23 to '/phx11dbt1/u03/partition/thdmas/thdmas_unit_test_1992.dbf'; set newname for datafile 24 to '/phx11dbt1/u03/partition/thdmas/thdmas_unit_test_1993.dbf'; set newname for datafile 25 to '/phx11dbt1/u03/partition/thdmas/thdmas_unit_test_1994.dbf'; set newname for datafile 26 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_1995.dbf'; set newname for datafile 27 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_1996.dbf'; set newname for datafile 28 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_1997_Q1.dbf';set newname for datafile 29 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_1997_Q2.dbf'; set newname for datafile 30 to '/phx11dbt1/u02/partition/thdmas/thdmas_unit_test_1997_Q3.dbf';
From: Antony Raj [mailto:ca_raj_at_yahoo.com] Sent: Wednesday, February 22, 2012 5:55 PM To: Mandal, Ashoke; oracle-l-bounce_at_freelists.org; oracle-l_at_freelists.org Subject: Re: RMAN Point in Time DUPLICATE fails with RMAN-20201 RMAN-06010
Hi Ashoke,
There is a failure of your SET command at the top. May I know your SET command(s)?
If you don't set UNTIL TIME "to_date(......................)" correctly,you will get this error.
Thanks
From: "Mandal, Ashoke" <ashoke.k.mandal_at_medtronic.com> To: "oracle-l-bounce_at_freelists.org" <oracle-l-bounce_at_freelists.org>; "oracle-l_at_freelists.org" <oracle-l_at_freelists.org> Cc: "Mandal, Ashoke" <ashoke.k.mandal_at_medtronic.com> Sent: Wednesday, February 22, 2012 6:17 PM Subject: RMAN Point in Time DUPLICATE fails with RMAN-20201 RMAN-06010
Greetings All,
I am trying to duplicate a database but it is failing with the following error:
RMAN-03002: failure of set command at 02/22/2012 14:48:56 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20201: datafile not found in the recovery catalog RMAN-06010: error while looking up datafile: 25
Did some checking in the Metalink but not able to find any solution to my scenario. For example the Metalink Note [ID 1107664.1] refers to a situation where the datafile was created after the date(to which I want to restore the database to]. In my case the datafile was created in 2004 and I am trying to do Pint In time to Feb 17, 2012. I also checked the backup of this file RMAN> list backup of datafile <file#>; It indicates that the datfile was backed up regularly.
This database has 438 datfiles. I hope that shouldn't cause this error.
Please let me know if you any suggestions to resolve this issue and succeed in the RMAN DUPLICATE.
Appreciate your help in advance,
Ashoke
[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records.
To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 22 2012 - 20:55:26 CST