RS_DB_DB2 - Messages for DB2-z/OS Implementation
The following messages are stored in message class RS_DB_DB2: Messages for DB2-z/OS Implementation.
It is part of development package RSDB2 in software component BW-SYS-DB-DB2. This development package consists of objects that can be grouped under "BW: Porting DB2-z/OS".
It is part of development package RSDB2 in software component BW-SYS-DB-DB2. This development package consists of objects that can be grouped under "BW: Porting DB2-z/OS".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | SQL error &1 has occurred |
| 002 | SQL error &1 when calling stored procedure &2 |
| 003 | Message &1&2 cannot be written to application log |
| 004 | &1 &2 &3 &4 |
| 005 | Folder &1 already exists; moved to new parent &2 |
| 006 | Folder &1 already exists - nothing done |
| 007 | Folder &1 added |
| 008 | Start loading tables for &1 into accelerator &2 |
| 009 | Started loading table &1 to accelerator &2 (&3 records, &4 KB) |
| 010 | &1 does not need to be uploaded. Data is up-to-date in accelerator &2. |
| 011 | Folder &1 is not empty and therefore cannot be dropped |
| 012 | Folder &1 dropped |
| 013 | Not able to drop folder &1 |
| 014 | Object does not exist: &1, &2 |
| 015 | Cannot create object: &1 (type &2) in accelerator &3 |
| 016 | Object &1 already exists in accelerator &2, parent folder: &3 |
| 017 | Add new object &1 to parent folder &2 |
| 018 | Folder &1 does not exist |
| 019 | No folder added or moved |
| 020 | The selected parent is invalid. Cannot add folder &1. |
| 021 | Object &1 dropped |
| 022 | Object &1 cannot be dropped |
| 023 | SQL error &1 has occurred |
| 024 | &1: Procedure &2 terminated with error &3 (&4 seconds) |
| 025 | &1: Procedure &2 ended with warning &3 (&4 seconds) |
| 026 | &1: Procedure &2 completed with message &3 (&4 seconds) |
| 027 | DB2 Accelerator not identified |
| 028 | Cannot instantiate XML scheme &1 |
| 029 | SQL issued in line &1 of method &2 |
| 030 | DB2 Accelerator name is ambiguous |
| 031 | DB2 Accelerator &1 found |
| 032 | DB2 Accelerator not found |
| 033 | Executing DB2 command &1 &2 |
| 034 | Error &1 when executing DB2 command &2 |
| 035 | Could not set parameter &1 to value &2 |
| 036 | Job &1 released |
| 037 | Job &1 scheduled |
| 038 | Job started for object &1 type &2 and parallel degree &3 |
| 039 | Invalid value &1 specified for parameter &2 |
| 040 | Diagnostics action &1 executed successfully |
| 041 | Diagnostics action &1 could not be executed |
| 042 | No item selected |
| 043 | Update has ended with message type &1 (see application log) |
| 044 | Update has completed successfully |
| 045 | Object &1 type &2 does not exist in DB2 Accelerator |
| 046 | InfoObject &1 not found |
| 047 | InfoObject &1 is not active -> modified version taken |
| 048 | Function is supported for DB2 for z/OS only |
| 049 | Select a table first |
| 050 | Select a physical accelerator first |
| 051 | DB2 profile table DSN_PROFILE_TABLE does not exist |
| 052 | Job &1 could not be scheduled: reason code &2 |
| 053 | Accelerator &1: &2 entries before, &3 entries after reorganization |
| 054 | &1 records deleted from table &2 |
| 055 | Reorganization of configuration control tables completed in &1 seconds |
| 056 | Subobjects cannot be dropped |
| 057 | Search pattern "&1" not found |
| 058 | Load scheduled for object &1 type &2 to accelerator &3 |
| 059 | Error &1 when uploading file: &2 |
| 060 | &2 bytes exported to file on front end: &1 |
| 061 | Level of node &1 is too high |
| 062 | Import of file &1 finished with errors |
| 063 | Node &1 has wrong level pattern &2. No import possible. |
| 064 | File format for import is not recognized: &1 |
| 065 | Subrc &1 at INSERT into rsdb2a_control (&2 / &3) -> item is not inserted |
| 066 | Item &1 is ignored. The object of type &2 does not exist. |
| 067 | Item &1 is ignored. The object of type &2 already exists in this folder. |
| 068 | Item &1 is ignored, because object type &2 is not defined |
| 069 | File &1 imported successfully |
| 070 | Old node &1 of type &2 could not be dropped: return code &3 |
| 071 | Search pattern "&1", occurrence &2 of &3 |
| 072 | Cannot create database connection to location &1 |
| 073 | Connection &1 to location &2 already exists |
| 074 | Repair done: &1 tables added, &2 tables removed and re-added |
| 075 | System objects cannot be dropped |
| 076 | Control table entry &1 is invalid. Please choose "Reorg Configuration". |
| 077 | Select a DB2 Accelerator other than &1 |
| 078 | File cannot be extended |
| 079 | Trace file could not be downloaded. Reason code &1 |
| 080 | Accelerator &1: replication set in control structure for &2 tables |
| 081 | Repair replication: &1 updates have been performed |
| 101 | Table &1 already in accelerator &2 - nothing done |
| 102 | Table &1 will be added to accelerator &2 |
| 103 | RUNSTATS successfully run on table &1 |
| 104 | Table &1 is used by other object - not removed |
| 105 | Table &1 will be removed from accelerator &2 |
| 106 | Unknown object type &1 |
| 107 | START DATABASE(&1) SPACENAM(&2) failed |
| 108 | RUNSTATS on table &1 failed |
| 109 | Cannot start new task, return code &1 |
| 110 | Error &1 has occurred |
| 111 | Error &1 occurred at line &2 of &3 |
| 112 | Access to table &1 failed |
| 113 | Function module &1 failed with return code &2 |
| 114 | Real Time Statistics not available for table &1 |
| 115 | Reference Real Time Statistics not saved for table &1 |
| 116 | Authorization check failed |
| 117 | Method &1 terminated with error |
| 118 | Real Time Statistics repaired for table &1 |
| 119 | Table &1 not removed: not in accelerator &2 or contains archived data |
| 120 | Deployment set to "&1". No action perfomed. |
| 121 | Table &1 loaded to accelerator &2 |
| 122 | Unable to load table &1 to accelerator &2 |
| 123 | Incremental update of table &1 on accelerator &2 not allowed |
| 124 | Could not update rollup status to &2 for InfoCube &1 |
| 125 | Object &1 of type &2 does not exist in DB2 accelerator |
| 126 | Table &1 has an obsolete layout and is being refreshed in accelerator &2 |
| 127 | Table &1 is being loaded by concurrent process. No action performed. |
| 128 | Table &1 has invalid status &2 for accelerator &3 |
| 129 | Deployment set to "&1" for object &2 of type &3. Nothing done. |
| 130 | Cannot determine load status of table &1 |
| 131 | Parallel degree reduced from &1 to &2 due to resource limitation |
| 132 | Tables loaded by &1 parallel tasks |
| 133 | &1 tables / partitions have been loaded to accelerator &2 successfully |
| 134 | &1 tables / partitions not loaded to accelerator &2 due to errors |
| 135 | &1 tables / partitions skipped loading to accelerator &2 |
| 136 | Table &1 already loaded according to status -> nothing done |
| 137 | Table &1: Wait for replication skipped |
| 138 | Table &1: Waiting up to &2 seconds for replication to DB2 Accelerator &3 |
| 139 | Table &1 does not exist |
| 140 | Utility &1 (id &2) has ended with return code &3 |
| 141 | Table &1 has been added to DB2 accelerator &2 by concurrent process |
| 142 | Replication confirmed after &1 seconds |
| 143 | Replication could not be confirmed for &1 seconds |
| 144 | Waiting up to &1 seconds for replication to accelerator &2 |
| 145 | Table &1 could not be loaded in time to accelerator &2 |
| 146 | Table &1 is being enabled for acceleration in accelerator &2 |
| 147 | Cannot instantiate object &1 type &2 accelerator &3 |
| 148 | Step load time: &1, elapsed time: &2, caller: &3 |
| 149 | &1 background jobs scheduled |
| 150 | &1 ended with return code &2 |
| 151 | Load of table &1 to accelerator &2 terminated with unexpected error |
| 152 | Update of object &1 terminated with error message "&2" |
| 153 | Could not perform operation &1 on object &2 |
| 154 | Table &1 not loaded to accelerator &2 due to status "FORCE FAILING" |
| 155 | Table &1 added to &2 by concurrent process after check. Remove canceled. |
| 156 | Table &1 exists in accelerator &2; DB2 catalog out of sync for &3 seconds |
| 157 | InfoProvider &1: Attribute &2 in table &3 has been set to value &4 |
| 158 | Data status has been reset for table &1, partition &2, accelerator &3 |
| 159 | Table &1, partition &2, accelerator &3: Status update after &4 seconds |
| 160 | &1 tables/partitions waited for concurrent load to accelerator &2 |
| 161 | XML parsing error: "&1", length: &2 |
| 200 | &1 |
| 201 | Near-line storage &1 connected |
| 202 | SQL error &1 has occurred |
| 203 | Database error &1 |
| 204 | Changing request to &1 not allowed in status &2 |
| 205 | Loading table &1 partition key &2 to the DB2 Accelerator |
| 206 | Table &1 partition &2 loaded in &3 seconds |
| 207 | Procedure &1 terminated with error &2 |
| 208 | Table &1 dropped |
| 209 | Table &1 removed from DB2 Accelerator |
| 210 | Table &1 cannot be dropped |
| 211 | Table &1 added to DB2 Accelerator |
| 212 | DB2 Accelerator deactivated, &1 not executed |
| 213 | DB2 Accelerator deactivated, request &1 not replicated |
| 214 | Table &1 activated |
| 215 | Activation of table &1 failed |
| 216 | Table &1 has &2 partitions, creating new version |
| 217 | Table &1 partition &2 added |
| 218 | Table &1 partition &2 is full |
| 219 | Database connection &1 not defined in table DBCON |
| 220 | SQL issued in line &1 of method &2 |
| 221 | Table &1 created on connection &2 |
| 222 | Procedure &1 ended with warning &2 |
| 223 | Procedure &1 successfully finished with message &2 |
| 224 | Table &1 dropped on connection &2 |
| 225 | Table &1 cannot be dropped on connection &2 |
| 226 | Table &1 contains data and thus cannot be dropped |
| 227 | Table &1 on connection &2 contains data and thus cannot be dropped |
| 228 | Creating table version &1 of nearline object &2 |
| 229 | DB2 Accelerator deactivated, request &1 not archived |
| 230 | Multiple DB2 Accelerators found, set &1 in table RSADMIN |
| 231 | Table &1 owned by system &2, but system is &3 - write access denied |
| 232 | Table &1 owned by system &2, not deleted |
| 233 | Archiving deactivated. Request &1 not transferred to the accelerator. |
| 234 | Authorization check failed |
| 235 | Archiving table &1 partition key &2 to the DB2 Accelerator |
| 236 | Table &1 partition &2 archived in &3 seconds |
| 237 | Enqueue on table &1 not available for &2 seconds |
| 238 | Table &1 partition key &2 archived by concurrent process. Nothing done. |
| 239 | Compounding &1 requests: table &2 partitions &3 |
| 240 | Deleting data from table &1 partition key &2 in DB2 Accelerator |
| 241 | Error when setting &1 in table &2 |
| 242 | Physical partition for partition key &1 not found |
| 243 | DB2 Utility &1 (ID &2) failed |
| 244 | ROTATE: Partition key &1 becomes partition key &2 |
| 245 | Creator of NLS database &1 (&2) is not equal to current schema (&3) |
| 246 | Table &1 partition key &2 not found |
| 247 | &1 repair task(s) executed |
| 248 | Could not execute &1 repair task(s) |
| 249 | The following tasks are required to repair archives |
| 250 | (&1) Accelerator &2: Adding table &3 |
| 251 | (&1) Accelerator &2: Archiving table &3 partition &4 |
| 252 | (&1) Accelerator &2: Deleting archive table &3 partition &4 |
| 253 | (&1) Setting PRO mode for table &2 partition &3 |
| 254 | (&1) Removing PRO mode for table &2 partition &3 |
| 255 | (&1) Truncating table &2 partition &3 |
| 257 | Repair not required. No action performed. |
| 258 | Executing repair tasks... |
| 259 | Request &1 (InfoProvider &2) is in status "&3" |
| 260 | &1 requests checked |
| 261 | &1 requests in status "&2" |
| 262 | Overall status is "&1" (for details, run report &2) |
| 263 | Table &1 partition &2 does not hold an archiving request - not deleted |
| 264 | Table &1 partition &2 partitionkey &3 not found |
| 265 | Job &1 is already scheduled |
| 266 | Parameter &1: &2 |
| 267 | Performing task "&1" |
| 268 | Invalid parameter: &1 |
| 269 | Table &1 partition &2 owned by system &3. Request must not be deleted. |
| 270 | Request &1 owned by system &2, but system is &3. Operation '&4' rejected. |
| 271 | Data archiving process owned by system &1. Extension created, version &2. |
| 272 | Archive extension owned by system &1 found, but system is &2 |
| 273 | Near-line object &1 version &2: Layout of table &3 is current. |
| 274 | Table &1 does not exist in accelerator &2 |
| 275 | Cannot create connection &1 |
| 276 | Length of table &1 (&2) exceeds data dictionary limit (&3) |