场景：
在对Oracle安装补丁后，会发现OS上被占用了大量的空间，本文档清理Opatch过程中的一些文件，释放空间
参考文档：
Can You Delete $ORACLE_HOME/.patch_storage Directory ? (Doc ID 403218.1)
How To Avoid Disk Full Issues Because OPatch Backups Take Big Amount Of Disk Space. (Doc ID 550522.1)
-- 查看$ORACLE_HOME下的隐藏文件夹.patch_storage。 可以看到之前的补丁过程，产生的一些文件。这些文件主要用于rollback补丁，如果不需要，可以清除，以释放空间。
[oracle@19ctest .patch_storage]$ du -sm *
1 29517242_Apr_17_2019_23_27_10
1 29585399_Apr_9_2019_19_12_47
2314 35042068_Apr_6_2023_15_25_04
1941 35320081_Jul_15_2023_12_54_11
2071 35643107_Oct_3_2023_13_34_29
1939 35943157_Jan_13_2024_05_42_55
2138 36233263_Apr_8_2024_17_16_56
1 interim_inventory.txt
1 LatestOPatchSession.properties
1 NApply
1 newdirs.txt
1 record_inventory.txt
[oracle@19ctest .patch_storage]$ pwd
/u01/app/oracle/product/19.0.0/db_1/.patch_storage
[oracle@19ctest .patch_storage]$ -- /u01目录剩余17G
[oracle@19ctest .patch_storage]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.3G 0 4.3G 0% /dev
tmpfs 4.4G 0 4.4G 0% /dev/shm
tmpfs 4.4G 8.8M 4.4G 1% /run
tmpfs 4.4G 0 4.4G 0% /sys/fs/cgroup
/dev/mapper/ol_19cdg01-root 17G 4.1G 13G 24% /
/dev/sdc1 120G 74G 47G 62% /oradata
/dev/sdd1 120G 60G 61G 50% /arch
/dev/sda1 1014M 169M 846M 17% /boot
/dev/sde1 100G 24G 76G 24% /mysql
/dev/sdf1 120G 47G 74G 39% /oradatapdb
/dev/sdb1 40G 24G 17G 59% /u01
tmpfs 883M 0 883M 0% /run/user/0
[oracle@19ctest .patch_storage]$ -- opatch clean的帮助，该命令清除.patch_storage directory文件夹下的'restore.sh,make.txt' files and 'scratch,backup'
[oracle@19ctest ~]$ opatch util cleanup -help
Oracle Interim Patch Installer version 12.2.0.1.41
Copyright (c) 2024, Oracle Corporation. All rights reserved.
DESCRIPTION
This utility cleans up 'restore.sh,make.txt' files and 'scratch,backup'
directories of the.patch_storage directory of Oracle Home.If -ps option is used,
then, it cleans the above specified areas only for that patch, else for all
patches under ORACLE_HOME/.patch_storage. You will be still able to
rollback patches after this cleanup.
SYNTAX
opatch util cleanup [-invPtrLoc <Path to oraInst.loc> ]
[-jre <LOC> ] [-oh <ORACLE_HOME> ]
[-silent] [-report]
[-ps <patch ID with time stamp>, this will
be located under ORACLE_HOME/.patch_storage/]
OPTIONS
-invPtrLoc
Used to locate the oraInst.loc file. Needed when the
installation used the -invPtrLoc flag. This should be
the path to the oraInst.loc file.
-jre
This option tells OPatch to use JRE (java) from the
specified location instead of the default location
under Oracle Home. Both -jdk and -jre options cannot
be specified together. OPatch will display error in
that case.
-oh
The oracle home to work on. This takes precedence over
the environment variable ORACLE_HOME.
-ps
This option is used to specify the Patch ID with timestamp.
This Patch ID with timestamp should be the same as in
.patch_storage directory.
A directory by this name will be present under
ORACLE_HOME/.patch_storage. If this directory is specified
and is valid, then the contents specified in the description
will be cleaned up only for this patch. Otherwise, all patch
related directories will be acted upon by this utility.
-silent
In silent mode, the cleanup always takes place.
-report
Prints the operations without actually executing them.
OPatch succeeded.
[oracle@19ctest ~]$
-- 从清理过程看，会清理'restore.sh,make.txt' files and 'scratch,backup' directories.但仍然可以对补丁进行rollback
[oracle@19ctest ~]$ opatch util cleanup
Oracle Interim Patch Installer version 12.2.0.1.41
Copyright (c) 2024, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/19.0.0/db_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/19.0.0/db_1/oraInst.loc
OPatch version : 12.2.0.1.41
OUI version : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatch/opatch2024-05-08_13-30-06PM_1.log
Invoking utility "cleanup"
OPatch will clean up 'restore.sh,make.txt' files and 'scratch,backup' directories.
You will be still able to rollback patches after this cleanup.
Do you want to proceed? [y|n]
y
User Responded with: Y
Backup area for restore has been cleaned up. For a complete list of files/directories
deleted, Please refer log file.
OPatch succeeded.
[oracle@19ctest ~]$ 一些log
[May 8, 2024 1:30:11 PM] [INFO] [OPSR-MEMORY] Loaded all one offs from inventory. Heap memory in use: 29 (MB)
[May 8, 2024 1:30:11 PM] [INFO] [OPSR-TIME] Raw inventory loaded successfully
[May 8, 2024 1:30:11 PM] [INFO] Invoking utility "cleanup"
[May 8, 2024 1:30:11 PM] [INFO] [OPSR-TIME] Cleaning up backup
[May 8, 2024 1:30:11 PM] [INFO] OPatch will clean up 'restore.sh,make.txt' files and 'scratch,backup' directories.
You will be still able to rollback patches after this cleanup.
Do you want to proceed? [y|n]-- 执行完毕后，貌似没有变化，可能和自己环境有关（19年开始测试补丁，基本上每个季度都测试，后面把又把数据库用RMAN做了迁移，又转换成了PDB模式）。
[oracle@19ctest ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.3G 0 4.3G 0% /dev
tmpfs 4.4G 0 4.4G 0% /dev/shm
tmpfs 4.4G 8.8M 4.4G 1% /run
tmpfs 4.4G 0 4.4G 0% /sys/fs/cgroup
/dev/mapper/ol_19cdg01-root 17G 4.1G 13G 24% /
/dev/sdc1 120G 74G 47G 62% /oradata
/dev/sdd1 120G 60G 61G 50% /arch
/dev/sda1 1014M 169M 846M 17% /boot
/dev/sde1 100G 24G 76G 24% /mysql
/dev/sdf1 120G 47G 74G 39% /oradatapdb
/dev/sdb1 40G 24G 17G 59% /u01
tmpfs 883M 0 883M 0% /run/user/0
[oracle@19ctest ~]$ -- 也可能和log中的以下有关
[oracle@19ctest db_1]$ tail -f /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatch/opatch2024-05-08_13-30-06PM_1.log
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] Cannot delete as either pathToBeDeleted is empty or it does not contain .patch_storage :
[May 8, 2024 1:30:59 PM] [INFO] [OPSR-TIME] Loading cooked inventory-- 查看到的补丁
SYS@cdbtest SQL> select comments from dba_registry_history;
COMMENTS
--------------------------------------------------------------------------------
RDBMS_19.23.0.0.0DBRU_LINUX.X64_240405
Patch applied from 19.3.0.0.0 to 19.21.0.0.0: Release_Update - 230930151951
Patch applied from 19.21.0.0.0 to 19.22.0.0.0: Release_Update - 240104023954
Patch applied from 19.22.0.0.0 to 19.23.0.0.0: Release_Update - 240406004238
SYS@cdbtest SQL> alter session set container =test;
Session altered.
SYS@cdbtest SQL> select comments from dba_registry_history;
COMMENTS
--------------------------------------------------------------------------------
RDBMS_19.23.0.0.0DBRU_LINUX.X64_240405
Patch applied on 19.3.0.0.0: Release_Update - 190410122720
Patch applied from 19.3.0.0.0 to 19.5.0.0.0: Release_Update - 190909180549
Patch applied from 19.5.0.0.0 to 19.11.2.0.0: Release_Update_Revision - 21100717
1159
RAN jvmpsu.sql
OJVM RU post-install
Patch rolled back from 19.11.2.0.0 to 19.11.0.0.0: Release_Update - 210413004009
Patch applied from 19.11.0.0.0 to 19.14.0.0.0: Release_Update - 211225122123
Patch applied from 19.14.0.0.0 to 19.15.0.0.0: Release_Update - 220331125408
COMMENTS
--------------------------------------------------------------------------------
Patch applied from 19.15.0.0.0 to 19.17.0.0.0: Release_Update - 220924224051
Patch applied from 19.17.0.0.0 to 19.18.0.0.0: Release_Update - 230111171738
Patch applied on 19.18.0.0.0: Release_Update - 230111171738
Patch applied on 19.18.0.0.0: Release_Update - 230111171738
Patch applied from 19.18.0.0.0 to 19.19.0.0.0: Release_Update - 230322020406
Patch applied from 19.19.0.0.0 to 19.20.0.0.0: Release_Update - 230715022800
Patch applied from 19.20.0.0.0 to 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
COMMENTS
--------------------------------------------------------------------------------
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
OJVM RU post-deinstall
Patch applied on 19.21.0.0.0: Release_Update - 230930151951
Patch applied from 19.21.0.0.0 to 19.22.0.0.0: Release_Update - 240104023954
Patch applied from 19.22.0.0.0 to 19.23.0.0.0: Release_Update - 240406004238
27 rows selected.
SYS@cdbtest SQL> -- 也可以手工清除，官网上对于手工清除，是这样说明的
Additionally, further cleanup of the $ORACLE_HOME/.patch_storage is possible if there are directories from patches applied to previous versions. This can be done manually as follows:
1. run command:
$ opatch lsinventory
2. Remove all the sub-directories from $ORACLE_HOME/.patch_storage that are not present in the list of installed patches. Directory names would be prefaced with the patchid for example:
13343438_<timestamp>
example to find sub-directories : $ opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Note: List of patches include the sub patches of install Bundle patches, PSU, GI PSU. Hence you should NOT remove the sub patch folders.
[oracle@19ctest ~]$ opatch lsinventory | grep -E "(^Patch.*applied)|(^Sub-patch)"
Patch 36233263 : applied on Fri Apr 19 08:54:31 CST 2024
Patch 29585399 : applied on Thu Apr 18 15:21:33 CST 2019
[oracle@19ctest ~]$ -- 手工清理掉
rm -rf 29517242_Apr_17_2019_23_27_10
rm -rf 35042068_Apr_6_2023_15_25_04
rm -rf 35320081_Jul_15_2023_12_54_11
rm -rf 35643107_Oct_3_2023_13_34_29
rm -rf 35943157_Jan_13_2024_05_42_55--清理后空间，剩余25G
[oracle@19ctest .patch_storage]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.3G 0 4.3G 0% /dev
tmpfs 4.4G 0 4.4G 0% /dev/shm
tmpfs 4.4G 8.8M 4.4G 1% /run
tmpfs 4.4G 0 4.4G 0% /sys/fs/cgroup
/dev/mapper/ol_19cdg01-root 17G 4.1G 13G 24% /
/dev/sdc1 120G 74G 47G 62% /oradata
/dev/sdd1 120G 60G 61G 50% /arch
/dev/sda1 1014M 169M 846M 17% /boot
/dev/sde1 100G 24G 76G 24% /mysql
/dev/sdf1 120G 47G 74G 39% /oradatapdb
/dev/sdb1 40G 16G 25G 39% /u01
tmpfs 883M 0 883M 0% /run/user/0
[oracle@19ctest .patch_storage]$ END
![Java中next()与nextLine()的区别[不废话，直接讲例子]](https://img-blog.csdnimg.cn/direct/6e84d847f52d40459f045dc9c9931858.png)
