dc/docs.datacontroller.io
5
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: automated commit

Browse Source
This commit is contained in:
munja
2022-12-14 23:22:48 +01:00
parent affe5f40e9
commit 5a4f62e2de
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/locking-mechanism.md
View File

@@ -17,7 +17,7 @@ Notice above the red box - this situation can occur in unusual circumstances (su
## Unlock Process ## 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) ![](/img/mpe_lockanytable.png)

1
mkdocs.yml
View File

@@ -21,6 +21,7 @@ nav:
- MPE_DATACATALOG_VARS: tables/mpe_datacatalog_vars.md - MPE_DATACATALOG_VARS: tables/mpe_datacatalog_vars.md
- MPE_DATASTATUS_LIBS: tables/mpe_datastatus_libs.md - MPE_DATASTATUS_LIBS: tables/mpe_datastatus_libs.md
- MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md - MPE_DATASTATUS_TABS: tables/mpe_datastatus_tabs.md
- MPE_LOCKANYTABLE: tables/mpe_lockanytable.md
- MPE_REVIEW: tables/mpe_review.md - MPE_REVIEW: tables/mpe_review.md
- MPE_SUBMIT: tables/mpe_submit.md - MPE_SUBMIT: tables/mpe_submit.md
- MPE_TABLES: tables/mpe_tables.md - MPE_TABLES: tables/mpe_tables.md