我们有一个与银行相关的应用程序，我们正面临这个非常严重的问题。问题是随机数量的事务被更改为不同的状态，例如今天有两个以上的 lac 事务被更改为 Pending 认为它们中的大多数已经解决、授权等。由于我们的应用程序太大，我们无法找到创建查询的问题.
所以暂时我想知道我是否可以以某种方式限制我与数据库的通信，以检查我是否收到太多类似的请求，或者数据库表中的条目是否过多它应该停止执行或停止或其他什么？至少可以让这件事再次发生的每一种可能的解决方案都受到高度赞赏。
谢谢
问问题
87 次
1 回答
1
If you have versioning enabled, which I'm sure there is, I'd suggest you start rolling back by a minor version point and check the DB related changes in each commit.
Edit:
If it is happening to a fixed set of tables, then for the time being (till you debug you production), you may want to revoke update privileges to these tables around that particular time of night for the database user under which these updates are happening. And then grant the privileges again after that window has passed. This is a desperate situation, and this is a desperate solution. You can only do it for a couple of days (which is the most you can spend to debug this without affecting users.)
Also, if the set of tables to which this is happening is fixed, then do a code search for update queries on these tables and look for sql injection vulnerabilities first. And then look for poorly formed update SQLs.
于 2013-10-22T12:58:43.613 回答