Database Administration (MOSC)

MOSC Banner

MAX_DUMP_FILE_SIZE behaviour and trace file rotation

edited Jul 9, 2009 8:42PM in Database Administration (MOSC) 12 commentsAnswered
 MAX_DUMP_FILE_SIZE puts a cap on trace file size and oracle stops writing to the specified trace files which reaches its max, but i have few concerns

once i clean this file oracle never starts back writing on the same trace.
is there a way i can get latest content of trace in case we hit any problem.
Is there a way to rotate trace files for oracle processes, so that i can keep the latest and delete the old.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center