跳转到主内容

以 "__Verification__" 开头的 SQL Server 数据库名称将保留在 SCSQL 作业之后

Views:
17
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx<a>200855725</a>
Last Updated:

适用场景

适用于 Microsoft SQL Server ( SCSQL ) 4.x 及更高版本的 SnapCenter 插件

问题描述

  • __Verification__在 SCSQL 验证失败后,以 " " 开头的 SQL Server 数据库名称仍会保留
  • SmSql_<JOB_ID>.log 显示验证期间检测到一些操作系统错误,因此无法使以 "__Verification__" 开头的数据库名称脱机

示例:

DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] verifying on server: [<SERVER>]
INFO  SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Running DBCC command on database: [__Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] DBCC CHECKDB ('__Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX') WITH NO_INFOMSGS, PHYSICAL_ONLY
ERROR SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
ERROR SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] An exception occurred while executing a Transact-SQL statement or batch.
ERROR SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
INFO  SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] SmVerificationResult for database __Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is [Verified_Failed]
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Connecting to SQL Server: [<SERVER>]
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Cleanup - PostVerification start
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Removing Job with Id [<JOB_ID>]....
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Cleanup - PostVerification Done
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Database [__Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] is going to be Offline...
ERROR SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] The operating system returned error 21 (The device is not ready.) to SQL Server during a read at offset 0x00000000600000 in file ‘<FILEPATH OF .mdf>’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe, system-level error condition that threatens database integrity and must be corrected immediately. It is recommended to complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
ALTER DATABASE statement failed.
WARN  SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Database [__Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] is in [Normal] status, could not set to offline ...
DEBUG SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Detaching database [__Verification__XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]...
INFO  SmSql_<JOB_ID> PID=[<PID>] TID=[<TID>] Detach database failed for Server '<SERVER>'.  This is an informational message only. No user action is required.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.