short dump CL_DBA_RDI_QUERY==============CP

Hello

We are getting this short dump in SolMan SP10.

CL_DBA_RDI_QUERY==============CP

Category ABAP Programming Error

Runtime Errors MESSAGE_TYPE_X

ABAP Program CL_DBA_RDI_QUERY==============CP

Application Component BC-DB

Date and Time 09.12.2013 14:50:27

Short text

Error analysis

Short text of error message:

Object RDI_QUERY: Method call INIT_FILTER failed with return code = No m

eta data for DDIC filter source NAME. Typicall

Long text of error message:

Technical information about the message:

Message class....... "DB6PM"

Number.............. 001

Variable 1.......... "RDI_QUERY"

Variable 2.......... "INIT_FILTER"

Variable 3.......... "No meta data for DDIC filter source NAME. Typicall"

Variable 4.......... " "

Cheers

SAP Managed Tags:
SAP Solution Manager

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (4)

Hi Marian,

I had the same issue.

Please check note 1971431 - Short dump MESSAGE_TYPE_X "No meta data for DDIC filter source NAME. Typicall" to resolve this.

Regards,

Stijn

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello Marian,

can you please attach the developer trace (dev_w*) associated with the error ? the whole dump will show that information.

Regards,

Javier

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Javier

Here are the infos from the wp trace:

ABAP Program CL_DBA_RDI_QUERY==============CP .

Source CL_DBA_RDI_QUERY==============CM01C Line 56.

Error Code MESSAGE_TYPE_X.

Module $Id: //bas/720_REL/src/krn/runt/abdynpro.c#11 $ SAP.

Function ab_jmess Line 1428.

Hello Marian,

it is a strange error as your system is Oracle and the error looks like coming from a DB6 system.

Please check if there is a DB6 system connected to this SolMan, you can see this in DBAcockpit connections. If there is one ore more DB6 systems connected then please check in those systems

if the dbacockpit composite note is applied (depending on Basis release) in transaction SNOTE

note

1456402 DB6: DBA Cockpit Correction Collection SAP Basis 7.02 / 7.30

1314750 DB6: DBA Cockpit Correction Collection SAP Basis 700 / 710

1309424 DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11

Regards,
Javier

Hello Marian ,

We are also having the same issue. Were you able to find a solution for this issue.

Regards

Ram

Hi Ram

No solution so far. I'm still searching ...

Cheers

Marian

I Also got this dump. I've identified a DVM extractor as the causer. I was able to inactivate the DVM extractors. Have you attempted DVM configuration?

THis isn't a solution. Just avoids the dump at the cost of DVM.

Ken

Marian

In case you want to avoid the dumps at the cost of DVM try this:

Run trans E2E_EXTRACTOR_FWK.

Filter by Extractor name = "DVM Size Statistics Extractor (DBCON)"

Select each (failing) extractor you find. If the extractor log says something like "...triggered a termination with a short dump" you could deactivate the extractor.

Set change mode, press deactivate button.

I actually think "1943833 SYB: MESSAGE_TYPE_X in dashboard screen" is a better fit in terms of termination location but I have no SYB db's... and SNOTE says cannot be implemented.

regards,

Ken

Hi Ken

Thank you for the info but unfortunately this workaround does not apply for my case.

The search continues ...

Cheers

Marian

Can you attach full dump?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Here are more details.

Category ABAP Programming Error

Runtime Errors MESSAGE_TYPE_X

ABAP Program CL_DBA_RDI_QUERY==============CP

Application Component BC-DB

Date and Time 09.12.2013

----------------------------------------------------------------------------------------------------

|Short text |

| The current application triggered a termination with a short dump. |

----------------------------------------------------------------------------------------------------

|What happened? |

| The current application program detected a situation which really |

| should not occur. Therefore, a termination with a short dump was |

| triggered on purpose by the key word MESSAGE (type X). |

----------------------------------------------------------------------------------------------------

|What can you do? |

| Note down which actions and inputs caused the error. |

| |

