Oracle Database Errors or Warnings from Error ORA-13913 to ORA-13970

SQLServerF1

ORA-13913: The threshold cannot be set when SYSAUXx 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

Above are list of Oracle Database Errors or Warnings from Error ORA-13913 to ORA-13970 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *