- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I 'fixed' that issue by the following steps:
- create a package in the orchestrator Client with all Workflows, Actions, resources, ...)
- Export that packages
- document schudle Workflows (paramtertes, time and so on)
- document how you Setup AD-Connection, SQL Connection for the workflows
- Change in Orchestrator webkonfiguration the database (and konfigure it)
- press under 'troublshooting' in the webkonfiguration to reinstall all plugins
- restart orchestrator service
- Import the package in the 'new' orchestrator
- create the SQL Databases for my Workflows again
- add the schedudle Workflows again (Feature request:. a automated way to Export / Import scheduled Workflows)
- finish
What I dislike ....
after checking the new database there was still no Table content_field_vmhost .. and there it made 'click' in my head.
That was one of a old, since months deleted table of one MySQL Connection i stored in the SQL-Ressources...
Can maybe someone confirm this as a bug:
- create a mysql Database on a serer
- add some tables with content to that database
- add that database to the Orchestrator SQL Ressources
- delete a table in the MySQL database with any Database-Tool ( i used MySQl Query Browser)
- upgrade Orchestrator and vCenter from 5.5 to 5.5.1
- check if there is an error if you try to expand the SQL Ressources in the Orchestrator Client.