chore: automated commit
This commit is contained in:
parent
affe5f40e9
commit
5a4f62e2de
@ -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) 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](/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'`.
|
||||
|
||||
![](/img/mpe_lockanytable.png)
|
||||
|
||||
|
@ -21,6 +21,7 @@ nav:
|
||||
- MPE_DATACATALOG_VARS: tables/mpe_datacatalog_vars.md
|
||||
- MPE_DATASTATUS_LIBS: tables/mpe_datastatus_libs.md
|
||||
- MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md
|
||||
- MPE_LOCKANYTABLE: tables/mpe_lockanytable.md
|
||||
- MPE_REVIEW: tables/mpe_review.md
|
||||
- MPE_SUBMIT: tables/mpe_submit.md
|
||||
- MPE_TABLES: tables/mpe_tables.md
|
||||
|
Loading…
Reference in New Issue
Block a user