SAP Knowledge Base Article - Preview

3086948 - CMS failed to be started after CMS database is upgraded to Oracle 19c

Symptom

  • CMS failed to be started after CMS database is upgraded to Oracle 19c
  • Log in to Central Management Console will be also failed with error: 
    Account information not recognized: Could not reach CMS 'xxxxxx'. The CMS on machine 'xxxxxx' was stopped due to a critical error. (FWM 20031)
  • Running cmsdbsetup.sh can see error as: 
    ORA-28040: No matching authentication protocol


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform 4.2 Support Pack 07
  • Oracle 19c
  • Suse Linux system

Product

SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 4.3

Keywords

cmc, oracle, ora, 28040, bi launch pad, cms, boe_cmsd , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , 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.