Get the App
SLTechnology News&Howtos  ›  Database  › 

The transaction not completed causes the object audit to be closed with [- 6407]: Lock timeout. Wrong processing record

Shulou Source: shulou.com Published: 2022-06-01 06:07:45 10月06日 Update

The transaction not completed causes the object audit to be closed with [- 6407]: Lock timeout. Mistake. As shown below.

SQL > sp_noaudit_object ('INSERT','SYSDBA','SYSDBA','CALLINFO','TIME','ALL'); sp_noaudit_object (' INSERT','SYSDBA','SYSDBA','CALLINFO','TIME','ALL'); [- 6407]: Lock timeout.used time: 0000 INSERT','SYSDBA','SYSDBA','CALLINFO','TIME','ALL' 12.007. Execute id is 0.

Solution: you need to commit or rollback the completed transaction on the object so that the transaction ends, and then close the object audit.

SQL > sp_noaudit_object ('INSERT','SYSDBA','SYSDBA','CALLINFO','TIME','ALL'); DMSQL executed successfullyused time: 2.846 (ms). Execute id is 89.SQL >

Tags: Transaction object audit error time out method processing Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Apple MariaDB macOS Shulou Information MySQL