SDB2U - DB2/390: Messages for Functiongroup SDB2U
The following messages are stored in message class SDB2U: DB2/390: Messages for Functiongroup SDB2U.
It is part of development package SDB2 in software component BC-DB-DB2. This development package consists of objects that can be grouped under "DB2/390: DDIC".
It is part of development package SDB2 in software component BC-DB-DB2. This development package consists of objects that can be grouped under "DB2/390: DDIC".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Buffer pool &1 not valid |
| 002 | Nothing found |
| 003 | Problems with &1 |
| 004 | Stogroup &1 does not exist |
| 005 | Tablespace &1 does not exist or cannot be used |
| 006 | SEGSIZE should be 0,4,8,...,64 |
| 007 | Limit key specification wrong |
| 008 | Table has no indexes in the database |
| 009 | Index does not exist in the database |
| 010 | PIECESIZE must be a power of 2 between 256 and &. |
| 012 | DSSIZE should be 1,2,4,8,16,32,64 or 128,256(V10) or 1024(V12) GB. |
| 013 | Table & does not exist |
| 014 | Index & does not exist |
| 015 | LIMITKEY report & could not be generated |
| 016 | Starting report generation |
| 017 | Report generation: total = &, ok = &, failed = & |
| 018 | Generation error in &: & |
| 019 | GBPCACHE should be CHANGED, ALL, SYSTEM or NONE |
| 020 | 1 < Number of partitions <= & |
| 021 | SEGSIZE > 0 only with MEMBER CLUSTER = 'NO' |
| 022 | MEMBER CLUSTER = 'YES' only with SEGSIZE = 0 |
| 023 | AUDIT should be NONE, ALL or CHANGES |
| 024 | MAXPARTITIONS should be between 1 and 4096 |
| 025 | DSSIZE too large. Adjusted to maximum possible value. |
| 100 | Storage parameters successfully altered |
| 101 | Object does not exist in the database |
| 102 | ALTER statement failed |
| 103 | & executed successfully |
| 104 | STOP DATABASE & timed out (after 20 seconds) |
| 105 | START DATABASE & failed |
| 106 | DB2 command failed -> ALTER not executed |
| 107 | ALTER not possible; convert with SE14->'Extras'->'Force conversion'! |
| 108 | Upload impossible: Number of lines not sufficient - must be 3 or more! |
| 109 | Upload impossible: Partitioning key specified in first line is invalid! |
| 110 | Default handling of DEFER YES and REBUILD INDEX enforced for &. |
| 111 | REBUILD INDEX options adjusted for &. |
| 112 | Automatic DEFER YES and REBUILD INDEX switched on for &. |
| 113 | Automatic DEFER YES and REBUILD INDEX switched off for &. |
| 114 | For details on automatic DEFER YES and REBUILD INDEX refer to SAP note &. |
| 115 | Action requires authorization & with obj. category & and activity &. |
| 116 | For details on how to convert indexes refer to SAP note &. |
| 117 | Below SAP NW 7.00 max. primary quantity is limited to 500000 KB. |
| 118 | Max. value for primary and secondary quantities in DB2 is 4194304 KB. |