ORA-00091: LARGE_POOL_SIZE must be at least string
Cause: The value of LARGE_POOL_SIZE is below the minimum size.
Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00091: LARGE_POOL_SIZE must be at least string
Cause: The value of LARGE_POOL_SIZE is below the minimum size.
Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00090: failed to allocate memory for cluster database ORADEBUG command
Cause: Could not allocate memory needed to execute cluster database oradebug.
Action: Reissue the command on each instance with single-instance oradebug.
ORA-00089: invalid instance number in ORADEBUG command
Cause: An invalid instance number was specified in a cluster database ORADEBUG command.
Action: Reissue the command with valid instance numbers
ORA-00088: command cannot be executed by shared server
Cause: Debug command issued on shared server.
Action: Reissue the command using a dedicated server.
ORA-00087: command cannot be executed on remote instance
Cause: Cluster database command issued for non cluster database ORADEBUG command.
Action: Issue the command without the cluster database syntax.
ORA-00086: user call does not exist
Cause: An invalid attempt was made to dump the user call heap.
Action: Wait until the process starts a call.
ORA-00085: current call does not exist
Cause: An invalid attempt was made to dump the current call heap.
Action: Wait until the process starts a call.
ORA-00084: global area must be PGA, SGA, or UGA
Cause: An attempt was made to dump an invalid global area.
Action: Specify either PGA, SGA, or UGA.
ORA-00083: warning: possibly corrupt SGA mapped
Cause: Even though there may be SGA corruptions, the SGA was mapped.
Action: Use the DUMPSGA command to dump the SGA.
ORA-00082: memory size of string is not in valid set of [1], [2], [4] stringstringstringstringstring
Cause: An invalid length was specified for the POKE command.
Action: Use a valid length (either 1, 2, 4, or possibly 8).