重启数据库的一场闹剧(r5笔记第68天)
在几周前，某个测试环境在尝试impdp导入dump的时候报了错误，有个DBA立马做了kill session的操作，但是持续了5个小时，session状态还是KILLED,于是他们就在等待session被pmon回收。结果又等了几个小时，还是KILLED状态。最后两拨DBA在交接的时候把这个问题就说明了一下，另外一个DBA继续尝试impdp就报了下面的错误。
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-31626: job does not exist
ORA-31637: cannot create job XXXXXX for user xxxxxx
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 798
ORA-31635: unable to establish job resource synchronization
因为已经做了kill操作，对应的进程已经不好定位了。所以作为一个小教训，自己会在kill session的时候尝试也找到对应的进程号。Shutting down instance (immediate)ORA-01092: ORACLE instance terminated. Disconnection forcedORA-00450: background process 'QMNC' did not startORA-00443: background process "QMNC" did not startProcess ID: 47857Session ID: 10341 Serial number: 3
Tue May 26 10:48:05 2015
Shutting down instance (immediate)
Stopping background process SMCO
我发送了封邮件抄给组内去确认，还没有得到消息。