e files (excluding the alert file). Change this limit if you are concerned that trace files may use too much space.
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.
odm fund：
ORA-600 [kole_t2u], [34] - description, bugs, and reasons (文档 ID 734474.1)
ORA-600 [kole_t2u] With Multibyte Character Sets While Appending To LOB In a Loop (文档 ID 739282.1)
Character set conversion when using UTL_FILE (文档 ID 227531.1)?
Getting ORA-7445 [_memmove()+64] and Instance Crashed (文档 ID 1294148.1) 转到底部转到底部
In this Document Symptoms Cause Solution This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.2 [Release 10.2 to 11.2] Information in this document applies to any platform. SYMPTOMS
In the alert log file there are reported errors like:
The trace files generated by these errors are truncated (not relevant) or have no information (0 bytes).
CAUSE
In this case the issue is caused by a resource problem outside Oracle. By checking the OS system log, you can see that the Oracle mount point has ran out of space just before the errors and until the instance crash.
For example in an HP-UX system, the messages can be as the following:
vmunix: vxfs: NOTICE: msgcnt 1 mesg 001: V-2-1: vx_nospace - /dev/vg01/lvora file system full (1 block extent)
SOLUTION
Monitor your system in order to avoid running out of space in Oracle mount points.