首页 > 运维 > linux运维 > 正文

Oracle 19c RAC 遇到的几个问题

絕刀狂花
发布: 2025-07-19 11:18:36
原创
635人浏览过

oracle19c 作为长期支持的大版本,是很多公司和个人选择的主流数据库版本,很多公司新上线的系统也都是以 19c 为主,也有很多企业渐渐地迁移数据库到19c,11204 版本已经逐渐退出了舞台。下面对 oracle 19c版本遇到的几个最主要的问题做个简单介绍。

1、Fock() 炸弹

19 RAC 使用 srvctl 无法正常启动,reboot 重启也不会随着 OS 启动而启动数据库实例。

现象如下图:

Oracle 19c RAC 遇到的几个问题

Alert 日志报错

Oracle 19c RAC 遇到的几个问题

对应 trace

Oracle 19c RAC 遇到的几个问题

猜测可能是资源限制问题,但查了很多都是正常。

ipcs –ma 查看 Oracle 共享内存段

Oracle 19c RAC 遇到的几个问题

ipcs -q

Oracle 19c RAC 遇到的几个问题

对应时间段的 OS message

Oracle 19c RAC 遇到的几个问题

Grid 用户资源限制情况,基本上都是无限制。

Oracle 19c RAC 遇到的几个问题

Oracle 用户资源限制情况,基本上都是无限制

Oracle 19c RAC 遇到的几个问题

使用 strace 跟踪启动过程

strace–o /tmp/strace2.log srvctl start database -d teststb –i teststb2

strace–o /tmp/strace1.log srvctl start database -d teststb -i teststb1

其他资源限制查看

Oracle 19c RAC 遇到的几个问题

cat /etc/security/limits.conf

Oracle 19c RAC 遇到的几个问题

cat /etc/systemd/system.conf

Oracle 19c RAC 遇到的几个问题

将此参数打开修改为 infinity 然后重启主机则恢复正常。

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">cat /etc/systemd/system.conf|grepDefaultTasksMax#DefaultTasksMax=512DefaultTasksMax=infinity</code>
登录后复制

Database And ASM InstanceOra-27300 OS System Dependent Operation Fork Failed With Status 11 (Doc ID2331884.1)

systemd limited maximumnumber of tasks that may be created on the node.This setting will alsoaffect maxpid value on the OS.

主要是MAX_PID

Oracle 19c RAC 遇到的几个问题
修改DefaultTasksMax

从SLES 12 SP2开始引入了PID cgroup controller,限制fork()的并发数,避免fork()炸弹。由配置参数DefaultTasksMax控制,缺省值为512,该值比较小,不适用于数据库运行的环境,需要修改为大于等于65536,在此修改为infinity(无限制)。

如果在DBCA期间抛出如下图所示错误,则可能是由于DefaultTasksMax值过小导致的。为了避免DBCA出现错误,提前修改该参数值。

Oracle 19c RAC 遇到的几个问题
Oracle 19c RAC 遇到的几个问题

解决办法:

1)、查看当前值:

test1:~ #systemctl show --property DefaultTasksMax

DefaultTasksMax=512

AI建筑知识问答
AI建筑知识问答

用人工智能ChatGPT帮你解答所有建筑问题

AI建筑知识问答 22
查看详情 AI建筑知识问答

2)、编辑/etc/systemd/system.conf,取消DefaultTasksMax该行注释,并修改值为"infinity".

# vi /etc/systemd/system.conf

DefaultTasksMax=infinity

3)、reboot OS

4)、查看修改后的值

oracle@test1:~>systemctl show --property DefaultTasksMax

DefaultTasksMax=18446744073709551615

2、客户端问题 ORA-28040

前置条件:已安装Oracle11g客户端,配置好环境变量,用PL/SQL Developer登录数据库

解决方案:

在oracle 19C服务器端oracle用户下:

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">cd $ORACLE_HOME/network/admin目录下 新建文件 sqlnet.oravi sqlnet.oraSQLNET.ALLOWED_LOGON_VERSION_SERVER=10;SQLNET.ALLOWED_LOGON_VERSION_CLIENT=10;</code>
登录后复制

②在服务器端,管理员身份登录,重新修改密码。

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">sqlplus / as sysdbaalter session set container=服务名; --如果使用 pdb 需要切换到 pdb 修改。alter user 用户名 identified by 密码;</code>
登录后复制

注意:配置完服务器端的sqlnet.ora文件后,务必要重新修改密码,否则仍登录失败

3、打补丁报错

