SQL Server database names starting with "__Verification__" remain after SCSQL job

Applies to

SnapCenter Plug-In for Microsoft SQL Server (SCSQL) 4.x and above

Issue

• SQL Server database names starting with "__Verification__" remains after SCSQL verification failure
• SmSql_<JOB_ID>.log shows some OS error is detected during verification then fails to offline database names starting with  "__Verification__"

Example:

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.