SAP ABAP Message Class SMMSS_ALERTS (Message class for MSSQL rz20 messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DB-MSS (Application Component) Microsoft SQL Server
⤷ STUN_MSS (Package) Package for new SQL Server monitoring objects
⤷ BC-DB-MSS (Application Component) Microsoft SQL Server
⤷ STUN_MSS (Package) Package for new SQL Server monitoring objects
Attributes
Message class | SMMSS_ALERTS | |
Short Description | Message class for MSSQL rz20 messages | |
Changed On | 20130531 | |
Last Changed At | 091524 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | SQL Server Monitoring Object. Please check F1 help 1 level below | The short text describes the object sufficiently | |
2 | 002 | &1: function call &2 failed with exception &3. Affected MTE: &4. | Space: object requires documentation | |
3 | 003 | This alert shows if level 17 or higher errors are in the SQL Server logs | Space: object requires documentation | |
4 | 004 | No Severity 17 or higher messages exist | Space: object requires documentation | |
5 | 005 | &1 errors exist in an error log | Space: object requires documentation | |
6 | 006 | Space: object requires documentation | ||
7 | 007 | This alert shows if the last good backup is too old | Space: object requires documentation | |
8 | 008 | This database was last backed up successfully &1 days ago | Space: object requires documentation | |
9 | 010 | SQL Server using &1% of CPU | Space: object requires documentation | |
10 | 011 | This alert tracks the percentage of CPU used by SQL Server | Space: object requires documentation | |
11 | 012 | &1 disk read/write error(s) have occurred | Space: object requires documentation | |
12 | 013 | This alert shows the # of disk read/write errors noticed by SQL Server | Space: object requires documentation | |
13 | 014 | &1 network packet error(s) have occurred | Space: object requires documentation | |
14 | 015 | This alert shows the # of network packet errors noticed by SQL Server | Space: object requires documentation | |
15 | 016 | This alert shows a configuration required in SQL Server has not been done | Space: object requires documentation | |
16 | 017 | This alert shows which trace flags were used to start SQL Server | Space: object requires documentation | |
17 | 018 | This alert shows if the memory setting for SQL Server follows SAP rec. | Space: object requires documentation | |
18 | 019 | SQL Server self monitoring | Space: object requires documentation | |
19 | 020 | This alert show information about the Operating System | Space: object requires documentation | |
20 | 021 | This alert tracks the data cache hit ratio of SQL Server | Space: object requires documentation | |
21 | 022 | This alert tracks the procedure cache hit ratio of SQL Server | Space: object requires documentation | |
22 | 023 | Data cache hit ratio of &1% could be improved | Space: object requires documentation | |
23 | 024 | Procedure cache hit ratio of &1% could be improved | Space: object requires documentation | |
24 | 025 | This alert shows information about SQL Server build numbers | Space: object requires documentation | |
25 | 026 | &1 | &2 | Chip:&3 | Space: object requires documentation | |
26 | 027 | &1&2 | Space: object requires documentation | |
27 | 028 | &1 | Cluster:&2| AWE:&3 | Space: object requires documentation | |
28 | 029 | Memory is &1 - follows SAP recommendation | Space: object requires documentation | |
29 | 030 | Memory is set to FIXED and no R/3 work processes are present on DB server | Space: object requires documentation | |
30 | 031 | Memory is set to &1 and &2 dialog R/3 work procs are present on DB server | Space: object requires documentation | |
31 | 032 | This alert shows how many non-R/3 connections are on the SAP DB | Space: object requires documentation | |
32 | 033 | This alert shows how many connections the R/3 work procs have to the DB | Space: object requires documentation | |
33 | 034 | &1 R/3 connections to the DB | Space: object requires documentation | |
34 | 035 | &1 non-R/3 connections to the R/3 DB | Space: object requires documentation | |
35 | 036 | This alert tracks the maximum runtime of a SQL statement | Space: object requires documentation | |
36 | 037 | Single SQL statement runtime of &1ms is very high | Space: object requires documentation | |
37 | 038 | This alert shows whether statistics collection is on or not | Space: object requires documentation | |
38 | 039 | This alert shows if a backup is currently being run against a database | Space: object requires documentation | |
39 | 040 | DB &1 is currently being backed up | Space: object requires documentation | |
40 | 041 | Statistics collection is &1 | Space: object requires documentation | |
41 | 042 | Last Reset: &1 | Space: object requires documentation | |
42 | 043 | This alert shows when the slow SQL statement statistics were last reset | Space: object requires documentation | |
43 | 044 | A backup is not currently running | Space: object requires documentation | |
44 | 046 | This alert shows if disk performance statistics are on for the DB server | Space: object requires documentation | |
45 | 047 | NOT on DB server - no Perfmon disk stats available | Space: object requires documentation | |
46 | 048 | Yes use Detail Analysis/Disk button of trx ST06 | Space: object requires documentation | |
47 | 049 | This alert shows the time since the last transaction log backup | Space: object requires documentation | |
48 | 050 | Transaction log backup &1 minutes ago | Space: object requires documentation | |
49 | 052 | This alert shows the count of the given object type missing from the DB | Space: object requires documentation | |
50 | 053 | There are &1 &2 defined in the data dictionary and missing from the DB | Space: object requires documentation | |
51 | 054 | This alert shows the percent of free space left in a file | Space: object requires documentation | |
52 | 055 | This alert shows if autogrowth has been set for the DB file | Space: object requires documentation | |
53 | 056 | The current size, used size, and growth setting of a DB file | Space: object requires documentation | |
54 | 057 | This alert shows the MB left on the device the DB file resides upon | Space: object requires documentation | |
55 | 058 | Autogrowth is &1 | Space: object requires documentation | |
56 | 059 | Size:&1 Used:&2 Growth:&3 | Space: object requires documentation | |
57 | 060 | &1 MB free disk space on device | Space: object requires documentation | |
58 | 061 | This alert tracks the maximum runtime of a SQL statement | Space: object requires documentation | |
59 | 062 | Single SQL statement run and fetch time of &1ms is very high | Space: object requires documentation | |
60 | 063 | Transaction AL02 is not supported in Sql Server | Space: object requires documentation | |
61 | 064 | This alert shows the ms/access | Space: object requires documentation | |
62 | 065 | The ave. number of millisecs/access for this file is &1 | Space: object requires documentation | |
63 | 066 | Transaction Log &1% used | The short text describes the object sufficiently | |
64 | 068 | This alert shows the % of total time used by a single statement | The short text describes the object sufficiently | |
65 | 069 | This alert shows the % of logical reads used by a single statement | The short text describes the object sufficiently | |
66 | 070 | This alert shows the % of cpu time used by a single statement | The short text describes the object sufficiently | |
67 | 071 | &1% of elapsed time caused by one statement | The short text describes the object sufficiently | |
68 | 072 | &1% of logical reads caused by one statement | The short text describes the object sufficiently | |
69 | 073 | &1% of cpu time caused by one statement | The short text describes the object sufficiently | |
70 | 074 | &1% free space in file | The short text describes the object sufficiently | |
71 | 078 | This alert shows the current kBytes/sec read for the DB | The short text describes the object sufficiently | |
72 | 079 | &1 kB/sec read for DB | The short text describes the object sufficiently | |
73 | 080 | This alert shows the batches/second processed by SQLServer | The short text describes the object sufficiently | |
74 | 081 | &1 Batches/sec processed by SQLServer | The short text describes the object sufficiently | |
75 | 082 | This alert shows the ms/write for the SQLServer LOG | The short text describes the object sufficiently | |
76 | 083 | &1 ms/wrt for the SQLServer log | The short text describes the object sufficiently | |
77 | 084 | This alert shows the seconds blocked of the oldest blocked spid | The short text describes the object sufficiently | |
78 | 085 | &1 seconds blocked | The short text describes the object sufficiently | |
79 | 086 | This alert shows the seconds of the oldest open transaction | The short text describes the object sufficiently | |
80 | 087 | &1 seconds open for a transaction | The short text describes the object sufficiently | |
81 | 088 | This alert tracks the page life expectancy reported by SQL Server | The short text describes the object sufficiently | |
82 | 089 | Page life expectancy of &1 could be improved | The short text describes the object sufficiently | |
83 | 090 | This alert shows the name of the object which caused high cpu % | The short text describes the object sufficiently | |
84 | 091 | This alert shows the object causing high logical reads | The short text describes the object sufficiently | |
85 | 200 | Data Collection | The short text describes the object sufficiently | |
86 | 201 | Check of the SQL Server Agent service status | Space: object requires documentation | |
87 | 202 | SQL Server Agent service status | Space: object requires documentation | |
88 | 203 | Start the SQL Server Agent service | Space: object requires documentation |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |