Overview
If you run show tables in a MySQL console, you will see tables missing in an LGP database. In the following example, tables are missing between lgp_inb_msg_20191219 and lgp_inb_msg_20191222.
mysql> SHOW tables;
+----------------------+
| Tables_in_lgp |
+----------------------+
| lgp_files |
| lgp_inb_msg_20191216 |
| lgp_inb_msg_20191217 |
| lgp_inb_msg_20191218 |
| lgp_inb_msg_20191219 |
| lgp_inb_msg_20191222 |
This article explains why the LGP database can skip log entries.
Information
The lack of logs entries can be due to the traffic moving away from a Lithium site. If there is no traffic on a Lithium site, the CDR file will be created empty. Hence, there won't be any Log record, and consequently, no entry will be created in the LGP database.
Entries created after the traffic was moved away, as lgp_inb_msg_20191222 in the example above, can be due to some residual traffic of outgoing messages, i.e., retries for stored messages. For more information, you can check the log content of the day:
mysql>
SELECT *
FROM lgp_inb_msg_20191222
LIMIT 10;