Error on SHADOW_IMPORT_UPG1

[Former Member]

Hello,

We are stuck in phase "SHADOW_IMPORT_UPG1", with the following error message :

1 ETP187 R3TRANS SHADOW IMPORT

1 ETP101 transport order : "SAPKLDENX0"

1 ETP102 system : "RY0"

1 ETP108 tp path : "/usr/sap/put/exe/tp"

1 ETP109 version and release : "372.03.35" "700"

1 ETP198

4 ETW000 /usr/sap/put/exe/R3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 08.06.2007 - 13:10:19

4 ETW000 control file: /usr/sap/put/tmp/SAPKKLDENX0.RY0

4 ETW000 > #pid 5155 on mvi929 (ry0adm)

4 ETW000 > import

4 ETW000 > onlyshadow=yes nosverschk=yes

4 ETW000 > buffersync=no

4 ETW000 > file='/usr/sap/put/data/RLDENX0.SAP'

4 ETW000 > continuation='/usr/sap/put/data/RLDENX0_#.SAP'

4 ETW000 > client cascade yes

4 ETW000 > cpshdw = '4G'

4 ETW000 > ddactive=yes

4 ETW000 > shadowtatables=yes

4 ETW000 R3trans was called as follows: /usr/sap/put/exe/R3trans -u 26 -w /usr/sap/put/tmp/SAPKL

DENX0.RY0 /usr/sap/put/tmp/SAPKKLDENX0.RY0

4 ETW000 active unconditional modes: 26

4 ETW000 Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'RY0' --- SYSTEM = 'RY0'.

4 ETW690 "0" "0"

4 ETW000 COMMIT (0).

4 ETW000 trace at level 1 opened for a given file pointer

4 ETW000

4 ETW000 ================== STEP 1 =====================

4 ETW000 date&time : 08.06.2007 - 13:10:20

4 ETW000 function : IMPORT

4 ETW000 data file : /usr/sap/put/data/RLDENX0.SAP

4 ETW000 Continuation : /usr/sap/put/data/RLDENX0_#.SAP

4 ETW000 buffersync : NO

4 ETW000 clients : cascade

4 ETW000 repeatimport : NO

4 ETW000 repeatclimport : NO

4 ETW000 c.s.i. : NO

4 ETW000 nosverschk : YES

4 ETW000 shdw tabs(W) : 4G

4 ETW000 considernewtables: NO

4 ETW000 l.s.m. : VECTOR

4 ETW000 charsetadapt : YES

4 ETW000 def. charset : WEUROPEAN

4 ETW000 commit : 100000

4 ETW000 table cache : dynamic

4 ETW000

4 ETW000 Calculating shadow tables: 395 shadow tables found (exchange tables)

1AETW000 ===> HALT: No exchange table for DD02L found in PUTTB for release MAX(UVERS.NEWRELEASE)

Please contact the SAP support.

4 ETW000 ROLLBACK (0).

4 ETW000 End of Transport (0016).

4 ETW000 date&time: 08.06.2007 - 13:10:20

4 ETW000 1 error occured.

1 ETP187 R3TRANS SHADOW IMPORT

1 ETP110 end date and time : "20070608131020"

1 ETP111 exit code : "16"

1 ETP199 ######################################

4 EPU202XEND OF SECTION BEING ANALYZED

929:/usr/sap/put/log =>

We already update the last R3trans version to Jun 4 2007 from market place.

We appreciate your Help

Regards

[markus_doehr2 · Accepted solution]

This sounds severe... if this is not production, I´d reset the upgrade and start from scratch. If you have some time I´d open an OSS call.

DD02L is a central table with all "SAP tables", I´d not try to overcome this issue before the support gave a statement on this.

Did you EUIMPORT* ran all successfull?

--

Markus

[Former Member · Accepted solution]

We already open an OSS Report, but we are waiting the answer.

The EUIMPORT PHASE finished without error.

We have doubt about the steps to migrate from SAP/R3 46C Oracle 8.0.5 with HPUX 11.0 to ECC 6.0 Oracle 10.2 with HP-UX IA64.

Thanks for you Help.

Kind Regards

[markus_doehr2 · Accepted solution]

I´d do the following way:

- Oracle 8.0.5 --> Oracle 9.2.0.8

- HP-UX 11.0 --> HP-UX 11.23 (or HP-UX 11.31)

- Oracle 9.2.0.8 --> Oracle 10.2.0.2 (+ all the necessary patches from note 871096)

- 4.6c --> ECC 6.0

--

Markus

[Former Member · Accepted solution]

We did the following way:

Initial SAP/R3 46C with Oracle 8.0.5 in HPUX 11.0

1.- Upgrade to Oracle 8.1.7 in HP-UX 11.0

2.- Upgrade to Oracle 9.2.0 patch 9.2.0.6 and upgrade to HP-UX 11.23 IA64

3.- Upgrade to Oracle 10.2 Patch 10.2.0.2

4.- Upgrade 46C to ECC 6.0

But we are stuck.

We don´nt know what´s the problem...

Regards

[markus_doehr2 · Accepted solution]

do you see anything in the Oracle alert log or in the traces?

--

Markus

[Former Member · Accepted solution]

No. i don´t see any problem in the alert log

i will chech the log completely again.

Thanks Markus

another idea?.

[markus_doehr2 · Accepted solution]

I believe this is a problem only SAP can solve.... unfortunately...

--

Markus

[Former Member · Accepted solution]

MARKUS--

We did the following way:

Initial SAP/R3 46C with Oracle 8.0.5 in HPUX 11.0

1.- Upgrade to Oracle 8.1.7 in HP-UX 11.0

2.- Upgrade to Oracle 9.2.0 patch 9.2.0.6 and upgrade to HP-UX 11.23 IA64

3.- Upgrade to Oracle 10.2 Patch 10.2.0.2

4.- Upgrade 46C to ECC 6.0 .- We must use SAP Kernel 46D 32 Bits to update the R3trans, disp+work and tp as per file CHECKS.LOG

Wich SAP Kernel did you use in your Upgrade?

Regards

[markus_doehr2 · Accepted solution]

> 4.- Upgrade 46C to ECC 6.0 .- We must use SAP Kernel

> 46D 32 Bits to update the R3trans, disp+work and tp

> as per file CHECKS.LOG

