Shulou(Shulou.com)05/31 Report--

What are the relevant details of v$sga and v$sgainfo? for this question, this article introduces the corresponding analysis and solutions in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

09:20:47 sys@cgidb1 (cgidb1) > select * from v$sga

NAME VALUE

Fixed Size 2284104 size = > fixed size, such as the running code of oracle software

Redo Buffers 12124160

Database Buffers 50331648

Variable Size 8489338296

09:20:53 sys@cgidb1 (cgidb1) > select * from v$sgainfo

NAME BYTES RES

Fixed SGA Size 2284104 No

Redo Buffers 12124160 No

Buffer Cache Size 50331648 Yes

Shared Pool Size 973078528 Yes

Large Pool Size 0 Yes

Java Pool Size 16777216 Yes

Streams Pool Size 0 Yes

Shared IO Pool Size 0 Yes

Granule Size 16777216 No = = > shared pool granularity is 16m, where redo buffers and fixed sga size are inconsistent.

Maximum SGA Size 8554078208 No

Startup overhead in Shared Pool 701807000 No = = > cost of starting a shared pool

Free SGA Memory Available 7499415552

As above, you can see the following formula:

Maximum SGA Size = Variable Size+Database Buffers+Redo Buffers+Fixed Size

Variable Size=Free SGA Memory Available+Shared Pool Size+Large Pool Size+Java Pool Size+Streams Pool Size+Shared IO Pool Size

If memory_target=0 and sga_target=0, manual sga management, specifying the sga component size is a fixed size. For example, shared_pool_size=928M (a multiple of 16m), the component has always been 928m, no increase, no decrease.

Automatic memory management or automatic sga management when specifying the sga component size is the minimum size. For example, shared_pool_size=928M (a multiple of 16m), the minimum size of the component is 928m.

You can view a component up to the maximum and minimum values and current values since the instance was started in the following view.

10:27:53 sys@cgidb1 (cgidb1) > select COMPONENT,CURRENT_SIZE,MIN_SIZE,MAX_SIZE from V$SGA_DYNAMIC_COMPONENTS

COMPONENT CURRENT_SIZE MIN_SIZE MAX_SIZE

-

Shared pool 973078528 973078528 973078528

Java pool 16777216 16777216 16777216

DEFAULT buffer cache 50331648 50331648 50331648

In addition, alter system set shared pool=928M, this sql only modifies the dynamic memory of the current instance and is not written into spfile or pfile.

You can adjust instances and objects through the sid and scope parameters.

This is the end of the answers to the relevant questions about v$sga and v$sgainfo. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.