Repository status: Started rolling back <1:d> records

[Former Member]

Hi experts,

I have a doubt about the 'Rolling back' option.

Correct me if I'm wrong, but I understand that this functionality should be used to recover the information of a record that contains wrong information after any change. Then, if you execute a roll back the system recovers the previous information (previous to last change done into the Data Manager).

On a easier way, comparing to Excel, it would be like the option 'Undo changes'. Am I right?

During last days, every time I check the repository status into the MDM Console, I see the following message for every repository loaded and running:

'Started rolling back <1:d> records'.

I don't know how this is achieved, why it's doing this and the way to deactivate it and see the 'normal' status 'Running'.

I've tried by unloading the repository and load it (updating indexs) again, by stop the MDM server and initializating again the server, stop the portal... but nothing changes, it always shows any repository under the status 'Started rolling back <1:d> records'.

I've been checking the MDM Console Guide and looking on this forum for threads related for rolling back, but I haven't anything that could explain why I see always this repository status into the Console.

We are on version 7.1.08.285.

Thanks for your feedback.

Regards,

Carlos Santamaría.

[Former Member · Accepted solution]

HI Carlos,

As suggested in earlier posts, you can check logs and traces to see if there is any information regarding this. Also you need to check MDS.ini file for following parameters:

Enable Slicing for Non-Bulk Operations : Check if it is set to True.

Enable Rollback Slicing : Check if it is set to True. Try making it as False and then check the status of Repository.

Rollback is non-bulk operation. In Console Reference Guide:

"Enabling slicing for a non-bulk operation requires two parameters to be set to True in mds.ini: the master Enable Slicing for Non-Bulk Operations parameter and the operation-specific parameter. To disable slicing for all non-bulk operations, set the master Enable Slicing for Non-Bulk Operations parameter to False. This disables non-bulk operation slicing regardless of the operation-specific parameters."

Kindly check this and let me know if this works or not.

Thanks and Regards,

Ankush Bhardwaj

[Former Member · Accepted solution]

Hi all for your replies,

I've checked the logs and traces for errors and warnings, but I haven't found anything related to rollingback.

The most similar message I've founded it's as follows:

ATTR(field: <1:d>, attrID: <2:d>, rating: <3:d>)

Component: Background_Thread@Workflow

File: Workflow.cpp

Operation: CatMgrDatabase::StartLoadThread

I've also tried by verifying and repairing the repository in case of errors, but nothing has changed. There were no errors when I've execute the option 'Verify'.

I've checked also the MDS.ini file, but parameter: 'Enable Slicing for Non-Bulk Operations was already set to False.

Parameter 'Enable Rollback Slicing' doesn't exist into the MDS.ini file.

Any other suggestion?

Thanks,

Best regards,

Carlos Santamaría.

[Former Member · Accepted solution]

In addition, what is exactly the meaning of rolling back at repository level?

What are the risks of having this status message?

It's used for recover previous information, so maybe I could lose new changes?

Thanks!

[Former Member · Accepted solution]

Hi Carlos,

Just for information, is this status in Repository affecting any operations of MDM like in Data Manager or Import etc?

You can raise OSS message for this issue to SAP. May be this is some bug introduced with SP08 only. Let us see what they say regarding this.

Thanks and Regards,

Ankush Bhardwaj

[Former Member · Accepted solution]

Hi Ankush,

No, it's not affecting normal operations in Data Manager or Import Manager.

I'll open the OSS and let you know.

Regards,

Carlos Santamaría.

[Former Member · Accepted solution]

HI Carlos,

It seems to me that repository is busy with workflows,also there are many data manager related operations.

Please check this status after stopping and relaoding repository.

Possibly there are to many notifications to data manager.

Please update.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

Sorry for late answer, but I was on holidays.

There are no workflows created, so this shouldn't be the cause for repository status 'Started rolling back <1:d> records.'

Do you have any other idea/suggestion?

Thanks,

Carlos.

[Former Member · Accepted solution]

Hi Carlos,

I think if you put all your workflows in not active state this would stop.

Please test this and update the thread.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi,

No, I don't have any workflow, so there is nothing to put in not active status.

Regards,

Carlos.

[Former Member · Accepted solution]

Hi Carlos,

Ok in Console check if any of the users have wrong email id i.e. incorrect/inappropriate format etc.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

No, none user has the email address informed.

All of them have this field empty.

Regards,

Carlos.

[Former Member · Accepted solution]

Hi Carlos,

Any update on the OSS message raised for this?

Kindly let us know as well. Thank you.

[Former Member · Accepted solution]

Hi Carlos,

Thanks for the update.Could you provde MDS.ini parameter set for SMTP setting.

It could be that either the server is too busy or time parameter set is too less.

Please update that here,also please provide the latest error like one provided earlier.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Ravi,

The parameter Mail SMTP Timeout is set to 1 in MDS.ini file.

[MDM Server\Databases\REPOSITORY_NAMESERVERMSQL_15_8_4_3]

Port=2000

Login=mdmuser

Password+=BA639K2CSUFF33IN762DOVSMG384873OKB07FC2

Stemmer Language=

Stemmer Variant=

Max Large Text Length=250000

Number of Rows Per Fetch=100

Max Initial MB to Retain=4

Max Send Failure MB to Retain=4

Workflow Detailed Report=False

Mail Server=

Mail SMTP Timeout=1

I attach an screenshot with a log that could be related to this status message.

Thanks,

Carlos.

[Former Member · Accepted solution]

Hi Carlos,

Thanks for the snapshot.It is now making some sense now.

Could you please update time interval based on the logs between 2 such entries.

Also,please update on OSS.

Thanks,

Ravi

[Former Member · Accepted solution]

HI Carlos,

Waiting for your input.

Thanks,

Ravi

[Former Member · Accepted solution]

Hi Carlos

First of all

Set your parameters "Workflow Detailed Report=True"

It help you to chek all WF activity in your repository reports.

You haven't seen any WF if you are not a launcher.

Maybe you have loaded many records and your WF have started immediatly but it rolling back now - for many records it may be very long process.

My suggestion - connect to Data manager as WF launcher and cancel all active of them.

I hope this help you to solve this problem.

Regards

Kanstantsin Chernichenka

[Former Member]

HI Carlos,

Please do the following -

Go through logs and traces and check for errors/warnings

Go through load report

Verify and if required reapair the repository after taking a backup

Let me know the results.

Thanks,

Ravi

[Former Member]

Hello Carlos,

Did you check the "Logs"? If not you can check to see if there are any activities going on the server.

If you don't find anything suspicious, please, check the MDS.ini file parameters with standards.

Let me know if this works.

-Ashwin