SAP Knowledge Base Article - Preview

3350367 - DB2: MPOS activation fails due to exception condition "ADBC_SQL_ERROR"

Symptom

MPOS (Master Planning Object Structure) activation fails with following dump:

Category               ABAP Programming Error
Runtime Errors         RAISE_EXCEPTION
ABAP Program           SAPLRSDU_CUBE_DB2
Application Component  BW-SYS-DB-DB2
Date and Time          22.06.2023 22:22:22

 Short Text
     Exception condition "ADBC_SQL_ERROR" triggered

 What happened?
     The current ABAP program has encountered an unexpected situation.

Information on where terminated
    The termination occurred in ABAP program "SAPLSTU3_CONFIG", in
     "STU3_GET_SYSPARMS". The main program was "/SAPAPO/SAPLMSDP_ADMIN".

    In the source code, the termination point is in line 203 of (Include)
    program "LSTU3_CONFIGU04".


The corresponding work process trace shows SQL204N error meaning the BW infocube tables do not exist.
For example:

*** ERROR => DB2 Call 'SQLExecDirectW' Error: conHdl = 00 SQLCODE = -204:
[IBM][CLI Driver][DB2] SQL0204N  "SAPDSA./BIC/V<cube name>F" is an undefined name


Checking infocube status shows the cube is not yet activated. 

  1. Run transaction code: RSA1
  2. Search with cube name
  3. Version: In process
    Object status: Inactive


Read more...

Environment

  • SAP Supply Chain Management with Advanced Planning and Optimization
  • IBM Db2 for z/OS

Product

SAP NetWeaver 7.5

Keywords

KBA , BW-SYS-DB-DB2 , BW DB2 for z/OS , SCM-APO-FCS-BF , Basic Functions , BW-WHM-DBA-ICUB , InfoCubes , 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.