GT - Arbeitsgebiet DB-Utility
The following messages are stored in message class GT: Arbeitsgebiet DB-Utility.
It is part of development package SDIC in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary".
It is part of development package SDIC in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary".
Message Nr ▲ | Message Text |
---|---|
001 | Database utility for ABAP Dictionary objects |
002 | No regular object class passed on |
003 | Requests: |
004 | $ $ $ $ |
005 | SQL tables: |
006 | Tables: |
007 | Views: |
008 | Indexes: |
009 | Matchcodes: |
010 | Set up matchcode records: |
011 | Start: & , & |
012 | End: & , & |
013 | 'Generate program' supported for table conversion only |
014 | Number of objects: &, partition: & |
015 | Form & of external program & not found |
016 | Form & of external program & called ... |
017 | Exception handling defined for & in report & |
018 | No background request found for & |
019 | No background requests found for matchcode objects |
020 | No background requests found for lock objects |
021 | System error (enqueue processing not anticipated) |
022 | Locks: |
023 | Convers. prog. mode = & |
024 | Start background processing for object & (&) |
025 | There are no terminated conversions to be edited |
026 | Not all conversions were successfully completed |
027 | Processing was successfully completed |
029 | ****** Various error messages from the conversion program ******** |
030 | Table name belongs to a reserved name range |
031 | Nametab for table & could not be generated from N version |
032 | Action was canceled |
033 | Invalid date |
034 | No object for editing found |
035 | Request for & & already dealt with |
036 | Data transfer is executed through application-specific program |
037 | Dependent objects have errors -> please check (see log) |
038 | Table & does not exist in the database |
039 | Problem with remote call of & (&) |
040 | Link for remote call of & could not be closed (&) |
041 | Trigger & will be deleted in the DB |
042 | Method & is not supported in field conversion |
043 | Selected type of data transfer is not supported |
044 | Runtime object for temporary table & could not be generated |
045 | Metadata for columns to be converted could not be saved |
046 | Runtime object for &: not-null information not updated |
047 | Runtime object &: refresh failed |
048 | &: table parameters could not be read from the DB |
049 | &: Table parameters could not be written |
050 | ********* 050 to 099 reserved for Dictionary_DB_OPERATION ************** |
051 | Convert & & by unloading and reloading the data |
052 | Request: Create & |
053 | Request: Delete & |
054 | Request: Convert & |
055 | Request: Delete and recreate & |
056 | Request: Restart conversion of table & |
057 | Request NOP: & empty operation |
058 | Request ERR: & semantic error |
059 | Request BUG: & program termination |
060 | Request is executed by activating & & |
061 | & & was activated |
062 | A restart log already exists for table & |
063 | Execute generated statements for & & |
064 | Generated statements successfully executed for & & |
065 | Table & was converted |
066 | Request for & executed successfully |
067 | Request for & could not be executed |
068 | Object is already locked for a database operation |
069 | Request: Multiplex data save & |
070 | Activation and DDL statements for & & required |
071 | & & cannot be activated |
072 | Create & & |
073 | Delete & & |
074 | Statements for & & could not be executed |
075 | Conversion of table & failed |
076 | Data from table & is deleted |
077 | Activation & is returning errors |
078 | Data from table & could not be deleted |
079 | Activate & & |
080 | & & was created |
081 | & & already exists |
082 | & & could not be created |
083 | & & was deleted |
084 | & & does not exist in the database |
085 | & & could not be deleted |
086 | Delete runtime object of & & |
087 | Runtime object of & & was deleted |
088 | Could not delete runtime object of & & |
089 | Conversion of table & must be restarted |
090 | Conversion of table & cannot be restarted |
091 | Activation of & & failed |
092 | Conversion of table & was restarted |
093 | Conversion was restarted successfully |
094 | Conversion could not be restarted |
095 | Conversion of table & is restarted |
096 | Request is dealt with by executing DDL statements |
097 | Request dealt with by deleting nametab |
098 | Deletion and recreation of & & failed |
099 | Error creating secondary indexes |
100 | Delete & & |
101 | Table & already locked for VTRUM conversion |
102 | Type change from VARC to LRAM detected in field & |
103 | Request dealt with by executing DDL statements |
104 | 'Generate program' not necessary |
105 | Request dealt with by activation |
106 | Field & activated |
107 | Object &: Function & not provided |
108 | Request: Generate programs for converting table & |
109 | Table & was revised further during conversion |
110 | Restore the previous version of table & |
111 | Error initializing step table TCNV |
112 | Error when setting a step in table TCNV |
113 | & & already exists |
114 | Compare module DD_DECIDE ended with error(s) |
115 | Object & has old restart logs; edit them online |
116 | Test activation of & & was successful |
117 | Force mode only allowed for conversion request |
118 | Table conversion without compare run |
119 | Target table type was modified again by table & |
120 | Could not create all views again for & & |
121 | Compare module contains empty nametabs for & & |
122 | Nametab of table & with status & does not exist |
123 | Activate the inactive substructures in & first |
124 | Inactive name tab for & could not be activated |
125 | Inactive nametab for & activated successfully |
126 | Execute generated ABAP program for & & |
127 | Generated ABAP program for & & successfully executed |
128 | Execution of ABAP program failed |
129 | Unknown object type & for & passed |
130 | Unexpected operation & received with mode flag & |
131 | Invalid operation & for & (object type:&) |
132 | Activate table & (using DB utility) |
133 | Test activation of & & |
134 | Test activation of & & successful |
135 | Nametab of type & for & could not be determined |
136 | Table & is made transparent by "transparent" flag |
137 | Kernel object & is not processed by the conversion program |
138 | Nametab reconstruction table & |
139 | Original table & does not exist |
140 | Request: ICNV switch & |
141 | SCAN is not supported for field conversions |
142 | User-defined conversion: |
143 | & records converted successfully |
144 | & records were not converted |
145 | Table & is converted using shadow field updates |
150 | *** 150-199 reserved for DB_<X>_TO_<Y>_MOVE and for DB_TABLE_MOVE *** |
151 | Report instantiation for table & (& to &) |
152 | Report(s) not instantiated |
153 | Report & not written to database |
154 | Reports ({,}) ended with errors |
155 | Table & locked |
156 | Report & not generated (syntax error?) |
157 | Report execution for table & (& to &) |
158 | Converter class used: & |
180 | 180-200 reserved for DD background requests |
181 | Job & released |
200 | ** 200-249 reserved for '{' and '}' reports |
201 | Not all the views on table & could be deleted |
202 | Execution of }-conversion report for table & |
203 | Table & is locked, but without actions |
204 | Table & is not locked for a conversion |
205 | Inconsistency between {/} report and TCNV table |
206 | Table & already exists in the database (inconsistency) |
207 | Creation of table & or primary index in DB failed |
208 | Renaming of table &1 to &2 failed |
209 | The conversion step could not be logged |
210 | Data unloaded from & to QCM |
211 | Data from original table & deleted |
212 | Table & was activated |
213 | Table activation of & failed |
214 | Renaming of QCM as & in database failed |
215 | Table &: Data copied to client & |
216 | Client copy to table & failed |
217 | Conversion steps for table & incomplete |
218 | Data loaded from &1 to &2 |
219 | Table & does not exist in the database |
220 | Return code = & |
221 | Creation of secondary indexes for table & failed |
222 | Number of inserted tuples=&, INSERTs=&, array size=& |
223 | Request can only be executed in client '000' (currently &) |
224 | Error deleting QCM table & |
225 | Error deleting index & |
226 | Error deleting table & |
227 | & work area bytes expected for copying |
228 | SQL: & |
229 | Not all indexes could be deleted for table & |
230 | Performance figures: |
231 | & |
232 | Step & executed successfully |
233 | Rows/minute: &; table width (old/new): &/& |
234 | No data for deletion found in old table & |
235 | Number of eliminated duplicates = & |
236 | The SQL statement was not executed |
237 | The target table & already contains data |
238 | Transp. table & already exists (restart when unloading) |
239 | Error in step & |
240 | Begin step &: |
241 | The conversion is continued at step & |
242 | Step is empty |
243 | Table & is kept for testing purposes |
244 | Total time for table &: & |
245 | Table & could not be unlocked |
246 | Type of conversion: & -> & |
247 | .... & was already removed |
248 | & could not be removed |
249 | Step &: & |
250 | No storage parameter found for temporary table & |
251 | No conversion exits found for table & |
252 | Table & is involved in the incremental conversion of table & |
253 | Total time for table &: & |
254 | The data was NOT loaded from & to & |
255 | Tupel is not converted |
256 | Conversion error (move-corresp.), field: & |
257 | ABAP runtime error (append), field: & |
258 | Value in field & too big for new DEC field |
259 | Value in field & too small for new DEC field |
260 | Conversion error for move-corresponding |
261 | ABAP runtime error in append |
262 | Field & is scanned |
263 | Database object for table & is checked |
264 | Database object for table & is inconsistent |
265 | Database object for table & is consistent |
266 | Database object for table cluster & is checked |
267 | Database object for table cluster & is inconsistent |
268 | Database object for table cluster & is consistent |
269 | & |
270 | Table delivery class: & |
271 | Table copied to client & |
272 | Table copied only to client 000 |
273 | Table copied to all clients of the system |
274 | Table copied to all production clients in the system |
275 | LRAW field & cannot be scanned |
276 | Conversion error LRAW field & |
277 | Length LRAW contents & > maximum length & |
278 | RFC connection could not be closed |
279 | Projection view & for data transfer will be created |
280 | Request: Force conversion & |
281 | sql: |
282 | Projection view & was deleted |
283 | Renaming of index & to & failed |
284 | Primary index & for index-org. table does not exist |
285 | CREATE_TABLE_AS method with two temp. names not allowed |
286 | Object already renamed |
287 | Table & is involved in the incremental migration of the table & |
288 | Runtime object for & could not be written |
289 | Database object table & is not partitioned |
290 | Inconsistency will be cleaned up through conversion |
291 | &&&& |
292 | & & & & |
293 | Statement exceeds currently allowed maximum length by & (& characters) |
294 | Statement new fields for temporary table & not generated |
295 | New fields for temporary table & could not be created |
296 | Statements delete fields for temporary table & not generated |
297 | Could not rename new columns in table & |
298 | Indexes of original table & could not be read |
299 | Index &-& (&) could not be created |
300 | Input error |
301 | Start time is in the past |
302 | The key columns of table & could not be determined. |
303 | Scheduling of object & was deleted |
304 | Job & is currently processing the object |
305 | Scheduling & was deleted |
306 | Job & could not be deleted |
307 | No scheduling of background or mass processing exists |
308 | Table & exists in database but not in ABAP Dictionary |
309 | View & exists in the database but not in the ABAP Dictionary |
310 | Object & cannot be edited using the DB utility |
311 | There is already a pool/cluster with the name & |
312 | Global existence tests are not currently possible; try again later |
313 | Canceled request already exists for object & & (see SE14) |
314 | A request for object & & is already running (see database utility) |
315 | The request was deleted successfully |
316 | The request for & & could not be deleted |
317 | Adjustment of table & was terminated |
318 | This function is not available for matchcodes |
319 | Nothing was scheduled |
320 | Do not edit the object with standard tools |
321 | Deleted |
322 | Nothing was selected for deletion |
323 | The current object was modified during processing |
324 | DDL lock set by tp (D0GEN) |
325 | DDPROF entry IGNORE found for DDL lock |
326 | Operation performed despite DDL lock |
327 | Operation terminated due to DDL lock |
328 | Table & does not exist in the database |
329 | Index & on table & does not exist in the database |
330 | Parameters were saved |
331 | Parameters were not changed |
332 | The changed parameters were used in the database |
333 | Only select empty tables/index nodes or your higher nodes |
334 | Enter an object name |
335 | Object does not exist |
336 | The parameters were not saved |
337 | Request & & & & could not be stored |
338 | Request & & & & is being created |
339 | All requests were successfully executed |
340 | Single logs in SE14 initial screen (Extras -> Logs) |
341 | Request & & & & not successfully executed |
342 | No action on & |
343 | No need to change the objects in the transport |
344 | No template selected - no parameters generated |
345 | Syntax error in generated program |
346 | Fields table & could not be read |
347 | Temporary DB fields table & already added |
348 | Active runtime object for & could not be saved |
349 | Runtime object & could not be read |
350 | Conversion information on columns is missing |
351 | Additional DDL statements for & could not be generated |
352 | Additional DDL statements for & could not be executed |
353 | Index &-& (&) could not be deleted |
354 | Could not generate ALTER statements for table & |
355 | Could not execute ALTER statements for table & |
356 | Deleting temporary runtime objects: & & |
357 | Runtime object for & could not be generated from the database |
358 | Renaming to original field & has already been done |
359 | Partitioning could not be adapted with regard to field deletions |
360 | Partitioning could not be changed |
361 | Deleting temporary runtime object & |
362 | Columns of primary key extended; it therefore has to be deleted |
363 | Configuration table & could not be adjusted |
364 | Partitioning information is missing for table & |
365 | ABAP-OO conversion exit is not complete |
366 | Combination of ABAP-OO CNV exit with a form-based exit is not permitted |
367 | Implementing class & is not available. |
368 | Change of client dependency is not supported with ABAP-OO exit |
369 | ABAP-OO CNV exit requires modeinfo=I in transport mode |
370 | Setting the new columns in table & to NOT NULL |
371 | New columns in table & were set to NOT NULL |
372 | Deleting the old columns from table & |
373 | The old columns were deleted from table & |
374 | Renaming the new columns in table & with the original names |
375 | The new columns in the table & were renamed with the original names |
376 | Table name is empty and needs to be defined |
377 | Accessed field & does not exist in table & |
378 | Accessed table & does not exist or is not active |
379 | Table & does not exist or is not active |
380 | ABAP-OO CNV exit initialized with class &1 |
381 | Could not read indexes for table & from the database |
382 | Table &1 has &2 partitions |
383 | Partition with ID &1 updated (&2 rows) |
384 | Error in verification of column names |
399 | Editing only possible in YI3 |
400 | ----------- Messages for Database Utility (SE14) 400 - 800----------- |
401 | No index was selected |
402 | Update timestamp error can be ignored |
403 | Only limited use of database utility possible in shadow system |
415 | Batch request & & is already available |
416 | Batch request & & was added |
500 | Start free space check before converting table & |
501 | Free space check not possible |
502 | Free space check before conversion successfully executed |
503 | Free space check for table and index & |
504 | & pages needed in DBSpace & |
505 | & pages free in DBSpace & |
506 | Free space check for table & |
507 | Free space check for table fragment & & |
508 | Free space check for index & |
509 | Target table is fragmented with strategy other than Round Robin |
510 | Primary index of target table is fragmented |
511 | Table is fragmented with strategy other than Round Robin |
512 | Secondary index is fragmented |
513 | Primary index is fragmented |
514 | Error occurred in free space check |
515 | Error: Free space for table is not sufficient |
516 | Error: Free space for index is not sufficient |
517 | Error: Free space for table and index is not sufficient |
518 | Target table is index-organized |
519 | Error when determining storage parameters for the target table |
520 | Table is index-organized |
521 | DDSTORAGE entry for initial extent is used for check |
522 | & blocks needed in tablespace & |
523 | & blocks free in tablespace & |
524 | & contiguous blocks needed in tablespace & |
525 | & contiguous blocks free in tablespace & |
526 | Primary index is partitioned |
527 | Table is partitioned |
528 | Table loses key fields or key fields are shortened |
529 | Target table is index-organized |
530 | Primary index does not exist in database |
531 | Table/target table has long string field |
532 | LMTS/automatic space management active; free space check is not necessary |
550 | Scan only possible if termination in step & |
551 | Scan only possible if termination in steps 2 or 5 |
552 | Scan only possible if conversion terminates |
553 | Scan of table & is restarted |
554 | Scan is restarted at step & |
555 | Scan was completed successfully |
556 | Error occurred during scan |
557 | Request: Scan & |
558 | Conversion not possible for cluster tables from EDI table clusters |
570 | Error writing to DDPROF |
571 | Distribution to all clients activated |
572 | Distribution activated to production clients only |
600 | ***** 600-700 Different Tools - Example: Reset Method in Converter ****** |
601 | Canceled conversion not recorded: reset not necessary |
602 | & version of table & does not exist |
604 | Update after step &; reset information no longer exists |
605 | Dictionary sources table & (revised version) successfully deleted |
607 | Error in &: Check of runtime object & against DB version is not possible |
608 | Differences between table (& version) and database object |
609 | Error while activating table version to which reset is to be performed |
610 | Error while renaming from & to & on the database |
611 | Table & could not be deleted on the database |
612 | Runtime object of temporary table & could not be deleted |
613 | Problems while deleting and recreating dependent views |
614 | Resetting of table & from step & of canceled conversion |
615 | Table & (& version) does not match DB version of & |
616 | Dependent views successfully adapted |
617 | Deletion of revised version of table & in Dictionary |
618 | Check of table (& version) against database |
619 | Renaming of table & to & on the database |
620 | Primary index already exists with the name & on the database |
621 | Primary index could not be created |
622 | Activation of table & for adapting indexes |
623 | Adapting dependent views |
624 | Dependent views could not be adapted successfully |
625 | Resetting of table & after canceled conversion |
626 | Resetting of table & performed successfully |
627 | Error while reading primary key |
628 | DDTYPES entry could not be created |
629 | Table & exists on the database |
630 | Table & and temporary table & exist on the database |
631 | Check of existence of table & on the database |
632 | &: Incorrect parameter (&=&) during call |
633 | Dictionary sources for table & could not be read |
634 | The active and inactive versions in DDIC do not match database table & |
635 | Table & and none of its temporary tables exist on the DB |
636 | Determination of necessary steps for resetting table |
637 | Latest version of table: & |
639 | Primary index was successfully created on the database |
640 | New or revised version does not exist |
641 | Recreate dependent views |
642 | Delete dependent views |
643 | Dependent views deleted |
644 | Dependent views recreated successfully |
645 | Runtime object for table & was written to the database |
646 | Deleting data from the original table & |
647 | Checking existence of DB triggers on table & |
648 | Could not delete DB trigger & |
649 | Creating temporary table & on the database |
650 | Table & was created on the database |
651 | Deleting memory parameters of table & |
652 | Table & was deleted on the database |
653 | Table & was renamed as & on the database |
654 | Table & has type (&, &); no updates possible |
655 | Field & contains the invalid value & |
656 | Runtime object of table & modified |
657 | Runtime object & copied to & |
663 | Runtime object copy for &1 written to &2 |
664 | Partitioned columns could not be determined |
665 | No information for DB property & could be determined |
666 | Error in active runtime object for & |
667 | Error in inactive runtime object for & |
668 | Error when updating sharing metadata (MTSHTABS_VERS) |
669 | Conversion for sharing change from & to & not supported |
670 | Could not save the active runtime object |
800 | Table & is locked; clean up using the DB utility first |
801 | Table &: Entry of request & (& -> transparent) failed |
802 | Table &: Conversion & -> transparent failed |
803 | Table &: Conversion � -> transparent successful |
804 | Job execution: Conversion & -> transparent failed |
805 | Job & already scheduled |
806 | Error scheduling the job for conversion & -> transparent |
807 | Job & (job no.&) for conversion & -> transparent scheduled |
810 | ---------- Function Group SDB2* 810 - 999 |
811 | Statements are not executed on &, as generated for & |
812 | No statements were generated |
813 | Syntax error in line & of the generated program |
814 | Overflow when calculating a temporary name for table & |
815 | Table &: Runtime object is missing and is reconstructed |
816 | Table &: Runtime object missing |
817 | Table & cannot be copied (incorrect type) |
818 | Commit after at least every & bytes |
819 | Array size used ....................: & |
820 | Number of inserts ..................: & |
821 | Number of inserted tuples ..........: & |
822 | Number of non-inserted duplicates .: & |
823 | Number of executed commits .........: & |
824 | Speed in tuple/min..................: & |
825 | Internal size of a tupel/byte.......: & |
826 | Copied dataset/bytes................: & |
827 | Number of deleted tuples ...........: & |
828 | Maximum number of subroutine pools reached |
829 | Speed in bytes/sec..................: & |
830 | Conversion method : & (&) |
831 | Mapping function: & (&) |
832 | Number of scanned tupels ...........: & |
833 | Scanned amount of data / bytes .....: & |
834 | The statements are executed UNRECOVERABLY |
835 | Deleting cluster table & by TRUNCATE of cluster table & |
836 | Number of tuples to be converted....: & |
837 | Table analysis .....................: & |
838 | Duplicates occurred when inserting in the target table |
839 | The original table is preserved with the name & |
840 | Number of conversion errors (tupel) ; & |
841 | Mapping function: & |
842 | Unknown database function & |
843 | Copying data from & to & |
844 | ... & data sets were copied |
845 | Deleting temporary table & |
846 | Number of processed cluster records...: & |
847 | Error occurred with 'TRUNCATE' of table cluster &. |
848 | Table & is unknown |
849 | Table & does not have a primary index |
850 | Beginning of Step & ( & ) |
851 | Step & successfully executed ( & ) |
852 | Table &: not all dependent views have been handled successfully |
853 | Conversion canceled deliberately for & (DDPROF) |
854 | Could not perform consistency check for table &1 |
900 | Temporary table for & not in database |
901 | This is a COMMIT; press ENTER |
902 | Enter table name |
903 | Enter R,T,D,S as processing type |
904 | Enter correction name |
905 | Enter R or S as a processing type |
906 | Enter a processing type |
907 | No restart log exists for this table |
908 | Check whether function was performed correctly |
909 | Lock entry deleted |
911 | Entry was saved |
912 | Error occurred when saving |
915 | Temporary table for & has been deleted |
916 | Lock entry for & does not exist |
917 | Function & not allowed |
918 | Command & not allowed |
919 | Log & was deleted |
920 | Logs older than & were deleted |
921 | Log older than & not found |
922 | Invalid QCM table name: |