my OS: OUL5x64
DB: 11.1..7
receive this error in alert.log but tend to not discover which parameter to improve.
Can someone help.

Non critical error ORA-48913 caught while conntacting trace file
Error message: ORA-48913: Writing into trace file unsuccessful, quality limit [10485760] arrived at

ORA-48913: Writing into trace file unsuccessful
*Cause:An effort is made to create right into a trace file that exceeds the trace’s quality limit
*Action:boost the trace’s quality limit.

Thanks ahead of time.

Эти материалы помечены как “окончательные”. Показать Ответов: 10

Hi,
You are able to relabel the present trace file, to ensure that oracle can create new otherwise you can boost the size.
Thanks

1 пользователь считает эту информацию полезной

• Мне нравится Показать отметки Мне нравится () ()
• Действия

Would you which parameter will be able to increase.

1 пользователь считает эту информацию полезной

• Мне нравится Показать отметки Мне нравится () ()
• Действия

max_dump_file_size default is 10240, you already set to 10mb so that you can increase this

if you’re in home windows attempt to relabel the alert file, because its open in notepad, huge files could problem to spread out.

*How you can Enlarge how big Trace Files [ID 197083.1]*

Edited by: CKPT on Jul 16, 2010 7:44 AM

1 пользователь считает эту информацию полезной

• Мне нравится Показать отметки Мне нравится () ()
• Действия

a little confuse here.
got this error in alert.log
Writing into trace file unsuccessful, quality limit [10485760] arrived at and
my
max_dump_file_size string 20480 (20M)

could it be since the os block size=512k
therefore the 20480 becomes 10240

Plus i got exactly the same error. Although I’ve elevated the dimensions for that parameter max_dump_file_size within my init.ora file.

consider my database runs through pfile. i realize this won’t enter into effect until n unless of course i bounce the database.

M i correct on my small understanding ?

I’ve yet another doubt.
everywhere its written to improve the parameter max_dump_file_size in order to relocate the alert log, but so far as i realize ,
is that this just because a trace file using the name XXXX_ora_8218.trc was getting generated having a greater size compared to one defined in max_dump_file_size. Is that this what went down ?

Also. I’m not capable of finding what directory performs this parameter suggests. could it be the trace directory or diag directory ?

i checked select * from v$diag_info ,however i couldn’t find any conclusion.

Most likely. on obtaining the above info. i can decide where you can slowly move the alert.log to produce space.

Thanks and Regards
Kk

always open a brand new thread and publish your question.
should you edit pfile parameter. you ought to have to bounce the database. it’ll reflect in next reboot only.

after restart look into the database.

I’m sorry. I figured this thread was concerning the same error so published it here.

Would you also suggest something for that other comment I’ve put concerning the max_dump_file_size information.