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