Clone from recovery catalog
Hi,
Every month i am doing duplicate from prod to test database,from coming month i have to change my strategy to do clone from standby instead of production.so i have created recovery catalog and registered my standby.my queston ,is it possible to do duplicate from recovery catalog to test database.if possible,this is my connection
rman catalog rman/rman123@catdb auxiliary /;,and i should do any modification in Recovery catalog. pls suggest me to do the cloning from RC.if possible
my database 10.2.aix server.
Regards
Faruk
You can use a recovery catalog when doing a cloning / DUPLICATE.
Note, however, the 10.2 restrictions on the DUPLICATE Command : http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta028.htm#RCMRF126
You must be connected to both the target database and auxiliary instance. The auxiliary instance must be started with the NOMOUNT option, and the target database must be mounted or open. The target database cannot be a standby database.
Hemant K Chitale
Similar Messages
-
Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AMThis Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete. -
Switching RMAN from Recovery Catalog DB to target db controlfile
I have a doubt.
Is it possible to make RMAN to use controlfile, from using Recovery Catalog(RC) DB ?
The scenario is like this:
I have a target db and a RC db. The RMAN presently uses RC db for backup and recovery.
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup (That is, controlfile should understand backup sets, which have backed-up using RC )
Is there a way to perform these tasks?Hi,
The rman backup information in the controlfile has a limitation due to space constraints in the controlfile.
Oracle uses the parameter "control_file_record_keep_time" which defaults to 7 days to purge rman backup information from the controlfile. (So if you run rman backups the backup information in the controlfile will be automaticly purged.)
If you run rman using a catalog the controlfile will synchronize new informaton to the catalog at the start of every backup but it won't actively purge information from the catalog. So the catalog (next to other features) has the ability to store information longer than the controlfile. (Delete commands will be needed to purge information from the catalog.)
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?Just skip the connect to the catalog in your script.
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup > (That is, controlfile should understand backup sets, which have backed-up using RC )This is not easy to answer, your restore might work if the backup information is still available in the controlfile (younger than control_file_record_keep_time). Success is not related to the fact the backup was taken with the controlfile and RC at the same time.
Regards,
Tycho -
Hello
How can I see the backup interval, database versions of the databases in recovery catalog ?adam wrote:
Hello
How can I see the backup interval, database versions of the databases in recovery catalog ?Which database interval, versions you want to check? Check for the views starting from rc_ and you would get to know all about recovery catalog.
Aman.... -
Query to identify the recovery catalog database name from target database
Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi PYou can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM -
Unregistering of a database from RMAN Catalog
Hello,
We had set up RMAN backup though RMAN Catalog for one of our database.
We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
We know that the tapes don't have the backup of this database.
Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
Thanks!Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
I have another question though -
We have compressed backup for one of the database/
If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
Question - How to check the compressed size of the backupset from the Catalog tables/views?
Thanks for your help on this!
Thanks!
, -
RMAN-20001: target database not found in recovery catalog
I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
RMAN> startup nomount;
Oracle instance started
Total System Global Area 209715200 bytes
Fixed Size 1272864 bytes
Variable Size 155190240 bytes
Database Buffers 50331648 bytes
Redo Buffers 2920448 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /u02/flash_recovery
database name (or database unique name) used for search: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Finished restore at 08-SEP-10
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.Hi BelMan,
Here is output
BS Key Type LV Size Device Type Elapsed Time Completion Time
56869 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
56993 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10 -
Error installing recovery catalog
Hi,
Inorder to implement RMAN in oracle 10g in windows environment I created a separate table space for rman and created a user as rman1;
then I issued the following commands :
GRANT connect, resource, recovery_catalog_owner TO rman1
grant create session to rman1;
grant create type to rman1;
then i entered into rman from dos prompt,
rman catalog=rman1/rman1@tc
from rman prompt I issued the command,
create catalog tablespace RMAN1;
then the following error occurs,
RMAN> create catalog tablespace RMAN1;
ORACLE error from recovery catalog database: ORA-01031: insufficient privileges
RMAN-00571: ====================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ====================================
RMAN-06433: error installing recovery catalog
Due to this error I am unable to proceed further and let me know the solution.
Thanks in advance.
Regards,
A.Mohammed Rafi.Hi,
Thanks for the help and the problem is solved.
Now I am facing another problem,
RMAN-03009: failure of catalog command on default channel
ORA-19657: cannot inspect current datafile D:\ORACLE\PRODUCT\10.1.0\DB_2\TC\EXAMPLE01.DBF
Could you please help me in this regard. -
Specification does not match any archive log in the recovery catalog
Hi
My rman backups sometimes fails with below error, any idea the reason ?
run {
allocate channel t1 type 'SBT_TAPE';
backup
incremental level 0
format '/%d_%p_%t.%s/'
maxsetsize = 8G
(database);
backup
format '/%d_%p_%t_al.%s/'
(archivelog from time 'SYSDATE-2');
backup
format '/%d_%p_%t_al.%s/'
(archivelog until time 'SYSDATE-2' delete input);
release channel t1;
Starting backup at 2011-01-18 22:41:59
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=7348 recid=6260 stamp=740682001
input archive log thread=1 sequence=7349 recid=6261 stamp=740702540
input archive log thread=1 sequence=7350 recid=6262 stamp=740739604
input archive log thread=1 sequence=7351 recid=6263 stamp=740746801
input archive log thread=1 sequence=7352 recid=6264 stamp=740757602
input archive log thread=1 sequence=7353 recid=6265 stamp=740768401
input archive log thread=1 sequence=7354 recid=6266 stamp=740788921
channel t1: starting piece 1 at 2011-01-18 22:42:04
channel t1: finished piece 1 at 2011-01-18 22:42:29
channel t1: backup set complete, elapsed time: 00:00:26
Finished backup at 2011-01-18 22:42:29
Starting backup at 2011-01-18 22:42:31
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/18/2011 22:42:31
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
Recovery Manager complete.Hi Ora 83,
What is the reason of this error ? The reason for the RMAN-20242 is there are no archivelogs which comply to the filter "until time 'SYSDATE-2'" at 18 Jan 22:42.
Probably you run a purge command more frequent because the oldest logsequence available for backup was created at:
2011 JAN 17 17 00 01 (=sequence=7348)
and the latest at:
2011 JAN 18 22 42 01 (=sequence=7354)
according to your output.
So for some reason the archivelogs created before 16th Jan 22:42 are not on the system as well as the archivelogs created between 16th Jan 22:42 and 17 Jan 17:00.
Maybe there are none (you can check in the alertlog and let us know)?
Regards,
Tycho -
Connecting rman and creating recovery catalog
I'm using oracle8i with Window/Nt
i have two database U10 and U20.
Using recovery manager, target db is U10 and recovery catalog of U10 is saved in U20.
i followed method in oracle8i manual(Rman Part)
when i attempt to connect rman, following message bothers me..
C:\WINDOWS>RMAN CATALOG RMAN/RMAN@U20
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT.
.INTO returns too many rows
RMAN-06097: text of failing SQL statement: select user into :b1 from dual
RMAN-06099: error occurred in source file: krmk.pc, line: 3842
and when i attempt to create recovery catalog, i got a bunch of message
RMAN> CREATE CATALOG TABLESPACE "RCVCAT"
RMAN-06099: error occurred in source file: krmk.pc, line: 6549
RMAN-06097: text of failing SQL statement: CREATE TABLE db
db_key NUMBER NOT NULL, -- sequence generated primary key
db_id NUMBER NOT NULL, -- kccfhdbi from controlfile
-- updatable columns
curr_dbinc_key NUMBER, -- current incarnation
CONSTRAINT db_p PRIMARY KEY (db_key),
CONSTRAINT db_u1 UNIQUE(db_id) -- ensure that db_id is unique
tablespace "RCVCAT"
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06433: error installing recovery catalog
i'm so hectic... plz help me....Based on the following errors:
RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT..INTO returns too many rows
RMAN-06097: text of failing SQL statement: select user into :b1 from dual
It looks like the table dual has more than 1 row.
select * from dual;
What do you get?
It should look like this:
D
X
1 row selected.
Your recovery catalog database may have a problem. You may need to start over and recreate the recovery catalog.
null -
Registering Clone database in Recovery catalog
Can we able to register the clone database in recovery catalog database without changing dbid?
I don't want to use dbid utility.
Is that any parameter?
Regards,
LathaWell you can register it without changing any parameters in oracle 10.2
That does not mean you should do it.
I would have answered as follows:
It is not a good idea to register a clone database in the same recovery catalog as the original database as the recovery catalog uses the dbid to identify the database and having two databases with the same dbid essentially corrupts the recovery catalog.
If you change the dbid then it is perfectly okay to store the cloned database in the same recovery catalog. -
From no recovery catalog to recovery catalog
sorry for the message to be posted 2nd time due to error in internet connection.
Message was edited by:
Nitesh JainHi Nitesh Jain!
First thing to do ist to register all your database in the RC (RC = Recovery Catalog)
test@localhost> rman target system/oracle@PRODDB1 catalog catowner/password@CATDB
REGISTER DATABASE;
exit;
In this example PRODDB1 is your first production Database and CATDB ist your Catalog database. The REGISTER DATABASE Command registers your DB in the RC. Do this step for all your productiv DBs.
Next thing to do is to resync your controlfile with your RC for all your productiv DBs.
i]test@localhost> rman target system/oracle@PRODDB1 catalog catowner/password@CATDB
RESYNC CATALOG;
exit;
RESYNC CATALOG takes all Information from your controlfiles and puts it into your RC.
This should be all. You can use LIST BACKUP to check whether your Backups are registered in your RC or not. If you have to register Backups manually try the CATALOG START WITH '/path_to_your_backups/' Command. You can read about it in the Onlinedocumentation in the RMAN Reference.
Hope this helps! -
Oracle 10.2.0.4 RMAN Duplicate without a Recovery Catalog
Production Backups are Tuesday - Sunday at 22:00:
RUN {
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
CROSSCHECK ARCHIVELOG ALL;
CROSSCHECK BACKUP;
DELETE NOPROMPT COPY OF ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';
DELETE NOPROMPT BACKUP;
BACKUP DATABASE PLUS ARCHIVELOG;
CROSSCHECK BACKUP;
RELEASE CHANNEL c1;
LIST BACKUPSET;
EOF
I have these files sent over to the development server on Wednesday, RMANbackup (log), backupset and the controlfile:
rcp -rp /backup/$1/flash_recovery/$2/RMANbackup/* kacdb4:/backup/common/flash_recovery/$2/RMANbackup
rcp -rp /backup/$1/flash_recovery/$2/backupset/* kacdb4:/backup/common/flash_recovery/$2/backupset
rcp -rp /backup/$1/flash_recovery/$2/controlfile/* kacdb4:/backup/common/flash_recovery/$2/controlfile
I run the RMAN Duplicate and the database gets created with no problems!
The question is: If I wait unit Thursday, to run the duplicate script, I get the traditional RMAN errors: RMAN-03002, RMAN-03015, RMAN-06026, RMAN-06023:
Starting restore at 20-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/20/2012 10:05:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
Is this because of the 'SYSDATE-2' in the RMAN runlist? Does RMAN connect back to the target and it does not find the logs, because they've been deleted, it aborts the duplicate? I've shipped over the backupset and controlfile of the scn I'm using in the duplicate runlist all is there? If I'm trying to cleanup the archive area, would'nt 'delete expired archivelog all' in my runlist, be better than using the 'SYSDATE-2'?
Or is it because of this database parameter:
control_file_record_keep_time= 7, should I set this to say 14?
Is it one of these RMAN configurations:
Retention Policy to Redundancy 1, should I set this to say 7?
Datafile Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space which is precious
Archivelog Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space too
Archive deletion policy to none change this to the other option?
I've tested this a few times now, and always fails if the dupicate is not done the next day.
If I have to create a development database on a Friday from Tuesday's copy FROM TAPE, I will get the error, because the files are no longer on disk.
What can I do to ensure that I can create an RMAN duplicate any day of the week from Tuesday to Sunday?
Look forward to your answer.
Please let me know if I left any details out that you may need.
Sincerely,
Elizabeth BurnsHi Valentin,
Here is the good duplicate log from Monday 9/24:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120924.log
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:32 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:41 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:43 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 24-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 24-SEP-12
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /usr/local/OLlinks/dupdb/system/system01.dbf
restoring datafile 00002 to /usr/local/OLlinks/dupdb/system/undotbs01.dbf
restoring datafile 00003 to /usr/local/OLlinks/dupdb/system/sysaux01.dbf
restoring datafile 00004 to /usr/local/OLlinks/dupdb/system/users01.dbf
restoring datafile 00005 to /usr/local/OLlinks/dupdb/data01/data1.dbf
restoring datafile 00006 to /usr/local/OLlinks/dupdb/index01/index1.dbf
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T1
01837_860txxs8_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T101837_860txxs8_.bkp tag=TAG
20120924T101837
channel aux1: restore complete, elapsed time: 00:00:47
Finished restore at 24-SEP-12
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858918 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858918 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
set until scn 211054288;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 24-SEP-12
starting media recovery
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=1403
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T1
01923_860tzfd7_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T101923_860tzfd7_.bkp tag=TAG
20120924T101923
channel aux1: restore complete, elapsed time: 00:00:05
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc thread=1 sequenc
e=1403
channel clone_default: deleting archive log(s)
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc recid=1 stamp=79
4858923
media recovery complete, elapsed time: 00:00:02
Finished recover at 24-SEP-12
contents of Memory Script:
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora';
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
set newname for tempfile 1 to
"/usr/local/OLlinks/dupdb/temp/temp01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/users01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/data01/data1.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/index01/index1.dbf";
switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed temporary file 1 to /usr/local/OLlinks/dupdb/temp/temp01.dbf in control file
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf recid=1 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf recid=2 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/users01.dbf recid=3 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/data01/data1.dbf recid=4 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/index01/index1.dbf recid=5 stamp=794858932
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858932 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858932 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
database opened
Finished Duplicate Db at 24-SEP-12
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:09:39 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
User altered.
User altered.
User altered.
User altered.
Database closed.
Database dismounted.
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Database mounted.
Database altered.
Database altered.
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Here is the duplicate log from this morning:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120926.log
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:31 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:42 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:45 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 26-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 26-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/26/2012 08:28:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:53 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
alter user sys identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user system identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user dbsnmp identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user sysman identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
ORA-01507: database not mounted
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
ORA-00205: error in identifying control file, check alert log for more info
alter database noarchivelog
ERROR at line 1:
ORA-01507: database not mounted
alter database open
ERROR at line 1:
ORA-01507: database not mounted
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Please let me know if you need anything else.
Sincerely,
Elizabeth -
Recovery Catalog showing wrong Archive Destination
Hi All,
I am using Oracle 10g on Solaris 10.
The problem I am facing is this, while taking backup using recover catalog..............
Starting backup at 27-JUL-11
current log archived
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/27/2011 11:16:47
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
This is because of the following reason
RMAN> list archivelog all;
List of Archived Log Copies
Key Thrd Seq S Low Time Name
39401 1 1567 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1567_756523261.dbf
39402 1 1568 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1568_756523261.dbf
39403 1 1569 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1569_756523261.dbf
39404 1 1570 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1570_756523261.dbf
39405 1 1571 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1571_756523261.dbf
39406 1 1572 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1572_756523261.dbf
39407 1 1573 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1573_756523261.dbf
39408 1 1574 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1574_756523261.dbf
39409 1 1575 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1575_756523261.dbf
39410 1 1576 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1576_756523261.dbf
39411 1 1577 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1577_756523261.dbf
39412 1 1578 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1578_756523261.dbf
39413 1 1579 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1579_756523261.dbf
39414 1 1580 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1580_756523261.dbf
39415 1 1581 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1581_756523261.dbf
39416 1 1582 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1582_756523261.dbf
39417 1 1583 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1583_756523261.dbf
39418 1 1584 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1584_756523261.dbf
39419 1 1585 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1585_756523261.dbf
39420 1 1586 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1586_756523261.dbf
39421 1 1587 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1587_756523261.dbf
39422 1 1588 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1588_756523261.dbf
39423 1 1589 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1589_756523261.dbf
39424 1 1590 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1590_756523261.dbf
39425 1 1591 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1591_756523261.dbf
39426 1 1592 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1592_756523261.dbf
39427 1 1593 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1593_756523261.dbf
39428 1 1594 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1594_756523261.dbf
39429 1 1595 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1595_756523261.dbf
39430 1 1596 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1596_756523261.dbf
39431 1 1597 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1597_756523261.dbf
39432 1 1598 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1598_756523261.dbf
39433 1 1599 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1599_756523261.dbf
39434 1 1600 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1600_756523261.dbf
39435 1 1601 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1601_756523261.dbf
39436 1 1602 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1602_756523261.dbf
39437 1 1603 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1603_756523261.dbf
39438 1 1604 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1604_756523261.dbf
39439 1 1605 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1605_756523261.dbf
39440 1 1606 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1606_756523261.dbf
39441 1 1607 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1607_756523261.dbf
39442 1 1608 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1608_756523261.dbf
39443 1 1609 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1609_756523261.dbf
39444 1 1610 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1610_756523261.dbf
39445 1 1611 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1611_756523261.dbf
39446 1 1612 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1612_756523261.dbf
39447 1 1613 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1613_756523261.dbf
39448 1 1614 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1614_756523261.dbf
39449 1 1615 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1615_756523261.dbf
39450 1 1616 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1616_756523261.dbf
39451 1 1617 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1617_756523261.dbf
39452 1 1618 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1618_756523261.dbf
39453 1 1619 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1619_756523261.dbf
39454 1 1620 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1620_756523261.dbf
39455 1 1621 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1621_756523261.dbf
39456 1 1622 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1622_756523261.dbf
39457 1 1623 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1623_756523261.dbf
39458 1 1624 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1624_756523261.dbf
39459 1 1625 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1625_756523261.dbf
39460 1 1626 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1626_756523261.dbf
39461 1 1627 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1627_756523261.dbf
39462 1 1628 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1628_756523261.dbf
39463 1 1629 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1629_756523261.dbf
39464 1 1630 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1630_756523261.dbf
39465 1 1631 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1631_756523261.dbf
39466 1 1632 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1632_756523261.dbf
39467 1 1633 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1633_756523261.dbf
39468 1 1634 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1634_756523261.dbf
39469 1 1635 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1635_756523261.dbf
39470 1 1636 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1636_756523261.dbf
39471 1 1637 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1637_756523261.dbf
39682 1 1638 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1638_756523261.dbf
39689 1 1639 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1639_756523261.dbf
40642 1 1640 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1640_756523261.dbf
40643 1 1641 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1641_756523261.dbf
40644 1 1642 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1642_756523261.dbf
40645 1 1643 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1643_756523261.dbf
40646 1 1644 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1644_756523261.dbf
40647 1 1645 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1645_756523261.dbf
40648 1 1646 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1646_756523261.dbf
41310 1 1647 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1647_756523261.dbf
41317 1 1648 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1648_756523261.dbf
41373 1 1649 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1649_756523261.dbf
41374 1 1650 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1650_756523261.dbf
41375 1 1651 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1651_756523261.dbf
41383 1 1652 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1652_756523261.dbf
*38725 1 56 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf*
*38946 1 57 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_57_757089402.dbf*
*39000 1 58 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_58_757089402.dbf*
*39022 1 59 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_59_757089402.dbf*
*39243 1 60 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_60_757089402.dbf*
*39297 1 61 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_61_757089402.dbf*
*39703 1 62 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_62_757089402.dbf*
*39704 1 63 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_63_757089402.dbf*
*39705 1 64 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_64_757089402.dbf*
*39933 1 65 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_65_757089402.dbf*
*39991 1 66 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_66_757089402.dbf*
*40023 1 67 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_67_757089402.dbf*
*40024 1 68 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_68_757089402.dbf*
*40025 1 69 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_69_757089402.dbf*
*40254 1 70 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_70_757089402.dbf*
*40308 1 71 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_71_757089402.dbf*
*40345 1 72 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_72_757089402.dbf*
*40570 1 73 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_73_757089402.dbf*
*41329 1 74 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_74_757089402.dbf*
I dont know from where recovery catalog is getting the information in bold.
I have crosschecked and deleted archives and resynced the catalog several times. Immediatly after doing that the backup works fine, but the other day its the same thing all over again.
Can some one tell me from where the catalog is getting this wrong infomation about archivelogs???
By the way here is some more info about my target Database:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oradb2/Archive/HCSPRD91
Oldest online log sequence 1651
Next log sequence to archive 1653
Current log sequence 1653
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=/oradb2/Archive/HCSPR
D91
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
NAME TYPE VALUE
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
NAME TYPE VALUE
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch
Regards .....Do you have any other DBs with the same DBID as the one you are backing up? Are they connect to the same RMAN catalog?
Iordan Iotzov
http://iiotzov.wordpress.com/ -
How to install the Recovery Catalog
Hi:
How to install the recovery catalog? I used the following commands from the menu and it didn't work:
connect rman/rman
@?/rdbms/admin/catrman
There is no catrman.sql exists.
Thank you very much.If you are using Oracle8i, make sure your compatibility is set to at least 8.1.0 and you are connected to the catalog database. Then type create catalog; at the RMAN command line.
Maybe you are looking for
-
Upgraded to Mavericks. Now External HDD Enclosure Won't Mount. Is there a fix?
Upgraded to Mavericks. Now I can't get my external HDD enclosure to mount. A little about this enclosure, as it's not the usual settup . I have four 3TB HDDs in a RAID5 settup. The most unique part is that they are formatted as a Windows NT Files
-
Cannot boot up, shut down after 5% progress bar
Newbie to Mac OS - recently ported over from Windows since July '12, when I gotten Mac Mini. Shut down Mini as usual before I went to bed one fine night. Strangely, I noticed the power light is still on the next morning. Turn on monitor and saw a str
-
Digital AV adapter not working with my iphone 4 having IOS 5.0.1
I recently purchased a digital AV adaptor and tried to connect it with my HDMI TV. But it says that this accessory is not compatible with iphone. If its not gonna work why are they selling this adaptor? I tried using another hdmi cable but it didnt w
-
Hi developers, in my WDJ, I am calling a webservice which, executed from wsnavigator, returns this time value: 1970-01-01T08:30:47.000Z On WDJ table I get: 10.30 both with direct binding and computed field such as: DateFormat df = DateFormat.getTimeI
-
Calling Procedures form Report 6i
I would highly appreciate it if I can get advise on how to call procedures from report 6i. My procedure requires two input parameters and returns about six columns in all. The problem I have is in trying to figure out how to display the values return