Oracle 参数shared_pool_size
shared_pool随着申请,一直尽量地长,长到占SGA的50%的时候,就不再长,然后由于碎片而报ORA-04031错误
环境:
idle> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
ASSM下
该参数的大小是shared pool的最小值,分配的值不能低于该值
如果超过这个值,Memory advisor会在sga_target的范围内自动调整
idle> select component, current_size,min_size,max_size,user_specified_size from v$sga_dynamic_components where component='shared pool';
COMPONENT CURRENT_SIZE MIN_SIZE MAX_SIZE USER_SPECIFIED_SIZE
------------------------- ------------ ---------- ---------- -------------------
shared pool 192937984 192937984 0 96468992
idle> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 92M
idle> select 92*1024*1024 from dual;
92*1024*1024
------------
96468992
但是,有些人建议,只要不是用来玩的库,都建议使用手动管理
shared_pool随着申请,一直尽量地长,,长到占SGA的50%的时候,就不再长,然后由于碎片而报ORA-04031错误
放养易失控,圈养不健康,Oracle提供的自动功能永远不会是最优化选择
如果SGA采用ASSM,对于事务繁忙的系统,shared_pool会不断长,到时候报ora-04031
案例1:
曾经一个运营商的库,sga_target 15G,不断报ora-04031,此时共享池到7.5G+了。
改成手动管理后,1g shared_pool,几年没报过错
案例2:
我手里有一个系统 10g on Linux ,shared_pool 从 800m 调到 1G,拼命报4031
为了不放弃自动调整SGA这个特性
我把db_cache_size调大,硬是把 shared_pool可增长的空间给吃掉就好
确实,设置db_cache_size即可解决shared_pool占用过多的问题
或者,您也可以:
设置这两个参数也行
shared_pool_reserved_size
_shared_pool_reserved_min_alloc:最小改到4100,不能任意小
idle> select a.ksppinm name,b.ksppstvl value,a.ksppdesc description
from x$ksppi a,x$ksppcv b
where a.indx = b.indx and
a.ksppinm like '%_shared_pool_reserved_min_alloc%';
NAME VALUE DESCRIPTION
-------------------------------- ---------- --------------------------------------------------
_shared_pool_reserved_min_alloc 4400 minimum allocation size in bytes for reserved area
of shared pool
附上OCP相关考题:

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

InnoDBBufferPool reduces disk I/O by caching data and indexing pages, improving database performance. Its working principle includes: 1. Data reading: Read data from BufferPool; 2. Data writing: After modifying the data, write to BufferPool and refresh it to disk regularly; 3. Cache management: Use the LRU algorithm to manage cache pages; 4. Reading mechanism: Load adjacent data pages in advance. By sizing the BufferPool and using multiple instances, database performance can be optimized.

MySQL efficiently manages structured data through table structure and SQL query, and implements inter-table relationships through foreign keys. 1. Define the data format and type when creating a table. 2. Use foreign keys to establish relationships between tables. 3. Improve performance through indexing and query optimization. 4. Regularly backup and monitor databases to ensure data security and performance optimization.
