Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13700 to ORA-13900
- ORA-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.
Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.
Action: Specify a valid object name.
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.
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.
Cause: The file on which threshold is specified was dropped and recreated during the procedure call.
Action: Retry this operation.
Cause: The tablespace threshold values can be in the range 0 to 100 only.
Action: Check the threshold values
Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.
Action: Check the tablespace type and reissue the command.
Cause: An attempt was made to specify an invalid value for critical or warning thresholds.
Action: Use non-negative integers only for threshold values.
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.
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.
Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter.
Action: Specify a valid value for this parameter.
Cause: The threshold did not exist with the specified threshold key.
Action: No action required.
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.
Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.
Action: Call SET_THRESHOLD procedure when SYSAUX is online.
Cause: An error occurred when sending notification for this threshold.
Action: Ensure that you have enough space on SYSAUX tablespace and retry this operation.
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.
Cause: An invalid value was specified for the the given parameter.
Action: Correct the value being specified for the parameter.
Cause: Connection to the database is dead, or invalid parameter to alert routine.
Action: If this condition repeats, please contact Oracle Support.
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.
Cause: Can only specify a value for one or the other.
Action: Pass just one of the parameters.
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.
Cause: MMON sub-action did not complete within the system specified time frame.
Action: None
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
Cause: Passed an unknown component, report, or transformation to the framework.
Action: Give a different name
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
Cause: An object is unknown within the given naming scope
Action: Change the parameters passed in or register the proper object
Cause: An object with the given name already exists
Action: Give a different name
Cause: An object with the first name already exists within the naming scope of the second name
Action: Give a different name
Cause: The top-level report tag was not built properly.
Action: Ensure that the report tag is built using the common tag library function.
Cause: An invalid content type was passed to the register format API
Action: Correct your code to use the values in dbmsrep.sql
Cause: An invalid parameter/value was passed to a dbms_report API
Action: Ensure that the parameter names and values are alphanumeric.
Cause: An invalid file name was passed to STORE_FILE
Action: Ensure that the filename is less than 500 bytes
Cause: A URL with invalid syntax was provided, either directly to the function or via an XML IMPORT or INCLUDE.
Action: Check the URL.
Cause: Either a URL or path prefix with invalid syntax was provided.
Action: Check the URL
Cause: The file requested could not be found in the given location.
Action: Check the URL provided.
Cause: An HTML document was passed to the function missing its body tag.
Action: Check the HTML source.
Cause: The given reference string could not be parsed.
Action: Check the reference string syntax.
Cause: An invalid URL was provided to the servlet.
Action: Check the URL.
Cause: An error was received from the xpath library during an xpath operation.
Action: Check xmlerr.h to understand the cause of the error.
Cause: Invalid input was given when attempting to build a common tag.
Action: Check the function input to ensure that all necessary information is given.
Cause: An invalid parameter was provided to one of the report framework variable argument list functions.
Action: Check the function input and try again.
Cause: An invalid parameter was provided to one of the report framework structured argument list functions.
Action: Check the function input and try again.
Cause: An invalid tag name was provided to the report framework common tag callout function.
Action: Check the function input and try again.
Cause: This is an internal Server Manageability Error
Action: Contact Oracle Support Services
Cause: CREATE INDEX statement contained more than one LOCAL clause
Action: Specify LOCAL option at most once