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