Oradebug命令
SQL> oradebug help
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
SHORT_STACK Dump abridged OS stack
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
DUMPTYPE Print/dump an address with type info
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] [syslevel] 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
IPC Dump ipc information
UNLIMIT Unlimit the size of the trace file
PROCSTAT Dump process statistics
CALL [arg1] ... [argn] Invoke function with arguments
Oradebug 介绍
--确认要追逐的进程,spid,oracle自己的pid
SQL> select s.username, s.sid,s.serial#, p.spid from v$session s ,v$process p where s.paddr=p.addr;
USERNAME SID SERIAL# SPID
------------------------------ ---------- ---------- ------------
170 1 8690
169 1 8692
168 1 8694
167 1 8696
166 1 8698
--查询spid
SQL> select pid,spid,username from v$process;
PID SPID USERNAME
---------- ------------ ---------------
1
2 8690 oracle
3 8692 oracle
4 8694 oracle
5 8696 oracle
6 8698 oracle
--设定oradebug环境
SQL> oradebug setospid 8763
Oracle pid: 21, Unix process pid: 8763, image: oracle@node1 (q001)
SQL> oradebug unlimit;
Statement processed.
--sid设定后,可以用dump的东西可用oradebug dumplist列出
--设置debug事件,收集完成后关闭debug事件
SQL>oradebug event 10046 trace name context forever, level 8;
SQL>oradebug event 10046 trace name context off;
--获得系统状态
--
SQL>oradebug dump systemstate 10
SQL>oradebug hanganalyze 12
oradebug event 10046 trace name context forever, level 8;oradebug event 10046 trace name context off;
--Level
Level 1: 等同于SQL_TRACE的功能
Level 4: 在Level 1的基础上增加收集绑定变量的信息
Level 8: 在Level 1的基础上增加等待事件的信息
Level 12:等同于Level 4+Level 8,即同时收集绑定变量信息和等待事件信息。
--获得某个进程的状态
SQL>oradebug setospid 3333--该进程必须是Oracle进程
SQL> oradebug dump processstate 10
--也可以获得进程的错误信息状态SQL> oradebug dump errorstack 3已处理的语句(注:本处没有产生新的trace,难道是需要出错的时候才有信息?)--定位现在在使用哪个traceSQL> oradebug TRACEFILE_NAME
高级一点的应用1>Trace a session SQL1.1>如果是只想抓取用户sql语句的话(level 1),使用DBMS_SYSTEM包SQL> select s.username, s.sid,s.serial#, p.spid from v$session s ,v$process p where s.paddr=p.addr;
USERNAME SID SERIAL# SPID
------------------------------ ---------- ---------- ------------
170 1 8690
169 1 8692
168 1 8694
167 1 8696
166 1 8698
--开启对进程的trace,记录在trace文件中SQL> execute dbms_system.set_sql_trace_in_session(143,6,true);
--关闭追踪
SQL> execute dbms_system.set_sql_trace_in_session(143,6,false);
1.2>如果想进行更高级别的抓取,level 4,要使用oradebug--首先按照前面得到进程的spidSQL> oradebug setospid 3260Oracle pid: 22, Windows thread id: 3260, image: oracle.exe (SHAD)SQL> oradebug event 10046 trace name context forever,level 4已处理的语句(注:可以同时追踪多个进程,setospid …. , Oradebug …10046…)--抓取后取消追踪使用SQL> oradebug event 10046 trace name context off
--获得tracename
SQL>oradebug tracefile_name2>Tracing errors use oradebug例如要追踪能造成ORA-00942/952错误的会话,则SQL> oradebug event 942 trace name errorstack level 3已处理的语句SQL> oradebug event 952 trace name errorstack level 3已处理的语句3>Trace ORA-04030ORA-04030是由于某些进程请求的内存不断增大最后导致溢出的错误SQL > oradebug setodpidSQL > oradebug unlimitSQL > oradebug dump heapdump 5 this dump PGA and UGA heaps4>waking up PMON to release DDL locks首先确认PMON进程是whoSQL> select pid,spid from v$process p,v$bgprocess bwhere b.paddr=p.addrand name='PMON';PID SPID---------- ------------2 3608SQL> oradebug wakeup 2已处理的语句5>暂停和启动进程(suspending and resuming a process)SQL> oradebug setospid ***SQL> oradebug suspendOrSQL> oradebug setospid ***SQL> oradebug resume6>DUMP很多东西oradebug可以dump很多内容,例如latch / library_cache / locks / controlfile等具体可参照 oradebug dumplist的信息例子:oradebug dump controlf 10oradebug dump file_hdrs 10
--------------------------------------------------------------------------oradebug 可以帮助我们做很多事情,如dump内存信息、设置事件、挂起进程等。本文主要介绍如何使用oradebug挂起进程。为什么要挂起进程呢?比如因为开发人员对数据库执行一个很大的操作,严重影响了数据库的正常运行,此时你有两个选择:1、删掉进程2、暂停进程实际上,我们往往不能十分确定把进程直接kill掉会造成什么后果,所以暂停进程的执行就是一个比较折中的选择。要暂停进程步骤很简单:首先找到进程,然后暂停就可以了。使用oradebug暂停进程时,可以使用pid,也可以使用spid。要找出这些信息有很多方式了,比如可以在操作系统中ps -ef、可以通过v$session、v$process、v$bgprocess等视图通过关联得到。下面通过一个例子来说明如何 oradebug干预进程的执行状态:1、找出进程号本例我们要挂起以用户suk登录的会话:以sys用户登录查询:SQL> select pid,spid from v$process where addr in (select paddr from v$session where username='SCOTT');PID SPID---------- ------------10 41072、设置要操作的进程号有两种方法:1)用spid设置SQL> oradebug setospid 4107Oraclepid: 10, Unix process pid: 4107, image:oracle@suk(TNS V1-V3)2)用pid设置SQL> oradebug setorapid 10Unix process pid: 4107, image:oracle@suk(TNS V1-V3)3、暂停进程执行SQL> oradebug suspendStatement processed.此时,进程号为4107的进程将会处于挂起状态。我们稍后可以重启它。4、重启进程重启进程也要先设置进程号:SQL> oradebug setospid 4107Oracle pid: 10, Unix process pid: 4107, image:oracle@suk(TNS V1-V3)SQL> oradebug resume
Statement processed.注意:不能在会话中suspend当前会话。如果那样做的话,当前会话会被hang,并且不能被其他session resume,只能kill方式关闭。
--------------------------------------------------------------------------