Solution to insufficient disk partition space for Oracle software and data files in Linux

ORACLE in the virtual machine has been running for a long time, archiving and data files are constantly increasing, and the original ORACLE installation space is insufficient. In this case, you can add a hard disk to the VM again

ORACLE in the virtual machine has been running for a long time, archiving and data files are constantly increasing, and the original ORACLE installation space is insufficient. In this case, you can add a hard disk to the VM again

Oracle in the virtual machine has been running for a long time, archiving and data files are constantly increasing, and the original ORACLE installation space is insufficient.
In this case, you can add a hard disk to the VM and mount ORACLE data files or archived directories to the newly added disk partition.
-- I have not added a new disk here. Instead, I want to repartition and format the unpartitioned part of the original disk for mounting. -- The principle is the same as adding a new disk to partition and format and remount it.

1. view disk space usage-always pay attention to disk space usage

-- If the space usage reaches 100%, the ORACLE database is running and HANG will exist. At this time, if you log on through SQLPLUS, an error will also be prompted-the specific prompt is not recorded. If it is not started, it cannot be started **.
Once the DML operation HANG fails due to insufficient disk space archiving.

[Root @ oel-01 ~] # Df-h
Filesystem Size Used Avail Use % Mounted on
/Dev/sda2 19 GB 13G 5.4G 71%/
/Dev/sda1 99 M 21 M 74 M 22%/boot
Tmpfs 3.0G 528 M 2.5G 18%/dev/shm
/Dev/sda5 4.6G 3.2G 1.2G 73%/backup
This directory is planned to be re-mounted: --- only for testing. The directory to be mounted to the new partition is determined based on actual needs.
[Root @ oel-01 ~] # Du-sh/home/oracle/rmanlog/
44 K/home/oracle/rmanlog/
[Root @ oel-01 ~] # Ls/home/oracle/rmanlog/
Back01.log back11.log back13.log back22.log back24.log
Back02_1.log back12.log back21.log back23.log rmanarch2013061815-40.log
############

2. Use fdisk to view disk partitions

-- Because I know that my disk is not used up, I can use fdisk to partition it directly. If a new disk is added, you can use fdisk-l to view the name of the new disk. -- Fdisk usage can be Baidu.
Start partitioning: -- software and system prompts are omitted to save space.
[Root @ oel-01 ~] # Fdisk/dev/sda
Command (m for help): p
Disk/dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065*512 = 8225280 bytes
Device Boot Start End Blocks Id System
/Dev/sda1*1 13 104391 83 Linux
/Dev/sda2 14 2563 20482875 83 Linux
/Dev/sda3 2564 2824 2096482 + 82 Linux swap/Solaris
/Dev/sda4 2825 3916 8771490 5 Extended
/Dev/sda5 2825 3433 4891761 83 Linux
Command (m for help): n
First cylinder (3434-3916, default 3434 ):
Using default value 3434
Last cylinder or + size or + sizeM or + sizeK (3434-3916, default 3916): + 100 M ---- used for testing, so only 100 M is divided.
Command (m for help): p -- verify that a new partition has been divided

Disk/dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065*512 = 8225280 bytes
Device Boot Start End Blocks Id System
/Dev/sda1*1 13 104391 83 Linux
/Dev/sda2 14 2563 20482875 83 Linux
/Dev/sda3 2564 2824 2096482 + 82 Linux swap/Solaris
/Dev/sda4 2825 3916 8771490 5 Extended
/Dev/sda5 2825 3433 4891761 83 Linux
/Dev/sda6 3434 3446 104391 83 Linux
Command (m for help): w
The partition table has been altered!
Calling ioctl () to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. ---- failed to re-read The partition table. the old Partition table is used. -- The New partition cannot be found in the direct format.
The new table will be used at the next reboot.
Syncing disks.
##################

For more details, please continue to read the highlights on the next page: