Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Administration (MOSC)

All redo members corrupted.

Dec 7, 2017 12:47PM edited Dec 11, 2017 7:44AM in Database Administration (MOSC) 3 commentsAnswered

Hello experts.

Environment.

MAIN SITE.

AIX 7.2

RDBMS 11.2.0.4

GI 11.2.0.4

RAC DB 2 node

3 x Storwize V7000 Gen2. ASM mirroring. Diskgroups:

+CRS high redundancy across 3 Storwize

+FRA normal redundancy across 2 Storwize

+DATA normal redundancy across 2 Storwize

STANDBY SITE (DG enabled).

AIX 7.2

RDBMS 11.2.0.4

GI 11.2.0.4

RAC DB 2 node

1 separate Storwize V7000 Gen2. Diskgroups:

CRS external redundancy

FRA external redundancy

DATA external redundancy

Symptoms.

The day before yesterday I received a message on first node:

ORA-00353: log corruption near block 471293 change 9354941709304 time 12/05/2017 22:29:09

ORA-00312: online log 23 thread 1: '+FRA/iabs/onlinelog/group_23.258.940717365'

ORA-00312: online log 23 thread 1: '+DATA/iabs/onlinelog/group_23.267.940717363'

No hardware errors detected on storages and servers.

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month