Shulou(Shulou.com)06/01 Report--

Find a problem

A job reports an error, and the error message is as follows. There is no reason for the error from the error message, and the manual operation of the job is successful again. It is not clear what caused the homework error at the moment.

Message

Executed as user: NT SERVICE\ SQLSERVERAGENT. ... eration. [SQLSTATE 01003] (Message 8153) Mar 6 2019 8:09AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:10AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:17AM [SQLSTATE 01000] (Message 0) Mar 6 2019 11:17AM [SQLSTATE 01000] (Message 0) Mar 7 2019 1:03PM [SQLSTATE 01000] (Message 0) Mar 6 2019 4:06PM [SQLSTATE 01000] (Message 0) Mar 7 2019 4:07PM [SQLSTATE 01000] (Message 0) Mar 6 2019 1:40PM [SQLSTATE 01000] (Message 0) Mar 7 2019 1:36PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:02AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:06AM [SQLSTATE 01000] (Message 0) Mar 7 2019 9:47AM [SQLSTATE 01000] (Message 0) Mar 6 2019 5:38PM [SQLSTATE 01000] (Message 0) Mar 7 2019 5:34PM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:16PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:07AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:09AM [SQLSTATE 01000] (Message 0) Mar 7 2019 2:18PM [SQLSTATE 01000] (Message 0) Mar 7 2019 1:24PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:11AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:12AM [SQLSTATE 01000] (Message 0) Mar 6 2019 11:34AM [SQLSTATE 01000] (Message 0) Mar 7 2019 11:39AM [SQLSTATE 01000] (Message 0) Mar 7 2019 4:20PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:51AM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:44AM [SQLSTATE 01000] (Message 0) Mar 7 2019 7:31AM [SQLSTATE 01000] (Message 0) Mar 6 2019 10:46AM [SQLSTATE 01000] (Message 0) Mar 6 2019 10:10AM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:08AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:04AM [SQLSTATE 01000] (Message 0) Mar 7 2019 3:19PM [SQLSTATE 01000] (Message 0) Mar 6 2019 9:02AM [SQLSTATE 01000] (Message 0) Mar 7 2019 9:01AM [SQLSTATE 01000] (Message 0) Mar 7 2019 9:48AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:01AM [SQLSTATE 01000] (Message 0) Mar 6 2019 4:16PM [SQLSTATE 01000] (Message 0) Mar 6 2019 2:17PM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:31AM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:04AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:08AM [SQLSTATE 01000] (Message 0) Mar 6 2019 1:08PM [SQLSTATE 01000] (Message 0) Mar 7 2019 1:04PM [SQLSTATE 01000] (Message 0) Mar 7 2019 2:03PM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:18PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:16AM [SQLSTATE 01000] (Message 0) Mar 6 2019 2:14PM [SQLSTATE 01000] (Message 0) Mar 6 2019 4:13PM [SQLSTATE 01000] (Message 0) Mar 7 2019 4:10PM [SQLSTATE 01000] (Message 0) Mar 6 2019 9:02AM [SQLSTATE 01000] (Message 0) Mar 7 2019 2:01PM [SQLSTATE 01000] (Message 0) Mar 7 2019 7:44AM [SQLSTATE 01000] (Message 0) Mar 6 2019 5:38PM [SQLSTATE 01000] (Message 0) Mar 7 2019 5:34PM [SQLSTATE 01000] (Message 0) Mar 6 2019 5:38PM [SQLSTATE 01000] (Message 0) Mar 7 2019 5:34PM [SQLSTATE 01000] (Message 0) Mar 6 2019 2:03PM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:05PM [SQLSTATE 01000] (Message 0) Mar 7 2019 7:01PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:05AM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:47PM [SQLSTATE 01000] (Message 0) Mar 6 2019 9:16AM [SQLSTATE 01000] (Message 0) Mar 6 2019 2:18PM [SQLSTATE 01000] (Message 0) Mar 7 2019 2:18PM [SQLSTATE 01000] (Message 0) Mar 7 2019 2:36PM [SQLSTATE 01000] (Message 0) Mar 6 2019 9:20AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:32AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:13AM [SQLSTATE 01000] (Message 0) Mar 6 2019 1:31PM [SQLSTATE 01000] (Message 0) Mar 6 2019 8:06AM [SQLSTATE 01000] (Message 0) Mar 7 2019 8:07AM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:16PM [SQLSTATE 01000] (Message 0) Mar 6 2019 3:16PM [SQLSTATE 01000] (Message 0) Mar 6 2019 9:03AM [SQLSTATE 01000] (Message 0) Mar 6 2019 11:59AM [SQLSTATE 01000] (Message 0) Mar 7 2019 12:01PM [SQLSTATE 01000] (Message 0) Mar 6 2019 2:59PM [SQLSTATE 01000] (Message 0) Mar 6 2019 11:49AM [SQLSTATE 01000]. The step failed.

