On 8/15/22 15:16, Beckstrom, Jeffrey
wrote:
The most significant event is “:
SID EVENT TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED
---------- --------------------------- ----------- -------------- -----------
AVERAGE_WAIT MAX_WAIT TIME_WAITED_MICRO EVENT_ID WAIT_CLASS_ID WAIT_CLASS#
------------ ---------- ----------------- ---------- ------------- -----------
WAIT_CLASS CON_ID TIME_WAITED_IN_SEC
-------------------- ---------- ------------------
38 SQL*Net message to client 383 0 0
0 0 424 2067390145 2000153315 7
Network 3 .000424
38 db file scattered read 35 0 31
.9 5 314295 506183215 1740759767 8
User I/O 3 .314295
Jeff, I wonder how is it that an experienced DBA like you still hasn't learned one of the basic rules of database administration: whenever it is unclear what's going on, it's a network problem. Network engineers have to prove their innocence, over and over again. You can sweeten the things up by saying that it used to work until yesterday and then by asking them what did they do yesterday? Being a network engineer entails large dose of masochism and equally large dose of sadism. Network engineers are blamed for everything, including the climate change, but they also can prevent any progress in your projects by being strict enough with the firewall.
Your most waited on event is SQL Net message to client.
That means that one of your clients cannot receive data as fast as
Oracle can deliver. Sounds rare, and it is, at least to my
knowledge. This very probably is a network problem.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com-- //www.freelists.org/webpage/oracle-l
