Home A - Z
Menu

Commit 129c70

2026-01-05 08:57:56 feagor: -/-
oracle/admin/Listener_Rotation.md ..
@@ 7,7 7,8 @@
Let’s run a quick test with a listener in version 19.4 :
- # lsnrctl status listener
+ ```bash
+ lsnrctl status listener
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 03-JAN-2020 21:55:44
@@ 26,7 27,7 @@
Listener Parameter File /u01/app/19_4_0_0/grid/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/collabn2/listener/alert/log.xml
[...]
-
+ ```
Set those 2 parameters with arbitrary values :
LOG_FILE_NUM_LISTENER=8
@@ 38,7 39,7 @@
# lsnrctl start listener
After running some load against the listener, check the state of the plain text log files :
-
+ ```bash
# [ oracle@collabn2:/u01/app/oracle/diag/tnslsnr/collabn2/listener/trace [21:42:04] [19.4.0.0.0 [GRID] SID=GRID] 0 ] #
# ls -lh
total 1.2G
@@ 51,9 52,11 @@
-rw-r-----. 1 oracle oinstall 595K Jan 2 21:32 listener_7.log
-rw-r-----. 1 oracle oinstall 595K Jan 2 21:35 listener_8.log
-rw-r-----. 1 oracle oinstall 209K Jan 2 21:42 listener.log
-
+ ```
I do have a number of files as expected, but they are approximately half the size I imagined. I had no idea that actually, the parameter LOG_FILE_SIZE_listener_name rather defines the size of log_*.xml files :
+ ```bash
+
# [ oracle@collabn2:/u01/app/oracle/diag/tnslsnr/collabn2/listener/trace [21:45:05] [19.4.0.0.0 [GRID] SID=GRID] 0 ] #
# ls -lh ../alert/
total 10M
@@ 68,7 71,7 @@
-rw-r-----. 1 oracle oinstall 1.1M Jan 2 21:35 log_8.xml
drwxr-xr-x. 2 oracle oinstall 4.0K Jan 2 21:35 .
-rw-r-----. 1 oracle oinstall 363K Jan 2 21:44 log.xml
-
+ ```
And plain text listener_*.log files are then rotated accordingly.
I will keep this detail in mind when implementing this useful new feature.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9