Rac _ production database log group corruption handling, rac logs

Rac _ production database log group corruption handling, rac logs

Original Works are from the "Deep Blue blog" blog. Be sure to indicate the source when reprinting. Otherwise, you have the right to pursue legal liability for copyright.

Deep Blue blog: http://blog.csdn.net/huangyanlong/article/details/46863813

 

Environment:

Operating System: CentOS 6.4 64bit

Middleware: WAS 7

Database: Oracle 11g rac 11.2.0.3

Problem:

The generated database was cannot connect to the database, and an archive error is reported.

Solution:

Oracle cannot be archived.

Operation records:

SQL> select instance_name from v $ instance;

INSTANCE_NAME

----------------

Hyl1

SQL> select * from v $ log;

SQL> alter system switch logfile;

-- Manually switch the log group, hold it for a long time, and stop it manually

^ Calter system switch logfile

*

ERROR at line 1:

ORA-01013: user requested cancel of current operation

 

-- View alarm logs, archiving failure errors found, pointing to ora-00333 errors, possible log group corruption

Incomplete read from log member '+ DATA/hyl/redo01.log'. Trying next member.

ARC0: All Archive destinations made inactive due to error 333

ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1: '+ ARCH/hyl/archivelog/2015_07_06/thread_eclipseq_3935.542.884340013' (error 333) (hyl1)

ARCH: Archival stopped, error occurred. Will continue retrying

ORACLE Instance hyl1-Archival Error

ORA-16038: log 1 sequence #3935 cannot be archived

ORA-00333: redo log read error block count

ORA-00312: online log 1 thread 1: '+ DATA/hyl/redo01.log'

Mon Jul 06 10:00:18 2015

ARCH: Archival stopped, error occurred. Will continue retrying

ORACLE Instance hyl1-Archival Error

ORA-16014: log 1 sequence #3935 not archived, no available destinations

ORA-00312: online log 1 thread 1: '+ DATA/hyl/redo01.log'

 

-- Verify the archive log directory space and eliminate the problem caused by insufficient space

SQL> select group_number, name, total_mb, free_mb from v $ asm_diskgroup;

GROUP_NUMBER NAME TOTAL_MB FREE_MB

--------------------------------------------------------------

1 CRS 449952 449023

2 DATA 14500000 13677212

3 ARCH 1000000 999167

4 FLASH 1000000 999895

 

SQL> select * from v $ log;

-- Check the archiving status. The log group 1 (non-current log group) is not archived.

SQL> col MEMBER for a50

SQL> select * from v $ logfile order by group #;

GROUP # status type member is _

-----------------------------------------------------------------------------

1 ONLINE + DATA/xzxt/redo01.log NO

2 ONLINE + DATA/xzxt/redo02.log NO

3 ONLINE + DATA/xzxt/redo03.log NO

4 ONLINE + DATA/xzxt/redo04.log NO

Logs are not diversified.

 

SQL> alter database clear unarchived logfile group 1;

-- If log group 1 is not the current log group, try to clear it

SQL> select * from v $ log;

-- Restore the archive to normal

SQL> alter system switch logfile;

 

Summary:

This fault is caused by damage to the log group. When the current log group is full and you need to archive it, an error occurs. Because the damaged log group is not the current log group, the processing is relatively simple. However, if the current log group is damaged due to power failure or hardware failure, the database may not be completely restored due to backup, resulting in data loss. We recommend that you set up multiple log groups.

 

After the fault, a brief summary of the subsequent maintenance suggestions was provided to the resident engineers.

Suggestion:

1. Check for recent power outages and determine the cause of log group damage;

2. confirm that the hardware device has no warning and whether it is a hardware fault;

3. If factors such as power failure and hardware failure are excluded, they may be caused by oracle logic errors and need to be tracked;

4. We recommend that you perform full backup as soon as possible after this fault;

5. We recommend that you diversify the log groups;

6. In terms of performance, we recommend that you add a single-node log group from two groups to three or more groups later;

 

**************************************** * ** Blue growth series ********************************* *******************

Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).

Blue growth note-chasing DBA (1): traveling on the road to Shandong

Blue growth notes-Chase DBA (2): Install! Install! Long-lost memories have aroused my new awareness of DBAs.

Blue growth note-chasing DBA (3): importing and exporting data on antiques becomes a problem

Blue growth note-chasing DBA (4): recalling the sorrow of teenagers, and exploring oracle Installation (10g and 11g in Linux)

Blue growth note-chasing DBA (5): Not talking about technology or business, annoying Application Systems

Blue growth note-chasing DBA (6): doing things and being human: Small technology, great human

Blue growth note-Chase DBA (7): Basic commands, foundation stone

Blue growth notes-chasing DBA (8): repicking SP reports and recalling oracle's STATSPACK Experiment

Blue growth note-chasing DBA (9): Chasing DBA, new planning, new departure

Blue growth note-chasing DBA (10): Flying knife defense, familiarity rather than expertise: Playing with middleware Websphere

Blue growth note-chasing DBA (11): It's easy to go home and wake up.

Blue growth notes-Chase DBA (12): seven days and seven gains of SQL

Blue growth note-chasing DBA (13): Coordinating hardware manufacturers, six stories: what you see as "servers, storage, switches ......"

Blue growth note-chasing DBA (14): An unforgettable "Cloud" end, started hadoop deployment

Blue growth note-chasing DBA (15): Who thinks FTP is "simple" and thinks it is a trigger

Blue growth note-chasing DBA (16): DBA also drank alcohol and was rejected

Blue growth note-Chase DBA (17): whether to share or consume, learn to grow in the Post-IOE Era

**************************************** **************************************** **********************************

 

**************************************** ******************************** *****************

Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).

Football and oracle series (1): 32-way zhoudianbing, overall view of group A Brazil smon process of oracle32 process Alliance

Football and oracle series (2)

Football and oracle series (3): oracle process rankings, the World Cup round is about to fight!

Football and oracle series (4): from Brazil to Germany, think of the different RAC topology comparison! 

Football and oracle series (5): The directX library missing in the voda14 game is similar to the oracle rpm package!

Football and oracle series (6): Asian Cup with database creation-come on, Chinese Team

**************************************** **************************************** **********************************

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.