RSCV -
The following messages are stored in message class RSCV: .
It is part of development package RSR in software component BW-BEX-ET. This development package consists of objects that can be grouped under "BW: General reporting processor".
It is part of development package RSR in software component BW-BEX-ET. This development package consists of objects that can be grouped under "BW: General reporting processor".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ------------------------------------------------------------------------- |
| 001 | & & & |
| 009 | Generation no longer possible. Start the transaction again |
| 010 | Without errors and warnings |
| 011 | Disallowed entry for function module |
| 012 | Other eror & & & & |
| 013 | No results available. |
| 014 | No long text exists for message no. & in class & |
| 015 | Message &1 in class &2 of type &3 not found in language &4 |
| 016 | Please select a function module |
| 017 | No initialized languages found |
| 018 | System language for installed languages not found |
| 020 | InfoCube & was not found. |
| 021 | Error when reading the InfoCatalog of InfoCube &. |
| 022 | InfoObject & was not found in the InfoCube & |
| 023 | Table names could not be determined from InfoObject &. |
| 024 | Invalid entry & InfoCube &. |
| 025 | First select an InfoCube |
| 026 | The data dictionary could not be read for the InfoCube & |
| 028 | Checking InfoCube & with function &. |
| 029 | Checking & produced no errors or warnings. |
| 030 | Manual table maintenance (SE16) was switched on for & |
| 040 | Documentation for function module not available in language &1 |
| 050 | Time characteristic &1 cannot be derived |
| 051 | Time characteristic &1 is checked against time characteristic &2 |
| 052 | Start of check |
| 053 | Record with the DIMID &1 contains non-compatible time characteristics |
| 054 | Time characteristic &1 value &2 does not fit with time char &3 val &4 |
| 055 | End of check. &1 data records have errors |
| 056 | Consistency of time dimension of InfoCube &1 |
| 057 | InfoCube &1 has no time dimension, or FISCVARNT is missing |
| 058 | InfoCube &1 does not exist or is not active |
| 059 | The following checks were carried out: |
| 060 | InfoCube &1 was marked as a Cube with a consistent time dimension |
| 061 | InfoCube &1 was marked as a Cube with an inconsistent time dimension |
| 062 | Table &1 contains &2 data records with an incorrect partition column |
| 063 | Table &1 contains no records with an incorrect partitioning column |
| 064 | Test of partitioning column of InfoCube &1 |
| 065 | Aggregates were deactivated. You must reconstruct them |
| 066 | Aggregates could not be automatically deactivated |
| 067 | Correcting table &1 |
| 068 | Processing &1 different DIMIDs (dimension keys) |
| 069 | This DIMID is used by &1 records of the fact tables |
| 070 | This DIMID is no longer used in the fact table |
| 071 | Time dimension entries not being used are to be removed |
| 072 | Time dimension entries not being used were successfully removed |
| 073 | Error when removing entries not being used |
| 074 | Time dimension entries not being used removed from &1 |
| 075 | Error when reading metadata for InfoCube &1 |
| 076 | InfoCube &1 is not partitioned. Test not carried out |
| 077 | Metadata inconsistency in InfoCube &1. Test not carried out |
| 078 | InfoCube &1 does not contain a time dimension. Test not carried out |
| 079 | An SQL error occured in the data repair. Process not ended |
| 080 | Total of &1 records repaired in table &2 |
| 081 | Changes were committed |
| 082 | Consistency of time dimension of all InfoCubes |
| 083 | No master data found for characteristic of test described subsequently |
| 084 | Fiscal year period is too large |
| 085 | Error when deriving or determining fiscal year period |
| 086 | Correction not necessary for InfoCube &1 |
| 087 | The partitioning column for InfoCube &1 is repaired |
| 088 | The following table contains suggested corrections |
| 089 | Execute suggested repairs in the time dimension table |
| 090 | Errors occurred while changing dimension table. Changes rolled back |
| 091 | The modified records were successfully written into the table |
| 092 | Additional &1 data records contain errors |
| 093 | Data records with a different fiscal variant already exist |
| 094 | Data records exist for one fiscal variant only |
| 095 | Fiscal variant can be subsequently set to a fixed value |
| 096 | Fiscal variant is not specified |
| 097 | Time characteristics are inconsistent |
| 098 | Only partial time characteristics. Check not possible |
| 099 | Cannot check partial time characteristics due to missing year |
| 100 | Time consistency check only possible for InfoCubes and Standard DSOs |
| 101 | Initial value for time is not allowed in NCUM provider |
| 102 | Maximum value for time is not allowed in NCUM provider |
| 103 | The time characteristics of a reference point record are inconsistent |
| 106 | DATAFL for SID &1 in SID table &2 not set |
| 107 | Checking of dimension '&1' (&2) produced errors or warnings |
| 108 | No errors: Dimension '&1' characteristic '&2' |
| 109 | Checking dimension '&1' characteristic '&2' |
| 110 | Module RSDG_CUBE_CHECK established an error in InfoCube & |
| 111 | Type of incorrect InfoObject is '&'. |
| 112 | The error affects InfoObject '&' |
| 113 | Referenced InfoObject '&' is incorrect. |
| 114 | Dimension '&' is incorrect |
| 115 | Number of errors: & |
| 116 | Checking InfoCube & with & without errors and warnings. |
| 117 | Check of the database indices could not be generated |
| 118 | Database index & is of type & |
| 119 | A BITMAP index for index &, field &2 (cat. &3) improves response times |
| 120 | One or more SIDs for the InfoObject are incorrect |
| 121 | No errors in the SID table for InfoObject &. |
| 122 | SID table does not exist for InfoObject &. |
| 123 | Master data table & does not exist for InfoObject &. |
| 124 | Dimension table & does not have any entries for version & |
| 125 | Default entry SID=0 missing in SID table &, InfoObject & |
| 126 | More than one SID = 0 in entry in SID table &, InfoObject & |
| 127 | In row &4 of table &1, the value '&3' has the SIF = 0, InfoObject &2 |
| 128 | SID table & has no entries. |
| 129 | Master data table & has no entries for version &. |
| 130 | Entry &1 in SID table of char. &2 is missing in master data table &3 |
| 131 | Entry & in master data table does not have an SID. |
| 132 | SID=0 Entry &1 in &2 also contained in master data &3 of InfoObject &4. |
| 133 | Checking SID for InfoObject & InfoCube & tables: & and & |
| 134 | Entry & in SID table & without CHCKFL although data is present in &. |
| 135 | Master data table & exists for InfoObject & but NOVALFL = 'X'. |
| 136 | Checking of MID table & produced warnings. |
| 137 | Checking of SID table & produced errors. |
| 138 | Field name could not be read for InfoObject & (CHABSNM &). |
| 139 | SIF & of InfoObject & appears several times, but must be unique |
| 140 | Dimension table '&' (techn. name &) does not exist for InfoCube & |
| 141 | Checking dimension no. &, '&' (techn. name &, table &) |
| 142 | No error in dimension no. &, '&' (techn. name &, table &) |
| 143 | Entry & in master data table & is missing in SID table & (InfoObject &) |
| 144 | Entry &1 in dimension table &2 is missing in SID table &3 |
| 145 | ID & of dimension & of the fact table is missing in dimension table & |
| 146 | ID 0 of dimension & of the fact table is missing in dimension table & |
| 147 | Entry & in table & cannot be derived from table & |
| 148 | Entry & in table & is not compatible with table & |
| 149 | Check of fact table / dimension &1 produced errors or warnings |
| 150 | No hierarchy exists for InfoObject & |
| 151 | No hierarchy data exists for InfoObject & in table & |
| 152 | Hierarchy &3 (SIF &1) for InfoObject &2 has obsolete version ' ' |
| 153 | No data for hierarchy &4 (SIF &1) version &2 in table &3 |
| 154 | Checking hierarchy &3 (SIF &1) version &2 |
| 155 | Hierarchies from InfoObject & o.k. |
| 156 | ROOTSID & is missing in inclusion table of hierarchy & version & |
| 157 | ROOTSID & jumps to & and not to & |
| 158 | RESTLEAF & has & as PRED & and not & |
| 159 | Hierarchy node has FACTOR = &, but the value must be 1 |
| 160 | Hierarchy screen & has SUM(FACTOR)=&, but the value must be 1 |
| 161 | Hierarchy screen & of type RESTLEAF is not unique |
| 162 | Hierarchy node & of type RESTNODE is not unique |
| 163 | Hierarchy leaf & is missing in the SID table |
| 164 | Hierarchy sheet & with SID & does not have INCFL flag in the SID table |
| 165 | Predecessor & of node & (LISTNO &) is not contained in the hierarchy |
| 166 | InfoCube & does not contain any InfoObjects with hierarchies |
| 167 | Hierarchy &2 (SIF &1) is defective. |
| 170 | Checks navigation attribute & (tables & and &) |
| 171 | Table & does not exist |
| 172 | There are no records in table & for records &, & |
| 173 | The check of navigation attribute & produced errors |
| 174 | The check of navigation attribute & produced warnings |
| 175 | Navigation attribute & without errors and warnings |
| 176 | No navigation attributes available |
| 177 | Master data of navigation attribute &1 in InfoCube &2 is incorrect. |
| 180 | Record with initial unit dimension (&) does not have initial key figures |
| 181 | Checking the units of InfoCube & produced errors |
| 182 | Checking the units of InfoCube & produced warnings |
| 183 | Checking the units of InfoCube & without errors and warnings |
| 184 | InfoCube & does not contain a dimension |
| 189 | No information from database system &1 contained for InfoCube &1 |
| 190 | The number of indices of InfoCube &1 is incorrect |
| 191 | Star transformation is not switched on |
| 192 | Merge area for bitmaps is too small (& < & MByte) |
| 193 | 'Create' area for bitmaps is too small (& < & MByte) |
| 194 | Index &1, field &2 (status &3) is invalid |
| 195 | InfoCube &1 indices are correctly set |
| 196 | Database parameters for star transformation and bitmap indices o.k. |
| 197 | Index &1, field &2 is of type &3 |
| 198 | The indices of InfoCube &1 are incorrectly set |
| 200 | Unique ID for program generation could not be created |
| 201 | Deletion of generated program & refused (authorization ?) |
| 202 | Error when deleting generated program &. |
| 203 | Template & not found when generating |
| 204 | Syntax error in template class & |
| 205 | Syntax error in generated program & (row &, message: &) |
| 206 | Program generated for InfoObject & |
| 207 | Invalid program class & |
| 208 | Unique program ID & invalid |
| 209 | Generation not possible due to external lock & |
| 210 | InfoObject &1: System error when generating &2 |
| 211 | Internal error function module RSS_PROGRAM_GENERATE |
| 212 | Error in row & |
| 213 | Generation of utility routines for characteristic & ... |
| 220 | Fact table &1 has not yet been analyzed |
| 221 | Fact table &1 was last analyzed &2 days ago |
| 222 | Dimension table &1 has never been analyzed |
| 223 | Dimension table &1 was last analyzed &2 days ago |
| 224 | Index &1 has never been analyzed |
| 225 | Index &1 was last analyzed &2 days ago |
| 226 | DB Statistics fact-, dimension table and indices are o.k. |
| 227 | DB statistics for InfoCube &1 must be recreated |
| 228 | DB statistics for InfoCube &1, table &2 must be recreated |
| 229 | Table &1 has &2 entries. Size corresponds to &3% of the InfoCube |
| 230 | Line item dimension &1 is not checked |
| 250 | An entry is missing in table RSMDATASTATE for InfoCube &1 |
| 251 | Condition &2 is not fulfilled for InfoCube &1 |
| 252 | RSMDATASTATE blank, although InfoCube &1 &2 contains trans. data records |
| 253 | Internal error when checking InfoCube &1 (RSDU_DATA_EXISTS_INFOCUBE) |
| 254 | Entry in RSMDATASTATE is initial although there is data in InfoCube &1 |
| 260 | Master data of characteristic &1 is consistent |
| 261 | The initial entry in the master data of characteristic &1 is missing |
| 262 | &1 Entries exist several times in master data of &1 |
| 263 | Master data of &1 has &2 overlapping entries in version '&3' |
| 264 | Master data of &1 display &2 gaps in version '&3' |
| 265 | Invalid record with version '&2', changed='&3' for &1 found |
| 266 | The master data cannot be checked for InfoObject &1 |
| 267 | Following errors occurred during master data check for char. &1: |
| 270 | No queries avaialble for InfoCube &1 |
| 271 | Query "&2" could not be found for InfoCube &1 |
| 272 | Errors occurred when loading query "&2" of InfoCube &1 |
| 273 | Query "&2" of InfoCube &1 could not be generated |
| 274 | Generation of query "&2" of InfoCube &1 produced the following errors |
| 275 | Queries of InfoCube &1 are all correct |
| 276 | Analyzing query &1 |
| 277 | Query &1 was generated without errors |
| 278 | The name (COMPID) for the query is blank (COMPUID &1, GENUNIID &2) |
| 300 | Check &1 (&2) successfully started in the background |
| 301 | Check &1 (&2) successfully started in the background (&3) |
| 320 | Checking the time-dependent master data produced no errors |
| 321 | Checking the time-dependent master data produced warnings |
| 322 | Checking the time-dependent master data produced errors or warnings |
| 323 | InfoCube &1 has no InfoObjects with time-dependent master data |
| 330 | InfoCube &1 has no InfoObjects with master data |
| 331 | Check of master data &1 &2 produced neither errors nor warnings |
| 332 | Check of master data &1 &2 produced warnings |
| 333 | Check of master data &1 &2 produced errors or warnings |
| 334 | Check of master data InfoObject &1, table &2 |
| 335 | Master data '&1' in table &2 (char. &3) contains disallowed characters |
| 336 | Master data of char. &1 (table &2) contain characters not permitted |
| 337 | Master data '&1' in table &2 (characteristic &3) contains small letters |
| 338 | Reconstruction of aggregates and hierarchies started in the background |
| 339 | Program 'RSR_ERROR_REPORT' could not be deleted |
| 340 | Aggregate &1 could not be filled |
| 341 | Node '&1' for hierarchy &2 (characteristic &3) contains small letters |
| 342 | Node '&1' for hierarchy &2 (char. &3) contains non-permitted characters |
| 343 | Check hierarchies for InfoObject &1 |
| 344 | Hierarchy '&1' for InfoObjects &2 could not be activated |
| 345 | Status of number range for characteristic &1 is &2 too small |
| 346 | Status of number range for characteristic &1 is correct |
| 347 | Number range object for characteristic &2 does not exist |
| 348 | The number range interval for characteristic &1 does not exist |
| 350 | Entry &1 in table &2 is invalid |
| 355 | Status of number range &1 for dimension &2 is &3 too small |
| 356 | The status of number range &1 for dimension &2 is correct |
| 357 | Number range object &1 for dimension &2 is missing |
| 360 | PSA table &1 is not partitioned in database |
| 361 | PSA table &1 ; request &2 partition &3, packages are in partition &4 |
| 362 | Inconsistency: High value for table &1: &2 ; PARTNO value in RSTSODS: &3 |
| 400 | Available repairs have been successfully carried out (see results) |
| 401 | No repairs were necessary |
| 402 | No repairs were carried out |
| 403 | A repair could not be successfully be carried out |
| 404 | Repair for Message &1 (Object &2) Failed |
| 405 | Repair for Message &1 (Object &2) Carried Out Successfully |
| 410 | Multiple SIF &1 of InfoObject &2 is generated with a number range |
| 411 | Multiple SIF &1 of InfoObject &2 is generated with an Exit module |
| 412 | Multiple SIF &1 of InfoObject &2 is generated in an unknown way |
| 440 | InfoObject &1 references basic InfoObject &2 |
| 441 | Characteristic value with SID &1 of InfoObject &2 not being used |
| 442 | InfoObject &1 is a navigation attribute |
| 500 | Table &1 is analyzed |
| 501 | Table &1 can be ignored |
| 502 | The number of secondary indexes for InfoCube &1 is correct |
| 503 | The fact table of InfoCube &1 is missing &2 secondary indexes |
| 504 | Index &1 type is OK (type &2) |
| 505 | Index &1 type is &2. Type &3 was expected |
| 506 | Index &1 is &2 |
| 507 | Index &1 is &2. &3 was expected |
| 508 | Read Note 401242 when analyzing index problems |
| 509 | --- reserved for DB-independent messages |
| 510 | --- reserved for DB-independent messages |
| 511 | --- reserved for DB-independent messages |
| 512 | --- reserved for DB-independent messages |
| 513 | --- reserved for DB-independent messages |
| 514 | --- reserved for DB-independent messages |
| 515 | --- reserved for DB-independent messages |
| 516 | --- reserved for DB-independent messages |
| 517 | --- reserved for DB-independent messages |
| 518 | --- reserved for DB-independent messages |
| 519 | --- reserved for DB-independent messages |
| 520 | ORACLE: Table &1 has not yet been analyzed |
| 521 | ORACLE: Statistics information for table &1 may be obsolete |
| 522 | ORACLE: Check in progress; statistics in table &1 are current |
| 523 | ORACLE: The status of index &1 is OK |
| 524 | ORACLE: The status of index &1 is &2 |
| 525 | ORACLE: Index &1 has possibly degenerated |
| 526 | ORACLE: No degenerated indexes were found for InfoCube &1. |
| 527 | ORACLE: Parameter &1 is set to value &2 (recommended value is &3) |
| 528 | Current recommendations for Oracle parameters are in SAP Note 830576 |
| 529 | Existence of catalog synonyms (SAP Notes 519448, 565416) is checked |
| 530 | ORACLE: Synonym &1 exists |
| 531 | ORACLE: Synonym &1 does not exist. See SAP Notes 519448, 565416 |
| 532 | Existence of catalog indexes (SAP Note 519407) is checked |
| 533 | ORACLE: Catalog index &1 exists |
| 534 | ORACLE: Catalog index &1 does not exist. See SAP Note 519407 |
| 535 | Existence of catalog statistics (SAP Note 558746) is checked |
| 536 | ORACLE: Catalog statistics are missing. Refer to SAP Note 558746 |
| 537 | ORACLE: Obsolete database version: &1 |
| 538 | ORACLE: |
| 539 | ORACLE: |
| 540 | INFORMIX: No 'Update statistics' has been carried out yet for table & |
| 541 | INFORMIX: Database statistics for table &1 are current (Threshold: &2 %) |
| 542 | INFORMIX: Database statistics for table &1 are obsolete (Threshold: &2 %) |
| 543 | INFORMIX: The status of index &1 is OK |
| 544 | INFORMIX: The status of index &1 is 'not active' (disabled) |
| 545 | INFORMIX: The type for index &1 is OK: Detached from the Basis table |
| 546 | INFORMIX: The type for index &1 is OK: Fragmented acc. to Basis table |
| 547 | INFORMIX: Index &1 does not have the expected type: 'Detached Index' |
| 548 | INFORMIX: Index &1 does not have the expected type: (Fragmented Strategy) |
| 549 | INFORMIX: The type for index &1 is not known |
| 550 | INFORMIX: ONCONFIG Parameter &1 equals &2 (recommended value is &3) |
| 551 | INFORMIX: Environment variable &1 equals &2 (recommended value is &3) |
| 554 | INFORMIX: Database Statistics for Table and Not Current (Indices) |
| 555 | INFORMIX: |
| 556 | INFORMIX: |
| 557 | INFORMIX: |
| 558 | INFORMIX: |
| 559 | INFORMIX: |
| 560 | SQL SERVER: Empty |
| 561 | SQL SERVER: Status OK |
| 562 | SQL SERVER: Index status OK |
| 563 | SQL SERVER: Status Wrong |
| 564 | SQL SERVER: The status of index &1 is OK |
| 565 | SQL SERVER: The status of the index &1 is &2 |
| 566 | SQL SERVER: Not used |
| 567 | SQL SERVER: Not used |
| 568 | SQL SERVER: Not used |
| 569 | SQL SERVER: Not used |
| 570 | SQL SERVER: Not used |
| 571 | SQL SERVER: Not used |
| 572 | SQL SERVER: Not used |
| 573 | SQL SERVER: Not used |
| 574 | SQL SERVER: Not used |
| 575 | SQL SERVER: Not used |
| 576 | SQL SERVER: Not used |
| 577 | SQL SERVER: Not used |
| 578 | SQL SERVER: Not used |
| 579 | SQL SERVER: Not used |
| 580 | DB2/UDB: Table &1 has not yet been analyzed |
| 581 | DB2/UDB: Statistics for table &1 were generated &2 days ago, max. &3 OK |
| 582 | DB2/UDB: Statistics for table &1 were generated &2 days ago |
| 583 | DB2/UDB: Index &1 created correctly |
| 584 | DB2/UDB: Index &1 is missing or is not correct in the ABAP dictionary |
| 585 | DB2/UDB: Stored procedures are not currently supported |
| 586 | DB2/UDB: The representative primary index&1 is OK |
| 587 | DB2/UDB: The representative primary index &1 is missing or is not correct |
| 588 | DB2/UDB: The representative primary index &1 is not unique. |
| 589 | DB2/UDB: Index &1 is not a clustering index |
| 590 | DB2/UDB: Partitioning key for table &1 is missing or incorrect. |
| 591 | DB2/UDB: Partitioning key for table &1 is correct. |
| 592 | DB2/UDB: Clustering of table &1 is not correct |
| 593 | DB2/UDB: Clustering of table &1 is not correct |
| 594 | DB2/UDB: The MDC columns of table &1 are not correct |
| 595 | DB2/UDB: The index &1 is missing from the database |
| 596 | DB2/UDB: |
| 597 | DB2/UDB: |
| 598 | DB2/UDB: |
| 599 | DB2/UDB: |
| 600 | DB2-z/OS: Table &1 has not yet been analyzed |
| 601 | DB2-z/OS: Statistics for table &1 were generated &2 days ago, max. &3 OK |
| 602 | DB2-z/OS: Statistics for table &1 were generated &2 days ago |
| 603 | DB2-z/OS: Index &1 is OK |
| 604 | DB2-z/OS: Index &1 is &2 |
| 605 | DB2-z/OS: Stored procedures are not currently supported |
| 606 | DB2-z/OS: Triggers are not currently supported |
| 607 | DB2-z/OS: Index &1 is in REBUILD PENDING mode |
| 608 | DB2-z/OS: Status of index &1 cannot be determined (rfcoscol?) |
| 609 | DB2/390: |
| 610 | DB2/390: |
| 611 | DB2-z/OS: No entry in RTS table for table &1 |
| 612 | DB2-z/OS: &2 % of data changed in table &1 |
| 613 | DB2-z/OS: Statistics from &1 are no longer up-to-date (&2) |
| 614 | DB2-z/OS: No entry in TABLESPACESTATS for table &1 partition &2 |
| 615 | DB2-z/OS: &3 % of data has changed in partition &2 from &1 |
| 616 | DB2-z/OS: Statistics from partition &2 from &1 are not up-to-date (&3) |
| 617 | DB2/390: |
| 618 | DB2/390: |
| 619 | DB2/390: |
| 620 | --- Beginning DB2/400 Messages --- |
| 621 | Index &1 exists, but index &2 was expected |
| 622 | The number of indexes for InfoCube &1 is correct |
| 623 | The status of index &1 is ok |
| 624 | The status of index &1 is not OK |
| 625 | DB2/400: The type of index &1 is OK (type &2) |
| 626 | DB2/400: The type of index &1 is &2, but type &3 was expected |
| 627 | DB2/400: Parameter &1 is set to value &2 (recommended value is &3) |
| 628 | DB2/400: The index &1 is &2 |
| 629 | DB2/400: The index &1 is &2, but &3 was expected |
| 630 | Fact table for InfoCube &1 contains &2 additional indexes |
| 631 | Index &1 does not belong to the standard indexes |
| 632 | Index &1 does not exist in the data dictionary |
| 633 | Index &1 does not exist in the database |
| 634 | The number of indexes for InfoCube &1 is incorrect |
| 635 | &2 indexes are missing in the DDIC from the fact table of InfoCube &1 |
| 636 | &2 indexes are missing in the database from the fact table of InfoCube &1 |
| 637 | DB2/400: The indexes were successfully converted |
| 638 | DB2/400: Indexes from fact tables are missing |
| 639 | Read Note 407528 on the indexing schema of BW fact tables on IBM i |
| 640 | SAP DB: Table &1 has not been analyzed |
| 641 | SAP DB: Statistics information on table &1 may be obsolete |
| 642 | SAP DB: Table &1 was analyzed on &2 (sample &3 %) |
| 643 | SAP DB: Status of index &1 is OK |
| 644 | SAP DB: Status of index &1 is &2 |
| 645 | SAP DB: Type of index &1 is OK (type &2) |
| 646 | SAP DB: |
| 647 | SAP DB: |
| 648 | SAP DB: |
| 649 | SAP DB: |
| 650 | SAP DB: |
| 651 | SAP DB: |
| 652 | SAP DB: |
| 653 | SAP DB: |
| 654 | SAP DB: |
| 655 | SAP DB: |
| 656 | SAP DB: |
| 657 | SAP DB: |
| 658 | SAP DB: |
| 659 | SAP DB: |
| 660 | SAP ASE: &1 &2 &3 &4 |
| 661 | &1 &2 &3 &4 |
| 662 | SAP ASE: |
| 663 | SAP ASE: The status of index &1 is OK |
| 664 | SAP ASE: The status of index &1 is &2 |
| 665 | SAP ASE: Statistics for table &1 are up to date |
| 666 | SAP ASE: Statistics for table &1 are obsolete |
| 667 | SAP ASE: Statistics for partition &1 of table &2 are obsolete |
| 668 | SAP ASE: DB index &1 inconsistent with DDIC source |
| 669 | SAP ASE: |
| 670 | SAP ASE: |
| 671 | SAP ASE: |
| 672 | SAP ASE: |
| 673 | SAP ASE: |
| 674 | SAP ASE: |
| 675 | SAP ASE: |
| 676 | SAP ASE: |
| 677 | SAP ASE: |
| 678 | SAP ASE: |
| 679 | SAP ASE: |
| 700 | Dimensions for InfoCube &1 contain unused entries |
| 701 | Dimensions for InfoCube &1 contain non-multiple entries |
| 800 | *********** Partitioning *************** |
| 801 | InfoCube & is not partitioned |
| 802 | InfoCube & is correctly partitioned |
| 803 | Partitioning settings for InfoCube & are not correct |
| 804 | Aggregate & is not partitioned |
| 805 | Aggregate & is correctly partitioned |
| 806 | Partitioning settings for aggregate & are not correct |
| 807 | Table & is correctly partitioned |
| 808 | Table & is not correctly partitioned |
| 809 | Table & is partitioned but it should not be |
| 810 | Table & could not be found in the database |
| 811 | Table & is not partitioned in the database |
| 812 | Table & is partitioned in the DB although it is not in the InfoCube |
| 813 | Partitioning details for table & could not be read |
| 814 | Table & does not have a partitioning column |
| 815 | Table & has partitioning column & |
| 816 | Partitioning column & is missing in table & |
| 817 | Table &1 has partitioning column &2 but it should be &3 |
| 818 | Table &1 has partitioning column &2 but should have none |
| 819 | Partition & from & to & is unnecessary |
| 820 | The partition from & to & is missing |
| 821 | The number of partitions in table & is correct |
| 822 | The partitioning type is & |
| 823 | The partitioning type is &; & was expected |
| 824 | The partitioning type is & but there should be no partitioning |
| 825 | Unknown partitioning type; & was expected |
| 826 | Unknown partitioning type but there should be no partitioning |
| 827 | The partitioning key is & |
| 828 | The partitioning key is &; & was expected |
| 829 | Table & has too many partitioning keys |
| 830 | Partition & starts at & |
| 831 | Partition & starts at &; & was expected |
| 832 | Partition & goes to & |
| 833 | Partition & extends to &; & was expected |
| 834 | The partition limit & is inclusive |
| 835 | The partition limit & is inclusive. Exclusive was expected. |
| 836 | The partition limit & is exclusive |
| 837 | The parition limit & is exclusive. Inclusive was expected. |
| 838 | Partition & is correct |
| 839 | Partition & is not correct |
| 840 | Consistency between InfoCube partitions and SAP administration |
| 841 | Expected: Partition by &1 from &2 to &3 |
| 842 | Expected: Partition by &1 (request ID) |
| 845 | F table of aggregate &1 is empty |
| 846 | F table of aggregate &1 has over 30 partitions |
| 847 | F table of aggregate &1 has over 50 partitions |
| 848 | E table of aggregate &1 is well partitioned |
| 849 | E table of aggregate &1 has too many partitions |
| 850 | E table of aggregate &1 should be partitioned |