cancel
Showing results for 
Search instead for 
Did you mean: 

Checks MAIN_NEWBAS/PARCONV_UPG were negative: DSYS_PHHEAD_ECI2PH

Former Member
0 Kudos

Hello,

we are middle in an upgrade ECC5.0 -- > ECC6.06 (MaxDB7.9/Win2008R2/UC System). And in in the processing phase we get an activation error (see below). Any ideas how to handle it? I already check the consistency (SE80). No errors found. The index/table is showed active. But if I try to activated it (again) the system returns: problems during the activation.

Thanks in advance!

  Checks after phase MAIN_NEWBAS/PARCONV_UPG were negative!

   


      Last error code set: Single errors (code > 😎 found in logfile
      'PARCONV.ELG'

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD990319.OHT

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 ETP355Xstatements:

3 ETP399 CREATE UNIQUE INDEX "DSYS_PHHEAD_ECI2PH"

on "DSYS_PHHEAD_ECI2"

3 ETP399 ("PHIO_ID")

3 ETP399

2WETP000

16:38:33: Retcode 1: error in DDL statement for "DSYS_PHHEAD_ECI2 " - repeat

2EETP345 16:38:45: Retcode 1: SQL-error "-1452-POS(1) Duplicate secondary

key" in DDL statement for

2EETP345 "DSYS_PHHEAD_ECI2 "

2 ETP399

--------------- DB-ROLLBACK() ---------------

2EETP334 16:38:45: error in

DDL, nametab for "DSYS_PHHEAD_ECI2" not activated

3 ETP355Xstatements:

3 ETP399 CREATE UNIQUE INDEX "DSYS_PHHYPE_ECI2RE" on "DSYS_PHHYPE_ECI2"

3 ETP399 ("REIO_ID")

3 ETP399

2WETP000 16:38:45: Retcode 1: error in

DDL statement for "DSYS_PHHYPE_ECI2 " - repeat

2EETP345 16:38:57: Retcode 1: SQL-error "-1452-POS(1) Duplicate secondary key" in DDL statement for

2EETP345 "DSYS_PHHYPE_ECI2 "

2 ETP399 --------------- DB-ROLLBACK()

---------------

2EETP334 16:38:57: error in DDL, nametab for

"DSYS_PHHYPE_ECI2" not activated

1 ETP111 exit code : "8"

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member188065
Participant
0 Kudos

Thanks for getting back on this.

To my findings this index is only used for performance issues. I took the aproach to have the Upgrader create a regular index instead by editing the DDL feed from TATAF removing the UNIQUE clause from the DDL statement for this particular one.

Interestingly enough is the fact, that after the upgrade both indices show up as unique in SE11

luisdarui
Active Contributor
0 Kudos

Hi SAP BASIS,

In case you can use the MaxDB Database Studio to query against the database the following query:

SELECT

          Field1, Field2, Field3, ..., FieldN, Count(*)

FROM

          Table1

GROUP BY

               Field1, Field2, Field3, ..., FieldN

HAVING

               count(*) > 1;

Use the Fields of your index. If you have only one retu

In case you can check whether it's a bug in SUM or your table has 2 results for the KEY specified in your index.

As James already suggested, it's weird enough to open an SAP incident to have this analyzed by the SUM or Dictionary experts.

Regards

JamesZ
Advisor
Advisor
0 Kudos

Apparently there is duplicate "PHIO_ID"  in table DSYS_PHHEAD_ECI2,(In fact some other tables have the same issue, this one just an example) thus unique index was not allowed to create.


the solution is either to create a non-unique index or drop the duplicate key. Each of the solutions is very critical to the system, I recommend you to reach to SAP for the right solution.

Former Member
0 Kudos

We dropped the duplicate key, and create an new one. It was only an index, so ...

former_member188065
Participant
0 Kudos

Hola Benita,

how did you resolve the issue back in 2013?

former_member188883
Active Contributor
0 Kudos

Hi Benita,

Could you just repeat the phase . Most of the time due to incorrect buffer entries such error appears.

Repeating the phase resolves it.

Regards,

Deepak Kori

former_member188065
Participant
0 Kudos

I doubt repetition can solve this issue.

The error says:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD990417.SID

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3 ETP355Xstatements:

3 ETP000 CREATE UNIQUE INDEX "DSYS_PHHEAD_ECI2PH" on "DSYS_PHHEAD_ECI2"

3 ETP000 ("PHIO_ID")

3 ETP000

2WETP000 20:48:22: Retcode 1: error in DDL statement for "DSYS_PHHEAD_ECI2 " - repeat

2EETP345 20:48:34: Retcode 1: SQL-error "-1452-POS(1) Duplicate secondary key" in DDL statement for

2EETP345 "DSYS_PHHEAD_ECI2 "

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

2EETP334 20:48:34: error in DDL, nametab for "DSYS_PHHEAD_ECI2" not activated

3 ETP355Xstatements:

3 ETP000 CREATE UNIQUE INDEX "DSYS_PHHYPE_ECI2RE" on "DSYS_PHHYPE_ECI2"

3 ETP000 ("REIO_ID")

3 ETP000

2WETP000 20:48:34: Retcode 1: error in DDL statement for "DSYS_PHHYPE_ECI2 " - repeat

2EETP345 20:48:47: Retcode 1: SQL-error "-1452-POS(1) Duplicate secondary key" in DDL statement for

2EETP345 "DSYS_PHHYPE_ECI2 "

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

2EETP334 20:48:47: error in DDL, nametab for "DSYS_PHHYPE_ECI2" not activated

1 ETP111 exit code : "8"

I read that DDL as an impossible attempt. A unique index can only become created if there are no duplicate keys.

This happens during PARCONV_UPG

Editing the properties in SE11 database utility from unique to non-unique doesn't help either