Shulou(Shulou.com)05/31 Report--

This article is a detailed introduction to "database server alarm case analysis" for everyone. The content is detailed, the steps are clear, and the details are properly handled. I hope this article "database server alarm case analysis" can help you solve your doubts. The following is a detailed introduction to "database server alarm case analysis." Let's learn new knowledge together.

The alarm message is from a different machine backup library. You can see that the server space is only more than 300 G, and the remaining space is only less than 30 G. So such a problem is very strange.

This server is very old, answer still in repair period, other configuration is not bad, how can a better configuration server only 300G storage space.

# fdisk -l

Disk /dev/sda: 299.4 GB, 299439751168 bytes

255 heads, 63 sectors/track, 36404 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x0006 ca1e Then the following is the partition settings information, the following paragraph to remind me:

Disk /dev/sdb: 1798.7 GB, 1798651772928 bytes

255 heads, 63 sectors/track, 218673 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00062df9

Device Boot Start End Blocks Id System

/dev/sdb1 * 1 218673 1756490841 83 Linux

It can be seen that the storage space of this server is not a low-profile 300G, in fact, there is a larger capacity disk, this problem seems to be easy to explain.

So let's take a moment to fix it quickly. I looked at my watch and gave it 10 to 20 minutes.

But now I only see the partition information, do not know if the file system has been initialized, so still need to confirm before starting. You can use parted at this time.

# parted /dev/sdb

GNU Parted 2.1

Using /dev/sdb

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print list

Model: DELL PERC H710P (scsi)

Disk /dev/sdb: 1799GB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 32.3kB 1799GB 1799GB primary ext3 boot

.... After confirmation, there is no initialization data yet, so the work I have done can be improved. ext3 is a long time ago setting. We should at least have ext4, or xfs, but now we use df -T to check that it is currently ext4, so for the sake of consistency, we should set it conservatively to ext4.

Reformat it.

# mkfs -t ext4 /dev/sdb1 Then use parted to view the information at a glance.

Model: DELL PERC H710P (scsi)

Disk /dev/sdb: 1799GB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 32.3kB 1799GB 1799GB primary ext4 boot At this time there is a brain teaser I need to do. There is currently a soft link U01 in the root directory/pointing to/home/U01, which means that the current data is obtained from the/home directory, in other words, from the root directory.

We set up a new partition, we need to move the data across the area, how to move it as smoothly as possible, we have to keep the soft link/U01 unchanged.

First, stop database services and monitoring of different backup databases.

Create a directory of U01 to switch. mkdir /home/U02

transfer of flowers

mv /home/U01/* /home/U02

mount new partition

mount /dev/sdb1 /home/U01 Modify permissions

chown -R oracle:oinstall /home/U01

chown -R oracle:oinstall /home/U02

This is when the data is actually moved to the new partition. This process takes a little time, but local replication is relatively fast.

mv /home/U02/* /home/U01

The whole process, plus the time it took to copy the file, took about 30 minutes. Soon the problem was fixed, and looking back, how could the problem be this situation now? I remembered that when I was doing data migration before, I found that the disk space of this server was not enough, so I applied for a larger capacity hard disk, but when I changed the disk, I took a vacation. As a result, this matter has been shelved, and the data has been stored in the original partition.

So looking at it as a whole, this problem occurs because of a series of small causes, and all kinds of causes eventually trigger the final problem.

Read here, this article "database server alarm case analysis" article has been introduced, want to master the knowledge of this article also need to practice to understand, if you want to know more related content of the article, welcome to pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.