Compliance System Case - Searches
Hi All,
I am preparing my EV environment to upgrade from v8.0.3 to v9.0.3, the first component that i am going to upgrade is my CA/DA server along with CA/DA clients.
When doing some pre-upgrade checks i found bunch of Searches which were not completed and were in either 'Pending Acceptance' or 'Pending Acceptance (with error)' out of these identified searches i could fix the one's which belong to the valid CA departments. But i also see bunch of searches for "Compliance System Case" in Pending Acceptance mode.
How can i clean these search types so that i don't run into any issues while doing the upgrade?
Here is the article that i am following to identify the pending searches in the system.
http://www.symantec.com/business/support/index?page=content&id=TECH63230
Thanks in Advance!
Satya
I was able to activate Search button, by adding a monitored employee and a department reviewer...
But unfortunately i couldn't see any searches listed for that department, also i tried above sql query to delete the enteries from SQL but it didn't work and 0 rows got affected...
Reached to Symantec support and got this query which deleted the pending search entries from the Compliance database.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
--Declare the Variable for SearchIDDECLARE @searchid int--Declare the cursor for the deletion process and get set the query for the cursorDECLARE search_delete CURSOR FORSELECT SearchID FROM tblIntSearches WHERE StatusID IN (3,10)--Start the deletion process and select the first search to processOPEN search_deleteFETCH NEXT FROM search_delete INTO @searchidWHILE @@FETCH_STATUS = 0--Start the block of code that will be processed until @@FETCH_STATUS = 1 (So all searches have been processed)BEGINUPDATE tblIntSearches SET StatusID = 4 WHERE searchid = @searchidEXEC usp_Search_DoRejecting @searchidFETCH NEXT FROM search_delete INTO @searchidEND--End the block of code--Once @@FETCH_STATUS = 1 close the cursor and deallocate itCLOSE search_deleteDEALLOCATE search_delete
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxHope this will help someone else stuck in the same situation as i was :)ThanksSatya