【Exadata】清理Exadata Cell文件系统

可以通过Patch Manager patchmgr, 存在一个cleanup 选项 ,该选项将清理该Cell节点上所有的Patch文件和临时文件。如果对cell节点打patch失败并没有移除/root/_patch_hctap_的情况。

实际上它会移除的文件包括以下:

/opt/oracle.cellos/DISABLE_HARDWARE_FIRMWARE_CHECKS
/root/_patch_hctap_
/root/dostep.sh
/root/.patch_timeouts
/root/.griddisks_to_activate_if_patch_failed
/tmp/_EXA_AXE_*
/root/_EXA_AXE_*
/opt/oracle.cellos/patch/history/stat
/opt/oracle.cellos/patch/bin/patchstat.sh

$pwd
/root

$du -sh *
4.0K 00
8.0K backup-node.bash
8.0K DoRdsPing.sh
68K dostep.sh
1.6G _patch_hctap_

一般建议在Cleanup之前收集仍需要的日志。

一个典型的打Cell Patch的流程如下:

1. Download any workarounds / help

2. Check the prerequisites:
./patchmgr -cells cell_group
-patch_check_prereq [-rolling]

3. Apply and monitor the patch
./patchmgr -cells cell_group –patch [-rolling]

4. Verify the Patch Succeeded
Executing ‘imageinfo’
Verifying patch logfiles
Check validations.log
Executing CheckHWnFWProfile
5. Cleanup: ./patchmgr -cells cell_group -cleanup

 

如果要重新打一个失败的Patch, 则也可以 先运行./patchmgr -cells cell_group -cleanup, 之后再patchmgr -patch

 

about reclaimdisk.sh
reclaimdisks.sh

Boot into Solaris and run /opt/oracle.SupportTools/ reclaimdisks.sh script to remove Linux partition and make space for Onecommand installation (see DBMOG).

[root@dm01db01 ~]# /opt/oracle.SupportTools/reclaimdisks.sh -check
[INFO] This is SUN FIRE X4170 M2 SERVER machine
[INFO] Number of LSI controllers: 1
[INFO] Physical disks found: 4 (252:0 252:1 252:2 252:3)
[INFO] Logical drives found: 3
[INFO] Dual boot installation: yes
[INFO] Linux logical drive: 0
[INFO] RAID Level for the Linux logical drive: 1
[INFO] Physical disks in the Linux logical drive: 2 (252:0 252:1)
[INFO] Dedicated Hot Spares for the Linux logical drive: 0
[INFO] Global Hot Spares: 0
[INFO] Valid dual boot configuration found for Linux: RAID1 from 2 disks
[root@dm01db01 ~]# /opt/MegaRAID/MegaCli/MegaCli64 -LDInfo -Lall -Aall

Adapter 0 — Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :DBSYS
RAID Level          : Primary-1, Secondary-0, RAID Level Qualifier-0
Size                : 278.464 GB
Mirror Data         : 278.464 GB
State               : Optimal
Strip Size          : 1.0 MB
Number Of Drives    : 2
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy   : Disabled
Encryption Type     : None
Is VD Cached: No

Virtual Drive: 1 (Target Id: 1)
Name                :
RAID Level          : Primary-0, Secondary-0, RAID Level Qualifier-0
Size                : 278.464 GB
Parity Size         : 0
State               : Optimal
Strip Size          : 1.0 MB
Number Of Drives    : 1
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy   : Disabled
Encryption Type     : None
Is VD Cached: No

Virtual Drive: 2 (Target Id: 2)
Name                :
RAID Level          : Primary-0, Secondary-0, RAID Level Qualifier-0
Size                : 278.464 GB
Parity Size         : 0
State               : Optimal
Strip Size          : 1.0 MB
Number Of Drives    : 1
Span Depth          : 1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy   : Disabled
Encryption Type     : None
Is VD Cached: No


Posted

in

by

Tags:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *