SQL Exception Handling remember once PLUS can not log in

SQL Exception Handling remember once PLUS can not log in

phenomenon

  1. PLSQL Developer accessed via remote data card found dead did not respond.

  1. By Sqlplus access data also hang dead in the login screen, and can not be canceled by Ctrl + C

[oracle@oracle ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Tue Jul 30 10:31:33 2019

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


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
  1. alert logs without any error

  2. Cpu database without pressure

  3. The number of connections does not reach the setting processes

deal with

Oracle $  sqlplus  - prelim  /  AS  SYSDBA 
the SQL > the oradebug setmypid
the SQL > the oradebug unlimit
the SQL > the oradebug hanganalyze . 3
the SQL > the oradebug the dump systemstate 266
< certain time interval, such as 20 is seconds and once data downsampling performed . >
the SQL > the oradebug hanganalyze . 3
the SQL > oradebug dump systemstate 266
SQL >  oradebug tracefile_name
SQL> oradebug close_trace

Trace files generated by direct search keywordsblocker

      Dumping 1 direct blocker(s):
       inst: 1, sid: 2282, ser: 85
     Dumping final blocker:
       inst: 1, sid: 2282, ser: 85

final blocker sid: 2282, 2282 and then search for and find the following information

SO: 0x552acf480, type: 4, owner: 0x551708ef0, flag: INIT/-/-/0x00 if: 0x3 c: 0x3
    proc=0x551708ef0, name=session, file=ksu.h LINE:12729, pg=0
  (session) sid: 2282 ser: 85 trans: (nil), creator: 0x551708ef0
             flags: (0x10041) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
             flags2: (0x40009) -/-/INC
             DID: , short-term DID:
             txn branch: (nil)
             edition#: 100              oct: 3, prv: 0, sql: 0x557a67f20, psql: 0x557a692d8, user: 0/SYS
   ksuxds FALSE at location: 0
   service name: SYS$USERS
   client details:
     O/S info: user: oracle, term: UNKNOWN, ospid: 81552
     machine: dbh01 program: oracle@dbh01 (J000)
     application name: DBMS_SCHEDULER, hash value=2478762354
     action name: SM$CLEAN_AUTO_SPLIT_MERGE, hash value=1890521210
   Current Wait Stack:
    0: waiting for 'library cache: mutex X'
       idn=0x41bd76b6, value=0x2000000000, where=0x4f
       wait_id=71 seq_num=72 snap_id=1
       wait times: snap=3 min 13 sec, exc=3 min 13 sec, total=3 min 13 sec
       wait times: max=infinite, heur=872 min 45 sec
       wait counts: calls=17580 os=17579
       in_wait=1 iflags=0x15b2
   There are 91 sessions blocked by this session.
   Dumping one waiter:
     inst: 1, sid: 16, ser: 157
     wait event: 'latch: shared pool'
       p1: 'address'=0x6010f288
       p2: 'number'=0x150
       p3: 'tries'=0x0
     row_wait_obj#: 4294967295, block#: 0, row#: 0, file# 0
     min_blocked_time: 52361 secs, waiter_cache_ver: 60751
   Wait State:
     fixed_waits=0 flags=0x22 boundary=(nil)/-1

There are the following important information:

(session) sid: 2282

ospid: 81552

machine: dbh01

program: oracle@dbh01 (J000)

application name: DBMS_SCHEDULER, hash value=2478762354

action name: SM$CLEAN_AUTO_SPLIT_MERGE, hash value=1890521210

0: waiting for 'library cache: mutex X'

There are 91 sessions blocked by this session.

* Kill the OS process 81552, fault recovery. **

Guess you like

Origin www.cnblogs.com/plluoye/p/11277949.html