- SAP Community
- Products and Technology
- Enterprise Resource Planning
- ERP Q&A
- upgrade to ECC6 SR3 - XPRAS_UPG - job RDDEXECL - d...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
upgrade to ECC6 SR3 - XPRAS_UPG - job RDDEXECL - dump DDIC_TYPE_INCONSISTE
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 05-06-2008 1:03 PM
Hello SAP upgrade gurus,
We are doing upgrade from 4.6C to ERP 2005. In phase XPRAS_UPG there is a problem. Job RDDEXECL was cancelled as follows.
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server r4252 were synchronized
ABAP/4 processor:
Job cancelled
There is a related short dump in ST22 ->
Runtime Errors DDIC_TYPE_INCONSISTENCY
Date and Time 06.05.2008 00:22:20
Short text
Inconsistency in the Dictionary for the structure "BCONT".
What happened?
Error in the SAP kernel.
The current ABAP "ISU_XPRA_LOGNO" program had to be terminated
because the
ABAP processor detected an internal system error.
Table
BCONT seems to be consistent in SE11. I tried Call transaction SE14 as
described in note 211492. -> Extras -> Database Object ->
Check and -> Extras -> Runtime Object -> Check
and there are no inconsistencies.
XPRASUPG.ELG log is here ->
**************************************************
******* LIST OF ERRORS AND RETURN CODES *******
**************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR700XPD.ISA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "22274500")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system
is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status "cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed. You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""22274500""ISA"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR700XPF.ISA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "22274501")
Long text: see above
1AEPU320 See job log"RDDEXECL""22274501""ISA"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
Edited by: Josef Macinka on May 6, 2008 2:15 PM
- SAP Managed Tags:
- SAP enhancement package for SAP ERP
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Runtime Errors DDIC_TYPE_INCONSISTENCY
Date and Time 23.07.2008 18:57:45
Short text
Inconsistency in the Dictionary for the structure "TSTAHTW".
What happened?
Error in the SAP kernel.
The current ABAP "/1BCDWBEN/SAPLSEN0000" program had to be terminated because
the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
There is an internal system error.
eliminated with ABAP/4.
How to correct the error
The internal system error cannot be fixed by ABAP means only.
You may be able to find a solution in the SAP note system. If you have
access to the SAP note system, try searching for the following terms:
"DDIC_TYPE_INCONSISTENCY" " "
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Can you pls paste the full log from ST22, pls
After the correction, the Job RDDEXECL needs to be run manually. To do this, call transaction code sm36 and schedule ABAP program RDDEXECU. This program authomatically reschedule the job RDDEXECL. Please note: RDDEXECU is a program and totally different from Job RDDEXECL.
Then oroceed with upgrade with Repeat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
source kernel is
--------------------
disp+work information
--------------------
kernel release 46D
kernel make variant 46D_EXT
DBMS client library OCI_920__OCI_7_API
DBSL shared library version 46D.00
compiled on AIX 1 5 0056AA8A4C00
compiled for 64 BIT
compile time Apr 12 2007 21:48:30
update level 0
patch number 2318
target kernel is
--------------------
disp+work information
--------------------
kernel release 700
kernel make variant 700_REL
DBMS client library OCI_102 ()
DBSL shared library version 700.08
compiled on AIX 2 5 005DD9CD4C00
compiled for 64 BIT
compilation mode Non-Unicode
compile time Feb 3 2008 20:53:59
update level 0
patch number 146
source id 0.146
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Try to execute the program RDDNEWPP, and see the job scheduled.
Try again.
Regards,
Alfredo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
short dump is here ->
Runtime Errors DDIC_TYPE_INCONSISTENCY
Date and Time 06.05.2008 00:22:20
Short text
Inconsistency in the Dictionary for the structure "BCONT".
What happened?
Error in the SAP kernel.
The current ABAP "ISU_XPRA_STDTFTR" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
There is an internal system error.
eliminated with ABAP/4.
How to correct the error
The internal system error cannot be fixed by ABAP means only.
You may be able to find a solution in the SAP note system. If you have
access to the SAP note system, try searching for the following terms:
"DDIC_TYPE_INCONSISTENCY" " "
"ISU_XPRA_STDTFTR" or "%_CISU25"
" "
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:
"DDIC_TYPE_INCONSISTENCY" " "
"ISU_XPRA_STDTFTR" or "%_CISU25"
" "
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 700
Application server... "r4252"
Network address...... "10.42.1.46"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00CFD3DC4C00"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 14
Shortdump setting.... "full"
Database server... "r4252"
Database type..... "ORACLE"
Database name..... "ISA"
Database user ID.. "SAPR3"
Char.set.... "cs_CZ.ISO8859-2"
SAP kernel....... 700
created (date)... "Feb 3 2008 20:53:59"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 2614224
EM...... 0
Heap.... 7960256
Page.... 40960
MM Used. 10427072
MM Free. 107200
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "481F8B7D629F034BE10080000A2A012E"
Program............. "ISU_XPRA_STDTFTR"
Screen.............. " "
Screen line......... " "
Information on where terminated
The termination occurred during generation of the ABAP/4 program
"ISU_XPRA_STDTFTR".
The termination occurred in line 212
of the source code of program "%_CISU25" (when calling the editor 2120).
The program "ISU_XPRA_STDTFTR" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 00221901
Source Code Extract
Line SourceCde
182 t_eabps TYPE isu25_budbildate_table,
183 END OF isu25_budbilplan_di.
184 TYPES: isu25_ever_table LIKE emigr_ever OCCURS 0.
185 TYPES: isu25_ejvl_table LIKE ejvl OCCURS 0.
186 TYPES: BEGIN OF isu25_budbilplan_di1,
187 eabp LIKE eabp,
188 t_ever TYPE isu25_ever_table,
189 t_eabps TYPE isu25_budbildate_table,
190 t_ejvl TYPE isu25_ejvl_table,
191 END OF isu25_budbilplan_di1.
192
193 TYPES: BEGIN OF isu25_lockset,
194 typ LIKE tfk080f-proid,
195 item TYPE fkloc_locksettype,
196 END OF isu25_lockset.
197 TYPES: isu25_t_lockset TYPE isu25_lockset OCCURS 0.
198
199 *.. Merken alten Abschlagsplan beim Anlegen
200 TYPES: BEGIN OF isu25_bbp_data_in_mem,
201 opbel LIKE eabp-opbel,
202 merklogfkkop LIKE sfkkop OCCURS 0,
203 END OF isu25_bbp_data_in_mem.
204 TYPES: isu25_bbp_data_in_mem_tab TYPE isu25_bbp_data_in_mem OCCURS 0.
205
206 * ITAB der in Fakturierung erzeugten neuen Abschlagspläne
207 TYPES: BEGIN OF isu25_bbp_inv,
208 opbel LIKE fkkop-opbel,
209 tmp_belnr LIKE fkkop-opbel,
210 t_eabp TYPE isu25_eabp_table,
211 t_eabps TYPE isu25_budbildate_table,
>>>>> bbp_obj TYPE isu25_budbilplan,
213 END OF isu25_bbp_inv,
214 isu25_t_bbp_inv TYPE isu25_bbp_inv OCCURS 6.
215
216 * Fehlertabelle fuer fehlende Muß-Felder bei Migration Abschlagsplan
217 TYPES: BEGIN OF isu25_input_error,
218 posnr(3) TYPE n,
219 vtref LIKE eabps-vtref,
220 field LIKE dd03d-fieldname,
221 END OF isu25_input_error,
222 isu25_t_input_error TYPE isu25_input_error OCCURS 0.
223
224 * Device cache
225 TYPES: BEGIN OF isu25_eanl_cache,
226 device LIKE eanlh-anlage,
227 ab LIKE eanlh-ab,
228 bis LIKE eanlh-bis,
229 aklasse LIKE eanlh-aklasse,
230 END OF isu25_eanl_cache.
231
Internal notes
The termination was triggered in function "ab_RxDdicTypeError"
of the SAP kernel, in line 1053 of the module
"//bas/700_REL/src/krn/runt/abucutil.c#3".
The internal operation just processed is " ".
Internal mode was started at 20080506002220.
There is an inconsistency in the DDIC structure "BCONT". This means there is
an error in the corresponding Dictionary runtime object (NAMETAB).
The number of components in the structure (NAMETAB component "fldcnt")
is given as 35. However, when all substructures are resolved, and the
actual total number of components is calculated (recursively), the value
is different.
This error was caused by a change being made to the structure "BCONT" or one
of its substructures, and an error occurring during the subsequent
activation. To find out the exact cause of the error, examine the
runtime object of the structure "BCONT" in the Dictionary.
If the program RSDDCHECK is in your system, you can use it check the
structure "BCONT".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = 2684354560
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x114633fe0
=> Stack address = 0xffffffffffa2960
=> Stack low = 0xffffffffffa2960
=> Stack high = 0xffffffffffff8a0
=> Stack Trace:
AixStack() at 0x1000a24d4
CTrcStack2() at 0x1000a25cc
rabax_CStackSave__Fv() at 0x1000d0c0c
ab_rabax() at 0x1000cd5ec
ab_RxDdicTypeError__FPCcUi() at 0x1007b4e80
FirstLevelChildCnt__FP7sc_type() at 0x1004565cc
UcTypeToTree__FP9UC_BUFFERP7sc_typePUiP7UC_NODEP17UC_CUST_INCL_INFOP18UC_UNSIGNED_TRIPLEP13UC_ALI
UcTypeToFragView__FPP12UC_FRAG_VIEWP17UC_CUST_INCL_INFOP7sc_type() at 0x100453fa4
sc_tparUcFragView__FP7sc_type() at 0x100453dd4
sc_loadflds__FP7sc_type_50_14() at 0x100cf1e28
sc_BaseType__FP7sc_type() at 0x100458258
LeafCnt__FPC14SC_STRUCT_ITEM() at 0x100456eec
FirstLevelChildCnt__FP7sc_type() at 0x100456508
UcTypeToTree__FP9UC_BUFFERP7sc_typePUiP7UC_NODEP17UC_CUST_INCL_INFOP18UC_UNSIGNED_TRIPLEP13UC_ALI
UcTypeToFragView__FPP12UC_FRAG_VIEWP17UC_CUST_INCL_INFOP7sc_type() at 0x100453fa4
sc_tparUcFragView__FP7sc_type() at 0x100453dd4
sc_loadflds__FP7sc_type_50_14() at 0x100cf1e28
sc_BaseType__FP7sc_type() at 0x100458258
UcTypeToTree__FP9UC_BUFFERP7sc_typePUiP7UC_NODEP17UC_CUST_INCL_INFOP18UC_UNSIGNED_TRIPLEP13UC_ALI
UcTypeToTree__FP9UC_BUFFERP7sc_typePUiP7UC_NODEP17UC_CUST_INCL_INFOP18UC_UNSIGNED_TRIPLEP13UC_ALI
UcTypeToFragView__FPP12UC_FRAG_VIEWP17UC_CUST_INCL_INFOP7sc_type() at 0x100453fa4
sc_tparUcFragView__FP7sc_type() at 0x100453dd4
sc_loadflds__FP7sc_type_50_14() at 0x100cf1e28
sc_ddictype__FPCc7HD_BOOLP7SC_INFO() at 0x10122e634
sc_global_type_find__FPCc9NEED_KIND7HD_BOOLT3P7SC_INFO() at 0x100cef608
simple_type_find_1__FPCc9TYPE_MODEPP3ENVP7SC_INFO() at 0x100ceebdc
sc_simple_type_find__FPCc9TYPE_MODEP7SC_INFO() at 0x100ceecd4
sc_ddicflds__FP7sc_type() at 0x10122d1e0
sc_loadflds__FP7sc_type_50_14() at 0x100cf1e0c
sc_ddictype__FPCc7HD_BOOLP7SC_INFO() at 0x10122e634
sc_global_type_find__FPCc9NEED_KIND7HD_BOOLT3P7SC_INFO() at 0x100cef608
simple_type_find_1__FPCc9TYPE_MODEPP3ENVP7SC_INFO() at 0x100ceebdc
sc_simple_type_find__FPCc9TYPE_MODEP7SC_INFO() at 0x100ceecd4
sc_ddicflds__FP7sc_type() at 0x10122d1e0
sc_loadflds__FP7sc_type_50_14() at 0x100cf1e0c
sc_ddictype__FPCc7HD_BOOLP7SC_INFO() at 0x10122e634
sc_global_type_find__FPCc9NEED_KIND7HD_BOOLT3P7SC_INFO() at 0x100cef608
simple_type_find_1__FPCc9TYPE_MODEPP3ENVP7SC_INFO() at 0x100cee47c
sc_complex_type_find__FPCc9TYPE_MODEP7SC_INFO() at 0x100cedd94
sc_ctypid__FPCc9TYPE_MODEUiP7SC_INFO() at 0x100ceca58
sc_typid() at 0x1004768a0
rs_oper_abap4140() at 0x10120acb8
Unknown at 0x101134a74
sc_expan__FUi() at 0x100f953b8
parse__FUiPi() at 0x100fa175c
sc_check() at 0x100f9f934
sc_inclu() at 0x100f9cba0
rs_oper_abap4113() at 0x10120bc74
Unknown at 0x101131e04
sc_expan__FUi() at 0x100f953b8
parse__FUiPi() at 0x100fa175c
sc_check() at 0x100f9f934
sc_inclu() at 0x100f9cba0
rs_oper_abap4113() at 0x10120bc74
Unknown at 0x101131e04
sc_expan__FUi() at 0x100f953b8
parse__FUiPi() at 0x100fa175c
sc_check() at 0x100f9f934
sc_inclu() at 0x100f9cba0
rs_oper_abap2164() at 0x1011ca59c
Unknown at 0x1010afff8
sc_expan__FUi() at 0x100f953b8
parse__FUiPi() at 0x100fa175c
sc_check() at 0x100f9f934
sc_checkStart() at 0x100f9f364
cg_generate() at 0x100aed57c
ab_gabap() at 0x100aea44c
dy_gen_abap() at 0x10082fae0
ab_genprog() at 0x100ae9250
ab_submit() at 0x10154462c
ab_retdynp__Fi() at 0x10081b59c
ab_run() at 0x101544eec
N_ab_run() at 0x10137593c
dynpmcal() at 0x101374730
dynppai0() at 0x1013723a8
dynprctl() at 0x10137b808
dynpen00() at 0x100840df0
Thdynpen00() at 0x1000fa448
TskhLoop() at 0x1000fc338
ThStart() at 0x100116918
DpMain() at 0x1017e5edc
nlsui_main() at 0x1018d29f4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
> There is an inconsistency in the DDIC structure "BCONT". This means there is
> an error in the corresponding Dictionary runtime object (NAMETAB).
>
> The number of components in the structure (NAMETAB component "fldcnt")
> is given as 35. However, when all substructures are resolved, and the
> actual total number of components is calculated (recursively), the value
> is different.
>
> This error was caused by a change being made to the structure "BCONT" or one
> of its substructures, and an error occurring during the subsequent
> activation. To find out the exact cause of the error, examine the
> runtime object of the structure "BCONT" in the Dictionary.
>
> If the program RSDDCHECK is in your system, you can use it check the
> structure "BCONT".
Check Note 595069 - Recursive check of inconsistent DDIC runtime objects
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Here is answer from sap :
Analyse with program RSNTABCONSISTENCY had a special inconsistency:
In table BCONT there is an include structure SI_BCONTU, which does
not exist in the dictionary.
But in the active runtime object of table BCONT this include was
marked as active, and there was an active runtime object of this
include also.
Such an inconsistency must not be.
I could not found any reason for it - this problem is unknow so far.
Probaply it was an error in the delivery.
There are two possible solutions:
1. create or import the dictionary source of this SI include
2. delete the obsolete runtime object of this SI include manually
- XPRAS_UPG running for a long time & SAPup died in between in Enterprise Resource Planning Q&A
- Error during upgrade phase XPRAS_UPG from SAP 4.6C to 6.20 in Enterprise Resource Planning Q&A
- SRM Upgrade in Enterprise Resource Planning Q&A
- Error in XPRAS_UPG Phase in Enterprise Resource Planning Q&A
- Upgrade BW3.1C to BI7.0 error in phase XPRAS_UPG in Enterprise Resource Planning Q&A
| User | Count |
|---|---|
| 91 | |
| 11 | |
| 10 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.