Remarkably Large Trace Files Were Generated
(Doc ID 1148343.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
You can see the error
- when an internal ORA-8103 is triggered when "Event 10736 level 4" is set as per Bug 8825048
- when dumping an old archive log
may show these errors as well
ORA-308: cannot open archived log
ORA-27037: unable to obtain file status
The database will produce very large trace files that could fill up the disk until the database crashes.
In the trace file you can find something like:
kcbzib: dump suspect buffer
buffer tsn: 5 rdba: 0x1106fba3 (68/457635)
scn: 0x0004.7e8aa271 seq: 0x01 flg: 0x04 tail: 0xa2710601
frmt: 0x02 chkval: 0x4f84 type: 0x06=trans data
Hex dump of block: st=0, typ_found=1
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