Tag: rman error

RMAN-20001: target database not found in recovery catalog

Posted on by Osama Mustafa in Database
===================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ===================================================
RMAN-03002: failure of list command at 11/13/2011 03:26:18

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog

  1. Connect to RMAN Catalog
$ rman catalog rman/rman@rmancat target rmanbkup/rmanbkup@orcl
Recovery Manager: Release 11.2.0.2.0 – Production on Sun Nov 13 03:25:49 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
connected to target database: orcl (DBID=5858479612)
connected to recovery catalog database
  1. Unregister the database
RMAN>unregister database noprompt;
  1. Register Database to RMAN catalog
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog

full resync complete

ORA-19566: exceeded limit of 0 corrupt blocks for file

Posted on by Osama Mustafa in Database
I already Talk about this Error but this Topics Share Another Solution For it :

RMAN> backup database;
 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/22/2011 11:45:40
ORA-19566: exceeded limit of 0 corrupt blocks for file /oracle/oradata/orcl/system01.dbf

 

SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
 
     FILE#     BLOCK#   BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
  5  2684        1    0 CHECKSUM

RMAN> blockrecover datafile 5 block 2684;

Thank you
Osama mustafa

ORA-19566 exceeded limit of %s corrupt blocks for file %s

Posted on by Osama Mustafa in Database 
Cause: The user specified limit of allowable corrupt blocks was exceeded 
 while reading the specified datafile for a datafile copy or backup. 
Action: None. The copy or backup operation fails. The session trace file 
 contains detailed information about which blocks were corrupt.
 
 
But The Below is Work around : 
 
  
 1)Run DBVerify utility. Have a look at Verify Physical Data Structure



For example,
 
 
 $ dbv file=/oradata2/data1/dbase1/system01.dbf 
 
 Also run this operation for against the all datafiles you suspect which has corrupt block.



2)While taking backup within RUN block specify SET MAXCORRUPT in order 
to say how many corruption it can handle. I ran dbverify utility and I 
saw 1 block corrupt each in SYSTEM(1) and SYSAUX(3) datafile.



3)Now backup database with SET MAXCORRUPT option.


 


Syntax : 

 


SET MAXCORRUPT FOR DATAFILE File_id For DatabaseFiles to ;
 

SET MAXCORRUPT FOR DATAFILE  to ;
 

RMAN> RUN{

2> SET MAXCORRUPT FOR DATAFILE 1,3 to 1;

3> BACKUP DATABASE;

4> }



For datafile 1 and 3 maximum 1 block corruption can be tolerated.


 





 


Thank you 


Osama Mustafa 


  

	

	

	




	
	

		
Working with RMAN Stored Scripts
				

					Posted on  by Osama Mustafa in Scripts				


				

	

		


Creating Stored Scripts: CREATE SCRIPT


 


Make sure RMAN is connected to the right target database and the recovery catalog. Then run the CREATE SCRIPT command, as shown in this example: 


 




 


CREATE SCRIPT full_backup 
{     
  BACKUP DATABASE PLUS ARCHIVELOG;
  DELETE OBSOLETE;
} 


 


 




 you can also provide a COMMENT with descriptive information:




CREATE GLOBAL SCRIPT global_full_backup 
COMMENT 'use only with ARCHIVELOG mode databases'
{     
  BACKUP DATABASE PLUS ARCHIVELOG;
  DELETE OBSOLETE;
}






Running Stored Scripts: EXECUTE SCRIPT


 




RUN { EXECUTE SCRIPT full_backup; }






Displaying a Stored Script: PRINT SCRIPT




PRINT SCRIPT full_backup;


PRINT SCRIPT full_backup TO FILE 'my_backup.txt'; 






Listing Stored Scripts: LIST SCRIPT NAMES




LIST SCRIPT NAMES;








LIST ALL SCRIPT NAMES;






Updating Stored Scripts: REPLACE SCRIPT




REPLACE SCRIPT full_backup 
{
  BACKUP DATABASE PLUS ARCHIVELOG;
}




Deleting Stored Scripts: DELETE SCRIPT


  




DELETE SCRIPT 'full_backup';


DELETE GLOBAL SCRIPT 'global_full_backup'; 




 


 


 


 Thank you 


Osama mustafa


 




 




 



	

	

	




	
	

		
rman-06054 media recovery requesting
				

					Posted on  by Osama Mustafa in Database				


				

	

		


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/13/2011 14:51:58
RMAN-06054: media recovery requesting unknown log: thread 1 seq 2 lowscn 547146


 


 


This Error Happened Sometimes When you try to restore rman backup from Real Application


Cluster To single Node 


 


Solution  





 RMAN > recover database noredo;


 



Thank you


Osama mustafa


 


 


Hope This is useful . 



	

	

	




	
	

		
RMAN-10003 ORA-12154
				

					Posted on  by Osama Mustafa in Database				


				

	

		
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/15/2011 12:54:22
RMAN-12001: could not open channel ORA_DISK_1
RMAN-10008: could not create channel context
RMAN-10003: unable to connect to target database
ORA-12154: TNS:could not resolve the connect identifier specified


Solution :


RMAN> run {
2> allocate channel ch00 type disk;
 3> restore database;
4>}


Thank You 
osama Mustafa