nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

bad results with sql queries

DGoodale

Hey folks, I was wondering if anyone else has problems with using sql queries to select devices in Orion NCM version 6.0 (although I had the same issues with earlier versions as well). I've pretty much given up on using sql queries.

I would like to be able to run a script against all our 2911 routers...about 100 of them. Unfortunately, if I build a simple query searching for all nodes with a node name that contains "2911" the console generally crashes and I have to exit the console and restart it. (I get weird diagonal lines across the screen with lots of popups talking about script failures). Today, I decided I was going to write down the failure and open a thread on it here at Thwack. Oddly enough, the query didn't crash. Instead it returned ONE of my 100 devices that contain "2911" in the node name. Not as bad as the console crashing, but STILL not very helpful.

I doubt the problem can be ME because building a simple query that selects all nodes where the node name contains "2911" is NOT rocket science.

Any suggestons, folks?

Dan Goodale - Network Engineer, Triwest Healthcare

Find more posts tagged with

sql

ncm_6.0

Accepted answers

DGoodale

I opened up a ticket and got a resolution to this one, at least as it pertains to using the "Specify a Selection Criteria" button in the Execute Script pane in NCM.

Oddly enough, you can't use the Node Name when building your Query. You have to use the System Name instead (under Discovered Properties). I was told the Node Name variable is reserved for Macro use. I changed my Point&Click built query to use the System Name instead and I actually found my 100 routers that have "2911" as part of the name.

All comments

Capt._Obvious

I am assuming you are using a query similar to:

select * from nodes where MachineType like '%2911'

Seems to work fine for me. have you opened a support ticket?

DGoodale

Actually, I'm not writing them myself directly. I'm using the tool in NCM that comes up in the Orion Network Configuration Manager App. on the server.

On the Quick Start tab in the NCM application I click on "Execute Command Scripts". Then I click the down arrow on the "Select Nodes Directly" button. I select "Specify a Selection Criteria" from the drop down menu. At that point you get a pane labeled "Select the Nodes to run this Command Script on:" The top of the pane has a square button labeled "Select Nodes where 'all' of the following apply". The 'all' is a link to a small popup that lets you select the logic for the query statements. The choices in the link are "all, any, none, not all". I leave it set to the default of all since I'm only building a one line query. Click the square to the left of the form and I get a dropdown where I choose "Add a Simple Condition". Now you're presented with a line that says "Where * is equal to * ". You click on the underscores to choose the options to build the queries. In my case, I make the line say "Where 'Node Name contains 2911". I click on the "View Selected Nodes" button and it either crashes or gives me ONE of my 100 routers that have names that contain "2911" in the node name.

It SOUNDS slow but actually, building a little query like that is pretty fast (and necessary when you don't know SQL). Anyway, the end results are as described, a console crash or a return of 1 out of a 100 routers with "2911" in the name. So, I have to choose "Select Nodes Directly" on the election button instead and choose them one at a time when they all display in the upper pane. It's a real "pane" in the butt.

No, I didn't open a ticket. I have a couple of problems and thought it would be easier to come back and look for replies to each of them separately.

Thanks,

Dan Goodale

Capt._Obvious

I think this would be a good candidate for a support case as the behavior may need a little more indepth research, an online case would probably be your best bet, as I cannot reproduce this behavior in house

billy10388

I think this would be a good candidate for a support case as the behavior may need a little more indepth research, an online case would probably be your best bet, as I cannot reproduce this behavior in house

I also think so.
_________________
[url=http://moviesonlinefree.biz]Watch Vampires Suck Online Free

DGoodale

I opened up a ticket and got a resolution to this one, at least as it pertains to using the "Specify a Selection Criteria" button in the Execute Script pane in NCM.