Symptom
- The SDA replication table does not function after a source database failover/takeover
- Error message in HANA Cloud indexserver trace file: "SQL Error: Unable to connect remote source: [SAP AG][LIBODBCHDB SO][HDBODBC] General error;10 authentication failed: Detailed info for this error can be found with correlation ID 'XXXXXXXXXXXXXXX' (adapter type: hanaodbc, source name: YYYYYYYY)".
- Error message in remote source on-premise HANA indexserver trace file: "403: internal error".
Once correlation ID in the error message parsed with below query, you will found the authentication error due to JWT issuer does not match what exists in HANA Cloud instance:
- SELECT * FROM SYS.AUTHENTICATION_ERROR_DETAILS WHERE CORRELATION_ID = '<your correlation ID>';
"JWT provider does not exist: issuer=hana_rtr://1a2b3c4d-1a2b-1a2b-1a2b-1a2b3c4d5e6f/{sid}/{dbname}."
Read more...
Environment
- SAP HANA 2.0 < SPS05 Revision 059.17.
- SAP HANA 2.0 < SPS07 Revision 079.04.
- SAP HANA 2.0 < SPS08 Revision 085.00.
Product
Keywords
RTR, remote table replication, sda replication, hana cloud, failover issue, takeover, jwt provider, authentication failed, hana_rtr, jwt issuer name, hana cloud replication, hana failover, hana sda error, hana cloud jwt fix, sap hana bug fix, hana sda workaround, hana replication error. , KBA , HAN-CLS-HC , HANA Cloud Services HANA Cloud , HAN-DB-SDA , SAP HANA Smart Data Access , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview