Are you sure with the Overloading?
You may check your Agent Options, how often you make Scans and so on,
to reduce this.
I would suggest you to open a case for this.
Yes, definitely overloaded - the Oracle DBA can see hundreds of open sessions across all four servers, and I'm still getting inventory failures. Agents were set to scan daily, but the real-time inventory scanners were enabled. I've pushed out a new agent deleting those, and we'll see if it reduces the load.
Issuing 'iisreset' on the core clears out most of the sessions. I'm currently digging for some IIS tuning docs for v9, but found nothing so far...
A typical event log entry:Event Type: ErrorEvent Source: LANDesk Inventory ServerEvent Category: NoneEvent ID: 4100Date: 9/14/2011Time: 11:17:48 AMUser: N/AComputer: DNRATW-LD01Description:Database exception: SCA1732.SCN, LDInv.dll-2146825023Item cannot be found in the collection corresponding to the requested name or ordinal.Update Table:TCP Column:ADDRESS PK:, Thread ID: 8284.
That's the most common error, although I also see a description of:
Clearing column INSTALLDATE from APPSOFTWARESUITES
7428, Thread ID: 7428.
Are you using the latest MCP Patches (0519?
I remember that in one (Core) of them, was a fix for Oracle Database with updating PK.
You may ask the Support for it.
>>Feb 2011 MCP Datamart Creates invalid PK column leading to invalid triggers for Oracle users.
Limiting the # of concurrent sessions will seriously cripple your LANDesk functionality. If you are managing 1000 nodes, then you should have as many as 200+ concurrent sessions running. LANDesk requires a database with close to dedicated database funcitionality.
I've currently got 200+ connections allowed on each of the four nodes - 800 total. We can push that closer to 300 if needed...
What do you mean by having four nodes? Have you setup multiple inventory services? For a 1,000 node environment this sound like a bit of overkill if you have.Not necessarily related to your issue, but sounded odd.
Definitely look into the patch since it sounds like what you are encountering, and having constant errors certainly won't be helping your performance.
The One-Stop Shop for LANDesk Enhancements
Sorry for the lack of clarity - I have two threads and a problem report open...
The core is a VMWare VM, WIndows Server 2003, 2 cores, 4GB RAM. Our Oracle is 11gR2 RAC - four front-end servers performing load balancing into a large multi-disk array. LANDesk was set to use only one node until recently, when it's 1000+ concurrent connections effectively killed that one node (refusing logins, etc.). The DBA set it to 120 connections per node, and allowed it to use all four nodes at once, which (according to LD) should have been sufficient; when we still had errors he increased it to 250 connections per node, or 1000 concurrent connections allowed.
LD Tech Support is digging into why this is happening, and why the errors seemed to snowball lately. I'm not going to apply any patches until I hear back from them. At least not yet - my OSD imaging is still working, and scripting seems to work, but anything query-related is broken, since inventory is horribly wrong and getting worse.