Oneoffs Patch 与目录有关?

本文记录了在Oracle环境中安装补丁5376770的过程,并解决了与现有补丁5375583的冲突问题。通过详细的步骤说明如何应用补丁、回滚旧补丁并完成集群节点的更新。

请看下面步骤:

$ cd henry
$ ls
5376770                       p5376770_10203_SOLARIS64.zip

$ opatch apply
Invoking OPatch 10.2.0.5.0

Oracle Interim Patch Installer version 10.2.0.5.0
Copyright (c) 2010, Oracle Corporation.  All rights reserved.


Oracle Home       : /opt/app/oracle/product/10.2.0/db_1
Central Inventory : /opt/app/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.5.0
OUI version       : 10.2.0.3.0
OUI location      : /opt/app/oracle/product/10.2.0/db_1/oui
Log file location : /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2010-08-09_01-36-54AM.log

Patch history file: /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

Failed to load the patch object.  Possible causes are:
  The specified path is not an interim Patch shiphome
  Meta-data files are missing from the patch area
  Patch location = /export/home/oracle
  Details = PatchObject constructor: Input file "/export/home/oracle/etc/config/actions" or "/export/home/oracle/etc/config/inventory" does not exist.

ApplySession failed: PatchObject constructor: Input file "/export/home/oracle/etc/config/actions" or "/export/home/oracle/etc/config/inventory" does not exist.
System intact, OPatch will not attempt to restore the system

OPatch failed with error code 73

$ cd henry
$ ls
5376770                       p5376770_10203_SOLARIS64.zip
$ mv 5376770 /tmp
$ ls
p5376770_10203_SOLARIS64.zip
$ cd /tmp
$ ls
5376770              disktacct.0805       hsperfdata_noaccess  hsperfdata_root
disktacct.0729       env.log              hsperfdata_oracle    opatch_debug.log
$ cd 5*
$ opatch apply
Invoking OPatch 10.2.0.5.0

Oracle Interim Patch Installer version 10.2.0.5.0
Copyright (c) 2010, Oracle Corporation.  All rights reserved.


Oracle Home       : /opt/app/oracle/product/10.2.0/db_1
Central Inventory : /opt/app/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.5.0
OUI version       : 10.2.0.3.0
OUI location      : /opt/app/oracle/product/10.2.0/db_1/oui
Log file location : /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2010-08-09_02-00-54AM.log

Patch history file: /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch '5376770' to OH '/opt/app/oracle/product/10.2.0/db_1'
Interim patch 5376770 conflict with patch(es) [  5375583 ] in the Oracle Home

Patch [ 5376770 ] conflict with patch(es) [  5375583 ] in the Oracle Home.

To resolve patch conflicts please contact Oracle Support Services.
If you continue, patch(es) [  5375583 ] will be rolled back and the new Patch  [ 5376770 ] will be installed.


Do you want to proceed? [y|n]
y
User Responded with: Y

Running prerequisite checks...
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Y

OPatch detected the node list and the local node from the inventory.  OPatch will patch the local system then propagate the patch to the remote nodes.


This node is part of an Oracle Real Application Cluster.
Remote nodes: 'tst-rac02-ud-us-eqx'
Local node: 'tst-rac01-ud-us-eqx'
Please shut down Oracle instances running out of this ORACLE_HOME on all the nodes.
(Oracle Home = '/opt/app/oracle/product/10.2.0/db_1')


Are all the nodes ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '5376770' for restore. This might take a while...
Backing up files affected by the patch '5375583' for restore. This might take a while...
ApplySession rolling back interim patch '5375583' from OH '/opt/app/oracle/product/10.2.0/db_1'

Patching component oracle.rdbms, 10.2.0.3.0...
Updating archive file "/opt/app/oracle/product/10.2.0/db_1/lib/libserver10.a"  with "lib/libserver10.a/kcl.o"
Updating archive file "/opt/app/oracle/product/10.2.0/db_1/lib/libserver10.a"  with "lib/libserver10.a/kjbm.o"
RollbackSession removing interim patch '5375583' from inventory


OPatch back to application of the patch '5376770' after auto-rollback.

Backing up files affected by the patch '5376770' for rollback. This might take a while...

