PARCONV_UPG - Last error code set: Unhandled mode flags found

[former_member229542]

Hi Guys, during an ERP 6 EHP7 Upgrade, during Downtime phase in PARCONV_UPG Step, the following error came up.

I never experienced this error, before, even with an Upgrade I did on a similar system.

During PARCONV_UPG step. it fails showing "450" Shadow-Nametab activations failed

System runs in Solaris 10/Oracle 11.0.2.3

PARCONV.LOG shows  Unhandled mode flags found

3 ETQ122 20150219160337: PID 26075 exited with status 0 (time: 0.000/0.110/0.270 real/usr/sys)

3 ETQ399 Reading selections from 'DDXTTCNT.LOG'.

4 ETQ399 Read 3 entries for table 'LIST'.

2 ETQ399 Found 9023 times modeflag 'V'.

2 ETQ399 Found 323 times modeflag 'A'.

2 ETQ399 Found 450 times modeflag 'F'.

1EETQ399 Unhandled entries found in inactive nametab:

2EETQ399 Modeflag 'F' appears 450 times

4 ETQ010 Date & Time: 20150219160337

1EETQ399 Last error code set is: Unhandled mode flags found, check 'PARCONV.LOG' for details

1EETQ203 Upgrade phase "PARCONV_UPG" aborted with errors ("20150219160337")

PD990219.ECP

2 ETP301 ----------------------------------------------------------------------

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2015/02/19 15:08:07")

2 ETP301 ----------------------------------------------------------------------

2 ETP000   processing modeflag 'F'

2 ETP301 ----------------------------------------------------------------------

2 ETP330XActivation of Shadownametabs with DDL

2 ETP301 ----------------------------------------------------------------------

3 ETP379X15:08:07: activating Nametab "BSIS":

2 ETP000   >> Name of inactive nametab to read  : DDXTT

2 ETP000   >> Format of inactive nametab to read: 5.0

3 ETP355Xstatements:

3 ETP000 >>>>>>>>> UNCRITICAL DIPGNTAB <<<<<<<<<

3 ETP000 CREATE

3 ETP000 INDEX "BSIS~ZME" ON "BSIS"

3 ETP000 ("BUKRS",

3 ETP000 "HKONT",

3 ETP000 "GJAHR")

3 ETP000 PCTFREE 10

3 ETP000 INITRANS 002

3 ETP000 TABLESPACE PSAPBTABI

3 ETP000 NOCOMPRESS

3 ETP000 STORAGE (INITIAL 0000000016 K

3 ETP000 NEXT 0000081920 K

3 ETP000 MINEXTENTS 0000000001

3 ETP000 MAXEXTENTS UNLIMITED

3 ETP000 PCTINCREASE 0000

3 ETP000 FREELISTS 001)

3 ETP000

2PETP374 15:09:54: Warning: Retcode 1: SQL-error "3113" in DDL statement for "BSIS

2PETP374          " - IGNORED

2PETP000 SQL-error-Text: "ORA-03113: end-of-file on communication channel

2PETP000 Process ID: 24634

2PETP000 Session ID: 314 Serial number: 35749"

2PETP358 -> this error should be corrected later

3 ETP000 DELETE FROM DDSTORAGE WHERE

3 ETP000 DBSYSABBR = 'ORA' AND

3 ETP000 TABNAME = 'BSIS' AND

3 ETP000 INDEXNAME = 'ZME'

3 ETP000

2WETP000 15:09:54: Retcode 1: error in DDL statement for "BSIS                          " - repeat

2EETP345 15:10:06: Retcode 1: SQL-error "3114-ORA-03114: not connected to ORACLE" in DDL statement

2EETP345 for "BSIS                          "

2 ETP000  --------------- DB-ROLLBACK() ---------------

2EETP334 15:10:06: error in DDL, nametab for "BSIS" not activated

3 ETP379X15:10:06: activating Nametab "BSPC_DL_PERSSTOR":

2 ETP000  --------------- DB-ROLLBACK() ---------------

