您的位置:首页 > 其它

修改Memory_max_target为0出错

2017-05-02 10:53 369 查看
SQL> connect / as sysdba

Connected.

SQL> alter system set memory_target=0;

System altered.

SQL> alter system set memory_max_target=0;

alter system set memory_max_target=0

                
*

ERROR at line 1:

ORA-02095: specified initialization parameter cannot be
modified

SQL> alter system set memory_max_target=0
scope=spfile; --

System altered.

SQL> alter system set sga_target=6G
scope=spfile;

System altered.

SQL> alter system set
pga_aggregate_target=2112M;

System altered.

SQL> alter system set shared_pool_size=0;

System altered.

SQL> shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup

ORA-00843: Parameter not taking MEMORY_MAX_TARGET into
account

ORA-00849: SGA_TARGET 6442450944 cannot be set to more than
MEMORY_MAX_TARGET 0.

SQL> startup nomount

ORA-00843: Parameter not taking MEMORY_MAX_TARGET into
account

ORA-00849: SGA_TARGET 6442450944 cannot be set to more than
MEMORY_MAX_TARGET 0.

 

解决方法:

 

 

Symptoms

When trying to set SGA_TARGET using an ALTER SYSTEM command, the
following errors are raised:

ORA-00843: Parameter not taking MEMORY_MAX_TARGET into
account

ORA-00849: SGA_TARGET 10737418240 cannot be set to more than
MEMORY_MAX_TARGET 0.


 

Changes

MEMORY_MAX_TARGET was set to 0.

Cause

The problem is caused by the MEMORY_MAX_TARGET parameter
explicitly being set to 0. In case AMM should not be used,
MEMORY_MAX_TARGET should not be set at all.

Solution

The solutions to the problem are:

create a PFILE from the SPFILE being used and remove the
MEMORY_MAX_TARGET=0 and MEMORY_TARGET=0 lines. After that, use the
modified PFILE to create a new SPFILE and start the instance with
this new setup.

should the instance be running, then use the following commands
to remove the explicit setting of MEMORY_TARGET=0 and
MEMORY_MAX_TARGET=0:

alter
system reset memory_target;

alter system reset memory_max_target;


 

 

 
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: