DB2 SQL5005C System Error Troubleshooting

Today, the on-site operation and maintenance personnel reported that "SQL5005C system error" was prompted when backing up the database. The operation and maintenance personnel feedback that this kind of error has never occurred in the backup database before, and this kind of error occurred during the backup today, and the database cannot be backed up.
Therefore, by querying the error explanation of "SQL5005C": "A system error, probably an I/O error, was encountered while accessing a configuration file", it prompts "an IO error occurred while accessing the configuration file". It was suspected that there was a problem with the database accessing some files, so I asked the operation and maintenance personnel to take the db2diag.txt file to see if there were detailed errors printed out. Sure enough, I saw the following errors in it:
2016-04-06-17.00 .56.529000+480 I7974839F392 LEVEL: Error
PID : 5936 TID : 5648 PROC : db2fmp64.exe
INSTANCE: DB2 NODE : 000
EDUID : 5648
FUNCTION: DB2 UDB, config/install, sqlfGetDbmCfg, DATA probe: 10
MESSAGE : SQL5005
#1 : Hexdump, 4 bytes
0x000000000931B188 : 0A00 0F86  

By querying the MESSGAE information, I found inspiration in the article at http://www-01.ibm.com/support/docview.wss?uid=swg21642594. The solution to this problem prompts the permission to query the db2systm file. Therefore, I asked the operation and maintenance colleagues to find this file, but the file could not be found in the system, but it could be found in the test environment. It suddenly occurred to me that due to insufficient disk space in the database, the operation and maintenance colleagues had deleted some log or monitoring files, which may have been deleted by mistake at that time. Therefore, after deleting the db2systm file in the local test environment, and then performing the backup operation, it was found that the phenomenon of the problem site and the on-site feedback were consistent, so it was concluded that since the db2systm file saved the configuration information of the database, mistakenly deleted the db2systm file. An error occurred while retrieving the file information, preventing the backup operation from being performed.

At this point the file has been deleted, think about how to remedy it. . .

In the test environment test, it was found that after deleting the db2systm file, and then restoring (re-copying) the db2systm file, the problem did not exist. I thought of whether it is OK to copy the db2systm file of the test environment to the production environment, so let the operation and maintenance The colleague copied the db2systm file to the same path in the production environment, and then performed the backup operation again, and the problem was solved.

Note: When I asked the operation and maintenance colleagues to execute the db2set command, no information was displayed. At that time, it did not attract enough attention. In fact, when executing the db2set command to query some variable information in the database, it should also be obtained by reading the db2systm file. Of course no information can be obtained. After the file is restored, the variable information can be obtained when the db2set command is executed.