ORA-03135 connections lost contact Process ID:0

场景描述:

领导callme,说pslql远程登录报错,报错信息:

1,赶紧vpn,登录后台去查看负载,看到负载很低:

[oracle@powerlong4 ~]$ w
 20:05:16 up 22 days,  6:33,  3 users,  load average: 0.45, 0.58, 0.38
USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT
root     pts/0    192.168.120.218  19:32   19:30   0.16s  0.03s sqlplus   as sysdba
root     pts/1    192.168.120.218  19:39    0.00s  0.18s  0.03s w
root     pts/2    :1.0             Fri15    5days  2:23   0.02s -bash
[oracle@powerlong4 ~]$ 


<版权所有,文章允许转载,但必须以链接方式注明源地址,否则追究法律责任!>

原博客地址: http://blog.csdn.net/mchdba/article/details/45921045

原作者:黄杉 (mchdba)


2,再去查看alert日志:

Wed May 27 02:00:00 2015
Clearing Resource Manager plan via parameter
Wed May 27 07:15:39 2015
Suspending MMON action ‘Block Cleanout Optim, Undo Segment Scan‘ for 82800 seconds
Wed May 27 07:35:48 2015
Suspending MMON action ‘undo usage‘ for 82800 seconds
Wed May 27 07:56:08 2015
Suspending MMON action ‘metrics monitoring‘ for 82800 seconds
Wed May 27 08:11:17 2015
Suspending MMON slave action kewrmafsa_ for 82800 seconds
Wed May 27 08:16:23 2015
Suspending MMON action ‘AWR Auto Purge Task‘ for 82800 seconds
Wed May 27 16:56:14 2015
Suspending MMON slave action kewfmcpsa_ for 82800 seconds
Wed May 27 19:32:45 2015

***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.1.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
  Time: 27-MAY-2015 19:32:45
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535

TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.120.218)(PORT=55693))
Wed May 27 19:39:43 2015

3,alert日志中没有看出啥问题来,去check是否有锁,卡住了,只好ctrl+c停住

执行sql检查是否有锁

SQL> select t2.username,t2.sid,t2.serial#,t2.logon_time from v$locked_object t1,v$session t2 where t1.session_id=t2.sid order by t2.logon_time;
^Cselect t2.username,t2.sid,t2.serial#,t2.logon_time from v$locked_object t1,v$session t2 where t1.session_id=t2.sid order by t2.logon_time
                                                        *
ERROR at line 1:
ORA-01013: user requested cancel of current operation

SQL> 

4,尝试重启下,卡住了,shutdown hang住了

SQL> shutdown immediate
^CORA-01013: user requested cancel of current operation

SQL> 

后台alert日志信息

Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
Wed May 27 19:39:44 2015
Stopping background process CJQ0
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
Wed May 27 19:39:48 2015
AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
License high water mark = 28
Stopping Job queue slave processes, flags = 7
Wed May 27 19:39:48 2015
Errors in file /oracle/app/oracle/diag/rdbms/pddev1/pddev1/trace/pddev1_j005_8455.trc:
ORA-12012: error on auto execute of job 57381
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-01089: immediate shutdown in progress - no operations are permitted
Process ID:
Session ID: 0 Serial number: 0
Wed May 27 19:39:48 2015
opiodr aborting process unknown ospid (7674) as a result of ORA-1089
Wed May 27 19:39:48 2015
opiodr aborting process unknown ospid (7002) as a result of ORA-1089
Wed May 27 19:39:48 2015
opiodr aborting process unknown ospid (9183) as a result of ORA-1089
Job queue slave processes stopped
Wed May 27 19:42:46 2015
Instance shutdown cancelled

再去看下trace日志,如下:

[[email protected] ~]$ more /oracle/app/oracle/diag/rdbms/pddev1/pddev1/trace/pddev1_j005_8455.trc
Trace file /oracle/app/oracle/diag/rdbms/pddev1/pddev1/trace/pddev1_j005_8455.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1
System name:    Linux
Node name:  powerlong4
Release:    2.6.32-358.el6.x86_64
Version:    #1 SMP Fri Feb 22 00:31:26 UTC 2013
Machine:    x86_64
Instance name: pddev1
Redo thread mounted by this instance: 1
Oracle process number: 49
Unix process pid: 8455, image: [email protected] (J005)

*** 2015-05-27 19:39:48.078
*** SESSION ID:(79.110) 2015-05-27 19:39:48.078
*** CLIENT ID:() 2015-05-27 19:39:48.078
*** SERVICE NAME:(SYS$USERS) 2015-05-27 19:39:48.078
*** MODULE NAME:() 2015-05-27 19:39:48.078
*** ACTION NAME:() 2015-05-27 19:39:48.078

ORA-12012: error on auto execute of job 57381
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-01089: immediate shutdown in progress - no operations are permitted
Process ID:
Session ID: 0 Serial number: 0
[[email protected] ~]$ 

