1.
SGA_MAX_SIZE; it is still effective after the restart must need to add scope = spfile; (not to exceed physical memory value)
SQL> alter system set sga_max_size=500M scope=spfile; System altered.
sga_target can take effect immediately; you do not specify scope = spfile can.
SQL> alter system set sga_target=500M; System altered.
sga_target can not exceed the value of sga_max_size, otherwise an error
show parameter target; View
SQL> show parameter target; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ 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 0 memory_target big integer 0 parallel_servers_target integer 32 pga_aggregate_target big integer 252M sga_target big integer 760M SQL> show parameter memory;
When sga_target because the value is too large, causing the database to get up, you need to modify the parameters under spfile or pfile.
SQL> alter system set sga_max_size=20G scope=spfile; System altered. SQL> alter system set sga_target=20G; alter system set sga_target=20G * ERROR at line 1: ORA-02097: parameter cannot be modified because specified value is invalid ORA-00823: Specified value of sga_target greater than sga_max_size
The best forced to close at the library; shutdown abort
Find the location spfile view with strings
strings spfileorcl.ora # View strings spfileorcl.ora > /tmp/dbs.ora # spfile will be exported to / under TEM
/ TEM temporary directory
Then open vi /tem/dbs.ora start modifying, modify the document to ensure that it is not wrong format (data in one line, do not wrap)
After editing startup pfile = '/ tem / dbs.ora' open
Then you can open the file specified as spfile