Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Operation log of unmounting ASM disk at once

2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

Because the Stream needs to be rebuilt, the export uses expdp, and the source database version is 10.2.0.1 (target library 11.2.0.2). The COMPRESSION effect of expdp in 10g is not good. The exported dmp is relatively large, about 450g, but the local disk space is not enough. Check that there is still a lot of free space in ASM space. The following operation is to separate a 100g LUN from Oracle ASM to the local file system to use.

Operating environment

View the size of the asm disk

View the corresponding disk

Plan to unmount / dev/archdisk5 for the file system, check the corresponding disk, device number 19

If you take a look at the corresponding disk, you can see that ASM uses the following disk, and the disk corresponding to device number 23 dev/rhdisk19 19 is / disk.

Verify the device number again, and the corresponding disk is hdisk19

Check the corresponding disk. The corresponding disk is hdisk19.

Delete ASM disk

According to the above query, the disk_name in the ASM corresponding to / dev/archdisk5 is ARCHDG_0004, and this LUN is about 100g. Check the corresponding diskgroup name.

You can check the status through V$ASM_DISK.HEADER_STATUS during the operation, and V$ASM_OPERATION and progress during the data balance process.

The following is the result of a successful execution. The status of HEADER_STATUS is FORMER, and the number of groups and disks is 0.

Join the file system

Delete the index node corresponding to hdisk19, that is, / dev/archdisk5, so that the asm process can unlock the disk

Add disks to the file system, and note that this system-level operation uses root

According to the error above, the solution seen on the Internet is to clean up disk information using dd.

After performing the above operation, another error was reported, so the database was restarted before operation, and this time was found to be successful.

The following shows that disk space has been freed

Bash-3.00# lsvg bkvg

VOLUME GROUP: bkvg VG IDENTIFIER: 00f6a21d00004c00000001306a03bc53

VG STATE: active PP SIZE: 64 megabyte (s)

VG PERMISSION: read/write TOTAL PPs: 7990 (511360 megabytes)

MAX LVs: 256 FREE PPs: 69 (4416 megabytes)

LVs: 2 USED PPs: 7921 (506944 megabytes)

OPEN LVs: 2 QUORUM: 3 (Enabled)

TOTAL PVs: 5 VG DESCRIPTORS: 5

STALE PVs: 0 STALE PPs: 0

ACTIVE PVs: 5 AUTO ON: yes

MAX PPs per VG: 32768 MAX PVs: 1024

LTG size (Dynamic): 256kilobyte (s) AUTO SYNC: no

HOT SPARE: no BB POLICY: relocatable

PV RESTRICTION: none

Bash-3.00#

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report