Oracle 11g Error Codes and Solution Suggestions from ORA-13900 to ORA-14000
- RA-13900: missing or invalid parameter string
- Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.
- Action: Specify a valid value for this parameter.
- ORA-13901: Object string was not found.
- Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.
- Action: Specify a valid object name.
- ORA-13902: The specified file string is not a data file.
- Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file.
- Action: Specify a valid data file name.
- ORA-13903: Invalid combination of string threshold value and operator.
- Cause: A non-positive number was used for “Blocked User Session Count” metrics while operator contains equal.
- Action: Use a positive number for the threshold value or use “greater than” operator.
- ORA-13904: The file has been dropped and recreated during the procedure call.
- Cause: The file on which threshold is specified was dropped and recreated during the procedure call.
- Action: Retry this operation.
- ORA-13905: Critical or warning threshold have incorrect values
- Cause: The tablespace threshold values can be in the range 0 to 100 only.
- Action: Check the threshold values
- ORA-13906: The tablespace is not of the right type.
- Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.
- Action: Check the tablespace type and reissue the command.
- ORA-13907: Threshold value is invalid.
- Cause: An attempt was made to specify an invalid value for critical or warning thresholds.
- Action: Use non-negative integers only for threshold values.
- ORA-13908: Invalid combination of metrics id and object type parameters.
- Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters.
- Action: Specify a valid combination of metrics id and object type parameters.
- ORA-13909: Invalid combination of threshold value and operator.
- Cause: An attempt was made to specify an invalid combination of threshold value and operator.
- Action: Check the operator and threshold values and reissue statement.
- ORA-13910: Parameter string cannot be NULL.
- Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter.
- Action: Specify a valid value for this parameter.
- ORA-13911: Threshold not found
- Cause: The threshold did not exist with the specified threshold key.
- Action: No action required.
- ORA-13912: Critical threshold value is less than warning threshold value.
- Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value.
- Action: Check the threshold values and reissue the statement.
- ORA-13913: The threshold cannot be set when SYSAUX is offline.
- Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.
- Action: Call SET_THRESHOLD procedure when SYSAUX is online.
- ORA-13914: Threshold notification failed.
- Cause: An error occurred when sending notification for this threshold.
- Action: Make sure you have enough space on SYSAUX tablespace and retry this operation.
- ORA-13915: Critical byte based free space threshold value is greater than warning threshold value.
- Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value.
- Action: Check the threshold values and reissue the statement.
- ORA-13916: Invalid value “string” specified for parameter “string“
- Cause: An invalid value was specified for the the given parameter.
- Action: Correct the value being specified for the parameter.
- ORA-13917: Posting system alert with reason_id string failed with code [string] [string]
- Cause: Connection to the database is dead, or invalid parameter to alert routine.
- Action: If this condition repeats, please contact Oracle Support.
- ORA-13918: Updating system alert with reason_id string failed; previous alert not found
- Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.
- Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support.
- ORA-13919: Cannot specify values for parameter “string” and for parameter “string“
- Cause: Can only specify a value for one or the other.
- Action: Pass just one of the parameters.
- ORA-13920: Threshold cannot be set when database is in read-only mode.
- Cause: SET_THRESHOLD procedure was called when database was open in read-only mode.
- Action: Call SET_THRESHOLD procedure when database is open in read/write mode.
- ORA-13951: MMON sub-action time limit exceeded
- Cause: MMON sub-action did not complete within the system specified time frame.
- Action: None
- ORA-13970: Invalid name of “string” given
- Cause: Passed an invalid component, report, or transformation name to the framework. Names must be alphanumeric and can contain the underscore (_) character.
- Action: Try again with a valid name
- ORA-13971: string “string” unknown
- Cause: Passed an unknown component, report, or transformation to the framework.
- Action: Give a different name
- ORA-13972: string “string” unknown for string “string“
- Cause: An object with the first name is unknown within the naming scope of the second name
- Action: Change the parameters passed in or register the proper object
- ORA-13973: string unknown for string “string“
- Cause: An object is unknown within the given naming scope
- Action: Change the parameters passed in or register the proper object
- ORA-13974: string with name “string” already exists
- Cause: An object with the given name already exists
- Action: Give a different name
- ORA-13975: string with name “string” already exists for string “string“
- Cause: An object with the first name already exists within the naming scope of the second name
- Action: Give a different name
- ORA-13976: Improperly-formed report tag
- Cause: The top-level report tag was not built properly
- Action: Make sure that the report tag is built using the common tag library function
- ORA-13977: Invalid content type
- Cause: An invalid content type was passed to the register format API
- Action: Correct your code to use the values in dbmsrep.sql
- ORA-13978: Invalid reference string parameter or value
- Cause: An invalid parameter/value was passed to a dbms_report API
- Action: Ensure that the parameter names and values are alphanumeric.
- ORA-13979: Filename too long
- Cause: An invalid file name was passed to STORE_FILE
- Action: Ensure that the filename is less than 500 bytes
- ORA-13980: Invalid file URL
- Cause: A URL with invalid syntax was provided, either directly to the function or via an XML IMPORT or INCLUDE.
- Action: Check the URL.
- ORA-13981: Invalid file URL or path prefix
- Cause: Either a URL or path prefix with invalid syntax was provided.
- Action: Check the URL
- ORA-13982: Could not find file at URL provided
- Cause: The file requested could not be found in the given location.
- Action: Check the URL provided.
- ORA-13983: Missing <body> tag from HTML
- Cause: An HTML document was passed to the function missing its <body> tag.
- Action: Check the HTML source.
- ORA-13984: Invalid reference string
- Cause: The given reference string could not be parsed.
- Action: Check the reference string syntax.
- ORA-13985: Invalid URL provided to servlet
- Cause: An invalid URL was provided to the servlet.
- Action: Check the URL.
- ORA-13986: Error \string received from XPath engine
- Cause: An error was received from the xpath library during an xpath operation.
- Action: Check xmlerr.h to understand the cause of the error.
- ORA-13987: Invalid input to build common <string> tag
- Cause: Invalid input was given when attempting to build a common tag.
- Action: Check the function input to make sure all necessary information is given.
- ORA-13988: Invalid input given to variable argument list report function.
- Cause: An invalid parameter was provided to one of the report framework variable argument list functions.
- Action: Check the function input and try again.
- ORA-13989: Invalid input given to structured argument list report function.
- Cause: An invalid parameter was provided to one of the report framework structured argument list functions.
- Action: Check the function input and try again.
- ORA-13990: Invalid tag name given to common tag callout function.
- Cause: This is an internal Server Manageability Error
- Action: Contact Oracle Support Services
- ORA-14000: only one LOCAL clause may be specified
- Cause: CREATE INDEX statement contained more than one LOCAL clause
- Action: Specify LOCAL option at most once