From aa513f7b12870adc8c4d800aa92e5ada53bf326b Mon Sep 17 00:00:00 2001 From: munja Date: Thu, 15 Dec 2022 11:27:33 +0100 Subject: [PATCH] chore: automated commit --- docs/locking-mechanism.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/locking-mechanism.md b/docs/locking-mechanism.md index 7479de1..dab3a53 100644 --- a/docs/locking-mechanism.md +++ b/docs/locking-mechanism.md @@ -17,7 +17,7 @@ Notice above the red box - this situation can occur in unusual circumstances (su ## Unlock Process -Before proceeding with an unlock, the first step should be to understand why the process is locked. By opening the [MPE_LOCKANYTABLE](/locking-mechanism) table it will be possible to see which user performed the lock, and when. Simply filter the table where `LOCK_STATUS_CD='LOCKED'`. +Before proceeding with an unlock, the first step should be to understand why the process is locked. By opening the [MPE_LOCKANYTABLE](/tables/mpe_lockanytable/) table it will be possible to see which user performed the lock, and when. Simply filter the table where `LOCK_STATUS_CD='LOCKED'`. ![](/img/mpe_lockanytable.png)