Upgrade Error in EU_IMPORT2 phase

[Former Member]

Hi

Our SAP 4.7 EE upgrade to ECC6 EHP6 is stuck in EU_IMPORT2 phase due to the below errors:

Additional notes:

1. I had to reset a previous upgrade attempt due to some other issues. I have reset the upgrade with SUM tool, as well as the report RSUPGRES report.

2. During the previous upgrade, at the end of CHECKS phase, I had to convert some of the 4K paze size tablespaces to 16K tablespaces (some of the old 4K tablespaces still exists even after their content is copied to a 16K tablespace).  I have not dropped those tablespaces on purpose - I wanted to do some analysis of those tablespaces.

3. As per note 1732061 (

--------------------< D031901 22/OCT/10 >-----------------------------

Preprocessing:ERROR: Found pattern "R3load:...

You have reset the update in the Preprocessing roadmap step and now, when running the Software Update Manager again, you get the following error message:

"ERROR: Found pattern "R3load: job completed" 0 times, but expected 1! Analyze the log file for further error messages or program abort."

This error occurs if you did not apply SAP Note 1518145 before the reset. To solve the problem, repeat the phase in which the error occured.)

This is exactly the error I am getting in one of the relavant log files EU_IMP2.ELG

We do not need to apply the SP as mentioned in  note 1518145, as we are already in a higher patch level.

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

Totally clue less, as to what the issue is about.

FYI, I have the latest kernel in place 721_EXT, SP 100, and latest R3load, R3ldctl and dbdb6slib.o.

Any clues gurus?

thanks,

Abdul

[paul_power]

Hi Abdul,

As the phase keeps failing when repeated, it seems there is really still an error in one of the

EX00000<number>.DPR logs, we would need to see these to say which is the one containing the error.

Assuming the only error is

"SQL0539N" "SAPR3.T777DITCLASS" does not have a primary key

please check via  (I assume you are using DB6 database)

describe indexes for table SAPR3."T777DITCLASS"

db2look -d RW2 -e -t  "T777DITCLASS"

Is the system up at this time?

If so:

Call transaction SE14.

Enter the name of the table and choose "Edit".

Choose "Indexes".

Select the primary index and choose "Choose (F2)".

If you choose "Activate and adjust", the system creates the index

again and it is consistent.

Check the object log of this activation.

If an error occurs, eliminate the cause and reactivate the index.

regards,

Paul

[Former Member]

Hi Paul,

1. Have attached a sample .DPR file that has this issue, in my above response.

2. SAP Support has confirmed that the primary key errors are not significant.  Upgrade phase is stopping because of the failed index creation jobs.

3. db2look is giving me the description of the table, no mention of any indexes on them (as the indexes do not exist yet).  After I manually created the index based on inputs from .DPR files, I can see them in db2look results. 

4. In SE14 tcode, I can see that the tables, for example T777DITCLASS~, exists in the the database level.  It doesnt exist in the data dictionary at SAP level.  The opptions for Activation or Adjustments are greyed out.

Thanks & Regards

Abdul

[former_member188883]

Hi Abdul,

Could you attach the log files *.DPR as mentioned in the screenshot.

Regards,

Deepak Kori

[Former Member]

Here is the log of a DPR file:

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

R3load: START OF LOG: 20130507003928

R3load: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#17 $ SAP
R3load: version R7.20/V1.4
Compiled Jan 16 2013 12:35:01
R3load -i /db2/RW2/sapdata19/SUM/abap/exchange/compack/EX000005.COD -p /db2/RW2/sapdata19/SUM/abap/log/EX000005.DPR -s /db2/RW2/sapdata19/SUM/abap/log/EX000005.DST -dbcodepage auto -nametab DDNTT~
DDNTF~ -stop_on_error

DbSl Trace: Error setting SQLSetEnvAttr( SQL_ATTR_DB2TRC_STARTUP_SIZE=32 ), rc=-2

DbSl Trace: SQLGetDiagField(SQL_DIAG_NUMBER): rc=-2

DbSl Trace: Unable to retrieve effective SQL_ATTR_DB2TRC_STARTUP_SIZE

DbSl Trace: SQLGetDiagField(SQL_DIAG_NUMBER): rc=-2

(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) ERROR: could not find regular export directory
(SQL) INFO: Searching for SQL file APPL1.SQL
(SQL) INFO: APPL1.SQL not found
(SQL) ERROR: could not find regular export directory
(DB) ERROR: DDL statement failed with SQL error
( ALTER TABLE "SNAP~" DROP PRIMARY KEY  )
  (SQL error -539)
  error message returned by dsql:
SQL0539N  Table or nickname "SAPR3.SNAP~" does not have a "PRIMARY" key.  SQLSTATE=42888
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE UNIQUE INDEX "SNAP~0" ON "SNAP~" ( "DATUM", "UZEIT", "AHOST", "UNAME", "MANDT", "MODNO", "SEQNO" ) ALLOW REVERSE SCANS  )
dsql_exec_immediate returned DS_DBOBJECTEXISTS
(DB) INFO: disconnected from DB

R3load: job finished with 1 error(s)

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

FYI, SAP Support says I am using an unsupported version of kernel (7.20).  However, this is not true, I have 721_EXT in my upgrade directory xxxx/xxxx/xxxx/abap/exe, which is one of the supported kernels for ECC 6 EHP6 upgrade, as per PAM.  For some reasons, R3load version shows still R720/V1.4 with kernel 720_EXT patch level 402.