Complete Source for Oracle Error Code Ora-, Pl/Sql Tips and Tricks and Oracle Error Message Description
Cause : The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
Action : Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
Popularity: 42% [?]
Cause : The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
Action : Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low.
Popularity: 37% [?]
Cause : The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
Action : Set MEMORY_TARGET to at least the recommended value.
Popularity: 29% [?]
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.
Popularity: 9% [?]
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.
Popularity: 12% [?]
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.
Popularity: 11% [?]
Cause : SGA_TARGET or MEMORY_TARGET set for an ASM instance.
Action : Do not set SGA_TARGET or MEMORY_TARGET.
Popularity: 9% [?]
Cause : SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.
Action : Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters, and do not use DB_BLOCK_BUFFERS which is an old cache parameter.
Popularity: 16% [?]
Cause : Unable to set SGA_TARGET or MEMORY_TARGET due to current parameter settings.
Action : See alert log for more information.
Popularity: 15% [?]
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.
Popularity: 20% [?]
