Hi,
We are having a problem related to one of our Application.
The Reconcile Process is getting stuck at 99%. Only 1 E-List item is not getting reconciled.
The same E-List item is not getting reconciled every time.
Initially when I had the problem, I tried to delete the E-list item and add it back. But still the problem continues.
I have one solution, to do client side reconciliation.
But I was wondering, if there is any way to reconcile that particular item from back-end using database Application Schema.
Please advice.
Thanks,
Anand
Are you getting any errors in the log? That would be useful in helping you. Is it stuck and not moving or does it move to FAILED or CANCELLED? If so, I found this useful in the past: http://www-01.ibm.com/support/docview.wss?uid=swg21579043
Read it carefully and determine if it actually addresses your issue before trying it but I know that last year I had to follow these steps and it fixed the problem when I had a reconcile that wouldn't complete.
Be sure to post more detailed error information so someone here can provide you with some guidance.
Thanks Danno for the reply.
The status of reconcile is RUNNING. It shows 99% Succeeded. But this state lasts forever.
The Log file is indicating very little about Reconcile.
The Error message is :
error calling logEnd with context=openModel: context stack is empty
That is a new one for me. When was the last time you rebooted the job servers?
I guess more importantly, did you resolve it yet? ;D
Try using the EPReconcileProgressViewer.exe (called smth like that, resides in cognos\bin folder) and it's repair functionality. Sometimes it works ;)
Quote from: ykud on 29 Feb 2012 12:11:43 AM
Try using the EPReconcileProgressViewer.exe (called smth like that, resides in cognos\bin folder) and it's repair functionality. Sometimes it works ;)
That would be in the link I posted. Great tool! I have to use it a couple times now.
Quote from: Danno on 29 Feb 2012 10:48:11 AM
That would be in the link I posted. Great tool! I have to use it a couple times now.
Sorry bout that, was answering from the phone and didn't check the link first.
The couple times it worked for me were both recprogress flag issues(calculated incorrectly at some point) and you can fix that with zeroing this field in nodestate table of application db.
But using this tool is more impressive, since it's rarely known )