Welcome to the Technical Portal: ORA-00076 to ORA-00100

ORA Code Code Description Cause Action
ORA-00076 Dump string not found An attempt was made to invoke a dump that does not exist Type DUMPLIST to see the list of available dumps
ORA-00077 Dump string is not valid An attempt was made to invoke an invalid dump Try another dump
ORA-00078 Cannot dump variables by name An attempt was made to dump a variable by name on a system that does not support this feature Try the PEEK command
ORA-00079 Variable string not found An attempt was made to dump a variable that does not exist Use a valid variable name
ORA-00080 Invalid global area specified by level string An attempt was made to dump an invalid global area Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra + level> to dump global area <level> as well as <extra> bytes for every pointer; <extra> must be a multiple of 4
ORA-00081 Address range [string, string) is not readable An attempt was made to read/write an invalid memory address range Try another address or length
ORA-00082 Memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring An invalid length was specified for the POKE command Use a valid length (either 1, 2, 4, or possibly 8)
ORA-00083 Warning: possibly corrupt SGA mapped Even though there may be SGA corruptions, the SGA was mapped Use the DUMPSGA command to dump the SGA
ORA-00084 Global area must be PGA, SGA, or UGA An attempt was made to dump an invalid global area Specify either PGA, SGA, or UGA
ORA-00085 Current call does not exist An invalid attempt was made to dump the current call heap Wait until the process starts a call
ORA-00086 User call does not exist An invalid attempt was made to dump the user call heap Wait until the process starts a call
ORA-00087 Command cannot be executed on remote instance Cluster database command issued for non cluster database ORADEBUG command Issue the command without the cluster database syntax
ORA-00088 Command cannot be executed by shared server Debug command issued on shared server Reissue the command using a dedicated server
ORA-00089 Invalid instance number in ORADEBUG command An invalid instance number was specified in a cluster database ORADEBUG command Reissue the command with valid instance numbers
ORA-00090 Failed to allocate memory for cluster database ORADEBUG command Could not allocate memory needed to execute cluster database oradebug Reissue the command on each instance with single-instance oradebug
ORA-00091 LARGE_POOL_SIZE must be at least string The value of LARGE_POOL_SIZE is below the minimum size Increase the value of LARGE_POOL_SIZE past the minimum size
ORA-00092 LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC
ORA-00093 %s must be between string and string The parameter value is not in a valid range Modify the parameter value to be within the specified range
ORA-00094 %s requires an integer value The parameter value is not an integer Modify the parameter value to be an integer
ORA-00095 Message 95 not found;  product=RDBMS; facility=ORA    
ORA-00096 Invalid value string for parameter string, must be from among string The value for the initialization parameter is invalid Choose a value as indicated by the message
ORA-00097 Use of Oracle SQL feature not in SQL92 string Level Usage of Oracle's SQL extensions none
ORA-00098 Message 98 not found;  product=RDBMS; facility=ORA                 
ORA-00099 Timed out while waiting for resource, potential PDML deadlock The resource needed by the transaction was busy. The
PDML transaction could not acquire the resource within the
specified amount of time. This indicates potential deadlock
involving this PDML transaction and other transactions
currently running in the system
Specify a valid process
ORA-00100 Process "string" not found in this instance An application made reference to unknown or inaccessible data Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100

 

    Back to ORA Code Topics

 

Google