ORA-00900: invalid SQL statement
Cause: The statement is not recognized as a valid SQL statement. This error can occur if the Procedural Option is not installed and a SQL statement is issued that requires this option (for example, a CREATE PROCEDURE statement). You can determine if the Procedural Option is installed by starting SQL*Plus. If the PL/SQL banner is not displayed, then the option is not installed
Action: Correct the syntax or install the Procedural Option
ORA-00845: MEMORY_TARGET not supported on this system
SQL> startup nomount;
This error occurs because you tried to use the automatic feature memory management (AMM) Oracle 11g R2. But it seems that its shared memory file system (shmfs) is not big enough. So let's look at the necessary steps to expand its shared memory file system to avoid the above error.
First of all, log in as root and check the file system:
[Root @ oracle in oracle] # df -h Filesystem Size Used Avail Use% Mounted on /Dev/mapper/vg_oracleem-lv_root 93G 19G 69g 22% / tmpfs 112K 5.9G 5.9G 1% /dev/shm /Dev/sda1 99M 485M 362M 22% /boot
So we can see that tmpfs has a 6GB in size. We can change the file system size with the following command:
[Root @ oracle in oracle] # mount -t tmpfs -o shmfs size = 12g /dev/shm
This command (re) mounts the system shmfs files. The shared memory file system must be large enough to accommodate the MEMORY_TARGET and MEMORY_MAX_TARGET values, or Oracle will report ORA-00845 error. Note that when you change something with the mount command, the changes are not permanent.
To make the change persistent, edit your /etc/ fstab to include the option specified above:
[Root @ oracle-in ~] # cat /etc/fstab [..] tmpfs / dev / shm tmpfs size = 12g 0 0 [..]
In my case, I replaced the "defaults" option with the size = 12g option. After saving the file, the changes must be permanent. Now back to Oracle. Let's see if we can start the database now ...
SQL> startup nomount ORACLE instance started
Total System Global Area 1.1758E + 10 bytes Fixed Size 2239056 bytes Variable Size 5939135920 bytes 5804916736 bytes Database Buffers Redo Buffers 12128256 bytes
ORA-00832: no streams pool created and cannot automatically create one
Cause: A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache
Action: Please set the parameter streams_pool_size or set sga_target
ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled
Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC
Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again
ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings
Cause: Unable to set shared_pool_reserved_size to specified value if sga_target set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log
Action: If possible, do not set shared_pool_reserved_size without setting shared_pool_size if sga_target set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size
ORA-00827: could not shrink sga_target to specified value
Cause: Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes
Action: Do not set sga_target to a value below the current value without first shrinking the individual SGA components
ORA-00826: cannot set sga_target for an ASM instance
Cause: sga_target set for an ASM instance
Action: Do not set sga_target
ORA-00825: cannot set db_block_buffers if sga_target set
Cause: sga_target set with db_block_buffers set
Action: Do not set sga_target or use new cache parameters and do not use db_block_buffers which is a old cache parameter
ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information
Cause: Unable to set sga_target due to current parameter settings
Action: See alert log for more information
ORA-00823: Specified value of sga_target greater than sga_max_size
Cause: The specified value of sga_target is greater than sga_max_size
Action: Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize