ESH_BOS_INDEX_CTRL - Trex Inderxing on the ES Hub
The following messages are stored in message class ESH_BOS_INDEX_CTRL: Trex Inderxing on the ES Hub.
It is part of development package S_ESH_ENG_BOS_INDEX in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "BOS Index".
It is part of development package S_ESH_ENG_BOS_INDEX in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "BOS Index".
Message Nr ▲ | Message Text |
---|---|
001 | Application log created by the index controller for logical system &1 |
002 | Existence check for &1: Index found |
003 | Existence check for &1: Error number &2, description: &3 |
004 | Deletion of index &1: Index deleted |
005 | Deletion of index &1: Error number &2, description: &3 |
006 | Creation of index &1: Index created |
007 | Creation of index &1: Error number &2, description: &3 |
008 | Existence check of &1: Index not found |
009 | Entries not consistent: Node &1 and object type &2 |
010 | Starting extraction/indexing for object type &1 and node &2 |
011 | Starting process chain &1 |
012 | Could not start process chain &1 -> stop indexing |
013 | Process chain &1 completed successfully |
014 | Process chain &1 ended with error |
015 | Process chain &1 was terminated |
016 | Data extraction ended with error -> indexing aborted |
017 | No process chain found for &1 &2 |
018 | Starting preparation for object type &1 and node &2 |
019 | Could not create definition for index ID &1 |
020 | Iterator for index ID &1 is missing |
021 | Iterator for index ID &1 contains no data |
022 | &1 |
023 | Indexing of &1 has returned subrc &2, error code &3, and error text &4 |
024 | Optimization of &1 has returned subrc &2, error code &3, and err. text &4 |
025 | Optimization of &1 was successful |
026 | TREX destination has not been maintained |
027 | Search connector ID &1 (&2) is not valid |
028 | Generating process chain for data source &1 |
029 | Number of nodes to prepare: &1 |
030 | Logical system &1 is different to the one used by instance &2 |
031 | Business object &1 is different to the one used by instance &2 |
032 | Index ID is initial |
033 | Error while indexing &1; index ID &2 returns no results |
034 | &1: Preparation is still running for some nodes |
035 | Schedule job &1 |
036 | Job &1 scheduled successfully |
037 | Exception at 'JOB_OPEN': &1 |
038 | Exception at 'JOB_SUBMIT': &1 |
039 | Exception at 'JOB_CLOSE': &1 |
040 | Extracting/indexing is still running for some nodes |
041 | No model instance received for model &1 |
042 | Number of nodes to index: &1 |
043 | An error occurred during indexing in TREX |
044 | Process chain &1 ended with status &2 |
045 | TREX comp. definition could not be determined for node &1 and index &2 |
046 | Error occurred during index creation in TREX |
047 | Error while creating the physical index &1 |
048 | Set node status to: &1 |
049 | Create join indices |
050 | No root node found for object type &1 |
051 | Error while decomposing index ID &1 |
052 | Invalid parameter while decomposing index ID &1 |
053 | Error while reading the index buffer |
054 | Error while creating the data structure for index ID &1 |
055 | No data to be indexed for authorization index ID &1 |
056 | Error while composing the index name for object type &1, node &2, type &3 |
057 | Error while filling the definition of object type &1, node &2, scope &3 |
058 | Logical system &1 or object type &2 is empty |
059 | Error while checking the existence of join index &1 on TREX &2 |
060 | Error while reading the model for the object type &1 |
061 | No instance of the object model was created |
062 | No instance of the data provider was created |
063 | No table entry found for data provider &1 and model &2 |
064 | Extraction technology: &1 |
065 | Data source type: &1 |
066 | Data source name: &1 |
067 | Cross client: &1 |
068 | Indexing ended with error |
069 | No data iterator was created for the node |
070 | Invalid parameter: ID &1, value &2 |
071 | User data is not indexed, yet. Index user data first |
072 | Indexing of authorization indices ended with error |
073 | Indexing of logical indices ended with error |
074 | At least one physical index could not be indexed |
075 | Indexing of authorization indices and logical indices not possible |
076 | Found status: &1 |
077 | Wait and try again |
078 | No nodes found -> exit program |
079 | Indexing of complete objects from type &1 has returned &2 &3 |
080 | Reading of &1 has returned subrc &2, error code &3, and error text &4 |
081 | No connectivity instance received for connection GUID &1 |
082 | No requests found -> exit program |
083 | No fields found -> exit program |
084 | No fields found for node &1 |
085 | Error while creating the data structure for node &1 |
086 | No instance of the indexing controller was created |
087 | No instance of the object iterator was created |
088 | No instance of the object iterator by time was created |
089 | Provider error during creation of the object iterator |
090 | Unknown ID error during creation of the object iterator |
091 | Delta indexing not supported -> switch to full indexing |
092 | Provider error during execution of the NEXT method |
093 | Error while populating index &1 |
094 | Execute initial indexing |
095 | Execute periodic indexing |
096 | Error while optimizing index &1 |
097 | Provider error during creation of the object iterator time |
098 | The implementing class does not support the iterator by time interface |
099 | Multi-index call of index &1 has returned &2: &3 |
100 | Not supported error during creation of the object iterator |
101 | Implementation did not provide any data -> exit indexing |
102 | &1 objects extracted in &2 seconds |
103 | Indexing &1; error when searching dependent entries from &2 |
104 | Data of NW authorization objects could not be indexed |
105 | No instance of class CL_ESH_OM_AUTHNW was created |
106 | No authorization objects found -> exit indexing |
107 | No hash code generated for node &1, check &2, and authorization object &3 |
108 | Error when reading the authorization check &1 |
109 | Error when reading the index &1 |
110 | No language attribute filled for the information to be indexed in &1 |
111 | No instance of the indexing controller was created for object type &1 |
112 | Error reading the model for object type &1 and node &2 |
113 | Response attribute &1 refers to something inactive &2 &3 &4 |
114 | Request attribute &1 refers to something inactive &2 &3 &4 |
115 | Relation &1 between node &2 and node &3 has no attribute mapping |
116 | Error while checking the response attributes of object type &1 node &2 |
117 | Error while checking the request attributes of object &1 node &2 req. &3 |
118 | Authorization check &1 refers to something inactive &2 &3 &4 |
119 | Authorization check &1 refers to an inactive start object type &2 &3 |
120 | Authorization check &1 could not be read |
121 | Could not calculate path object type &1 node &2 to object type &3 node &4 |
122 | Could not find the node for object type &1 and check &2 |
123 | Indexing for object &1, logsys &2 already running. Process canceled |
124 | Technical error while requesting lock for indexing object &1 logsys &2 |
125 | Check if the generic extraction can be used for &1 |
126 | The generic extraction implementation cannot be used for &1 |
127 | Indexing of type &1 has no information for the root node |
128 | Use the generic extraction implementation for &1 |
129 | No implementation has been selected for object type &1 |
130 | TREX classification: Could not calculate path to node &1 |
131 | TREX classification: Could not calculate path to node &1 |
132 | Error while creating the property join index &1 on TREX &2 |
133 | Error while creating the extraction tables for object type &1 |
134 | No class instance was created to get the data by ID |
135 | Error in method CREATE_JOIN_CRT: ASSERT &1 |
136 | Error in method GET_INVOLVED_ATTRIBUTES: ASSERT &1 |
137 | Create attribute &1 in index &2: Error number &3, description: &4 |
138 | Delete attribute &1 in index &2: Error number &3, description: &4 |
139 | Change attribute &1 in index &2: Error number &3, description: &4 |
140 | Invalid search connector ID: &1 |
150 | Indexing of index &1 failed with dynamic call/illegal type exception |
151 | TREX call ended with return code &1, error message: &2&3&4 |