| LRM-00100: internal error [number] Cause: An internal error has occurred. Action: Contact Oracle Support Services and report the error. |
| LRM-00101: unknown parameter name "string" Cause: The parameter name was misspelled. Action: Spell the parameter name correctly. |
| LRM-00102: "string" is not in the legal range for "string" Cause: The value of the parameter is not within the legal range. Action: Refer to the manual for the allowable values for this parameter. |
| LRM-00103: "string" contains an illegal integer radix for "string" Cause: An illegal integer radix specification was found. Action: Only "d", "h", "D", and "H" may be used as radix specifications. |
| LRM-00104: "string" is not a legal integer for "string" Cause: The value is not a valid integer. Action: Specify only valid integers for this parameter. |
| LRM-00105: "string" is not a legal Boolean for "string" Cause: The value is not a valid Boolean. Action: Refer to the manual for allowable Boolean values. |
| LRM-00106: out of memory Cause: The operating system has run out of memory. Action: Take action to make more memory available to the program. |
| LRM-00107: parameter name abbreviation "string" is not unique Cause: The given abbreviation was not unique. Action: Use a longer abbreviation to make the parameter name unique. |
| LRM-00108: invalid positional parameter value "string" Cause: An invalid positional parameter value has been entered. Action: Remove the invalid positional parameter. |
| LRM-00109: could not open parameter file "string" Cause: The parameter file does not exist. Action: Create an appropriate parameter file. |
| LRM-00110: syntax error at "string" Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. |
| LRM-00111: no closing quote for value "string" Cause: A quoted string was started but not finished. Action: Put a closing quote in the proper location. |
| LRM-00112: multiple values not allowed for parameter "string" Cause: An attempt was made to specify multiple values for a parameter which can take only one value. Action: Do not specify more than one value for this parameter. |
| LRM-00113: error when processing file "string" Cause: A problem occurred when processing this file. Action: Examine the additional error messages and correct the problem. |
| LRM-00114: error when processing from command line Cause: A problem occurred when processing the command line. Action: Examine the additional error messages and correct the problem. |
| LRM-00115: error when processing an environment variable Cause: A problem occurred when processing an environment variable. Action: Examine the additional error messages and correct the problem. |
| LRM-00116: syntax error at "string" following "string" Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. |
| LRM-00117: syntax error at "string" at the start of input Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. |
| LRM-00118: syntax error at "string" at the end of input Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. |
| LRM-00119: unable to obtain a valid value for "string" Cause: No valid value was obtained for this parameter. Action: Rerun the application and enter a valid value. |
| LRM-00120: "string" is not a legal Oracle number for "string" Cause: The value is not a valid Oracle number. Action: Refer to the manual for allowable Oracle number values. |
| LRM-00121: "string" is not an allowable value for "string" Cause: The value is not a legal value for this parameter. Action: Refer to the manual for allowable values. |
| LRM-00122: value "string" for "string" must be between "number" and "number" Cause: The value of the parameter is not within the legal range. Action: Specify a value that is within the legal range. |
| LRM-00123: invalid character number found in the input file Cause: A character that is invalid was found in the input file. Action: Specify an input file that contains only valid characters. |
| |
| Last updated: August 25, 2009 |
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
