Skip to main content

High 'cursor: pin S wait on X' and/or 'library cache lock' Waits.

Symptoms:

A spike in "cursor: pin S wait on X" or "library cache lock" waits may be seen. This is more likely to be seen in an OLTP environment where both shared pool and buffer cache are in demand. The problem will happen randomly and intermittently.

Cause:

Alternating frequent shrink and grow of the buffer cache and shared pool may be seen with automatic memory management enabled causing various waits in sessions and concurrency issues. The frequent resize of the shared pool and buffer cache is causing contention so that waits on "cursor: pin S wait on X" and "library cache lock" may be seen.

Solution:

Option 1: Disable Automatic memory management by setting SGA_TARGET=0.

Option 2:Following parameter cna be set dynamically:
alter system set "_memory_broker_stat_interval"=999;

This will increase the time between resize to at least 999 seconds and thereby reducing the number of resize operations.

"_memory_broker_stat_interval" is in seconds and is by default 30 seconds.
You can set _memory_broker_stat_interval to a larger value.
This should be done on all RAC nodes.

Option 3:

Apply patch:
For 10.2.0.4 apply Patch:7189722
For 11g apply Patch:9267837

The bug fix is included in 11.2.0.2 patchset
Labels:

Comments

Post a Comment

Popular posts from this blog

Data Wrangling vs EDA

  Aspect Data Wrangling (Data Preprocessing) Exploratory Data Analysis (EDA) Objective Prepare raw data for modeling by cleaning, transforming, and formatting it appropriately. Explore and understand the data to gain insights, identify patterns, and make decisions on data handling and modeling. Order Typically performed as a preliminary step before EDA. Usually conducted after data wrangling to further investigate data characteristics. Data Handling Focuses on data cleaning, filling missing values, encoding categorical variables, and scaling features. Involves data visualization, statistical analysis, and summary statistics to uncover patterns, relationships, and anomalies. Techniques Techniques include imputation, outlier detection, feature scaling, and one-hot encoding. Techniques include histograms, scatter plots, box plots, correlation matrices, and descriptive statistics. Data Transformation Involves structural changes to the dataset, such as feature engineering, data normaliz...
Post a Comment
Read more

What is Tensor Parallelism and relationship between Buffer and GPU

  Tensor Parallelism in GPU Tensor parallelism is a technique used to distribute the computation of large tensor operations across multiple GPUs or multiple cores within a GPU .   It is an essential method for improving the performance and scalability of deep learning models, particularly when dealing with very large models that cannot fit into the memory of a single GPU. Key Concepts Tensor Operations : Tensors are multidimensional arrays used extensively in deep learning. Common tensor operations include matrix multiplication, convolution, and element-wise operations. Parallelism : Parallelism involves dividing a task into smaller sub-tasks that can be executed simultaneously. This approach leverages the parallel processing capabilities of GPUs to speed up computations. How Tensor Parallelism Works Splitting Tensors : The core idea of tensor parallelism is to split large tensors into smaller chunks that can be processed in parallel. Each chunk is assigned to a different GP...
Post a Comment
Read more

Infrastructure limitations ESX Server 4 vs ESXI 5

Some limitations in ESX Server 4 may constrain the design of data centers:[28][29] • Guest system maximum RAM: 255 GB • Host system maximum RAM: 1 TB[28] • Number of hosts in a high availability cluster: 32 • Number of Primary Nodes in ESX Cluster high availability: 5 • Number of hosts in a Distributed Resource Scheduler cluster: 32 • Maximum number of processors per virtual machine: 8 • Maximum number of processors per host: 160 • Maximum number of cores per processor: 12 • Maximum number of virtual machines per host: 320 • VMFS-3 limits files to 262,144 (218) blocks, which translates to 256 GB for 1 MB block sizes (the default) or up to 2 TB for 8 MB block sizes.[30] However, on a VMFS Boot drive, it is usually very difficult to use anything other than 1 MB Block size [31]. With ESXI 5 there has been some changes to these limits[32] • Guest system maximum RAM: 1 TB • Host system maximum RAM: 2 TB • Number of hosts in a high availability cluster: 32 • Maximum number ...
Post a Comment
Read more