Upgrade SolMan 7.2 SP5 - Error in MAIN_SHDRUN/PARDIST_SHD - RDDGENBB_x - COMPUTE_DBC_OVERFLOW

[former_member292138]

Hi all!

We are upgrading to SolMan 7.2 SP5 on a sandbox system.

In phase MAIN_SHDRUN/PARDIST_SHD of SUM we got dumps in batch jobs RDDGENBB_x while building shadow instance.

Error in ST22 is COMPUTE_DBC_OVERFLOW. It looks like one field (TTAB-POSNR) is too small.

Any ideas? I will attach dump below message...

Regards

Peter Meyer

Dump:

************************** Batch Job Info ***************************

Batch Job Name RDDGENBB_0
Batch Job ID 09003300
Batch Job Work Process ID 7
Batch Job Host Name sapsmxci_SMX_04
Batch Job Status A
Batch Job Started by User DDIC
Batch Job End Date 20170531
Batch Job End Time 090256

************************** Batch Job Log ****************************

20170531 090033 Job started
20170531 090033 Step 001 started (program RDDGENBB, variant SAP_PARDISTV, user ID DDIC)
20170531 090033 Start of distribution: 09:00:33
20170531 090256 Internal session terminated with a runtime error (see ST22)
20170531 090256 Job cancelled

*************************** System Log ******************************

Instance sapsmxci_SMX_04
Work Process ID 007
Work Process Type BTC
Client 000
User Name DDIC
Date 31.05.2017
Time 09:02:56

Severity Icon @5C\QVery High Priority@
Message Text Run-time error "COMPUTE_BCD_OVERFLOW" occurred

Severity Icon @SR\QInformation@
Message Text > Short dump "170531 090256 sapsmxci_SMX_04 DDIC " created.

Severity Icon @5C\QVery High Priority@
Message Text Transaction Canceled 00 671 ( COMPUTE_BCD_OVERFLOW 20170531090256sapsmxci_SMX_04 DDIC 000 )

************************** ABAP Dump Content ************************

ABAP Short Dump Header Data
---------------------------
Short Dump Category: ABAP Programming Error
Runtime Error: COMPUTE_BCD_OVERFLOW
ABAP Program: FUGR SDNT
ABAP Main Program: SAPLSDNT
ABAP Package: SDIC
Software Component: SAP_BASIS
Application Component: BC-DWB-DIC-AC Activation Program, Conversion Program, DB Utility, MC, SPDD

Where did the dump occur
------------------------
Frame Program: RDDDISTY
ABAP Program: SAPLSDNT
ABAP Include: LSDNTU12
Line Number: 60
Additional Info: DD_PUT_TATAF

