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

I encountered an error while resizing sga today.

SQL > alter system set sga_target=600 scope=both;alter system set sga_target=600 scope=both*ERROR at line 1:ORA-02097: parameter cannot be modified because specified value is invalidORA-00827: could not shrink sga_target to specified value

First, take a look at the database-related configuration.

SQL > show parameter sgaNAME TYPE VALUE-- lock_sga Boolean FALSEpre_page_sga boolean FALSEsga_max_size big integer 600Msga_target big integer 600MSQL > show parameter memoryNAME TYPE VALUE-- -hi_shared_memory_address integer 0memory_max_target big integer 0memory_target big integer 0shared_memory_address integer 0

Obviously, we can see that this is an oracle under asmm. Can't we adjust it because of dynamic or static relationship, and then we do the following experiments?

SQL > alter system set sga_target=700 scope=spfile;System altered

It turns out that it can only be modified in spfile and take effect after restart, but then I continued to do the experiment and found a very interesting thing.

SQL > alter system set sga_target=400M scope=both;System altered.

This is why, why this sga can now be used in both, access to the document found that an original 10g before the size of the sga_target can not be adjusted, but after the emergence of a parameter sga_max_size, this parameter so that sga_target can really adjust itself, as long as below the sga_max_size, all sga_target can be static or dynamic automatic adjustment.

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.