• Oracle 19.20 patch 注意事项


    1. 打patch 用root 打

    /u01/app/19.0.0/grid/OPatch/opatchauto apply /u01/app/patch/35319490

    2.打patch 之前 所有NODE上OPatch 版本要一样

    3.  OPatch 目录不要是root权限

    4.打一台,一台自动重启。 有几个node 在几个node 打。patch 都要传到不同的node上

    5.Patch包 给777 权限最好

    6.文档说2 3 node可以并行打, 可能不行!

    CAUSE

    OPatch  is extracted as root user

    SOLUTION

     - Change the ownership of $ORACLE_HOME/OPatch directory to the home owner, say grid

    # chown -R grid: $ORACLE_HOME/OPatch

    - Resume/retry patching operation

    # opatchauto apply

    [root@rac1 patch]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /u01/app/patch/35319490

    OPatchauto session is initiated at Tue Sep 26 15:05:47 2023

    System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2023-09-26_03-05-53PM.log.

    Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2023-09-26_03-06-36PM.log
    The id for this session is R4NA
    Remote command execution failed due to Can't open perl script "/u01/app/19.0.0/grid/OPatch/auto/database/bin/RemoteHostExecutor.pl": (null)
     Command output: 
    oracle.dbsysmodel.driver.sdk.productdriver.ProductDriverException: Execution failed for host rac3 due to : java.lang.Exception: Remote comman
     Command output: 
    OPatchAuto failed.

    OPatchauto session completed at Tue Sep 26 15:06:56 2023
    Time taken to complete the session 1 minute, 4 seconds

     opatchauto failed with error code 42
    [root@rac1 patch]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /u01/app/patch/35319490

    OPatchauto session is initiated at Tue Sep 26 15:07:46 2023

    System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2023-09-26_03-07-50PM.log.

    Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2023-09-26_03-08-09PM.log
    The id for this session is HKAL
    Remote command execution failed due to Can't open perl script "/u01/app/19.0.0/grid/OPatch/auto/database/bin/RemoteHostExecutor.pl": (null)
     Command output: 
    oracle.dbsysmodel.driver.sdk.productdriver.ProductDriverException: Execution failed for host rac3 due to : java.lang.Exception: Remote comman
     Command output: 
    OPatchAuto failed.

    OPatchauto session completed at Tue Sep 26 15:08:23 2023
    Time taken to complete the session 0 minute, 33 seconds

     opatchauto failed with error code 42

    ### node2 打完再打node3

    [root@rac2 patch]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /u01/app/patch/35319490

    OPatchauto session is initiated at Tue Sep 26 17:34:34 2023

    System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2023-09-26_05-34-47PM.log.

    Remote command execution failed due to Exception in thread "main" oracle.dbsysmodel.driver.sdk.productdriver.ProductDriverException: failed to detect Grid Infrastructure setup due to null
        at oracle.dbsysmodel.driver.sdk.productdriver.ClusterInformationLoader.detectCrsHome(ClusterInformationLoader.java:328)
        at oracle.dbsysmodel.driver.sdk.productdriver.ClusterInformationLoader.loadInventory(ClusterInformationLoader.java:81)
        at oracle.dbsysmodel.driver.sdk.productdriver.ClusterInformationLoader.getInstance(ClusterInformationLoader.java:70)
        at oracle.dbsysmodel.driver.sdk.productdriver.remote.HomeListCollector.executeAction(HomeListCollector.java:31)
        at oracle.dbsysmodel.driver.sdk.productdriver.remote.RemoteOperationHelper.main(RemoteOperationHelper.java:26)
     Command output: 
    OPATCHAUTO-72050: System instance creation failed.
    OPATCHAUTO-72050: Failed while retrieving system information.
    OPATCHAUTO-72050: Please check log file for more details.

    OPatchauto session completed at Tue Sep 26 17:35:53 2023
    Time taken to complete the session 1 minute, 7 seconds

    Topology creation failed.
     
     

    CAUSE

    Database Vault is enabled.
     

    SOLUTION

    The symptoms are documented under Bug 23199899 - ORA-01031: INSUFFICIENT PRIVILEGES WHEN CONVERTING DBV ENABLED NCDB

    The workaround is as follows:

    1) GRANT  DV_PATCH_ADMIN to SYS

    2) re-execute datapatch

    3) REVOKE DV_PATCH_ADMIN from SYS

  • 相关阅读:
    CentOS 7注册服务开机自启动
    MySQL表分区
    数据库系统原理与应用教程(038)—— MySQL 的索引(四):使用 EXPLAIN 命令分析索引
    零售门店管理 会员管理系统 零售会员管理系统 零售会员管理体系 门店管理软件 会员管理系统软件
    Linux i2ctool 工具的使用方法
    项目中使用@Transactional需要注意的点
    09【SpringMVC的Json支持】
    中文汉字转拼音首字母
    git rebase 和 git merge的区别?以及你对它们的理解?
    元宇宙基础知识全汇总
  • 原文地址:https://blog.csdn.net/jnrjian/article/details/133313097