一. Oradebug 命令 帮助文档
SYS@dave2(db2)> oradebug help
Command
Arguments
Description
HELP
[command]
Describe one or all commands
SETMYPID
Debug current process
SETOSPID
Set OS pid of process to debug
SETORAPID
['force']
Set Oracle pid of process to debug
DUMP
[addr]
Invoke named dump
DUMPSGA
[bytes]
Dump fixed SGA
DUMPLIST
Print a list of available dumps
EVENT
Set trace event in process
SESSION_EVENT
Set trace event in session
DUMPVAR
[level]
Print/dump a fixed PGA/SGA/UGA variable
SETVAR
Modify a fixed PGA/SGA/UGA variable
PEEK
[level]
Print/Dump memory
POKE
Modify memory
WAKEUP
Wake up Oracle process
SUSPEND
Suspend execution
RESUME
Resume execution
FLUSH
Flush pending writes to trace file
CLOSE_TRACE
Close trace file
TRACEFILE_NAME
Get name of trace file
LKDEBUG
Invoke global enqueue service debugger
NSDBX
Invoke CGS name-service debugger
-G
Parallel oradebug command prefix
-R
Parallel oradebug prefix (return output)
SETINST
Set instance list in double quotes
SGATOFILE
Dump SGA to file; dirname in double quotes
DMPCOWSGA
Dump & map SGA as COW; dirname in double quotes
MAPCOWSGA
Map SGA as COW; dirname in double quotes
HANGANALYZE
[level]
Analyze system hang
FFBEGIN
Flash Freeze the Instance
FFDEREGISTER
FF deregister instance from cluster
FFTERMINST
Call exit and terminate instance
FFRESUMEINST
Resume the flash frozen instance
FFSTATUS
Flash freeze status of instance
SKDSTTPCS
Helps translate PCs to names
WATCH
Watch a region of memory
DELETE
watchpoint
Delete a watchpoint
SHOW
watchpoints
Show watchpoints
CORE
Dump core without crashing process
UNLIMIT
Unlimit the size of the trace file
PROCSTAT
Dump process statistics
CALL
[arg1] ... [argn]
Invoke function with arguments
1.1 TRACEFILE_NAME command
This command prints the name of the current trace file e.g.
SQL>oradebug tracefile_name
For example
/export/home/admin/SS92003/udump/ss92003_ora_14917.trc
This command does not work on Windows 2000 (Oracle 9.2)
1.2 UNLIMIT command
In Oracle 8.1.5 and below the maximum size of the trace file is restricted by default. This means that large dumps (LIBRARY_CACHE, BUFFERS) may fail.
To remove the limitation on the size of the trace file use
SQL>oradebug unlimit
In Oracle 8.1.6 and above the maximum size of the trace file defaults to UNLIMITED
1.3 FLUSH command
To flush the current contents of the trace buffer to the trace file use
SQL>oradebug flush
1.4 CLOSE_TRACE command
To close the current trace file use
SQL>oradebug close_trace