Database Utility (SE14) Conversion Error (Step 4)

[Sandra_Rossi]

Hello Gurus,

I recently added some custom fields in Material Master 'Customer Data' Tab. Then I changed those ZZ fields domains and activated them... Then I adjusted table MARA in SE14 and now its stuck at Step 4.

[Sandra_Rossi]

2180238 - DDIC Inconsistency Check (with video)

[Sandra_Rossi]

If the message says to "see object log and analysis", you should at least read the log, and at least attach it to your question...

[Former Member]

Dear Sara,

I read the log and the log had errors:

• MARA-ZZ_FIELD1(specify reference table AND reference field)
• MARA-ZZ_FIELD2(specify reference table AND reference field)
• MARA-ZZ_FIELD3(specify reference table AND reference field)
• MARA-ZZ_FIELD4 (specify reference table AND reference field)

I corrected these errors and thus I had no inconsistencies in SE14 -> Runtime Object -> Check..

Screenshot is attached for your reference.

[Sandra_Rossi]

As it stopped in step 4 and you have corrected the errors, there's no issue to simply "Continue Adjustment".

[Former Member]

Dear Sandra,

It doesn't proceed. If I click on "Continue Adjustment", it starts its process in background, then simply displays "Object Log" . Upon rerunning SE14, it still shows the same error as shown in picture attached in question

[Sandra_Rossi]

You say "in background". So, there's a job DB-TABLMARA running? What about it?

What do you mean "rerunning SE14"? (I hope you only did "Continue adjustment").

[Former Member]

What I meant by "in background" is that SAP does it's own process as I see profress indicator in status bar with message "Table MARA being adjusted"...

There's no job running by the name of "DB-TABLMARA" when checked in SM37

And yes, I only did "Continue Adjustment"

[Sandra_Rossi]

You say "progress indicator", so I guess that the activation is in "dialog"? i.e. your SAP screen is locked while SAP is activating the table? Dialog and background are two almost opposite terms in SAP. It will run for a long time. So, you have to wait until it's done I guess, right? But you say that it shows the same error? How long does it last before showing the same error? Did you try to exit SE14 and re-enter and click "Continue adjustment" again?

[former_member876]

Please check sap note "1925322 - How to roll back table conversion"

[Former Member]

Dear Mukesh,

That note is regarding to when "Table conversion stopped with "Error in step 5" in SE14:"...

Mine got terminated at Step 4, so i don't think this note is applicable at the moment

[former_member876]

Ohh..my bad, it's in next step, please ask basis to keep a copy of table data in temp table, for worst case. I will wait for you to explain more on background job, as pointed out by Sandra.

[albanleong]

I upvoted Mukesh's answer because I think it has the right steps to solve your issue.

But to be more specific, here's probably what you need to do

Step 1. Transaction SE14 - Table: MARA - select "Unlock table"

Step 2. Using FM DB_RENAME_TABLE - Pass in Parameter TABNAME_NEW = MARA and TABNAME_OLD = QCMMARA

Step 3. Transaction SE14 - Table: MARA - Select menu Table > Reconstruct

Step 4. (Since you said you've fixed the ZZ-fields error) Go to SE11 and reactivate MARA.

That should do it.

*** DISCLAIMER *** Given the fact that the OP's scenario is dealing with a standard SAP table (MARA), PROCEED AT OWN RISK.

[Former Member]

The note Mukesh shared is in regards if there's a termination at Step 5. My process terminated at Step 4.

Additionally, if I currently go to SE11 to activate "MARA" it gives messages as shown in screenshot.

Note: If I try to unlock table it gives me a warning:

"The original data is currently in a temporary table. For this reason, it is not possible to guarantee that all the data has been converted and copied to the new table. The temporary table is deleted with the next request to adjust the table. As a result, there could be a partial or complete LOSS OF DATA ! If you unlock the table now, the adjustment cannot be continued automatically at a later time. First try to correct the error and continue the adjustment. Use the object log and the sys log (SM21) for an error analysis. Really unlock table ?"

[albanleong]

Yeah - okay. The SAP warning is valid. Given the fact that this is a standard SAP table and I don't know if you have a new system or a pretty old system with tons of data, I'd say proceed with caution. Maybe have the DBA backup the data first on the DB level before attempting the steps in the OSS notes?

As for your point about the OSS note Step 5 vs your Step 4, I think the underlying issue is the same. The original DB table has been dropped and no longer exists in DB and you can't activate it. The steps outlined in the OSS note will restore the DB table BUT - the OSS note is dealing with a custom Z-table and you, have a potentially large/huge table.

Again. proceed with caution...