How do we read Listener.log file ?

[vr76413]

Hello all..

I have this Listener.log file...where i have a webserver trying to connect to this Unix Box which has database 9.0.1 version.

Now my webserver which uses ODBC connection to connect to ORacle 9.0.1 , after certain period of time loses its connection to the database...

si i want to see when exactly its loosing its connection. I guess i need to look into Listener.log file to see the connection times.

This is what my listener.log looks like...
********************************************************************
Trace level is currently 0
15-JAN-2003 14:51:17 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=ora2.dpi.state.nc.us)(
USER=oracle901b))(COMMAND=reload)(ARGUMENTS=64)(SERVICE=LISTENER901)(VERSION=150999040)) * reload * 0
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=149.168.35.22)(PORT=2482))(PRESENTATION=GIOP)(SESSION=RAW ))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=149.168.35.22)(PORT=2481))(PRESENTATION=GIOP)(SESSION=RAW) )
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)HOST=149.168.35.22)(PORT=9090))(PRESENTATION=http://admin)(SESSION=RAW))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=8080))(PRESENTATION=http://admin)(SESSION=RAW))
15-JAN-2003 14:51:17 * service_register * heat901t * 12542
TNS-12542: TNS:address already in use
TNS-12560: TNSrotocol adapter error
TNS-00512: Address already in use
Solaris Error: 125: Address already in use
15-JAN-2003 15:01:19 * service_update * heat901t * 0
15-JAN-2003 15:21:23 * service_update * heat901t * 0
15-JAN-2003 15:31:25 * service_update * heat901t * 0
15-JAN-2003 15:41:27 * service_update * heat901t * 0
15-JAN-2003 15:51:29 * service_update * heat901t * 0
15-JAN-2003 16:01:31 * service_update * heat901t * 0
15-JAN-2003 16:11:33 * service_update * heat901t * 0
15-JAN-2003 16:15:43 * (CONNECT_DATA=(SERVICE_NAME=heat901t)(CID=(PROGRAM=C:\Pro
gram Files\HEAT\CallLog32.exe)(HOST=PEDPIHEAT)(USER=Administrator))) * (ADDRESS=
(PROTOCOL=tcp)(HOST=199.90.6.227)(PORT=2676)) * establish * heat901t * 0
15-JAN-2003 16:20:41 * service_update * heat901t * 0
15-JAN-2003 16:30:43 * service_update * heat901t * 0
15-JAN-2003 16:40:45 * service_update * heat901t * 0
15-JAN-2003 16:59:31 * (CONNECT_DATA=(SERVICE_NAME=heat901t)(CID=(PROGRAM=C:\WIN
NT\System32\dllhost.exe)(HOST=PEDPIHEAT)(USER=IUSR_PEDPIHEAT))) * (ADDRESS=(PROT
OCOL=tcp)(HOST=199.90.6.227)(PORT=3503)) * establish * heat901t * 0
15-JAN-2003 17:00:49 * service_update * heat901t * 0
15-JAN-2003 17:02:02 * (CONNECT_DATA=(SERVICE_NAME=heat901t)(CID=(PROGRAM=C:\Pro
gram Files\HEAT\CallLog32.exe)(HOST=PEDPIHEAT)(USER=Administrator))) * (ADDRESS=
(PROTOCOL=tcp)(HOST=199.90.6.227)(PORT=3550)) * establish * heat901t * 0
15-JAN-2003 17:10:51 * service_update * heat901t * 0
15-JAN-2003 17:20:53 * service_update * heat901t * 0
15-JAN-2003 17:30:55 * service_update * heat901t * 0
15-JAN-2003 17:40:57 * service_update * heat901t * 0
15-JAN-2003 17:50:59 * service_update * heat901t * 0
15-JAN-2003 18:01:01 * service_update * heat901t * 0
15-JAN-2003 18:11:03 * service_update * heat901t * 0
15-JAN-2003 18:21:05 * service_update * heat901t * 0
15-JAN-2003 18:31:07 * service_update * heat901t * 0
15-JAN-2003 18:41:09 * service_update * heat901t * 0
15-JAN-2003 18:51:11 * service_update * heat901t * 0
15-JAN-2003 19:01:13 * service_update * heat901t * 0
15-JAN-2003 19:15:34 * service_update * heat901t * 0
15-JAN-2003 19:25:36 * service_update * heat901t * 0
bash-2.05$
****************************************************




Can we make anything out of Listener.log file ?.....I mean how do we read and understand Listener.log file ?...

Thanks and any help is appreciated.

Ron

[Tarry]

Follow these steps to track an error using a log file:
1. Browse the log file for the most recent error that matches the error number you have received from the application. This is almost always the last entry in the log file. Notice that an entry or error stack in the log file is usually many lines in length. In the example earlier in this chapter, the error number was 12207.
2. Starting at the bottom, look up to the first non-zero entry in the error report. This is usually the actual cause. In the example earlier in this chapter, the last non-zero entry is the "ns" error 12560.
3. Look up the first non-zero entry in later chapters of this book for its recommended cause and action. (For example, you would find the "ns" error 12560 under ORA-12560.) To understand the notation used in the error report, see the previous chapter, "Interpreting Error Messages."
4. If that error does not provide the desired information, move up the error stack to the second to last error and so on.
5. If the cause of the error is still not clear, turn on tracing and re-execute the statement that produced the error message. The use of the trace facility is described in detail later in this chapter. Be sure to turn tracing off after you have re-executed the command.

For further info .........
http://otn.oracle.co.kr/docs/oracle7.../NWMSG/ch2.htm