Managers,
I had one response from Sandro Martins, thankyou Sandro
>
>
> If your Oracle listener port are blocked, you can just kill
> the listener
> processes ("ps -ef |grep tns") and than start them again.
>
> kill -9 xxxx
> lsntctl start {listener_name}
>
> Rgds,
>
The problem was that we could not start the oracle listeners at all.
Something had the ports in use... We don't know what caused the problem but
a good old reboot fixed it. At the moment it is not worth spending the time
and effort to get to the root cause unless it happens again!
We did find out some useful information from Compaq such as lsof and the
following;
------------------------------------
Basically "netstat -A" gives PCB values which can be used to
find the PID of the process using the port. So find the entry in "netstat
-A" which applies to the port you are interested in and make a note of the
corresponding PCB, it should be the value in the first column of the output.
Then use the following command to get all ports/sockets being used by
processes;
# echo "socket;quit" | kdbx -k /vmunix > /var/tmp/opensockets
Then search the output file /var/tmp/opensockets for the PCB value and find
the Process ID line just above. That should give the pid of the process
causing the problem.
The output file contents should look like this;
[Process ID: 442]
k0x02cdb980 k0x04f5b340 DGRAM k0x02ecb880 0 0 0 0
k0x03a3dc80 k0x04f5b500 DGRAM k0x02ec4000 0 0 0 0
k0x03a3db80 k0x04f5b6c0 DGRAM k0x04f58480 0 0 0 0
k0x03a3d6c0 k0x04f5b880 DGRAM k0x04f58900 0 0 0 0
Of course you can use "ps" to find the process from the PID. (# ps ax |grep
<PID>)
----------------------------------------------------
Yours,
Charlotte
>
> Managers,
>
> I was trying to do a change on one half of a cluster, a
> rolling upgrade from
> 4.0d to 4.0f. The very first step was to fail over the
> services from one
> side to the other. The service failed over ok, but the
> listeners associated
> with the oracle database would not start up as the ports were locked.
>
> netstat -a shows lots of tcp ports open for this service in
> establised and
> close_wait state. Is there any way that these can be freed
> without rebooting
> the box?
>
> Charlotte
>
Received on Mon Jul 10 2000 - 14:34:40 NZST