SAP instance Slow and trace file generates below errors : DiagOConvert...

[Former Member]

Hello,

please help to resolve the problem bellow :

SAP informations :

- SAP ECC 6.0

- ORACLE : 10.2.0.4.0

- Kernel release : 700

Trace file content :

*** ERROR => platform : WINDOWS/NT [diagsrv.c 842]

*** ERROR => gui version : 710 [diagsrv.c 851]

*** ERROR => gui patchlevel: 12 [diagsrv.c

*** ERROR => transaction : SP01 [diagsrv.c 867]

*** ERROR => user : SAPSERVE [diagsrv.c 881]

*** ERROR => display : FRBOUD083 [diagsrv.c 887]

*** ERROR => DiagOConvert: input and output buffer overlap [diagconv.c 1146]

+0) 0x400000000149b6a8 CTrcStack2 + 0x1d8 [dw.sapP05_DVEBMGS21]+

+1) 0x400000000149b4c0 CTrcStack + 0x18 [dw.sapP05_DVEBMGS21]+

+2) 0x40000000015d5080 DiagOConvert + 0x1e0 [dw.sapP05_DVEBMGS21]+

+3) 0x40000000015d7050 DiagoString0 + 0xf0 [dw.sapP05_DVEBMGS21]+

+4) 0x400000000161e740 DiagoCurrentCodepage + 0x2c0 [dw.sapP05_DVEBMGS21]+

+5) 0x4000000001601490 diagoutput + 0xb50 [dw.sapP05_DVEBMGS21]+

+6) 0x40000000016003fc diagmout + 0x1cc [dw.sapP05_DVEBMGS21]+

+7) 0x4000000001620f20 diagmsgo + 0x638 [dw.sapP05_DVEBMGS21]+

+8) 0x4000000001508728 dytrcexit + 0x648 [dw.sapP05_DVEBMGS21]+

+9) 0x4000000001507a30 dypex00 + 0x858 [dw.sapP05_DVEBMGS21]+

+10) 0x4000000001513498 dynpoutf + 0x450 [dw.sapP05_DVEBMGS21]+

+11) 0x400000000150a464 dynprctl + 0x61c [dw.sapP05_DVEBMGS21]+

+12) 0x4000000001504554 dynpen00 + 0x1f04 [dw.sapP05_DVEBMGS21]+

+13) 0x400000000128e9c8 Thdynpen00 + 0xf08 [dw.sapP05_DVEBMGS21]+

+14) 0x400000000128d1a8 TskhLoop + 0x5980 [dw.sapP05_DVEBMGS21]+

+15) 0x4000000001281e44 ThStart + 0x214 [dw.sapP05_DVEBMGS21]+

+16) 0x40000000011c8648 DpMain + 0x410 [dw.sapP05_DVEBMGS21]+

+17) 0x40000000011c5c0c nlsui_main + 0x14 [dw.sapP05_DVEBMGS21]+

+18) 0x40000000011c5bd4 main + 0x3c [dw.sapP05_DVEBMGS21]+

+19) 0xc00000000000b7a8 $START$ + 0xa0 [/usr/lib/pa20_64/dld.sl]+

Thank you.

[JPReyes]

Read,

SAP Note 1112768 - error trace: DiagOConvert input and output buffer ...

Regards

Juan

[Former Member]

first of all, Than you for your answer,

Yes i'v already seen thta note, but what they propose exactelly as aplicative solution by this text :

Solution

By applying a kernel patch, the trace output is enhanced with the information of the callpoint so that the cause of the problem can be analyzed faster.

The error traces were issued with the print view of texts. The problem is solved with a kernel patch.

The error trace output now works at trace levels higher than 1 only.

[former_member185031]

this error we were also facing on the Kernel Patch 144 if i remeber correctly. But after the upgrade of Kernel patch this error message has been resolved

Regards,

Subhash

[JPReyes]

Upgrade your kernel.

Regards

Juan