Oracle数据库shutdown immediate被hang住的几个原因
实验操作环境:
操作系统:Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
数据库 : Oracle Database 10g Release 10.2.0.4.0 – Production 32bit
今晚使用shutdown immediate(其实是执行stop_oracle.sh脚本关闭数据库,如下所示)关闭数据库的时候,
1: [oracle@gsp-orasvr02 scripts]$ more stop_oracle.sh
2: lsnrctl stop LISTENER
3: sleep 15
4: sqlplus /nolog <<EOF
5: conn / as sysdba;
6: alter system switch logfile;
7: alter system checkpoint;
8: shutdown immediate;
9: exit
10: EOF
在另外一个会话中使用tail -20f 命令查看告警日志的输出,结果发现数据库等待了很长时间都没有正常关闭,hang住在下面地方:
Active call for process 11121 user 'oracle' program 'oracle@get-orasvr02 (S000)'
Active call for process 7162 user 'oracle' program 'oracle@get-orasvr02 (S011)'
截图如下
这时解决办法是找出hang住的进程并杀掉(当时操作没有截图,也没有保存输出信息),因为有些session无法被pmon进程清理,导致数据库无法顺利关闭,需要手工杀掉进程。首先使用ps 和grep找到这两个进程。
[ oracle@get-orasvr02 bdump]$ ps -ef | grep oracle | grep S000
[ oracle@get-orasvr02 bdump]$ ps -ef | grep oracle | grep S011
然后使用kill -9 processesid杀掉这两个进程即可,杀掉这两个进程后,从告警日志里面看到里面跳到关闭dispatcher 。如下所示:
1: [ oracle@get-orasvr02 bdump]$ tail alert_epps.log
2: Current log# 3 seq# 242223 mem# 1: /u02/oradata/epps/redo03_01.log
3: Sun Jan 5 05:14:50 2014
4: Starting control autobackup
5: Control autobackup written to DISK device
6: handle '/u01/app/oracle/product/10.2.0/db_1/dbs/c-2179993557-20140105-0e'
7: Sun Jan 5 05:14:54 2014
8: ALTER SYSTEM ARCHIVE LOG
9: Sun Jan 5 05:14:55 2014
10: Thread 1 cannot allocate new log, sequence 242224
11: Checkpoint not complete
12: Current log# 3 seq# 242223 mem# 0: /u01/app/oracle/oradata/epps/redo03_1.log
13: Current log# 3 seq# 242223 mem# 1: /u02/oradata/epps/redo03_01.log
14: Sun Jan 5 05:14:58 2014
15: Thread 1 advanced to log sequence 242224 (LGWR switch)
16: Current log# 5 seq# 242224 mem# 0: /u01/app/oracle/oradata/epps/redo05_1.log
17: Current log# 5 seq# 242224 mem# 1: /u02/oradata/epps/redo05_02.log
18: Sun Jan 5 07:31:56 2014
19: Thread 1 advanced to log sequence 242225 (LGWR switch)
20: Current log# 2 seq# 242225 mem# 0: /u01/app/oracle/oradata/epps/redo02_1.log
21: Current log# 2 seq# 242225 mem# 1: /u02/oradata/epps/redo02_02.log
22: Sun Jan 5 07:32:20 2014
23: Starting background process EMN0
24: Shutting down instance: further logons disabled
25: EMN0 started with pid=43, OS id=7062
26: Sun Jan 5 07:32:21 2014
27: Stopping background process CJQ0
28: Sun Jan 5 07:32:21 2014
29: Stopping background process QMNC
30: Sun Jan 5 07:32:23 2014
31: Stopping background process MMNL
32: Sun Jan 5 07:32:34 2014
33: Background process MMNL not dead after 10 seconds
34: Sun Jan 5 07:32:34 2014
35: Killing background process MMNL
36: Sun Jan 5 07:32:35 2014
37: Stopping background process MMON
38: Sun Jan 5 07:33:05 2014
39: Background process MMON not dead after 30 seconds
40: Sun Jan 5 07:33:05 2014
41: Killing background process MMON
42: Sun Jan 5 07:33:06 2014
43: Shutting down instance (immediate)
44: License high water mark = 561
45: Sun Jan 5 07:33:06 2014
46: Stopping Job queue slave processes, flags = 7
47: Sun Jan 5 07:33:06 2014
48: Process OS id : 6088 alive after kill
49: Errors in file /u01/app/oracle/admin/epps/udump/epps_ora_7055.trc
50: Sun Jan 5 07:33:09 2014
51: Waiting for Job queue slaves to complete
52: Sun Jan 5 07:33:09 2014
53: Job queue slave processes stopped
54: Sun Jan 5 07:38:10 2014
55: Active call for process 11121 user 'oracle' program 'oracle@get-orasvr02 (S000)'
56: Active call for process 7162 user 'oracle' program 'oracle@get-orasvr02 (S011)'
57: SHUTDOWN: waiting for active calls to complete.
58: Sun Jan 5 07:57:28 2014
59: Waiting for dispatcher 'D000' to shutdown
60: Waiting for dispatcher 'D001' to shutdown
61: Waiting for dispatcher 'D002' to shutdown
62: Waiting for dispatcher 'D003' to shutdown
63: Waiting for dispatcher 'D004' to shutdown
64: Waiting for dispatcher 'D005' to shutdown
65: Waiting for dispatcher 'D006' to shutdown
66: Sun Jan 5 07:59:29 2014
67: All dispatchers and shared servers shutdown
68: Sun Jan 5 08:04:30 2014
69: SHUTDOWN: Active processes prevent shutdown operation
70: Sun Jan 5 08:09:32 2014
71: SHUTDOWN: Active processes prevent shutdown operation
Oracle的官方文档介绍、解释如下
The database is waiting for pmon to clean up processes, but pmon is unable to
clean them. The client connections to the server are causing the shutdown
immediate or normal to hang. Killing them allows pmon to clean up and release
the associated Oracle processes and resources.
What resources are we talking about?
1) Any non committed transactions must be rolled back
2) Any temporary space (sort segments / lobs / session temporary tables) must be freed
3) The session itself and any associated memory consumed by the session.
4) Internal locks / enqueues must be cleaned up
Often Oracle (SMON or PMON depending on whether Shared Server is used) will wait for the OS to terminate the process(es) associated with the session. If the OS never returns, or fails to terminate them, then the instance shutdown will hang with this message (Shutdown Waiting for Active Calls to Complete)
Other means exist to achieve a quick shutdown, as outlined inNote 386408.1- What Is The Fastest Way To Cleanly Shutdown An Oracle Database?
结果解决上面问题后,本以为可以顺利关闭数据库,结果又hang住了,告警日志信息提示为
SHUTDOWN: Active processes prevent shutdown operation
出现这个错误原因:
因为我大概如下的操作导致:
[oracle@gsp-orasvr02 scripts]$ sqlplus / as sysdba
...........
SQL> !
[oracle@get-orasvr02 ~]$
..... (执行了一些shell 命令)
然后又使用了sqlplus启动登录了数据库,然后做shutdown immediate操作,这时导致shutdown immediate被hang住。
[oracle@gsp-orasvr02 scripts]$ sqlplus / as sysdba
解决办法:退出当前的会话,回到原始会话,并重新连接,就可以正常的关闭数据库了
参考资料:
http://oracle.chinaitlab.com/optimize/761636_2.html
http://blog.csdn.net/xionglang7/article/details/8997081
http://blog.csdn.net/leshami/article/details/9466559
Oracle数据库shutdown immediate被hang住的几个原因的更多相关文章
- 如何诊断oracle数据库运行缓慢或hang住的问题
为了诊断oracle运行缓慢的问题首先要决定收集哪些论断信息,可以采取下面的诊断方法:1.数据库运行缓慢这个问题是常见还是在特定时间出现如果数据库运行缓慢是一个常见的问题那么可以在问题出现的时候收集这 ...
- Oracle数据库的经典问题 snapshot too old是什么原因引起的
Oracle数据库的经典问题 snapshot too old是什么原因引起的 ORACLE经典错误求解:ORA-1555错误(Snapshot too old ) - ... 书上说是因为the r ...
- shutdown immediate时 hang住 (转载)
shutdown immediate 经常关库时hang住,在alert中有 License high water mark = 4All dispatchers and shared servers ...
- oracle数据库字符集和客户端字符集(2%)是不同的,字符集转化可能会造成不可预期的后果
转载请在文章显眼位置注明出处:https://www.cnblogs.com/sunshine5683/p/10036321.html 今天在plsql连接oracle时候报错提示“数据库字符集和客户 ...
- df执行hang住
一.现象 在linux操作系统中,执行df -h命令,后hang住 二.思路 排查是否存在Nfs问题,无法正常挂载nfs路径导致的问题. 三.解决过程 3.1 cat /etc/rc.local #m ...
- linux下重启oracle数据库
如何在linux下重启oracle数据库 | 浏览:3930 | 更新:2013-09-18 19:33 1 2 3 4 5 6 分步阅读 在实际工作项目中,有时候会遇到需要对oracle数据库进行重 ...
- 一次数据库hang住的分析过程
现象: 普通用户和sysdba都无法登陆,业务中断 分析过程: 1.先做hanganalyze和systemstate dump $sqlplus -prelim "/as sysdba&q ...
- NDMCDB数据库hang住故障分析 - cursor: pin S wait on X
问题描写叙述: 上午刚刚到办公室,就有监控人员邮件反馈,昨晚NDMCDB407数据库被重新启动过,让我分析一下数据库重新启动的原因.因为昨晚业务有版本号上线,所以短信警告关闭了,所以没有短信下发到我手 ...
- oracle故障处理之删除大表空间hang住
背景 数据库分区表数据越来越大,需要对过期话的数据进行迁移,以及大的分区表需要进行数据的清理和删除,达到释放磁盘空间的目的. 问题说明 环境:linux 6.X 数据库:oracle 11.2.0.4 ...
随机推荐
- 安装nginx
[yum安装nginx] yum clean all(这步不执行会出现no more mirrors to try错误) cd /etc/yum.repos.d/ vi nginx.repo 填写 [ ...
- Java (JVM) Memory Model – Memory Management in Java
原文地址:http://www.journaldev.com/2856/java-jvm-memory-model-memory-management-in-java Understanding JV ...
- CentOS 7.2 yum方式安装MySQL 5.7
CentOS 7之后的版本yum的默认源中使用MariaDB替代原先MySQL,因此安装方式较为以往有一些改变: 下载mysql的源 wget http://dev.mysql.com/get/mys ...
- vue+node开发手机端h5页面开发遇到的坑
项目进行中...随时更新 这里记录了一些手机端调试的方式 一 css 1.文字超过span宽度显示...(单行文字) .topWrap .introduce span { padding: 0 17p ...
- 【Java基础】并发
Num1:同步访问共享的可变数据 关键字Synchronized可以保证在同一时刻,只有一个线程可以执行某一个方法,或者某一个代码块.. 同步不仅仅理解为互斥的方式,如果没有同步,一个线程的变化就不能 ...
- chrome浏览器的跨域设置——包括版本49前后两种设置
做前后分离的webapp开发的时候,出于一些原因往往需要将浏览器设置成支持跨域的模式,好在chrome浏览器就是支持可跨域的设置,网上也有很多chrome跨域设置教程.但是新版本的chrome浏览器提 ...
- PHP获取网站图标(favicon.ico)文件
有的网站源码中加入了这几行代码: <link rel="shortcut icon" href="/favicon.ico" type="ima ...
- 【Python实战】Django建站笔记
前一段时间,用Django搭建一个报表分析的网站:借此正好整理一下笔记. 1. 安装 python有包管理工具pip,直接cd Python27/Scripts,输入 pip install djan ...
- Composer Player 属性设置
/// <summary> /// 设置选中名称 /// </summary> /// <param name="name"></para ...
- [修正] Firemonkey TSelection 控件等比缩放时,左下角拉动问题
说明:TSelection 控件,当在属性 Proportional = True 为等比缩放时,拉动左下角,右上角会跟着移动. 适用:Berlin 10.1.1 (或之前版本) Firemonkey ...