Oracle ASM recovery

An Oracle ASM disk group that will not mount should be preserved before FORCE mount, drop or rebalance changes its metadata.

ASM distributes database extents and mirrors across disks according to the disk group's redundancy. Missing paths, stale headers, failed disks or incomplete discovery can make a group dismount even when many extents remain readable.

Understand the symptom

ASM recovery depends on disk identities, allocation units, metadata directories and redundancy state.

WHY

What is happening

The same symptom can come from a missing storage path, changed discovery string, cloned LUN, header damage or failures beyond tolerated redundancy. Recovery maps disk numbers, failgroup membership, incarnation, voting and mirror placement before deciding whether a protected mount or virtual reconstruction is viable.

What you may see

Symptoms that change the recovery path.

01

ORA-15032 or ORA-15040

The disk group is incomplete or cannot satisfy mount requirements.

02

Disks show FORMER or UNKNOWN

Headers or discovery no longer match the expected membership.

03

Only some nodes see the group

Multipath, permissions, discovery or cluster storage presentation differs.

04

Mount FORCE is requested

ASM believes one or more disks are unavailable but may still have sufficient mirrored extents.

Protect the source

Actions that can make the situation worse.

01

FORCE mount can accept missing members

That may be appropriate only when redundancy and failure scope are understood.

02

Rebalance changes surviving metadata

Dropping or replacing disks relocates extents and can overwrite evidence.

03

Header repair on the wrong LUN is destructive

Clones and reused device paths can look similar while holding different incarnations.

Do this now

Safe steps before evaluation.

01

Freeze ASM changes

Stop rebalance, disk drop, header clearing and repeated mount attempts.

02

Map every device

Record OS paths, WWIDs, sizes, ASM disk names, failgroups, discovery strings and node visibility.

03

Preserve all members

Image or snapshot every present, missing-returned and recently replaced LUN before repair.

04

Collect database context

Keep alert logs, ASM metadata, control files, redo, RMAN catalog and recovery priorities.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Membership reconstruction

NEPFOSYS maps ASM headers, disk numbers, failgroups, allocation units and missing paths.

02

Redundancy analysis

Extent mirrors and failure combinations are evaluated on protected device copies.

03

Database extraction and validation

ASM files are reconstructed or restored and priority databases are validated separately.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Is MOUNT FORCE always unsafe?

It is an administrative option for defined failure states, but using it before preserving disks and confirming redundancy can commit an uncertain configuration.

Can an ASM disk group be recovered without every disk?

Possibly when redundancy and surviving mirror extents cover the missing members. Feasibility depends on the exact disk group layout and failures.

Should I repair ASM headers manually?

Not on original devices. Header changes can assign the wrong identity or destroy the membership evidence needed for reconstruction.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case