Hello @Luciano

I don't have anything of this sort of size to event try to replicate with, but with a large TB then it will take time.

It appears the processing time was just 1.5 hours, the majority of the time (Beginn/Ende) will be from the data being read, before attempting to reorganise.

If you have the TB stored on a remote location, It's probably best to save it locally, which should speed things up- or perhaps run it overnight if you can.

You said

Luciano said:

the reorganization actually started 21 hours after I initiated it in MultiTerm.

am I missing something here-

The start time (today) was at 09.01 and ended today at 15.56

Hello @Luciano

I don't have anything of this sort of size to event try to replicate with, but with a large TB then it will take time.

It appears the processing time was just 1.5 hours, the majority of the time (Beginn/Ende) will be from the data being read, before attempting to reorganise.

If you have the TB stored on a remote location, It's probably best to save it locally, which should speed things up- or perhaps run it overnight if you can.

You said

Luciano said:

the reorganization actually started 21 hours after I initiated it in MultiTerm.

am I missing something here-

The start time (today) was at 09.01 and ended today at 15.56

Hi ,

Thank you for answering so quickly.

I initiated the reorganization in MultiTerm yesterday at 11:47 am, as my MultiTerm log reports (also I remember doing this yesterday ).

However, the result report after the reorganization finished says it started today at 9 am in the morgning, 21 hours after I actually initiated it.

Hi ,

Last week I initiated the reorganization within MultiTerm on Friday at noon. The process was successfully finished Monday 3.30 pm. The reorganization report said it had started Monday morning at 9.01 am. Interestingly, the start time of the reports coincides with my login time on my workstation. I work remotely via RDP. Does the reorganization need a user to be active on the computer? Is there an option to having it run in the background without having to be logged in?