Database Reference
In-Depth Information
SQL> ORADEBUG SETOSPID 14807
Oracle pid: 34, Unix process pid: 14807, image: oracleDZAV024@l012r065
SQL> ORADEBUG SHORT_STACK
ksdxfstk()+32<-ksdxcb()+1547<-sspuser()+111<-__funlockfile()+64<-kdsgrp()+283<- kdsf
br()+228<-qertbFetchByRowID()+889<-qergiFetch()+315<-qergiFetch()+315<- qernsFetch()
+603<-qerseFetch()+158<-subex1()+176<-subsr3()+195<-evaopn2()+4188<- expepr..7()+470
<-expeal()+82<-qerflFetchOutside()+158<-rwsfcd()+88<-insfch()+496<- insdrv()+592<-in
scovexe()+404<-insExecStmtExecIniEngine()+85<-insexe()+343<- opiexe()+9038<-opipls()
+2107<-opiodr()+984<-rpidrus()+198<-skgmstack()+158<- rpidru()+116<-rpiswu2()+420<-r
pidrv()+1519<-psddr0()+438<-psdnal()+339<- pevm_EXIM()+216<-pfrinstr_EXIM()+53<-pfrr
un_no_tool()+65<-pfrrun()+906<- plsql_run()+841<-peicnt()+298<-kkxexe()+504<-opiexe(
)+9038<-opipls()+2107<- opiodr()+984<-rpidrus()+198<-skgmstack()+158<-rpidru()+116<-
rpiswu2()+420<- rpidrv()+1519<-psddr0()+438<-psdnal()+339<-pevm_EXIM()+216<-pfrinstr
_EXIM()+53<- pfrrun_no_tool()+65<-pfrrun()+906<-plsql_run()+841<-peicnt()+298<-kkxex
e()+504<- opiexe()+9038<-kpoal8()+2280<-opiodr()+984<-ttcpip()+1235<-opitsk()+1298<-
opiino()+1028<-opiodr()+984<-opidrv()+547<-sou2o()+114<-opimai_real()+163<- main()+
116<-__libc_start_main()+234<-_start()+42
The current routine is at the top of the output. Of course, dumping the call stack affects the
call stack itself. Presumably ksdxcb is a debug callback function for performing a stack dump. I
assume that the routine kdsgrp was executed when the command SHORT_STACK was received by
the attached process. The names of the routines may be used as search keywords on the Metalink
support platform.
Diagnostic Dumps
Oracle9 i Release 2 supports 85 different diagnostic dumps, Oracle10 g supports 146, and Oracle11 g
165. Due to the large amount of dumps, it's impossible to cover more than a few. To list the
dump names, run ORADEBUG DUMPLIST .
CONTROLF
This option is for dumping the control file(s) at different levels of detail. Here's an example of a
level 1 dump:
Received ORADEBUG command 'DUMP CONTROLF 1' from process Windows thread id: 3580,
image:
DUMP OF CONTROL FILES, Seq # 545 = 0x221
V10 STYLE FILE HEADER:
Compatibility Vsn = 169869568=0xa200100
Db ID=1156831202=0x44f3d7e2, Db Name='ORCL'
Activation ID=0=0x0
Control Seq=545=0x221, File size=430=0x1ae
File Number=0, Blksiz=16384, File Type=1 CONTROL
 
Search WWH ::




Custom Search