Hi ,
"There is a collection in progress for this collector. Changes are not allowed to be submitted until the collection completes."
We are not able to stop the identity collector.Though it showing the above message but actually its not collecting any data. what to do please suggest.
I believe only way is to stop running collections are by restarting app server. You may also try restarting DB server.
Restarting the appliance will abort any running collectors, database restart is not required.
Vishwanath Babali Rajkiran Paul
HI All,
I am facing the same issue like Rajkiran I tried restarting the application server. Still getting the same error.
Any Idea how we can resolve this ?
Any help is much appreciated .
Regards,
Sabthami Subramanian
Did you try restart the Database ? If not please give a try.
Regards,
Hemanth
Hi Hemanth,
Thanks for the reply !
I have tried restarting all the modules in the below mentioned order but that dint work.Still getting same error.
service afx_server stop
service aveksa_server stop
service aveksa_server stopdb
service aveksa_server startdb
service aveksa_server start
service afx_server start
Is that's fine to Stop and Start the DB while application is running ? Is that is a correct approach to follow ?
Regards,
Sabthami Subramanian
Please give try the below steps
sudo service aveksa_server stop
sudo service aveksa_server startoracle
sudo reboot
sudo service aveksa_server startoracle
sudo service aveksa_server start
Regards,
Hemanth
Hi Hemanth,
Just to confirm, the second step is "sudo service aveksa_server startoracle" is that is startoracle or stoporacle ???
Regards,
Sabthami Subramanian
Sorry for the typo. It was stop
sudo service aveksa_server stop
sudo service aveksa_server stoporacle
sudo reboot
sudo service aveksa_server startoracle
sudo service aveksa_server start
Regards,
Hemanth
Hi, Do you see an active run on the Monitoring page for that collector. If not, please do the following steps.
1. Run below query replacing by providing the collector id for the source.
select * from t_data_run_tasks where source = ? and status = 'InProgress' and
type in ('DataCollection', 'DataProcessing', 'DataPreProcessing', 'DataObjectProcessing', 'DataRelationshipProcessing')
2. Take note of the RUN_ID's and see how the tasks in that role are looking for that run. You might be seeing the run as completed but one/more tasks as InProgress. This is the reason why collector edit is not being allowed.
3. If the data runs are not latest, simply use below query to mark them as Aborted(use correct source) and commit changes. The collector should be editable after that.
update t_data_run_tasks set status = 'Aborted' where source = ? and status = 'InProgress' and
type in ('DataCollection', 'DataProcessing', 'DataPreProcessing', 'DataObjectProcessing', 'DataRelationshipProcessing')
The tasks being 'InProgress' in the completed runs is a bug. Please raise a ticket for that.
Hi Venkata Ramana Reddy Kanaparthy,
Make sense to the way you suggested.
Out of curiosity, delete the IDC.pkb file from the below location will be reflected in Aveksa UI ?
aveksa.ear/aveksa.war/WEB-INF/database/packages/collectors/IDC/<IDC Collctor Name>.pkb
Regards,
Hemanth
Deleting that file will not affect anything on UI but they should not be deleted. They will be required when you want to import some older dump and migrate it to existing version or even when you simply want to run a migration.
What do you you expect to achieve by deleting them?
Venkata Ramana Reddy Kanaparthy
I was under impression that IDC collectors would be removed from Aveksa UI if we delete the respective <IDC>.pkb file
Regards,
Hemanth
Restarting the appliance will abort any running collectors, database restart is not required.