| To process the problem further, contact you SAP system |

| administrator. |

| |

| Using Transaction ST22 for ABAP Dump Analysis, you can look |

| at and manage termination messages, and you can also |

| keep them for a long time. |

----------------------------------------------------------------------------------------------------

|Error analysis |

| Short text of error message: |

| Object RDI_QUERY: Method call INIT_FILTER failed with return code = No m |

| eta data for DDIC filter source NAME. Typicall |

| |

| Long text of error message: |

| |

| Technical information about the message: |

| Message class....... "DB6PM" |

| Number.............. 001 |

| Variable 1.......... "RDI_QUERY" |

| Variable 2.......... "INIT_FILTER" |

| Variable 3.......... "No meta data for DDIC filter source NAME. Typicall" |

| Variable 4.......... " " |

----------------------------------------------------------------------------------------------------

|How to correct the error |

| Probably the only way to eliminate the error is to correct the program. |

| - |

| |

| If the error occures in a non-modified SAP program, you may be able to |

| find an interim solution in an SAP Note. |

| If you have access to SAP Notes, carry out a search with the following |

| keywords: |

| |

| "MESSAGE_TYPE_X" " " |

| "CL_DBA_RDI_QUERY==============CP" or "CL_DBA_RDI_QUERY==============CM01C" |

| "INIT_FILTER" |

| |

| If you cannot solve the problem yourself and want to send an error |

| notification to SAP, include the following information: |

| |

| 1. The description of the current problem (short dump) |

| |

| To save the description, choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 2. Corresponding system log |

| |

| Display the system log by calling transaction SM21. |

| Restrict the time interval to 10 minutes before and five minutes |

| after the short dump. Then choose "System->List->Save->Local File |

| (Unconverted)". |

| |

| 3. If the problem occurs in a problem of your own or a modified SAP |

| program: The source code of the program |

| In the editor, choose "Utilities->More |

| Utilities->Upload/Download->Download". |

| |

| 4. Details about the conditions under which the error occurred or which |

| actions and input led to the error. |

| |

----------------------------------------------------------------------------------------------------

|System environment |

| SAP Release..... 702 |

| SAP Basis Level. 0013 |

| |

| Application server... "xxxxxx" |

| Network address...... "xxxxxx" |

| Operating system..... "Linux" |

| Release.............. "xxxxxx" |

| Hardware type........ "x86_64" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 24 |

| Shortdump setting.... "full" |

| |

| Database server... "xxxxxx" |

| Database type..... "ORACLE" |

| Database name..... "xxxxxx" |

| Database user ID.. "xxxxxx" |

| |

| Terminal.......... " " |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 720 |

| created (date)... "Oct 13 2013 19:25:13" |

| create on........ "xxxxxx" |

| Database version. "OCI_112, 11.2.0.3.0, V1, default" |

| |

| Patch level. 514 |

| Patch text.. " " |

| |

| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |

| SAP database version. 720 |

| Operating system..... "Linux 2.6, Linux 3" |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 4189800 |

| Heap.... 0 |

| Page.... 0 |

| MM Used. 3784752 |

| MM Free. 402400 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. 001 |

| User................ "SM_EFWK" |

| Language key........ "xxxxxx" |

| Transaction......... " " |

| Transaction ID...... "52A5A4285CEF0D60E10000000A020258" |

| |

| EPP Whole Context ID.... "000C29A3C1C21EE3978245692E788B9B" |

| EPP Connection ID....... "52A56340CB9242ADE10000000A020258" |

| EPP Caller Counter...... 1 |

| |

| Program............. "CL_DBA_RDI_QUERY==============CP" |

| Screen.............. "SAPMSSY1 3004" |

| Screen Line......... 2 |

| Debugger Active..... "none" |

----------------------------------------------------------------------------------------------------

The "xxxx" fields are replaced on purpose.

Hello Marian,

Can you check if this note is applicable to your system.

1855464 - DB6: Runtime error MESSAGE_TYPE_X during REORG of a table

Mudasir.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count