WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK

最新推荐文章于 2024-03-04 10:33:07 发布

iteye_20025

最新推荐文章于 2024-03-04 10:33:07 发布

阅读量304

点赞数

文章标签：数据库

本文详细分析了Oracle数据库实例挂起问题，原因在于等待过长的行缓存排队锁定，并提供了通过调整Share pool_size参数来解决的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

现象：

1.数据库ALERT持续报如下错误，一段时间后数据库实例Hang住无法使用
Wed Oct 26 09:10:52 2011
>>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=604
System State dumped to trace file /oracle/product/10.2.0/admin/jxsoh/udump/jxsoh1_ora_1486930.trc

2.检查TRC文件
/oracle/product/10.2.0/admin/jxsoh/udump/jxsoh1_ora_1486930.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /oracle/product/10.2.0/db_1
System name:AIX
Node name:sohrac1
Release:3
Version:5
Machine:00C71E704C00
Instance name: jxsoh1
Redo thread mounted by this instance: 1
Oracle process number: 604
Unix process pid: 1486930, image: oracle@sohrac1

*** 2011-10-26 09:10:52.514
*** SERVICE NAME:(SYS$USERS) 2011-10-26 09:10:52.512
*** SESSION ID:(489.4) 2011-10-26 09:10:52.512
>>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! <<<
row cache enqueue: session: 70000018f4892c0, mode: N, request: S
===================================================
SYSTEM STATE
------------
System global information:
processes: base 700000189374220, size 1000, cleanup 700000189395d30
allocation: free sessions 70000018a428e08, free calls 0
control alloc errors: 0 (process), 0 (session), 0 (call)
PMON latch cleanup depth: 0
seconds since PMON's last scan for dead processes: 26
……

分析：
此为Sharepool抖动

解决办法：
alter system set share_pool_size=XXg scope=both;