Urgent: Errors detected during SHADOW_IMPORT_UPG2

[ThomasKjelsrud]

Hi.

we are upgrading from R/3 4.7x200 to ERP2005 on Windows 2003 / SQL2005.

In phase SHADOW_IMPORT_UPG2 I get this error message:

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

SHADOW IMPORT ERRORS and RETURN CODE in SAPK700TEA.U01

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

2EETW000 sap_dext called with msgnr "2":

2EETW000 -

---

db call info -

---

2EETW000 function: db_setget

2EETW000 fcode: RT_SETB

2EETW000 tabname: RSPLPPM_PSDIR

2EETW000 len: 0

2EETW000 key:

2EETW000 retcode: 2

1 ETP111 exit code : "12"

In SAPK700TEA.U01 I have this info:

4 ETW000 1 entry for RSPLPPM_ADD_SET inserted (CHECKREPORT_SUCCESSFUL).

4 ETW714 end import of "R3TRTABURSPLPPM_ADD_SET" (to shadow tables).

4 ETW000 [dev trc ,00000] Thu Mar 08 16:12:06 2007 34084711 131.321614

4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 12849]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.

4 ETW000 39 131.321653

4 ETW000 [dev trc ,00000] Procname: [##Y4SAPR3Du0100000171720000144091160955]

4 ETW000 17 131.321670

4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 12849]: Error/Message: (err 208, sev 16), Invalid object name 'RSPLPPM_PSDIR'.

4 ETW000 74 131.321744

4 ETW000 [dev trc ,00000] Procname: [##Y4SAPR3Du0100000171720000144091160955]

4 ETW000 17 131.321761

4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT "PSDIR" FROM "RSPLPPM_PSDIR" ORDER BY "PSDIR"

4 ETW000 /* R3:KRN:0 T:RSPLPPM_PSDIR */ 48 131.321809

4 ETW000 ]

4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000

4 ETW000 25 131.321834

4 ETW000 [dbtrtab ,03888] ***LOG BZA=>table RSPLPPM_PS does not exist on database [dbtrtab#5 @ 3888]

4 ETW000 38 131.321872

2EETW000 sap_dext called with msgnr "2":

2EETW000 -

---

db call info -

---

2EETW000 function: db_setget

2EETW000 fcode: RT_SETB

2EETW000 tabname: RSPLPPM_PSDIR

2EETW000 len: 0

2EETW000 key:

2EETW000 retcode: 2

4 ETW000 ROLLBACK (8842714).

1 ETP187 R3TRANS SHADOW IMPORT

1 ETP110 end date and time : "20070308161206"

1 ETP111 exit code : "12"

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

4 EPU202XEND OF SECTION BEING ANALYZED

We have bound the Service Package SAPKW70011 to the upgrade, and I realize now that we should not have done that...(note 1013807).

What I need is a way to fix this so that I can proceed with the upgrade. I have read the other thread about this kind of error with Oracle, but if possible I would appreciate a solution directly related to MSSQL 2005.

Thanks!

Regards,

Thomas

[markus_doehr2 · Accepted solution]

> Hi.

>

> we are upgrading from R/3 4.7x200 to ERP2005 on

> Windows 2003 / SQL2005.

[...]

> In phase SHADOW_IMPORT_UPG2 I get this error message:

> We have bound the Service Package SAPKW70011 to the

> upgrade, and I realize now that we should not have

> done that...(note 1013807).

>

> What I need is a way to fix this so that I can

> proceed with the upgrade. I have read the other

> thread about this kind of error with Oracle, but if

> possible I would appreciate a solution directly

> related to MSSQL 2005.

>

I would recommend resetting the upgrade if you are not under time presure and start from scratch either omitting KW70011 or adding KW70012. We had the same issue (it's not ERP but NW2004s specific) and reset the upgrade.

There is a "workaround" by manually setting table activation states in the shadow instance. If you want to make use of that, create an OSS call - people there may help you better.

--

Markus

[ThomasKjelsrud · Accepted solution]

Hi Markus.

Thanks for your quick reply. We have decided to reset the upgrade and start from scratch.. We do have a time pressure, but a day has 24 hours.. right:)

Regards,

Thomas

[markus_doehr2 · Accepted solution]

> Hi Markus.

>

> Thanks for your quick reply. We have decided to reset

> the upgrade and start from scratch.. We do have a

> time pressure, but a day has 24 hours.. right:)

maybe the best choice for the system (but not for you unfortunately).

Good luck for next time!

PS: Also check note 865142 (if you use EDI) and if you add KB70009 to in BIND_PATCH check that you have the correct version (note 822379).

--

Markus