Cannot start database due to corruption of database after .lk file is intentionally removed.

Cannot start database Memory Violation (49)
Can't startup database server with dbman or _mprosrv.
Database startup errors with Memory Violation (49)
Single user -RO session is possible, but the database still cannot be opened multi-user
Truncate BI is possible, but the database still cannot be opened multi-user

User run scripts first verify if the .lk file exists and delete it prior to running an intensive data load or schema update single user
The initial script used to start the database contains "delete <db>.lk" prior to the _mprosrv

Contents of protrace file indicate attempting to get object record from database metaschema failing: omGetObjectRecord

Stack trace from _mprosrv reads:

Evidence of removal of .lk file:  

The .lk file was deleted while database was running while multiple user sessions were updating the database. The watchdog detected the missing lock file and initiated an abnormal shutdown but the damage was already done to the database.  As a consequence, the database has become irrecoverably corrupted.  For further clarification refer to Article:

•  What causes ".lk is missing, shutting down 4195  

Recommended course of action:

• Restore the database from backup.
• Roll forward any subsequent available AI files to a point in time just before the .lk file was removed.

Alternate course of action:

• Dump the data from the database (which may fail due to the suspected meta-schema corruption)
• If the dump is successful (and no errors listed in the database log) then load the data into a completely new database.

Progress Article:

 The database .lk file.