cancel
Showing results for 
Search instead for 
Did you mean: 

Development server performance is slow [ Review the error and help me,]

Former Member
0 Kudos

Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE

Exception CX_SY_IMPORT_MISMATCH_ERROR

Date and Time 24.12.2007 07:02:58

-

-


-

-


Short text

Error when attempting to IMPORT object "HIST2".

-

-


-

-


What happened?

Error in the ABAP Application Program

The current ABAP program "RSORAT4M" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

-

-


-

-


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

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 "AKT_DAY_HIST2" "(FORM)", 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 "HIST2", the component no. 8 in the

dataset has a different type from the corresponding component

of the target object in the program "RSORAT4M".

The data type is "I" in the dataset, but "P" in the program.

-

-


-

-


How to correct the error

Try to find out why the type of the object should be different.

There are various possible options:

1. The type of the imported field has changed in the Data Dictionary.

Make sure that the type of the imported field matches the type

of the field in the Data Dictionary.

If the data cannot be restored from another source, the data must be

read by the 'old' structure, converted und again eported with the new

structure, so that future IMPORTs will always function with the new

structure.

2. A new program version is active, which no longer fits the dataset.

Try to solve the error generating the program "RSORAT4M" again. This

works as follows: Select transaction SE38 in the SAP system. Enter

the program name "RSORAT4M". Then activate the function 'Generate'.

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:

"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"

"RSORAT4M" or "RSORAT4M"

"AKT_DAY_HIST2"

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.

The exception must either be prevented, caught within proedure

"AKT_DAY_HIST2" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

-

-


-

-


System environment

SAP-Release 700

Application server... "UBSDEV"

Network address...... "10.22.6.68"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4v"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 11

Shortdump setting.... "full"

Database server... "UBSDEV"

Database type..... "ORACLE"

Database name..... "UBD"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Apr 2 2006 21:14:52"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "OCI_101 "

Patch level. 52

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "SunOS 5.9, SunOS 5.10"

Memory consumption

Roll.... 1117168

EM...... 0

Heap.... 0

Page.... 93315072

MM Used. 638120

MM Free. 458608

-

-


-

-


User and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Program............. "RSORAT4M"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-

-


-

-


Information on where terminated

Termination occurred in the ABAP program "RSORAT4M" - in "AKT_DAY_HIST2".

The main program was "RSORAT4M ".

In the source code you have the termination point in line 163

of the (Include) program "RSORAT4M".

The program "RSORAT4M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 06004902

The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"

occurred in

procedure "AKT_DAY_HIST2" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "RSORAT4M "; its source code begins in line

161 of the (Include program "RSORAT4M ".

-

-


-

-


Source Code Extract

-

-


Line

SourceCde

-

-


133

134

REFRESH HIST2_DAY.

135

CLEAR HIST2_DAY.

136

137

HIST2_DAY-SIZE = TD110-TSSI.

138

HIST2_DAY-FREE = TD110-TSFR.

139

HIST2_DAY-USED = 100 - TD110-TSFRP.

140

HIST2_DAY-TABLES = TD110-TANO.

141

HIST2_DAY-INDICES = TD110-TINO.

142

HIST2_DAY-TSIZE = TD110-TASI.

143

HIST2_DAY-ISIZE = TD110-TISI.

144

145

  • PERFORM new_analysis_db.

146

HIST2_DAY-DATE = DATE.

147

HIST2_DAY-TIME = TIME.

148

APPEND HIST2_DAY.

149

ENDFORM.

150

*----

-


Beschaffung neuer Analyse-Daten für Historien <<<

151

152

*----

-


Historie, Tage >>>

153

FORM DELETE_AKT_DAY_HIST2.

154

DATA: FLAG VALUE ' '.

155

LOOP AT HIST2.

156

IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.

157

ENDLOOP.

158

IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.

159

ENDFORM.

160

161

FORM AKT_DAY_HIST2. " Aktualisiere Tage-Historie

162

PERFORM PREPARE_MONIKEY USING 36. " Lese Historie

>>>>>

IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.

164

IF SY-SUBRC <> 0.

165

REFRESH HIST2. CLEAR HIST2.

166

PERFORM LOGBUCH_INIT USING 1.

167

PERFORM TRANSFORM_ALL_HISTORIES. " Strukturaenderung fuer Dynami

168

PERFORM PREPARE_MONIKEY USING 36. " Lese Historie

169

IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.

170

ENDIF.

171

READ TABLE HIST2 INDEX 1.

172

IF SY-SUBRC <> 0.

173

REFRESH HIST2. CLEAR HIST2.

174

PERFORM LOGBUCH_INIT USING 1.

175

ENDIF.

176

PERFORM DELETE_AKT_DAY_HIST2. " Delete aktuellen Tag

177

LOOP AT HIST2_DAY. " Füge neue Analyse an

178

MOVE-CORRESPONDING HIST2_DAY TO HIST2.

179

APPEND HIST2.

180

ENDLOOP.

181

ADD 1 TO LOGBUCH-ANZDAYS.

182

MOVE DATE TO LOGBUCH-LASTDAY.

-

-


-

-


Contents of system fields

-

-


Name

Val.

-

-


SY-SUBRC

0

SY-INDEX

0

SY-TABIX

1

SY-DBCNT

0

SY-FDPOS

0

SY-LSIND

0

SY-PAGNO

0

SY-LINNO

1

SY-COLNO

1

SY-PFKEY

SY-UCOMM

SY-TITLE

SY-MSGTY

SY-MSGID

SY-MSGNO

000

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO

0

SY-DATUM

20071224

SY-UZEIT

070256

SY-XPROG

SAPMSSY0

SY-XFORM

NEW-LINE

-

-


-

-


Active Calls/Events

-

-


No. Ty. Program Include Line

Name

-

-


2 FORM RSORAT4M RSORAT4M 163

AKT_DAY_HIST2

1 EVENT RSORAT4M RSORAT4M 73

END-OF-SELECTION

-

-


-

-


Chosen variables

-

-


Name

Val.

-

-


No. 2 Ty. FORM

Name AKT_DAY_HIST2

-

-


SCREEN

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

%_DUMMY$$

0000

0000

2222

0000

MONIKEY

--UBD days h/2

0000000000000000000000

0000000000000000000000

2254422222667722226232

DD52400000419300008F20

MONI

DB--UBD days h/2 ## ##################################################################

00000000000000000000000000000F0083300C019880423CCCCBA185073210552E8C0334266086A470B60061642777

00000000000000000000000000000F1204000802DCF80B619C242588C81881810C0A70020645DC07BF1AFE070ECE1C

4422544222226677222262320022800003300001090100EE1161721CA580CAFEA65BC607333BC23214789666B6D8BC

42DD52400000419300008F20000076120120000F291C430000062325261E520B6388C203600303CA0830014245D093

MONI-CLUSTR

8912646

08

07

OBJ3

0000000000000000000000000000000

0000000000000000000000000000000

2222222222222222222222222222222

0000000000000000000000000000000

OBJ4[]

Table[initial]

HIST2[]

Table[initial]

SY-SUBRC

0

0000

0000

HIST2

00000000000000######################

000000000000000000000000000000000000

000000000000000000000000000000000000

333333333333330000000000000000000000

00000000000000000C000C000000000C000C

S2

0

0

2

0

KBYTES

0.0.0.0.0.0.0.1.

00000000

0000000C

-

-


No. 1 Ty. EVENT

Name END-OF-SELECTION

-

-


TSN

000000000000000

000000000000000

222222222222222

000000000000000

TYP

00000000000000000

00000000000000000

22222222222222222

00000000000000000

S3

0

0

2

0

LOGBUCH-LASTDAY

20070315

00000000

00000000

33333333

20070315

DATE

20071224

00000000

00000000

33333333

20071224

SY-REPID

RSORAT4M

0000000000000000000000000000000000000000

0000000000000000000000000000000000000000

5545453422222222222222222222222222222222

23F2144D00000000000000000000000000000000

S5

0

0

2

0

S7

0

0

2

0

ROOT

000000000000000000000000000000000000000000000000000000000000000000000000000000000

000000000000000000000000000000000000000000000000000000000000000000000000000000000

222222222222222222222222222222222222222222222222222222222222222222222222222222222

000000000000000000000000000000000000000000000000000000000000000000000000000000000

SEG_TYPE

00000000000000000

00000000000000000

22222222222222222

00000000000000000

S4

0

0

2

0

-

-


-

-


Internal notes

The termination was triggered in function "CheckSimpleComponent"

of the SAP kernel, in line 1183 of the module

"//bas/700_REL/src/krn/runt/abconne.c#16".

The internal operation just processed is "IMPO".

Internal mode was started at 20071224070256.

-

-


-

-


Active Calls in SAP Kernel

-

-


Lines of C Stack in Kernel (Structure Differs on Each Platform)

-

-


DoStack2 ( 0x105c65dc0, 0xffffffff7fff9900, 0x1004ffecc, 0x0, 0x20, 0x10315f010 ), at 0x1004ff

CTrcStack2 ( 0x105c65dc0, 0x0, 0x18800, 0x1031a4d20, 0x100b21370, 0x10315f010 ), at 0x1004ffa6

__1cQrabax_CStackSave6F_v_ ( 0x103385400, 0x3385400, 0x103a0e490, 0x1021a9af0, 0x100000000, 0x

ab_rabax ( 0x100000000, 0x31a4c00, 0x103a0d000, 0x3a0d000, 0x2000, 0x0 ), at 0x100b21370

__1cUCheckSimpleComponent6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kCkL6kpknHAB_DATA_kI9D9D_i_ ( 0xf

__1cRConneCmpCheckList6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kppnMImportOpHead_kLpknHAB_DATA_kpk9

__1cNConneCmpCheck6FkpnICONNE_RD_pknHAB_DATA_kpnQDESCRIPTION_CNTL_ppnMImportOpHead_kLkpLII_i_

__1cMimport_check6FpnICONNE_RD_ppnMImportOpHead_kpCC_i_ ( 0xffffffff7fffa9a8, 0xffffffff7fffbb

__1cLab_connread6FIpnLIMPORT_INFO_kpkHpnHAB_DATA_pFpHLp6ppv_ipFppCpLInJEXPO_MODE__i_i_ ( 0xfff

__1cLexpo_import6F_v_ ( 0x0, 0xfffffffe324a90a4, 0xfffffffe324a90ac, 0x105be9e84, 0x0, 0x105ce

__1cIab_jimpo6F_v_ ( 0x100000000, 0x5c66400, 0x1, 0x0, 0x0, 0x94 ), at 0x1009d7f64

__1cIab_extri6F_i_ ( 0x100000000, 0x5cea400, 0x230, 0x1, 0x0, 0x46 ), at 0x1006f9298

__1cJab_xevent6FpkH_i_ ( 0xfffffffe324a9fe8, 0xfffffffe324a7398, 0x2ac, 0x0, 0x4c, 0x105c6648

__1cIab_trigg6F_i_ ( 0x105bea340, 0x105c69588, 0x10093cc48, 0x20, 0x215fc00, 0x0 ), at 0x1009

ab_run ( 0x1062f8288, 0x105c69000, 0x1021b23fc, 0x0, 0x105c6647c, 0x0 ), at 0x100b9346c

dynpmcal ( 0x106305708, 0x6, 0xc, 0x1035867c8, 0x100589628, 0x1031a4d14 ), at 0x100581e1c

dynppai0 ( 0x106305708, 0x106306d14, 0x0, 0x1031a4d78, 0x0, 0x105c86004 ), at 0x10057f120

dynprctl ( 0x106305708, 0x0, 0x103199024, 0x1300, 0x1, 0x128c ), at 0x10057d764

dynpen00 ( 0x0, 0x106305708, 0x106305708, 0x0, 0x106305708, 0x102a5fc00 ), at 0x100579c64

TskhLoop ( 0x0, 0xb, 0xffffffff6f408530, 0x0, 0x100288854, 0x0 ), at 0x10028f248

ThStart ( 0x1, 0x280800, 0x100280800, 0x100000000, 0x1, 0x10319a0c0 ), at 0x1002815f4

DpMain ( 0x37e6800, 0x3197400, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001b2e8c

-

-


-

-


List of ABAP programs affected

-

-


Index

Typ

Program

Group

Date

Time

Size

Lang.

-

-


0

Prg

RSORAT4M

0

21.03.2007

19:50:50

98304

E

1

Prg

SAPMSSY0

1

21.03.2007

19:51:33

90112

E

2

Prg

SAPMSSYD

1

21.03.2007

19:51:17

21504

E

3

Prg

SAPFSYSCALLS

1

09.09.2004

14:18:32

11264

E

4

Prg

RSDBRUNT

0

21.03.2007

19:50:43

254976

E

5

Typ

RSSCR

0

30.03.2005

10:21:45

5120

6

Prg

RSDBSPBL

0

30.03.2005

10:21:58

72704

E

7

Prg

SAPDB__S

0

30.03.2005

10:22:01

19456

E

8

Prg

RSDBSPMC

0

21.03.2007

19:28:01

79872

E

9

Typ

DDSHDESCR

0

03.09.1997

03:05:16

4096

10

Typ

SPPARAMS

0

07.05.1997

13:10:38

2048

11

Typ

SPPARAMS

0

07.05.1997

13:10:38

2048

12

Prg

SAPLSABE

12

09.09.2004

14:18:36

13312

E

13

Prg

SAPLSECU

13

27.03.2007

17:41:57

87040

E

14

Typ

RSSUBINFO

0

14.10.1999

22:01:03

3072

15

Prg

SAPLSTUP

15

08.03.2005

19:04:31

74752

E

16

Prg

SAPLCNDP

16

21.03.2007

16:17:37

193536

E

17

Prg

SAPLSCNT

17

18.02.2005

14:16:06

30720

E

18

Prg

SAPSHDTV

17

05.01.2005

16:26:16

36864

E

19

Prg

SAPFGUICNTL

1

18.02.2005

14:15:08

24576

E

20

Prg

SAPLOLEA

20

05.07.2005

13:10:18

96256

E

21

Prg

SAPLSGUI

21

21.03.2007

19:51:33

82944

E

22

Prg

SAPLSTTM

22

05.07.2005

13:10:18

69632

E

23

Prg

SAPLSBDC

23

05.07.2005

13:10:18

44032

E

24

Prg

SAPLSFES

24

27.03.2007

17:42:13

257024

E

25

Prg

SAPLTHFB

25

27.03.2007

17:38:01

392192

E

26

Typ

WPINFO

0

26.02.1999

14:49:01

6144

27

Prg

SAPLURFC

27

15.06.2005

11:39:01

22528

E

28

Prg

SAPLSPLUGIN

28

09.09.2004

14:18:36

8192

E

29

Typ

SWCBCONT

0

15.11.2000

17:55:11

3072

30

Typ

OLE_VERBS

0

04.04.1995

16:02:20

2048

31

Typ

OLE_PA

0

04.04.1995

16:02:19

2048

32

Typ

MONI

0

31.03.2004

16:41:21

5120

33

Prg

CX_SY_IMPORT_MISMATCH_ERROR===CP

33

05.07.2005

13:10:16

10240

E

34

Typ

SCX_SRCPOS

0

18.05.2004

14:07:11

2048

35

Prg

CX_DYNAMIC_CHECK==============CP

35

05.07.2005

13:10:16

10240

E

36

Prg

CX_ROOT=======================CP

36

05.07.2005

13:10:16

11264

E

37

Prg

CX_NO_CHECK===================CP

37

05.07.2005

13:10:16

10240

E

38

Prg

CX_SY_NO_HANDLER==============CP

38

05.07.2005

13:10:16

10240

E

39

Typ

SYST

0

09.09.2004

14:18:12

31744

-

-


-

-


Directory of Application Tables

-

-


Name Date Time Lngth

Val.

-

-


Program RSORAT4M

-

-


SYST 09.09.2004 14:18:12 00004612

00000x00010000000000000000000

MONI . . : : 00002944

DB--UBD days h/2 00 x0087######00#0####

-

-


-

-


ABAP Control Blocks (CONT)

-

-


Index

Name

Fl

PAR0

PAR1

PAR2

PAR3

PAR4

PAR5

PAR6

Source Code

Line

-

-


1841

BRAX

01

FFF2

RSORAT4M

157

1842

comp

00

0242

C000

00A2

RSORAT4M

158

1844

BRAF

05

0005

RSORAT4M

158

1845

ccqi

4C

0000

0000

2610

0001

0000

0000

2610

RSORAT4M

158

1849

ENDF

00

0000

RSORAT4M

159

1850


00

0000

RSORAT4M

159

1851

PERP

00

0000

RSORAT4M

161

1852

perf

00

000C

RSORAT4M

162

1853

PERP

80

0001

RSORAT4M

162

1854

PERP

80

00CC

RSORAT4M

162

1855

IMPO

00

0001

007B

007A

010C

0000

00EA

0000

RSORAT4M

163

1859

PAR2

06

0000

00EB

009B

RSORAT4M

163

>>>>>

IMPO

07

0000

0000

0000

0000

0000

0000

0000

RSORAT4M

163

1865

cmpr

00

00CA

00F8

0000

RSORAT4M

164

1867

BRAF

05

0016

RSORAT4M

164

1868

REFR

00

0000

009B

0000

RSORAT4M

165

1870

CLEA

00

009C

RSORAT4M

165

1871

perf

00

0035

RSORAT4M

166

1872

PERP

80

0001

RSORAT4M

166

1873

PERP

80

0006

RSORAT4M

166

-

-


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Please apply the following correction manually.

1. Go to transaction ST03N

2. Change user from 'Administrator' to 'Expert Mode'.

3. Go to Collector and performance analysis -> Performance database

-> Monitoring database -> Contents

4. Search where further info contains the string "h/2"

like the following monikeys:

- 'days h/2'

- 'weeks h/2'

- 'months h/2'

5. Double click on each, so that they become red and show ** delete

6. Finally SAVE

This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.

-


How can I identify the monikey that has to be deleted?

When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:

"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".

To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or

'tabgrowth 2'...

You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.

997535 DB02: Problems with History Data.

Award points if helpful.

Thanks,

Tanuj