US 11,940,974 B2
Database lock
Angela Lee, Monmouth Junction, NJ (US); Padma Samala, Princeton, NJ (US); Shameka DaCosta, Bordentown, NJ (US); Indra Agarwal, Clarksburg, MD (US); Fugui Dong, Rockville, MD (US); and Srikanth Gottipati, Princeton Junction, NJ (US)
Assigned to OTSUKA AMERICA PHARMACEUTICAL, INC., Rockville, MD (US)
Filed by Otsuka America Pharmaceutical Inc., Rockville, MD (US)
Filed on Apr. 3, 2019, as Appl. No. 16/374,697.
Claims priority of provisional application 62/652,149, filed on Apr. 3, 2018.
Prior Publication US 2019/0303360 A1, Oct. 3, 2019
Int. Cl. G06F 11/00 (2006.01); G06F 11/30 (2006.01); G06F 11/34 (2006.01); G06F 16/23 (2019.01); G06Q 10/06 (2023.01); G16H 10/20 (2018.01)
CPC G06F 16/2343 (2019.01) [G06F 11/302 (2013.01); G06F 11/3065 (2013.01); G06F 11/3495 (2013.01); G06Q 10/06 (2013.01); G16H 10/20 (2018.01)] 27 Claims
OG exemplary drawing
 
1. A method for monitoring the status of a database prior to locking the database, the method comprising:
receiving, by a first computer, a request to generate a mock database lock for the database at a point in time before the database is locked; and
responsive to the request to generate the mock database lock:
accessing, by the first computer, a data structure stored in a first data source, wherein the data structure includes fields structuring data describing a set of database lock readiness metrics, wherein the set of database lock readiness metrics include one or more attribute values that each specify a value of an attribute of database data that must be satisfied for the database to be locked;
correlating, by the first computer, information that includes (i) the data structured by the fields of the first data structure that describes the set of database lock readiness metrics and (ii) the database data, wherein the database data is stored by a second data source and includes respective values corresponding to the set of database lock readiness metrics; and
generating, by the computer and based on the correlated information, a mock database lock representing a snapshot of the database at a particular point in time, the snapshot having a data structure that stores:
the set of database lock readiness metrics,
the respective values corresponding to the database lock readiness metrics at the particular point in time,
at least a first indication that a first respective attribute value specified by a first database lock readiness metric, from among the database lock readiness metrics, has been satisfied and is ready for locking, and
at least a second indication that a second respective attribute value specified by a second database lock readiness metric, from among the set of database lock readiness metrics, has not been satisfied and is not ready for locking.