数据库无法正常关闭的处理步骤

最新推荐文章于 2018-01-27 18:50:18 发布

1ihj2015

最新推荐文章于 2018-01-27 18:50:18 发布

阅读量1.1k

点赞数

CC 4.0 BY-SA版权

分类专栏： Oracle Troubleshooting

本文链接：https://blog.youkuaiyun.com/itdba/article/details/37689713

Oracle Troubleshooting 专栏收录该内容

37 篇文章

订阅专栏

本文记录了一次Oracle数据库中出现的问题及解决过程，包括使用oradebug进行跟踪、查看进程状态和通过kill命令终止异常进程等内容。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1 shen zhi shijian

SQL> conn / as sysdba
Connected.
SQL> oradebug setmypid
Statement processed.
SQL> oradebug event 10400 trace name context forever,level 1
Statement processed.
SQL> oradebug tracefile_name
Statement processed.
SQL> oradebug tracefile_name
Statement processed.
SQL> oradebug event 10400 trace name context forever,level 1;
Statement processed.
SQL> oradebug tracefile_name
Statement processed.
SQL> oradebug event 10046 trace name context forever,level 12;
Statement processed.
SQL> oradebug tracefile_name
/home/oracle/admin/text/udump/text_ora_17673.trc

2cha kan gen zong

FETCH #2:c=1000,e=561,p=0,cr=0,cu=0,mis=0,r=1,dep=2,og=1,tim=1372108683411088
EXEC #1:c=4000,e=3627,p=0,cr=0,cu=0,mis=0,r=1,dep=1,og=4,tim=1372108683413837
WAIT #0: nam='dispatcher shutdown' ela= 1 waited=0 p2=0 p3=0 obj#=-1 tim=1372108683417612
WAIT #0: nam='dispatcher shutdown' ela= 977376 waited=1 p2=0 p3=0 obj#=-1 tim=1372108684395025
WAIT #0: nam='dispatcher shutdown' ela= 978464 waited=2 p2=0 p3=0 obj#=-1 tim=1372108685373580
ksukia: Starting kill, force = 0
ksukia: Attempt 1 to kill process oracle@VSZ-ORCLE-jftest (TNS V1-V3), OS id=17637

ksukia: killed 1 out of 1 processes.
WAIT #0: nam='opishd' ela= 978219 p1=0 p2=0 p3=0 obj#=-1 tim=1372108686352109
ksukia: Starting kill, force = 0
ksukia: killed 0 out of 1 processes.
WAIT #0: nam='opishd' ela= 977509 p1=0 p2=0 p3=0 obj#=-1 tim=1372108687329748
ksukia: killed 0 out of 1 processes.
WAIT #0: nam='opishd' ela= 978413 p1=0 p2=0 p3=0 obj#=-1 tim=1372108690264389
ksukia: Starting kill, force = 0
ksukia: Attempt 2 to re-kill process oracle@VSZ-ORCLE-jftest (TNS V1-V3), OS id=17637
*** 2014-07-11 08:41:38.830
Process diagnostic dump for oracle@VSZ-ORCLE-jftest (TNS V1-V3), OS id=17637,
pid: 11, proc_ser: 3, sid: 153, sess_ser: 7

-------------------------------------------------------------------------------
loadavg : 0.01 0.30 0.28
Memory (Avail / Total) = 593.34M / 3949.79M
Swap (Avail / Total) = 5951.92M / 5951.99M
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
0 Z oracle 17637 17636 0 77 0 - 0 exit 08:38 ? 00:00:00 [oracle] <defunct>
Short stack dump: WAIT #0: nam='ksdxexeotherwait' ela= 19 p1=0 p2=0 p3=0 obj#=-1 tim=1372108690283323
WAIT #0: nam='ksdxexeotherwait' ela= 2 p1=0 p2=0 p3=0 obj#=-1 tim=1372108690283375
WAIT #0: nam='ksdxexeotherwait' ela= 2 p1=0 p2=0 p3=0 obj#=-1 tim=1372108690283408

[oracle@VSZ-ORCLE-jftest ~]$ ps -ef|grep sqlplus
oracle   17636 17604 0 08:38 pts/5    00:00:00 sqlplus
oracle   17643 17440 0 08:38 pts/1    00:00:00 grep sqlplus
[oracle@VSZ-ORCLE-jftest ~]$ ps -ef|grep sqlplus
oracle   17636 17604 0 08:38 pts/5    00:00:00 sqlplus
oracle   17672 17644 0 08:38 pts/5    00:00:00 sqlplus
oracle   17675 17440 0 08:38 pts/1    00:00:00 grep sqlplus

[oracle@VSZ-ORCLE-jftest ~]$ ps -ef|grep sqlplus
oracle   17636 17604 0 08:38 pts/5    00:00:00 sqlplus
oracle   17672 17644 0 08:38 pts/5    00:00:00 sqlplus
oracle   17688 17440 0 08:42 pts/1    00:00:00 grep sqlplus
[oracle@VSZ-ORCLE-jftest ~]$ ps -ef|grep 17637
oracle   17637 17636 0 08:38 ?        00:00:00 [oracle] <defunct>
oracle   17694 17440 0 08:42 pts/1    00:00:00 grep 17637
[oracle@VSZ-ORCLE-jftest ~]$ kill -9 17636

--就可以成功关闭