MAX_DUMP_FILE_SIZE

最新推荐文章于 2021-05-11 13:01:40 发布

huangliang0703

最新推荐文章于 2021-05-11 13:01:40 发布

阅读量1.6k

点赞数

CC 4.0 BY-SA版权

分类专栏： 11g新特性文章标签： oracle

本文链接：https://blog.youkuaiyun.com/huangliang0703/article/details/43021511

11g新特性专栏收录该内容

2 篇文章

订阅专栏

本文详细介绍了如何在Oracle数据库环境中修改MAX_DUMP_FILE_SIZE参数以控制trc文件大小，防止使用过多存储空间。通过设置数值、单位（K/M）或特殊值'UNLIMITED'来实现灵活的配置，同时展示了参数调整后的潜在错误提示及其解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the alert file). Change this limit if you are concerned that trace files may use too much space.

MAX_DUMP_FILE_SIZE 指定trc文件的最大值（不包括alert文件）

A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in operating system blocks.
单独一个数值的话指系统块的数目
A number followed by a K or M suffix specifies the file size in kilobytes or megabytes.
The special value string UNLIMITED means that there is no upper limit on trace file size. Thus, dump files can be as large as the operating system permits.

SQL>  alter system set max_dump_file_size= '1k' scope=spfile;

System altered.

SQL> startup force;
ORACLE instance started.

SQL> create table liang(id int);

Table created.

SQL> show parameter max_dump_file_size

NAME                                 TYPE
------------------------------------ ----------------------
VALUE
------------------------------
max_dump_file_size                   string
1K
SQL>

************************************************************************
Thu Jan 22 03:34:15 2015
create table liang(id int)
Thu Jan 22 03:34:52 2015
<span style="color:#ff0000;">Non critical error ORA-48913 caught while writing to trace file "/export/11g/diag/rdbms/orcl1/orcl/trace/orcl_j000_15547.trc"</span>
Error message: ORA-48913: Writing into trace file failed, file size limit [1000] reached
Writing to the above trace file is disabled for now on...
Thu Jan 22 03:39:14 2015
Starting background process SMCO
Thu Jan 22 03:39:14 2015
SMCO started with pid=25, OS id=15654