Scope=spfile in DB_FILE_NAME_CONVERT

Hello All,
I am using Oracle 11g R2 and I am configuring Data guard between a primary database (RAC 2 nodes) and a physical standby database single instance.
I want to create my standby database without shutting down the primary database, one of the requirement is to set the below 2 parameters :
alter system set DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/DATAFILE' scope=spfile;
alter system set LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/ONLINELOG' scope=spfile;These parameters cannot be set at the memory level, it can be set only if i mentioned "scope=spfile"
Does that require to restart my primary database? or it will directly take affect even if scope=spfile?
Regards,

I tested and here's my results:
SQL> alter system set DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/DATAFILE' scope=both;
alter system set DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/DATAFILE' scope=both
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/ONLINELOG' scope=both;
alter system set LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/STANDBY','+DATA/ORCL/ONLINELOG' scope=both
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modifiedThe Oracle document says ALTER SESSION for both but my test results say above.
If it works, its works.
Best Regards
mseberg

Similar Messages

Alter system scope=spfile not taking

This should have been brain-dead simple but something is happening I've never seen and don't understand.
Oracle SE 10.2.0.4 on Windows Serve 2003
I do an ALTER SYSTEM ... SCOPE=SPFILE, but when the database is restarted, values have reverted back.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      E:\ORACLE\PRODUCT\10.2.0\ROY\D
                                                 ATABASE\SPFILEROYDEV.ORA
SQL> show parameter control
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
control_files                        string      +SAN/roydev/controlfile/curren
                                                 t.261.686792331, +SAN/roydev/c
                                                 ontrolfile/current.260.6867923
                                                 31
SQL> --
SQL> alter system set control_files='x:\oradata\roydev\controlfile\control01.ctl','y:\oradata\roydev\controlfile\control02.ctl' scope=spfile;
System altered.
SQL> --
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size                  1298192 bytes
Variable Size             167772400 bytes
Database Buffers          440401920 bytes
Redo Buffers                2895872 bytes
Database mounted.
Database opened.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      E:\ORACLE\PRODUCT\10.2.0\ROY\D
                                                 ATABASE\SPFILEROYDEV.ORA
SQL> show parameter control
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
control_files                        string      +SAN/roydev/controlfile/curren
                                                 t.261.686792331, +SAN/roydev/c
                                                 ontrolfile/current.260.6867923
                                                 31
SQL> spool off

