Operating system error 32(failed to retrieve text for this e

因为DMS有时候会读取事务日志备份文件中的内容,通过DPA监控,刚好找的了这个DMS的账号,在事务日志备份的时间点在执行下面SQL语句(如下所示)。那么就是因为这个进程在读取事务日志备份中内容(跟普通的Replication有点不同),导致事务日志备份出现Operating system error 32错误(The process cannot access the file because it is being used by another process)

昨天遇到一个案例,YourSQLDba做事务日志备份时失败,检查YourSQLDba输出的错误信息如下:

 

图片 1

 

当时检查时,发现磁盘空间还剩下十多G,然后自己手工又将代码取出,手工执行测试,依然报这个错误:

COMMENT:  (None)

</err>

 

图片 2

 

 

   其实以前刚好遇到过这样的案例,使用AplexSQL Log去分析事务日志的备份文件,YourSQLDba的事务日志备份的时候,就会遇到上面错误(YourSQLDba_LogBackups事务日志备份会追加到同一个备份文件),但是这个怎么定位这个错误呢?其实出现这个错误,一定有相关进程在访问事务日志备份文件,那么只要排查这些应用或程序即可。刚好最近配置了AWS的DMS的(DMS简单介绍如下,具体参考官方文档

这个“failed :112”信息一出现,意味着肯定是磁盘空间不够,昨天总结的那篇博客DBCC CHECKDB 遭遇Operating system error 112(failed to retrieve text for this error. Reason: 15105) encountered其实遇到的问题也是类似的,Operating System error 112 meaning There is not enough space on the disk.

 

<Sql>

 

图片 3

JOB RUN:  (None)

<ctx>yMaint.backups</ctx>

 

<Exec>

     The process cannot access the file because it is being used by another process.

to disk = 'M:DB_BACKUPLOG_BACKUPxxxx_[2016-11-22_01h11m05_Tue]_logs.TRN'

DESCRIPTION: BackupDiskFile::CreateMedia: Backup device 'M:DB_BACKUPLOG_BACKUPxxxx_[2018-07-30_06h03m10_Mon]_logs.TRN' failed to create. Operating system error 32(failed to retrieve text for this error. Reason: 15105).

</Exec>

一台数据库服务器的事务日志备份作业偶尔会出现几次备份失败的情况,具体的错误信息为:

Error 3013, Severity 16, level 1 : BACKUP LOG is terminating abnormally.

 

backup log [xxxx] 

to disk = 'M:DB_BACKUPLOG_BACKUPxxxx_[2016-11-22_01h11m05_Tue]_logs.TRN' 

with noInit, checksum, 

NAME = 'YourSQLDba:00h10: M:DB_BACKUPLOG_BACKUPxxxx_[2016-11-22_01h11m05_Tue]_logs.TRN'

本文由太阳集团所有网址16877发布于太阳集团城网址送彩金,转载请注明出处:Operating system error 32(failed to retrieve text for this e

您可能还会对下面的文章感兴趣: