Message Number list used by SAP ABAP Class CX_ESH_TREX_PROXY (General ESH TREX Exception)
SAP ABAP Class CX_ESH_TREX_PROXY (General ESH TREX Exception) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | ESH_HANA_ADMIN - 001 | HANA destination is not available | |
2 | Message Number | ESH_HANA_ADMIN - 002 | HANA server with destination &1 is not available | |
3 | Message Number | ESH_HANA_ADMIN - 003 | Destination type has not been set | |
4 | Message Number | ESH_HANA_ADMIN - 004 | Destination type &1 not supported | |
5 | Message Number | ESH_HANA_ADMIN - 005 | Could not determine HANA version for connection &1 | |
6 | Message Number | ESH_HANA_ADMIN - 006 | HANA Sanity Check: Wrongly instantiated | |
7 | Message Number | ESH_HANA_ADMIN - 007 | HANA call terminated with a technical error | |
8 | Message Number | ESH_HANA_ADMIN - 007 | HANA call terminated with a technical error | |
9 | Message Number | ESH_HANA_ADMIN - 008 | HANA call terminated with HANA engine error. Error code: &1 | |
10 | Message Number | ESH_HANA_ADMIN - 008 | HANA call terminated with HANA engine error. Error code: &1 | |
11 | Message Number | ESH_HANA_ADMIN - 009 | Error message: &1&2&3&4 | |
12 | Message Number | ESH_HANA_ADMIN - 009 | Error message: &1&2&3&4 | |
13 | Message Number | ESH_HANA_ADMIN - 010 | No further error messages from HANA server | |
14 | Message Number | ESH_HANA_ADMIN - 010 | No further error messages from HANA server | |
15 | Message Number | ESH_HANA_ADMIN - 011 | TREX API "&1" not supported with a HANA destination | |
16 | Message Number | ESH_HANA_ADMIN - 012 | Database table &1 could not be created | |
17 | Message Number | ESH_HANA_ADMIN - 013 | Database view &1 could not be created | |
18 | Message Number | ESH_HANA_ADMIN - 014 | Database table &1 could not be copied | |
19 | Message Number | ESH_HANA_ADMIN - 015 | Attributes could not be defined for table/view &1 | |
20 | Message Number | ESH_HANA_ADMIN - 016 | Database table/view &1 could not be deleted | |
21 | Message Number | ESH_HANA_ADMIN - 017 | Could not retrieve attribute definitions for table/view &1 | |
22 | Message Number | ESH_HANA_ADMIN - 018 | Could not delete attributes from table/view &1 | |
23 | Message Number | ESH_HANA_ADMIN - 019 | Could not get list of tables from HANA database | |
24 | Message Number | ESH_HANA_ADMIN - 020 | Table &1 could not be cleared | |
25 | Message Number | ESH_HANA_ADMIN - 021 | Could not check existence of table(s) on HANA | |
26 | Message Number | ESH_HANA_ADMIN - 022 | Could not rename database table &1 | |
27 | Message Number | ESH_HANA_ADMIN - 023 | Changes could not be committed | |
28 | Message Number | ESH_HANA_ADMIN - 024 | Model information for database table/view &1 could not be accessed | |
29 | Message Number | ESH_HANA_ADMIN - 025 | Attributes could not be redefined for database table &1 | |
30 | Message Number | ESH_HANA_ADMIN - 026 | Metadata for database table/view &1 could not be accessed | |
31 | Message Number | ESH_HANA_ADMIN - 027 | Serializing data to XML stream unsuccessful for database table &1 | |
32 | Message Number | ESH_HANA_ADMIN - 028 | Sending indexing requests to HANA database failed | |
33 | Message Number | ESH_HANA_ADMIN - 029 | Sending indexing requests to HANA database table &1 failed | |
34 | Message Number | ESH_HANA_ADMIN - 030 | Search request on view &1 failed | |
35 | Message Number | ESH_HANA_ADMIN - 031 | Could not determine content counts from view &1 | |
36 | Message Number | ESH_HANA_ADMIN - 034 | Error while checking existence of table or view &1 in schema &2 | |
37 | Message Number | ESH_HANA_ADMIN - 035 | Proxy Method '&1' only supported for HANA destination | |
38 | Message Number | ESH_HANA_ADMIN - 036 | Error on determination of content counts for table/view &1 in schema &2 | |
39 | Message Number | ESH_HANA_ADMIN - 040 | Executed SQL statement: &1&2&3&4 | |
40 | Message Number | ESH_HANA_ADMIN - 041 | Ownership violation error on table modification operation | |
41 | Message Number | ESH_HANA_ADMIN - 047 | Proxy API error: Attempt to create HDB column table via TREX API '&1' | |
42 | Message Number | ESH_HANA_ADMIN - 048 | Proxy API error: Attempt to create TREX index via HDB Proxy API '&1' | |
43 | Message Number | ESH_HANA_ADMIN - 049 | Proxy API error: Attempt to modify HDB column table via TREX API '&1' | |
44 | Message Number | ESH_HANA_ADMIN - 050 | Proxy API error: Attempt to modify TREX index via HDB Proxy API '&1' | |
45 | Message Number | ESH_HANA_ADMIN - 051 | Could not create fulltext index on HDB table &1.&2 for attribute &3 | |
46 | Message Number | ESH_HANA_ADMIN - 052 | Could not drop fulltext index for attribute &3 on HDB table &1.&2 | |
47 | Message Number | ESH_HANA_ADMIN - 053 | Could not check existence of fulltext index for attribute &3 on &1.&2 | |
48 | Message Number | ESH_HANA_ADMIN - 054 | Could not get fulltext index for attribute &3 on HDB table &1.&2 | |
49 | Message Number | ESH_HANA_ADMIN - 055 | Fulltext index for attribute &3 on HDB table &1.&2 does not exist | |
50 | Message Number | ESH_HANA_ADMIN - 056 | Fulltext index for attribute &3 on HDB table &1.&2 not in ESH domain | |
51 | Message Number | ESH_HANA_ADMIN - 057 | Cannot drop fulltext index | |
52 | Message Number | ESH_HANA_ADMIN - 058 | Technical error on accessing fulltext index | |
53 | Message Number | ESH_HANA_ADMIN - 059 | Cannot generate fulltext index name for attribute &3 on HDB table &1.&2 | |
54 | Message Number | ESH_HANA_ADMIN - 060 | Fulltext index adjustment ended with errors | |
55 | Message Number | ESH_HANA_ADMIN - 061 | Technical error during re-execution of authorization index update: &1 | |
56 | Message Number | ESH_HANA_ADMIN - 062 | Process currently locked for some of the object types: &1 | |
57 | Message Number | ESH_HANA_ADMIN - 068 | Could not instantiate data access proxy, parameter &1 not supplied | |
58 | Message Number | ESH_HANA_ADMIN - 069 | Could not instantiate data access proxy for logical system &1 | |
59 | Message Number | ESH_HANA_ADMIN - 070 | Could not instantiate data access proxy for local system | |
60 | Message Number | ESH_HANA_ADMIN - 071 | Could not instantiate data access proxy for connection guid &1 | |
61 | Message Number | ESH_HANA_ADMIN - 072 | Connectivity error: Connection guid not mapped to logsys / ext system id | |
62 | Message Number | ESH_HANA_ADMIN - 073 | Could not instantiate data access proxy for system id &1 | |
63 | Message Number | ESH_HANA_ADMIN - 074 | Search system for search request cannot be determined | |
64 | Message Number | ESH_HANA_ADMIN - 075 | Search system for search request cannot uniquely be determined | |
65 | Message Number | ESH_HANA_ADMIN - 076 | Proxy for search system administration access not instantiated | |
66 | Message Number | ESH_HANA_ADMIN - 077 | Proxy for search system runtime access not instantiated | |
67 | Message Number | ESH_HANA_ADMIN - 078 | Scenario analyzer for landscape configuration analysis not instantiated | |
68 | Message Number | ESH_HANA_ADMIN - 079 | Index metadata compiler not instantiated | |
69 | Message Number | ESH_HANA_ADMIN - 080 | Connectivity mismatch on &1 instantiation (wrong conn guid &2) | |
70 | Message Number | ESH_HANA_ADMIN - 081 | Local connection [HDB/TREX] not set up on system &1 / client &2 | |
71 | Message Number | ESH_HANA_ADMIN - 082 | Connectivity error: Template type &1 not supported with hdb/trex proxy | |
72 | Message Number | ESH_HANA_ADMIN - 083 | Connectivity error: Connection for &1 (destination: &2) not valid | |
73 | Message Number | ESH_HANA_ADMIN - 084 | Remote connecitvity for &1, &2-Conn. &3, supports read-only access only | |
74 | Message Number | ESH_HANA_ADMIN - 085 | Remote connecitvity for &1, &2-Conn. &3: Database schema not supplied | |
75 | Message Number | ESH_HANA_ADMIN - 086 | Cannot determine database schema for log. system &1, &2-connection &3 | |
76 | Message Number | ESH_HANA_ADMIN - 087 | Cannot determine database schema - connectivity not specified | |
77 | Message Number | ESH_HANA_ADMIN - 088 | Cannot build schema mapping: &1 | |
78 | Message Number | ESH_HANA_ADMIN - 089 | Cannot compile index/table metadata for node: &1 | |
79 | Message Number | ESH_HANA_ADMIN - 092 | Calculated attribute maintenance on database ended with errors | |
80 | Message Number | ESH_HANA_ADMIN - 093 | Could not generate calculated attribute &1&2 on table &3.&4 | |
81 | Message Number | ESH_HANA_ADMIN - 094 | Could not check existence of calculated attribute &1&2 on table &3.&4 | |
82 | Message Number | ESH_HANA_ADMIN - 095 | Could not drop calculated attribute &1&2 from table &3.&4 | |
83 | Message Number | ESH_HANA_ADMIN - 096 | Could not get properties of calculated attribute &1&2 on table &3.&4 | |
84 | Message Number | ESH_HANA_ADMIN - 097 | Calculated attribute &1&2 on HDB table &3.&4 does not exist | |
85 | Message Number | ESH_HANA_ADMIN - 098 | Calculated attribute &1&2 on HDB table &3.&4 not in ESH domain | |
86 | Message Number | ESH_HANA_ADMIN - 099 | Cannot drop calculated attribute | |
87 | Message Number | ESH_HANA_ADMIN - 100 | &1&2&3&4 | |
88 | Message Number | ESH_HANA_ADMIN - 105 | HANA version too old: HANA revision: &1, required HANA revision: &2 | |
89 | Message Number | ESH_TREX_ADMIN - 000 | Index &1 could not be cleared | |
90 | Message Number | ESH_TREX_ADMIN - 001 | Index &1 could not be copied | |
91 | Message Number | ESH_TREX_ADMIN - 002 | Index &1 could not be created | |
92 | Message Number | ESH_TREX_ADMIN - 003 | Join index &1 could not be created | |
93 | Message Number | ESH_TREX_ADMIN - 004 | Language index &1 could not be created | |
94 | Message Number | ESH_TREX_ADMIN - 005 | Attributes could not be defined for index &1 | |
95 | Message Number | ESH_TREX_ADMIN - 006 | Index &1 could not be deleted | |
96 | Message Number | ESH_TREX_ADMIN - 007 | Could not retrieve attribute definitions for index &1 | |
97 | Message Number | ESH_TREX_ADMIN - 008 | Could not get list of indexes | |
98 | Message Number | ESH_TREX_ADMIN - 009 | MIME types could not be determined | |
99 | Message Number | ESH_TREX_ADMIN - 010 | Could not determine TREX version information for destination &1 | |
100 | Message Number | ESH_TREX_ADMIN - 011 | Could not check whether or not indexes exist | |
101 | Message Number | ESH_TREX_ADMIN - 012 | Could not rename index &1 | |
102 | Message Number | ESH_TREX_ADMIN - 013 | Indexes could not be renamed | |
103 | Message Number | ESH_TREX_ADMIN - 014 | Index &1 could not be shown | |
104 | Message Number | ESH_TREX_ADMIN - 015 | Indexes could not be shown | |
105 | Message Number | ESH_TREX_ADMIN - 016 | Index information cannot be retrieved for index &1 | |
106 | Message Number | ESH_TREX_ADMIN - 027 | Attributes could not be redefined for index &1 | |
107 | Message Number | ESH_TREX_ADMIN - 028 | Attribute could not be deleted for index &1 | |
108 | Message Number | ESH_TREX_ADMIN - 038 | Index request did not succeed | |
109 | Message Number | ESH_TREX_ADMIN - 039 | Search was unsuccessful | |
110 | Message Number | ESH_TREX_ADMIN - 040 | Serializing data to XML stream unsuccessful for index &1 | |
111 | Message Number | ESH_TREX_ADMIN - 041 | Indexing an internal table unsuccessful for index &1 | |
112 | Message Number | ESH_TREX_ADMIN - 051 | Unknown TREX version | |
113 | Message Number | ESH_TREX_ADMIN - 055 | Could not resolve a TREX destination | |
114 | Message Number | ESH_TREX_ADMIN - 063 | Could not optimize index &1 | |
115 | Message Number | ESH_TREX_ADMIN - 066 | Retrieving join index information unsuccessful for index: &1 | |
116 | Message Number | ESH_TREX_ADMIN - 083 | Error while retrieving landscape information for destination &1; &2 | |
117 | Message Number | ESH_TREX_ADMIN - 084 | Error while retrieving landscape summary for destination &1; &2 | |
118 | Message Number | ESH_TREX_ADMIN - 085 | TREX server is in a bad state. Check the TREX landscape summary | |
119 | Message Number | ESH_TREX_ADMIN - 086 | TREX version &1 is not up-to-date. Update to the latest revision | |
120 | Message Number | ESH_TREX_ADMIN - 089 | Error occured on adjusting authorization indexes | |
121 | Message Number | ESH_TREX_ADMIN - 092 | Error while retrieving TREX load history for destination &1; &2 | |
122 | Message Number | ESH_TREX_ADMIN - 093 | Ownership violation error on index modification operation | |
123 | Message Number | ESH_TREX_ADMIN - 131 | TREX call terminated with TREX engine error. Error code: &1 | |
124 | Message Number | ESH_TREX_ADMIN - 132 | TREX call terminated with technical error | |
125 | Message Number | ESH_TREX_ADMIN - 133 | Error message: &1&2&3&4 | |
126 | Message Number | ESH_TREX_ADMIN - 134 | Further specific error messages could not be retrieved | |
127 | Message Number | ESH_TREX_ADMIN - 136 | TREX sanity check: &1&2&3&4 | |
128 | Message Number | ESH_TREX_ADMIN - 138 | TREX sanity check failed | |
129 | Message Number | ESH_TREX_ADMIN - 143 | Could not set property &1 for index &2. Should have been set to &3. | |
130 | Message Number | ESH_TREX_ADMIN - 144 | Index check on join creation: Cannot check indexes for existence: &1 | |
131 | Message Number | ESH_TREX_ADMIN - 145 | Index check on join creation: Cannot check index &1 for existence | |
132 | Message Number | ESH_TREX_ADMIN - 146 | Cannot interpret index suffix for index id &1 | |
133 | Message Number | ESH_TREX_ADMIN - 147 | Index check on join creation: Cannot recreate missing index &1 | |
134 | Message Number | ESH_TREX_ADMIN - 148 | Could not merge deltas for index &1 | |
135 | Message Number | ESH_TREX_ADMIN - 201 | Bulk search execution not successful | |
136 | Message Number | ESH_TREX_ADMIN - 202 | Handle status for parallel query could not be retrieved | |
137 | Message Number | ESH_TREX_ADMIN - 203 | Search result for handle of parallel query could not be retrieved |