oracle 19.9 升级到19.14 螃蟹-凯发app官方网站

[oracle@db1-[orcl19c1]-/oracle/app/oracle/product/19.3.0/db_1/opatch]$ ./datapatch -verbose
sql patching tool version 19.14.0.0.0 production on thu apr 28 19:24:51 2022
log file for this invocation: /oracle/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_4141_2022_04_28_19_24_51/sqlpatch_invocation.log
connecting to database...ok
gathering database info...done
bootstrapping registry and package to current versions...done
determining current state...done
current state of interim sql patches:
interim patch 33561310 (ojvm release update: 19.14.0.0.220118 (33561310)):
binary registry: installed
sql registry: not installed
current state of release update sql patches:
binary registry:
no release update patches installed
sql registry:
applied 19.6.0.0.0 release_update 191217155004 successfully on 01-mar-21 11.34.56.633243 am
error: prereq checks
patch 30484981: error reading descriptor from registry: couldn't open encmap gbk.enc:
no such file or directory
at /oracle/app/oracle/product/19.3.0/db_1/perl/lib/site_perl/5.28.1/x86_64-linux-thread-multi/xml/parser.pm line 187.
xml::simple called at /oracle/app/oracle/product/19.3.0/db_1/sqlpatch/sqlpatch.pm line 8123.
patch 30557433: error reading descriptor from registry: couldn't open encmap gbk.enc:
no such file or directory
at /oracle/app/oracle/product/19.3.0/db_1/perl/lib/site_perl/5.28.1/x86_64-linux-thread-multi/xml/parser.pm line 187.
xml::simple called at /oracle/app/oracle/product/19.3.0/db_1/sqlpatch/sqlpatch.pm line 8123.
prereq check failed, exiting without installing any patches.
please refer to mos note 1609718.1 and/or the invocation log
/oracle/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_4141_2022_04_28_19_24_51/sqlpatch_invocation.log
for information on how to resolve the above errors.
sql patching tool complete on thu apr 28 19:25:14 2022

不知道为何不能打开gbk.enc，的确没有这个文件，解决方法比较奇葩

create restore point rp1 guarantee flashback database; --为防止出现问题，加了个还原点以便回退
create table registry$sqlpatch_org as select * from registry$sqlpatch;
create table registry$sqlpatch_ru_info_org as select * from registry$sqlpatch_ru_info;
drop table registry$sqlpatch;
drop table registry$sqlpatch_ru_info;
@?/rdbms/admin/catsqlreg.sql

--然后再执行

./datapatch -verbose
--确认没有问题后，删掉还原点
drop restore point rp1;

怀疑还是xml信息解析时导致

这个看起来很像

凯发app官方网站的解决方案给的是删除这些表后重建，执行datapatch时再填入最新的补丁信息。

参考：doc id 2645981.1

阅读(1660) | 评论(0) | 转发(0) |

上一篇：在备库发起一个一致的备份

下一篇：基础工作：archivelog的提取

给主人留下些什么吧！~~

| | | | |

感谢所有关心和支持过chinaunix的朋友们