cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1375
Views
0
Helpful
5
Replies
Highlighted
Beginner

Prime Collaboration Provisioning sync stuck

Hi,

 

We have PCP v 11.6 and have a job set up to sync the infrastructure and users of a particular call processor. it is currently stuck for the past few days in "In progress" state and shows that it completed the infrastructure sync, but has been stuck on the user sync.

 

Any ideas how to force stop it?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

No. There is a value to be cleared in the DB.  Open a TAC case to get it fixed.  I suspect there is a stuck or stale user somewhere in the DB, possibly deleted in CM but not in PCP.  

View solution in original post

5 REPLIES 5
Highlighted
Cisco Employee

No. There is a value to be cleared in the DB.  Open a TAC case to get it fixed.  I suspect there is a stuck or stale user somewhere in the DB, possibly deleted in CM but not in PCP.  

View solution in original post

Highlighted
Collaborator

Hi there

 

There was a bug with similar kind in PCP v9. The workaround was to Abort the job and recreate it.

 

Batch provisioning jobs stop executing subsequent actions
CSCud53658
 
Description
Symptom:

Batch provisioning jobs stop executing without any errors.

Condition:

This has been observed with Cisco Prime Collaboration 9.0 when executing large batch jobs.

Workaround:

None. Abort the job and recreate a new job.
 
 
 
Hope this Helps

Cheers
Rath!

***Please rate helpful posts***
 
 
Highlighted

Rath!,

Wow 9.0 (first release of PCP) was about 15  or 16 releases ago. That bug was fixed long ago and batch error handling is much different now.

Most of the problems that can cause a sync to fail have been found and fixed during development of 11.0. We still see the stuck at 1% problem on rare occasions and have tracked down the root cause related to a stale entry in the PCP DB.

The display indicates the status of the sync flag, stopping at step 1, which may make you think sync is still running.  Until the flag is set to complete you cannot run the sync again. TAC can reset it and also clear out the stale DB entry that is causing it.

We have several improvements to the sync error handling planned for 12.6 (~Aug 2018) which will address the problem automatically.

Highlighted

That’s great. Thanks a lot Anthony for the detailed updated.

-Rath
Highlighted

I had same issue with 12.5.1862 version. 

Content for Community-Ad