Upgrade Stop at Phase PARMVNT_XCNV

[Former Member]

Dear Experts,

I am trying to upgrade R/3 46C to ECC6 SR3, But I stuck at phase PARMVNT_XCNV. Please find below logs for your reference. Please help me to resolve this issue.

MVNTXCNV.LOG file

1 ETQ201XEntering upgrade-phase "PARMVNT_XCNV" ("20081020140543")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_mss_schema=dbo

4 ETQ399 auth_shadow_upgrade=0

4 ETQ380 computing toolpath for request "TP_MOVENTABS_SHD"

4 ETQ381 request "TP_MOVENTABS_SHD" means "tp mvntabs for shadow tables"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHDNEW"

4 ETQ383 translates to path "exe"

4 ETQ383 translates to path "exe"

2 ETQ399 Starting 4 tp processes:

4 ETQ010 Date & Time: 20081020140543

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10824

4 ETQ010 Date & Time: 20081020140545

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10832

4 ETQ010 Date & Time: 20081020140547

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10840

4 ETQ399 ... programs total : 4

4 ETQ399 ... programs started: 3

4 ETQ399 ... programs running: 3

4 ETQ399 ... nr 0: tp ddlntabs, pid 10824

4 ETQ399 ... nr 1: tp ddlntabs, pid 10832

4 ETQ399 ... nr 2: tp ddlntabs, pid 10840

2 ETQ399 2008/10/20 14:05:47: sleeping 60 seconds

4 ETQ399 ... programs total : 4

4 ETQ399 ... programs started: 3

4 ETQ399 ... programs running: 3

4 ETQ399 ... nr 0: tp ddlntabs, pid 10824

4 ETQ399 ... nr 1: tp ddlntabs, pid 10832

4 ETQ399 ... nr 2: tp ddlntabs, pid 10840

2 ETQ399 2008/10/20 14:06:47: sleeping 60 seconds

2 ETQ399 tp ddlntabs finished with error (rc=8)

4 ETQ010 Date & Time: 20081020140747

2 ETQ399 tp ddlntabs finished with error (rc=8)

4 ETQ010 Date & Time: 20081020140747

4 ETQ010 Date & Time: 20081020140747

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10848

2 ETQ399 tp ddlntabs finished successfully

4 ETQ010 Date & Time: 20081020140749

2 ETQ399 tp ddlntabs finished with error (rc=8)

4 ETQ010 Date & Time: 20081020140749

2 ETQ399 Starting 2 tp processes:

4 ETQ010 Date & Time: 20081020140750

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10880

4 ETQ010 Date & Time: 20081020140752

4 ETQ010 Starting: tp ddlntabs operation

2 ETQ399 started tp ddlntabs: pid 10888

2 ETQ399 tp ddlntabs finished successfully

4 ETQ010 Date & Time: 20081020140754

2 ETQ399 tp ddlntabs finished with error (rc=8)

4 ETQ010 Date & Time: 20081020140952

2EETQ399 Dialogue: ERROR

2EETQ399 tp processes returned errors.

2EETQ399 View latest 'TP*.ECO' files in log-directory for details.

MVNTXCNV.ELG File

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

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD001020.MS1

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

2EETP345 14:08:02: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGBDC "

2EETP334 14:08:02: error in DDL, nametab for "/SAPDMC/LSGBDC" not activated

2EETP345 14:08:14: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGBDCA "

2EETP334 14:08:14: error in DDL, nametab for "/SAPDMC/LSGBDCA" not activated

2EETP345 14:08:26: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGBDCS "

2EETP334 14:08:26: error in DDL, nametab for "/SAPDMC/LSGBDCS" not activated

2EETP345 14:08:38: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGBDCT "

2EETP334 14:08:38: error in DDL, nametab for "/SAPDMC/LSGBDCT" not activated

2EETP345 14:08:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGPRO "

2EETP334 14:08:50: error in DDL, nametab for "/SAPDMC/LSGPRO" not activated

2EETP345 14:09:02: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGPROT "

2EETP334 14:09:02: error in DDL, nametab for "/SAPDMC/LSGPROT" not activated

2EETP345 14:09:14: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGSUB "

2EETP334 14:09:14: error in DDL, nametab for "/SAPDMC/LSGSUB" not activated

2EETP345 14:09:26: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSGSUBT "

2EETP334 14:09:26: error in DDL, nametab for "/SAPDMC/LSGSUBT" not activated

2EETP345 14:09:38: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOALG "

2EETP334 14:09:38: error in DDL, nametab for "/SAPDMC/LSOALG" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOATT "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOATT" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOCOD "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOCOD" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSODOC "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSODOC" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOFIL "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOFIL" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOFIS "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOFIS" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOFIW "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOFIW" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOFLD "

2EETP334 14:09:50: error in DDL, nametab for "/SAPDMC/LSOFLD" not activated

2EETP345 14:09:50: Retcode 1: SQL-error "8144-Procedure or function sap_atomic_next_typemodfield ha

2EETP345 s too many arguments specified." in DDL statement for "/SAPDMC/LSOINF "

2EETP334 14:09:50: error in DDL, nametab for "VTEST10" not activated

1 ETP111 exit code : "8"

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

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD011020.MS1

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

1 ETP111 exit code : "0"

Regards

Kiran Umbare

[rajesh_gupta11 · Accepted solution]

Delete from sapr3.DDXTT~;

I read the follwing note in the unicode and conversion guide:

Make sure that tables DDXTT, DDXTF, DDXTF_CONV_UC and DDXTT_CONV_UC

are empty!

[markus_doehr2]

Is this SQL-Server?

Markus

[Former Member]

Yes this SAP on SQL 2005. the LOG files are SAP Log files. I think this may be SQL error

Kiran Umbare

[markus_doehr2]

to me it seems that a wrong procedure is called. I'd open an OSS call and let the support have a look on the system.

What you can try to do is to download the latest SAPEXE and SAPEXEDB patch, stop the system and update the kernel and try again.

Markus

[Former Member]

Hi Kiran ,

Can u letme know the path of the software you have downloaded for upgrade of 46C to ECC 6.0..

Find the note numbers from the error you got and i think you might get your solution.may be some parameters have to been changed.I had some error related to SQLSERVER,but could find solution for most of them.