05-06-2015
You should check to see if tracing is turned on in the database. Of the directories that you show, which directory has the diag directory and how large is the .../diag/rdbms/<sidname>/<sidname>/trace directory. If that is the directory that is growing, then you need to turn off tracing and clean up the old trace files. Another option would be if either the temp or undo table spaces can grow without limit. If so you should check the size of your temp and undo directories to see if they are way too large. Ultimately, this looks like a database issue.
Careful about deleting database files, unless you really want to practice your database recovery strategy. ;-)
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
How I can call routines for write large files' text if I've a libraries that can't be compiled in 64 bits? I tried whit open O_LARGEFILE option but if I see the rows whith cat are strange because I only see the first one. (1 Reply)
Discussion started by: glfuentes
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to understand the webserver log file for an error which has occured on my live web site.
The webserver access file is very big in size so it's not possible to open this file using vi editor. I know the approximate time the error occured, so i am interested in looking for the log file... (4 Replies)
Discussion started by: sehgalniraj
4 Replies
3. UNIX for Dummies Questions & Answers
How do we check 'large files' is enabled on a Unix box -- HP-UX B11.11 (2 Replies)
Discussion started by: ranj@chn
2 Replies
4. UNIX for Dummies Questions & Answers
I'm looking to display the largest files in a file system without descending into subdirectories.
The / file system is 65% full and I'm looking to display only the files in / without taking into
consideration other filesystem/directories.
I can execute this command
du -sk ./* |sort -nr... (2 Replies)
Discussion started by: Steelysteel
2 Replies
5. UNIX for Dummies Questions & Answers
When I have a file for example with the wrong name I normally use the cp {filename} {new filename} comand so I will have the original as well as the correct named file. Just for backup purposes.
Problem: I have a file that is 24gb with a case sensitive filename. The file was named with upper... (3 Replies)
Discussion started by: trek88
3 Replies
6. Shell Programming and Scripting
Hello everyone!
I have 2 types of files in the following format:
1) *.fa
>1234
...some text...
>2345
...some text...
>3456
...some text...
.
.
.
.
2) *.info
>1234 (7 Replies)
Discussion started by: ad23
7 Replies
7. Solaris
Hello everyone. Need some help copying a filesystem. The situation is this: I have an oracle DB mounted on /u01 and need to copy it to /u02. /u01 is 500 Gb and /u02 is 300 Gb. The size used on /u01 is 187 Gb. This is running on solaris 9 and both filesystems are UFS.
I have tried to do it using:... (14 Replies)
Discussion started by: dragonov7
14 Replies
8. UNIX for Dummies Questions & Answers
hi guys
I have suse 11 sp1 and I have a lot of warn file filling / these are under /var/log
there's this big one
-rw-r----- 1 root root 3.9G Feb 1 10:28 warn
warn: ASCII text
and the others that are about 2.5 to 3MB - they are about 130 warn-*.bz2
-rw-r----- 1 root root 3.9G Feb... (2 Replies)
Discussion started by: karlochacon
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have to text files that I want to merge by the first column. The values in the first column pretty much match for the first part. However there are some values that are present in column 1 and not present in column 2 or vice versa. For such values I would like to substitute X for the... (9 Replies)
Discussion started by: evelibertine
9 Replies
LEARN ABOUT CENTOS
trace-cmd
TRACE-CMD(1) TRACE-CMD(1)
NAME
trace-cmd - interacts with Ftrace Linux kernel internal tracer
SYNOPSIS
trace-cmd COMMAND [OPTIONS]
DESCRIPTION
The trace-cmd(1) command interacts with the Ftrace tracer that is built inside the Linux kernel. It interfaces with the Ftrace specific
files found in the debugfs file system under the tracing directory. A COMMAND must be specified to tell trace-cmd what to do.
COMMANDS
record - record a live trace and write a trace.dat file to the
local disk or to the network.
report - reads a trace.dat file and converts the binary data to a
ASCII text readable format.
hist - show a histogram of the events.
options - list the plugin options that are available to *report*
start - start the tracing without recording to a trace.dat file.
stop - stop tracing (only disables recording, overhead of tracer
is still in effect)
extract - extract the data from the kernel buffer and create a trace.dat
file.
reset - disables all tracing and gives back the system performance.
(clears all data from the kernel buffers)
split - splits a trace.dat file into smaller files.
list - list the available plugins or events that can be recorded.
listen - open up a port to listen for remote tracing connections.
restore - restore the data files of a crashed run of trace-cmd record
stack - run and display the stack tracer
check-events - parse format strings for all trace events and return
whether all formats are parseable
OPTIONS
-h, --help
Display the help text.
Other options see the man page for the corresponding command.
SEE ALSO
trace-cmd-record(1), trace-cmd-report(1), trace-cmd-hist(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1),
trace-cmd-reset(1), trace-cmd-restore(1), trace-cmd-stack(1), trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1), trace-cmd.dat(5),
trace-cmd-check-events(1)
AUTHOR
Written by Steven Rostedt, <rostedt@goodmis.org[1]>
RESOURCES
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
COPYING
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
NOTES
1. rostedt@goodmis.org
mailto:rostedt@goodmis.org
06/11/2014 TRACE-CMD(1)