2AETP344 sqlerror "3114" occured at location "LOC133"    (object "BSPC_DL_PERSSTOR")

3 ETP379X15:10:06: activating Nametab "BUT050":

2 ETP000  --------------- DB-ROLLBACK() ---------------

2AETP344 sqlerror "3114" occured at location "LOC133"    (object "BUT050")

3 ETP379X15:10:06: activating Nametab "CACS_TGACV":

2 ETP000  --------------- DB-ROLLBACK() ---------------

2AETP344 sqlerror "3114" occured at location "LOC133"    (object "CACS_TGACV")

3 ETP379X15:10:06: activating Nametab "CACS_TGRATV":

2 ETP000  --------------- DB-ROLLBACK() ---------------

2AETP344 sqlerror "3114" occured at location "LOC133"    (object "WSD_KEYWORD_AS")

2 ETP301 ----------------------------------------------------------------------

3 ETP361 "0" Shadow-Nametabs activated, DDL executed

2 ETP362 "450" Shadow-Nametab activations failed

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2015/02/19 16:01:37")

2 ETP363 End  : Act. of Shadow-Nametabs with DDL ("2015/02/19 16:03:26")

When checking any of this objects in SE14, it shows in un Update Status but inconsistent, DB objects are not the same as runtime objects.

Not sure if this objects should be created during this step, or this inconsistencies are causing the error in the nametab

My main concern is how to fix 450 objects has modeflag F.

Any help would be highly valuable

Best

Database object for BUT050 is inconsistent: (Fields)

Header: Konsistent mit dem Laufzeitobjekt

Client-Specific	Storage Type
Ja	Undefiniert

Fields: Inconsistent with the runtime object

Runtime Object	Database	Position	Data Type	Length	Decimals	Not null	Default
CLIENT	CLIENT	1	VARCHAR2	3		X	'000'
RELNR	RELNR	2	VARCHAR2	12		X	' '
PARTNER1	PARTNER1	3	VARCHAR2	10		X	' '
PARTNER2	PARTNER2	4	VARCHAR2	10		X	' '
DATE_TO	DATE_TO	5	VARCHAR2	8		X	'00000000'
DATE_FROM	DATE_FROM	6	VARCHAR2	8		X	'00000000'
RELTYP	RELTYP	7	VARCHAR2	6		X	' '
XRF	XRF	8	VARCHAR2	1		X	' '
DFTVAL	DFTVAL	9	VARCHAR2	20		X	' '
RLTYP	RLTYP	10	VARCHAR2	6		X	' '
RELKIND	RELKIND	11	VARCHAR2	4		X	' '
CRUSR	CRUSR	12	VARCHAR2	12		X	' '
CRDAT	CRDAT	13	VARCHAR2	8		X	'00000000'
CRTIM	CRTIM	14	VARCHAR2	6		X	'000000'
CHUSR	CHUSR	15	VARCHAR2	12		X	' '
CHDAT	CHDAT	16	VARCHAR2	8		X	'00000000'
CHTIM	CHTIM	17	VARCHAR2	6		X	'000000'
XDFREL	XDFREL	18	VARCHAR2	1
XDFREL2	XDFREL2 does not exist	19	VARCHAR2	1		U	' '
DB_KEY	DB_KEY does not exist	20	RAW	16		U
DB_KEY_TD	DB_KEY_TD does not exist	21	RAW	16		U

[Reagan · Accepted solution]

>>2PETP000 SQL-error-Text: "ORA-03113: end-of-file on communication channel

2EETP345 15:10:06: Retcode 1: SQL-error "3114-ORA-03114: not connected to ORACLE" in DDL statement<<

The issue could most likely be with the database. Check the Oracle alert log.

I would try with a different kernel set and if that doesn't help consider applying the latest SBP.

[former_member229542 · Accepted solution]

Thanks Benjamin

Issue was with Index BSIS-ZME, which was not present in Oracle but it does existed in SAP Dictionary. It caused a memory dump when creating it.

As a workaround, it was deleted from SAP Dictionary; then step completed successfully