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.
Posts Tagged ‘process id’
Locating Orchestrator Runbooks using bad credentials
Posted: May 17, 2016 in Orchestrator, Solved, System CenterTags: database, objectinstancedata, pid, policymodule, process id, runbook, size, SQL
1