tag:blogger.com,1999:blog-4096575.post6230436060534057755..comments2024-03-28T07:44:02.549-04:00Comments on The Arup Nanda Blog: Switching Back to Regular Listener Log FormatArup Nandahttp://www.blogger.com/profile/03392706779349258765noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4096575.post-81356688627416115952013-05-02T21:00:49.678-04:002013-05-02T21:00:49.678-04:00This is cool!
I like your post,visit my homepage h...This is cool!<br />I like your post,visit my homepage here:<br /><a href="http://bestmemoryfoammattressreviews2013.blogspot.com/" rel="nofollow">best memory foam mattress 2013</a>Tara Tylernoreply@blogger.comtag:blogger.com,1999:blog-4096575.post-5909939105876962052013-04-06T19:37:34.485-04:002013-04-06T19:37:34.485-04:00@Anonymous I think you missed the spirit of this p...@Anonymous I think you missed the spirit of this post. You are not doing a log rotation; you are pausing and restarting at a new location. The entries between your log_status off and log_status on will be on no listener log file.<br /><br />A true log rotation simply starts a new logfile. In pre-11g days we used to do that by using:<br /><br />LSNRCTL> set log_file_listener <br /><br />With ADR enabled in 11g, you will get this error:<br /><br />LSNRCTL> set log_file mylog.xml<br />Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))<br />TNS-01251: Cannot set trace/log directory under ADR<br />LSNRCTL> set log_directory /tmp<br />Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))<br />TNS-01251: Cannot set trace/log directory under ADR<br /><br />This is where disabling ADR helps, and what this post describes. <br /><br />Hope this helps.Arup Nandahttps://www.blogger.com/profile/03392706779349258765noreply@blogger.comtag:blogger.com,1999:blog-4096575.post-12575856723970495682013-04-06T10:18:29.717-04:002013-04-06T10:18:29.717-04:00Hi Arup
The log-rotation I'm doing for 11g R2...Hi Arup<br /><br />The log-rotation I'm doing for 11g R2 is no different than with previous versions.<br /><br />Just do this:<br />lsnrctl SET LOG_STATUS OFF<br />mv /listener.log <br />lsnrctl SET LOG_STATUS ON<br /><br />The only difference in 11gR2 was to determine where this logfile is. Since <br /><br />lsnrctl STATUS<br /><br />will give you the default logfile (which is the log.xml in 11gR2) just grep for this line, and replace "alert/log.xml" witch "trace/listener.log"<br /><br />So something like this (untested, don't have my script here):<br /><br />lsnrctl status | grep "Listener Log File" | awk '{print $4}' | sed 's/alert\/log.xml/trace\/listener.log/<br /><br />This can be done for all listeners (TRACE and normal).Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4096575.post-62447524895632470132013-04-06T10:06:39.920-04:002013-04-06T10:06:39.920-04:00@Timur - yes, it does; and I have mentioned it in ...@Timur - yes, it does; and I have mentioned it in the blog too. However this log simply keeps growing. In pre-11g days you could temporarily change the log_file name or directory to create a new one and archive the old one. In 11g, you can't change the file name or the directory unless you set this special parameter.Arup Nandahttps://www.blogger.com/profile/03392706779349258765noreply@blogger.comtag:blogger.com,1999:blog-4096575.post-38460984428117963912013-04-06T05:36:41.293-04:002013-04-06T05:36:41.293-04:00Hi Arup
I think that in addition to the *.xml log...Hi Arup<br /><br />I think that in addition to the *.xml log Oracle also logs usual listener.log in the trace directory. At least this is what I see on most 11.2 installs.Anonymousnoreply@blogger.com