Re: v$abc.. table names - nightmare

From: joel garry <>
Date: Wed, 18 May 2011 10:01:13 -0700 (PDT)
Message-ID: <>

On May 18, 1:00 am, neilsolent <> wrote:
> > Dude this has been done and redone so many times in the last 25 years
> > that unless you know exactly what you are doing and why you are doing
> > it ... using something pre-written and off the shelf will at least
> > initially probably be a whole lot better than what you are currently
> > doing.
> It is very unlikely that scripts written 25 years ago will work now.
> There wasn't even Perl then!
> Off the shelf code won't cater for the non-Oracle parts of the scripts
> I write - they do a whole lot more than just Oracle-related stuff.
> > All in all ... it might be a whole lot easier for you to either find
> > some good prewritten stuff ( google things like "oracle health check
> > script" maybe beware of the references to the site run by you know
> > who )
> Errr .. that's what I'm doing. This is the internet right here :-)

Much as I'd like to think not, usenet ain't the whole intertube. Perhaps if you told exactly what you are trying to accomplish, we could suggest or direct.

> > Not to be rude but if you are struggling just to be able to in a
> > script issue sqlplus commands against v$database it seems like you
> > have a pretty steep learning curve in your immediate future.
> I am not struggling.
> This thread was really just a simple question about the $ signs.
> Noone has presented any good reason why they are there (they've been
> there for 25 years - perhaps that was long enough to fix this design
> no-no?)

Oracle came out of the DEC world, where using a dollar sign was considered a mark of he-man internals guru-dom. On the pdp machines, $ was the identifier of the system account [1,2], on VMS machines it signified system objects in an object name. Rather than a design nono  that should have been fixed, it is a backward compatibility convention that has no reason to change. Oracle was written in C to be compatible across platforms, though real he-men programmed in BLISS, the language of the OS. Meanwhile, unix was written in C, and is really where you have problems with shells and other pathetically eclectic languages doing strange stuff with with special characters screwed up substantial fractions of a century ago, not to mention the silliness of training generations of CS students to do application programming in C. The blame isn't with Oracle here.

> I know shell is not ideal for Oracle programming in general - but you
> do have to consider the bigger picture beyond Oracle.
> Perhaps I do know what I am doing and I was just asking a simple
> question..

I use it all the time. I ought to use perl more, but I've been saying that for decades too. Then again, perl code coming out of Oracle isn't always the best code either. I've made the same complaint about the dollar signs, but there are some things where you just have to deal with "that's the way it works." Don't get me started on friggin' csv files and quote characters.

John answered your simple question, but I have to wonder what you've been doing that you aren't familiar with these common interactions. As Sybrand noted, there may be a userenv way. John was wrong (or joking) about Oracle versions though. Everyone knows there was no Version 1, 'cause first versions always suck.


-- is bogus.
Received on Wed May 18 2011 - 12:01:13 CDT

Original text of this message