Symptom
Transactions blocked in IBQ due to lack of resources as long as memory_control=SMART then the flow starts again as soon as the 'memory_control' is set to "off".
=> memory_control set to 'SMART'
'memory_limit' config parameter is: 32768 megabytes.
TICKETS blocked in SRS EXEC(170) and didn't move to the SQT then DIST
T. 2023/11/23 21:19:42. (170): V=2;H1=SD2_c0;PDB(pdb)=11/23/23 21:05:15.360;RA(pdb)=11/23/23 21:19:42:560;EXEC(170)=11/23/23 21:19:42.563;B(170)=12117207936
W. 2023/11/23 21:22:40. WARNING #24068 SQT(161:1 DIST PDS.pdb) - generic/sqt/sqtint.c(1355)
SQT cache size is too low to load more than one transaction into the cache.
admin who, sqt
118 Flow Controlling 161:1 DIST PDS.pdb 0 1 1 2 0 1 0 st:O,cmds:28040,qid:3763960:40:11
...
118 Active 161:1 DIST PDS.pdb 0 1 2 3 0 1 0 st:O,cmds:28040,qid:3763960:40:11
admin stats, mem_detail_stats
Object(State) Memory_Consumed Memory_Consumed_Mb Max_Memory_Consumed_Mb Avg_Memory_Consumed_Mb Memory_Threshold_Mb Memory_Ctrl_Time(s)
-------------- ------------------- ------------------- ------------------------ ------------------------ ------------------- -------------------
IBQ (Norm) 1371994472 1308 1636 1308 1635 37
SQT (Norm) 595452720 567 8833 567 8833 0
Transaction 'st:O,cmds:28040,qid:3763960:40:11' is blocked in IBQ because of lack of resource.
SQT: 'Max_Memory_Consumed_Mb' reached 'Memory_Threshold_Mb' but when 'Memory_Consumed' decreases the transaction remains blocked in the IBQ/SQT
=> memory_control set back to 'OFF'
sqt_max_cache_size 41943040
memory_limit 32768
T. 2023/11/23 21:23:06. (100): V=2;H1=SD2_c0;PDB(pdb)=11/23/23 21:05:15.360;RA(pdb)=11/23/23 21:19:42:560;EXEC(170)=11/23/23 21:19:42.563;B(170)=12117207936;DIST(100)=11/23/23 21:23:06.940
T. 2023/11/23 21:23:06. (59): V=2;H1=SD2_c0;PDB(pdb)=11/23/23 21:05:15.360;RA(pdb)=11/23/23 21:19:42:560;EXEC(170)=11/23/23 21:19:42.563;B(170)=12117207936;DIST(100)=11/23/23 21:23:06.940;RSI(59)=11/23/23 21:23:06.946;RSI_B=33380981000;PRS=RS2
T. 2023/11/23 21:23:07. (146): V=2;H1=SD2_c0;PDB(pdb)=11/23/23 21:05:12.446;RA(pdb)=11/23/23 21:05:12:446;EXEC(170)=11/23/23 21:05:12.449;B(170)=12113843044;DIST(100)=11/23/23 21:23:06.737;DSI(146)=11/23/23 21:23:07.278;DSI_T=9211583;DSI_C=34746552;RRS=RS2
T. 2023/11/23 21:23:07. (146): V=2;H1=SD2_c0;PDB(pdb)=11/23/23 21:05:15.360;RA(pdb)=11/23/23 21:19:42:560;EXEC(170)=11/23/23 21:19:42.563;B(170)=12117207936;DIST(100)=11/23/23 21:23:06.940;DSI(146)=11/23/23 21:23:07.441;DSI_T=9212143;DSI_C=34748844;RRS=RS2
TICKETS from PDB(pdb) that were blocked in SRS EXEC thread, they moved now to SQT/DIST only when changing memory_control to 'OFF'
admin who, sqt
118 Active 161:1 DIST PDS.pdb 0 870 2 872 0 1 0 st:O,cmds:7971,qid:3764144:21:13
Read more...
Environment
SRS 16.0 SP04 PL03 HF1
Product
Keywords
SRS, Repserver, CR#828911, CR828911, 828911, backlog, increase, ,memory_control, SMART , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.