ORA-27101异常处理

系统：CentOS 7.9
数据库：oracle 19.15
问题描述：节点2从19.14升级到19.15成功后，执行./datapatch -verbose指令时报错ORA-27101，如下所示：
[oracle@hisdb2 OPatch]$ ./datapatch -verbose
SQL Patching tool version 19.15.0.0.0 Production on Tue May 31 12:03:51 2022
Copyright (c) 2012, 2022, Oracle. All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_30790_2022_05_31_12_03_51/sqlpatch_invocation.log

Connecting to database...
Error: prereq checks failed!
Database connect failed with: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4475
Additional information: 1130588979 (DBD ERROR: OCISessionBegin)

Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_30790_2022_05_31_12_03_51/sqlpatch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Tue May 31 12:03:52 2022

查看log文件
[oracle@hisdb2 ~]$ cat /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_30790_2022_05_31_12_03_51/sqlpatch_invocation.log
......
[2022-05-31 12:03:52]
[2022-05-31 12:03:52] Connecting to database...[2022-05-31 12:03:52]
[2022-05-31 12:03:52] Error: prereq checks failed!
[2022-05-31 12:03:52] Database connect failed with: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4475
Additional information: 1130588979 (DBD ERROR: OCISessionBegin)
......

经查询资料，一般情况下造成此异常原因为在同一个服务器上，使用了不同的ORACLE_HOME.
不过此处是由于数据库没有开启造成，节点2开启数据库后 ./datapatch -verbose成功执行.
如下：

[oracle@hisdb2 OPatch]$ ./datapatch -verbose
SQL Patching tool version 19.15.0.0.0 Production on Tue May 31 12:57:53 2022
Copyright (c) 2012, 2022, Oracle. All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_44944_2022_05_31_12_57_53/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 33808367 (OJVM RELEASE UPDATE: 19.15.0.0.220419 (33808367)):
Binary registry: Installed
SQL registry: Not installed

Current state of release update SQL patches:
Binary registry:
19.15.0.0.0 Release_Update 220331125408: Installed
SQL registry:
Applied 19.15.0.0.0 Release_Update 220331125408 successfully on 22-MAY-22 12.32.02.272029 PM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
No interim patches need to be rolled back
No release update patches need to be installed
The following interim patches will be applied:
33808367 (OJVM RELEASE UPDATE: 19.15.0.0.220419 (33808367))

Installing patches...
Patch installation complete. Total patches installed: 1

Validating logfiles...done
Patch 33808367 apply: SUCCESS
logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/33808367/24680225/33808367_apply_ORCL_2022May31_12_58_21.log (no errors)
SQL Patching tool complete on Tue May 31 12:58:23 2022

Linux执行可执行文件提示No such file or directory的解决方法

Linux执行可执行文件提示No such file or directory的解决方法，文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值，需要的朋友们下面随着小编来一起学习学习吧

最近在使用Linux操作系统执行一个可执行文件，结果出现了No such file or directory的提示，表示很疑惑。

查看文件信息，可以看到文件是存在的，并且是可以执行的。

查阅资料后，原因是系统位数与该可执行文件需要的lib库位数不匹配。

用uname命令打印系统信息，发现系统是64位系统

用file命令查看文件信息，发现是一个32位可执行文件。

要想在64位系统上与运行32位程序，则需要安装32位lib库。

对于Ubuntu用户可以使用下面的命令安装。

过程中有可能找不到需要的库，但是会有几个替代包，选择安装其中一个。

然后就可以正常运行之前的可执行文件了。

遇到这种问题其实还有可能是其他原因，例如文本的编码格式问题等，本文仅提出了一种解决方法，读者遇到相同问题要具体问题具体分析。

到此这篇关于Linux执行可执行文件提示No such file or directory的解决方法的文章就介绍到这了,希望大家以后多多支持！