Size of the datapatch related tables are constantly increasing
(Doc ID 2965212.1)
Last updated on FEBRUARY 27, 2025
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Database - Enterprise Edition - Version 19.19.0.0.0 and later
Information in this document applies to any platform.
Symptoms
The size of the patching related tables are constantly increasing and the below 3 LOBSEGMENTS related to patching info are the main consumers :
select a.owner, a.segment_name "ObjectName", b.SEGMENT_TYPE "ObjectType", b.bytes "SizeBytes", a.table_name, a.column_name
from dba_lobs a, dba_segments b
where a.segment_name = b.segment_name
and a.owner = b.owner
and a.owner='SYS'
and a.column_name='PATCH_DIRECTORY'
order by b.bytes desc;
Owner ObjectName ObjectType SizeBytes Table name Column name
-----------------------------------------------------------------------------------------------------------------------------------------
SYS SYS_LOB0001774654C00008$$ LOBSEGMENT 931,135,488 REGISTRY$SQLPATCH_RU_INFO PATCH_DIRECTORY
SYS SYS_LOB0001682334C00008$$ LOBSEGMENT 310,378,496 REG$SP_RU_INF$18$2110061305 PATCH_DIRECTORY
SYS SYS_LOB0001682328C00014$$ LOBSEGMENT 268,435,456 REG$SQLPATCH$181$2110061305 PATCH_DIRECTORY
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 |
| Cause |
| Solution |
| References |