Oracle体系结构初探：监听日志的开启关闭

关于监听的作用与基本知识在【Oracle体系结构初探】这个专栏中都有两篇文章都已经提到：session与process、Oracle网络结构。因为今天遇到了Oracle监听日志的相关问题，所以想补充一篇文章说下Oracle监听日志的开启与关闭。

监听日志可以用于监控哪些客户端与服务端建立了连接，在排查问题时会发挥一定的作用。但是对于一些连接特别频繁的数据库，有些项目可能担心监听日志满了（超过4G）会影响到数据库，要求关闭监听日志。

注意以下命令都不需要加分号 -- “;”

否则会报错

• 查看监听日志是否开启

进入LSNRCTL命令行

lsnrctl

查看监听日志状态

show log_status

#实际操作

LSNRCTL> show log_status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
LISTENER parameter "log_status" set to ON
The command completed successfully

• 关闭监听日志

set log_status off

• 保存修改配置

save_config

#实际操作

LSNRCTL> set log_status off
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
LISTENER parameter "log_status" set to OFF
The command completed successfully
LSNRCTL> save_config
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
Saved LISTENER configuration parameters.
Listener Parameter File   /u01/app/oracle/product/19c/db_1/network/admin/listener.ora
Old Parameter File   /u01/app/oracle/product/19c/db_1/network/admin/listener.bak
The command completed successfully
LSNRCTL> show log_status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
LISTENER parameter "log_status" set to OFF
The command completed successfully

• 开启监听日志

set log_status on

开启后记得再次 save_config 保存修改配置。

#实际操作

set log_status on
save_config
LSNRCTL> set log_status on
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
LISTENER parameter "log_status" set to ON
The command completed successfully
LSNRCTL> save_config
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
Saved LISTENER configuration parameters.
Listener Parameter File   /u01/app/oracle/product/19c/db_1/network/admin/listener.ora
Old Parameter File   /u01/app/oracle/product/19c/db_1/network/admin/listener.bak
The command completed successfully
LSNRCTL> show log_status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle19c)(PORT=1521)))
LISTENER parameter "log_status" set to ON
The command completed successfully