Source Code Extract
-------------------
1 function dd_put_tataf.
2 *"----------------------------------------------------------------------
3 *"*"Lokale Schnittstelle:
4 *" IMPORTING
5 *" VALUE(ONLY_TEST) DEFAULT SPACE
6 *" VALUE(TABNAME) LIKE TATAF-TABNAME
7 *" VALUE(REPLACE) DEFAULT SPACE
8 *" VALUE(TAKE_ALL_ROWS) TYPE ABAP_BOOL DEFAULT ABAP_FALSE
9 *" TABLES
10 *" STATEMENTS
11 *"----------------------------------------------------------------------
12
13 * PW241193 condense eingebaut, wegen 8KB-Grenze in DSQL
14 * KUGL220694: isolieren der Entfernung von Kommentaren und der
15 * EXEC-SQL/ENDEXEC-Klammerung
16
17 data: in_exec.
18 data: begin of ttab occurs 100. "für array_insert.
19 include structure tataf.
20 data: end of ttab.
21
22 * temporare Statement-Tabelle für Aufruf der Statement-Konvertierung
23 data: begin of raw_sql_tab occurs 200,
24 line(80),
25 end of raw_sql_tab.
26
27
28 ttab-tabname = tabname.
29
30
31
32 * Bestimme erste freie Position in Tataf
33 * unbedingt notwendig, da bei duprec im array-insert -> Abbruch
34 * AW011194 Nicht nötig im Replacemodus, da alter Inhalt gelöscht wird.
35 if replace eq space.
36 ttab-posnr = 0.
37 select max( posnr )
38 into ttab-posnr
39 from tataf
40 where tabname = tabname.
41 * PERFORM MAX_TATAF_POS(SDDSQL01) USING TABNAME TTAB-POSNR.
42 endif.
43
44 *KUGL220694:
45 *Fkt.baustein entfernt Kommentare und die EXEC-SQL/ENDEXEC-Klammerung
46 *und trennt die Statements durch Semikolons.
47 call function 'DD_ABAP_TO_EXEC_CNV'
48 exporting
49 upgrade = 'X'
50 take_all_rows = take_all_rows
51 tables
52 statements_in = statements
53 statements_out = raw_sql_tab
54 exceptions
55 conversion_error = 01.
56
57 *NOW LOOP OVER PURE STATEMENTS AND COPY THEM TO TTAB.
58 loop at raw_sql_tab.
59 ttab-prtext = raw_sql_tab.
-----> 60 add 1 to ttab-posnr.
61 append ttab.
62 endloop.
63
64
65
66 * Kopiere SQLs aus Statements in TTAB
67 * LOOP AT STATEMENTS.
68 * IF STATEMENTS CA '"'.
69 * CLEAR TTAB-PRTEXT. "Weil sonst alles hinter SY-FDPOS stehen bleibt
70 * WRITE STATEMENTS TO TTAB-PRTEXT(SY-FDPOS). "Kommentar entfernen
71 * ELSE.
72 * TTAB-PRTEXT = STATEMENTS.
73 * ENDIF.
74 * IF TTAB-PRTEXT(1) <> '*' AND
75 * TTAB-PRTEXT <> SPACE. "Zeilenkommentar überlesen
76 * IF IN_EXEC = 'X'.
77 * IF TTAB-PRTEXT CS 'ENDEXEC'.
78 * IN_EXEC = SPACE.
79 * TTAB-PRTEXT = ';'. "mehrere Stmts durch ';' trennen
80 * ENDIF.
81 * ADD 1 TO TTAB-POSNR.
82 * PW241193 condense, wegen 8KB-Grenze in DSQL
83 * CONDENSE TTAB-PRTEXT.
84 * APPEND TTAB.
85 * ELSEIF TTAB-PRTEXT CP '*EXEC *SQL*'.
86 * IN_EXEC = 'X'.
87 * ENDIF.
88 * ENDIF.
89 * ENDLOOP.
90
91 * Mache Array Insert in die TATAF.
92 if only_test = space.
93
94 if replace ne space.
95 * Im Replacemodus wird der alte Inhalt überschrieben.
96 delete from tataf where tabname = tabname.
97 endif.
98
99 insert tataf from table ttab.
100 else.
101 loop at ttab.
102 write: / ttab-tabname, (4) ttab-posnr, (60) ttab-prtext.
103 endloop.
104 endif.
105 endfunction.

Short text
----------
Overflow during the arithmetical operation (type P) in program "SAPLSDNT".

What happened?
--------------
Error in the ABAP Application Program

The current ABAP program "SAPLSDNT" 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_ARITHMETIC_OVERFLOW', was not caught in
procedure "DD_PUT_TATAF" "(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:An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:

1. The result field of type P is too small for the result.

2. The result or a intermediate result has more than 31 decimal places.

How to correct the error
------------------------
The result field must be enlarged, if this is still possible. It may
also be possible to break up the current process into subprocesses so
that only smaller values occur.

There may already be a solution to the error in the SAP notes system.
If you have access to the SAP notes system first try searching with the
following keywords:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this position)
"SAPLSDNT" or "LSDNTU12"
"DD_PUT_TATAF"

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
"DD_PUT_TATAF" "(FUNCTION)", 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..... 702
SAP Basis Level. 0016

Application server... "sapsmxci"
Network address...... "10.16.65.43"
Operating system..... "Linux"
Release.............. "3.0.101-71-default"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 7
Shortdump setting.... "full"

Database server... "sapsmxci"
Database type..... "SYBASE"
Database name..... "SMX"
Database user ID.. "SAPSR3"

Terminal.......... "???"

Char.set.... "C"