Patching component oracle.rdbms, 10.2.0.3.0...
Updating archive file "/opt/app/oracle/product/10.2.0/db_1/lib/libserver10.a"  with "lib/libserver10.a/kcl.o"
Updating archive file "/opt/app/oracle/product/10.2.0/db_1/lib/libserver10.a"  with "lib/libserver10.a/kjbm.o"
Running make for target ioracle
ApplySession adding interim patch '5376770' to inventory

Verifying the update...
Inventory check OK: Patch ID 5376770 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 5376770 are present in Oracle Home.

Patching in all-node mode.

Updating nodes 'tst-rac02-ud-us-eqx'
   Apply-related files are:
     FP = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_files.txt"
     DP = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_dirs.txt"
     MP = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/make_cmds.txt"
     RC = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/remote_cmds.txt"

   Auto-Rollback-related files are:
     FR = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/remove_files.txt"
     DR = "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/remove_dirs.txt"

Instantiating the file "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/remove_dirs.txt.instantiated" by replacing $ORACLE_HOME in "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/remove_dirs.txt" with actual path.
Removing directories on remote nodes...
Instantiating the file "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_files.txt.instantiated" by replacing $ORACLE_HOME in "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_files.txt" with actual path.
Propagating files to remote nodes...
Instantiating the file "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_dirs.txt.instantiated" by replacing $ORACLE_HOME in "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/copy_dirs.txt" with actual path.
Propagating directories to remote nodes...
Instantiating the file "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/make_cmds.txt.instantiated" by replacing $ORACLE_HOME in "/opt/app/oracle/product/10.2.0/db_1/.patch_storage/5376770_Mar_29_2008_07_38_24/rac/make_cmds.txt" with actual path.
Running command on remote node 'tst-rac02-ud-us-eqx':
cd /opt/app/oracle/product/10.2.0/db_1/rdbms/lib; /usr/ccs/bin/make -f ins_rdbms.mk ioracle ORACLE_HOME=/opt/app/oracle/product/10.2.0/db_1 || echo REMOTE_MAKE_FAILED::>&2

 

All nodes have been patched.  You may start Oracle instances on the local system and nodes 'tst-rac02-ud-us-eqx'

There were relinks on remote nodes.  Remember to check the binary size and timestamp on the nodes 'tst-rac02-ud-us-eqx' .
The following make commands were invoked on remote nodes:
'cd /opt/app/oracle/product/10.2.0/db_1/rdbms/lib; /usr/ccs/bin/make -f ins_rdbms.mk ioracle ORACLE_HOME=/opt/app/oracle/product/10.2.0/db_1
'

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67619:Interim patch 5376770 conflict with patch(es) [  5375583 ] in the Oracle Home
--------------------------------------------------------------------------------
OPatch Session completed with warnings.

OPatch completed with warnings.
$ $ opatch lsinventory
Invoking OPatch 10.2.0.5.0

Oracle Interim Patch Installer version 10.2.0.5.0
Copyright (c) 2010, Oracle Corporation.  All rights reserved.


Oracle Home       : /opt/app/oracle/product/10.2.0/db_1
Central Inventory : /opt/app/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.5.0
OUI version       : 10.2.0.3.0
OUI location      : /opt/app/oracle/product/10.2.0/db_1/oui
Log file location : /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2010-08-09_02-07-57AM.log

Patch history file: /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : /opt/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2010-08-09_02-07-57AM.txt

--------------------------------------------------------------------------------
Installed Top-level Products (2):

Oracle Database 10g                                                  10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 2                            10.2.0.3.0
There are 2 products installed in this Oracle Home.


Interim patches (44) :

Patch  5376770      : applied on Mon Aug 09 02:05:06 EDT 2010
   Created on 29 Mar 2008, 07:38:24 hrs PST8PDT
   Bugs fixed:
     5376770

Patch  5961454      : applied on Tue Oct 21 04:32:52 EDT 2008
   Created on 8 Oct 2007, 23:25:52 hrs PST8PDT
   Bugs fixed:
     5961454

 

