SAP ABAP Message Class RSMSS_ANALYZER_MSG (Messages for RSMSS_ANALYZER)

Basic Data

Hierarchy

☛ SAP_BW (Software Component) SAP Business Warehouse
   ⤷ BW-SYS-DB-MSS (Application Component) BW Microsoft SQL Server
     ⤷ RSMSS (Package) Microsoft SQL Server Porting

Attributes

Message class	RSMSS_ANALYZER_MSG
Short Description	Messages for RSMSS_ANALYZER
Changed On	20140121
Last Changed At	101801

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	Basis InfoCubes with many uncompressed requests	Space: object requires documentation	☐
2	001	Property: INFOCUBE	Space: object requires documentation	☐
3	002	Property: NUMBER_OF_REQUESTS	Space: object requires documentation	☐
4	003	InfoCube tables without index statistics	Space: object requires documentation	☐
5	004	Inconsistently compressed Basis InfoCube requests	Space: object requires documentation	☐
6	005	Property: BACKUP_TABLES_BEFORE_REPAIR	Space: object requires documentation	☐
7	006	InfoCube dimension tables with missing indexes/obsolete index layout	Space: object requires documentation	☐
8	007	Shadow tables (@k tables) resulting from an incomplete partition drop	Space: object requires documentation	☐
9	008	InfoCube E-Fact tables with missing indexes/obsolete index layout	Space: object requires documentation	☐
10	009	InfoCube F-Fact tables with missing indexes/obsolete index layout	Space: object requires documentation	☐
11	010	Property: ONLINE	Space: object requires documentation	☐
12	011	Property: MAXDOP	Space: object requires documentation	☐
13	012	Uncompressed fact tables (SQL Server decimal compression)	Space: object requires documentation	☐
14	013	Missing and superfluous partitions of F-Fact tables	Space: object requires documentation	☐
15	014	Property: CHECK_TABLE	Space: object requires documentation	☐
16	015	Partitioned F-Fact tables that can be unpartitioned	Space: object requires documentation	☐
17	016	Unpartitioned F-Fact tables that can be partitioned	Space: object requires documentation	☐
18	017	Tables containing many partitions	Space: object requires documentation	☐
19	018	Property: NUMBER_OF_PARTITIONS	Space: object requires documentation	☐
20	019	Parallel rapair runs are prohibited for this check	Space: object requires documentation	☐
21	020	Backup tables created by this program	Space: object requires documentation	☐
22	021	To be updated	The short text describes the object sufficiently	☐
23	022	To be deleted	The short text describes the object sufficiently	☐
24	023	To be created	The short text describes the object sufficiently	☐
25	024	Scheduled...	The short text describes the object sufficiently	☐
26	025	Running...	The short text describes the object sufficiently	☐
27	026		The short text describes the object sufficiently	☐
28	027		The short text describes the object sufficiently	☐
29	028		The short text describes the object sufficiently	☐
30	029		The short text describes the object sufficiently	☐
31	030		The short text describes the object sufficiently	☐
32	031	(Job:&1)	The short text describes the object sufficiently	☐
33	032	Dialog processing	The short text describes the object sufficiently	☐
34	033	No log entries found	The short text describes the object sufficiently	☐
35	034	No check results to display	The short text describes the object sufficiently	☐
36	035	Check and repair log display were refreshed	The short text describes the object sufficiently	☐
37	036	Data dictionary could not generate the CREATE INDEX statement	The short text describes the object sufficiently	☐
38	037	Data dictionary could not activate the index	The short text describes the object sufficiently	☐
39	038	Error occured while determining indexes from InfoCube activator(&1)	The short text describes the object sufficiently	☐
40	039	SAP standard index &1 is missing in dictionary	The short text describes the object sufficiently	☐
41	040	SAP standard index &1 exists in dictionary but is missing in database	The short text describes the object sufficiently	☐
42	041	Index field &1 is missing in index &2	The short text describes the object sufficiently	☐
43	042	SAP standard definition for index &1 is &2	The short text describes the object sufficiently	☐
44	043	Current definition is &1	The short text describes the object sufficiently	☐
45	044	Existing index &1 is not an SAP standard index	The short text describes the object sufficiently	☐
46	045	Define it as extension index in SE11 to keep it during repair	The short text describes the object sufficiently	☐
47	046	Index field &1 must not be included in SAP standard index &2	The short text describes the object sufficiently	☐
48	047	Data package &1 = &2 (&3 rows transferred)	The short text describes the object sufficiently	☐
49	048	All data rows have been transferred in one batch (&1)	The short text describes the object sufficiently	☐
50	049	Error occured while transferring data	The short text describes the object sufficiently	☐
51	050	Error occured while transferring datapackage &1 = &2	The short text describes the object sufficiently	☐
52	051	You can rerun the repair run to complete the data transfer	The short text describes the object sufficiently	☐
53	052	Data transfer succeeded. &1/&2 data rows inserted	The short text describes the object sufficiently	☐
54	053	Index created successfully in database	The short text describes the object sufficiently	☐
55	054	Check system log for details on the error	The short text describes the object sufficiently	☐
56	055	Index creation options:	The short text describes the object sufficiently	☐
57	056	DROP INDEX statement generated	The short text describes the object sufficiently	☐
58	057	CREATE &INDEX statement generated	The short text describes the object sufficiently	☐
59	058	New index include columns will be:	The short text describes the object sufficiently	☐
60	059	No index include columns have been defined	The short text describes the object sufficiently	☐
61	060	Waiting for statement execution via background job...	The short text describes the object sufficiently	☐
62	061	Clustered indexes cannot have include columns	The short text describes the object sufficiently	☐
63	062	&1 remove include columns or remove clustered property	The short text describes the object sufficiently	☐
64	063	Index &1 is already clustered. Only one clustered index is possible	The short text describes the object sufficiently	☐
65	064	Do you want to uncluster index &1 and cluster index &2 instead?	The short text describes the object sufficiently	☐
66	065	Backup table could not be deleted in database	The short text describes the object sufficiently	☐
67	066	Error while creating backup table for package dimension	The short text describes the object sufficiently	☐
68	067	Table &1 was backed up to &2	The short text describes the object sufficiently	☐
69	068	Initial package dimension record DIMID = 0	The short text describes the object sufficiently	☐
70	069	0REQUID = 0 could not be written	The short text describes the object sufficiently	☐
71	070	0REQUID = 0 has been written successfully	The short text describes the object sufficiently	☐
72	071	Could not delete unnecessary DIMID = 0 from package dimension	The short text describes the object sufficiently	☐
73	072	Deleted inconsistent package dimension record with &1 &2	The short text describes the object sufficiently	☐
74	073	Error while creating backup table for E-Fact table	The short text describes the object sufficiently	☐
75	074	Could not set value &1 for &2&3 in table &4. Action rolled back.	The short text describes the object sufficiently	☐
76	075	Corrected E-Fact table records with &1 = &2 to &1 = &3	The short text describes the object sufficiently	☐
77	076	Cannot automatically repair orphan request in F-Fact table	The short text describes the object sufficiently	☐
78	077	&1 in package dimension is &2; &3 is &4	The short text describes the object sufficiently	☐
79	078	Error occured while creating statistics	The short text describes the object sufficiently	☐
80	079	Vardecimal storage format has been enabled for database &1	The short text describes the object sufficiently	☐
81	080	Error while enabling vardecimal storage format in database &1	The short text describes the object sufficiently	☐
82	081	Error while enabling vardecimal storage format for this table	The short text describes the object sufficiently	☐
83	082	Table is not a dimension table or does not exist	The short text describes the object sufficiently	☐
84	083	Could not get table lock for processing the table	The short text describes the object sufficiently	☐
85	084	Not all indexes could be activated	The short text describes the object sufficiently	☐
86	085	Could not drop primary key from currently processed table	The short text describes the object sufficiently	☐
87	086	Table to repair is not an E-Fact table or does not exist	The short text describes the object sufficiently	☐
88	087	Table to repair is not an F-Fact table or does not exist	The short text describes the object sufficiently	☐
89	088	Table does not exist in database	The short text describes the object sufficiently	☐
90	089	Cannot determine SAP standard indexes for the table	The short text describes the object sufficiently	☐
91	090	Error calling function module &1	The short text describes the object sufficiently	☐
92	091	Could not determine partitioning column of F-Fact table	The short text describes the object sufficiently	☐
93	092	Partition with boundary &1 &2 has been created	The short text describes the object sufficiently	☐
94	093	Partition with boundary &1 &2 could not be created. &3	The short text describes the object sufficiently	☐
95	094	Errors occured while creating missing partitions (see above)	The short text describes the object sufficiently	☐
96	095	Partition with boundary &1 &2 was dropped because it was empty	The short text describes the object sufficiently	☐
97	096	Partition with boundary &1 &2 could not be dropped. &3	The short text describes the object sufficiently	☐
98	097	Errors occured while creating/dropping partitions	The short text describes the object sufficiently	☐
99	098	Error occured while unpartitioning the table	The short text describes the object sufficiently	☐
100	099	Shadow table could not be deleted in database	The short text describes the object sufficiently	☐
101	100	Error occured while partitioning the table	The short text describes the object sufficiently	☐
102	101	Repair finished successfully (back check succeeded)	The short text describes the object sufficiently	☐
103	102	Repair finished with errors (back check failed)	The short text describes the object sufficiently	☐
104	103	Repair finished successfully (back check not available)	The short text describes the object sufficiently	☐
105	104	Unknown inherited error occured	The short text describes the object sufficiently	☐
106	105	&1 of &2 items were repaired successfully (see details above)	The short text describes the object sufficiently	☐
107	106	&1 of &2 items were not repaired (see details above)	The short text describes the object sufficiently	☐
108	107	Backup table of aborted repair run renamed to original table (&1 => &2)	The short text describes the object sufficiently	☐
109	108	Original table renamed to backup table (&1 => &2)	The short text describes the object sufficiently	☐
110	109	Reset renaming. Continue based on state of previously aborted run	The short text describes the object sufficiently	☐
111	110	Secondary indexes have been created	The short text describes the object sufficiently	☐
112	111	No longtext available for this check. Read SAP note &1 for a description.	The short text describes the object sufficiently	☐
113	112	Error while creating secondary indexes	The short text describes the object sufficiently	☐
114	113	Aborted repair run found. Table &1 is reused for this run	The short text describes the object sufficiently	☐
115	114	Clustered index has been created in database	The short text describes the object sufficiently	☐
116	115	Error while creating clustered index in database (SQL Error)	The short text describes the object sufficiently	☐
117	116	Partitioned table &1 has been created in database	The short text describes the object sufficiently	☐
118	117	Unpartitioned table &1 has been created in database	The short text describes the object sufficiently	☐
119	118	Error occured while creating table in database (SQL Error)	The short text describes the object sufficiently	☐
120	119	&1 while processing table/index &2	The short text describes the object sufficiently	☐
121	120	SQL Error(s)&1 occured	The short text describes the object sufficiently	☐
122	121	Dialog processing mode enabled	The short text describes the object sufficiently	☐
123	122	Background processing mode enabled	The short text describes the object sufficiently	☐
124	123	Expert mode enabled	The short text describes the object sufficiently	☐
125	124	Switched back to standard mode	The short text describes the object sufficiently	☐
126	125	Specify a table before selecting an index	The short text describes the object sufficiently	☐
127	126	Selected check offers no items to repair	The short text describes the object sufficiently	☐
128	127	Error while creating application log	The short text describes the object sufficiently	☐
129	128	Error in &1: Calling &2 failed.	The short text describes the object sufficiently	☐
130	129	The table is a backup table of &1 created during repair run of check &2	The short text describes the object sufficiently	☐
131	130	InfoCube &1 does not exist or has no active version. No check possible	The short text describes the object sufficiently	☐
132	131	InfoCube &1 contains &2 uncompressed requests	The short text describes the object sufficiently	☐
133	132	No InfoCube/s with more than &1 uncompressed requests found.	The short text describes the object sufficiently	☐
134	133	Check executed with restriction/s &	The short text describes the object sufficiently	☐
135	134	Initial P-Dimension entry is missing in table &1	The short text describes the object sufficiently	☐
136	135	Inconsistently compressed request in E-Fact table	The short text describes the object sufficiently	☐
137	136	Orphan request in F-Fact table. 0REQUID in package dimension is 0	The short text describes the object sufficiently	☐
138	137	Cube contains inconsistent requests	The short text describes the object sufficiently	☐
139	138	No inconsistent requests found for Basis InfoCube	The short text describes the object sufficiently	☐
140	139	Not all table indexes have statistics	The short text describes the object sufficiently	☐
141	140	No InfoCube without statistics found	The short text describes the object sufficiently	☐
142	141	Table is not vardecimal compression enabled.	The short text describes the object sufficiently	☐
143	142	Table indexes are not compatible to the SAP standard (Repair optional)	The short text describes the object sufficiently	☐
144	143	No inconsistent indexes found	The short text describes the object sufficiently	☐
145	144	Table does not exist in database. Check has been skipped for this table.	The short text describes the object sufficiently	☐
146	145	Partition missing for request &1 (DIMID = &2)	The short text describes the object sufficiently	☐
147	146	Unnecessary empty partition found for InfoCube request &1(DIMID = &2)	The short text describes the object sufficiently	☐
148	147	Missing/unnecessary partitions found for F-Fact table of InfoCube &1	The short text describes the object sufficiently	☐
149	148	No missing/unnecessary partitions found	The short text describes the object sufficiently	☐
150	149	Table is partitioned	The short text describes the object sufficiently	☐
151	150	No partitioned table found	The short text describes the object sufficiently	☐
152	151	Tables residing from a partition drop can be deleted.	The short text describes the object sufficiently	☐
153	152	No shadow tables found	The short text describes the object sufficiently	☐
154	153	Table contains &1 partitions	The short text describes the object sufficiently	☐
155	154	Table &1 does not have more than &2 partitions	The short text describes the object sufficiently	☐
156	155	Table &1 does not exist in database. Check returned no result.	The short text describes the object sufficiently	☐
157	156	No tables with more than &1 partitions found	The short text describes the object sufficiently	☐
158	157	Prerequisite check "&1" returned issues for the corresponding InfoCube.	The short text describes the object sufficiently	☐
159	158	&1 Execute that check/repair first	The short text describes the object sufficiently	☐
160	159	Prerequisite check &1 returned more than &2 uncompressed requests.	The short text describes the object sufficiently	☐
161	160	SAP recommends to compress the InfoCube to have less than &1	The short text describes the object sufficiently	☐
162	161	&1 uncompressed requests left for query performance reasons	The short text describes the object sufficiently	☐
163	162	Table is not partitioned.	The short text describes the object sufficiently	☐
164	163	No relevant unpartitioned BW tables found	The short text describes the object sufficiently	☐
165	164	Check did not find relevant tables that can be decimal compressed	The short text describes the object sufficiently	☐
166	165	Check did not find backup table that can be deleted	The short text describes the object sufficiently	☐
167	166	Table indexes are not compatible to the SAP standard	The short text describes the object sufficiently	☐
168	167	Index &1 is currently clustered.Instead index &2 should be clustered	The short text describes the object sufficiently	☐
169	168	Index &1 should be created with option COLUMNSTORE=&2	The short text describes the object sufficiently	☐
170	169	Index/primary key &1 must be unique	The short text describes the object sufficiently	☐
171	170	Table &1 does not have a clustered primary key	The short text describes the object sufficiently	☐
172	171	SAP standard dictionary index &1 may not exist in DB	The short text describes the object sufficiently	☐
173	172	Index &1 is expected to be clustered	The short text describes the object sufficiently	☐
174	173	The definition of index &1 does not match SAP standard or is obsolete	The short text describes the object sufficiently	☐
175	174	Log message longtext	The short text describes the object sufficiently	☐
176	175	Display longtext	The short text describes the object sufficiently	☐
177	176	Executing checks is possible for items without scheduled repairs only	The short text describes the object sufficiently	☐
178	177	Backup table	The short text describes the object sufficiently	☐
179	178		The short text describes the object sufficiently	☐
180	179		The short text describes the object sufficiently	☐
181	180		The short text describes the object sufficiently	☐
182	181	Columnstore index detected on this table. Maintenance is not allowed.	The short text describes the object sufficiently	☐
183	182	InfoCube and aggregate index consistency	Space: object requires documentation	☐
184	183	& is not a positive integer value.	The short text describes the object sufficiently	☐
185	184	The database table & does not exist.	The short text describes the object sufficiently	☐
186	185	InfoCube & is not a Basis InfoCube or does not exist	The short text describes the object sufficiently	☐
187	186	Aggregate & does not exist	The short text describes the object sufficiently	☐
188	187	InfoCube/aggregate & does not exist	The short text describes the object sufficiently	☐
189	188	InfoCube & does not exist	The short text describes the object sufficiently	☐
190	189	Cannot obtain enqueue for repairing the indexes of table &	The short text describes the object sufficiently	☐
191	190	Inherited error occurred while repairing the indexes of table &	The short text describes the object sufficiently	☐
192	191	Cannot obtain enqueue for table &	The short text describes the object sufficiently	☐
193	192	You are not authorized to run this report	The short text describes the object sufficiently	☐
194	193	The selected check does not offer a repair option	The short text describes the object sufficiently	☐
195	194	SQL error occurred: &	The short text describes the object sufficiently	☐
196	195	Internal error occurred: &	The short text describes the object sufficiently	☐
197	196	Include columns cannot be specified for partitioned tables/indexes	The short text describes the object sufficiently	☐
198	197	Include columns cannot be specified for primary keys	The short text describes the object sufficiently	☐
199	198	Check started at & &	The short text describes the object sufficiently	☐
200	199	Check finished at & &	The short text describes the object sufficiently	☐
201	200	Repair started at & &	The short text describes the object sufficiently	☐
202	201	Repair finished at & &	The short text describes the object sufficiently	☐
203	202	Index creation started in database at &2 &3	The short text describes the object sufficiently	☐
204	203	Index creation finished in database at &2 &3	The short text describes the object sufficiently	☐

History

Last changed on/by	20140121	SAP
SAP Release Created in	730