RS_DB_DB6 - DB6-Specific Messages in SAP BW
The following messages are stored in message class RS_DB_DB6: DB6-Specific Messages in SAP BW.
It is part of development package RSDB6 in software component BW-SYS-DB-DB6. This development package consists of objects that can be grouped under "BW: Port DB6".
It is part of development package RSDB6 in software component BW-SYS-DB-DB6. This development package consists of objects that can be grouped under "BW: Port DB6".
Message Nr ▲ | Message Text |
---|---|
010 | You have selected &1 key fields for MDC, but the maximum allowed is &2 |
011 | You cannot select all key fields for MDC |
012 | InfoCube already contains data; clustering can no longer be changed |
013 | You have to select at least one key field (!= package dimension) for MDC |
014 | InfoCube contains data; clustering of active version is retained |
015 | Clustering not specified; index clustering is used |
016 | MDC is not supported in DB2 pureScale. |
017 | MDC is not supported for column-organized tables |
018 | Column-organized tables are not available in your environment |
019 | Reclustering is not supported for column-organized tables |
020 | DB2/LUW: Index &1 deleted as not required |
021 | DB2/LUW: Primary index &1 created |
022 | DB2 LUW: Default primary index &1 exists but should not exist |
023 | DB2 LUW: Default primary index &1 deleted |
024 | DB2 LUW: Default primary index &1 is missing |
025 | DB6CONV version too old to perform this operation |
026 | Serious error during processing of InfoProvider |
027 | &1&2&3 |
028 | Compression cannot be checked for column-organized tables |
029 | DB2 LUW: Statistics for table &1 calculated by DB2 is required |
030 | DB2/LUW: InfoProvider &1 does not use MDC |
031 | DB2/LUW: Internal error while reading information about InfoProvider &1 |
032 | DB2/LUW: Test not supported for write-optimized DataStore objects |
033 | DB2/LUW: &1 % of the memory reserved for InfoProvider &2 is free |
034 | &1 % of the memory reserved for table &2 is free |
035 | DB2/LUW: MDC memory consumption (estimated) |
036 | Number of records: &1 |
037 | Number of MDC cells: &1 |
038 | Number of different values in MDC dimension &1: &2 |
039 | Average number of records for each MDC cell: &1 |
040 | Number of allocated pages: &1 |
041 | Number of free pages: &1 |
042 | Allocated memory in KB: &1 |
043 | Free memory space in KB: &1 |
044 | Database statistics of &1 &2 |
045 | No database statistics for &1; refresh |
046 | Data row compression: compression rate &1 % |
049 | Table &1 is empty |
050 | InfoCube &1 |
051 | Aggregate &1 |
052 | DataStore object &1 |
053 | Data row compression for table &1 is switched on |
054 | Data row compression for table &1 is switched off |
055 | The data object of table &1 has the size &2 &3 |
056 | Offline reorganization job scheduled for InfoProvider &1 |
057 | Inspect job scheduled for InfoProvider &1 |
058 | After executing, check the log in SM37 or DB13 |
059 | For data row compression, you require DB2 9 |
060 | Internal error while reading information about PSA table &1 |
061 | Table &1 does not have a compression dictionary |
062 | Table &1 has a compression dictionary of size &2 &3 |
063 | Change log table for DataStore object &1 not found |
064 | Offline reorganization job scheduled for PSA table &1 |
065 | Inspect job scheduled for PSA table &1 |
066 | Reorganization/inspect is not necessary |
067 | Inspect job for PSA table &1 not scheduled |
068 | Reorganization/inspect job already scheduled |
069 | Reorganization/inspect job started and ended with errors |
070 | Reorganization/inspect job started and ended with warnings |
071 | Reorganization/inspect job completed successfully |
072 | Reorganization/inspect job scheduled but not started |
073 | Offline reorganization job for PSA table &1 not scheduled |
074 | Offline reorganization job for InfoProvider &1 not scheduled |
075 | Inspect job for PSA table &1 is not scheduled |
076 | Inspect job for InfoProvider &1 is not scheduled |
077 | Activation queue table of DataStore object &1 not found |
079 | Table &1 is column-organized |
082 | Function module or method call &1 failed with return code &2 |
083 | &1 ended with return code &2 |
200 | Adjust metadata for InfoProvider clustering to DB implementation |
201 | Processing InfoCubes and aggregates... |
202 | Processing of InfoCubes and aggregates finished |
203 | Processing DataStore objects... |
204 | Processing of DataStore objects finished |
205 | Error in InfoCube &1: Could not determine metadata |
206 | Error in InfoCube &1: Could not determine fact tables |
207 | InfoCube &1: Database: Index clustering |
208 | InfoCube &1: Metadata: MDC |
209 | InfoCube &1: Database: MDC |
210 | InfoCube &1: Metadata: Index clustering |
211 | InfoCube &1: Could not adjust metadata to database |
212 | InfoCube &1: Incorrect PARTTIM field: &2 |
213 | InfoCube &1: MDC dimensions &2 entered in metadata |
214 | InfoCube &1: Could not enter MDC metadata |
215 | DataStore object &1: InfoObject for column &2 not found |
216 | DataStore object &1: Metadata not found |
217 | DataStore object &1: Could not adjust metadata to database |
218 | DataStore object &1: No MDC |
219 | DataStore object &1: MDC dimensions &2 |
220 | No active InfoCubes found |
221 | Index &1 of table &2 is compressed |
222 | Index &1 of table &2 is not compromised |
223 | &1% storage space can be saved with index compression |
224 | &1% storage space can be saved with index compression |
301 | NLS connection &1 established |
302 | DB connection &1 closed |
303 | NLS connection &1 is not defined in table DBCON |
304 | SQL error &2 in NLS connection &1: &3 |
305 | Could not create NLS connection &1 (internal error) |
306 | Data structure for NLS object &1 is not consistent |
307 | Last NLS operation in the &1 database has time stamp &2 |
308 | NLS database must be rolled forward to time stamp &1 |
309 | SAP system &1 is not a unicode system |
310 | Error while creating tablespace &1 |
311 | Error while creating database partition group &1 |
318 | BW system/BW DB hostname does not match NLS connection parameters (&1) |
320 | Opened data package &1 to write data records to NLS object &2 |
321 | Wrote &1 data records in data package &2 for NLS object &3 |
322 | Closed data package &1 with data records for NLS object &2 |
323 | Error while adding data to NLS object &1 |
330 | Status &1 is invalid for request &2 |
331 | Error while accessing request table for NLS object &1 |
332 | Error while writing data package &1 |
333 | No connection to NLS database |
340 | NLS object structure &1 read |
341 | &1 data records read in a data package from NLS objekt &2 |
342 | No more data records to be read in NLS object &1 |
343 | Read cursor opened for NLS object &1 |
344 | Read cursor closed for NLS object &1 |
350 | No NLS object for InfoProvider &1 in database |
351 | Table &1 access error |
352 | InfoProvider name &1 is invalid |
353 | Error reading NLS object &1 |
354 | Error while accessing cursor for NLS object &1 |
355 | Error while opening the cursor for NLS object &1 |
356 | Error while closing the cursor for NLS object &1 |
360 | Table &1 created |
361 | Data structure for NLS object &1 saved |
362 | Table &1 deleted |
363 | Data structure for NLS object &1 deleted |
364 | Table &1 changed |
370 | Error while inserting table &1 in ABAP dictionary |
371 | Error while activating table &1 in ABAP dictionary |
372 | Error while saving the data structure for NLS object &1 |
373 | Error while deleting table &1 |
374 | Error while creating table &1 |
375 | Error while creating index &1 in table &2 |
376 | Error while inserting default values for table &1 |
377 | Error while changing table &1 |
378 | Error while deleting data structure for NLS object &1 |
379 | Error while deleting index &1 in table &2 |
380 | Error while deleting default values for table &1 |
381 | Dimension change from &1 to &2 for field &3 was ignored |
382 | Field &1 cannot be changed from &2 to &3 |
383 | &1: CDE tables cannot be changed |
390 | Request &1 does not exist |
391 | Request status cannot be changed |
392 | Error while accessing request table |
393 | Request &1 already exists |
394 | &1 data records in invalid request &2 deleted in table &3 |
395 | Index for dimension &1 cannot be created due to size limit |
396 | Index width is &1, and index size limit is &2 |
397 | Error during determination of pagesize of the database |
400 | HERE MESSAGES FOR ADDITIONALINDEX 020 ON SID TABLES |
401 | Table &1 could not be retrieved from ABAP Dictionary |
402 | Index &1 on table &2 already exists |
403 | Index &1 on table &2 could not be written to ABAP Dictionary |
404 | Index &1 on table &2 could not be activated |
405 | Index &1 on table &2 was created successfully |
406 | Index &1 on table &2 could not be created |
407 | Index &1 on table &2 could not be dropped |
408 | Index &1 on table &2 was dropped successfully |
409 | Job &1 to create additional SID table indexes is running |
410 | Job &1 to drop additional SID table indexes is running |
411 | Job &1 aborted. Determining status of indexes On SID tables... |
412 | Determining status of indexes on SID tables... |
413 | Please enter a start time |
414 | This program creates or drops additional indexes on SID tables |
415 | This program requires Db2 11.1 MP3 FP3 or higher and SAP Note 2688115 |
500 | HERE START THE MESSAGES FOR THE BW OBJECT CONSISTENCY CHECKER |
501 | Checking object &1... |
502 | Checking table organization... |
503 | PSA table is row-organized |
504 | InfoObject &1 is row-organized |
505 | Checking indexes... |
506 | Checking multidimensional clustering (MDC)... |
507 | Checking distribution key... |
508 | Checking compression settings... |
509 | Checking for warnings on PSAs... |
510 | Comparing metadata for DSO with table organization on database... |
511 | DSO has inconsistent table layout |
512 | BW object does not exist in the system, enter a valid name |
513 | Table &1 is column-organized |
514 | Table &1 is row-organized |
515 | Table &1 is column-organized |
516 | Table &1 is row-organized |
517 | Metadata for InfoCube &1 does not match table organization on database |
518 | Metadata for DataStore object &1 does not match table organization |
519 | PSA table &1: Non-unique index does not exist, but is defined in metadata |
520 | |
521 | PSA is column-organized, no MDC check |
522 | No MDC index defined for table &1 |
523 | Too many MDC indexes defined for table &1 |
524 | MDC index on column &1 exists for table &2; OK |
525 | MDC index on column &1 does not exist for table &2 |
526 | An MDC block index does not exist |
527 | Too many MDC block indexes exist |
528 | Metadata and MDC definition on database differ in fields or sequence |
529 | Fields on database: |
530 | Fields in metadata: |
531 | MDC definition for block index found on &1, matches metadata; OK |
532 | No MDC definition on package found for &1, matches metadata; OK |
533 | MDC definition on package found for &1, does not match metadata |
534 | MDC definition on package found for &1, matches metadata; OK |
535 | Table compression for &1 is not activated |
536 | Index compression for &1 is not activated |
537 | Recommended compression is activated for all tables and indexes |
538 | Distribution key for active DSO table &1 differs from metadata |
539 | Distribution key for active DSO table &1 matches metadata |
540 | Distribution key for DSO activation queue &1 differs from metadata |
541 | Distribution key for DSO activation queue &1 matches metadata |
542 | Distribution key for DSO change log &1 differs from metadata |
543 | Distribution key for DSO change log &1 matches metadata |
544 | Distribution key for E fact table &1 differs from metadata |
545 | Distribution key for E fact table &1 matches metadata |
546 | Distribution key for F fact table &1 differs from metadata |
547 | Distribution key for F fact table &1 matches metadata |
548 | DSO &1: Non-unique index &2 is defined as unique in metadata |
549 | Checking modification state indexes... |
550 | DSO &1: Non-unique index does not exist, but is defined in metadata |
551 | Modification state index exists on column-organized tables with index; OK |
552 | InfoCube &1 is set to index clustering in metadata |
553 | InfoCube &1 is set to MDC clustering in metadata |
554 | InfoCube &1 is column-organized, no MDC check |
555 | InfoCube &1: 010 index is limited to 64 characteristics |
556 | |
557 | InfoCube &1: 990 index is limited to 63 characteristics |
558 | |
559 | InfoCube &1: There are more than three MDC dimensions in metadata |
560 | Inconsistent metadata for InfoCube &1 |
561 | Index &1 for InfoObject table &2 in metadata does not exist on database |
562 | Checking index layout on database, using metadata as reference... |
563 | Checking index metadata, using index layout on database as reference... |
564 | An MDC definition exists on column &1 instead |
565 | Metadata and index layout for &1 differ regarding uniqueness definition |
566 | Metadata and index layout for &1 differ regarding primary key definition |
567 | Metadata and index layout for &1 differ regarding clustering definition |
568 | Metadata and index layout for index &1 on table &2 differ |
569 | There are differences regarding fields or sequence |
570 | &1 |
571 | Comparison done: &1 errors |
572 | Layout according to metadata: |
573 | Layout on database: |
574 | Table: &1 Index: &2 Unique: &3 Primary key: &4 |
575 | Tables H/J/K/I should be row-organized, which is not the case |
576 | Tables S/X/Y/P/Q/T have an inconsistent table layout |
577 | Distribution key for PSA table &1 differs from metadata |
578 | Index &1 for InfoCube table &2 in metadata does not exist on database |
579 | Distribution key for PSA table &1 matches metadata; OK |
580 | Fields of distribution key according to metadata: |
581 | Fields of distribution key on database: |
582 | Write-optimized DataStore object is row-organized |
583 | Standard DataStore object is row-organized |
584 | DataStore object for direct update is row-organized |
585 | Index &1 for PSA table &2 in metadata does not exist on database |
586 | Only static table compression for &1 is activated |
587 | Consider activating adaptive table compression for &1 |
588 | Comparing object layout &1 with &2 as defined in RSADMIN parameter... |
589 | Layout of object &1 does not match layout &2 from RSADMIN parameter |
590 | Index &1 for DSO table &2 in metadata does not exist on database |
591 | Index &1 for table &2 on database does not exist in metadata |
592 | Fields in metadata: |
593 | Fields on database: |
594 | Checking MDC definition for F fact table &1... |
595 | Checking MDC definition for E fact table &1... |
596 | Write-optimized DataStore object is column-organized; no MDC check |
597 | Checking database partition groups for InfoCube fact tables... |
598 | InfoCube &1: F and E fact tables in the same database partition group |
599 | InfoCube &1: F and E fact tables in different database partition groups |
600 | Flat InfoCube, no check for database partition groups |
601 | Aggregate &1: F and E fact tables in the same database partition group |
602 | Aggregate &1: F and E fact tables in different database partition groups |
603 | PSA table is column-organized |
604 | InfoObject &1 is column-organized |
605 | Write-optimized DataStore object is column-organized |
606 | Standard DataStore object is column-organized |
607 | Checking for warnings for DataStore objects... |
608 | Checking for warnings for InfoCubes... |
609 | Comparing metadata of InfoCube with table organization on database... |
610 | InfoCube has inconsistent table layout |
611 | InfoObject has inconsistent table layout |
612 | Metadata for InfoCube &1 is set to row-organized |
613 | Metadata for DataStore object &1 is set to row-organized |
614 | Metadata matches the row-organized layout on the database |
615 | Metadata for InfoCube &1 is set to column-organized |
616 | Metadata for DataStore Object &1 is set to column-organized |
617 | Metadata matches the column-organized layout on the database |
618 | There is a unique index &2 on table &1 |
619 | There is a unique index &2 on table &1 with a primary key |
620 | There is a non-unique index &2 on table &1 |
621 | Table &1 without modification state index, but secondary indexes enabled |
622 | Table &1 with modification state index, but secondary indexes not enabled |
623 | List of tables having a modification state index: |
624 | Table &1 has a modification state index |
625 | Modification state indexes do not exist for column-organized tables; OK |
627 | InfoObject is reference to &1; no check needed |
628 | InfoObject has no SID table; no check needed |