Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Mourad2

16 Posts

684

August 2nd, 2008 02:00

Unable to stop running job

Hi gus,
We have replication manager SE in our data-center running on windows server 2003.
I have one job that I could not to stop it and it's running for long time.
When tried to expire the replica I received this error message:
Cannot expire replica XXXXXXX, This replica is locked by an other replication manager operation, RM was unable to expire the replica
What can I do to stop it please ?

Regards

AranH1

2.2K Posts

August 4th, 2008 07:00

You won't be able to expire the replica if the job is running, and if RM Console won't allow you to stop the job then you could take the brute force approach and close the console, then stop the Replication Manager Server service (irccd.exe).

This of course will kill any other jobs you have running.

JamesBEMC

257 Posts

August 6th, 2008 04:00

Hi there

The problem here could be that the production or mount host could have been rebooted during an actual job.

RM/SE utilizes an xml file-based databaase. These .xml files contain values of job states, for example if they are starting, replicating, mounting, restoring, etc etc.


Firstly, stop the RM agent on all hosts when no replication is running and start them again.
Try to expire the replica which is hung in the console showing as running.

If this does not succeed, it probably means that one or more replica properties files have a state of running in them, which is blocking the next job from running.


I suggest to use this opportunity to upgrade to the full version, RM 5.1 which has far better resilience to issues like these.

Was this post helpful?

View All

0 events found

No Events found!

Top