Do you have any question about this error?
Message type: E = Error
Message class: ESH_HANA_ADMIN - ESH HANA Index Administration
Message number: 220
Message text: Objekt &1 (SWK &2) kann nicht tabellenbasiert angelegt werden
This message is returned - as warning only - on ESH search connector
creation or update if an ESH search connector or a single model
contained or used or referenced in an ESH search connector cannot be
generated as "table-based" - as modeled - but has to be generated as
"replication-based".
The reason(s) for the switch from "table-based" to "replication-based"
will typically be reported in the neighboring messages (in most cases:
also warnings) in the job log.
Connector creation will continue,
but the result - replication-based connectors - is probably not as
intended.
Connectors which get created in "replication mode" will not be active
right from the start.
They will only be set to status "Prepared" after creation, and require
initial indexing to be set to status "Active" and "Searchable" and -
depending on use-case - registration for real-time indexing or scheduled
delta indexing to get updated regularly.
If you get this message you should check whether the switch to
"replication mode" is intended - some scenarios can only be run in
replication mode - or whether it happened accidentally, for example due
to missing scenario configuration or due to missing table access
privileges for the HANA database tables. In the switch to
replication-mode is not intended the reasons should be identified and
the scenario should be corrected.
To find out the reasons for the switch from table-based to the
replication scenario for the affected objects check the neighboring
detail messages in the job log.
Once the reasons for the switch to replication mode are detected and
corrected you can re-update the connectors from the ESH cockpit. They
will then be generated as table-based.
&SYS_ADMIN
The message applies only to scenario Enterprise Search on HANA
In the scenario Enterprise Search on TREX all connectors will require
indexing by default.
Note: Some search models are generally not table-based for technical
reasons, i.e. they are "replication-only" by nature. If a connector is
relying on at least one of these replication-based objects the overall
connector will require an indexing step, whereby only the
replication-based objects will have to be indexed to activate the
connector.
For objects modeled as "replication-only" the message "object has been
switched to replication mode" will not be issued.
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
ESH_HANA_ADMIN220
- Objekt &1 (SWK &2) kann nicht tabellenbasiert angelegt werden ?Get instant SAP help. Start your 7-day free trial now.
ESH_HANA_ADMIN219
Schemazuordnung für Knoten &1.&2: Tabelle &3 nicht in Schema &4 gefunden
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
ESH_HANA_ADMIN218
Tabellen-/Schemazuordnung an folgender Stelle fehlgeschlagen
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
ESH_HANA_ADMIN221
Objekt &1 (SWK &2) wird im Replikationsmodus generiert
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
ESH_HANA_ADMIN222
Spez. Tab./Schemazuordnung f. Knoten &1.&2: Knoten zu Tab &3.&4 zugeordn.
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.