ESH_HANA_ADMIN - ESH HANA Index Administration
The following messages are stored in message class ESH_HANA_ADMIN: ESH HANA Index Administration.
It is part of development package S_ESH_ENG_TREX in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "TREX handling for Enterprise Search".
It is part of development package S_ESH_ENG_TREX in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "TREX handling for Enterprise Search".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | HANA destination is not available |
| 002 | HANA server with destination &1 is not available |
| 003 | Destination type has not been set |
| 004 | Destination type &1 not supported |
| 005 | Could not determine HANA version for connection &1 |
| 006 | HANA Sanity Check: Wrongly instantiated |
| 007 | HANA call terminated with a technical error |
| 008 | HANA call terminated with HANA engine error. Error code: &1 |
| 009 | Error message: &1&2&3&4 |
| 010 | No further error messages from HANA server |
| 011 | TREX API "&1" not supported with a HANA destination |
| 012 | Database table &1 could not be created |
| 013 | Database view &1 could not be created |
| 014 | Database table &1 could not be copied |
| 015 | Attributes could not be defined for table/view &1 |
| 016 | Database table/view &1 could not be deleted |
| 017 | Could not retrieve attribute definitions for table/view &1 |
| 018 | Could not delete attributes from table/view &1 |
| 019 | Could not get list of tables from HANA database |
| 020 | Table &1 could not be cleared |
| 021 | Could not check on HANA whether table &1 exists |
| 022 | Could not rename database table &1 |
| 023 | Changes could not be committed |
| 024 | Model information for database table/view &1 could not be accessed |
| 025 | Attributes could not be redefined for database table &1 |
| 026 | Metadata for database table/view &1 could not be accessed |
| 027 | Serializing data to XML stream unsuccessful for database table &1 |
| 028 | Sending indexing requests to HANA database failed |
| 029 | Sending indexing requests to HANA database table &1 failed |
| 030 | Search request on view &1 failed |
| 031 | Could not determine content counts from view &1 |
| 032 | Environment Details: &1 Version &2, Destination: &3, SAP Release &4 |
| 033 | Internal error: Multi-language indexing request for HANA destination |
| 034 | Error while checking existence of table or view &1 in schema &2 |
| 035 | Proxy Method '&1' only supported for HANA destination |
| 036 | Error on determination of content counts for table &1 in schema &2 |
| 037 | SELECT COUNT(*) query to database table ended with SQL exception |
| 038 | SQL query to database terminated with remote initialization error |
| 039 | SQL query to database terminated with exception 'bad request' |
| 040 | Executed SQL statement: &1&2&3&4 |
| 041 | Ownership violation error on table modification operation |
| 042 | Attempt to create table or view &1 with name not in ESH namespace |
| 043 | Attempt to delete table or view &1 not in ESH namespace |
| 044 | Attempt to alter table or view &1 not in ESH namespace |
| 045 | Attempt to copy table or view &1 to a table not in ESH namespace |
| 046 | Attempt to rename table or view &1 to a name not in ESH namespace |
| 047 | Proxy API error: Attempt to create HDB column table via TREX API '&1' |
| 048 | Proxy API error: Attempt to create TREX index via HDB Proxy API '&1' |
| 049 | Proxy API error: Attempt to modify HDB column table via TREX API '&1' |
| 050 | Proxy API error: Attempt to modify TREX index via HDB Proxy API '&1' |
| 051 | Could not create fulltext index on HDB table &1.&2 for attribute &3 |
| 052 | Could not drop fulltext index for attribute &3 on HDB table &1.&2 |
| 053 | Could not check existence of fulltext index for attribute &3 on &1.&2 |
| 054 | Could not get fulltext index for attribute &3 on HDB table &1.&2 |
| 055 | Fulltext index for attribute &3 on HDB table &1.&2 does not exist |
| 056 | Fulltext index for attribute &3 on HDB table &1.&2 not in ESH domain |
| 057 | Cannot drop fulltext index |
| 058 | Technical error on accessing fulltext index |
| 059 | Cannot generate fulltext index name for attribute &3 on HDB table &1.&2 |
| 060 | Fulltext index adjustment ended with errors |
| 061 | Technical error during re-execution of authorization index update: &1 |
| 062 | Process currently locked for some of the object types: &1 |
| 063 | Process to adjust attributes of table &1 ended with errors |
| 064 | Could not add attribute &1 to table &2 |
| 065 | Could not delete attribute &1 from table &2 |
| 066 | Could not resize attribute &1 of table &2 (type: &3, new length: &4) |
| 067 | Could not change type of attribute &1 of table &2 from &3 to &4 |
| 068 | Could not instantiate ESH connectivity: Parameter &1 not supplied |
| 069 | Could not instantiate ESH connectivity: Logical system &1 is invalid |
| 070 | Could not instantiate ESH connectivity: Local connection not found |
| 071 | Could not instantiate ESH connectivity: Connection Guid &1 is invalid |
| 072 | Connectivity error: Connection guid not mapped to logsys / ext system id |
| 073 | Could not instantiate ESH connectivity: System ID &1 is invalid |
| 074 | Search system for search request cannot be determined |
| 075 | Search system for search request cannot uniquely be determined |
| 076 | Proxy for search system administration access not instantiated |
| 077 | Proxy for search system runtime access not instantiated |
| 078 | Scenario analyzer for landscape configuration analysis not instantiated |
| 079 | Index metadata compiler not instantiated |
| 080 | Connectivity mismatch on &1 instantiation (wrong conn guid &2) |
| 081 | Local connection [HDB/TREX] not set up on system &1 / client &2 |
| 082 | Connectivity error: Template type &1 not supported with hdb/trex proxy |
| 083 | Connectivity error: Connection for &1 (destination: &2) not valid |
| 084 | Remote connecitvity for &1, &2-Conn. &3, supports read-only access only |
| 085 | Remote connecitvity for &1, &2-Conn. &3: Database schema not supplied |
| 086 | Cannot determine database schema for log. system &1, &2-connection &3 |
| 087 | Cannot determine database schema - connectivity not specified |
| 088 | Cannot build schema mapping: &1 |
| 089 | Cannot compile index/table metadata for node: &1 |
| 090 | Connectivity error: Cannot determine connection guid |
| 091 | Connectivity error: Cannot determine template type |
| 092 | Calculated attribute maintenance on database ended with errors |
| 093 | Could not generate calculated attribute &1&2 on table &3.&4 |
| 094 | Could not check existence of calculated attribute &1&2 on table &3.&4 |
| 095 | Could not drop calculated attribute &1&2 from table &3.&4 |
| 096 | Could not get properties of calculated attribute &1&2 on table &3.&4 |
| 097 | Calculated attribute &1&2 on HDB table &3.&4 does not exist |
| 098 | Calculated attribute &1&2 on HDB table &3.&4 not in ESH domain |
| 099 | Cannot drop calculated attribute |
| 100 | &1&2&3&4 |
| 101 | HANA version does not support calculated attributes |
| 102 | Search on alpha-numeric attributes may not support all input formats |
| 103 | Search on date or timestamp attributes may not support all date formats |
| 104 | For support of missing features you have to upgrade your HANA version |
| 105 | HANA version too old: HANA revision: &1, required HANA revision: &2 |
| 106 | File loader queue population for object &1, node &2 terminated with error |
| 107 | Cannot determine HTTP Destination to HANA Server |
| 108 | Supported languages for text analysis cannot be provided by HANA Server |
| 109 | Remote initialization exception occured |
| 110 | SQL exception occured |
| 111 | Exception '&1' occured |
| 112 | Cannot compile inlist query from data: Source attribute &1 unknown |
| 113 | Cannot compile inlist query from data: Bracket error |
| 114 | Cannot compile inlist query from data: Data reference assignemnt error |
| 115 | Check HTTP Destination for File Loader: &1 &2 &3 &4 |
| 116 | HTTP connection test failed |
| 117 | HTTP services for file loader cannot be reached |
| 118 | Connection check: There are duplicate local connections |
| 119 | Connection cleanup after system copy / client copy required |
| 120 | &1 connection test failed |
| 121 | Connectivity error: &1 connection &2 for local system &3 is failing |
| 122 | Connection '&1' to database is unknown |
| 123 | Creation of table &1 from source table &2 failed at step &3 |
| 124 | Error when merging delta index for &1 |
| 125 | Coud not determine table keys for table &1 |
| 126 | Enterprise Search is running on TREX |
| 127 | Enterprise Search is running on HANA |
| 128 | Enterprise Search is running on connected HANA server (Sidecar scenario) |
| 129 | Analytics-only scenario (Destination "No TREX") |
| 130 | TREX Destination: &1 |
| 131 | Enterprise Search Database Connection: &1 |
| 132 | Connection Details |
| 133 | HANA Host: &1 |
| 134 | HANA Version: &1 |
| 135 | DB User for ESH Connection: &1 |
| 136 | Schema for Search Connectors: &1 |
| 137 | Table source schema (DDIC Default) for table-based connectors: &1 |
| 138 | In addition, there are the following customized schema mappings |
| 139 | There are no customized table source schemata |
| 140 | Table source schema (customized) for SWC &2: &1 |
| 141 | Table source schema (customized) for SWC &2, Object Type &3: &1 |
| 142 | Table source schema (customized) for SWC &2, Object Type &3, Node &4: &1 |
| 143 | Table source schema (customized) for table-based connectors: &1 |
| 144 | Table source schema (customized) for the remaining connectors: &1 |
| 145 | Connectors for which tables cannot be located in &1 will be set up as &2 |
| 146 | The HANA server could not be reached or has not reacted (DB Conn. &1) |
| 147 | Please check the HANA connectivity |
| 148 | SQL Connection to HANA database (DB conn: &1) could not be opened |
| 149 | Check whether HANA connection &1 has been modified |
| 150 | SQL Table Function &1 could not be created |
| 151 | SQL Table Function &1 could not be deleted |
| 152 | Check whether SQL Table Function &1 exists failed with exception |
| 153 | Check whether SQL Table Function &1 is active failed with exception |
| 154 | Table &1 could not be created because old version still exists |
| 155 | Preceding existence check and/or deletion has failed |
| 156 | Could not copy database table &1 |
| 157 | Could not determine SQL datatypes for view attributes of view &1 |
| 158 | Could not determine SQL datatypes for table attributes of table &1 |
| 159 | Could not determine fulltext indices for search view &1 |
| 160 | Connectivity check failed |
| 161 | Process cannot continue and will be terminated |
| 162 | Real-time indexing will be rescheduled for reexecution in &1 minutes |
| 163 | Process will be terminated and a new process will be scheduled |
| 164 | Maximum runtime has been reached |
| 165 | Reorganization job &1 has been scheduled |
| 166 | Could not determine HANA Master Node for ATR Replication Scenario |
| 167 | Could not determine HANA Replication Node for ATR Replication Scenario |
| 168 | Could not determine HANA node assignments for application tables |
| 169 | Could not determine Volume ID for HANA Node &1 / indexserver |
| 170 | Could not determine HANA nodes |
| 171 | Could not determine the tables set up as ASYNCHRONOUS TABLE REPLICAS |
| 172 | Could not read HANA landscape host configuration |
| 173 | Could not move table &1.&2&3 to node &4 |
| 174 | Could not generated Replica Schema &1 for ATR Scenario |
| 175 | Check whether schema &1 exists ended with exception |
| 176 | Could not determine ATR replication tables for application tables |
| 177 | Could not determine table placement rules assigning schema to HANA node |
| 178 | Invalid ATR Replica Schema &1 |
| 179 | Invalid SQL Connection &1 |
| 180 | Replication Master Node not supplied |
| 181 | No HANA nodes, or missing authorization |
| 182 | No HANA nodes apart from Master Node, or missing authorization |
| 183 | Tables for table location check not supplied |
| 184 | Error occured on &1 - see further log messages |
| 185 | Not authorized for &1 |
| 186 | Could not schedule connector recompilation job |
| 187 | Execution of SELECT DISTINCT query on &1 (schema &2) failed |
| 188 | Cannot compose WHERE condition for query: &1 &2 &3 &4 |
| 189 | Invalid schema name &1 |
| 190 | Invalid table name &1 |
| 191 | Table &1 is not in ESH namespace |
| 192 | Could not create or access table &1 |
| 193 | Cannot determine client attribute - object/table metadata missing |
| 194 | Cannot generate calculated attributes for object type &1 |
| 195 | Cannot get DDIC schema for table - object/table metadata missing |
| 196 | Cannot get DDIC attributes for table &1 - DDIC raises &2 |
| 197 | Cannot check for data-aging attribute - object/table metadata missing |
| 198 | Cannot determine ESH key attributes - object/table metadata missing |
| 199 | Cannot determine ESH key attributes for &1 node &2 |
| 200 | Keys have to be defined either in model or in table/view definition |
| 201 | Keys have to be defined in model (node &1 is not table-based) |
| 202 | Cannot map generic domain attributes - object/table metadata missing |
| 203 | Cannot map generic domain attributes for &1 node &2 - domain: &3 |
| 204 | Attribute &1 cannot be determined and mapped in domain text-table &2 |
| 205 | Cannot determine authorization checks - model metadata missing |
| 206 | Cannot determine data providers - model metadata missing |
| 207 | Cannot determine calculated attribute usages - model metadata missing |
| 208 | Cannot determine calculated attribute usages - invalid relation &1 |
| 209 | Database table for &1 table-based node &2 does not comprise CLIENT attr |
| 210 | Cannot map authorization check &1 via ESHCLIENT |
| 211 | Cannot determine schema mapping for virtual object &1 - &2 |
| 212 | Cannot determine HANA attribute definition for node field &1 - &2 |
| 213 | Get Table for Join: Cannot determine file loader node table (ID: &1) |
| 214 | Get Table for Join: Schema mapping inconsistency for object &1 node &2 |
| 215 | Get Table for Join: Schema mapping not found for object &1 node &2 |
| 216 | Cannot determine application table mapping for object &1 node &2 |
| 217 | Application table mapping for object node &1.&2 not possible |
| 218 | Table/schema mapping failed at the following place |
| 219 | Schema mapping for node &1.&2: Table &3 is not found in schema &4 |
| 220 | Cannot create object &1 (SWC &2) as table-based object |
| 221 | Object &1 (SWC &2) will be generated in replication mode |
| 222 | Special table/schema mapping for node &1.&2: Node mapped to table &3.&4 |
| 223 | Table/schema mapping could not be determined for object node &1.&2 |
| 224 | Check access privileges for HANA user &1 to database schema &2 |
| 225 | Cannot determine table/schema mapping for ref-table of auth check &1 |
| 226 | Cannot generate auth index metadata for object &1 node &2 - &3 |
| 227 | Table/schema mapping determination ended with errors |
| 228 | Cannot create full-text index on &1.&2 - attribute &3 does not exist |
| 229 | ESH connectivity for client &1 cannot be determined |
| 230 | Asynchronous table replication scenario (ATR) is active |
| 231 | Search connectors will be generated based on ATR replication schema &1 |
| 232 | No master node selected |
| 233 | Choose a valid master node |
| 234 | Selected node is already used as replica node |
| 235 | No replica node selected |
| 236 | Choose a valid replica node |
| 237 | Selected node is already used as master node |
| 238 | Choose master node first |
| 239 | Replica Schema &1 already in use on system - cannot be changed |
| 240 | Could not determine fulltext indices for table &1.&2 |
| 241 | HANA Destination for CDS connectivity is not unique - &1 &2 &3 &4 |
| 242 | Logical system ID for CDS connectivity is not unique - &1 &2 &3 &4 |
| 243 | HANA Destination for CDS connectivity is inconsistent - &1 &2 &3 &4 |
| 244 | Initial connectivity setup has not succeeded |
| 245 | Could not acquire lock for fulltext index update - &1 &2 &3 &4 |
| 246 | &1: Fulltext index creation while another job tries to delete - &2 &3 &4 |
| 247 | It was not possible to adjust all fulltext indices for ESH |
| 248 | To repair: Execute reports &1 and &2 after the job is through |
| 249 | Parallel job is running on client &1 |
| 250 | System not based on SAP HANA |
| 251 | Could not instantiate the default HANA connectivity (local system) - &1 |
| 252 | Check the ESH setup |
| 253 | Full-text index for object node &1.&2 - attribute &3 is missing |
| 254 | The full-text index is expected on database table &1.&2 |
| 255 | The full-text index is expected on generated ESH table &1.&2 |
| 256 | Expected full-text index name: &1&2&3&4 |
| 257 | Execute "Repair" action in the ESH consistency check to resolve the issue |
| 258 | "Repair" action could not automatically correct the issue |
| 259 | Full-text index on database: &1&2&3&4 |
| 260 | Full-text index metadata is not in sync with database |
| 261 | Full-text index &1&2&3&4 is not parameterized as expected for ESH search |
| 262 | Fast preprocessing is OFF - Index cannot be used for all languages |
| 263 | Full-text index cannot be used to determine text snippets |
| 264 | Parameter "Original format" should to be set to "saved in index" |
| 265 | Full-text index is not enabled for fuzzy search |
| 266 | Error on database access |
| 267 | Regeneration of full-text indices has ended with errors |
| 268 | Could not release change-pointer reorganization job &1 |
| 269 | Check the authorization profile of real-time indexing user &1 |
| 270 | Full-text index for &1 is obsolete and will be removed |
| 271 | Obsolete entities detected - check whether connectors are still intact |
| 272 | No index content supplied for object &1, root node &2 |
| 273 | Table reference not found in imported object data |
| 274 | Index table for &1.&2 not registered in ESH_CRT_INDEX (type: physical) |
| 275 | Check the ESH search connector setup |
| 276 | Check the data extractor for object &1 or the ESH search connector setup |
| 277 | Affected Search Connector: &1 |
| 278 | Errors occured on determination of content counts |
| 279 | Errors occured while checking full-text index status |
| 280 | Could not determine HANA API Version: Metadata Call failed - HTTP-Dest &1 |
| 281 | This feature is not supported in bluesky context |
| 282 | System is view-layer-enabled ("bluesky" active) |
| 283 | DDIC Access Schema (View Layer, CDS): &1 |
| 284 | Generic HANA connectivity &1 (Conn Type &2) - No HANA version supplied |
| 285 | Blue-sky enabled system cannot be used as remote system - &1 &2 &3 &4 |
| 286 | Could not determine HANA API Version: SQL-Error occured - HANA Dest &1 |
| 287 | Could not determine HANA API Version: HANA unavailable - HANA Dest &1 |
| 288 | Could not reparameterize full-text index &1 - &2 &3 &4 |
| 289 | Full-text index &1 for &2 &3 field &4 has been reparameterized |
| 290 | Parameter &1: Changed from &2 to &3 |
| 291 | &1 : Skipped - as per SAP Note 3088737 |