When operations are in progress-Modify the database password

From today on, I continue to share the problems and ideas that I have encountered in the team and motivate myself and the team to grow and improve.

It's hard to start, but I don't know where to begin ...

Just start by modifying the database password tonight.

The last full-volume database password can be traced back to 3 years ago, 3 years in a row, not to move the database password. This year the payment system needs a card concentration, facing the expansion of future business, the security of the database is hidden.

For historical reasons is not retrospective, in order to minimize the risk of database password modification, the team spent nearly one months to read the library, write library, Cacou, report Library to comb, in line with the least impact principle, divided four times to modify, today is the third batch modification.

The Database Password modification specification should be the norm, the first modification with expected to have a large discrepancy, the plan ended within 1 hours, the results took nearly 2 hours, and affected the online business. Why do these problems arise when you are not thinking about it?

Lists the issues that occurred when the database was modified the first time:

1, the database password has the complexity, before the modification to give the need to modify the password, from the complexity of the problem, but the password is the beginning of the number, resulting in the pre-written configuration file in the modification of all again. No one realizes that the password is illegal.

2, password changes still have the wrong password in the constant connection to the database, resulting in the database is locked, only constantly unlocked, the reason is that the stop application is not considered comprehensive, resulting in some of the functions in the call, troubleshooting and use for a long time.

3, Dblink use is not standardized, in the revision has been combed good dblink scope, but in the operation was also added 3 Dblink, this is not configured to modify the scope, resulting in later troubleshooting to find the reason. Anyone can build dblink, the security of data, controllability are hidden.

4, the business does not consider the whole, only take into account 3.0 of the business, in 2.0 still have business not considered.

5, change the password is expected this time does not need to stop the core business, do not need to stop monitoring, the monitoring side can clearly see the volume of business to the bottom, how to affect the business? Callback is also not considered comprehensive in the business.

6, after the modification, many people still use the old password to log in, resulting in a new lock, this is still controllable range.

7, after the modification, some hosts did not restart, resulting in the password is not effective.

Out of so many problems, the first day feeling out of control, fortunately in the second revision of the timely correction, half an hour to change the report library. Tonight to revise the library, the advantage is all business stop, you can rest assured that the changes.

When operations are in progress-Modify the database password