My Oracle Support Banner

ORA-4031 Hit In Large Pool during RMAN backup (Doc ID 1286414.1)

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.

Symptoms

ORA-4031 when trying to allocate 4202584 bytes in Large Pool during RMAN backup.

Changes

Problem is hit under the following circumstances:

Large Pool is set to 200 Mb.

Free memory in Large Pool

Below query confirms there is a lot of free space within the Large Pool:

SQL>select * from v$sgastat where pool='large pool';

Granule size

From the ORA-4031 tracefile we can see GRANULE SIZE is 4194304 bytes:

GRANULE SIZE is 4194304

RMAN parameter BLKSIZE is set to 4194304 bytes:

ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' maxpiecesize 70G parms='BLKSIZE=4194304';

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
 Problem is hit under the following circumstances:
 Free memory in Large Pool
 Granule size
 RMAN parameter BLKSIZE is set to 4194304 bytes:
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.