- #Lock request time out period exceeded error 1222 how to
- #Lock request time out period exceeded error 1222 windows
05:03:48,spid68,Unknown,During undoing of a logged operation in database 'DB2' (page (0:0) if any) an error occurred at log record ID (11603:2070928:33). Restore the database or file from a backup or repair the database. Typically the specific failure is logged previously as an error in the operating system error log. 05:03:48,spid68,Unknown,During undoing of a logged operation in database 'DB2' (page (0:0) if any) an error occurred at log record ID (11603:2070928:31). 05:03:48,spid68,Unknown,During undoing of a logged operation in database 'DB2' (page (0:0) if any) an error occurred at log record ID (11603:2070928:15). 05:03:48,spid68,Unknown,Error during rollback. Resolve any errors and restart the database. Check the operating system error log for related error messages. 05:03:48,spid68,Unknown,The log for database 'DB2' is not available. 05:03:48,spid68,Unknown,During undoing of a logged operation in database 'DB2' (page (0:0) if any) an error occurred at log record ID (11603:2070928:25). 05:03:48,spid68,Unknown,During undoing of a logged operation in database 'DB2' (page (0:0) if any) an error occurred at log record ID (11603:2070928:1). Reason: Failed to open the explicitly specified database 'DB2'. 05:03:52,Logon,Unknown,Login failed for user 'sql_user'. 05:04:00,spid70s,Unknown,Parallel redo is started for database 'DB2' with worker pool size. 05:04:02,spid70s,Unknown,Recovery of database 'DB2' (5) is 3% complete (approximately 34 seconds remain). 05:04:02,spid70s,Unknown,Recovery of database 'DB2' (5) is 12% complete (approximately 11 seconds remain). 05:04:02,spid70s,Unknown,10 transactions rolled forward in database 'DB2' (5:0).
05:04:02,spid54s,Unknown,12 transactions rolled back in database 'DB2' (5:0). 05:04:02,spid54s,Unknown,Recovery is writing a checkpoint in database 'DB2' (5). This is an informational message only no user action is required. 05:04:02,spid70s,Unknown,CHECKDB for database 'DB2' finished without errors on 20:00:05.017 (local time). 05:04:02,spid54s,Unknown,Recovery completed for database DB2 (database ID 5) in 3 second(s) (analysis 1117 ms redo 308 ms undo 108 ms. 05:04:02,spid54s,Unknown,Parallel redo is shutdown for database 'DB2' with worker pool size. 05:25:38,spid75,Unknown,DBCC TRACEON 3604 server process ID (SPID) 75. 05:25:38,spid75,Unknown,DBCC TRACEOFF 3604 server process ID (SPID) 75. Elapsed time: 0 hours 0 minutes 1 seconds. Log Details: 05:55:57,spid67,Unknown,DBCC CHECKDB (DB1) WITH all_errormsgs no_infomsgs executed by domain\SqlAgt_Svc found 0 errors and repaired 0 errors. In our case, is it Memory? or TDE? or some corruption in log? Oh SQL!!
#Lock request time out period exceeded error 1222 how to
I am wondering how to really track this error - may be to engage MS Support guys as there is very little information on this and goes case by case!! However, the error in those scenarios were 1117 (IO disk subsystem). The server is heavily loaded when a job runs(consumes more memory) and there is a TDE as well.
#Lock request time out period exceeded error 1222 windows
1 (X64) 16:10:35 Copyright (C) 2019 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor) SQL Server: 58GB SQL Server Memory with plenty remaining for OS 12core processor, running on SSD. I know I am behind 4 CU's for 2019 which I will be updating soon. Also, there were no other errors logged in Event Viewer. The database came backup and DBCC Check reported no errors. I have encountered this situation on one of our production server.
0 kommentar(er)