EdStevens wrote:
Girish Sharma wrote:
EdStevens wrote:
Ok, here's what I figured out (and I don't have any experience with Oracle Managed files either)...
The db was using the default spfile, to a point. When I did my ALTER SYSTEM, the timestamp on the default spfile was changing, and that was part of what threw me off. I finally created a pfile from the spfile, and that pfile reflected my changes, but also included a parameter -- spfile=+ASM/... yada, yada. Looking at the contents of the actual spfile (yes, I know it's a binary, but the parms themselves are clear text, so you can see what's going on .. just don't try to edit it). I saw exactly what was in the created pfile.
Next I renamed my newly created pfile, then did another CREATE PFILE FROM SPFILE, only this time specified the spfile name, pointing to the ASM based file. Sure enough, none of my changes were reflected in that file; further evidence that it was overriding. I did a sanity check on the two pfiles, merging a few things from the first into the one created from the ASM file, the created a new default spfile from that. After that life was good.
This was a first for me. Of course I've been at this long enough to have used pfiles before there were spfiles. I've seen pfiles that had a single line, 'SPFILE= ..' to point to some non-standard spfile. But I've never seen an spfile itself refer to yet another spfile.
Oh well. All's well that ends well, and I learned something new.Sorry Ed, but I am still not able to understand your solution because I am bit confused of below text specially :
only this time specified the spfile namewhat you specified here other than first one's pfile spfile=+ASM/...folder1/folder2 ?
Sure enough, none of my changes were reflected in that file; further evidence that it was overriding.completely failed to understand this line, what happened 2nd time that you did't got changes reflected; while you got in the first one pfile.
The more cause of my confusion may be poor and bad in English, but I know, I don't have poor wish of oracle learning, so I am asking for removing doubts please.
Regards
Girish SharmaOk, let me see if I can clarify.
When first approaching the database, I checked to see if it was using a pfile or spfile. A 'show parameter spfile' indicated it was using an spfile, and it was the default name in the default location (%ORACLE_HOME\database\spfile%ORACLE_SID%.ora).
Next I did a couple of ALTER SYSTEM SET .... SCOPE=SPFILE commands.
Next I bounced the database and rechecked the parameters I had set, and they were back to their original values.
After a couple of more iterations to make sure I wasn't doing something really stupid (after all, this should have been dead simple) I opened this thread, then continued to poke at it. So,
Next I created a default pfile from the default spfile - CREATE PFILE FROM SPFILE. This created %ORACLE_HOME%\database\init%ORACLE_SID%.ora.
On examining the resulting pfile, I saw my changes reflected in it, but also was surprised to see the parameter *.SPFILE=+ASM/...., so was including an addition spfile that was under ASM. (BTW, the entire purpose of this exercise was to migrate the database off of ASM.) At this point, as a sanity check I opened the default spfile - the one pointed to by the SHOW PARAMTER SPFILE command, the one in ORACLE_HOME\database. It did - as it should have - matched perfectly with the newly created pfile. So it was apparent that my ALTER SYSTEM changes were going to this default spfile but - unbeknownst to me at the outset - were being over-ridden by that second, ASM-based spfile.
At this point, I renamed the just-created pfile to something like initORCL.sav. Then created a new pfile from the ASM-based spfile - CREATE PFILE FROM SPFILE='+ASM\spfile.ora'. This new pfile was much more extensive than the first, and there were the parameters that were overriding the ones I was trying to change. I hand-modified this pfile, including some other things I found in the first, then created a new default spfile from it. So at this point I had the default spfile without it pulling in a second one that would override what I did.
Does that clarify?Yes, now its 100% clear to me.
Thank you.
Regards
Girish Sharma

ALTER SYSTEM SET SGA_TARGET = 0 scope=spfile; not working

SQL> ALTER SYSTEM SET SGA_TARGET = 0 scope=spfile;
System altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 2121256960 bytes
Fixed Size 2243280 bytes
Variable Size 1140852016 bytes
Database Buffers 973078528 bytes
Redo Buffers 5083136 bytes
Database mounted.
Database opened.
SQL> show parameters sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2032M
sga_target big integer 0
SQL> create pfile=#/home/oracle/per03pfile' from spfile;
pfile has
*.sga_max_size=0
*.sga_target=0
and
instance1.__sga_target=2130706432
instance2.__sga_target=2130706432
tried ALTER SYSTEM SET SGA_TARGET = 0 scope=spfile sid='*'; aswell ...
oracle v11.2.0.2
GI 11.2.0.2
linux 64 bit

Chinar wrote:
user9198889 wrote:
SQL> ALTER SYSTEM SET SGA_TARGET = 0 scope=spfile;
System altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 2121256960 bytes
Fixed Size 2243280 bytes
Variable Size 1140852016 bytes
Database Buffers 973078528 bytes
Redo Buffers 5083136 bytes
Database mounted.
Database opened.
SQL> show parameters sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2032M
sga_target big integer 0
SQL> create pfile=#/home/oracle/per03pfile' from spfile;
pfile has
*.sga_max_size=0
*.sga_target=0
and
instance1.__sga_target=2130706432
instance2.__sga_target=2130706432
tried ALTER SYSTEM SET SGA_TARGET = 0 scope=spfile sid='*'; aswell ...
oracle v11.2.0.2
GI 11.2.0.2
linux 64 bitWhile SGA_MA_SIZE <> 0 then it seems SHARED MEMORY constructed according this setting.So it is not recommended to avoid automatic shared memory management.But if you decide this then you have to identify SHARED_PLOOL_SIZE,DB_CACHE_SIZE(in additionally LOG_BUFFER and LARGE_POOL) parameter manually and
ALTER SYSTEM SET SGA_TARGET=o scope=spfile and ALTER SYSTEM SET SGA_MAX_SIZE=o scope=spfile and restart database again.SQL> alter system set sga_max_size=0 scope=spfile sid='instance1';
System altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
SQL> show parameters sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2032M
sga_target big integer 0
SQL>
has it got todo with AMM being enabbled?

Changing DB_FILE_NAME_CONVERT

Oracle Database 10g Enterprise Edition
Oracle Enterprise Linux
I am trying to learn creating Dataguard configuration on my laptop. Since I am creating both Primary and Standby databases on the same laptop using same Oracle home I need to use db_file_name_convert and Log_file_name_convert. But I just can't change db_file_name_convert parameter. I am using spfile.
I am getting ORA-2096 errors. That this parameter cannot be modified with these options.
Can anyone tell me how to change this parameter.
I have tried various ways,
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE= BOTH;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=SPFILE;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=BOTH DEFERRED;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=SPFILE DEFERRED;
Everytime I am getting 2096 error.

This is the error I am getting
This is the primary database.
SQL> select name from v$database;
NAME
XYZ
SQL> show parameter db_file_name_convert
NAME TYPE VALUE
db_file_name_convert string
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile deferred;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile deferred
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') deferred scope=spfile;
alter system set db_file_name_convert=('ABC','XYZ') deferred scope=spfile
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=memory;
alter system set db_file_name_convert=('ABC','XYZ') scope=memory
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*';
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*'
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*' deferred;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*' deferred
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option

Confusion in the DB_FILE_NAME_CONVERT parameter

Hi all, for the parameter DB_FILE_NAME_CONVERT, do we put database SIDs ( primary first then standby ) or the file path for both in the same order
thanks for help

REDOLOG wrote:
Hi, thanks
exactly, that what get me confused, here is the link in the official documentation: http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm#i68626 please look at the
Example 3-4 Primary Database: Standby Role Initialization Parameters paragraph, and here is another link witch says a different thing, please search for string:
alter system set db_file_name_convert='/oracle/oradata/standby','/oracle/oradata/primary' scope=spfile sid='*';
What are you confused about.
That doc shows you a COMPLETE example of the parameters, and their order, for both the primary and standby databases. See Example 3-5 for the standby settings.
You should do yours the same way and in the same order.

How to edit spfile in RAC with location +DATA/

Dear All,
My RAC is 2 node 11gR2 on Linux.
I need to modify my spfile since my UNDO tablespace is giving error while Oracle Starts up:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS2' does not exist or of wrong type
I changed UNDO TABLESPACE recently using alter system only.
Now I want to change the UNDO TABLESPACE in spfile.
When i go to dbs directory i can see the parameter file and its contents are: SPFILE='+DATA/racdb/spfileracdb.ora'
I need to edit this file, how can i edit it?
Kindly help
Regards,
Imran

mrimran,
After asking an enormous amount of doc questions you should know
alter system scope=spfile
alters the spfile
You should also know how to find the documentation (searchable) at http://tahiti.oracle.com and to use it
Your abuse of this forum with doc questions is completely unacceptable.
I will, from now on, mark every further doc question from your handle as abuse of this forum. Every question, until moderators have removed you!!!
Sybrand Bakker
Senior Oracle DBA

Clearing (removing) an SPFILE parameter

11.2.0.3/Solaris
I want to clear the value set for LOCAL_LISTENER and set it to null. As per doc, I have to use RESET command. But RESET works only with SCOPE= SPFILE . ie. I have to bounce the DB to bring this change into effect.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      /u01/app/oracle/product/11.2.0
                                                 /dbhome_1/dbs/spfileorcl.ora
SQL>
SQL> show parameter LOCAL_LISTENER
NAME                                 TYPE        VALUE
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))
SQL>
SQL>
SQL>
SQL> alter system reset LOCAL_LISTENER scope=both;
alter system reset LOCAL_LISTENER scope=both
ERROR at line 1:
ORA-32029: resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported
SQL> alter system reset LOCAL_LISTENER ;
System altered.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      /u01/app/oracle/product/11.2.0
                                                 /dbhome_1/dbs/spfileorcl.ora
