Thank you! Output (three for each process) from oradebug SHORT_STACK is shown
below for Q003 and Q002
SQL> oradebug setospid 10689
Oracle pid: 192, Unix process pid: 10689, image: oracle@ebststdb11 (Q003)
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-kglGetMutex()+100<-kglpnal()+760<-kglpin()+4796<-kglgob()+916<-kwqicgob()+268<-kwqicrqo0()+1088<-kwqbmspmain()+1204<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
SQL>
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-kglpin()+4744<-kglgob()+916<-kwqicgob()+268<-kwqicrqo0()+1088<-kwqbmspmain()+1204<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
SQL>
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-kssrmf_numa_intl()+664<-ksudlc()+692<-kssdel()+196<-ksupop()+712<-kwqbmspmain()+2156<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
SQL> oradebug setospid 24300
Oracle pid: 28, Unix process pid: 24300, image: oracle@ebststdb11 (Q002)
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-knglcpblt()+1304<-knglcpurge()+28<-kwqbmfrmain()+168<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
SQL>
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-knglcpblt()+1300<-kwqbmfrmain()+168<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
SQL>
SQL> oradebug SHORT_STACK
ksedsts()+380<-ksdxfstk()+52<-ksdxcb()+3592<-sspuser()+140<-__sighndlr()+12<-call_user_handler()+868<-sigacthandler()+92<-knglcpblt()+1304<-kwqbmfrmain()+168<-kwqmnslv()+3108<-ksvrdp()+1928<-opirip()+1972<-opidrv()+748<-sou2o()+88<-opimai_real()+512<-ssthrdmain()+324<-main()+316<-_start()+380
@ash_wait_chains.sql username||':'||program2||event2 "program2 like '%Qnn%'"
sysdate-1/24 sysdate
%This SECONDS AAS #Blkrs WAIT_CHAIN
FIRST_SEEN LAST_SEEN
------ ---------- ---------- ------
--------------------------------------------------------------------------------
------------------- -------------------
96% 6273 1.7 3 -> SYS:(Qnnn) ON CPU
2021-07-14 09:04:32 2021-07-14 10:04:31
3% 205 .1 2 -> SYS:(Qnnn) library cache: mutex X
2021-07-14 09:06:36 2021-07-14 10:04:26
0% 25 0 1 -> SYS:(Qnnn) library cache: mutex X ->
SYS:(Qnnn) ON CPU 2021-07-14 09:17:00 2021-07-14 10:04:30
How can I add columns to the ash_wait_chains.sql script output? I would like to
add session_id to the output.
Thanks!
From: Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx>
Sent: Wednesday, July 14, 2021 10:52 AM
To: Hameed, Amir <amir.hameed@xxxxxxxxxxxxxxx>; oracle-l@xxxxxxxxxxxxx
Subject: RE: [EXTERNAL] RE: AQ process waiting on "library cache: mutex X"
Hi Amir,
You could get stacks without the OS access:
Oradebug setorapname (or setorapid or setospid) -you have to connect to AQ
process
oradebug SHORT_STACK
Do a couple of those to see if they repeat.
By the way, you can replace session_type='BACKGROUND' with "program2 like
'%Qnn%'" when you're interested only in AQ processes.
Best regards,
Nenad
From: Hameed, Amir
<amir.hameed@xxxxxxxxxxxxxxx<mailto:amir.hameed@xxxxxxxxxxxxxxx>>
Sent: Mittwoch, 14. Juli 2021 16:43
To: Noveljic Nenad
<nenad.noveljic@xxxxxxxxxxxx<mailto:nenad.noveljic@xxxxxxxxxxxx>>;
oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: RE: [EXTERNAL] RE: AQ process waiting on "library cache: mutex X"
Thank you, Nenad. Please see the output from ASHTOP. The highlighted lines are
Qnnn processes.
@ashtop session_id,username,sql_id,in_parse,sql_opname,top_level_call_name
session_type='BACKGROUND' sysdate-2/24 sysdate
Total
Distinct Distinct
Seconds AAS %This SESSION_ID USERNAME SQL_ID I SQL_OPNAME
TOP_LEVEL_CALL_NAME FIRST_SEEN LAST_SEEN
Execs Seen Tstamps
--------- ------- ------- ---------- --------------- ------------- -
-------------------- ------------------------------ -------------------
------------------- ---------- --------
7103 1.0 54% | 28 SYS N
VERSION2 2021-07-14 07:36:23 2021-07-14
09:36:22 1 7103
5820 .8 44% | 607 SYS N
VERSION2 2021-07-14 07:36:23 2021-07-14
09:36:22 1 5820
91 .0 1% | 1066 SYS N
LOGOFF 2021-07-14 07:36:57 2021-07-14
09:35:56 1 91
78 .0 1% | 452 SYS N
2021-07-14 07:41:21 2021-07-14
09:35:06 1 78
33 .0 0% | 451 SYS N
2021-07-14 07:36:35 2021-07-14
09:35:00 1 33
28 .0 0% | 1 SYS N
2021-07-14 07:41:49 2021-07-14
09:32:59 1 28
20 .0 0% | 602 SYS N
2021-07-14 08:02:00 2021-07-14
09:30:53 1 20
11 .0 0% | 302 SYS N
2021-07-14 07:38:57 2021-07-14
09:28:37 1 11
6 .0 0% | 157 SYS N
VERSION2 2021-07-14 07:37:57 2021-07-14
09:35:00 1 6
5 .0 0% | 1052 SYS N
2021-07-14 07:49:10 2021-07-14
09:28:45 1 5
4 .0 0% | 301 SYS N
2021-07-14 07:58:03 2021-07-14
09:26:02 1 4
2 .0 0% | 21 SYS bunssq950snhf N INSERT
VERSION2 2021-07-14 09:00:33 2021-07-14
09:00:34 1 2
2 .0 0% | 903 SYS N
2021-07-14 07:50:09 2021-07-14
08:27:55 1 2
2 .0 0% | 1053 SYS N
VERSION2 2021-07-14 08:06:16 2021-07-14
08:42:26 1 2
1 .0 0% | 7 SYS N
VERSION2 2021-07-14 07:52:24 2021-07-14
07:52:24 1 1
15 rows selected.
I will try to get pstack of the above two processes. I don't have access to the
oracle account, I will have to ask someone to do it for me.
Thank you!
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to as
"Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version.
Please note that all e-mail communications to and from the Vontobel Group are
subject to electronic storage and review by Vontobel Group. Unless stated to
the contrary and without prejudice to any contractual agreements between you
and Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the
sender. Please note for an exact reference to the affected group entity the
corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult
www.vontobel.com<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vontobel.com%2F&data=04%7C01%7Camir.hameed%40sleepnumber.com%7C632e98772a34429f520708d946d70ae3%7Ced8aabd514de49829fb6d6528851af5e%7C0%7C0%7C637618711706490889%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BLM0wmjm%2FAppLYFLDE6Z6zZcwpC6VRGZWK5p42xTIzk%3D&reserved=0>.