Find Oracle Error Code Ora- and Pl/SQL Tips and Tricks

For you Oracle Developer, Oracle Programmer and Oracle Professional, should be familiar with this Oracle Error Code Ora-XXXXX and Oracle Error Messages. This Oracle Error Code and Oracle error messages basically generated by Oracle database. The prefix “ORA-” shows that the message was generated by Oracle products. Every oracle error code or messages contains the message statement, a brief explanation of the probable causes, and a recommended action that you can do.

On this OraFind.com you can find the Oracle Error Code or Oracle Error Messages that you got. It is based on Oracle database error messages (Oracle 11g release 1 and some of it Oracle 8i). Please use this information only for personal, informational and non-commercial purposes. If you still don’t have any solution for your problem, you can leave your comment in every Error Code or Error Message that you find at OraFind.com, or for more detailed information please contact Oracle Support Services.

Popularity: 100% [?]

Share This

Cause : MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set
Action : Do not set MEMORY_TARGET or MAX_MEMORY_TARGET if LOCK_SGA is set to TRUE.

Popularity: 37% [?]

Share This

Cause : Attempted to shrink MEMORY_TARGET to the specified value but did not succeed because the PGA and SGA components could not be shrunk.
Action : Do not set MEMORY_TARGET to a value below the current value without first shrinking the individual memory components.

Popularity: 31% [?]

Share This

Cause : The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
Action : Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.

Popularity: 41% [?]

Share This

Cause : The parameter was larger than MEMORY_TARGET.
Action : Set the parameter to a lower value than MEMORY_TARGET.

Popularity: 29% [?]

Share This

Cause : The parameter was larger than MEMORY_MAX_TARGET.
Action : Set the parameter to a lower value than MEMORY_MAX_TARGET.

Popularity: 31% [?]

Share This

Cause : MEMORY_TARGET parameter was not supported on this system as shmfs was disabled.
Action : Refer to documentation for a list of supported systems.

Popularity: 28% [?]

Share This

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

Share This

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

Share This

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

Share This