Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Database adjustment - Conversion failed at step5

Former Member
0 Likes
1,325

Hi All,

When I changed the field length from char7 to char5 for a ZField, which is being used in many other tables like BSEG and COEP, SAP tried to convert all those tables. All the tables were converted and activated properly except for COEP.

Conversion process of COEP is failed at step 5 of the process defined by SAP.

Restart Log of the conversion:

1) Initialization was successful

2) Unload - Successful

3) Delete data - Successful

4) Activate - Successful

5) Reload data - failed

6) Create Indexes - Failed

When I open COEP table through SE11, it displays a information message saying " Table COEP does not exist in the database".

Please help me in correcting above mentioned issue.

Thanks for your time,

Regards,

Jalendhar

4 REPLIES 4
Read only

Former Member
0 Likes
999

Hey Hi ,

Did you try adusting the table using se14 transaction .

Regards,

Ragesh

Read only

0 Likes
999

Thanks for the quick reply.

I did that but it is failed to restart the conversion again. It says correct the conversion errors and try adjust the table.

Here are the errors

SQL0551N "SAPP02" does not have the privilege to perform operation "C

REATE TABLE" on object "ZP02#BTAB06D". SQLSTATE=42501

DDL time(___1): ........18 milliseconds

1) The SQL statement was not executed Error

sql:

DROP TABLE "QCM8COEP"

SQL0204N "SAPP02.QCM8COEP" is an undefined name. SQLSTATE=42704

DDL time(___1): .........1 milliseconds

.... QCM8COEP was already removed

2) Creation of table COEP or primary index in DB failed

3) Error in step COEP-STEP5

Please suggest a way to fix this issue. Thanks again for your time!

Read only

0 Likes
999

Any suggestions please..

Read only

0 Likes
999

Hi Jalendhar,

How did you resolve this issue?

We have the same issue with VBKD table.

Your reply will be appreciated.

Thank you

Prasuna.