SAP ABAP Message Class SDB2U (DB2/390: Messages for Function Group SDB2U)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DB-DB2 (Application Component) DB2 for z/OS
⤷
SDB2 (Package) DB2/390: DDIC
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
SDB2 (Package) DB2/390: DDIC 
Attributes
| Message class |  |
SDB2U |
| Short Description |  |
DB2/390: Messages for Function Group SDB2U |
| Changed On |  |
20130531 |
| Last Changed At |  |
120006 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1 &2 &3 &4 | Space: object requires documentation | |
| 2 | 001 |
Buffer pool &1 not valid | Space: object requires documentation | |
| 3 | 002 |
Nothing found | Space: object requires documentation | |
| 4 | 003 |
Problems with &1 | Space: object requires documentation | |
| 5 | 004 |
Stogroup &1 does not exist | Space: object requires documentation | |
| 6 | 005 |
Tablespace &1 does not exist or cannot be used | Space: object requires documentation | |
| 7 | 006 |
SEGSIZE should be 0,4,8,...,64 | Space: object requires documentation | |
| 8 | 007 |
Limit key specification wrong | Space: object requires documentation | |
| 9 | 008 |
Table has no indexes in the database | Space: object requires documentation | |
| 10 | 009 |
Index does not exist in the database | Space: object requires documentation | |
| 11 | 010 |
PIECESIZE must be a power of 2 between 256 and &. | The short text describes the object sufficiently | |
| 12 | 012 |
DSSIZE should be 1,2,4,8,16,32 or 64. As of DB2 V10 also 128 or 256 GB. | Space: object requires documentation | |
| 13 | 013 |
Table & does not exist | Space: object requires documentation | |
| 14 | 014 |
Index & does not exist | Space: object requires documentation | |
| 15 | 015 |
LIMITKEY report & could not be generated | Space: object requires documentation | |
| 16 | 016 |
Starting report generation | Space: object requires documentation | |
| 17 | 017 |
Report generation: total = &, ok = &, failed = & | Space: object requires documentation | |
| 18 | 018 |
Generation error in &: & | Space: object requires documentation | |
| 19 | 019 |
GBPCACHE should be CHANGED, ALL, SYSTEM or NONE | Space: object requires documentation | |
| 20 | 020 |
1 < Number of partitions <= & | Space: object requires documentation | |
| 21 | 021 |
SEGSIZE > 0 only with MEMBER CLUSTER = 'NO' | Space: object requires documentation | |
| 22 | 022 |
MEMBER CLUSTER = 'YES' only with SEGSIZE = 0 | Space: object requires documentation | |
| 23 | 023 |
AUDIT should be NONE, ALL or CHANGES | The short text describes the object sufficiently | |
| 24 | 024 |
MAXPARTITIONS should be between 1 and 4096 | The short text describes the object sufficiently | |
| 25 | 025 |
DSSIZE 128GB and higher only with DB2 V10 and higher. Adjusted to 64GB. | The short text describes the object sufficiently | |
| 26 | 100 |
Storage parameters successfully altered | The short text describes the object sufficiently | |
| 27 | 101 |
Object does not exist in the database | The short text describes the object sufficiently | |
| 28 | 102 |
ALTER statement failed | The short text describes the object sufficiently | |
| 29 | 103 |
& executed successfully | The short text describes the object sufficiently | |
| 30 | 104 |
STOP DATABASE & timed out (after 20 seconds) | The short text describes the object sufficiently | |
| 31 | 105 |
START DATABASE & failed | The short text describes the object sufficiently | |
| 32 | 106 |
DB2 command failed -> ALTER not executed | The short text describes the object sufficiently | |
| 33 | 107 |
ALTER not possible; convert with SE14->'Extras'->'Force conversion'! | The short text describes the object sufficiently | |
| 34 | 108 |
Upload impossible: Number of lines not sufficient - must be 3 or more! | The short text describes the object sufficiently | |
| 35 | 109 |
Upload impossible: Partitioning key specified in first line is invalid! | The short text describes the object sufficiently | |
| 36 | 110 |
Default handling of DEFER YES and REBUILD INDEX enforced for &. | The short text describes the object sufficiently | |
| 37 | 111 |
REBUILD INDEX options adjusted for &. | The short text describes the object sufficiently | |
| 38 | 112 |
Automatic DEFER YES and REBUILD INDEX switched on for &. | The short text describes the object sufficiently | |
| 39 | 113 |
Automatic DEFER YES and REBUILD INDEX switched off for &. | The short text describes the object sufficiently | |
| 40 | 114 |
For details on automatic DEFER YES and REBUILD INDEX refer to SAP note &. | The short text describes the object sufficiently | |
| 41 | 115 |
Action requires authorization & with obj. category & and activity &. | The short text describes the object sufficiently | |
| 42 | 116 |
For details on how to convert indexes refer to SAP note &. | The short text describes the object sufficiently | |
| 43 | 117 |
Below SAP NW 7.00 max. primary quantity is limited to 500000 KB. | The short text describes the object sufficiently | |
| 44 | 118 |
Max. value for primary and secondary quantities in DB2 is 4194304 KB. | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in |
