Home » RDBMS Server » Backup & Recovery » Setting MAXCORRUPT Parameter. (10gR2,Win2k3)
Setting MAXCORRUPT Parameter. [message #430192] Mon, 09 November 2009 07:06 Go to next message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Hello,

I faced a new situation today whose solution was to set the MAXCORRUPT parameter in my RMAN backup script and there are few things I would like you experts to shed your lights on.
Well, the database concerned with the issue runs on NOARCHIVELOG mode and the backup script I wrote againts it executes every Sunday at 23:00. The instructions in the script are as follow:

run
{
shutdown immediate;
startup nomount;
alter database mount;
backup database format 'D:\oracle\cold_rman_bkp_tmsbd\full_bkp_hebdo_tmsbd_%s';
alter database open;
}

Last yesterday it didn't execute totally and the the database could not open. When I looked into the problem, I realized there were a set of errors to fix but the new one for me was the one RMAN threw :

ORA-19566: la limite de 0 blocs altÚrÚs pour le fichier D:\ORACLE\ORADATA\TMSBD\EXAMPLE01.DBF est dÚpassÚe


I made a search over the net and I found the solution through the MAXCORRUPT parameter. But as the database is to run in NOARCHIVELOG mode, I couldn't run the BACKUP ...VALIDATE command against all the dafiles that had corrupted blocks. As a result, the v$DATABASE_BLOCK_CORRUPTION view couldn't help me (RMAN threw an error with an emphasis on the archiving mode)

Finaly, I added the following line in my RMAN backup script:
set maxcorrupt for datafile 1,4,17 to 10;
and it worked.

My questions are:
1- Is there a way to fix the blocks affected in those datafiles? If yes, how to do that?
2- Is the limit I set (10) too high?
3- How to prevent it from happening again?

Thanks in advance.
Re: Setting MAXCORRUPT Parameter. [message #432407 is a reply to message #430192] Mon, 23 November 2009 23:52 Go to previous messageGo to next message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
Forms is wrong forum for this question. I will move it.

David
Re: Setting MAXCORRUPT Parameter. [message #432410 is a reply to message #430192] Tue, 24 November 2009 00:34 Go to previous messageGo to next message
Michel Cadot
Messages: 64153
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Run dbverify (dbv) to know the blocks that are corrupteed, then depending if the blocks are free or not, and which objects own these objects you can fix them.

Regards
Michel
Re: Setting MAXCORRUPT Parameter. [message #432509 is a reply to message #430192] Tue, 24 November 2009 10:38 Go to previous messageGo to next message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Thanks David for moving the post to the right section. I didn't pay enough attention when I was posting. Sorry for the inconvenience.

Thanks Michel for the tip. As one of the HDD was showing signs of failure, we decided to move it to another machine. (We actually made an export of the schema holding the application's data, and imported it to the new database). Is it still necessary to run the dbverify?

Thanks in advance.
Re: Setting MAXCORRUPT Parameter. [message #432513 is a reply to message #432509] Tue, 24 November 2009 10:44 Go to previous messageGo to next message
Michel Cadot
Messages: 64153
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
It is wiser.
It does not hurt and may allow to anticipate problems.

Regards
Micehel
Re: Setting MAXCORRUPT Parameter. [message #432629 is a reply to message #432513] Wed, 25 November 2009 05:33 Go to previous messageGo to next message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
I followed your advice Michel and I ran dbv against the 3 datafiles that caused problems before. At first sight, the result shows there are no errors on the latters (nombre de pages marquées alterées = 0), unless that message is misleading...

Here are the output:
BVERIFY: Release 9.2.0.1.0 - Production on Me Nov 25 12:05:10 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.


DBVERIFY - Début de vérification : FILE = D:\oracle\oradata\TMSBD\system01.dbf

DBVERIFY - Vérification terminée

Nbre de pages examinées           : 52480
Nbre de pages traitées (Données)  : 36491
Nbre de pages en échec (Données)  : 0
Nbre de pages traitées (Index)    : 4465
Nbre de pages en échec (Index)    : 0
Nbre de pages traitées (Autre)    : 1631
Nbre de pages traitées (Seg)  : 0
Nbre de pages en échec (Seg)  : 0
Nbre de pages vides               : 9893
Nbre de pages marquées altérées   : 0
Nbre de pages Influx              : 0


DBVERIFY: Release 9.2.0.1.0 - Production on Me Nov 25 12:13:42 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.


DBVERIFY - Début de vérification : FILE = D:\oracle\oradata\TMSBD\drsys01.dbf

DBVERIFY - Vérification terminée

Nbre de pages examinées           : 2560
Nbre de pages traitées (Données)  : 90
Nbre de pages en échec (Données)  : 0
Nbre de pages traitées (Index)    : 99
Nbre de pages en échec (Index)    : 0
Nbre de pages traitées (Autre)    : 470
Nbre de pages traitées (Seg)  : 0
Nbre de pages en échec (Seg)  : 0
Nbre de pages vides               : 1901
Nbre de pages marquées altérées   : 0
Nbre de pages Influx              : 0


DBVERIFY: Release 9.2.0.1.0 - Production on Me Nov 25 12:14:44 2009

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.


DBVERIFY - Début de vérification : FILE = D:\oracle\oradata\TMSBD\tms_tbs_stock_tb.dbf


DBVERIFY - Vérification terminée

Nbre de pages examinées           : 12800
Nbre de pages traitées (Données)  : 1695
Nbre de pages en échec (Données)  : 0
Nbre de pages traitées (Index)    : 0
Nbre de pages en échec (Index)    : 0
Nbre de pages traitées (Autre)    : 168
Nbre de pages traitées (Seg)  : 0
Nbre de pages en échec (Seg)  : 0
Nbre de pages vides               : 10937
Nbre de pages marquées altérées   : 0
Nbre de pages Influx              : 0


I ran it also against the remaining datafiles and the result was also the same. However, I had to run it directly on the server. Is it possible to run that utility remotely? If yes, how.

Thanks in advance.
Re: Setting MAXCORRUPT Parameter. [message #432634 is a reply to message #432629] Wed, 25 November 2009 06:30 Go to previous messageGo to next message
Michel Cadot
Messages: 64153
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
It is OK.
No, you can't execute it remotely (there is no connection) but you can copy the file on a remote destination and then execute dbv there.

Regards
Michel

Re: Setting MAXCORRUPT Parameter. [message #432643 is a reply to message #432634] Wed, 25 November 2009 07:28 Go to previous message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Ok, I got it. That's what I finaly did. Thank you Michel for your assistance.

Regards.
Previous Topic: RMAN not deleting all archived logs
Next Topic: 8i "until change is before resetlogs" error
Goto Forum:
  


Current Time: Sun Dec 11 04:14:04 CST 2016

Total time taken to generate the page: 0.08843 seconds