[/table] |
|
|
MEMORY_MAX_TARGET--MEMORY_TARGET |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SQL> show parameters target |
|
|
---------------------------------------------------------- ------------------------------ |
|
archive_lag_target integer 0 |
|
db_flashback_retention_target integer 1440 |
|
fast_start_io_target integer 0 |
|
fast_start_mttr_target integer 0 |
|
memory_max_target big integer 1216M |
|
memory_target big integer 1216M |
|
pga_aggregate_target big integer 0 |
|
|
|
|
(Automatic Shared Memory Management, ASMM) |
|
|
引入的管理方式,要使用这种方式,需要设置初始化参数 |
|
|
SQL> alter system set sga_target=1024mscope=both; |
|
alter system set sga_target=1024m scope=both |
|
|
|
ORA-02097: parameter cannot be modified becausespecified value is invalid |
|
ORA-00839: SGA_TARGET cannot be modified to thespecified value |
|
SQL> alter system set memory_target=0scope=both; |
|
|
SQL> alter system set sga_target=1024mscope=both; |
|
|
|
这两个参数的修改是有严格顺序的,如果不遵守倒也没问题 |
|
|
|
|
这个又更加原始了一些。因为原始,所以新的初始化参数 |
|
|
|
|
MANUAL .(Thanks vongates) |
|
|
|
|
WORKAREA_SIZE_POLICY = manual , |
相关的参数。估计现在没有人干这个吃力不讨好的事情了。这个模式大可以忽略。 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
,则这两个参数将各自被分配为最小值最为它们的目标值。 |
|
Memory_Target =SGA_TARGET+PGA_AGGREGATE_TARGET |
|
|
|
=memory_target-sga_target |
|
|
=memory_target-pga_aggregate_target |
|
|
将根据数据库运行状况进行分配大小。但在数据库启动是会有一个固定比例来分配: |
|
sga_target =memory_target *60% |
|
pga_aggregate_target=memory_target *40% |
|
|
|
|
|
shared pool,buffercache,redo log buffer,java pool,larger pool |
|
|
|
中的各组件大小都要明确设定,不能自动调整各组建大小。 |
|
styleq�'n-���0pt;font-family:"Courier New";color:#2B91AF;mso-font-kerning:0pt'> |
2. public String regularExpression( 3. @PathVariable String textualPart, 4. @PathVariable String numericPart){ 5. 6. System.out.println("Textual part: " + textualPart + 7. ", numeric part: " + numericPart); 8. return "someResult"; 9. } |
|
|
[table=100%,white]比如如下的 |