APO - DBIF_DSQL2_CONNECTSTR_ERROR

[Former Member]

Hi,

We are having abap dumps in APO system related to above DBIF_DSQL2_CONNECTSTR_ERROR

Details:

Runtime Errors         DBIF_DSQL2_CONNECTSTR_ERROR

ABAP Program           CL_RSDRS_SQL_QUERY============CP

Application Component  BW-BEX-OT

Short Text

    The connection identifier is not known.

What happened?

    The connection identifier points to data in table DBCON that is

    required to create a database connection for multiconnect. No entry has

    been defined with key " " however.

Error analysis

    Triggering ABAP statement: Connect to " "

This is affecting /SAPAPO/* loads, I believe this is related to livecache, but unfortunately the SAPnotes I have checked were all pointing to description of issue "... defined with key "LCA"" or with "LCA", this does not.

Anyone has experience with this issue and resolution?

Thanks

[former_member229109]

Hello,

- Post the entries in DBCO.

- Create the SAP message to BW-BEX-OT to check it.

  Attach to the message the complete ABAP dump, system log & dev log of corresponding WP.

- What is your SCM database?

- Why do you think it is the liveCache issue?

Are you running the liveCache on HANA or MAXDB? What version?

- Post the part of the code where the dump occurred & the ABAP back stack.

  Review the help information at:

http://help.sap.com/abapdocu_70/en/ABAPEXEC_CONNECTION.htm

  What transaction you run when the dump occurred?

  Post the system log & corresponding dev log entries.

Regards, Natalia Khlopina

[Former Member]

Hi Natalia,

We are running on DB2 for SCM and MAXDB for Livecache.

1. We are not entirely sure that it is related to livecache but sT22 dumps are pointing to a processing calling out connection " " on dbcon but checking DBCO alll connections there are correctly configured.

2. Processes which are canceling are apo loads (/sapapo/xxx) using parallel profile processing.. it was isolated that without parallel processing profile the loads are working fine but putting it in parameters causing this dump to occur.

3. We have checked parallel profile processing in SCM and it is correctly configured to a working server group which is active and has sufficient workprocesses.

Yes already opened a message with SAP. We are working on trying to trace processes for this.

[Brindavan_M]

Hi Lan,

This dump is well know issue..

kindly check the database tablespace  and the filsystems which is related to database and increase the size.. if the dumps occurred frequently more then 500 hundreds then restart the system and cleanipc. Check the tmp directories , tablespace it might getting full or any long running jobs which affecting database.

Thanks,

BM

[Former Member]

Already checked this, the DB is fine, tablespace have enough free space.

[JamesZ]

Hi Ian,

Are you able to connect liveCache from SCM side?

LC10->LCA -> monitor

Please attach the dump and SAP work process trace for the dump to this discussion.

Also what is output of SE16->DBCON

Cheers,
James

[Former Member]

Hi James,

Yes LC10>LCA can be monitored fine.

st11 dev_w45 details on error:

A  Wed Mar  4 18:03:52 2015

A

A  ABAP Program CL_RSDRS_SQL_QUERY============CP        .

A  Source CL_RSDRS_SQL_QUERY============CM018      Line 39.

A  Error Code DBIF_DSQL2_CONNECTSTR_ERROR.

A  Module  $Id: //bas/741_REL/src/krn/abap/runt/absqlcon.c#4 $ SAP.

A  Function ab_CommitConnection Line 136.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_APC_ERROR entered.

A  ** RABAX: level LEV_RX_APC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end RX_RFC

We cannot display DBCON using se16, "you cannot display DBCON using standard tools", I've tried running connection tests on entries in DBCO and all succesfully connected to DB.

[JamesZ]

Hi Ian,

In that case, I think you better raise a ticket for SAP.

You need to provide below information for SAP:

1. the whole shot dump
2. SAP work process trace

I think either component BW-BEX-OT or BC-DB-LCA is possible component.

Cheers,
James