Shulou(Shulou.com)06/01 Report--

ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings

ORA-00842: DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or MEMORY_TARGET

Because when I was doing the experiment, in order to try the manual setting of the SGA of the earlier version of ORACLE, I tried to modify the parameter value of DB_BLOCK_BUFFERS, and the above two errors occurred after restarting the database.

The error is clearly that the DB_BLOCK_BUFFERS parameter setting is conflicting with the SGA_TARGET or MEMORY_TARGET parameter setting.

When doing this experiment, it is best to back up the spfile. Of course, there is still a way to solve the problem without backup:

SQL > show parameter sga_target;NAME TYPE VALUE- sga_target big integer 0SQL > show parameter memory_target NAME TYPE VALUE--memory_target big integer 6400m

When I see here, I set zero two parameter values.

SQL > alter system set sga_target=0 scope=both;System altered.SQL > alter system set memory_target=0 scope=both;System altered.SQL > alter system set db_block_buffers=249856 scope=spfile;System altered.

When I changed the db_block_buffers parameter value, I found that the above error occurred. Because this parameter was used before 9i, it was deprecated after 9i. If you make this setting, it will conflict with the current parameters, resulting in an error.

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.