commit 8b7236

2026-01-05 09:02:44 feagor: -/-

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

`oracle/admin/Listener_Rotation.md` ..
@@ 6,7 6,7 @@

	Let’s run a quick test with a listener in version 19.4 :

-	```+ bash
+	``` bash
	lsnrctl status listener

	LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 03-JAN-2020 21:55:44
@@ 33,12 33,12 @@
	LOG_FILE_SIZE_LISTENER=1

	Then restart the listener because a simple reload will not take these modifications into account :
-
-	# lsnrctl stop listener
-	# lsnrctl start listener
-
-	After running some load against the listener, check the state of the plain text log files :
	```bash
+	lsnrctl stop
+	lsnrctl start
+	```
+	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
@@ 54,8 54,7 @@
	```
	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
-
+	```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