As shown in the screenshot above, we can see that the Sql Severity level of the error message is 13. Through the database engine error severity (Database Engine Error Severities), we can know that 13 means Indicates transaction deadlock errors. In other words, a deadlock occurs, causing the session of the job to become the victim of the deadlock. However, it is also strange that jobs fail due to deadlocks in the past. There will be prompts in Message, but in the version of this instance, SQL Server 2012 SP3 (11.0.6020.0), there is a deadlock, but there is no deadlock information. It's not clear if it's Bug or something else.

Severity level

The following table lists and describes the severity of errors caused by the SQL Server database engine.

Severity level

Description

0-9

An informational message that returns less serious status information or report errors. The database engine does not cause system errors with a severity level of 0 to 9.

ten

An informational message that returns less serious status information or report errors. For compatibility reasons, the database engine converts the severity level from 10 to 0 before returning the error message to the calling application.

11-16

Indicates errors that can be corrected by the user.

eleven

Indicates that the given object or entity does not exist.

twelve

Special severity for queries that do not use locking because of special query hints. In some cases, read operations performed by these statements can result in inconsistent data because no locks are used to guarantee consistency.

thirteen

Indicates a transaction deadlock error.

fourteen

Indicates a security-related error, such as permission denied.

fifteen

Instruct Transact-SQL? Syntax error in command.

sixteen

Indicates general errors that can be corrected by the user.

17-19

Indicates software errors that cannot be corrected by the user. Please notify the system administrator of the problem.

seventeen

The directive statement causes SQL Server? Running out of resources, such as database memory, locks, or disk space, or exceeding some of the limits set by your system administrator.

eighteen

Indicates that there is a problem in the database engine software, but the execution statement can be completed and the connection to the database engine instance can be maintained. The system administrator should be notified whenever a message with a severity level of 18 appears.

nineteen

Indicates that the non-configurable database engine limit has been exceeded and the current batch has been terminated. Error messages with a severity level of 19 or higher stop the execution of the current batch. Errors with a severity level of 19 are rare and must be corrected by your system administrator or primary support provider. When raising a message with a severity level of 19, contact your system administrator. Error messages with severity levels from 19 to 25 are written to the error log.

20-24

Indicates a system problem and is a fatal error, which means that the database engine task executing a statement or batch has stopped running. This task records information about what happened and then terminates. In most cases, the connection between the application and the database engine instance may also be terminated. If this happens, the problem may prevent the application from reconnecting.

Error messages within this scope can affect all processes accessing data in the same database and may indicate that the database or object is corrupted. Error messages with severity levels from 19 to 24 are written to the error log.

twenty

Indicates that the statement encountered a problem. Since this problem only affects the current task, the database itself may not have been corrupted.

twenty-one

Indicates that a problem has been encountered that affects all tasks in the current database, but the database itself may not be corrupted.

twenty-two

Indicates that the table or index specified in the message is corrupted due to a software or hardware problem.

Errors with a severity level of 22 rarely occur. If this error occurs, run DBCC CHECKDB to determine if other objects in the database are also corrupted. This problem may only occur in the cache and not in the disk itself. If this error occurs, restart the instance of the database engine to correct the problem. To continue working, you must reconnect to the database engine instance; otherwise, use DBCC to fix the problem. In some cases, you may need to restore the database.

If restarting the instance of the database engine does not solve this problem, then the problem is on disk. Sometimes destroying the object specified in the error message can solve this problem. For example, if the message reports that an instance of the database engine found a row of length 0 in a nonclustered index, delete the index and rebuild it.

twenty-three

Indicates that there is a problem with the integrity of the entire database due to hardware or software problems.

Errors with a severity level of 23 rarely occur. If this error occurs, run DBCC CHECKDB to determine the extent of the damage. This problem may only occur in the cache and not in the disk itself. If this error occurs, restart the instance of the database engine to correct the problem. To continue working, you must reconnect to the database engine instance; otherwise, use DBCC to fix the problem. In some cases, you may need to restore the database.

twenty-four

Indicates a media failure. Your system administrator may need to restore the database. You may also need to call the hardware vendor

Reference:

Https://docs.microsoft.com/zh-cn/sql/relational-databases/errors-events/database-engine-error-severities?view=sql-server-2017

Summary

The above is the whole content of this article. I hope the content of this article has a certain reference and learning value for everyone's study or work. Thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.