How to delete a restart log ?

[Former Member]

Hi,

I worked with an Incremental Conversions in SE14 to convert a table, and an error is accured.

So I am getting this message " <tablename> is locked because a restart log exists" when I want to fix this error in SE11.

How can I fix the problem? please.

Thanks.

[Former Member]

hi Moutaa

make it clear plz. r u talking about INCV transaction?

thnx

prashant

[Former Member]

I talk about SE14 (the database utility)

SE14 -> BD requests -> Incremental

Yes, the take me to ICNV transaction!

Edited by: Noureddine MOUTAA on Jun 27, 2008 1:11 PM

Edited by: Noureddine MOUTAA on Jun 27, 2008 1:20 PM

Edited by: Noureddine MOUTAA on Jun 27, 2008 1:36 PM

[Former Member]

This message was moderated.

[Former Member]

For the moment my table is locked. So, how can I unlock it?

[ThomasZloch]

>

> I would like to mention in my own way of understanding.
> 

your own understanding? that following text is "borrowed" from here:

http://help.sap.com/saphelp_nw04s/helpdata/en/1c/525643a38a11d194a100a0c930df15/content.htm

[Former Member]

Thanks Thomas.

I correct my mistake.

Noureddine.

As an corrective action, If this helps you.

YOU CAN TRY, I am not sure:

If development workbench is locked, during import of shadow tables. The locking and unlocking can be done by:

tp unlock_eu <SID> to unlock

tp lock_eu <SID> to lock the workbench again.

if your R/3 system is locked:

tp unlocksys <SID> to unlock.

tp locksys <SID> to lock again.

Regards Harsh

Edited by: Harsh Dave on Jun 27, 2008 9:47 PM

[Former Member]

Sorry, but I'm didn't understand what do mean or who to do this :

tp unlock_eu <SID> to unlock

tp lock_eu <SID> to lock the workbench again.

if your R/3 system is locked:

tp unlocksys <SID> to unlock.

tp locksys <SID> to lock again.

What is SID?

there is any transaction that allow me to do this?

[Former Member]

Hi friend.

Sorry, to get back that late.

I want to ask you one thing.

Which action caused this locking, try to recollect and supply me the information and what was the purpose of incrementation.

Was It during upgrade?

I have looked upon some features in SE14.

It may be that your table might be inactive so the partially inactive data would be not accessed. So, this might be the cause during the conversion process.

So, Go to SE14 and enter your table name and press EDIT.

Click on ACTIVATE & ADJUST DATABASE.

It will take some time depending upon the contents inactive.

So, be patient.

Else, If you afford to delete and create a new table, please do that and read all instructions of the perform assistant.

For the time being supply me the details of your situation, At what point it happened and what was the purpose of your table conversion.

Regards Harsh.

And may the force be with you.

[Former Member]

Hi,

I am back with some important points.

It seems you did not read the

SAP HELP LIBRARY

carefully before conversion process.

For more details read the LIBRARY or ONLINE HELP under category ABAP DICTIONARY->ADJUSTING DATABASE STRUCTURES->CONVERSION PROCESS.

The concept is that when you convert any table it goes through a series of conversion process:

1. Setting a lock.

2. Renaming table.

3. Activating tables.

4. Reloading data.

5. Deleting QCM (differes case to case) table.

6. Rename table and creating secondary indexes.

7. Removing the lock.

According to *SAP HELP*:

[Please read this in help as it contains the description of the same problem: "If the conversion terminates, the table stays locked is a reset log is written. Each successful step of the conversion is recorded in this reset log. The restart log is deleted together with the lock when the conversion has been completed. If the conversion terminates (see Conversion Problems), you can find the place where the conversion terminated in the reset log (last step to be executed).]

-

-

---

Another important tips from the

help.sap

:

[You must clean up terminated conversions! Programs that access tables might otherwise not execute correctly. You must find out why the conversion terminated (for example overflow of the corresponding tablespace) and correct it. You must then continue the terminated conversion (see Continuing Terminated Conversions)].

During this process some fault can lead to terminated conversion which keeps the table in locked condition.

To unlock this table, we need to resume the terminated conversion.

These are steps recommended by SAP to resume terminated conversions:

Procedure:

In the initial screen of the ABAP Dictionary, choose Utilities ® Database utility (Transaction SE14).
The initial screen for the database utility appears.

Select object type Tables, enter the table name and choose Edit.
You will go to the maintenance screen for database tables.

Choose  Analyze adjustment.
The next screen lists the conversion steps that were processed correctly. It also shows the status of the tables involved in the conversion (table with old structure, QCM table and table with new structure). It can also be used to display the existing syslog entries or short dumps.

Choose Object log.
You can usually find out the exact cause of the termination from the object log. If the object log does not provide any information about the error, you have to analyze the system log or the short dumps.

Correct the errors found in the object log or syslog or in the short dumps (see Conversion Problems).
The conversion can usually only be continued once the error causing the termination has been corrected.

Go back to the previous maintenance screen and continue the conversion there with Continue adjustment.
Result

Result:

The system now tries to continue the conversion from the termination point.

Besides Continue adjustment, there is also the option Unlock table. This option only deletes the lock entry that exists for the table. Never choose Unlock table for a terminated conversion if the data only exists in the temporary table, that is the conversion terminated after Step 2 was completed and before Step 4 was completed.

Hope this mobilizes your situation.

Regards Harsh

[Former Member]

Hi,

Also, To see the terminated conversion process.

GoTo DB Requests->Terminated.

double click on the line and see the details and the follow the conversion process as stated in the post before.

Regards Harsh.

[Former Member]

Here is the steps to make the problem

1 - Define a table ZZTAB1 and some fields (MANDT, F11, F12)

2 - Define a table ZZTAB2 and some fields (MANDT, F21, F22)

3 - Save and Active both of them

4 - Change the type of ZZTAB2-F22 to CURR

5 - Put ZZTAB1 as table reference of ZZTAB2-F22

6 - Put F13 (name of a field does not exists) as field reference

7 - Save & Active (don't about the system message)

8 - Try to adjust the table with INCV transaction

Here the system block ZZTAB2, so I can't change its definition into SE11 :s

I want a solution without adding the field F13 in ZZTAB1

[Former Member]

Thanks.

I have noted down your problem and I am working on the issue.

Will get back to you as soon as possible.

Regards Harsh.