Anyone see this error before, BCV does not succeed as a result.

Question

While running a BCV which used to execute successfully, I am getting the following errors:

2008 07 10 17:32:33 wwwpdcpsoraca02 Details of the Devices at the time of failure: Symid: xxxxxxxxxxxx;DEVICE-1 : 00FF 04E7;
DEVICE-2 : 00FD 04E9;
2008 07 10 17:32:33 wwwpdcpsoraca02 A Solutions Enabler function call failed with SYMAPI_C_CONSISTENCY_ALREADY_SET(3,654). Reason: Consistency window was already opened on some devices.
2008 07 10 17:32:33 wwwpdcpsoraca02 026150 ERROR: Function Symmlib_Split failed.
2008 07 10 17:32:33 wwwpdcpsoraca02 026084 ERROR: Storage Services operation ExecuteReplication failed with an error as follows: Storage Services has terminated with an error.
2008 07 10 17:32:33 wwwpdcpsoraca02 026084 ERROR: Storage Services operation processExecute failed with an error as follows: Storage Services has terminated with an error.

Any help would be greatly appreciated.

desimus · Answer

Sorry, forgot to mention that this is RM 5.1.1.0 running on Windows 2003 server. The host server is a Solaris 10 server, running Solutions Enabler 6.4.2.

desimus · Answer

Found a primus that looks to be a very similar issue, I've opened a case with EMC referencing primus emc178909. Just incase anyone else ever faces the same issue, I'll report back any info from the case.

desimus · Answer

Nothing that support provided for me to run, corrected my issues. PSE dialed in and cleared the condition rather quickly. This is pretty much what the primus stated, but for whatever reason support kept having me try various things before they cleared it. Just FYI in case this happens to anyone else, call support and tell them to clear it for you, just as the primus says.

AranH1 · Answer

That is interesting, I have had similar experiences. I have clariions and a sym, and use RM 5.1 to manage clones for development use with the cloning operations occurring daily. About once every month or so the clones fail on the sym (we are using STDs and TimeFinder Clone for the operations through RM). After calling support and trying to resolve the problems through SE commands, the PSE lab has to dial in and clear some bits to resolve the issue.

Each time this occurs it requires the PSE lab to fix it. This has happened often enough that I have tasked my local Services Manager to open a case to investigate why this happens with our sym. As you probably know, it can take a few days before the PSE lab will actually fix the problem, and that is time that our developers don't have production data to work with.

Replication Manager

Anyone see this error before, BCV does not succeed as a result.

Was this post helpful?