SQL>
------ Still showing the old value as a bounce is required
SQL> show parameter LOCAL_LISTENER
NAME                                 TYPE        VALUE
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))Is setting the parameter to empty string supported in Oracle . It seems to have worked for me, But i would like to know if it is recommended.
SQL> show parameter LOCAL_LISTENER
NAME                                 TYPE        VALUE
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))
SQL> alter system set LOCAL_LISTENER = '' scope = both;
System altered.
SQL> show parameter LOCAL_LISTENER
NAME                                 TYPE        VALUE
local_listener                       string
SQL>The below article says it is not recommeded to use empty string. But , what other option do I have to clear a parameter's value without bouncing the DB ?
http://coskan.wordpress.com/2007/03/07/setting-or-resetting-unsetting-parameters/
Edited by: greeny on 12-Nov-2012 06:25

1)
if you want to set local_listener for only this session
ALTER SYSTEM SET LOCAL_LISTENER='' SCOPE=MEMORY;
if you want to make it persistent (need rebound to take effect):
ALTER SYSTEM SET LOCAL_LISTENER='' SCOPE=SPFILE;
if you want use at this session and make persistent when rebound database:
ALTER SYSTEM SET LOCAL_LISTENER='' SCOPE=BOTH;
2)SQL> alter system reset LOCAL_LISTENER scope=both;
alter system reset LOCAL_LISTENER scope=both
ERROR en lÝnea 1:
ORA-32029: actualmente no se soporta el restablecimiento con SCOPE=MEMORY o
SCOPE=BOTH
SQL> alter system set LOCAL_LISTENER='' scope=MEMORY;
Sistema modificado.
SQL> alter system reset LOCAL_LISTENER ;
Sistema modificado.Edited by: Fran on 12-nov-2012 6:43

