Case:
The IBM 3650 server, the bottom layer uses 5 SAS 500GB disk RAID5, one of which is a heat -reserve disk.The server operating system is Windows 2003 X64. The entire storage is divided into three partitions. The first 40GB is the Windows system area, the second is about 700GB, which is the partition where the DB2 production library is located.Division.Customers use the IBM DB2V8.2 database. The overall data is not large. The DB2MOVE backup file is about 16GB.However, multiple tables in the database store external file pointers, pointing to more than 1 million scanned parts.
Solution:
The engineer began to mirrize all disks, and found that two disks had serious physical bad channels. Maximize the data through special equipment, and then set the RAID analysis and reorganization process.The analysis found that the heat -prepared disk has already been topped the RAID disk, and then analyzes the first two disks to the line. At this time, the three disks required to restore the data are determined, but there is a large number of bad ducts in the front of a disk. The location is in WindowsSystem area.According to the analysis of the original RAID parameters, reorganize RAID and repair the Windows system.Use the normal Windows system file to replace the Windows system file in the damaged RAID, and then the mirror back to the customer to use the new disk to make a new RAID, start the server, and enter the system, but one is normal.Verify DB2 database: The database cannot be started. It is found that there are problems with Windows services. Fix it well. The database still cannot be started. The database instance can be restored again. The database instance can start normally and activate the two databases under the instance.The data in the database in the database, the latest data, and the operation are normal.
