vCO Database maintenance

[tschoergez]

Hi,

the Installation Guide states:

1 Log in to the Orchestrator configuration interface as vmware.
2 On the Generaltab, click Advanced Configuration.
3 Fill in the Max number of events text box.
To track every change in your infrastructure, enter 0 (zero=infinite). This means that the server never rolls
over, but it might become unavailable. Database administrators must periodically clean the server and
archive events.
4 Fill in the Max number of runs text box.
After you reach the maximum number of runs, the rollover process starts. If you do not want the rollover
process to start, enter 0 in this text box. If you enter 0, your database continues to extend.

Is there any documenation (or ready-to-use SQL scripts), what a database administrator has to do to clean the server?

Regards,

Joerg

[cdecanini_]

To clean up the events you can just open a client and right click "Delete all workflow runs" on the top level of your workflows.

Christophe.

[tschoergez]

ok, that does half of the job 🙂

Is there a way to delete the (still to the workflow linked) events in the GUI?

[cdecanini_ · Accepted solution]

You are right. These are not more reported by the GUI but are still on the tables. I was under the impression it was emoving them from the tables as well.

You can either adjust the purge mechanism to keep only 1 token per workflow and 1 event and wait up to 1 hour (purge is hourly if I recall well) or remove all the rows in the vmo_workflowtoken and vmo_logevent tables.

If you want to keep some you can also reindex your tables (db vendor / db version specific) to greatly improve performance and keeping important data.

Christophe.

[tschoergez]

So the configuratin setting is the way to go in my use case 🙂

Thanks!

Regards,

Joerg