Problems with spfile. How to change database parameters

Hello
My Oracle database is 10.2.0 and SAP version is NW2004s. I am having errors in alert.log file
Thread 1 cannot allocate new log, sequence 3959
Checkpoint not complete
Sun Aug 27 01:38:12 2006
I have changed the parameter log_buffer from 14274560 to 1048576 following the SAP Note 830576. I changed the pfile and created a spfile from this pfile. Now the pfile and spfile reflect the parameter log_buffer as 1048576.
But surprisingly, when I say
SQL> show parameter log_buffer
NAME                               TYPE                VALUE
log_buffer                         integer         14274560
Even after pfile and spfile reflecting 1048576 value for log_buffer, the database is showing this old value. Kindly let me know how to change the log_buffer parameter.

hi,
check which file it is reading
sql>sho parameter spfile
If it is reading spfile
issue alter system set log_buffer=<value> scope=spfile;
down and bring up database
If it is not reading spfile means reading pfile change parameter in INIT<SID>.ORA file
move all files which starts with spfile in dir $ORACLE_HOME/dbs to backup location
connect to database
create spfile from pfile
check $ORACLE_HOME/dbs only one spfile<sid>.ora exists
bring up database
and look for log_buffer
I guess ur changing in some other file which oracle is not reading.
or u can issue startp pfile='path';
then u can create spfile and issue startup force.
regards
Vinod

Changes to spfile in +ASM

I'm having to do some changes to an 11.2 database on Linux 5.9 and have a simple question:
The database is a primary database for two physical standby databases.
The database is configured with Grid and ASM.
I need to make some parameter changes and save them to the spfile and restart the databases.
Normally, I would "alter system set something=value scope=spfile".
But with ASM, our spfile is in the ASM, and there is no spfile at the OS level, only an init<sid>.ora file which of course points to the spfile in the ASM.
My question is if I can simply run the command as I normally would and it would save the changes to the spfile in the ASM.
Or, do I have to create a backup copy of my pfile, then make the changes to the spfile, then create a pfile from spfile, and start the database up using the pfile (with system changes), then delete the old spfile in the ASM and then create a new spfile in the ASM from the pfile? Then when I'm done, copy back over my saved backup pfile as the new init<sid>.ora file, and bounce the database again.
It seems I've had to do this in the past when dealing with ASM and DG.
As for the standby databases, can I simply just make the changes and save them to the spfile and restart the standby database up to mount mode again?
Also (one last question), these databases are configured with DGMGRL. Do I need to deal with it too (or instead)?
The changes I need to make are Oracle hidden parameter changes that are needed to avoid hitting a bug (as directed by OSS).
Thanks in advance.

Okay, thank you. I wonder in what situation I am thinking of when I had to do it the way I described.
Thanks again.

