Gargantuan trace file

[Thargy]

Hi,

I am running several 9i2 databases, which occasionally produce internal errors, which appear in the alert log. The alert log says to look in certain trace files, for further details.

These trace files do indeed contain error information, but they are sometimes huge (in excess of 50 gigabytes).

Is there any setting, similar to 'max_dump_file_size', which a can alter to stop these files wiping out all the free space on the server's hard disk?

Regards

Tharg

Grinding away at things Oracular

 

[Scunningham99]

hi

why not set the the parameter you mentioned to a particular size ie 1024M

see link:-

http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1109.htm#REFRN10103

hth


Sy UK

 

[Turkbear]

Hi,
And, not to be a smarta__, but why not eliminate the errors?
That much trace file usage seems to indicate serious problems..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[Thargy]

Turkbear,

I agree wholeheartedly. Unfortunately we are not patched to the latest version, so support won't touch us. Rest assured that otherwise, right now, there would be an open priority 2 TAR on metalink.

I'm a lone Oracle DBA, so I have to fire fight a lot, instead of doing strategic updates and security patching etc.

Not a nice position to be in.

Regards

Tharg.

Grinding away at things Oracular