ITPub博客

首页 > 数据库 > Oracle > 1Z0-053 V13.02 Q518

1Z0-053 V13.02 Q518

原创 Oracle 作者:cow977 时间:2016-07-18 19:21:45 0 删除 编辑
518.The DBA has chosen to manage SGA and PGA memory separately in an OLTP database because of his unique knowledge of the application. Which of these are good starting points to use when configuring the maximum values for SGA and PGA, based on the amount of memory available on the system?
A. 20% SGA, 80% PGA
B. 25% SGA, 75% PGA
C. 50% SGA, 50% PGA
D. 75% SGA, 25% PGA
E. 80% SGA, 20% PGA
Answer: E

参考:http://docs.oracle.com/cd/E11882_01/server.112/e41573/memory.htm#PFGRF94352

Example 7-2 Initial Setting of PGA_AGGREGATE_TARGET

Assume that an Oracle database instance is configured to run on a system with 4 GB of physical memory. Part of that memory should be left for the operating system and other non-Oracle applications running on the same hardware system. You might decide to dedicate only 80% (3.2 GB) of the available memory to the Oracle database instance.

You must then divide the resulting memory between the SGA and the PGA.

  • For OLTP systems, the PGA memory typically accounts for a small fraction of the total memory available (for example, 20%), leaving 80% for the SGA.

  • For DSS systems running large, memory-intensive queries, PGA memory can typically use up to 70% of that total (up to 2.2 GB in this example).

Good initial values for the parameter PGA_AGGREGATE_TARGET might be:

  • For OLTP: PGA_AGGREGATE_TARGET = (total_mem * 80%) * 20%

  • For DSS: PGA_AGGREGATE_TARGET = (total_mem * 80%) * 50%

    where total_mem is the total amount of physical memory available on the system.

In this example, with a value of total_mem equal to 4 GB, you can initially set PGA_AGGREGATE_TARGET to 1600 MB for a DSS system and to 655 MB for an OLTP system.

来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/81227/viewspace-2122186/ ,如需转载,请注明出处,否则将追究法律责任。

上一篇: 1Z0-053 V13.02 Q480
下一篇: 1Z0-053 V13.02 Q519
请登录后发表评论 登录
全部评论

注册时间:2011-03-02

  • 博文量
    698
  • 访问量
    894416