在之前的HangAnalyze 中有使用oradebug命令,在这篇文章里,我们主要是重点看一下这个oradebug命令: 一. Oradebug 命令 帮助文档
SYS@dave2(db2)> oradebug help | Command | Arguments | Description |
| HELP | [command] | Describe one or all commands |
| SETMYPID | | Debug current process |
| SETOSPID | <ospid> | Set OS pid of process to debug |
| SETORAPID | <orapid> ["force"] | Set Oracle pid of process to debug |
| DUMP | <dump_name> <lvl> [addr] | Invoke named dump |
| DUMPSGA | [bytes] | Dump fixed SGA |
| DUMPLIST | | Print a list of available dumps |
| EVENT | <text> | Set trace event in process |
| SESSION_EVENT | <text> | Set trace event in session |
| DUMPVAR | <p|s|uga> <name> [level] | Print/dump a fixed PGA/SGA/UGA variable |
| SETVAR | <p|s|uga> <name> <value> | Modify a fixed PGA/SGA/UGA variable |
| PEEK | <addr> <len> [level] | Print/Dump memory |
| POKE | <addr> <len> <value> | Modify memory |
| WAKEUP | <orapid> | 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 | <Inst-List | def | all> | Parallel oradebug command prefix |
| -R | <Inst-List | def | all> | Parallel oradebug prefix (return output) |
| SETINST | <instance# .. | all> | Set instance list in double quotes |
| SGATOFILE | <SGA dump dir> | Dump SGA to file; dirname in double quotes |
| DMPCOWSGA | <SGA dump dir> | Dump & map SGA as COW; dirname in double quotes |
| MAPCOWSGA | <SGA dump dir> | 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 | <ifname> <ofname> | Helps translate PCs to names |
| WATCH | <address> <len> <self|exist|all|target> | Watch a region of memory |
| DELETE | <local|global|target> watchpoint <id> | Delete a watchpoint |
| SHOW | <local|global|target> watchpoints | Show watchpoints |
| CORE | | Dump core without crashing process |
| UNLIMIT | | Unlimit the size of the trace file |
| PROCSTAT | | Dump process statistics |
| CALL | <func> [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_nameFor example /export/home/admin/SS92003/udump/ss92003_ora_14917.trcThis 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 useSQL>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 useSQL>oradebug flush 1.4 CLOSE_TRACE command
To close the current trace file useSQL>oradebug close_tracedba_registry 和 v$option 与 Oracle 特新及组件Oracle 物理结果损坏处理相关资讯 Oracle教程
- Oracle中纯数字的varchar2类型和 (07/29/2015 07:20:43)
- Oracle教程:Oracle中查看DBLink密 (07/29/2015 07:16:55)
- [Oracle] SQL*Loader 详细使用教程 (08/11/2013 21:30:36)
| - Oracle教程:Oracle中kill死锁进程 (07/29/2015 07:18:28)
- Oracle教程:ORA-25153 临时表空间 (07/29/2015 07:13:37)
- Oracle教程之管理安全和资源 (04/08/2013 11:39:32)
|
本文评论 查看全部评论 (0)