Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: 10g downwards compatibility
Christoph Kukulies wrote:
> Christoph Kukulies <kuku_at_accms33.physik.rwth-aachen.de> wrote:
>
>>After installing 10g I find that some things are different. >>Especially I had to rely on O7_dictioniary_accessibility=TRUE on init.ora.
>>The parameter is understood. But still I have problems with the SYS user. >>Seems I cannot run an SQL script under user SYS any longer that creates some >>Views on SYS.all_tables or something in that vein.
Please, Christoph... take an hour or so to read the documentation. You are digging yourself in deeper and deeper.
One, no the pfile is not generated at every startup from the spfile. They are mutually exclusive, and if you have both, then the spfile will be used, and the pfile ignored. Unless you force the use of the pfile with the pfile clause of the startup command, that is.
Two, if you read the documentation, then you will discover that scope=both means 'change my current value for the parameter dynamically, and also change it in the spfile for future use'. Clearly, this particular parameter cannot be changed dynamically (a fact which you can verify by looking at the ISSYS_MODIFIABLE column in v$parameter). Therefore, you must limit your alter system command to only modifying the value in the spfile, and bouncing your instance to get the change picked up. Therefore, you want a scope=spfile clause.
If you would like a quick guide to this and similar new features in 9i, then you can go to http://www.dizwell.com/html/oracle_e-books.html and spend just a few dollars or euros to get up to speed on it. (You want chapter 6, by the way).
HJR Received on Wed Dec 01 2004 - 21:32:50 CST
![]() |
![]() |