Home » RDBMS Server » Backup & Recovery » ORA-00368,00353,00312. (Win2K3, 10.2.0.1)
ORA-00368,00353,00312. [message #379593] Wed, 07 January 2009 04:03 Go to next message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Hello,

Here's an usual behvior that my database presented to me yesterday at startup:

C:\Documents and Settings\Administrateur>sqlplus /nolog

SQL*Plus: Release 10.2.0.1.0 - Production on Mar. Janv. 6 18:47:40 2009

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

SQL> conn / as sysdba
ConnectÚ Ó une instance inactive.
SQL> startup
Instance ORACLE lancÚe.

Total System Global Area  167772160 bytes
Fixed Size                  1247900 bytes
Variable Size              75498852 bytes
Database Buffers           88080384 bytes
Redo Buffers                2945024 bytes
Base de donnÚes montÚe.
ORA-00368: erreur de total de contr¶le dans le bloc du journal redo
ORA-00353: journal endommagÚ prÞs du bloc 56436, modification 34359662,
horodatage 01/06/2009 06:28:29
ORA-00312: journal en ligne 1 thread 1 :
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\META4\TEST\REDO01.LOG'


SQL>


Can anyone please help me fix that?

I went through some solutions over the net such as setting an undocumented parameter -allow_resetlogs_corruption=true or performing an incomplete recovery or a recovery until a SCN, but I would rather check with you guys what can be the best set actions in such case.

This is a database in which I perform tests before going to prod. It runs in ARCHIVELOG mode but I have never taken a backup of it. I hope my case isn't hopeless.

Thanks in advance.
Re: ORA-00368,00353,00312. [message #379596 is a reply to message #379593] Wed, 07 January 2009 04:30 Go to previous messageGo to next message
Michel Cadot
Messages: 64151
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Stop the instance
Copy the other member of the same group into this file
Start the instance

Regards
Michel

[Updated on: Wed, 07 January 2009 04:31]

Report message to a moderator

Re: ORA-00368,00353,00312. [message #379670 is a reply to message #379596] Wed, 07 January 2009 09:58 Go to previous messageGo to next message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Can't do that Michel, because each of my log group has only 1 member Embarassed . I haven't added other members to those group, neither did I create other groups. Sad
Re: ORA-00368,00353,00312. [message #379672 is a reply to message #379670] Wed, 07 January 2009 10:04 Go to previous messageGo to next message
Frank Naude
Messages: 4502
Registered: April 1998
Senior Member
00368, 00000, "checksum error in redo log block"
// *Cause:  The redo block indicated by the accompanying error, is not
//          vaild. It has a checksum that does not match the block contents.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.
// *Action: Restore correct file or reset logs.


00353, 00000, "log corruption near block %s change %s time %s"
// *Cause:  Some type of redo log corruption has been discovered. This error
//          describes the location of the corruption. Accompanying errors
//          describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
//          recovery up to the indicated change or time.


Next steps:

1. As the OS guys to check the system's disks for problems that can cause file corruption.

2. Perform incomplete recovery on the DB.

Re: ORA-00368,00353,00312. [message #379692 is a reply to message #379672] Wed, 07 January 2009 12:23 Go to previous messageGo to next message
Michel Cadot
Messages: 64151
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
And 3. Add a member to each log group to prevent from losing data in this way next time.

Regards
Michel
Re: ORA-00368,00353,00312. [message #379843 is a reply to message #379692] Thu, 08 January 2009 02:14 Go to previous message
abdulaziz
Messages: 102
Registered: May 2008
Location: Douala
Senior Member
Uhmm...Thanks Frank for the tips. I performed a changed-based recovery using the SCN as follows:
recover database until change 34359662
the result I had was the following:
ORA-01547: attention : opÚration RECOVER rÚussie, mais OPEN RESETLOGS gÚnÚrera
l'erreur ci-dessous
ORA-01194: le fichier 1 nÚcessite plus de rÚcupÚration pour Ûtre cohÚrent
ORA-01110: fichier de donnÚes 1 :
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\META4\TEST\SYSTEM01.DBF'


When I questionned the v$log about the status of my logs through the following:
select group#,status,members,archived from v$log;
I got:
  
  GROUP# STATUS              MEMBERS ARC
---------- ---------------- ---------- ---
         1 CURRENT                   1 NO
         3 INACTIVE                  1 YES
         2 INACTIVE                  1 YES


What do you suggest I should do next? I am tempted to clear unarchived logfile of group 1... Confused

I neglected taking a backup of that database...darn it!. (Ne jamais remettre à demain ce qu'on peut faire le jour même)

I am definitely going to add members to each group after that Michel. Smile
Previous Topic: How to restore backup from a patricular set directly from TAPE using RMAN
Next Topic: Recovery RMAN
Goto Forum:
  


Current Time: Fri Dec 09 23:33:13 CST 2016

Total time taken to generate the page: 0.06979 seconds