标签云
asm 恢复 asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (100)
- 数据库 (1,598)
- DB2 (22)
- MySQL (70)
- Oracle (1,463)
- Data Guard (49)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (530)
- Oracle安装升级 (84)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- PostgreSQL解析wal日志之—walminer
- Oracle 19c/21c最新patch信息-202404
- PostgreSQL恢复系列:pg_filedump批量处理
- PostgreSQL部分主要字典信息
- PostgreSQL恢复系列:pg_filedump恢复字典构造
- PostgreSQL 16 源码安装
- ORA-00742 ORA-00312 恢复
- 数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
- ORA-600 ktsiseginfo1故障
- ORA-00600: internal error code, arguments: [16703], [1403], [4] 原因
- 最近遇到几起ORA-600 16703故障(tab$被清空),请引起重视
- ORA-600 2662快速恢复之Patch scn工具
- TNS-12518: TNS:listener could not hand off client connection
- ora.storage无法启动报ORA-12514故障处理
- 断电引起文件scn异常数据库恢复
- ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- .[hudsonL@cock.li].mkp勒索加密数据库完美恢复
- 模拟带库实现rman远程备份
- 又一例:ORA-600 kclchkblk_4和2662故障
- Oracle误删除数据文件恢复
分类目录归档:ORACLE 19C
利用createGoldImage 创建 19.11(含202104patch)完整版db和grid
最近实施了一套19c rac并且打上patch 32545008(GI Update 202104)和32399816(OJVM Update 202104),通过createGoldImage 创建了安装程序,直接使用该zip包即可安装含gi/db(含ojvm) 2021年4月的patch
[oracle@dzbl1 ~]$ $ORACLE_HOME/runInstaller -createGoldImage -silent -destinationLocation /tmp/soft_img Launching Oracle Database Setup Wizard... Successfully Setup Software. Gold Image location: /tmp/soft_img/db_home_2021-05-20_09-05-40PM.zip [oracle@dzbl1 ~]$ exit logout [root@dzbl1 ~]# su - grid Last login: Thu May 20 20:57:05 CST 2021 [grid@dzbl1 ~]$ ./gridSetup.sh -createGoldImage -silent -destinationLocation /tmp/soft_img -bash: ./gridSetup.sh: No such file or directory [grid@dzbl1 ~]$ $ORACLE_HOME/gridSetup.sh -createGoldImage -silent -destinationLocation /tmp/soft_img Launching Oracle Grid Infrastructure Setup Wizard... Successfully Setup Software. Gold Image location: /tmp/soft_img/grid_home_2021-05-20_09-13-58PM.zip [grid@dzbl1 ~]$ md5sum /tmp/soft_img/grid_home_2021-05-20_09-13-58PM.zip 7cefb1be8ead8250435d5a95785d1239 /tmp/soft_img/grid_home_2021-05-20_09-13-58PM.zip [grid@dzbl1 ~]$ md5sum /tmp/soft_img/db_home_2021-05-20_09-05-40PM.zip 325841792c44f168c524b440440773b0 /tmp/soft_img/db_home_2021-05-20_09-05-40PM.zip [grid@dzbl1 ~]$ opatch lspatches 32585572;DBWLM RELEASE UPDATE 19.0.0.0.0 (32585572) 32584670;TOMCAT RELEASE UPDATE 19.0.0.0.0 (32584670) 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32576499;ACFS RELEASE UPDATE 19.11.0.0.0 (32576499) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [grid@dzbl1 ~]$ su - oracle Password: Last login: Thu May 20 21:04:33 CST 2021 on pts/1 [oracle@dzbl1 ~]$ opatch lspatches 32399816;OJVM RELEASE UPDATE: 19.11.0.0.210420 (32399816) 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [oracle@dzbl1 ~]$ ls -l /tmp/soft_img/ total 9225956 -rw-r--r-- 1 oracle oinstall 4268265132 May 20 21:13 db_home_2021-05-20_09-05-40PM.zip -rw-r--r-- 1 grid oinstall 5179109549 May 20 21:21 grid_home_2021-05-20_09-13-58PM.zip [oracle@dzbl1 ~]$
下载到win,并且按照oracle官方命名方式进程重命名,并且md5验证,确定文件完整性
C:\Users\XFF>CertUtil -hashfile E:\vm_shared\LINUX.X64_1911000_grid_home.zip md5 MD5 的 E:\vm_shared\LINUX.X64_1911000_grid_home.zip 哈希: 7cefb1be8ead8250435d5a95785d1239 CertUtil: -hashfile 命令成功完成。 C:\Users\XFF>CertUtil -hashfile E:\vm_shared\LINUX.X64_1911000_db_home.zip md5 MD5 的 E:\vm_shared\LINUX.X64_1911000_db_home.zip 哈希: 325841792c44f168c524b440440773b0 CertUtil: -hashfile 命令成功完成。
通过此类方法,可以自己制作19c含patch版本的安装介质
发表在 Oracle, ORACLE 19C, Oracle安装升级
评论关闭
19c 打RU patch遇到oui-patch.xml (Permission denied)问题
有一段时间没有做实施的活,今天安装一套19c rac,并且计划安装Patch 32545008 – GI Release Update 19.11.0.0.210420,在安装过程中遇到oui-patch.xml问题,记录下来供参考:
1. OPATCHAUTO-72088
[root@jbsbdb1 ~]# opatchauto apply /u01/soft/32545008 OPatchauto session is initiated at Wed Apr 28 14:20:24 2021 System initialization log file is /u01/app/19.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-04-28_02-20-29PM.log. Session log file is /u01/app/19.0/grid/cfgtoollogs/opatchauto/opatchauto2021-04-28_02-20-57PM.log The id for this session is N2PG Wrong OPatch software installed in following homes: Host:jbsbdb2, Home:/u01/app/oracle/product/19.0/db_1 Host:jbsbdb2, Home:/u01/app/19.0/grid OPATCHAUTO-72088: OPatch version check failed. OPATCHAUTO-72088: OPatch software version in homes selected for patching are different. OPATCHAUTO-72088: Please install same OPatch software in all homes. OPatchAuto failed. OPatchauto session completed at Wed Apr 28 14:21:15 2021 Time taken to complete the session 0 minute, 51 seconds opatchauto failed with error code 42
故障原因,只是升级了节点1的grid和oracle的opatch,把节点2的opatch也升级之后该问题解决
2. oui-patch.xml (Permission denied)文件处理
[root@jbsbdb2 soft]# opatchauto apply /u01/soft/32545008 OPatchauto session is initiated at Wed Apr 28 14:52:29 2021 System initialization log file is /u01/app/19.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-04-28_02-52-32PM.log. Session log file is /u01/app/19.0/grid/cfgtoollogs/opatchauto/opatchauto2021-04-28_02-52-58PM.log The id for this session is T6ST Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.0/grid Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0/db_1 Patch applicability verified successfully on home /u01/app/19.0/grid Patch applicability verified successfully on home /u01/app/oracle/product/19.0/db_1 Executing patch validation checks on home /u01/app/19.0/grid Patch validation checks successfully completed on home /u01/app/19.0/grid Executing patch validation checks on home /u01/app/oracle/product/19.0/db_1 Patch validation checks successfully completed on home /u01/app/oracle/product/19.0/db_1 Verifying SQL patch applicability on home /u01/app/oracle/product/19.0/db_1 SQL patch applicability verified successfully on home /u01/app/oracle/product/19.0/db_1 Preparing to bring down database service on home /u01/app/oracle/product/19.0/db_1 Successfully prepared home /u01/app/oracle/product/19.0/db_1 to bring down database service Performing prepatch operations on CRS - bringing down CRS service on home /u01/app/19.0/grid Prepatch operation log file location: /u01/app/grid/crsdata/jbsbdb2/crsconfig/crs_prepatch_apply_inplace_jbsbdb2_2021-04-28_02-54-34PM.log CRS service brought down successfully on home /u01/app/19.0/grid Performing prepatch operation on home /u01/app/oracle/product/19.0/db_1 Perpatch operation completed successfully on home /u01/app/oracle/product/19.0/db_1 Start applying binary patch on home /u01/app/oracle/product/19.0/db_1 Failed while applying binary patches on home /u01/app/oracle/product/19.0/db_1 Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures: Patch Target : jbsbdb2->/u01/app/oracle/product/19.0/db_1 Type[rac] Details: [ ---------------------------Patching Failed--------------------------------- Command execution failed during patching in home: /u01/app/oracle/product/19.0/db_1, host: jbsbdb2. Command failed: /u01/app/oracle/product/19.0/db_1/OPatch/opatchauto apply /u01/soft/32545008 -oh /u01/app/oracle/product/19.0/db_1 -target_type rac_database -binary -invPtrLoc /u01/app/19.0/grid/oraInst.loc -jre /u01/app/19.0/grid/OPatch/jre -persistresult /u01/app/oracle/product/19.0/db_1/opatchautocfg/db/sessioninfo/sessionresult_jbsbdb2_rac_2.ser -analyzedresult /u01/app/oracle/product/19.0/db_1/opatchautocfg/db/sessioninfo/sessionresult_analyze_jbsbdb2_rac_2.ser Command failure output: ==Following patches FAILED in apply: Patch: /u01/soft/32545008/32545013 Log: /u01/app/oracle/product/19.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-04-28_15-00-49PM_1.log Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: ApplySession failed in system modification phase... 'ApplySession::apply failed: java.io.IOException: oracle.sysman.oui.patch.PatchException: java.io.FileNotFoundException: /u01/app/oraInventory/ContentsXML/oui-patch.xml (Permission denied)' After fixing the cause of failure Run opatchauto resume ] OPATCHAUTO-68061: The orchestration engine failed. OPATCHAUTO-68061: The orchestration engine failed with return code 1 OPATCHAUTO-68061: Check the log for more details. OPatchAuto failed. OPatchauto session completed at Wed Apr 28 15:05:29 2021 Time taken to complete the session 13 minutes, 0 second opatchauto failed with error code 42
在节点1打patch成功之后,对节点2进行打patch,遇到类似:ApplySession::apply failed: java.io.IOException: oracle.sysman.oui.patch.PatchException:
java.io.FileNotFoundException: /u01/app/oraInventory/ContentsXML/oui-patch.xml (Permission denied)问题,通过查询mos发现类似文章opatchauto apply Results java.io.FileNotFoundException:
[root@jbsbdb2 soft]# ls -l /u01/app/oraInventory/ContentsXML/oui-patch.xml -rw-r----- 1 grid oinstall 174 Apr 28 14:04 /u01/app/oraInventory/ContentsXML/oui-patch.xml
确实文件权限不对,对其授权处理
[root@jbsbdb2 soft]# chmod 660 /u01/app/oraInventory/ContentsXML/oui-patch.xml [root@jbsbdb2 soft]# ls -l /u01/app/oraInventory/ContentsXML/oui-patch.xml -rw-rw---- 1 grid oinstall 174 Apr 28 14:04 /u01/app/oraInventory/ContentsXML/oui-patch.xml
处理oui-patch.xml文件异常之后,尝试回滚操作
[root@jbsbdb2 soft]# opatchauto rollback /u01/soft/32545008 OPatchauto session is initiated at Wed Apr 28 15:13:58 2021 System initialization log file is /u01/app/19.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-04-28_03-14-00PM.log. Session log file is /u01/app/19.0/grid/cfgtoollogs/opatchauto/opatchauto2021-04-28_03-14-28PM.log The id for this session is KFYI Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0/db_1 Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.0/grid Patch applicability verified successfully on home /u01/app/19.0/grid Patch applicability verification failed on home /u01/app/oracle/product/19.0/db_1 Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures: Patch Target : jbsbdb2->/u01/app/oracle/product/19.0/db_1 Type[rac] Details: [ ---------------------------Patching Failed--------------------------------- Command execution failed during patching in home: /u01/app/oracle/product/19.0/db_1, host: jbsbdb2. Command failed: /u01/app/oracle/product/19.0/db_1/OPatch/opatchauto rollback /u01/soft/32545008 -oh /u01/app/oracle/product/19.0/db_1 -target_type rac_database -binary -invPtrLoc /u01/app/19.0/grid/oraInst.loc -jre /u01/app/19.0/grid/OPatch/jre -persistresult /u01/app/oracle/product/19.0/db_1/opatchautocfg/db/sessioninfo/sessionresult_analyze_jbsbdb2_rac_2.ser -analyze -online -prepare_home Command failure output: ==Following patches FAILED in analysis for rollback: Patch: /u01/soft/32545008/32579761 Log: Reason: Failed during listing in Analysis: java.lang.Exception: oracle.opatch.opatchsdk.OPatchException: Unable to create patchObject Possible causes are: ORACLE_HOME/inventory/oneoffs/32545013 is corrupted. PatchObject constructor: Input file "/u01/app/oracle/product/19.0/db_1/inventory/oneoffs/32545013/etc/config/actions" or "/u01/app/oracle/product/19.0/db_1/inventory/oneoffs/32545013/etc/config/inventory" does not exist. Patch: /u01/soft/32545008/32545013 Log: Reason: Failed during listing in Analysis: java.lang.Exception: oracle.opatch.opatchsdk.OPatchException: Unable to create patchObject Possible causes are: ORACLE_HOME/inventory/oneoffs/32545013 is corrupted. PatchObject constructor: Input file "/u01/app/oracle/product/19.0/db_1/inventory/oneoffs/32545013/etc/config/actions" or "/u01/app/oracle/product/19.0/db_1/inventory/oneoffs/32545013/etc/config/inventory" does not exist. After fixing the cause of failure Run opatchauto resume ] OPATCHAUTO-68061: The orchestration engine failed. OPATCHAUTO-68061: The orchestration engine failed with return code 1 OPATCHAUTO-68061: Check the log for more details. OPatchAuto failed. OPatchauto session completed at Wed Apr 28 15:14:50 2021 Time taken to complete the session 0 minute, 53 seconds opatchauto failed with error code 42
检查发现/u01/app/oracle/product/19.0/db_1/inventory/oneoffs/32545013确实不存在,从节点1把该文件夹tar过来,然后再次回滚
[root@jbsbdb2 ~]# /u01/app/oracle/product/19.0/db_1/OPatch/opatchauto rollback /u01/soft/32545008 -oh >/u01/app/oracle/product/19.0/db_1 OPatchauto session is initiated at Wed Apr 28 16:12:33 2021 System initialization log file is /u01/app/oracle/product/19.0/db_1/cfgtoollogs/opatchautodb/systemconfig2021-04-28_04-12-36PM.log. Session log file is /u01/app/oracle/product/19.0/db_1/cfgtoollogs/opatchauto/opatchauto2021-04-28_04-12-53PM.log The id for this session is JRS3 Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0/db_1 Patch applicability verified successfully on home /u01/app/oracle/product/19.0/db_1 Executing patch validation checks on home /u01/app/oracle/product/19.0/db_1 Patch validation checks successfully completed on home /u01/app/oracle/product/19.0/db_1 Verifying SQL patch applicability on home /u01/app/oracle/product/19.0/db_1 SQL patch applicability verified successfully on home /u01/app/oracle/product/19.0/db_1 Preparing to bring down database service on home /u01/app/oracle/product/19.0/db_1 Successfully prepared home /u01/app/oracle/product/19.0/db_1 to bring down database service Bringing down database service on home /u01/app/oracle/product/19.0/db_1 Following database(s) and/or service(s) are stopped and will be restarted later during the session: racdb Database service successfully brought down on home /u01/app/oracle/product/19.0/db_1 Performing prepatch operation on home /u01/app/oracle/product/19.0/db_1 Perpatch operation completed successfully on home /u01/app/oracle/product/19.0/db_1 Start rolling back binary patch on home /u01/app/oracle/product/19.0/db_1 Binary patch rolled back successfully on home /u01/app/oracle/product/19.0/db_1 Performing postpatch operation on home /u01/app/oracle/product/19.0/db_1 Postpatch operation completed successfully on home /u01/app/oracle/product/19.0/db_1 Starting database service on home /u01/app/oracle/product/19.0/db_1 Database service successfully started on home /u01/app/oracle/product/19.0/db_1 Preparing home /u01/app/oracle/product/19.0/db_1 after database service restarted No step execution required......... Trying to roll back SQL patch on home /u01/app/oracle/product/19.0/db_1 SQL patch rolled back successfully on home /u01/app/oracle/product/19.0/db_1 OPatchAuto successful. --------------------------------Summary-------------------------------- Patching is completed successfully. Please find the summary as follows: Host:jbsbdb2 RAC Home:/u01/app/oracle/product/19.0/db_1 Version:19.0.0.0.0 Summary: ==Following patches were SKIPPED: Patch: /u01/soft/32545008/32576499 Reason: This patch is not applicable to this specified target type - "rac_database" Patch: /u01/soft/32545008/32585572 Reason: This patch is not applicable to this specified target type - "rac_database" Patch: /u01/soft/32545008/32584670 Reason: This patch is not applicable to this specified target type - "rac_database" Patch: /u01/soft/32545008/32579761 Reason: This Patch does not exist in the home, it cannot be rolled back. ==Following patches were SUCCESSFULLY rolled back: Patch: /u01/soft/32545008/32545013 Log: /u01/app/oracle/product/19.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-04-28_16-15-05PM_1.log
回滚成功,直接使用opatchauto apply /u01/soft/32545008打节点2成功
3. RU安装成功结果
[grid@jbsbdb2 ~]$ opatch lspatches 32585572;DBWLM RELEASE UPDATE 19.0.0.0.0 (32585572) 32584670;TOMCAT RELEASE UPDATE 19.0.0.0.0 (32584670) 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32576499;ACFS RELEASE UPDATE 19.11.0.0.0 (32576499) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [oracle@jbsbdb2 ~]$ opatch lspatches 32579761;OCW RELEASE UPDATE 19.11.0.0.0 (32579761) 32545013;Database Release Update : 19.11.0.0.210420 (32545013) OPatch succeeded. [grid@jbsbdb2 ~]$ crsctl query crs softwarepatch Oracle Clusterware patch level on node jbsbdb2 is [3331580692]. [grid@jbsbdb2 ~]$ crsctl query crs activeversion -f Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [3331580692]. SQL> select PATCH_ID,DESCRIPTION from dba_registry_sqlpatch; PATCH_ID ---------- DESCRIPTION -------------------------------------------------------------------------------- 29517242 Database Release Update : 19.3.0.0.190416 (29517242) 32545013 Database Release Update : 19.11.0.0.210420 (32545013)
在打patch之前已经知晓该问题,比较粗心的把oui-patch.xml文件从节点1scp拷贝到节点2,没有确认oui-patch.xml权限(拷贝过来是640)从而引起后续很多麻烦
无法启动此程序,因为计算机中丢失api-ms-win-crt-runtime-l1-1-0.dll
在新安装的win操作操作系统中安装oracle 19.3版本数据库,结果不幸遭遇到如下错误
查询oracle 19c对于win操作系统认证列表
本机操作系统为win 2012,在此认证列表中
通过上述认证查询以及是新安装的原版系统,很可能是由于19c安装特殊之处导致,通过查询mos,确认是由于19c的数据库在安装之时perl需要VS 2017的运行库进行一些操作的依赖,因此安装Microsoft Visual C++ Redistributable for Visual Studio 2017或者更高版本即可.下载link:https://aka.ms/vs/16/release/vc_redist.x64.exe
具体参考MOS:Oracle DB 19C Install fails with the error – “THE PROCEDURE ENTRY POINT _REGISTER_ONEXIT_FUNCTION COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY