SAP Knowledge Base Article - Preview

3618301 - SUM connects to wrong database host name in the phase MAIN_MIGPREPARE/SUBMOD_MIG_PREPARE_DT/EU_CLONE_MIG_DT_REV_PRP

Symptom

There is the following error in phase: MAIN_MIGPREPARE/SUBMOD_MIG_PREPARE_DT/EU_CLONE_MIG_DT_REV_PRP, the errors can be found in the SUM log MIGRATE_DT_REV_UNDO_PRP<XXX>_IMP.LOG 

A0TEDBSL 000 DBSL trace (): connect property [STATEMENTROUTINGWARNINGS = TRUE]
A0TEDBSL 000 DBSL trace (): Connect to database failed, rc=1, rcSQL=-10709
A0TEDBSL 000 DBSL trace ():: SQLCODE : -10709
A0TEDBSL 000 000 DBSL trace (): SQLERRTEXT : Connection failed (RTE:[89001] Cannot resolve host name 'A' rc=11001: No such host is kn\
A0TEDBSL 000 DBSL trace (): own. (A:38015))
A1EECTL 000 Connection to the database failed 

From the log, SUM detects the database host as A, but the system database host is B.


Read more...

Environment

ABAP systems

Product

SAP enhancement package for SAP ERP all versions

Keywords

sum, sandbox, production, dbhost, connection failed, s4hana conversion, sapdbhost, default.pfl, sapstartsrv, abap, main_migprepare, submod_mig_prepare_dt, eu_clone_mig_dt_rev_prp, DMO , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , 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.