<think> 嗯,用户再次询问图像分patchpatch的含义,看来对基础概念有持续探究的需求。虽然之前已经系统解释过,但用户可能希望更聚焦在“patch”这个术语本身的理解上。 注意到用户提供了三则站内引用,其中[1]详细说明了CNN中的patch定义,[2]展示具体计算过程,[3]涉及resize操作的局限。这些引用恰好覆盖了patch的三个关键维度:概念定义、数学实现、处理动机。 用户似乎处于技术学习阶段,可能需要更直观的类比。不妨用拼图游戏比喻:整幅图像是拼图成品,每个patch就像单独拼图块,处理时先研究每块的特征(颜色/边缘),再组合成整体。 特别要注意的是,用户引用的材料提到两个易混淆点:1)patch卷积核的关系;2)overlap的处理逻辑。这提示需要在回答中明确区分“处理单元”(patch)和“处理工具”(卷积核),并用图示说明重叠区域(如引用[2]的示例)。 考虑到用户连续追问该概念,可能在为论文或项目做准备。回答时需强调工程实践中的关键参数选择(如尺寸/步长),并补充实际案例(如ViT的16×16分割),这样能帮助用户建立理论实践的连接。 </think> 在图像处理领域,"分Patch输出"中的**Patch指图像中固定尺寸的局部子区域**,是独立处理的基本单元。其核心含义作用如下: --- ### 一、Patch的本质特性 1. **几何定义** - 尺寸固定的矩形/正方形区域(如$3\times3$、$16\times16$像素)[^1] - 通过滑动窗口在图像上提取,覆盖整图 - 每个Patch独立承载局部视觉信息(如纹理、边缘) 2. **数学描述** 设图像尺寸$W \times H$,Patch尺寸$P_w \times P_h$,步长$S$: - Patch数量计算: $$ N_{\text{col}} = \left\lfloor \frac{W - P_w}{S} \right\rfloor + 1, \quad N_{\text{row}} = \left\lfloor \frac{H - P_h}{S} \right\rfloor + 1 $$ - 第$(i,j)$个Patch的坐标范围: $$ x\in[i\cdot S,\ i\cdot S+P_w], \quad y\in[j\cdot S,\ j\cdot S+P_h] $$ --- ### 二、分Patch的核心目的 | **目标** | **实现方式** | **典型场景** | |-------------------|------------------------------------------|--------------------------| | 降低计算复杂度 | 将大图分解为GPU可处理的小单元 | 高分辨率医学影像分析[^3] | | 提取局部特征 | 卷积核在Patch上操作捕捉细节 | CNN边缘检测[^1] | | 保持空间结构 | 通过坐标映射还原全局关系 | ViT位置编码[^1] | | 适应不规则区域 | 重叠或填充策略处理边界 | 图像修复任务 | --- ### 三、关键技术实现 1. **重叠策略** - 当步长$S < P$时产生重叠区域(图1) ```mermaid graph LR A[输入图像] --> B[滑动窗口提取Patch] B --> C{S < Patch尺寸?} C -->|是| D[重叠区域保留边界信息] C -->|否| E[无重叠高效处理] ``` - 重叠比例公式:$Overlap = \frac{P - S}{P} \times 100\%$ 2. **边界处理** - **填充法**:用零值/镜像值扩展图像边界 - **丢弃法**:舍弃不完整Patch(如引用[2]示例) 3. **特征提取流程** ```python # 伪代码:Patch处理流程 for patch in extract_patches(image, size=(pw, ph), stride=S): features = conv_layer(patch) # 卷积提取特征 pooled = max_pooling(features) # 池化增强鲁棒性 output_buffer.save(patch_coord, pooled) # 存储结果 ``` --- ### 四、相关概念对比 | **概念** | **Patch的关系** | **典型区别** | |---------------|-------------------------------------------|------------------------------| | 卷积核(Kernel) | 在Patch上滑动进行特征提取的工具 | Patch是输入区域,Kernel是处理器 | | ROI(感兴趣区域)| Patch是均匀分割的规则区域,ROI是任意形状 | ROI常用于目标检测任务 | | 9-Patch | Android特有的可拉伸图像格式 | 专为解决UI适配问题设计[^1] | > 如引用[3]指出,相比直接resize整图,分Patch处理能**避免插值导致的像素信息损失**,保留原始细节精度。 --- ### 五、典型应用场景 1. **Vision Transformer** 将图像分割为$16\times16$的Patch序列,通过线性投影转换为token输入[^1] 2. **医学影像分析** 病理切片分Patch检测癌细胞(如$512\times512$子区域) 3. **图像压缩** JPEG编码将图像分为$8\times8$块进行DCT变换 --- ### 总结 在"图像分Patch输出"中,**Patch的本质是图像处理的原子单元**,通过局部处理-全局整合的范式,在降低计算复杂度的同时保留空间结构信息。其核心价值在于平衡**计算效率****特征表达能力**,成为现代计算机视觉的基石技术之一[^1][^3]。
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值