打补丁报错 Prerequisite check "CheckActiveFilesAndExecutables" failed。

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">testrac1:~# /app/app/19.0.0.0/grid/OPatch/opatchauto apply /app/soft/32226239OPatchautosession is initiated at Thu Mar  415:27:50 2022Systeminitialization log file is /app/app/19.0.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2022-03-04_03-27-53PM.log.Sessionlog file is /app/app/19.0.0.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-04_03-28-19PM.logTheid for this session is U4JFExecutingOPatch prereq operations to verify patch applicability on home/app/app/oracle/product/19.0.0.0/dbhome_1ExecutingOPatch prereq operations to verify patch applicability on home/app/app/19.0.0.0/gridPatchapplicability verified successfully on home /app/app/19.0.0.0/gridPatchapplicability verified successfully on home/app/app/oracle/product/19.0.0.0/dbhome_1Executingpatch validation checks on home /app/app/19.0.0.0/gridPatchvalidation checks successfully completed on home /app/app/19.0.0.0/gridExecutingpatch validation checks on home /app/app/oracle/product/19.0.0.0/dbhome_1Patchvalidation checks successfully completed on home/app/app/oracle/product/19.0.0.0/dbhome_1VerifyingSQL patch applicability on home /app/app/oracle/product/19.0.0.0/dbhome_1"/bin/sh-c 'cd /app/app/oracle/product/19.0.0.0/dbhome_1;ORACLE_HOME=/app/app/oracle/product/19.0.0.0/dbhome_1 ORACLE_SID=piccyx1/app/app/oracle/product/19.0.0.0/dbhome_1/OPatch/datapatch -prereq-verbose'" command failed with errors. Please refer to logs for more details.SQL changes, if any, can be analyzed by manually retrying the same command.SQLpatch applicability verified successfully on home/app/app/oracle/product/19.0.0.0/dbhome_1Preparingto bring down database service on home /app/app/oracle/product/19.0.0.0/dbhome_1Successfullyprepared home /app/app/oracle/product/19.0.0.0/dbhome_1 to bring down databaseserviceBringingdown CRS service on home /app/app/19.0.0.0/gridPrepatchoperation log file location: /app/app/grid/crsdata/testrac1/crsconfig/crs_prepatch_apply_inplace_testrac1_2022-03-04_03-29-01PM.logCRSservice brought down successfully on home /app/app/19.0.0.0/gridPerformingprepatch operation on home /app/app/oracle/product/19.0.0.0/dbhome_1Perpatchoperation completed successfully on home/app/app/oracle/product/19.0.0.0/dbhome_1Startapplying binary patch on home /app/app/oracle/product/19.0.0.0/dbhome_1Failedwhile applying binary patches on home /app/app/oracle/product/19.0.0.0/dbhome_1Executionof [OPatchAutoBinaryAction] patch action failed, check log for more details.Failures:PatchTarget : testrac1->/app/app/oracle/product/19.0.0.0/dbhome_1 Type[rac]Details:[---------------------------PatchingFailed---------------------------------Commandexecution failed during patching in home:/app/app/oracle/product/19.0.0.0/dbhome_1, host: testrac1.Commandfailed: /app/app/oracle/product/19.0.0.0/dbhome_1/OPatch/opatchauto  apply /app/soft/32226239 -oh/app/app/oracle/product/19.0.0.0/dbhome_1 -target_type rac_database -binary-invPtrLoc /app/app/19.0.0.0/grid/oraInst.loc -jre/app/app/19.0.0.0/grid/OPatch/jre -persistresult/app/app/oracle/product/19.0.0.0/dbhome_1/opatchautocfg/db/sessioninfo/sessionresult_testrac1_rac_2.ser-analyzedresult /app/app/oracle/product/19.0.0.0/dbhome_1/opatchautocfg/db/sessioninfo/sessionresult_analyze_testrac1_rac_2.serCommandfailure output: ==Followingpatches FAILED in apply:Patch:/app/soft/32226239/32218454Log:/app/app/oracle/product/19.0.0.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-04_15-30-20PM_1.logReason: Failed during Patching:oracle.opatch.opatchsdk.OPatchException: Prerequisite check"CheckActiveFilesAndExecutables" failed. Afterfixing the cause of failure Run opatchauto resume]OPATCHAUTO-68061:The orchestration engine failed.OPATCHAUTO-68061:The orchestration engine failed with return code 1OPATCHAUTO-68061:Check the log for more details.OPatchAutofailed.OPatchautosession completed at Thu Mar  4 15:31:152022Timetaken to complete the session 3 minutes, 25 seconds opatchauto failed with error code 42</code>
登录后复制

