oracle10g create many large dump files

[tareq_2]

hi there
my problem is my database is create many large dump files in the directory cdump
I don't know what the trouble in my database?
thanx

[T G Manikandan]

BDUMP, UDUMP, and CDUMP are directories pointed to by the
BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization
parameters, respectively. Any user trace files are stored in UDUMP. Any
trace files made by background processes are stored in BDUMP. Any core
dump trace files are stored in CDUMP. You need these files to diagnose
problems with your database

It depends for how many days you need these files to be maintained for. I would delete files older than 30 days by having a cron job like :

find - mtime +30 -exec -name 'core*' -exec rm -fr {} \+

[Hein van den Heuvel]

>> I don't know what the trouble in my database?

Look at the time of the dump files.
Now open up (read) the Alert.log file in /bdump.

Try reading the dump and/or .TRC file (/udump)

You'll probably find a corresponding entry with an indication of the problem. POssibly aome mumbo-jumbo about memory or communications, but perhaps it triggers a correction or workaround thought.
Perhaps there is an 'ORA-600' indication ("something went badly wrong" :-).

Search METALINK for matches on errors number/text + platform.

Make sure you are up-to-date.

Don't spend too much time on it though, escalate to Oracle Support pretty quickly as it is not supposed to dump, no matter what.
That is, if for example memory is mis configured, it should just tell you, not dump.

Good luck!
Hein van den Heuvel.
HvdH Performance Consulting.

[Volker Borowski]

Hello,

it is not clear, if you want to get rid of the dumpfiles or the error causing them.
If the later, you should give us some extract from these dumpfiles otherwise it would be just guessing.

You can use max_dumpfile_size in init.ora to limit their size.

Volker

[tareq_2]

thanks for all