Use the ass. awk script to analyze the trace file generated by systemstate

In the past, many customers and friends used to look for the ass109.awk script to analyze the trace file generated by systemstate.
Because the ass109.awk file was originally written by a foreigner in Oracle, it was not a product of Oracle, and it was not supported by Oracle.
In LTOM431, the ass109.awk script is provided:
Sftp> lpwd
E:/CRT-temp/tools/ltom431/ltom/tom_base/tom/src
Sftp> pwd
/Rootwork
Sftp> lls
Ass109.awk dumptracebuffer. sh errorstack. sh
Flush. sh goiostat. sh govmstat. sh
Ha. sh haLevel. sh hfile. sh
Initiostat. sh initvmstat. sh ksdwrf. sh
Lc2.sh lc4.sh liststatspack. sh
Ltom. jar ltomHeader.txt ltommail. sh
Monlatch. lst pha. sh prelim. sh
Prelimss. sh prha. sh processstate. sh
Prss. sh pss. sh rhaLevel. sh
Rss. sh runfile. sh session_statspack.sh
Spcpkg. lis spalb. lis spcusr. lis
Sprepins. SQL ss. sh statspack. sh
Testee. sh tom92spreport. SQL tomsprepins. SQL
Tomspreport. SQL topaix. sh tracebufferoff. sh
Tracebuffeon. sh
Sftp>
How to use ass. awk:
D: \> awk-f ass109.awk edw_ora_8371.trc
..........................
Ass. Awk Version 1.0.9-Processing edw_ora_8371.trc
System State 1
~~~~~~~~~~~~~~~~
1:
2: waiting for 'rdbms ipc message' wait
3: waiting for 'pmon timer' wait
4: waiting for 'rdbms ipc message' wait
5: waiting for 'rdbms ipc message' wait
6: waiting for 'rdbms ipc message' wait
7: waiting for 'rdbms ipc message' wait
8:
9: waiting for 'rdbms ipc message' wait
10:
11: waiting for 'rdbms ipc message' wait
12: for 'streams AQ: waiting for time management or cleanup tasks 'Wait
13: waiting for 'rdbms ipc message' wait
14: waiting for 'streams AQ: qmn coordinator idle wait' wait
15: waiting for 'rdbms ipc message' wait
16: waiting for 'wait for shrink lock' Wait
17: waiting for 'smon timer 'wait
18: waiting for 'SQL * Net message from client' wait
19: waiting for 'rdbms ipc message' wait
21: waiting for 'rdbms ipc message' wait
23: waiting for 'rdbms ipc message' wait
25: waiting for 'SQL * Net message from client' wait
27: waiting for 'SQL * Net message from client' wait
29: last wait for 'ksdxexeotherwait' [Rcache object = 4f4e57138,]
Cmd: Insert
30: waiting for 'streams AQ: qmn slave idle wait' wait
33: for 'streams AQ: waiting for messages in the queue 'Wait
Blockers
~~~~~~~~
Above is a list of all the processes. If they are waiting for a resource
Then it will be given in square brackets. Below is a summary of
Waited upon resources, together with the holder of that resource.
Notes:
~~~~~
O A process id '??? 'Implies that the holder was not found in
Systemstate.
Resource Holder State
Rcache object = 4f4e57138, 16: waiting for 'wait for shrink lock'
Object Names
~~~~~~~~~~~~
Rcache object = 4f4e57138,
 
77807 Lines Processed.
From the above analysis, we can see that:
Rcache object = 4f4e57138, 16: waiting for 'wait for shrink lock'
Indicates that the blocker of the current database is the database's No. 16 process (pid 16 in systemstate). He holds the Row Cache lock of the object 4f4e57138, while pid 16 is waiting for: Wait for shrink lock.
29: last wait for 'ksdxexeotherwait' [Rcache object = 4f4e57138,]
Cmd: Insert
Here, it is clearly pointed out that the final wait of the process on the 29th is on the 4f4e57138 object, which is currently suspended and cannot be executed, blocking its formal pid 16
However, LTOM is no longer developed. Many of his functions are integrated into ASH:
IMPORTANT: LTOM is a legacy tool and is no longer being developed.
Much of the functionality is now available within the Active Session History (ASH ).
For details see: Document 243132.1 Analysis of Active Session History (Ash) Online and Offline