Unable to set sga_max_size parameter through spfile

My 10g db running in spfile. I am trying to decrease sga_max_size to 1024M where i have 1504 now ...
Do i am not doing in a right way ? Please suggest me
i am trying like this .....
SQL> sho parameter sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 1504M
sga_target big integer 0
alter system set sga_max_size =1020M scope= spfile;
SQL>system altered
SQL> sho parameter sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 1504M
sga_target big integer 0

SCOPE=SPFILE would not change the in-memory value. So a SHOW PARAMETER would still show the previous value.
You must compare the SPFILE before and after the ALTER SYSTEM. (Don't copy the spfile in a text editor but make a copy of the spfile to view OR use the "strings" command on Unix/Linux . If you accidentally write to the spfile with a text editor you will corrupt it. So, the best way to check the value is to run a CREATE PFILE FROM SPFILE and view the pfile which would be the initSID.ora file.

New control file using spfile

Hi all,
I want to multiplex my control file to another volume. I have an spfile (no init.ora file). Do I just use an alter system with scope = SPFILE?
i.e. ALTER SYSTEM SET CONTROL_FILES=... scope=SPFILE"
Thanks for any feedback.

geeter wrote:
Hi all,
I want to multiplex my control file to another volume. I have an spfile (no init.ora file). Do I just use an alter system with scope = SPFILE?
i.e. ALTER SYSTEM SET CONTROL_FILES=... scope=SPFILE"
Thanks for any feedback.Change spfile while database running
Close the db
Start it and it will use new settings for CONTROL_FILES
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Setting sga_target in Oracle10g using spfile in Window OS

Hi all
Previously we used to set the parameter values thru initora
Now we wish to follow the default spfile for parameters as provided by Oracle.
When we give
alter system set pga_aggregate_target = ???M;
it works properly but the same syntex does not work properly for'
processes as well as sga_target
1. Kindly guide the exact syntix to set these parameters
2. Also advise whether setting sga_target would be sufficient or do we need to set sga_max_size also and possible advantage
3. Role of Oracle Processes and what should be the ideal number for Live installation with say 100-150 simultaneous users. RAM available is enough say 8GB.
Suresh Bansal

Suresh Bansal wrote:
Hi all
Previously we used to set the parameter values thru initora
Now we wish to follow the default spfile for parameters as provided by Oracle.
When we give
alter system set pga_aggregate_target = ???M;
it works properly but the same syntex does not work properly for'
processes as well as sga_target
1. Kindly guide the exact syntix to set these parameters
2. Also advise whether setting sga_target would be sufficient or do we need to set sga_max_size also and possible advantage
3. Role of Oracle Processes and what should be the ideal number for Live installation with say 100-150 simultaneous users. RAM available is enough say 8GB.
Suresh BansalBoth SGA_MAX_SIZE and PROCESSES are parameters that cannot be changed dynamically, because you have omitted the SCOPE= clause of ALTER SYSTEM it takes it's default of BOTH. SGA_TARGET is modifiable in memory, but only up to the limit specified by SGA_MAX_SIZE which defaults to whatever you have SGA_TARGET set to, this means in a default setup you can only reduce SGA_TARGET. From my system
SYS @ DB10G >show parameter SGA_
NAME                                 TYPE        VALUE
sga_max_size                         big integer 584M
sga_target                           big integer 584M
SYS @ DB10G >SELECT NAME,ISSYS_MODIFIABLE
2* FROM V$PARAMETER WHERE NAME LIKE 'sga%'
SYS @ DB10G >/
NAME                                                                             ISSYS_MOD
sga_max_size                                                                     FALSE
sga_target                                                                       IMMEDIATESo I have 584m set for both as a result I can reduce the size, but not increase it.
SYS @ DB10G >alter system set SGA_TARGET=600M;
alter system set SGA_TARGET=600M
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00823: Specified value of sga_target greater than sga_max_size
SYS @ DB10G >alter system set SGA_TARGET=400M;
System altered.But I can set it in the spfile.
SYS @ DB10G >alter system set SGA_TARGET=600M SCOPE=SPFILE;
System altered.You only need to set SGA_TARGET, but if you set SGA_MAX_SIZE larger you give yourself room for growth later. This should be clear from the demo above.
PROCESSES controls the size of Oracle's internal process table (externalized as v$process) which is why you can't dynamically reset it, you'll need more entries in this process table than you anticipate user sessions, generally about 15-25% more.
Niall Litchfield
http://www.orawin.info/

Dynamic parameter scope check

Dear All,
My colleague has changed a parameter open_cursor, now if I want to verify the scope of that parameter then how can i check.
scope = both
scope = memory
scope = spfile
Is there any view or table available.?
Thanks
Ajay

refer to v$parameter(is_sysmodifiable)
NO means scope=spfile only
YES means scope=memory or both
Sybrand Bakker
Senior Oracle DBA

Event = "10262......" in SPFILE

Hi,
I'm in 10G R2 and in note : 39308.1 (mtalink) it is said :
SUGGESTIONS:
Event 10262 can be set to safely ignore small memory leaks.
Set the following in init.ora for example to disable space
leaks less than 4000 bytes:
event = "10262 trace name context forever, level 4000"
and stop and restart the database.How can we put it in spfile since we start database with SPFILE.
Thank you.

something like this??
alter system set event = "10262 trace name context forever, level 4000" scope=spfile;Regards

9I의 SPFILE사용에 대해서

제품 : ORACLE SERVER
작성날짜 : 2004-10-12
9I의 SPFILE 사용에 대해서
========================
PURPOSE
Oracle9i부터는 database의 initial parameter를 지정하는 initSID.ora file외에
server parameter file이라고 불리는 spfileSID.ora가 새로 소개되었다.
이 spfile을 사용하게 되면 alter system을 통해 database가 운영 중에
parameter를 수정할 수 있게 되면서 parameter 수정때마다 database를 restart
시켜야 하는 필요을 줄여주고, 앞으로 소개될 dynamic한 server tuning에
중요한 역할을 할 수 있다.
Explanation
이 문서에서는 이러한 spfile에 대해서 실제 사용하면서 알아두어야 할 다음과
같은 내용에 대해서 정리하였다.
1. spfile을 vi로 직접 변경한 경우의 영향
2. db open시 spfile을 읽었는지 확인하는 방법
3. initSID.ora를 spfileSID.ora로 migration하거나 그 반대의 방법
4. alter system으로 parameter변경시 scope에 대해서
5. v$parameter와 v$spparameter에 대해서 (static parameter 확인)
1. spfileSID.ora 화일을 vi로 직접 변경한 경우의 영향
spfile이 크기 않은 관계로 vi등으로 읽으면 마치 text 화일처럼 parameter가
보이는데 이 화일은 실제로는 binary file로 직접 변경하면 안된다.
특히 이 화일의 header에는 checksum과 기본적인 meta-data 정보등을
포함하여 manual하게 변경하게 되면 이 checksum의 값이 맞지 않게 되면서,
이후 startup시 이 화일을 읽지 않고 initSID.ora file을 읽게 된다.
db를 운영하면서 spfile에 계속 parameter가 변경된 경우라면 이러한 문제로
tuning등을 통해 변경된 parameter value를 모두 잃게될 수 있는것이다.
2. db open 시 spfile을 읽었는지 확인하는 방법
db가 open 시에 참조한 initial parameter file이 무엇인지를 확인하기
위해서는 다음과 같이 조회하면 된다.
SQL> show parameter pfile
NAME TYPE VALUE
spfile string ?/dbs/[email protected]
여기에서 ?는 ORACLE_HOME을 나타내고 @는 SID를 나타낸다.
3. initSID.ora를 spfileSID.ora로 migration하거나 그 반대의 방법
spfile을 사용하다가 그 화일의 내용을 initSID.ora에 backup 차원에서
반영시켜 두거나, 혹은 spfile대신 initSID.ora를 사용하고자 하는 경우,
또는 반대로 initSID.ora를 참조하여 spfileSID.ora를 생성하고 하는
경우 다음과 같이 간단히 작업하면 된다.
SQL>connect / as sysdba
SQL>create pfile='initORA9i.ora' from spfile='spfileORA9i.ora';
SQL>create spfile='spfileORA9i.ora' from pfile='initORA9i.ora';
위 문장에서 화일명 대신 직접 directory까지 절대 path로 지정할 수 있고,
화일명은 임의로 지정 후 나중에 사용시 initSID.ora나 spfileSID.ora 형태로
만들어줄 수 있다.
default인 $ORACLE_HOME/dbs directory이고 SID가 붙는 이름 형태이면 간단히,
다음과 같이 지정하여도 된다.
SQL>create pfile from spfile;
SQL>create spfile from pfile;
sysdba 권한이 없으면 권한 부족 오류가 발생한다.
4. alter system으로 parameter 변경 시 scope에 대해서
spfile을 사용하게 되면 앞에서도 언급한 것과 같이 spfile을 직접 변경하는
대신 alter system command를 통해 initial parameter를 수정할 수 있다.
단 이때 alter system command 뒤에 scope를 지정할 수 있는 데 scope로
지정가능한 값은 memory/spfile/both 세가지가 된다.
memory가 이중 default여서 scope를 지정하지 않으면 memory가 된다.
memory: 변경이 현재 상태에만 영향을 미치며 db가 restartup되면,
변경 이전값으로 돌아간다.
spfile: 변경 내용을 spfile에만 저장하고 현재 상태에는 영향을 미치지
않게 한다.
static parameter의 경우는 이 scope만이 지정가능하다.
즉, spfile을 사용하더라도 static parameter에 대해서는 db
운영중에 바로 값을 변경하여 restartup없이 반영하는 것은 불가능
한 것이다.
both: 변경 내용을 현재상태에도 바로 반영하고, spfile에도 반영시켜,
이후 rebooting시에도 영향을 미치도록 한다.
지정하는 방법은 다음과 같다.
SQL>alter system set open_cursors=300;
SQL>alter system set open_cursors=300 scope=spfile;
SQL>alter system set open_cursors=300 scope=both;
단, spfile을 참조하지 않고 init.ora를 참조하여 db가 open한 경우 이러한
alter system 명령을 통해 initial parameter를 변경하려고 하면
다음과 같은 오류가 발생한다.
특히 spfile에 외부의 변경이 가해져 spfile이 참조되지 않은 경우에 주로
다음 오류를 만날 수 있다.
ORA-02095: specified initialization parameter cannot be modified
5. v$parameter와 v$spparameter에 대해서 (static parameter 확인)
initial parameter의 종류에는 db가 운영 중에는 바로 그 값을 변경하여
반영시킬 수 없고, 다음 startup 후에만 변경된 값이 영향을 주게되는
parameter가 있다.
이러한 parameter를 static parameter라고 부른다.
이 static parameter의 경우는 그래서 alter system으로 변경하더라도,
scope=spfile 로만 지정 가능한 것이다.
이러한 static parameter를 scope를 지정 안 해서 memory로 하거나 both로
하게 되면 4번에서 설명한 ORA-2095 오류가 발생하게 된다.
그럼 static parameter는 어떻게 확인할 수 있는가?
SQL>select name, issys_modifiable from v$parameter;
여기에서 보면, issys_modifiable의 값으로 다음 세 가지가 나타난다.
FLASE: static parameter로 scope=spfile로만 값을 변경 가능하다.
즉 값을 변경해도 이후 startup 시부터 영향을 미치게 된다.
IMMEDIATE: 값을 변경하면 현재 session부터 바로 영향을 받게된다.
DEFERRED: 변경된 값이 이후 접속되는 session부터 영향을 준다.
alter system을 통해 parameter를 변경하는 경우 변경된 값이 반영이 잘
되었는가를 확인하려면 다음과 같이 show parameter나 v$parameter를
조회하고, 현재 반영은 안 되었더라도 spfile에 저장은 되었는지를 확인하
려면 v$spparameter를 조회하면 된다.
SQL>show parameter open_cursors
SQL>select value from v$prameter where name = 'open_cursors';
SQL>select value from v$spparameter where name = 'open_cursors';
즉, scope=spfile로 parameter를 변경한 경우는 v$spparameter에만 변경
된 값이 나타나고, show parameter나 v$parameter에서는 변경 전 값이
나타나게 된다.

Scope=spfile in DB_FILE_NAME_CONVERT

Similar Messages

Maybe you are looking for