Have you enabled EnableRetentionPolicy ?

Also what value is set for RESULTS_RETENTION_TIME. Property dictionary view->job. 0 means do not delete.


A restart would be required after updating above.

Also try executing below command to see what all is expected to clean during this clean process.

select count (*) from depot_object where is_deleted = '1';

If there is not records returned then you may have set in correct RESULTS_RETENTION_TIME

records are there to be deleted but script failed to clean up then run the job w/ debug mode enabled and attach log here.


select * from delete_tasks;

what's in there?  what backend is your db ?  are jobs running ok while this is happening ?

so you are running w/ debug mode. Did you see anything in the log ?

You should be running the cleanupHistoricalData cleanups before you run cleanupDatabase.  Was that done ?

https://docs.bmc.com/docs/display/bsa83/CleaninguptheBMCServerAutomationdatabase

I doubt there is anything wrong.  cleanupDatabase will run the stored procs for the various historical cleanups, and if you haven’t been running them regularly and there is a lot of data to delete, then this might take a while.  you can see if there are active sessions in the db and probably the update xxx is_deleted  = 1 or deletes will be associated w/ the cleanups.

Well, if cleanupDatabase is running the same stored proc, it’s not a great idea to try and essentially run the same thing again.  though for that error there’s a known fix for it (the FK error in job_schedule)

Right…because it’s already running as part of cleanupDatabase?

What db back end do you have ?

uh...

blcli -v defaultProfile Delete cleanupDatabase 6 false 240 is now stuck

[Thu Jan 22 11:23:43 GMT 2015] Executing available patches.

[Thu Jan 22 11:26:39 GMT 2015] Successfully executed available patches.

[Thu Jan 22 11:26:39 GMT 2015] Executing stored procedure: ComplianceResult

[Thu Jan 22 11:26:49 GMT 2015] Finished Executing stored procedure: ComplianceResult

[Thu Jan 22 11:26:49 GMT 2015] Executing stored procedure: SnapshotResult

I started it almost two hours ago

?  so you have run cleanup database.  and it's been 'hung' for 2 hours ... right ?

get and awr and addm covering from when you started cleanupDatabase.  see if there are any blocked sessions...  if not, i'd just let it go.  and then go read the doc i linked to and open a support ticket to fix the fk issue in job_schedule.

Ticket # ?