Oracle单实例情况下的library cache pin的问题模拟与问题分析

本文通过创建多个用户及对象,在Oracle单实例环境下模拟了library cache pin等待事件的发生,并详细分析了如何定位引发该等待事件的对象及锁定双方。

Oracle单实例情况下的library cache pin的问题模拟与问题分析

参考自:


WAITEVENT: "library cache pin" Reference Note (文档 ID 34579.1)
How to Find the Blocker of the 'library cache pin' in a RAC environment? (文档 ID 780514.1)

 

本机环境:Oracle 10.2.0.5 x86-64bit for RHEL5.8 x86-64bit

 

第一个session:

[oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Fri Jun 12 17:27:28 2015

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area  281018368 bytes
Fixed Size                  2095672 bytes
Variable Size              96470472 bytes
Database Buffers          176160768 bytes
Redo Buffers                6291456 bytes
Database mounted.
Database opened.

SQL> create user lc0019999 identified by aaaaaa;

User created.

SQL> grant dba to lc0019999;

Grant succeeded.

SQL> create user lc0029999 identified by aaaaaa;

User created.

SQL> grant dba to lc0029999;

Grant succeeded.

SQL> create user lc0039999 identified by aaaaaa;

User created.

SQL> grant dba to lc0039999;

Grant succeeded.

SQL> conn lc0019999/aaaaaa
Connected.
SQL> show user
USER is "LC0019999"

SQL> select * from v$mystat where rownum<2;

       SID STATISTIC#      VALUE
---------- ---------- ----------
       159          0          1

SQL> Create or replace procedure dummy is
  2   begin
  3   null;
  4   end;
  5   /

Procedure created.


SQL> Begin
  2   Dummy;
  3   Dbms_lock.sleep(1000);
  4   End;
  5   /
------------>一直sleep着



以lc0029999登陆新开的一个session

[oracle@localhost ~]$ sqlplus lc0029999/aaaaaa

SQL*Plus: Release 10.2.0.5.0 - Production on Fri Jun 12 17:34:04 2015

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select * from v$mystat where rownum<2;

       SID STATISTIC#      VALUE
---------- ---------- ----------
       158          0          1

SQL> 
SQL> alter procedure lc0019999.dummy compile;

------------>一直hang着

 


 

以sys用户新开一个session

[oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Fri Jun 12 17:31:33 2015

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> set line 200
SQL> select sid, serial#,event from v$session where event like '%library cache pin%';

       SID    SERIAL# EVENT
---------- ---------- ----------------------------------------------------------------
       158         28 library cache pin

SQL> select sid, serial#,p1raw,event from v$session where event like '%library cache pin%';

       SID    SERIAL# P1RAW            EVENT
---------- ---------- ---------------- --------------------------------------------------
       158         28 000000006BFF19B0 library cache pin

SQL> col owner for a30
SQL> col object for a30
SQL> SELECT kglnaown "Owner", kglnaobj "Object"
  2  FROM x$kglob
  3  WHERE kglhdadr='000000006BFF19B0'---->上面查出的P1RAW值。
  4  ;                                ---->该语句是查询出这个等待事件发生在哪个object上。

Owner                          Object
------------------------------ ------------------------------
LC0019999                      DUMMY

SQL> 
SQL> SELECT s.sid, kglpnmod "Mode", kglpnreq "Req"
  2      FROM x$kglpn p, v$session s
  3     WHERE p.kglpnuse=s.saddr
  4       AND kglpnhdl='000000006BFF19B0';---->该语句是查询出这个等待事件的等待者sid(REQ>0)和持有者sid(Mode>0)

       SID       Mode        Req
---------- ---------- ----------
       158          0          3
       159          2          0

SQL> 
---补充:如下文字来源于:
<blockquote><strong><code>Mode</code></strong><span> </span>is the mode in which the pin is wanted. This is a number thus:<ul><li>2 - Share mode</li><li>3 - Exclusive mode</li></ul></blockquote>
 
 
 
如下摘自:WAITEVENT: "library cache pin" Reference Note (文档 ID 34579.1)
 An X request (3) will be blocked by any pins held S mode (2) on the object.
 An S request (2) will be blocked by any X mode (3) pin held, or may queue behind some other X request.


 

内容概要:本文详细介绍了“秒杀商城”微服务架构的设计实战全过程,涵盖系统从需求分析、服务拆分、技术选型到核心功能开发、分布式事务处理、容器化部署及监控链路追踪的完整流程。重点解决了高并发场景下的超卖问题,采用Redis预减库存、消息队列削峰、数据库乐观锁等手段保障数据一致性,并通过Nacos实现服务注册发现配置管理,利用Seata处理跨服务分布式事务,结合RabbitMQ实现异步下单,提升系统吞吐能力。同时,项目支持Docker Compose快速部署和Kubernetes生产级编排,集成Sleuth+Zipkin链路追踪Prometheus+Grafana监控体系,构建可观测性强的微服务系统。; 适合人群:具备Java基础和Spring Boot开发经验,熟悉微服务基本概念的中高级研发人员,尤其是希望深入理解高并发系统设计、分布式事务、服务治理等核心技术的开发者;适合工作2-5年、有志于转型微服务或提升架构能力的工程师; 使用场景及目标:①学习如何基于Spring Cloud Alibaba构建完整的微服务项目;②掌握秒杀场景下高并发、超卖控制、异步化、削峰填谷等关键技术方案;③实践分布式事务(Seata)、服务熔断降级、链路追踪、统一配置中心等企业级中间件的应用;④完成从本地开发到容器化部署的全流程落地; 阅读建议:建议按照文档提供的七个阶段循序渐进地动手实践,重点关注秒杀流程设计、服务间通信机制、分布式事务实现和系统性能优化部分,结合代码调试监控工具深入理解各组件协作原理,真正掌握高并发微服务系统的构建能力。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值