5,没有看出啥问题,领导催的紧急,看来只好用绝招了shutdown abort;

SQL> shutdown abort
ORACLE instance shut down.
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.

Total System Global Area 1820540928 bytes
Fixed Size          2214296 bytes
Variable Size        1191183976 bytes
Database Buffers      620756992 bytes
Redo Buffers            6385664 bytes
Database mounted.
Database opened.
SQL> select t2.username,t2.sid,t2.serial#,t2.logon_time from v$locked_object t1,v$session t2 where t1.session_id=t2.sid order by t2.logon_time;

no rows selected

SQL> 

OK,能登录正常了。事后诸葛亮,我这台线上db完全是边缘业务,无压力的,怎么会plsql远程登录不上呢?奇怪。看alert日志也么有异常信息,留此纪念,以待后续观察。

时间: 2024-08-10 12:23:23

ORA-03135 connections lost contact Process ID:0的相关文章

error: failed to attach to process ID 0

重启Xcode可能会正确运行,或者用以下方法: 步骤1:Xcode目录Window->Organizer,将工程名文件删除. 步骤2:Xcode目录Xcode->Open Developer Tool->iOS Simulator,弹出模拟器后,菜单上"iOS模拟器"选项->还原内容和设置,退出模拟器. 步骤3:重启Xcode.

Failed to Attach to Process ID Xcode 解决办法

方法1. go to the Product menu and find the Edit Scheme menu there. While in Edit Scheme window, select the "Run" option on the left hand side of the screen and then on the right hand side, change the debugger from LLDB to GDB. 方法2. Step1: ping$ pi

open数据库报错ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 3880 Session ID: 125 Serial number: 3

1.今天打开数据时,失败,报错 ERROR at line 1:ORA-03113: end-of-file on communication channelProcess ID: 3880Session ID: 125 Serial number: 3 2.想看下数据库的状态,发现提示:not connected to ORACLE[email protected]> select status,instance_name from v$instance;ERROR:ORA-03114: no

jQuery对象与dom对象的转换-$(&#39;#id)[0]

取原生态的DOM对象,因为jquery会把选择器匹配的dom对象存放在以$.fn.init为构造函数生成对象的泛型数组里. 一直以来对于通过jQuery方式获取的对象使不能直接使用JavaScript的一些方法的,开始的时候不理解,现在此案知道,原来jQuery获得的对象并不和我们平时使用getElementById获得的对象是一样的对象.所以一些新手就很迷惑,为什么${"#Element"}不能直接innerHTML,这就是原因所在,解决方式请看下文.jQuery对象与dom对象的转

java代码中获取进程process id(转)

另一方面,线程ID=进程ID+内部线程对象ID并不成立,    参考: blog.csdn.net/heyetina/article/details/6633901     如何在java代码中获取进程process id, 实现方法如下所示:    参考: rednaxelafx.iteye.com/blog/716918 http://www.cnblogs.com/mumuxinfei/p/3678854.html

kkjcre1p: unable to spawn jobq slave process, slot 0, error 1089(Linux x86_64)补丁

在shutdown immediately的时候,alert Log出现如下错误信息,并且不能正常关闭 kkjcre1p: unable to spawn jobq slave process, slot 0, error 1089 该问题是由bug23102157引起,查看MOS,并没有Linux平台的Patch,后来开SR,Oracle support高效的开发出来Linux x86_64平台的补丁并更新出来. 补丁链接 https://updates.oracle.com/download

Transaction (Process ID xxx) was deadlocked on lock

Transaction (Process ID 161) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. --This will cause read transactions to not take any locks and not be blocked

进程ID[PID(Process ID)]与端口号[(Port ID)]的联系

1.首先声明一点:PID不是端口(port id),而是Process ID进程号的意思. 2.那么,什么是进程号? 采集网友的意见就是: 进程号,是系统分配给么一个进程的唯一标识符.PID就是各进程的身份标识符,程序一运行系统就会自动分配给进程一个独一无二的PID.进程终止后,PID被系统回收,可能会被继续给新运行的程序. 3.深入理解二者关系: 一个程序一个端口: 一个端口可以有多个进程: (顺便提一下:一个进程可以有多个线程(将一个进程的系统资源共享给一个程序内多道分程序,并行运行,以达到

Kafka:Configured broker.id 2 doesn&#39;t match stored broker.id 0 in meta.properties.

在安装Kafka集群的时候,碰到这个问题. 我们知道在搭建Kafka集群的时候,我们需要设置broker.id,以作为当前服务器在整个集群的唯一标志. 网上搜查资料是说,log.dirs目录下的meta.properties中配置的broker.id和配置目录下的server.properties中的broker.id不一致了,解决问题的方法是将两者修改一致后再重启. 而当时为何会产生这个问题? 1.Kafka配置目录下文件server.properties中一个broker.id # The