Upgrade from 4.6C to ECC 604 SP 5 stop on phase PMVNTAB_VIEW

[Former Member]

Hello,

we are upgrading from an SAP R/3 4.6C to a ECC 604 SP5.

The upgrade is now in the downtime phase (standard strategies) and it stops on phase PMVNTAB_VIEW due to an DDL error in a view creation.

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

MVNTABS errors (DDL) and RETURN CODE in PD070310.DEV

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

2EETP345 11:47:23: Retcode 1: SQL-error "907-ORA-00907: missing right parenthesis" in DDL statement

2EETP345 for "ZHRP10001 "

2EETP334 11:47:23: error in DDL, nametab for "ZHRP10001" not activated

1 ETP111 exit code : "8"

We discover what is the error, and if we run the sql statement by hand it works.

Now we wish to correct the sql statement that run the SAPUp, but we don't knwo where it is stored?

Any idea?

Thanks in advance for your support.

Regards

Matteo Stocco

[paul_power]

Hello Matteo,

Regarding the error, please carry out a consistency check

of table ZHRP10001.

If the termination occurs in ABAP Open SQL, during an upgrade or

when applying transports / support packages, an inconsistency

between R/3-DDIC, R/3 nametab and Oracle DDIC is possible. In this

case, check the consistency of the runtime object and the database

object using transaction "SE11 -> <table> -> Execute -> Utilities ->

Database Object -> Check" and "SE11 -> <table> -> Execute ->

Utilities -> Runtime Object -> Check". If an inconsistency is

reported, correct it. In the case of problems, please update.

Regards,

Paul

[Former Member]

We are running an upgrade.

Now we are in the dowtime phase and it is not possible to start the system, so I'm not abble to run a consystency check.

But a a similar system in release 4.6C the view doesn't exist in the db.

The problem is that SAPUp run this where condition

T2."MC_STEXT" LIKE 'ACQUISTI - AUTORIZZAZIONI BASE MENO%

while the correct is

T2."MC_STEXT" LIKE 'ACQUISTI - AUTORIZZAZIONI BASE MENO%'

[Former Member]

To by pass the problema we worked at db level on the table DDXTT and DDXTF.

We delete from these table the entries for the view ZHRP10001 that has the problem.

The upgrade and unicode conversion goes on without problem.

But the view ZHRP10001 has some problem (incosistency DDIC and DB, but it is not important for us), our development team are working to solve the problem.

It is a view and not a table...so no data lost...

Bye