Re: Non-default spfile location

On Oct 10, 6:49 am, joel garry <joel-ga..._at_home.com> wrote:
> On Oct 9, 1:31 am, "astalavista" <nob..._at_nowhere.com> wrote:
>
> > hi,
>
> > How can I specify a non-default location for a spfile ?
> > I can only do that through a pfile ... pity
> > am I right or I miss something ?
>
> > Why I cannot specify
> > startup spfile=.... ?
>
> > Thanks in advance
>
> > 10.2.0.3 on Windows
>
> All you need is a single line pfile pointing at the spfile, is that
> really so hard? http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statem...
>
> jg
> --
> @home.com is bogus.
> "I'm the poor man's Alan Greenspan." - Merle Haggard

I think he knows this, which is why he talked about "I can only do that through a pfile"

His real question, however, is, "Why I cannot specify startup spfile=.... ? "

To which the only rational reply is: why can't Oracle make me a cup of tea in the morning?

Ah, OK. That'll be because it's *coded* that way.

In short, the OP has a wishlist item. The reason why wishlist items are wishlist items and not product features is because they haven't got that far yet...

Or perhaps they never will: there are reasons they introduced the spfile, and the fact that it can be no place other than ORACLE_HOME \database and can't be called anything other than SPFILExxx.ora. Those reasons are to do with security and manageability. The spfile cannot be anywhere other than on the server, and this is a good thing because it prevents three hundred copies of your configuration file being scattered across your network. It stops there being arguments as to whose version of the init.ora is the operative statement. By restricting the configuration to one box and one location, you do away with all that nonsense.

And the security argument is a winner, too: unless I can gain access to your OH\database subdirectory, I cannot affect the way the instance behaves. Whereas, so long as I could knock together a text file, I could do all sorts of fun and games to your instance in the old pfile scenario.

Well, these sorts of arguments can be batted back and forth, and there are pros and cons on each side. But the point I'd make to the OP is: it's designed this way for a reason, and I would never want to see a "startup spfile=" command introduced as a result. In fact, I look forward to the day the pfile is abolished and the spfile is the only way to do it, and "startup", no parameter file arguments allowed, is the only way to start your instance. Received on Thu Oct 11 2007 - 20:33:59 CDT