Skip to main content

Wait Events - Analysis

Log Buffer Space

This wait occurs because you are writing Log Buffers fater than LGWR can write to the redo log files.

Log Switches are very slow

Solution

1. Increase log buffer;
2. Increase Log file size;
3. faster disk for redo logs

Logfile Switch

All commit requests are waiting for logfile switch (archiving needed) OR logfile switch (checkpoint incomplete)

Cause

1. Ensure that archive disk is not full or slow

2. DBWR may be too slow due to I/O

3. Even though a logfile has been archived, it's contents still need to be
written to disk via a checkpoint before it can be used again. This insures
that instance recovery is possible (you would have to do media recovery
after shutdown abort in some cases if this was not so).

4. So, what is happening is that your disks are not keeping up with the
checkpoint volume. Until the checkpoints can complete, your database will
just stall, waiting.

Solution

1. You may need to add more larger redo logs

2. Need to add DBWR is there is probs with DBWR

Log File Sync

When a user session commits, the session's redo information
needs to be flushed (FROM MEMORY) to the redo logfile (TO DISK).
The session issuing the commit will wait on the log file sync event.

Solution

1. Where possible reduce the commit frequency. Eg: Commit at batch intervals

2. Speed up redo writing (Eg: Do NOT use RAID 5, use fast disks etc..)

3. Tune LGWR to get good throughput to disk . eg: Do not put redo logs on RAID

Free Buffer

This indicates your system is waiting for a buffer in memory, because none is currently available. Waits in this category may indicate that you need to increase the DB_BUFFER_CACHE, if all your SQL is tuned. Free buffer waits could also indicate that unselective SQL is causing data to flood the buffer cache with index blocks

Solution

1. Need to tune the query

2. Need to accelerate more checkpoint

3. Using more DBWR process or incresasing No. of physical disks

DB file scattered read

Indicate many full table scan

1. Tune the code

2. cache small tables

DB file sequential read

Indicates many Index Scan

1. Tune the code (especially joins)

2. Check to ensure index scans are necessary

Buffer Busy - Segment Header Segment Header : Add freelist or freelist group

Buffer Busy Waits

Buffer Busy - Data Block Data Block : separate hot data; use reverse key indexes; smaller block
Data Block : increase initrans and or maxtrans
Buffer Busy - UNDO Header UNDO Header : add rollback segments or areas

Buffer Busy - UNDO Block UNDO Block : commit more; larger rollback segments area
Labels:

Comments

Post a Comment

Popular posts from this blog

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

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's replicated, what's not?

Logged operations are replicated. These include, but are not limited to: DDL DML Create/alter table space Create/alter storage group Create/alter buffer pool XML data. Logged LOBs Not logged operations are not replicated. These include, but are not limited to: Database configuration parameters (this allows primary and standby databases to be configured differently). "Not logged initially" tables Not logged LOBs UDF (User Defined Function) libraries. UDF DDL is replicated. But the libraries used by UDF (such as C or Java libraries)  are not replicated, because they are not stored in the database. Users must manually copy the libraries to the standby. Note: You can use database configuration parameter  BLOCKNONLOGGED  to block not logged operations on the primary.
Post a Comment
Read more