A leap second will be inserted at the end of June.
(used NTP to sync the time)
Any SAP notes talk about this?
Will leap second impact ASE?
Is the following ASE message relay?
Warning: The internal timer is not progressing. If this messages is generated multiple times, report to Sybase Technical Support and restart the server(alarminterval=-577028)
When updating a model from the db the window listing them doesn't have them sorted. I've only seen this problem with ASE. How do I get them sorted?
Since 15.0.x ASE comes with handy PC MDAs - monProcedureCacheMemoryUsage and monProcedureCacheModuleUsage. Both are "essential" in sizing the PC correctly - and analyzing PC behavior for your application & ASE. There counters are very nice but... over time they become user-un-friendly.
Both counters are not absolute point-in-time sample values but rather grow over time. But if they grow - what do they show?
There may be further broken down into sub-allocators.
You'd expect Active to indicate the sample value from the point-of-time of inspection and HWM to indicate the number of memory pages since the startup (i.e. relative to the DaysRunning from the monState). Yet, both behave in the same cumulative manner and both yield useless values if divided into daily portions and compared to say monitorconfig. The same applies to the reuse values packed into these tables.
Anyone tried to make sense of these values? They are essential in configuring PC on the one hand but accumulate over time on the other (and exceed PC size in hundreds of % + are marked as indicator&1). What do these in fact display? How do they relate to monitorconfig? When you restart ASE (or play with these on your private ASE) the numbers seem to make sense. When you analyze them on the real production environment - they only mislead (as does the sysmon bit in the Indicator column related to them).
Any insights?
Thanks,
Andrew
ps. PERFORMANCE SCALABILITY ENHANCEMENTS IN SAP ADAPTIVE SERVER® ENTERPRISE has a neat section on PC sizing which, too, rely on monProcedureCacheModuleUsage. However, the values are taken as simple aggregates - without any respect to their cumulative nature. Was ASE bounced to take correct measurement? How reliable are the HWM/Reuse numbers in that paper?
hi guys!
I test the system for SMP/P/Sun_svr4/OS 5.10/ase160sp01plx/3663/64-bit Adaptive Server Enterprise/16.0 SP01 PL01/EBF 24357 versions.
And during some time frame I receive very high cpu values.
I assumed that it is a spinlock but when I сhecked mon tables I don't find some high values.
I don't understand why values Engine Utilization (Tick %) & Thread Utilization (OS %) so strongly differ?
What different between Engine Utilization (Tick %) & Thread Utilization (OS %) in sysmon?
Also I noted that in comparison with last sample very grew value NetController Activity - Polls & NetController Activity -Polls Returning Events/
with 1000 up to 30000.
What does it mean?
Kernel Utilization
------------------
Engine Utilization (Tick %) User Busy System Busy I/O Busy Idle
------------------------- ------------ ------------ ---------- ----------
ThreadPool : syb_default_pool
Engine 0 68.5 % 1.3 % 14.1 % 16.2 %
Engine 1 70.8 % 0.5 % 14.4 % 14.3 %
Engine 2 70.7 % 0.4 % 14.6 % 14.3 %
Engine 3 69.1 % 0.0 % 15.1 % 15.8 %
Engine 4 69.6 % 1.2 % 14.5 % 14.8 %
Engine 5 68.7 % 0.1 % 15.2 % 16.0 %
Engine 6 70.0 % 0.8 % 14.2 % 14.9 %
Engine 7 70.0 % 0.0 % 14.5 % 15.6 %
Engine 8 69.4 % 0.9 % 14.7 % 14.9 %
Engine 9 68.9 % 0.0 % 15.5 % 15.6 %
Engine 10 70.2 % 0.6 % 14.3 % 14.9 %
Engine 11 70.2 % 0.1 % 14.6 % 15.1 %
Engine 12 71.1 % 0.0 % 14.3 % 14.6 %
Engine 13 69.7 % 0.7 % 14.1 % 15.5 %
Engine 14 71.3 % 0.5 % 13.0 % 15.2 %
Engine 15 69.2 % 0.5 % 14.9 % 15.4 %
Engine 16 70.7 % 0.1 % 13.7 % 15.6 %
Engine 17 69.3 % 0.9 % 14.6 % 15.2 %
Engine 18 68.6 % 0.4 % 14.6 % 16.3 %
Engine 19 70.3 % 0.3 % 14.7 % 14.7 %
Engine 20 68.6 % 1.2 % 14.2 % 16.0 %
Engine 21 68.5 % 0.4 % 15.3 % 15.8 %
Engine 22 70.3 % 0.1 % 13.8 % 15.8 %
Engine 23 69.9 % 0.4 % 14.9 % 14.7 %
Engine 24 69.8 % 0.0 % 14.9 % 15.3 %
Engine 25 69.9 % 0.6 % 14.5 % 14.9 %
Engine 26 70.2 % 0.4 % 14.2 % 15.2 %
Engine 27 70.2 % 0.8 % 13.8 % 15.2 %
Engine 28 69.7 % 0.0 % 14.5 % 15.8 %
Engine 29 70.1 % 0.1 % 14.7 % 15.2 %
Engine 30 69.6 % 0.3 % 15.0 % 15.1 %
Engine 31 71.3 % 0.5 % 13.8 % 14.5 %
Engine 32 70.1 % 0.2 % 15.6 % 14.2 %
Engine 33 69.6 % 1.2 % 14.8 % 14.5 %
Engine 34 70.8 % 0.1 % 14.6 % 14.5 %
Engine 35 70.3 % 0.1 % 14.5 % 15.2 %
Engine 36 69.9 % 0.6 % 14.8 % 14.6 %
Engine 37 69.2 % 0.7 % 14.6 % 15.6 %
Engine 38 71.2 % 0.1 % 14.4 % 14.3 %
Engine 39 68.7 % 0.2 % 15.4 % 15.7 %
Engine 40 70.6 % 0.6 % 14.1 % 14.8 %
Engine 41 71.8 % 0.2 % 14.3 % 13.8 %
Engine 42 70.0 % 0.7 % 14.2 % 15.1 %
Engine 43 68.6 % 0.1 % 15.9 % 15.4 %
Engine 44 69.9 % 0.2 % 15.1 % 14.8 %
Engine 45 69.2 % 0.2 % 15.0 % 15.7 %
Engine 46 70.8 % 0.4 % 14.3 % 14.5 %
Engine 47 70.5 % 0.1 % 14.2 % 15.2 %
Engine 48 70.2 % 1.4 % 14.1 % 14.3 %
Engine 49 70.6 % 0.2 % 14.6 % 14.6 %
Engine 50 68.0 % 2.0 % 14.7 % 15.3 %
Engine 51 68.3 % 0.4 % 15.6 % 15.7 %
Engine 52 71.2 % 0.3 % 14.3 % 14.3 %
Engine 53 69.6 % 0.7 % 14.0 % 15.8 %
Engine 54 69.4 % 0.6 % 15.1 % 14.9 %
Engine 55 70.0 % 0.9 % 14.3 % 14.8 %
Engine 56 72.0 % 0.3 % 13.7 % 14.1 %
Engine 57 69.0 % 0.2 % 15.0 % 15.8 %
Engine 58 70.3 % 0.3 % 14.2 % 15.2 %
Engine 59 71.2 % 0.7 % 13.3 % 14.8 %
Engine 60 69.1 % 1.2 % 14.1 % 15.6 %
Engine 61 71.2 % 0.0 % 13.3 % 15.5 %
Engine 62 69.4 % 0.5 % 14.0 % 16.2 %
Engine 63 69.9 % 0.5 % 14.5 % 15.1 %
Engine 64 70.2 % 0.3 % 14.1 % 15.4 %
Engine 65 70.0 % 0.3 % 14.2 % 15.6 %
Engine 66 70.7 % 0.1 % 14.6 % 14.7 %
Engine 67 69.7 % 0.2 % 13.9 % 16.3 %
Engine 68 69.3 % 0.1 % 14.8 % 15.8 %
Engine 69 69.9 % 0.1 % 14.2 % 15.8 %
Engine 70 71.7 % 0.4 % 13.8 % 14.1 %
Engine 71 71.0 % 0.1 % 13.8 % 15.1 %
Engine 72 70.1 % 0.6 % 14.9 % 14.5 %
Engine 73 69.8 % 0.0 % 14.2 % 16.1 %
Engine 74 70.1 % 0.6 % 14.0 % 15.3 %
Engine 75 71.2 % 0.3 % 14.1 % 14.5 %
------------------------- ------------ ------------ ---------- ----------
Pool Summary Total 5318.3 % 32.7 % 1098.0 % 1151.0 %
Average 70.0 % 0.4 % 14.4 % 15.1 %
------------------------- ------------ ------------ ---------- ----------
Server Summary Total 5318.3 % 32.7 % 1098.0 % 1151.0 %
Average 70.0 % 0.4 % 14.4 % 15.1 %
Average Runnable Tasks 1 min 5 min 15 min % of total
------------------------- ------------ ------------ ---------- ----------
ThreadPool : syb_default_pool
Global Queue 4.5 1.7 0.6 2.8 %
Engine 0 1.8 0.8 0.4 1.1 %
Engine 1 1.6 0.8 0.4 1.0 %
Engine 2 1.9 1.1 0.6 1.2 %
Engine 3 2.5 1.0 0.5 1.5 %
Engine 4 2.5 1.2 0.6 1.5 %
Engine 5 2.0 1.1 0.5 1.2 %
Engine 6 3.1 1.5 0.7 1.9 %
Engine 7 2.6 1.0 0.5 1.6 %
Engine 8 1.5 0.8 0.4 0.9 %
Engine 9 2.3 1.3 0.6 1.4 %
Engine 10 2.1 0.9 0.5 1.3 %
Engine 11 1.3 0.8 0.4 0.8 %
Engine 12 4.0 1.7 0.8 2.5 %
Engine 13 3.0 1.3 0.6 1.9 %
Engine 14 2.3 1.1 0.5 1.4 %
Engine 15 2.7 1.5 0.7 1.7 %
Engine 16 1.6 0.9 0.5 1.0 %
Engine 17 1.3 0.8 0.4 0.8 %
Engine 18 2.4 1.0 0.5 1.5 %
Engine 19 1.6 0.8 0.4 1.0 %
Engine 20 3.8 1.5 0.7 2.4 %
Engine 21 1.8 1.0 0.5 1.1 %
Engine 22 1.7 0.8 0.4 1.1 %
Engine 23 2.0 0.9 0.5 1.2 %
Engine 24 1.6 0.8 0.4 1.0 %
Engine 25 1.3 0.8 0.4 0.8 %
Engine 26 2.2 1.1 0.5 1.3 %
Engine 27 2.3 1.1 0.5 1.4 %
Engine 28 1.7 0.9 0.4 1.1 %
Engine 29 1.9 0.9 0.4 1.2 %
Engine 30 1.8 0.8 0.4 1.1 %
Engine 31 2.5 1.0 0.5 1.5 %
Engine 32 1.8 0.8 0.4 1.1 %
Engine 33 1.6 0.8 0.4 1.0 %
Engine 34 1.5 0.9 0.5 1.0 %
Engine 35 2.0 0.9 0.5 1.3 %
Engine 36 3.4 1.3 0.6 2.1 %
Engine 37 1.5 0.9 0.5 0.9 %
Engine 38 1.4 0.7 0.4 0.8 %
Engine 39 2.3 1.1 0.6 1.4 %
Engine 40 1.6 0.8 0.4 1.0 %
Engine 41 2.0 1.0 0.5 1.2 %
Engine 42 1.6 0.7 0.4 1.0 %
Engine 43 2.1 1.1 0.5 1.3 %
Engine 44 2.0 1.0 0.5 1.2 %
Engine 45 2.2 1.0 0.5 1.4 %
Engine 46 3.4 1.3 0.6 2.1 %
Engine 47 1.6 0.9 0.5 1.0 %
Engine 48 2.0 0.9 0.5 1.2 %
Engine 49 1.5 0.8 0.4 0.9 %
Engine 50 1.8 0.8 0.4 1.1 %
Engine 51 2.2 1.3 0.6 1.4 %
Engine 52 1.6 0.8 0.4 1.0 %
Engine 53 1.2 0.6 0.3 0.7 %
Engine 54 2.5 1.1 0.5 1.5 %
Engine 55 3.0 1.4 0.7 1.9 %
Engine 56 2.1 1.0 0.5 1.3 %
Engine 57 1.7 0.8 0.4 1.1 %
Engine 58 1.2 0.6 0.3 0.7 %
Engine 59 2.5 1.1 0.5 1.6 %
Engine 60 2.8 1.1 0.5 1.7 %
Engine 61 1.4 0.8 0.4 0.9 %
Engine 62 1.5 0.8 0.4 0.9 %
Engine 63 1.6 1.0 0.5 1.0 %
Engine 64 1.9 1.0 0.5 1.2 %
Engine 65 2.4 1.1 0.6 1.5 %
Engine 66 2.8 1.8 0.8 1.7 %
Engine 67 1.9 0.9 0.4 1.2 %
Engine 68 2.9 1.9 0.9 1.8 %
Engine 69 1.7 0.9 0.4 1.0 %
Engine 70 1.7 0.9 0.4 1.1 %
Engine 71 2.8 1.3 0.6 1.7 %
Engine 72 1.8 0.9 0.5 1.1 %
Engine 73 1.5 0.8 0.4 1.0 %
Engine 74 2.9 1.2 0.6 1.8 %
Engine 75 1.8 0.8 0.4 1.1 %
------------------------- ------------ ------------ ----------
Pool Summary Total 162.0 78.2 38.3
Average 2.1 1.0 0.5
------------------------- ------------ ------------ ----------
Server Summary Total 162.0 78.2 38.3
Average 2.1 1.0 0.5
CPU Yields by Engine per sec per xact count % of total
------------------------- ------------ ------------ ---------- ----------
ThreadPool : syb_default_pool
Engine 0
Full Sleeps 21.7 0.0 3931 1.1 %
Interrupted Sleeps 4.0 0.0 727 0.2 %
Engine 1
Full Sleeps 21.0 0.0 3795 1.1 %
Interrupted Sleeps 4.5 0.0 807 0.2 %
Engine 2
Full Sleeps 21.1 0.0 3826 1.1 %
Interrupted Sleeps 4.2 0.0 764 0.2 %
Engine 3
Full Sleeps 21.6 0.0 3911 1.1 %
Interrupted Sleeps 3.6 0.0 655 0.2 %
Engine 4
Full Sleeps 22.1 0.0 4009 1.1 %
Interrupted Sleeps 3.9 0.0 703 0.2 %
Engine 5
Full Sleeps 22.2 0.0 4018 1.1 %
Interrupted Sleeps 4.3 0.0 772 0.2 %
Engine 6
Full Sleeps 21.6 0.0 3912 1.1 %
Interrupted Sleeps 4.3 0.0 784 0.2 %
Engine 7
Full Sleeps 22.6 0.0 4097 1.2 %
Interrupted Sleeps 4.4 0.0 802 0.2 %
Engine 8
Full Sleeps 22.2 0.0 4016 1.1 %
Interrupted Sleeps 4.1 0.0 736 0.2 %
Engine 9
Full Sleeps 22.1 0.0 4000 1.1 %
Interrupted Sleeps 4.0 0.0 719 0.2 %
Engine 10
Full Sleeps 21.7 0.0 3927 1.1 %
Interrupted Sleeps 4.0 0.0 728 0.2 %
Engine 11
Full Sleeps 21.1 0.0 3828 1.1 %
Interrupted Sleeps 4.0 0.0 728 0.2 %
Engine 12
Full Sleeps 22.5 0.0 4071 1.2 %
Interrupted Sleeps 5.0 0.0 900 0.3 %
Engine 13
Full Sleeps 21.2 0.0 3835 1.1 %
Interrupted Sleeps 4.1 0.0 742 0.2 %
Engine 14
Full Sleeps 21.3 0.0 3850 1.1 %
Interrupted Sleeps 4.4 0.0 789 0.2 %
Engine 15
Full Sleeps 22.4 0.0 4049 1.2 %
Interrupted Sleeps 3.8 0.0 691 0.2 %
Engine 16
Full Sleeps 21.7 0.0 3936 1.1 %
Interrupted Sleeps 3.9 0.0 706 0.2 %
Engine 17
Full Sleeps 21.1 0.0 3825 1.1 %
Interrupted Sleeps 3.6 0.0 646 0.2 %
Engine 18
Full Sleeps 21.6 0.0 3902 1.1 %
Interrupted Sleeps 3.8 0.0 692 0.2 %
Engine 19
Full Sleeps 21.2 0.0 3845 1.1 %
Interrupted Sleeps 3.6 0.0 650 0.2 %
Engine 20
Full Sleeps 20.5 0.0 3717 1.1 %
Interrupted Sleeps 3.6 0.0 654 0.2 %
Engine 21
Full Sleeps 21.0 0.0 3801 1.1 %
Interrupted Sleeps 3.7 0.0 663 0.2 %
Engine 22
Full Sleeps 21.5 0.0 3900 1.1 %
Interrupted Sleeps 3.9 0.0 711 0.2 %
Engine 23
Full Sleeps 21.6 0.0 3907 1.1 %
Interrupted Sleeps 4.0 0.0 725 0.2 %
Engine 24
Full Sleeps 21.6 0.0 3911 1.1 %
Interrupted Sleeps 4.0 0.0 727 0.2 %
Engine 25
Full Sleeps 21.0 0.0 3804 1.1 %
Interrupted Sleeps 4.0 0.0 723 0.2 %
Engine 26
Full Sleeps 21.8 0.0 3939 1.1 %
Interrupted Sleeps 3.9 0.0 714 0.2 %
Engine 27
Full Sleeps 21.9 0.0 3964 1.1 %
Interrupted Sleeps 4.0 0.0 727 0.2 %
Engine 28
Full Sleeps 21.8 0.0 3938 1.1 %
Interrupted Sleeps 4.1 0.0 740 0.2 %
Engine 29
Full Sleeps 21.6 0.0 3913 1.1 %
Interrupted Sleeps 4.3 0.0 782 0.2 %
Engine 30
Full Sleeps 21.8 0.0 3950 1.1 %
Interrupted Sleeps 4.3 0.0 777 0.2 %
Engine 31
Full Sleeps 21.4 0.0 3878 1.1 %
Interrupted Sleeps 4.1 0.0 747 0.2 %
Engine 32
Full Sleeps 21.0 0.0 3793 1.1 %
Interrupted Sleeps 3.8 0.0 695 0.2 %
Engine 33
Full Sleeps 20.5 0.0 3716 1.1 %
Interrupted Sleeps 4.7 0.0 842 0.2 %
Engine 34
Full Sleeps 20.7 0.0 3743 1.1 %
Interrupted Sleeps 3.6 0.0 658 0.2 %
Engine 35
Full Sleeps 21.8 0.0 3939 1.1 %
Interrupted Sleeps 4.4 0.0 796 0.2 %
Engine 36
Full Sleeps 21.3 0.0 3864 1.1 %
Interrupted Sleeps 4.0 0.0 731 0.2 %
Engine 37
Full Sleeps 21.0 0.0 3807 1.1 %
Interrupted Sleeps 3.6 0.0 643 0.2 %
Engine 38
Full Sleeps 21.5 0.0 3888 1.1 %
Interrupted Sleeps 3.9 0.0 708 0.2 %
Engine 39
Full Sleeps 21.7 0.0 3920 1.1 %
Interrupted Sleeps 4.2 0.0 763 0.2 %
Engine 40
Full Sleeps 21.1 0.0 3828 1.1 %
Interrupted Sleeps 4.2 0.0 759 0.2 %
Engine 41
Full Sleeps 20.6 0.0 3733 1.1 %
Interrupted Sleeps 4.3 0.0 774 0.2 %
Engine 42
Full Sleeps 21.0 0.0 3804 1.1 %
Interrupted Sleeps 4.5 0.0 812 0.2 %
Engine 43
Full Sleeps 21.1 0.0 3818 1.1 %
Interrupted Sleeps 4.0 0.0 730 0.2 %
Engine 44
Full Sleeps 21.6 0.0 3918 1.1 %
Interrupted Sleeps 4.2 0.0 761 0.2 %
Engine 45
Full Sleeps 20.5 0.0 3719 1.1 %
Interrupted Sleeps 3.3 0.0 591 0.2 %
Engine 46
Full Sleeps 20.9 0.0 3788 1.1 %
Interrupted Sleeps 4.1 0.0 742 0.2 %
Engine 47
Full Sleeps 21.4 0.0 3872 1.1 %
Interrupted Sleeps 4.3 0.0 774 0.2 %
Engine 48
Full Sleeps 21.0 0.0 3793 1.1 %
Interrupted Sleeps 3.8 0.0 691 0.2 %
Engine 49
Full Sleeps 21.1 0.0 3817 1.1 %
Interrupted Sleeps 3.8 0.0 681 0.2 %
Engine 50
Full Sleeps 22.0 0.0 3985 1.1 %
Interrupted Sleeps 4.0 0.0 722 0.2 %
Engine 51
Full Sleeps 21.5 0.0 3888 1.1 %
Interrupted Sleeps 4.0 0.0 732 0.2 %
Engine 52
Full Sleeps 21.6 0.0 3912 1.1 %
Interrupted Sleeps 4.1 0.0 743 0.2 %
Engine 53
Full Sleeps 21.0 0.0 3805 1.1 %
Interrupted Sleeps 3.9 0.0 700 0.2 %
Engine 54
Full Sleeps 20.9 0.0 3782 1.1 %
Interrupted Sleeps 4.0 0.0 715 0.2 %
Engine 55
Full Sleeps 21.5 0.0 3900 1.1 %
Interrupted Sleeps 4.0 0.0 720 0.2 %
Engine 56
Full Sleeps 22.0 0.0 3978 1.1 %
Interrupted Sleeps 4.8 0.0 876 0.2 %
Engine 57
Full Sleeps 22.5 0.0 4081 1.2 %
Interrupted Sleeps 4.4 0.0 801 0.2 %
Engine 58
Full Sleeps 22.0 0.0 3988 1.1 %
Interrupted Sleeps 3.8 0.0 691 0.2 %
Engine 59
Full Sleeps 21.0 0.0 3792 1.1 %
Interrupted Sleeps 4.4 0.0 799 0.2 %
Engine 60
Full Sleeps 22.0 0.0 3979 1.1 %
Interrupted Sleeps 4.1 0.0 735 0.2 %
Engine 61
Full Sleeps 21.1 0.0 3814 1.1 %
Interrupted Sleeps 3.9 0.0 706 0.2 %
Engine 62
Full Sleeps 21.3 0.0 3864 1.1 %
Interrupted Sleeps 4.0 0.0 730 0.2 %
Engine 63
Full Sleeps 22.2 0.0 4019 1.1 %
Interrupted Sleeps 4.6 0.0 827 0.2 %
Engine 64
Full Sleeps 20.3 0.0 3677 1.0 %
Interrupted Sleeps 4.1 0.0 750 0.2 %
Engine 65
Full Sleeps 20.6 0.0 3722 1.1 %
Interrupted Sleeps 3.9 0.0 708 0.2 %
Engine 66
Full Sleeps 20.5 0.0 3715 1.1 %
Interrupted Sleeps 3.8 0.0 681 0.2 %
Engine 67
Full Sleeps 21.6 0.0 3909 1.1 %
Interrupted Sleeps 3.9 0.0 704 0.2 %
Engine 68
Full Sleeps 21.4 0.0 3875 1.1 %
Interrupted Sleeps 3.7 0.0 663 0.2 %
Engine 69
Full Sleeps 22.2 0.0 4020 1.1 %
Interrupted Sleeps 4.1 0.0 735 0.2 %
Engine 70
Full Sleeps 21.4 0.0 3876 1.1 %
Interrupted Sleeps 3.9 0.0 712 0.2 %
Engine 71
Full Sleeps 21.1 0.0 3822 1.1 %
Interrupted Sleeps 4.6 0.0 826 0.2 %
Engine 72
Full Sleeps 21.7 0.0 3931 1.1 %
Interrupted Sleeps 4.1 0.0 744 0.2 %
Engine 73
Full Sleeps 21.0 0.0 3807 1.1 %
Interrupted Sleeps 3.9 0.0 704 0.2 %
Engine 74
Full Sleeps 21.0 0.0 3802 1.1 %
Interrupted Sleeps 4.0 0.0 715 0.2 %
Engine 75
Full Sleeps 21.8 0.0 3951 1.1 %
Interrupted Sleeps 4.3 0.0 774 0.2 %
------------------------- ------------ ------------ ----------
Pool Summary 1937.3 1.3 350654
------------------------- ------------ ------------ ----------
Total CPU Yields 1937.3 1.3 350654
Thread Utilization (OS %) User Busy System Busy Idle
------------------------- ------------ ------------ ----------
ThreadPool : syb_blocking_pool : no activity during sample
ThreadPool : syb_default_pool
Thread 6 (Engine 0) 36.8 % 0.1 % 63.1 %
Thread 7 (Engine 1) 37.3 % 0.1 % 62.6 %
Thread 8 (Engine 2) 37.7 % 0.1 % 62.2 %
Thread 9 (Engine 3) 36.5 % 0.1 % 63.4 %
Thread 10 (Engine 4) 35.6 % 0.1 % 64.3 %
Thread 11 (Engine 5) 35.5 % 0.1 % 64.5 %
Thread 12 (Engine 6) 37.7 % 0.1 % 62.2 %
Thread 13 (Engine 7) 36.4 % 0.1 % 63.5 %
Thread 14 (Engine 8) 35.9 % 0.1 % 64.0 %
Thread 15 (Engine 9) 35.9 % 0.1 % 64.0 %
Thread 16 (Engine 10) 36.3 % 0.1 % 63.6 %
Thread 17 (Engine 11) 36.8 % 0.1 % 63.1 %
Thread 18 (Engine 12) 37.1 % 0.1 % 62.7 %
Thread 19 (Engine 13) 37.3 % 0.1 % 62.5 %
Thread 20 (Engine 14) 38.2 % 0.1 % 61.6 %
Thread 21 (Engine 15) 36.8 % 0.1 % 63.1 %
Thread 22 (Engine 16) 36.2 % 0.1 % 63.7 %
Thread 23 (Engine 17) 36.7 % 0.1 % 63.2 %
Thread 24 (Engine 18) 36.7 % 0.1 % 63.2 %
Thread 25 (Engine 19) 37.3 % 0.1 % 62.6 %
Thread 26 (Engine 20) 36.4 % 0.1 % 63.5 %
Thread 27 (Engine 21) 36.5 % 0.1 % 63.4 %
Thread 28 (Engine 22) 36.2 % 0.1 % 63.7 %
Thread 29 (Engine 23) 36.5 % 0.1 % 63.4 %
Thread 30 (Engine 24) 36.4 % 0.1 % 63.5 %
Thread 31 (Engine 25) 37.8 % 0.1 % 62.1 %
Thread 32 (Engine 26) 36.8 % 0.1 % 63.1 %
Thread 33 (Engine 27) 35.8 % 0.1 % 64.1 %
Thread 34 (Engine 28) 36.5 % 0.1 % 63.4 %
Thread 35 (Engine 29) 37.0 % 0.1 % 62.9 %
Thread 36 (Engine 30) 37.0 % 0.1 % 62.9 %
Thread 37 (Engine 31) 37.0 % 0.1 % 62.9 %
Thread 38 (Engine 32) 36.9 % 0.1 % 63.0 %
Thread 39 (Engine 33) 38.0 % 0.1 % 61.9 %
Thread 40 (Engine 34) 37.3 % 0.1 % 62.6 %
Thread 41 (Engine 35) 37.7 % 0.1 % 62.2 %
Thread 42 (Engine 36) 36.1 % 0.1 % 63.8 %
Thread 43 (Engine 37) 36.5 % 0.1 % 63.4 %
Thread 44 (Engine 38) 37.0 % 0.1 % 62.9 %
Thread 45 (Engine 39) 36.9 % 0.1 % 63.0 %
Thread 46 (Engine 40) 37.2 % 0.1 % 62.7 %
Thread 47 (Engine 41) 38.0 % 0.1 % 61.9 %
Thread 48 (Engine 42) 38.5 % 0.1 % 61.4 %
Thread 49 (Engine 43) 36.9 % 0.1 % 63.0 %
Thread 50 (Engine 44) 37.9 % 0.1 % 62.0 %
Thread 51 (Engine 45) 35.3 % 0.1 % 64.6 %
Thread 52 (Engine 46) 37.9 % 0.1 % 62.0 %
Thread 53 (Engine 47) 37.7 % 0.1 % 62.1 %
Thread 54 (Engine 48) 36.6 % 0.1 % 63.3 %
Thread 55 (Engine 49) 37.3 % 0.1 % 62.6 %
Thread 56 (Engine 50) 35.3 % 0.1 % 64.6 %
Thread 57 (Engine 51) 35.6 % 0.1 % 64.3 %
Thread 58 (Engine 52) 36.8 % 0.1 % 63.1 %
Thread 59 (Engine 53) 37.4 % 0.1 % 62.5 %
Thread 60 (Engine 54) 36.6 % 0.1 % 63.3 %
Thread 61 (Engine 55) 36.1 % 0.1 % 63.8 %
Thread 62 (Engine 56) 36.4 % 0.1 % 63.5 %
Thread 63 (Engine 57) 36.8 % 0.1 % 63.1 %
Thread 64 (Engine 58) 36.4 % 0.1 % 63.5 %
Thread 65 (Engine 59) 38.6 % 0.1 % 61.3 %
Thread 66 (Engine 60) 36.0 % 0.1 % 63.9 %
Thread 67 (Engine 61) 36.8 % 0.1 % 63.1 %
Thread 68 (Engine 62) 36.9 % 0.1 % 63.0 %
Thread 69 (Engine 63) 37.2 % 0.1 % 62.7 %
Thread 70 (Engine 64) 38.0 % 0.1 % 61.9 %
Thread 71 (Engine 65) 37.9 % 0.1 % 62.0 %
Thread 72 (Engine 66) 36.7 % 0.1 % 63.2 %
Thread 73 (Engine 67) 35.5 % 0.1 % 64.4 %
Thread 74 (Engine 68) 35.6 % 0.1 % 64.3 %
Thread 75 (Engine 69) 35.9 % 0.1 % 64.0 %
Thread 76 (Engine 70) 37.1 % 0.1 % 62.8 %
Thread 77 (Engine 71) 38.6 % 0.1 % 61.3 %
Thread 78 (Engine 72) 36.5 % 0.1 % 63.4 %
Thread 79 (Engine 73) 36.8 % 0.1 % 63.1 %
Thread 80 (Engine 74) 36.8 % 0.1 % 63.1 %
Thread 81 (Engine 75) 38.1 % 0.1 % 61.8 %
------------------------- ------------ ------------ ----------
Pool Summary Total 2801.0 % 7.4 % 4791.5 %
Average 36.9 % 0.1 % 63.0 %
ThreadPool : syb_system_pool
Thread 1 (Signal Handler) 0.2 % 0.0 % 99.8 %
Thread 82 (NetController) 8.5 % 6.8 % 84.8 %
Thread 83 (DiskController) 3.8 % 0.5 % 95.7 %
------------------------- ------------ ------------ ----------
Pool Summary Total 12.4 % 7.3 % 280.3 %
Average 4.1 % 2.4 % 93.4 %
------------------------- ------------ ------------ ----------
Server Summary Total 2813.4 % 14.8 % 5471.8 %
Average 33.9 % 0.2 % 65.9 %
Adaptive Server threads are consuming 28.3 CPU units.
Throughput (committed xacts per CPU unit) : 51.0
Context Switches at OS per sec per xact count % of total
------------------------- ------------ ------------ ---------- ----------
ThreadPool : syb_blocking_pool
Voluntary 0.0 0.0 0 0.0 %
Non-Voluntary 0.0 0.0 0 0.0 %
ThreadPool : syb_default_pool
Voluntary 1899.2 1.3 343764 48.4 %
Non-Voluntary 1097.1 0.8 198577 27.9 %
ThreadPool : syb_system_pool
Voluntary 917.2 0.6 166007 23.4 %
Non-Voluntary 12.3 0.0 2225 0.3 %
------------------------- ------------ ------------ ---------- ----------
Total Context Switches 3925.8 2.7 710573 100.0 %
CtlibController Activity per sec per xact count % of total
------------------------- ------------ ------------ ---------- ----------
Polls 0.0 0.0 0 0.0 %
DiskController Activity per sec per xact count % of total
------------------------- ------------ ------------ ---------- ----------
Polls 19331.3 13.4 3498973 n/a
Polls Returning Events 194.3 0.1 35164 1.0 %
Polls Returning Max Events 0.2 0.0 33 0.0 %
Total Events 344.8 0.2 62404 n/a
Events Per Poll n/a n/a 0.018 n/a
NetController Activity per sec per xact count % of total
------------------------- ------------ ------------ ---------- ----------
Polls 29362.6 20.4 5314627 n/a
Polls Returning Events 29362.6 20.4 5314627 100.0 %
Polls Returning Max Events 0.3 0.0 51 0.0 %
Total Events 29434.4 20.4 5327635 n/a
Events Per Poll n/a n/a 1.002 n/a
I have two windows 2003 hosts that are each running ASE 12.5
I want to setup a windows 2003 cluster, where the storage and networking for host1 are in an "app" I can fail over to either box.. same for host 2 ("app2") This means that if one box goes down the sybase from it will fail over and run from the 2nd box.. at that point TWO SQLSERVER.EXEs will be running on the same host ... is this config possible with the 12.5 version?
Just trying to remove single points of failure as cheap as possible...
-Ken
..and yes.... we are upgrading versions in a separate project which will take over a year to complete..
Hi Dears,
I am working whit Visual Basic 6 and Sybase Adaptive Server Enterprise 15.0.3, and I get the following error:
ERROR 40002 TIEMPO DE EJECUCION
HY000: [DataDirect] [ODBC Sybase wire protocol Driver] Sybase does not allow more that one active statement when retrieving results with out a cursor
Can you help me, please!!!!
Anyone knows about? Can be fixed? Logging in goes in endless loop....
Hi there,
is there a way to point to a sql.ini (or other interface file) on another server?
The idea is to create a central sql.ini where all servers and clients look at.
I am aware of the consequences (singel point of failure, no freedom for clients etc) but maintaining hundreds of sql.ini/dns/odbc files is not why i became a DBA ;-).
I'm not looking for a push mechanism....(autocopy to servers and clients)
Thanks in advance for your input,
Harry Splinter
Can help me someone with the following issues?
We are testing the database inmemory option for SAP ASE, the purpose is to reduce the execution time of the batch process, but we have had the following problems:
When we have enabled full dml_logging the log is consumed very quickly and we visualize LOG SUSPEND message therefore we have placed this dml_logging minimal
Could this help us optimize the runtime on a batch process?
That we could have disadvantages when using this option?
Thanks in Advance
I been manually pulling replication-based synchronization monitoring data from Sybase Control Center (Monitoring - Replication - History). Is there anyway to retrieve the replication history automatically by running script or command prompt?
Good day,
I have a process which after some minutes starts blocking users . The output shows for command "dbcc", status "lock sleep" and the tx name is "rs_logexec". ( no Rep Server used )
If sp_procxmode in not used, are there any other known reasons for this to happen?
It's an old ASE 12.5.3 on Solaris 9
Thank you
Regards
Jose
Hi, I'm installing a new ASE 16 server on Windows 2008 R2 SP1, after the server has been set up and started, there is a system process which seems stuck on "Maintenance Token" as the cmd. When I try and shutdown the server, it waits indefinitely for this process to stop. The only way I can shutdown is with nowait option. Why is this process stuck on "Maintenance Token"?
Any help greatly appreciated!
Hi Everybody,
I have 2 ASE companion servers running on a symmetric configuration and I need to configure a proxy db on my primary companion server that points to third ASE server
What are the considerations, that I need to have? and what steps I need to follow in order to obtain this configuration?
Best Regards,
Jairo
For the server to have the correct statistics of the indexes on the temporary table when should the indexes be created?
a. When the table is created and there is no data.
b. When the data is inserted in the table.
c. We cannot create an index on a temporary table
d. Anywhere before the usage of the table.
With the introduction of ASE Edge Edition, I was wondering if anyone knows what the final version of ASE Small Business Edition (SBE) will be? Also, what is the latest SBE version?
Any help appreciated.
Hi, I am digging around online, without any luck, trying to find descriptions or release notes for the various EBF releases for ASE 16. Anyone know where I can find these online?
Thanks!
For the past few months we have had an error like the one below appear in our ASE log. The error initially occurred once a week or so but in the last few weeks it has started happening almost daily.
00:03:00000:00078:2015/06/15 08:27:18.38 kernel Address 0x0x0000000000b7c67b (fm_unlink_frame+0x2b), siginfo (code, address) = (1, 0x0x00000000deadbabe)
00:03:00000:00078:2015/06/15 08:27:18.39 kernel ************************************
00:03:00000:00078:2015/06/15 08:27:18.39 kernel SQL causing error :
00:03:00000:00078:2015/06/15 08:27:18.39 kernel ************************************
00:03:00000:00078:2015/06/15 08:27:18.39 server SQL Text:
00:03:00000:00078:2015/06/15 08:27:18.39 kernel curdb = 1 tempdb = 0 pstat = 0x10000 p2stat = 0x141000
00:03:00000:00078:2015/06/15 08:27:18.39 kernel p3stat = 0x900 p4stat = 0x0 p5stat = 0x8 p6stat = 0x10 p7stat = 0x10000
00:03:00000:00078:2015/06/15 08:27:18.39 kernel lasterror = 0 preverror = 0 transtate = 1
00:03:00000:00078:2015/06/15 08:27:18.39 kernel curcmd = 0 program = PHP 5
00:03:00000:00078:2015/06/15 08:27:18.39 kernel extended error information: hostname: xxx.xxx.xxx login: lGbReportXXXXXXXX
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x000000000176740f pcstkwalk+0x30()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000001767205 ucstkgentrace+0x1a5()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000001706771 ucbacktrace+0x43()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x000000000074360e terminate_process+0xd5e()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000001733d03 kisignal+0x3b3()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b7c67b fm_unlink_frame+0x2b()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b7c346 fm_free_frame+0x16()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b7c3c8 fm_free_list+0x18()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b68d56 db__create_sysusages_map+0x126()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b66cf9 db_fill+0x159()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b6bdfb dbt(float, int, long, long)+0x16b()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x00000000019b0a70 dbt_get+0x440()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b6dd4f dbt_get_with_statuscheck+0xf()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x0000000000b62f4a usedb_cmd+0x7a()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel [Handler pc: 0x0x00000000010b644f hdl__login installed by the following function:-]
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x000000000074c7d4 login+0x734()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel [Handler pc: 0x0x0000000000d4e930 ut_handle installed by the following function:-]
00:03:00000:00078:2015/06/15 08:27:18.40 kernel pc: 0x000000000191c52f conn_hdlr+0x51f()
00:03:00000:00078:2015/06/15 08:27:18.40 kernel end of stack trace, spid 78, kpid 951451747, suid 1621
After this error occurs, MAINTENANCE TOKEN processes start appearing on the server. More and more of them start, never finish, and they cannot be killed. Dataserver performance eventually degrades - the only solution is to perform a shutdown with nowait and restart the dataserver.
The error is usually like the above, but occasionally has errors like this related to memory:
00:03:00000:00127:2015/06/11 20:43:18.95 server Error: 715, Severity: 20, State: 2
00:03:00000:00127:2015/06/11 20:43:18.95 server Unable to locate a procedure cache memory control descriptor for memory '0x0x176731800' in the global list.
00:03:00000:00127:2015/06/11 20:43:18.95 server Error: 715, Severity: 20, State: 2
00:03:00000:00127:2015/06/11 20:43:18.95 server Unable to locate a procedure cache memory control descriptor for memory '0x0x16ec53000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1a10ec800' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b12c7000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x177752000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x18fe13000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x16bfe9000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 714, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b5c22800' allocated by process 127.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b4a92000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b64bd800' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 715, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b64df000' in the global list.
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 714, Severity: 20, State: 2
00:01:00000:00127:2015/06/11 20:43:19.13 server Unable to locate a procedure cache memory control descriptor for memory '0x0x1b63bb560' allocated by process 127.
00:01:00000:00127:2015/06/11 20:43:19.13 server (mem_freepages) Diagnostics for error 707 state 8: addr=0x0x1b63bb560 mem free failed retcode=-3 pgcount=0
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x000000000176740f pcstkwalk+0x30()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000001767205 ucstkgentrace+0x1a5()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000001706771 ucbacktrace+0x43()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x00000000019c8715 mem_freepages+0x205()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b868a8 free_memchunk+0x98()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b7c390 fm_free_frame+0x60()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b7c3c8 fm_free_list+0x18()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b68d56 db__create_sysusages_map+0x126()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b66cf9 db_fill+0x159()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b6bdfb dbt(float, int, long, long)+0x16b()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x00000000019b0a70 dbt_get+0x440()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b6dd4f dbt_get_with_statuscheck+0xf()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x0000000000b62f4a usedb_cmd+0x7a()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel [Handler pc: 0x0x00000000010b644f hdl__login installed by the following function:-]
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x000000000074c7d4 login+0x734()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel [Handler pc: 0x0x0000000000d4e930 ut_handle installed by the following function:-]
00:01:00000:00127:2015/06/11 20:43:19.13 kernel pc: 0x000000000191c52f conn_hdlr+0x51f()
00:01:00000:00127:2015/06/11 20:43:19.13 kernel end of stack trace, spid 127, kpid 1491992657, suid 1853
00:01:00000:00127:2015/06/11 20:43:19.13 server Error: 707, Severity: 20, State: 8
00:01:00000:00127:2015/06/11 20:43:19.13 server System error detected during attempt to free memory at address 0x1b63bb560. Please consult the ASE error log for more details.
00:01:00000:00127:2015/06/11 20:43:20.03 server WARNING: memory usage in procedure headers (2)
does not match memory usage count in Pss (4294965921) for server process id 127.
00:01:00000:00127:2015/06/11 20:43:20.33 server Error: 715, Severity: 20, State: 2
We have tried tweaking the server settings in this post SAP Sybase Forums - ASE - Administration - Maintenance Token and high CPU but it has not helped. We have a support license for one of our machines, unfortunately it it not for this machine. Our other servers perform similar work and have similar hardware specifications but this server is the only one with a problem. The login lGbReportXXXXXXXX is one login of many and it changes each time - the issue does not appear to be related to a single database or login.
The server version is:
Adaptive Server Enterprise/15.5/EBF 18661 SMP ESD#4/P/x86_64/Enterprise Linux/a
sear155/2545/64-bit/FBO/Thu Jun 16 06:45:54 2011
Any idea what is causing these errors and how we can fix the issue?
Any help appreciated. Cheers
Unable to connect to database. xxx.db.ConnectionException: DBServer::GetConnection: mscorlib: Could not load file or assembly 'Sybase.AdoNet4.AseClient, Version=4.157.1300.0, Culture=neutral' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040): at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at
I am getting the above error when i use the new 64 bit dll. Can you please suggest from stack trace what could be the error?
Anyone knows where the documentation for ASE 16 Sp02 may be found?
Thanks.
Since 15.0.x ASE comes with handy PC MDAs - monProcedureCacheMemoryUsage and monProcedureCacheModuleUsage. Both are "essential" in sizing the PC correctly - and analyzing PC behavior for your application & ASE. There counters are very nice but... over time they become user-un-friendly.
Both counters are not absolute point-in-time sample values but rather grow over time. But if they grow - what do they show?
There may be further broken down into sub-allocators.
You'd expect Active to indicate the sample value from the point-of-time of inspection and HWM to indicate the number of memory pages since the startup (i.e. relative to the DaysRunning from the monState). Yet, both behave in the same cumulative manner and both yield useless values if divided into daily portions and compared to say monitorconfig. The same applies to the reuse values packed into these tables.
Anyone tried to make sense of these values? They are essential in configuring PC on the one hand but accumulate over time on the other (and exceed PC size in hundreds of % + are marked as indicator&1). What do these in fact display? How do they relate to monitorconfig? When you restart ASE (or play with these on your private ASE) the numbers seem to make sense. When you analyze them on the real production environment - they only mislead (as does the sysmon bit in the Indicator column related to them).
Any insights?
Thanks,
Andrew
ps. PERFORMANCE SCALABILITY ENHANCEMENTS IN SAP ADAPTIVE SERVER® ENTERPRISE has a neat section on PC sizing which, too, rely on monProcedureCacheModuleUsage. However, the values are taken as simple aggregates - without any respect to their cumulative nature. Was ASE bounced to take correct measurement? How reliable are the HWM/Reuse numbers in that paper?