cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP Dump : CONNE_IMPORT_WRONG_COMP_LENG while accessing db02 table spaces overview

Former Member
0 Kudos

Hi Experts,

Recently our BW system has been upgraded to SAP NetWeaver 7.3, and after this upgrade activity we are getting the dumps "CONNE_IMPORT_WRONG_COMP_LENG" while accessing the table spaces over view using DB02 Tcode.

Can someone please help me to come out from this issue.

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

Short text

    Error when attempting to IMPORT object "TAB_TS_GE_HI".

What happened?

    Error in the ABAP application program.

    The current ABAP program "SAPLS_ORA_COCKPIT_5" had to be interrupted because it

     contains

    a statement that cannot be executed.

    data was not the same as the length of the data created

    in the program.

What can you do?

    Take note of the actions and inputs that lead to the error.

    Contact your SAP administrator for further processing of the problem.

    Using transaction ST22 for ABAP short dump analysis you can see and

    administrate termination messages and retain them for a longer period.

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was

     not caught in

    procedure "C_ORA_TS_INIT" "(FUNCTION)", nor was it propagated by a RAISING

     clause.

    Since the caller of the procedure could not have anticipated that the

    exception would occur, the current program is terminated.

    The reason for the exception is:

    When importing the object "TAB_TS_GE_HI", the component 13 in the dataset

    had a different length from the corresponding component of the

    target object in the program "SAPLS_ORA_COCKPIT_5".

    The length is 12 in the dataset, but 8 in the program.

How to correct the error

    Try to find out why the object's number of decimal places should

    be 12.

    There are several possibilities:

    1.  The number of decimal places of the imported field has changed

        in the Data Dictionary. Make sure that the number of decimal

        places of the imported field is equal to the number of decimal

        places of the field in the Data Dictionary.

        If you cannot restore the data using another source, you must

        read the data using the "old" structure, convert it and then

        reexport it using the new structure. This ensures that future

       IMPORTs always use the new structure.

   2.  A new program version is active which no longer matches the data

       set. Try to correct the error by regenerating the program

    "SAPLS_ORA_COCKPIT_5".

       To do this, choose transaction SE38 in the SAP System. There

       enter the program name "SAPLS_ORA_COCKPIT_5". Then choose the "Gene

    function.

   You may able to find an interim solution to the problem

   in the SAP note system. If you have access to the note system yourself,

   please use the following search criteria:

       "CONNE_IMPORT_WRONG_COMP_LENG" "CX_SY_IMPORT_MISMATCH_ERROR"

       "SAPLS_ORA_COCKPIT_5" bzw. "LS_ORA_COCKPIT_5U14"

       "C_ORA_TS_INIT"

   If you cannot solve the problem yourself, please send the

   following documents to SAP:

   1. A hard copy print describing the problem (short dump).

      To obtain this, select "System->List->Save->Local File (unconverted)

      on the current screen.

   2. A suitable hardcopy printout of the system log.

      To obtain this, call the system log with Transaction SM21

      and set the time interval to 10 minutes before and 5 minutes after

      the short dump. In the display choose "System->List->Save->

      Local File (unconverted)"

   3. If the programs are your own programs or modified SAP programs,

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

Thanks & Regards,

Suresh Babu

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Suresh,

Check this OSS Note #1637421  - Short dump CONNE_IMPORT_WRONG_COMP_LENG

After system upgrade, you may face the following dump during execution of transaction DB02:

''

Reproducing the Issue

  1. Transaction DB02
  2. Tablespaces
  3. Overview

Resolution

     To correct this error you need to identify the affected monikey.

THanks,

Samik

Former Member
0 Kudos

Hi Samik,

Thanks a lot for your quick response and for the solution provided.

This is was resolved by following the procedures in Note 997535 to remove old entries from the MONI table.

Thanks & Regards

Suresh Babu

Answers (1)

Answers (1)

ronak_pandya
Explorer
0 Kudos

Hi Guys,

I am a fresher in SAP ABAP. I am also facing the same issue

(CONNE_IMPORT_WRONG_COMP_LENG") .

As suggested i tried implementing note 9967535 .

But the note 997535 ,status is showing Cannot be implemented. Is there any alternate to this note.

Can someone please help me to come out from this issue.


Regards

Ronak Pandya

Former Member
0 Kudos

Hi Ronak,

This note 997535 can't be applied through SNOTE, This note have manual steps. So you need to follow those steps to fix your issue.

You have mentioned the wrong note 9967535 which is typo, the correct note number is : 997535

Regards,

Suresh Babu