cancel
Showing results for 
Search instead for 
Did you mean: 

DDIC_TYPE_INCONSISTENCY error during/after SAP_BASIS patch load in SPAM

Former Member
0 Kudos

Dear Awesome Gurus,

I'm probably screwed, but I'll post this anyway for a possible solution.

I just build a NW 7.0 (2004s) PI system, Solaris, Oracle 10.2.0.2 system

I was bringing it up to SP15 support stack ABAP.

During the install in SPAM for SAP_BASIS (SAPKB70011 - SAPKB70015) my oraarch logs filled up and also we had a power failure on my PC, so I lost the SPAM that was running in dialogue mode.

I created more room in the oraarch directory, but the DB was not available when I did startsap check, but the CI instance was still up.

So I did a startsap/stopsap and got the DB back up.

But now when I login to SAP GUI, I get this message for just about every TCODE I try to run:

Let me know if I'm totally screwed and just need to give up and go to my backup I made before the patches were done.

Runtime Errors DDIC_TYPE_INCONSISTENCY

Date and Time 05/21/2008 15:54:28

Short text

Inconsistency in the Dictionary for the structure "WDY_CTLR_PARAM".

Source Code Extract

Line SourceCde

443 DD26V TYPE DD26V OCCURS 0,

444 DD27V TYPE DD27V OCCURS 0,

445 DD28V TYPE DD28V OCCURS 0,

446 MDLOG TYPE SMODILOG OCCURS 0,

447 END OF SVRS2_VIED.

448 TYPES: BEGIN OF SVRS2_VIET,

449 DD09V TYPE DD09V OCCURS 0,

450 MDLOG TYPE SMODILOG OCCURS 0,

451 END OF SVRS2_VIET.

452 TYPES: BEGIN OF SVRS2_WAPD,

453 APPL TYPE O2APPL OCCURS 0,

454 APPLT TYPE O2APPLT OCCURS 0,

455 NAVGR TYPE O2NAVGRAPH OCCURS 0,

456 NAVMP TYPE O2NAVMAP OCCURS 0,

457 END OF SVRS2_WAPD.

458 TYPES: BEGIN OF SVRS2_WAPP,

459 PCON TYPE O2PAGCON OCCURS 0,

460 PDIR TYPE O2PAGDIR OCCURS 0,

461 PPAR TYPE O2PAGPAR OCCURS 0,

462 PPART TYPE O2PAGPART OCCURS 0,

463 PVH TYPE O2PAGEVH OCCURS 0,

464 PDIRT TYPE O2PAGDIRT OCCURS 0,

465 END OF SVRS2_WAPP.

466 TYPES: BEGIN OF SVRS2_WDYC,

467 CATTR TYPE WDY_CTX_ATTRIB OCCURS 0,

468 CCOMP TYPE WDY_CTLR_COMPO_VRS OCCURS 0,

469 CCOMS TYPE WDY_CTLR_COMPO_SOURCE_VRS OCCURS 0,

470 CCOMT TYPE WDY_CTLR_COMPOT OCCURS 0,

471 CMAPP TYPE WDY_CTX_MAPPING OCCURS 0,

472 CNODE TYPE WDY_CTX_NODE OCCURS 0,

>>>>> CPARA TYPE WDY_CTLR_PARAM OCCURS 0,

474 CPART TYPE WDY_CTLR_PARAMT OCCURS 0,

475 CUSAG TYPE WDY_CTLR_USAGE OCCURS 0,

476 DEFIN TYPE WDY_CONTROLLER OCCURS 0,

477 DESCR TYPE WDY_CONTROLLERT OCCURS 0,

478 FGRPS TYPE WDY_FIELDGROUP OCCURS 0,

479 MDLOG TYPE SMODILOG OCCURS 0,

480 END OF SVRS2_WDYC.

481 TYPES: BEGIN OF SVRS2_WDYD,

482 CTMAP TYPE WDY_EXT_CTX_MAP OCCURS 0,

483 CTUSE TYPE WDY_EXT_CTLR_USE OCCURS 0,

484 CUSAG TYPE WDY_COMPO_USAGE OCCURS 0,

485 DEFIN TYPE WDY_COMPONENT OCCURS 0,

486 DESCR TYPE WDY_COMPONENTT OCCURS 0,

What happened?

Error in the SAP kernel.

The current ABAP "SAPLSEUF" program had to be terminated because the

ABAP processor detected an internal system error.

Error analysis

There is an internal system error.

eliminated with ABAP/4.

Trigger Location of Runtime Error

Program SAPLSEUF

Include LSVRXPIN

Row 473

Thanks!

Nick

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Nicolas,

Before restoring backup you might want to contact SAP. Let them remotely login and check.

regards, Sean.

Answers (2)

Answers (2)

Former Member
0 Kudos

Guys,

Thanks for the tips. Yep, I just restored the backup and am doing the patches again.

Nick

former_member185954
Active Contributor
0 Kudos

Hello Nicholas,

If i have time, i would normally do BASIS and ABAP patches one by one, cause if BASIS or ABAP patches crash, they bring down the system with them.

Regards,

Siddhesh

former_member185954
Active Contributor
0 Kudos

Hello Nicholas,

yes i understand its not pleasant, hope you performed a backup before the support packs, restore it back.