Re: monitoring listener.log

Hi,
Typical errors in sql*net traces are like this: nserror: nsres: id=0, op=67, ns=12571, ns2=12560; nt[0]=533, nt[1]=57, nt[2]=0
Means:
You get protocol error 57. If you are using TCP/IP, check winsock errors, if I'm not wrong it should be 20057 or 10057. This error causes sql*net 533 error. 533,12560 and 12571 are result. Saurabh Sharma wrote:

hey
can u elaborate how do u scan each log file, and convert it in email msg.how do u do this.. saurabh
sharmadba 
<blockquote

style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px"> ----- Original Message -----

<div

  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black">From: NGUYEN
Philippe (Cetelem)

To: Multiple
recipients of list ORACLE-L

Sent: Wednesday, April 25, 2001 9:10
PM

Subject: monitoring listener.log
 Hi list,
We have a script wich monitor the alert.log for each database. This script scan the alert.log file and send an email if an ORA-xxx error occured
Now, we want to write a script monitoring the listener.log file : wich kind of message or variable indicate a network  problem (ORA-xxx, ...) ?
...then we 'll have the same question
for the log file made by OEM !
TIA Received on Fri Apr 27 2001 - 08:12:35 CDT