O & M fault: If you pay attention next time, you may not be so lucky.

I started O & M recently. I had an accident for two days. Although I was surprised, I think I was lucky! The fault records are as follows: 1. The new project was launched on November 1,. When executing the DDL command, I forgot to confirm the character set. As a result, the developer found that it was garbled. 2. On February 3, Oracle DG was deployed. I thought the master database was not an online database and restarted the master database after initialization.
When things happen, we all like Zhuge Liang afterwards. then we say, "my next attention". Don't forget that the production environment is walking randomly, and you can't expect it to happen. I mean there are many uncontrollable risks, and some of them cannot be avoided.
I have made some reflections on the faults over the past two days: 1. backup: must be backed up before any operation 2. delete: if this operation can be performed, it is best not to do it. If it is to be done, it is best to communicate and coordinate with all parties first, confirm and execute again, and back up 3 before execution. restart: inform the relevant business party, program party, and your department boss before restarting. evaluation: You must be clear about the purpose of the command you are executing, the risks involved, and whether the change can be rolled back .... wait 5. environment: Server resources (CPU, I/O, MEM), number of database instances, their respective statuses, and services they serve ...... these are the databases you manage. Have you ever cared about them? 6. Solution: Before going online or performing major operations, you must first formulate a solution to refine the potential risks of each one.
If you are interested, you can also read the previous articles to sum up the ten O & M work experiences of escaping from the fault.
Respect and respect your online environment!
If you pay attention next time, you may be lucky.
Good Luck!