SAP Knowledge Base Article - Preview

3760283 - replica creation leaves replication_status unknown due to unresolved source hostname

Symptom

  • After running CREATE DATABASE AS REPLICA OF AT '', tenant replication does not start.
  • M_DATABASE_REPLICAS and M_DATABASE_REPLICA_STATISTICS show REPLICATION_STATUS = UNKNOWN and REPLICATION_MODE = UNKNOWN; TARGET_FULLY_RECOVERABLE = FALSE.
  • Trace/log shows hostname resolution error: “exception 2112401: Failed to resolve hostname […] with exception 2050100: System call failed [addrinfo:-2]: Name or service not known”.
    [2003901]{-1}[-1/-1] 2026-05-15 14:45:19.176922 e sr_dataaccess    DisasterRecoverySecondaryImpl.cpp(00938) : Error occurred during connect to primary: exception 2112401: Failed to resolve hostname [hostname1] with exception
    exception 2050100: System call failed [addrinfo:-2]: Name or service not known
  • During attempts, SSL errors may be observed: “DBTech JDBC: general error … SQLDBC error -10709 … SSL certificate validation failed: Peer not trusted; chain incomplete or untrusted”.
  • Nameserver trace may show: “Could not load PSE file … 3_dbrep_temp.pse (security profile not found)”.


Read more...

Environment

SAP HANA, platform edition

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

hana tenant copy, system replication, replication_status unknown, replication_mode unknown, target_fully_recoverable false, failed to resolve hostname, name or service not known, exception 2050100, exception 2112401, create database as replica, m_database_replicas, m_database_replica_statistics, dns, hosts file, peer not trusted, ssl certificate validation failed , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem

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.