My Oracle Support Banner

MAX_DUMP_FILE_SIZE='UNLIMITED' Reverting After Restart (Doc ID 2136465.1)

Last updated on AUGUST 28, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 and later
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

Non critical error ORA-48913 caught while writing to trace file "<$ORACLE_BASE>/diag/rdbms/<sid>/<DBNAME>/trace/<DBNAME>_ora_22721.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached
Writing to the above trace file is disabled for now on...

Changes

Even after changing the value for MAX_DUMP_FILE_SIZE to UNLIMITED, it is reverting to its previous value after a database restart.

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.