we use the newest (as of that time, I don't remember exactly which one... ) 46D_EXT kernels but not 32bit.. in fact, there is no 32bit kernel for HP-UX IA64...

--

Markus

[Former Member · Accepted solution]

Markus

one more question.

When you migrate your system

- HP-UX 11.0 to HP-UX 11.23

did you upgrade you SAP Kernel from 46C to 46D EXT? or

in wich moment do you change to 46DEXT 64 bits (11.23)?

did you only download the last SAP Kernel 46DEXT to migrate SAP from 46C to 46DEXT?

[markus_doehr2 · Accepted solution]

At the time you go to IA64 you use the 46D_EXT kernel. You're moving from PA-RISC HP/9000 11.00 to IA64 Integrity, right? You can't run 32bit PA-RISC kernels on IA64...

--

Markus

[Former Member · Accepted solution]

Dear Markus....Excuse me by bother you with this problem...we apreciatte your help.

We still don´t have answer from OSS reports.

As i told you, we did migration this way. And you can see, we did not have problems to work with SAP Kernel 46C 32 bits in HP-UX 11.23.

Initial

1.- Oracle 8.0 .5 | SAp Kernel 46C 32 bits | O.S HP-UX 11.0 PA-RISC

We migrate to 8.1.7

2.- Oracle 8.1.7 |SAP Kernel 46C 32bits | O.S HP-UX 11.0 PA-RISC

We migrate to 9.2

3.- Oracle 9.2 |SAP Kernel 46C 32 bits | O.S HP-UX 11.23 (IA64)

We migrate to 10.2

4.- Oracle 10.2 | SAP Kernel 46C 32 bits || O.S HP-UX 11.23 (IA64)

5.- We start Prepare

6.- When we read the CHECKS.LOG we update the Kernel from 46C 32 bits to SAP Kernel 46D 32 bits

7.- Problems in Upgrade Phase SHADOW_IMPORT_UPG .

Can you describe step by step the way you UPGRADE your system?.

Because we want start again, taking your recommendations.

Thank you, very much!!!

[markus_doehr2 · Accepted solution]

So does that mean you were using the 32bit PA-RISC kernel on the IA64 box? It will WORK technically (in an emulation mode) but you would in my understanding have problems with shared libraries interdependencies (PA-RISC executables can't load Itanium libraries and vice versa); I really, really wonder how you got that far

1. Oracle 8.0.5 - Kernel 4.6C_32 - 11.00 PA-RISC

2. Oracle 8.1.7 - Kernel 4.6C_32 - 11.00 PA-RISC

3. Oracle 9.2.0.8 - Kernel 4.6D_EXT_64 11.23 IA64

4. Oracle 10.2 - Kernel 4.6D_EXT_64 11.23 IA64

You don't need to start from scratch completely, I'd reset the upgrade (it's still early enough), reset PREPARE, change your kernel to 4.6D_EXT 64bit IA64 (not PA-RISC) and use the native tools for the next PREPARE.

4.6c kernel are LONG out of maintenance and were replaced (really years ago) with 4.6D and now 4.6D_EXT to support newer operating systems.

Also, according to note 156548 you NEED to run 4.6D_EXT, everything else is not supported:

SAP KERNEL 4.6D 64-BIT: ORACLE 9.2 64-BIT HP-UX 11.23/IA64 64BIT 1,2,3,4

SAP KERNEL 4.6D_EXT 64-BIT: ORACLE 10.2 64-BIT HP-UX 11.23/IA64 64BIT 3,5,6

ORACLE 10.2 64-BIT HP-UX 11.31/IA64 64BIT 3,5

ORACLE 9.2 64-BIT HP-UX 11.23/IA64 64BIT 2,3

So I'd do the following now:

- stop your upgrade

- reset the upgrade (run the program RSUPGRES, see section 7.16 of the upgrade guide and the note)

- replace your kernel with 4.6D_EXT and Oracle client 9.2.0.7

- restart PREPARE

You can leave /usr/sap/trans/EPS/in, no need to start again binding patches if you found your combination, it's just a matter of running time.

Keep me posted about your progress.

--

Markus

[markus_doehr2 · Accepted solution]

Just as additional info: The upgrade is described in

Note 612796 - Move to HP-UX Itanium systems

[...]

Although HP-UX for Itanium is largely binary-compatible for HP-UX PA-Risc, SAP software usually requires a higher degree of optimization than is the case if PA-Risc optimized software runs on HP-UX for Itanium. Therefore, we only release optimized versions for HP-UX for Itanium.

[...]

The following upgrade scenarios are typical for HP-UX Itanium customers:

4. Source release: 4.6C with 64-bit 4.6D kernel/HP-UX 11.0/11i/Oracle 8.1.7.

Target release: 4.6C with 64-bit 4.6D kernel/HP-UX 11.23/Oracle 9i or Oracle 10G.

a) Switch to the Itanium server and upgrade of the operating system to HP-UX 11.23.

b) Use of the Itanium kit for HP-UX 64-bit 4.6D kernel. After you apply the update kit, the 64-bit Oracle database is updated to Version 9.2 and an optimized version of the 64-bit SAP kernel on HP-UX IA64 is installed.

The error your see is because your source kernel is too old and not supported.

--

Markus

[Former Member · Accepted solution]

We start th eUpgrade from scratch this way:

1. Oracle 8.0.5 - Kernel 4.6C_32 - 11.00 PA-RISC

2. Oracle 8.1.7 - Kernel 4.6C_32 - 11.00 PA-RISC

3. Oracle 9.2.0.8 - Kernel 4.6D_EXT_64 11.23 IA64

4. Oracle 10.2 - Kernel 4.6D_EXT_64 11.23 IA64

Bu we´still have the same Error.

We also update the R3trans and tp to 04 jun 2007 version in /usr/sap/put/exe, sending the same error.

We have errors in EU_IMPORT Phases like this

--- This is the output from EU_IMPORT1 ---

$ cat /usr/sap/put/log EX000000.DPR

/usr/sap/put/exe/R3load: START OF LOG: 20070613185659

/usr/sap/put/exe/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/put/exe/R3load: version R7.00/V1.4

Compiled Aug 29 2006 06:07:03

/usr/sap/put/exe/R3load -i /usr/sap/put/exchange/compack/EX000000.COD -p /usr/sap/put/log/EX000000.DPR -s /usr/sap/put/log/EX000000.DST -datacodepage 1100 -dbcodepage auto -upg_nametab DDNTT~ DDNTF~

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII

(SQL) INFO: SLEXC.SQL not found

(DB) INFO: CO2MAP~ created #20070613185700

(DB) INFO: CO2MAP~0 created #20070613185700

(DB) INFO: CO2MAP~IDX created #20070613185700

(DB) INFO: CO2MAPINF~ created #20070613185700

(DB) INFO: CO2MAPINF~0 created #20070613185700

(DB) INFO: DDFTX~ created #20070613185700

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "DDFTX_{0" ON "DDFTX}" ( "TABNAME", "FIELDNAME", "DDLANGUAGE" ) TABLESPACE PSAPEL700I STORAGE (INITIAL 0000000016K NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

DbSlExecute: rc = 102

(SQL error 955)

error message returned by DbSl:

ORA-00955: name is already used by an existing object

(DB) ERROR: DDL statement failed

(CREATE INDEX "DDFTX_{1" ON "DDFTX}" ( "ROLLNAME" ) TABLESPACE PSAPEL700I STORAGE (INITIAL 0000000016K NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

DbSlExecute: rc = 102

(SQL error 955)

error message returned by DbSl:

ORA-00955: name is already used by an existing object

--- This is the output of EU_IMPORT2 -

-

---

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "SXC_ATTR_{0" ON "SXC_ATTR}" ( "IMP_NAME" ) TABLESPACE PSAPES700I STORAGE (INITIAL 262144 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

DbSlExecute: rc = 102

(SQL error 955)

error message returned by DbSl:

ORA-00955: name is already used by an existing object

(DB) INFO: SXC_ATTRT~ created #20070613191732

(IMP) INFO: import of SXC_ATTRT~ completed (6937 rows) #20070613191732

-

-

---

Maybe this can help to solve the problem! -

-

---

Thanks for you help

P.D. we already post message to OSS.

[markus_doehr2 · Accepted solution]

did you execute RSUPGRES before you started the upgrade again? If yes, just in default mode or in force mode?

The index seems to be still exisiting...

--

Markus

[Former Member · Accepted solution]

Hi Markus..

I mean we start from the beginning.

This is a Test Instance for the Upgrade.

We restore a BACKUP and we start from the beggining before the PREPARE.

[markus_doehr2 · Accepted solution]

In this case it's really really strange...

How many import processes did you use? We used 3

--

Markus

[Former Member · Accepted solution]

We use 3 too.

Thanks

[markus_doehr2 · Accepted solution]

I apologize, I have no more idea why this is happening.

Hopefully the SAP support can say something soon. Keep me posted about your results

--

Markus

[Former Member · Accepted solution]

Markus,

We have a similar problem in the EU_IMP1 phase. Below is the log file content.

Thanks,

Nayab

cat EX000000.DPR

/usr/sap/put/exe/R3load: START OF LOG: 20071009123022

/usr/sap/put/exe/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP

/usr/sap/put/exe/R3load: version R7.00/V1.4

Compiled Aug 29 2006 01:25:23

/usr/sap/put/exe/R3load -i /usr/sap/put/exchange/compack/EX000000.COD -p /usr/sap/put/log/EX000000.DPR -s /usr/sap/put/log/EX000000.DST -datacodepage 1100 -dbcodepage auto -upg_nametab DDNTT~ DDNTF~

(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20

(DB) ERROR: DbSlErrorMsg rc = 20

/usr/sap/put/exe/R3load: job finished with 1 error(s)

/usr/sap/put/exe/R3load: END OF LOG: 20071009123023

[Former Member · Accepted solution]

Markus,

Problem is resolved. It was using the latest R3load(7.00) we replaced it with 6.40.

Thanks,

Nayab

[Former Member]

This problem is caused by the fact of setting the US7ASCII. The oracle

note 819830 explains that inconsistencies occur during the upgrade if

one uses US7ASCII. Unfortunately, these inconsistencies cannot be

removed. And the only solution is to restore the system from the backup.

With Warm Regards,

Related Notes 102402 and 836517.

Thanks MArkus for your Help

Thanks to OSS.

We´ve already finish the Migration.