查看日志

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">tail -100f/app/app/oracle/product/19.0.0.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-04_15-30-20PM_1.log[Mar4, 2022 3:31:14 PM] [INFO]     Finishfuser command /bin/fuser /app/app/oracle/product/19.0.0.0/dbhome_1/bin/expdp atThu Mar 04 15:31:14 CST 2021[Mar4, 2022 3:31:14 PM] [INFO]    Followingactive executables are not used by opatch process :                                /app/app/oracle/product/19.0.0.0/dbhome_1/lib/libclntsh.so.19.1                                 /app/app/oracle/product/19.0.0.0/dbhome_1/lib/libsqlplus.so                              Followingactive executables are used by opatch process :[Mar4, 2022 3:31:14 PM] [INFO]    Prerequisite check "CheckActiveFilesAndExecutables" failed.                                    The detailsare: Following active executables are not used byopatch process :                                    /app/app/oracle/product/19.0.0.0/dbhome_1/lib/libclntsh.so.19.1                               /app/app/oracle/product/19.0.0.0/dbhome_1/lib/libsqlplus.so  Following active executables are used byopatch process :[Mar4, 2022 3:31:15 PM] [SEVERE]   OUI-67073:UtilSessionfailed: Prerequisite check "CheckActiveFilesAndExecutables" failed.[Mar4, 2022 3:31:15 PM] [INFO]     FinishingUtilSession at Thu Mar 04 15:31:15 CST 2022[Mar4, 2021 3:31:15 PM] [INFO]     Log filelocation: /app/app/oracle/product/19.0.0.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-04_15-30-20PM_1.log</code>
登录后复制

查看进程占用情况

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">fuser/app/app/oracle/product/19.0.0.0/dbhome_1/lib/libclntsh.so.19.1/app/app/oracle/product/19.0.0.0/dbhome_1/lib/libclntsh.so.19.1:89500m 109054m</code>
登录后复制

kill 掉占用的进程

kill-9 89500

kill-9 109054

验证没有进程占用

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">fuser/app/app/oracle/product/19.0.0.0/dbhome_1/lib/libsqlplus.sofuser /app/app/oracle/product/19.0.0.0/dbhome_1/lib/libclntsh.so.19.1</code>
登录后复制

继续打补丁

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">testrac1:~# /app/app/19.0.0.0/grid/OPatch/opatchauto resume</code>
登录后复制
4、CRS-6706 patchlevel 不一致

19.3.RAC 的 2 节点打补丁失败,导致2节点集群无法启动报错:

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">[root@testrac2 soft]#/u01/app/19.0.0.0/grid/bin/crsctl start crsCRS-6706: OracleClusterware Release patch level ('4203896349') does not match Software patchlevel ('724960844'). Oracle Clusterware cannot be started.CRS-4000: Command Startfailed, or completed with errors.</code>
登录后复制

从报错补丁 patch level 不一致导致。然后查看 mos

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">1.  Run the following command as the root user tocomplete the patching set up behind the scenes:#GI_HOME/bin:>  ./clscfg -localpatch2.  Run the following command as the root user tolock the GI home:#GI_HOME/crs/install:>  ./rootcrs.sh -lock3.  Run the following command as the root user tostart the GI:#GI_HOME/bin:>  ./crsctl start crs执行:[root@testrac2 bin]#./clscfg -localpatch[root@testrac2install]# ./rootcrs.sh -lock[root@testrac2 bin]#./crsctl start crs</code>
登录后复制

然后集群可以启动。

参考文档:

代码语言:javascript代码运行次数:0运行复制
<code class="javascript">CRS-6706: OracleClusterware Release patch level ('nnn') does not match Software patch level('mmm') (文档 ID 1639285.1)Patching 12.2.0.1 GridInfrastructure gives error CRS-6706: Oracle Clusterware Release Patch Level('748994161') Does Not Match Software Patch Level (文档 ID 2348013.1)</code>
登录后复制
5、内存大页配置过低 ORA-27106

由于内存大页配置小于 SGA 导致数据库无法启动。可调大HugePages内存大页或者改小 SGA,对于HugePages内存大页设置问题后面单独说明。

Oracle 19c RAC 遇到的几个问题

以上就是Oracle 19c RAC 遇到的几个问题的详细内容,更多请关注php中文网其它相关文章!

最佳 Windows 性能的顶级免费优化软件
最佳 Windows 性能的顶级免费优化软件

每个人都需要一台速度更快、更稳定的 PC。随着时间的推移,垃圾文件、旧注册表数据和不必要的后台进程会占用资源并降低性能。幸运的是,许多工具可以让 Windows 保持平稳运行。

下载
来源:php中文网
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系admin@php.cn
最新问题
开源免费商场系统广告
热门教程
更多>
最新下载
更多>
网站特效
网站源码
网站素材
前端模板
关于我们 免责申明 举报中心 意见反馈 讲师合作 广告合作 最新更新 English
php中文网:公益在线php培训,帮助PHP学习者快速成长!
关注服务号 技术交流群
PHP中文网订阅号
每天精选资源文章推送
PHP中文网APP
随时随地碎片化学习

Copyright 2014-2025 https://www.php.cn/ All Rights Reserved | php.cn | 湘ICP备2023035733号