在自己的虚拟机的做实验，突然发现使用PL/SQL Developer无法连接到数据库，报错ORA-12514，说是监听没有启动。
先介绍虚拟机一下环境：redhat7.2+GI 12.2.0.1+Oracle 12.2.0.1，为了测试12.2的ASM特性安装了GI。平时监听程序默认是开启启动的。但是今天不知道为什么没有启动。使用crsctl查看资源状态：发现监听的状态确实是OFFLINE状态
[root@rhel7 .oracle]# crsstat--------------------------------------------------------------------------------Name Target State Server State details --------------------------------------------------------------------------------Local Resources--------------------------------------------------------------------------------ora.DATA.dg ONLINE ONLINE rhel7 STABLEora.LISTENER.lsnr ONLINE OFFLINE rhel7 STABLEora.asm ONLINE ONLINE rhel7 Started,STABLEora.ons OFFLINE OFFLINE rhel7 STABLE--------------------------------------------------------------------------------Cluster Resources--------------------------------------------------------------------------------ora.cssd 1 ONLINE ONLINE rhel7 STABLEora.diskmon 1 OFFLINE OFFLINE STABLEora.driver.afd 1 ONLINE ONLINE rhel7 STABLEora.evmd 1 ONLINE ONLINE rhel7 STABLEora.ora12c.db 1 ONLINE ONLINE rhel7 Open,HOME=/u01/app/o racle/product/12.2/d b_home1,STABLE--------------------------------------------------------------------------------
尝试手动启动监听，依然报错：
[grid@rhel7 ~]$ srvctl start listenerPRCR-1079 : Failed to start resource ora.LISTENER.lsnrCRS-5016: Process "/u01/app/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/12.2/grid/diag/crs/rhel7/crs/trace/ohasd_oraagent_grid.trc"CRS-5016: Process "/u01/app/grid/bin/lsnrctl" spawned by agent "ORAAGENT" for action "start" failed: details at "(:CLSN00010:)" in "/u01/app/12.2/grid/diag/crs/rhel7/crs/trace/ohasd_oraagent_grid.trc"CRS-2674: Start of 'ora.LISTENER.lsnr' on 'rhel7' failed
根据提示查看trc文件，看到如下报错：
LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 15-NOV-2017 20:03:28Copyright (c) 1991, 2016, Oracle. All rights reserved.Starting /u01/app/grid/bin/tnslsnr: please wait...TNSLSNR for Linux: Version 12.2.0.1.0 - ProductionSystem parameter file is /u01/app/grid/network/admin/listener.oraLog messages written to /u01/app/12.2/grid/diag/tnslsnr/rhel7/listener/alert/log.xmlListening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rhel7)(PORT=1521)))Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))TNS-12555: TNS:permission denied TNS-12560: TNS:protocol adapter error TNS-00525: Insufficient privilege for operation Linux Error: 1: Operation not permittedListener failed to start. See the error message(s) above...
看到Insufficient privilege for operation这个字样觉得很纳闷，怎么会权限不足呢，于是尝试用root直接启动监听，依然报错：
[root@rhel7 .oracle]# lsnrctl startLSNRCTL for Linux: Version 12.2.0.1.0 - Production on 15-NOV-2017 20:22:30Copyright (c) 1991, 2016, Oracle. All rights reserved.Starting /u01/app/grid/bin/tnslsnr: please wait...TNS-12546: TNS:permission denied TNS-12560: TNS:protocol adapter error TNS-00516: Permission denied Linux Error: 13: Permission denied
于是各种百度，下面把百度到内容列出来，可能会对看此文的同学有用，但是对我这种情况没有用：
主要是说 /var/tmp/.oracle、/tmp/.oracle 这两个目录的权限访问问题。 进入 一看，我的/var/tmp/.oracle权限 没问题，而/tmp/.oracle压根就没有这个文件。
于是直接查MOS，看有没有相关的文档，找到两篇文档：
Starting the Listener Fails With: TNS-12557 or TNS-12555: TNS:Permission Denied (文档 ID 343253.1)
Listener Fails To Start With IPC Permission Errors (TNS-12546 TNS-12555 TNS-00516 TNS-00525) (文档 ID 434062.1)
对比了文档中列出的问题，跟我的情况也不一相，看到最后发现这样一句话：
4. If you find that there are no adapters linked or they have errors (such as "Permission denied") then issue a "relink all"
Reference:
Doc ID 1467060.1
于是只有用这种方法来试试了，由于crs使用的是grid home下的监听命令所以对grid home做relink all操作。可是又出现报错：
[grid@rhel7 bin]$ relink all The Oracle home in which you are running this relinking tool does not have proper write permissions. Please run this relink script as the sameuser who owns the Oracle home and ensure that the Oracle home has thepermissions from the original installation. If this is a Grid Infrastructure home, please refer to the documentation for the proper steps to relink and apply oneoff patches.
意思是说权限不足，使用root执行，又报错说不能用root执行
[root@rhel7 bin]# relink allThe relink script cannot be run as root.
又查看grid home目录权限
[root@rhel7 app]# ls -ld gridtotal 8drwxr-x--- 84 root oinstall 4096 Jul 18 20:26 grid
原来owner是root，怪不得第一次执行不成功，修改owner(应该直接chmod也可以，这里没有做测试)，重新执行relink all
[root@rhel7 app]# chown grid grid[grid@rhel7 ~]$ relink allwriting relink log to: /u01/app/grid/install/relink.log
成功后再次启动监听，启动成功。
[grid@rhel7 ~]$ lsnrctl startLSNRCTL for Linux: Version 12.2.0.1.0 - Production on 15-NOV-2017 20:50:59Copyright (c) 1991, 2016, Oracle. All rights reserved.Starting /u01/app/grid/bin/tnslsnr: please wait...TNSLSNR for Linux: Version 12.2.0.1.0 - ProductionSystem parameter file is /u01/app/grid/network/admin/listener.oraLog messages written to /u01/app/12.2/grid/diag/tnslsnr/rhel7/listener/alert/log.xmlListening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rhel7)(PORT=1521)))Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=rhel7)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux: Version 12.2.0.1.0 - ProductionStart Date 15-NOV-2017 20:51:00Uptime 0 days 0 hr. 0 min. 0 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File /u01/app/grid/network/admin/listener.oraListener Log File /u01/app/12.2/grid/diag/tnslsnr/rhel7/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rhel7)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))The listener supports no servicesThe command completed successfully
至次问题解决。
总结
以上所述是小编给大家介绍的Oracle 12.2监听无法启动解决方法，希望对大家有所帮助，如果大家有任何疑问请给我留言，小编会及时回复大家的。在此也非常感谢大家对脚本之家网站的支持！
您可能感兴趣的文章:
- OracleOraDb10g_home1TNSListener服务无法启动怎么解决
- 修改计算机名或IP后Oracle10g服务无法启动的解决方法
- oracle修改SGA后无法启动问题分析及解决方法
