Description of problem: The table RHQ_CONFIG_PROPERTY contains 43620376 rows. The purge is logged, but it not purging table RHQ_CONFIG_PROPERTY. Version-Release number of selected component (if applicable): RHQ 4.13.1 Database Product Name : PostgreSQL 9.1.15 JVM SUN 1_7_0_07 Linux x86_64 RHEL 5 How reproducible: Every time Steps to Reproduce: Actual results: The Data is not purged. Expected results: purging of the table RHQ_CONFIG_PROPERTY Additional info: see in attachment server.log (DEBUG)
how to purge this table with batch or script ?
The configuration database does not get "purged" on purpose. If you purge it, you lose your inventory data and your RHQ system would be corrupt or non-functioning. Are you instead thinking of "configuration history?" If you want to get rid of your configuration history then do so from the Reports > Configuration History page. Simply select the configuration update history you no longer want and delete it. Alternatively, you can do this on specific resources from their configuration history page.
Closing due to insufficient data but there does seem to be an issue with orphaned configuration entries. This could be what comment 0 is actually reporting. Bug 1323332 has been captured with the relevant details -- or what little is known -- in regards to the orphaned configuration issue.