nametab for "VZFZE" not activated

[Former Member]

Hello,

We would like to ask for any help in case you have encountered this type of error:

MVNTABS ERRORS: ddlntabs and RETURN CODE in PD991030.EC2

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

2EETP345 12:21:37: Retcode 1: SQL-error "22859-ORA-22859: invalid modification of columns" in DDL s

2EETP345 tatement for "VZFZE "

2EETP334 12:21:37: error in DDL, nametab for "VZFZE" not activated

1 ETP111 exit code : "8"

We are currently doing an enhancement package 4 on our ECC6 and we are stuck on "downtime" phase with this type of error.

Thanks in advance for your reponse.

[sunny_pahuja2 · Accepted solution]

Hi,

This error generally comes in upgrade when upgrade tries to change data type of column XVAR700 from CLOB to VARCHAR2(3600).

When we faced this problem we took backup of the table then changed the data type of this column to VARCHAR2(3600) manually. And it went through.

Thanks

Sunny

[Former Member · Accepted solution]

Hi Sunny,

Thanks for the response.

Could you happen to tell us the command you have used in :

- backing up table

- altering the data type

I have made a backup on the database already (datafiles) but for certain table "VZFZE" not yet.

Hope to hear your response soon. Thank you.

[Former Member · Accepted solution]

Hi Sunny,

Hope you could help us on our problem. We have been stuck on this problem already and we haven't gotten any solution yet.

Could you let me know on where did you change the data type of this table via transaction code se11 or via sql?

Hope to hear your response. Thank you.

[Former Member · Accepted solution]

Hi Jaypee,

If you have a valid backup of the table or the database. You could modify the table manually at sql prompt.

Use:

ALTER TABLE SAPEC2.VZFZE MODIFY XVAR700 VARCHAR2(3600);

If this results in the same error, then you could change the table by renaming the column. Please check link: http://it.toolbox.com/blogs/oracle-guide/minitip-18-changing-a-column-data-type-21828

Try this option if nothing works.

[stefan_koehler]

Hello Jaypee,

your error .... "ORA-22859: invalid modification of columns".

Now let's check at first the table definition (copy and paste from my ECC 6.0 system with any EPHs).

SQL> desc SAPSR3.VZFZE ;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 MANDT                                     NOT NULL VARCHAR2(9)
 BUKRS                                     NOT NULL VARCHAR2(12)
 SVORGANG                                  NOT NULL VARCHAR2(30)
 LFDNR                                     NOT NULL VARCHAR2(9)
 SBUAKT                                    NOT NULL VARCHAR2(9)
 SATZART                                   NOT NULL VARCHAR2(30)
 SOBJEKT                                   NOT NULL VARCHAR2(30)
 VARLNG                                    NOT NULL NUMBER(5)
 XVAR700                                            CLOB

And now let's check the service market place for informations about "ORA-22859" ... and find sapnote #1160950.

This error may occur when you activate a table, in the phase PARCONV_UPG of an upgrade, or when you import a Support Package.
Reason and Prerequisites
The field of the relevant table has a DDIC length (in a Non-UNICODE case) of between 2000 and 4000 or of between 666 and 1333 in a UNICODE case. This field has the data type LONG or CLOB on the database.

Regards

Stefan

[Former Member]

Hi Stefan,

Good day.

Thanks for your response. This is actually the content of the table:

SQL> desc SAPEC2.VZFZE;

Name Null? Type

-

---

-

---

-

---

MANDT NOT NULL VARCHAR2(9)

BUKRS NOT NULL VARCHAR2(12)

SVORGANG NOT NULL VARCHAR2(30)

LFDNR NOT NULL VARCHAR2(9)

SBUAKT NOT NULL VARCHAR2(9)

SATZART NOT NULL VARCHAR2(30)

SOBJEKT NOT NULL VARCHAR2(30)

VARLNG NOT NULL NUMBER(5)

XVAR700 CLOB

I tried to implement the said note but it prompts that version 2 of the note does not exist. The current release of the note is on version 3.

Would there be a way to do it via sql? Thanks in advance.

[stefan_koehler]

Hello Jaypee,

> I tried to implement the said note but it prompts that version 2 of the note does not exist. The current release of the note is on version 3.

Why not opening just a sap call to get the sapnote fixed instead of executing unsupported manual steps.

Are you sure that the problem is fixed after the manual undocumented step (i wouldn't)?

Do you know the exact table definition after upgrade (i don't know) ?

My suggestion .. open a sap call refering to the mentioned sapnote and get a fix for it.

Regards

Stefan

[Former Member]

Problem resolved.