My Oracle Support Banner

ERROR: Paging ASM Fault Extent Map Failed (Doc ID 2114347.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Suddenly experienced a transitory ASM error which caused a job to fail.

In the database alert log, you will see errors related to the following:

Thu Feb 11 04:54:56 2016
Thread 1 advanced to log sequence 10172 (LGWR switch)
 Current log# 4 seq# 10172 mem# 0: +REDO/<DB name>/onlinelog/group_4.264.887449583
Thu Feb 11 04:55:05 2016
ERROR: paging ASM fault extent map failed gn=1 fn=1048 extent=1726              >>>>>>>>>>> ERROR: paging ASM fault extent map failed
ERROR: paging ASM fault extent map failed gn=1 fn=996 extent=470
ERROR: paging ASM fault extent map failed gn=1 fn=998 extent=578
ERROR: paging ASM fault extent map failed gn=1 fn=1004 extent=590
ERROR: paging ASM fault extent map failed gn=1 fn=1005 extent=562
ERROR: paging ASM fault extent map failed gn=1 fn=1008 extent=522
ERROR: paging ASM fault extent map failed gn=1 fn=1012 extent=706
ERROR: paging ASM fault extent map failed gn=1 fn=1014 extent=670
ERROR: paging ASM fault extent map failed gn=1 fn=1017 extent=706
ERROR: paging ASM fault extent map failed gn=1 fn=1020 extent=562
ERROR: paging ASM fault extent map failed gn=1 fn=1030 extent=542
ERROR: paging ASM fault extent map failed gn=1 fn=1035 extent=750
ERROR: paging ASM fault extent map failed gn=1 fn=1038 extent=546
ERROR: paging ASM fault extent map failed gn=1 fn=1039 extent=426
ERROR: paging ASM fault extent map failed gn=1 fn=1048 extent=858
Thu Feb 11 04:55:16 2016
Archived Log entry 10175 added for thread 1 sequence 10171 ID 0x541c688 dest 1:
Thu Feb 11 04:58:18 2016
ERROR: paging ASM fault extent map failed gn=1 fn=894 extent=8446
Thu Feb 11 05:23:01 2016
Thread 1 cannot allocate new log, sequence 10173
Private strand flush not complete
 Current log# 4 seq# 10172 mem# 0: +REDO/<DB name>/onlinelog/group_4.264.887449583

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.