-
URGENT - RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file XXX/XXX/syste
Any suggestions?
OS - Solaris
DB - 10G
Last edited by dba_dada; 06-22-2006 at 01:05 PM.
-
My Rman Backup problem...
ORA-19566: exceeded limit of 0 corrupt blocks for file /XXX/XXX/system01.dbf
Need your help.
-
you have corrupt blocks in your system tablespace. YOu probably want to get that sorted
-
Since you don't have the MAXCORRUPT parameter set, you may want to run a BACKUP...VALIDATE and then review V$DATABASE_BLOCK_CORRUPTION for entries.
These links may help:
Detecting Physical Block Corruption With RMAN BACKUP... VALIDATE
Handling Corrupt Datafile Blocks in RMAN Backup: MAXCORRUPT
Performing Block Media Recovery with RMAN
-
Any example would be very helpful..please
-
an example of what? you need to work out what the exact problem is. Have you raised a TAR with oracle?
-
Yes..TAR is open on that.
I was looking for the exact syntax for SET MAXCORRUPT.
set maxcorrupt for datafile 1 to .....
-
Originally Posted by dba_dada
set maxcorrupt for datafile 1 to .....
That's the correct syntax and you just specify a value where you have '...'
You can also choose to do the following:
RMAN> BACKUP VALIDATE DATAFILE 1;
This will check that one file. You could also check all the files and archivelog files with:
RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL;
After the validate has finished, query V$DATABASE_BLOCK_CORRUPTION for records.
However, as davey pointed out, this is your system tablespace's datafile, a TAR would be the best way to go.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|