What Tanel wrote works.
Sadly, of 63 enhancement requests voted into the first Oracle VLDB list circa
1992, one of the highest ranking losers was to automatically grandfather all
trace files down one directory into a date named subdirectory dYYYYMMDD (the
leading d being optional on OSes that support all numeric “folder” or directory
names.
The number of problems by simply down foldering all old files cannot be counted.
IF memory serves, Tanel once described a problem rooted in a huge number of
files in a directory as the most complex to debug he’d ever seen (as of that
time).
You CAN do this yourself for files that are not open on most operating systems
(that alternate not quite solution being one of the reasons that nice bit of
transparent automation didn’t make the cut.)
SIGH. The worst one we failed to reach consensus on was creating a varchar type
that recorded the difference between NULL and the empty string. That still
blows chunks to this day and my comment at dinner at Kincaid’s to Bob Miner
that changing all our code would be a lot of work was the thing I’ve said in my
entire life that I would most like to not have said. Since we’d already
laboriously handled the mistake that Oracle considered empty strings to mean
NULL in all our code, I couldn’t justify the effort to my employer at the time.
oops. Sorry.
mwf
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Tanel Poder
Sent: Monday, February 25, 2019 1:37 PM
To: dougk5@xxxxxxx
Cc: oracle-l-freelist
Subject: Re: Managing large ASM trace files
Hi Doug,
At OS level, you can truncate the file using:
echo > filename.trc
or just
filename.trc
