如何解决甲骨文的错误NL-00280，NL-00278，SNL-00016？

Question

目标：启动lsnrctl

"/u01/app/oracle/product/11.2.0/test/network/admin/listener.ora“命令： lsnrctl启动

期望值：成功启动

实数：

[oracle@srvr0 root]$ lsnrctl start "/u01/app/oracle/product/11.2.0/test/network/admin/listener.ora"

LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 10-APR-2020 05:53:00

Copyright (c) 1991, 2011, Oracle.  All rights reserved.

Starting /u01/app/oracle/product/11.2.0/test/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.2.0 - Production
NL-00280: error creating log stream /u01/app/oracle/product/11.2.0/test/network/admin/listener.ora
 NL-00278: cannot open log file
  SNL-00016: snlfohd: error opening file
   Linux Error: 13: Permission denied

Listener failed to start. See the error message(s) above...

含量listener.ora:

test_lsnr=
    (DESCRIPTION-LIST=
        (DESCRIPTION=
            (ADDRESS_LIST=
                (LOAD_BALANCE=OFF)
                (FAILOVER=OFF)
                (ADDRESS=(PROTOCOL=TCP)(HOST=srvr0)(PORT=1600))
            )
            (CONNECT_DATA=
                (SERVER=DEDICATED)
                (SERVICE_NAME=test)
            )
        )
    )
STARTUP_WAIT_TIME_test_lsnr=5
CONNECT_TIMEOUT_test_lsnr=10
LOG_DIRECTORY_test_lsnr=/u01/app/oracle/product/11.2.0/test/network/log
LOG_FILE_test_lsnr=test_lsnr.log
TRACE_LEVEL_test_lsnr=OFF
TRACE_DIRECTORY_test_lsnr=/u01/app/oracle/product/11.2.0/test/network/trace
TRACE_FILE_test_lsnr=test_lsnr.trc
SID_LIST_test_lsnr=
    (SID_LIST=
        (SID_DESC=
            (GLOBAL_DB_NAME=test)
            (SID_NAME=test)
            (ORACLE_HOME=/u01/app/oracle/product/11.2.0/test)
        )
    )

请帮助我解决上述甲骨文问题！

Answer 1

有时，我的Docker容器(linux )也会出现这种情况。如果尝试了这里解释的chmod解决方案(http://raman-kumar.blogspot.com/2020/03/solved-nl-00280-error-creating-log.html；在您的Oracle容器中运行以下代码)：

cd /u01/app/oracle/product/11.2.0/xe/network/log/
touch listener.log
chmod 766 listener.log

，侦听器仍未启动，然后打开一个新终端并执行以下操作：

docker container ls

检查dev-oracle容器的容器ID，例如，类似于9d0dc139ed18。复制它。

docker container kill 9d0dc139ed18

如果你再这样做：

docker container ls

神谕容器应该不见了。继续并重新启动您的码头容器(对接-组成-d，重新启动监听器等)