Please see my other blog for Oracle EBusiness Suite Posts - EBMentors

Search This Blog

Note: All the posts are based on practical approach avoiding lengthy theory. All have been tested on some development servers. Please don’t test any post on production servers until you are sure.

Tuesday, January 04, 2011

PING with Timestamp

We were getting ORA-3113 errors for some web clients and after investigations, I found that this is due the many network dropouts on all Oracle related servers. I just ran the simple pingtest as below

C:\Documents and Settings\inam>ping 192.168.6.32 -t
Pinging 192.168.16.32 with 32 bytes of data:
Reply from 192.168.16.32: bytes=32 time<1ms TTL=128
Reply from 192.168.16.32: bytes=32 time<1ms TTL=128
Reply from 192.168.16.32: bytes=32 time=1ms TTL=128
Request timed out.
Reply from 192.168.6.32: bytes=32 time<1ms TTL=128

I sent the output related to all servers to Network department and they further demanded that , in order to investigate the issue we need the exact time for timeout.
So i wrote a small script below for them

FileName: pingto_32.bat
@echo off
:Loop
set dt=%date% %time%
echo %dt%
ping 192.168.16.32
goto Loop

and ran it like below

C:\Users\inam>pingto_32 > TestOn4_126_to_32DB1.txt
output of the script was like below
Tue 01/04/2011 14:13:24.00

Pinging 192.168.6.33 with 32 bytes of data:
Reply from 192.168.6.33: bytes=32 time=1ms TTL=128
Request timed out.
Reply from 192.168.16.33: bytes=32 time<1ms TTL=128
Reply from 192.168.16.33: bytes=32 time<1ms TTL=128

No comments: