A problem recently encountered was causing major headaches. There was a runbook somewhere in the system that had an action running with the security credentials of a user that had left sometime ago. Their account had recently been disabled and the Orchestrator was logging thousands of errors and causing the Orchestrator database to grow at a massive rate. OBJECTINSTANCEDATA was growing at thousands of rows a second and hit 50 million rows and 16GB in size after only a few days.
Archive for the ‘Orchestrator’ Category
Locating Orchestrator Runbooks using bad credentials
Posted: May 17, 2016 in Orchestrator, Solved, System CenterTags: database, objectinstancedata, pid, policymodule, process id, runbook, size, SQL
Picture this scenario:
You’ve just inherited an existing Opalis implementation and the guy that set it up didn’t write any doco (or it’s lost). You want to do something that requires connection to the Opalis database…but you have no idea what server the database is on.
Interestingly enough, while starting my learning of Opalis/Orchestrator I’ve discovered there is no obvious place that you can see what database is being used. I’ve searched the registry, the console, and all the files and the closest is a mention of the SQL server in a log file if an Action server can’t connect.
If you run the Database Configuration tool, you need to enter all details from scratch, it doesn’t tell you the current setting. I would have also thought there would be a setting in the console *somewhere* that would show the server.
So anyway, I’ll see if someone on the MS forums has an answer, and will see if the situation is improved in Orchestrator.