Re: v$abc.. table names - nightmare

# I am not an expert in Oracle, or really any of the technologies on
this list. I have no time to be an expert in any of these, and I don't need to be.

Know about how and when to escape special characters in unix/linux environments does not exactly come close to expert level. Somewhere along the lines "geez is there anything special about the dollar sign in a unix/linux script that I should be aware of?" ...

If one is indeed in charge of writing and deploying script based monitoring solutions across so many different platforms and software architectures some basic scripting knowledge and competency is on the nice to have list.

# What is more important for me is that the scripts follow a common
standard - very specific STDOUT, STDERR and return code, respect a clearly documented set of environment variables, etc etc.

One way to avoid "most" problems in querying oracle internal views/ tables and ( especially ) some of the stranger x and v etc views is to put your code inside a sql file and executing that sql file.

No reason that you cannot use that technique probably along with whatever other "common standards" that you are working from.

On the other hand if you are really as handy at C++ as you say then you can also go directly at Oracle databases instead of driving file based monitoring solutions to and from the database instances. Received on Wed May 18 2011 - 14:34:47 CDT