

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Policy DBSPI Discovery already running - new request to run is
I'm seeing this in several of the system.txt files on systems running DBSPI 11.5 for MSSQL.
agtrep (3756/3996): (agtrep-41) Policy DBSPI Discovery already running - new request to run is ignored
Does anyone know how to correct the issue?
Say "Thanks" by clicking on Kudo's to the left 🙂


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
The previous scheduled DBSPI discovery policy script is stuck and not exiting. Check the ps -ef output for hung dbspi discovery processes else restart the agent (you can use the om tool if there are multiple nodes with same issue).


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
there could be some .lock files which did not get deleted on the node and the new schedule finds the lock file and does not launch new discovery thinking the previous one is still active.....


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I don't think ps -ef will display the process information on a Windows Server 🙂
I was hoping to hear of a hotfix that has been released for this issue. Guess I'll have to open a case with HP. There are way too many systems to try to fix by hand...
Say "Thanks" by clicking on Kudo's to the left 🙂


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Oh OK, MSSQL .. didn't notice that ... try with agent restart if that works else HP ......