SAP kernel....... 745
created (date)... "Jan 23 2017 16:12:28"
create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr170123"
Database version. "Sybase ASE 16.0.02.04"

Patch level. 400
Patch text.. "???"

Database............. "15.7, 16.0"
SAP database version. 745
Operating system..... "Linux"

Memory consumption
Roll.... 0
EM...... 0
Heap.... 66364256
Page.... 32768
MM Used. 57386160
MM Free. 3424880

User and Transaction
--------------------
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction.........
Transaction ID...... "592E2FC369F3A2EAE10000000A1040B8"

EPP Whole Context ID.... "00000144004900530054005F00520045"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0

Program............. "SAPLSDNT"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"

Information on where terminated
-------------------------------
Termination occurred in the ABAP program "SAPLSDNT" - in "DD_PUT_TATAF".
The main program was "RDDDISTY".

In the source code you have the termination point in line 60
of the (Include) program "LSDNTU12".
The program "SAPLSDNT" was started as a background job.
Job Name....... "RDDGENBB_0"
Job Initiator.. "DDIC"
Job Number..... 09003300
The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW" occurred in
procedure "DD_PUT_TATAF" "(FUNCTION)", but it was neither handled locally nor declared
in the RAISING clause of its signature.

The procedure is in program "SAPLSDNT"; its source code begins in line
1 of the (Include program "LSDNTU12".

Internal notes
--------------
The termination was triggered in function "ab_bcdArithmeticOverflow"
of the SAP kernel, in line 191 of the module "//bas/745_STACK/src/krn/abap/runt/abcalc.c#2".
The internal operation just processed is "CALC".
Internal mode was started at 20170531090033.

Active Calls in SAP Kernel
--------------------------
Lines of C Stack in Kernel (Structure Differs on Each Platform)
dw.sapSMX_DVEBMGS04_SHD[S](LinStackBacktrace+0x8c)[0x661f09]
dw.sapSMX_DVEBMGS04_SHD[S](LinStack+0x35)[0x665f58]
dw.sapSMX_DVEBMGS04_SHD[S](CTrcStack2+0x4e)[0x661cc7]
dw.sapSMX_DVEBMGS04_SHD[S](rabax_CStackSave()+0xcf)[0x8388e5]
dw.sapSMX_DVEBMGS04_SHD[S](ab_rabax+0x55bd)[0x8430d7]
dw.sapSMX_DVEBMGS04_SHD[S](ab_bcdArithmeticOverflow(int, CONT*)+0xab)[0x1ed7d07]
dw.sapSMX_DVEBMGS04_SHD[S](AbCalc<CalD<TraitsD> >::loop()+0x1440)[0x1e69650]
dw.sapSMX_DVEBMGS04_SHD[S](AbCalc<CalD<TraitsD> >::run()+0x43)[0x1e6b673]
dw.sapSMX_DVEBMGS04_SHD[S](ab_extri()+0x197)[0x1b8a057]
dw.sapSMX_DVEBMGS04_SHD[S](ab_xevent(char16_t const*)+0x32)[0x1bca3f2]
dw.sapSMX_DVEBMGS04_SHD[S](ab_trigg()+0x4c)[0x1e9058c]
dw.sapSMX_DVEBMGS04_SHD[S](ab_run+0x119)[0x1eb8489]
dw.sapSMX_DVEBMGS04_SHD[S](dynpmcal(DINFDUMY*, STPDUMMY*)+0x514)[0x1dea9d4]
dw.sapSMX_DVEBMGS04_SHD[S](dynppai0(DINFDUMY*)+0x345)[0x1deb3a5]
dw.sapSMX_DVEBMGS04_SHD[S](dynprctl(DINFDUMY*)+0x20c)[0x1dece0c]
dw.sapSMX_DVEBMGS04_SHD[S](dynpen00+0x4bb)[0x1dddbab]
dw.sapSMX_DVEBMGS04_SHD[S](ThrtCallAbapVm+0xc0)[0x1dba780]
dw.sapSMX_DVEBMGS04_SHD[S](ThHandleRequest(REQUEST_BUF*, unsigned char, unsigned char)+0x1a7)[0x1d7e357]
dw.sapSMX_DVEBMGS04_SHD[S](TskhLoop()+0xa2)[0x1b73c62]
dw.sapSMX_DVEBMGS04_SHD[S](ThStart()+0x26e)[0x4ebbf0]
dw.sapSMX_DVEBMGS04_SHD[S](DpMain+0x36c)[0x1d1696c]
libc.so.6[S](__libc_start_main+0xe6)[0x7ffff0ab7c36]

Content of System Fields
------------------------
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 100000
SY-DBCNT 0
SY-FDPOS 100
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-TITLE 3.0 Comparator
SY-MSGTY E
SY-MSGID DA
SY-MSGNO 300
SY-MSGV1 V_CDC_GRP_RES_C
SY-MODNO 0
SY-DATUM 20170531
SY-UZEIT 090038
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET

ABAP Call Stack
---------------
3 'Event Type FUNCTION' in SAPLSDNT LSDNTU12, Line Number 60

2 'Event Type FUNCTION' in SAPLSDSB LSDSBU04, Line Number 711

1 'Event Type EVENT' in RDDDISTY RDDDISTY, Line Number 22

Content of Chosen Variables
---------------------------

Chosen Variables of Program SAPLSDNT Include LSDNTU12
Line Number 60 Event: FUNCTION DD_PUT_TATAF (Index 3 )
------------------------------------------------------

Name: ONLY_TEST Values:

Name: REPLACE Value: X

Name: TABNAME Value: V_CDC_GRP_RES_C

Name: TAKE_ALL_ROWS Value: X

Name: STATEMENTS[] Values:
" >DELVIEWV_CDC_GRP_RES_C
EXEC SQL.
DROP VIEW "V_CDC_GRP_RES_C"
ENDEXEC.
" <DELVIEWV_CDC_GRP_RES_C

Name: CLNT_FIXED_LENGTH Value: 000003

Name: TTAB-POSNR Value: 99999

Chosen Variables of Program SAPLSDSB Include LSDSBU04
Line Number 711 Event: FUNCTION DD_MASS_DIST (Index 2 )
-------------------------------------------------------

Name: DBCHECK_LEVEL Values:

Name: DBSYS Value: SYBASE

Name: DBSYS_SEC Value: SYBASE

Name: LOGNAME Values:

Name: LONGPROT Value: X

Name: MARK_DELETED_FIELDS Values:

Name: MARK_LONG_OPERATIONS Values:

Name: MODUS Value: I

Name: NO_EXISTS_CHECK Values:

Name: PARALLEL Value: X

Name: SHADOW_UPGRADE Value: X

Name: SUBRC Value: 0

Name: SELNAMES[] Value: Table[initial]

Name: TAKE_ALL_ROWS Value: X

Name: SYST-REPID Value: SAPLSDSB

Name: DROP_VIEWS Value: 16

Name: PSTATEMENTS1[] Value: Table[initial]

Name: PSTATEMENTS Value: ENDEXEC.

Name: DELETE_POOL Value: 7

Name: INFO-DDLSINFO-IS_DDL_VIEW Value: X

Name: ABAP_TRUE Value: X

Name: %_SPACE Values:

Name: TESTFLAG Values:

Name: X030L_NEW-TABNAME Value: V_CDC_GRP_RES_C

Name: PSTATEMENTS[] Values:

Chosen Variables of Program RDDDISTY Include RDDDISTY
Line Number 22 Event: EVENT START-OF-SELECTION (Index 1 )
---------------------------------------------------------

Name: SY-LDBPG Value: SAPDB__S

Name: %_DUMMY$$ Values:

Name: SY-REPID Value: RDDDISTY

Name: DBCHECK Values:

Name: %_SSCR[] Values:
LONGPROT䉀#P ##CCHAR
####
##
LOGNAME 䉁#P x#CCHARTRBAT-LOGNAME
##ð# X
##
MODUS 䉂#P ##CCHAR
####
##
PARALLEL䉃#P ##CCHAR
####
##
NOEXCHK 䉄#P ##CCHAR
####
##

Name: LOGNAME Values:

Name: %_SSCR Value: SHADOWUP䉈#P ##CCHAR #### ##

Name: LONGPROT Value: X

Name: MARK_DFI Values:

Name: MARK_LOP Values:

Name: MODUS Value: I

Name: NOEXCHK Values:

Name: PARALLEL Value: X

Name: SHADOWUP Value: X

Name: SYST-REPID Value: RDDDISTY

Name: SUBRC Value: 0

Application Calls
-----------------
background job RDDGENBB_0 09003300

Application Tables
------------------

Program RDDDISTY
Table SYST 20041216 203111
Content \x0001\0\0\0蚠\x0001镺\x0001\0\0\0\0F\0\0\0\0\0\0\0\0\0d\0
Table SY
Content \x0001\0\0\0蚠\x0001镺\x0001\0\0\0\0F\0\0\0\0\0\0\0\0\0d\0

Program SAPFSDS1
Table TDCLD
Content RE DOKU 40R XX XXLIMUDOCUX (XR3TRPROGX X|

Program SAPLLANG
Table T002
Content ES1EN|

Program SAPFS_SECLOG
Table INDX
Content 000%L%_SeclogExcludedCaller\0\0\0 00000000

Program SAPLSDSB
Table TSYNC
Content V V_CGPL_VRSN_HDR |
Table VSYNC
Content VT005B V_CGPL_VRSN_HDR

Program CONTEXT_X_TR_SYS_PARAMS
Table CONTEXTB
Content 000EBTR_SYS_PARAMS 000006000100000000000000\0\0\0\0
Table TCONT
Content TR_SYS_PARAMS 20170529155254|

Program SAPLSDNT
Table DDXTT
Content V_CDC_GRP_RES_C 挸䊻胕휞频퇌ᠽ骼20170530012738

Program SAPLSDD2
Table DD09L
Content TST05 A0000 P000 SAP
Table DD06L
Content 0000 0000000000000000000 00

Data about occurred ABAP OO exception
-------------------------------------

ABAP OO exception status info
-----------------------------
System Exception: X
Exception: X
Interface: X

Exception: CX_SY_ARITHMETIC_OVERFLOW
Reason: 05
Exception Source Line Info: Program SAPLSDNT Include LSDNTU12 Line number 1
Exception Source Line Info: Program SAPLSDNT Include LSDNTU12 Line number 60

***** End of ABAP Short Data Content *****

****************************** Admin Info ***************************

FUNC 'SUBST_READ_ABAP_DUMP' was used to retrieve ABAP dump content (SY-SAPRL '702').
FUNC 'SUBST_READ_SYSTEM_LOG' was used to retrieve system log entries (SY-SAPRL '702').

[former_member292138]

There is now a note for this issue:

2493557 - SUM upgrade - PARDIST_SHD phase fails in COMPUTE_BCD_OVERFLOW - SAP ASE for Business Suite

[former_member292138]

Hi all!

Sorry for the late answer but I was on Holidays... 🙂

I don´t know if there is a SAP note at the Moment. Our ticket took also "some" time..
We don´t know what SAP did on our System. We asked but there was no answer!

The issue described in note 2071190 but as SAP said just a Workaround exists.

Peter

[ggarcia]

Hi Guys, you have any answer from your OSS message?, I'm facing the same issue.

[sergey_elkin]

Hi guys.

Do you have any news? I faced with same problem/\.

[Former Member]

Hi Peter,

I am facing the same issue as well. May I know did SAP release a SAP Note correction for this?

What was the fix actually?

Thank you.

[Former Member]

Hi guys,

Is there any fix or remedy for this error?

Kindly advise. Thank you.

[former_member258646]

hi All,

I am also facing the same issue any solution for the same.I have raised the OSS also

[Former Member]

Hi Peter,

I opened a ticket 5 days ago, but SAP did not solve the problem yet.

Thanks,

[former_member292138]

Hi!

This is a SAP issue and there is no fix and note existing at the Moment.

We opened a ticket and SAP did something on our System that solved our problem.

So open a ticket!

Peter

[Former Member]

Hello Peter,

I got the same error.

Upgrading Solman 7.1 SP13 to Solman 7.2 SP5.

Linux x Sybase

I did not find any SAP notes about these problem.