Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

user_dump_dest location is not working.

Bhavani DhulipallaJun 26 2017 — edited Jun 27 2017

Environment:11.2.0.4

Version Exadata

We are doing database wide tracing and found out that the mount point(/u01) is getting filled very quickly on 1st node and we wanted to change the user_dump_dest parameter to NFS mount point which is shared b/w two nodes.

1st case

started the tracing with below commans

alter system set timed_statistics = true;

alter system set statistics_level=all;

alter system set MAX_DUMP_FILE_SIZE=unlimited;

alter system set events '10046 trace name context forever,level 12'

found out that mount point is getting full ..so changed the user_dump_dest using below command

ALTER SYSTEM SET user_dump_dest='/backup/trace' SCOPE=BOTH SID='*';

Now on server

cd /backup/trace

[oracle@***********:/backup/trace]$ ll

total 0

Even I restarted the tracing and I don't see any trace files got created.  Please let me know if this is expected or do i need to change any other parameters?

Thanks for the help

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 25 2017
Added on Jun 26 2017
1 comment
662 views