Archive for March, 2008

ORA-00837: Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET

Friday, March 28th, 2008

Cause : The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET.
Action : Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET.

Popularity: 13% [?]

ORA-00832: no streams pool created and cannot automatically create one

Friday, March 28th, 2008

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% [?]

ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled

Friday, March 28th, 2008

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.

Popularity: 3% [?]

ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings

Friday, March 28th, 2008

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% [?]

ORA-00827: could not shrink sga_target to specified value

Friday, March 28th, 2008

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: 12% [?]

ORA-00826: cannot set SGA_TARGET or MEMORY_TARGET for an ASM instance

Friday, March 28th, 2008

Cause : SGA_TARGET or MEMORY_TARGET set for an ASM instance.
Action : Do not set SGA_TARGET or MEMORY_TARGET.

Popularity: 8% [?]

ORA-00825: cannot set DB_BLOCK_BUFFERS if SGA_TARGET or MEMORY_TARGET is set

Friday, March 28th, 2008

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: 15% [?]

ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information

Friday, March 28th, 2008

Cause : Unable to set SGA_TARGET or MEMORY_TARGET due to current parameter settings.
Action : See alert log for more information.

Popularity: 13% [?]

ORA-00823: Specified value of sga_target greater than sga_max_size

Friday, March 28th, 2008

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: 17% [?]

ORA-00822: MMAN process terminated with error

Friday, March 28th, 2008

Cause: The Memory Management process died.
Action: Warm start instance

Popularity: 11% [?]

Close
E-mail It