Listener Status Blocked again
hello...
We are running oracle DB 9.0.2 and oracle developer 6i rel2 for the application we have developed on client/server based tecnology..
the listener status is blocked once i go to the lsnrctl i get the status is blocked..once i give the reload command it sets it to ready and then the no of connections increase very rapidly...and set the connection to blocked again...for further investigation of the problem i used etheral for checking the network traffic and found that one of the client machine is making so many connections..that the listener is getting blocked.. when I close the application on the client machine and then give the reload command on the lsnrctl prompt and it sets the status back to ready...
and it works fine for some days and then the same problem happens again...
what can i do to solve this problem of mine ?
schwertner had given me a solution of turning of the firewall of the clients ..which i did and the system worked fine all these days ..but today again the same problem occured ?
anyother options that i should try..
We are running oracle DB 9.0.2 and oracle developer 6i rel2 for the application we have developed on client/server based tecnology..
the listener status is blocked once i go to the lsnrctl i get the status is blocked..once i give the reload command it sets it to ready and then the no of connections increase very rapidly...and set the connection to blocked again...for further investigation of the problem i used etheral for checking the network traffic and found that one of the client machine is making so many connections..that the listener is getting blocked.. when I close the application on the client machine and then give the reload command on the lsnrctl prompt and it sets the status back to ready...
and it works fine for some days and then the same problem happens again...
what can i do to solve this problem of mine ?
schwertner had given me a solution of turning of the firewall of the clients ..which i did and the system worked fine all these days ..but today again the same problem occured ?
anyother options that i should try..
ASKER
the opened sessions are just 42 and max number of sesions is set at a high value..so number of sessions cannot be exceeded..
Did you change the IP of the computer recently?
Or the Domain name of the computer?
Check in listener.ora and sqlnet.ora if the the names are correct.
Check if the network card of the working. Possibly change it.
Check if the computer is not a MultiHome computer ( they have 2 network cards).
Try to ping the computer from the client.
Try to tnsping the computer from the client.
Read carefully the listener.log on the server. Does it says what is wrong?
Or the Domain name of the computer?
Check in listener.ora and sqlnet.ora if the the names are correct.
Check if the network card of the working. Possibly change it.
Check if the computer is not a MultiHome computer ( they have 2 network cards).
Try to ping the computer from the client.
Try to tnsping the computer from the client.
Read carefully the listener.log on the server. Does it says what is wrong?
ASKER
IPs on the network are dymamic (DHCP) only the server has static IP
no change in the domain name
yes the names in the listener.ora and sqlnet..ora are correct
network card ? well asked the network guys to check it they said that the NIC cards are fine
no there is only one NIC card in every machine
ping to the client works
tnsping to the client also works
listener log has grown over 1gb so it takes time to open..:)
no change in the domain name
yes the names in the listener.ora and sqlnet..ora are correct
network card ? well asked the network guys to check it they said that the NIC cards are fine
no there is only one NIC card in every machine
ping to the client works
tnsping to the client also works
listener log has grown over 1gb so it takes time to open..:)
ASKER
increaased the points
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also investigate carefully LISTENER.LOG, ALERT<SID>.LOG and other
log files. The reason will be registered there.
Keep these files short and read them regularly.
log files. The reason will be registered there.
Keep these files short and read them regularly.
what is going on with the one client that it tries to connect so much? Is that an application error?
ASKER
It is not always the same client that blocks the listner ..well in the application we have a timer set which executes certain sql to check if there is any letter that has been transfered to the logged in user..and if there is a letter transffered to the user the timer is set to hide/show a canvas to have a blinking effect...
Attached is the code for the start timer procedure and the trigger for the timer expired
and the listner.log file has grown more that 1 GB and it does not allow me to open gives me a memory error..tried to copy file to a client pc and still it did not let me open it...
SNIPPET.txt
Attached is the code for the start timer procedure and the trigger for the timer expired
and the listner.log file has grown more that 1 GB and it does not allow me to open gives me a memory error..tried to copy file to a client pc and still it did not let me open it...
SNIPPET.txt
ASKER
Even the listener.trc file is 1.6 GB...when I stop the listener can i even rename/delete the trace file and create a new one...
Immediatelly clean these big files.
They cause the error.
Try to find files greater then 2 GB.
32 bit architecture is not able to serve files bigger then 2 GB.
They cause the error.
Try to find files greater then 2 GB.
32 bit architecture is not able to serve files bigger then 2 GB.
ASKER
ok will clear them today ....Even the listener.trc file is 1.6 GB...when I stop the listener can i even rename/delete the trace file and create a new one...
thankx
thankx
Delete them or put them on another machine.
Possible you have files greater the 2 GB.
See also the .dbf files.
Such files are able to stop the Oracle instance ....
alert<SID>.log is one of them,
listener.log is the next
but for first time i see .trc files in size of 1.6 GB.
Great surprise! possibly it is cumulative file and
collects messages appending them.
If it is so try to open it and see what is written there.
Possible you have files greater the 2 GB.
See also the .dbf files.
Such files are able to stop the Oracle instance ....
alert<SID>.log is one of them,
listener.log is the next
but for first time i see .trc files in size of 1.6 GB.
Great surprise! possibly it is cumulative file and
collects messages appending them.
If it is so try to open it and see what is written there.
Also antivirus programs can block ports.
You have also to investigate the opened sessions:
select counts(*) from v$session;
Also investigate the maximum number of the sessions allowed. If this is small
then try to increase the allowed session number. Of course be aware that
every session eats up to 5 MB RAM.