what db is this ? if it's oracle, get addm/awr reports? from when the cleanup started for about an hour or two out and open a ticket.
Its on Oracle DB 11g Enterprise 64bit. We'll get a ticket open.
We have faced the same problem when we ran the DB clean up. Job got stopped while cleaning up patch. We are really wonder why it is stuck at that point as we are not using bladelogic for patch management in our environment.
Application server: bladelogic 8.6
DB: Microsoft SQL
Anybody has any idea, could you please suggest. There are loads of bugs in 8.6
We have a same issue. Running DB cleanup for the first time and last messge is ""Executing stored procedure: PatchResult".".
Cancelled the job from the bladelogic console, assumed all fine BUT it seems it is still running SP on the DB server. Procedure
dbm_online_del_jres is still running on SQL server and TLogs are filling up.
What was your solution?
We are on 8.6 SP1, SQL 2008 R2 DB. We primarily use bladelogic for Application Automation and do not use it for Patching.
For the cleanup problem Log a support case - the team will be able to help you resolve this problem
For your other comment, please upgrade to BSA 8.8 - it contains resolution for known problems with BSA 8.6
Log a support case - the team will be able to help you resolve this problem
"There are loads of bugs in 8.6 " - specifically what problems are you having w/ 8.6.<what version>?
why did you cancel the job ?
bcz it has stuck in the process of patching data clean-up for aboout 5 hours not progressing further. However we not using bladelogic for pathing in our envrionment.
In agreement with Bill and Jim, submit a case with BMC and they will resolve with you. We submitted our support case and BMC assisted in resolving.
We just had 6 hour window to run the DB cleanup as it was on a shared server. Thought setting the MaxDuration in the job would have stopped the job gracefully but it did not. Reluctantly had to cancel !!!
In any case, we are working with BMC support. They have provided us with a DB Hotfix to apply for next time we run the clean up job.
"ISS04468201 - BSA Recommended Database Cleanup PatchResult
job caused BSA stop working"
We are rolling back the DB to start again...