This is a known issue affecting VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Appliance 5.1.x.
Currently, there is no resolution.
Running VMware vRealize Orchestrator with internal or embedded databases is only supported for testing purposes. Use an external database if your VMware vRealize Orchestrator is in a production environment.
If you are using the embedded database, work around this issue by performing these steps:
- Set up a new VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) appliance and configure it with the same plug-in and configuration as your original system.
- Copy the database files from Orchestrator_install_DIR/app-server/data, on the old VMware vRealize Orchestrator server to Orchestrator_install_DIR/app-server/data on the new VMware vRealize Orchestrator server.
- Copy all files and folders beginning with internal.hsqldb.*.
- Verify the permissions for all the files copied that are set to owner/group of VMware vRealize Orchestrator.
- Restart the VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) server.