SGA_TARGET

Hi,
I have one quick question regarding the SGA_TARGET parameter.
This is my sga allocation so far:
Total System Global Area 2147483648 bytes
Fixed Size 2140320 bytes
Variable Size 2124240736 bytes
Database Buffers 16777216 bytes
Redo Buffers 4325376 bytes
My RAM size is 16GB and i would be creating many other applications as well. now i have the following sga parameters:
SQL> sho parameter sga;
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2G
sga_target big integer 0
Now my worry is the sga_target i want to make use but i have given old parameters as well and i am getting the error
Error:     ORA-00381 (ORA-381)
Text:     cannot use both new and old parameters for buffer cache size
     specification
now my db* parameter settings are:
SQL> sho parameter db;
NAME TYPE VALUE
db_16k_cache_size big integer 0
db_2k_cache_size big integer 0
db_32k_cache_size big integer 0
db_4k_cache_size big integer 0
db_8k_cache_size big integer 0
db_block_buffers integer 2048
db_block_checking string FALSE
db_block_checksum string TRUE
db_block_size integer 8192
db_cache_advice string ON
db_cache_size big integer 0
NAME TYPE VALUE
db_create_file_dest string
db_create_online_log_dest_1 string
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string
db_domain string PFIZER.COM
db_file_multiblock_read_count integer 16
db_file_name_convert string
db_files integer 1024
db_flashback_retention_target integer 1440
NAME TYPE VALUE
db_keep_cache_size big integer 0
db_name string EAMS01
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
db_recycle_cache_size big integer 0
db_unique_name string EAMS01
db_writer_processes integer 2
dbwr_io_slaves integer 0
rdbms_server_dn string
standby_archive_dest string ?/dbs/arch
standby_file_management string MANUAL
and my init parameters are:
EAMS01.__streams_pool_size=33554432
*._allow_level_without_connect_by=TRUE
*.aq_tm_processes=1
*.ARCHIVE_LAG_TARGET=900
*.audit_file_dest='/u03/oracle/admin/EAMS01/adump'
*.audit_trail='TRUE'
*.background_dump_dest='/u03/oracle/admin/EAMS01/bdump'
*.control_files='/u04/oradata/EAMS01/control01.ctl','/u04/oradata/EAMS01/control02.ctl','/u04/oradata/EAMS01/control03.ctl'
*.core_dump_dest='/u03/oracle/admin/EAMS01/cdump'
*.db_block_buffers=550# SMALL
*.db_domain='PFIZER.COM'
*.db_file_multiblock_read_count=16# SMALL
*.db_files=1024# SMALL
*.db_name='EAMS01'
*.global_names=TRUE
*.java_pool_size=96M
*.job_queue_processes=15
*.large_pool_size=32M
*.log_archive_dest='/u04/arch/EAMS01'
*.log_archive_format='EAMS01_%t_%s_%r.arc'
*.log_archive_max_processes=5
*.log_checkpoint_interval=10000
*.log_checkpoints_to_alert=TRUE
*.max_dump_file_size='10240'# limit trace file size to 5 Meg each
*.NLS_DATE_FORMAT='YYYY-MM-DD'
*.nls_length_semantics='CHAR'
*.NLS_TERRITORY='AMERICA'
*.open_cursors=768
*.open_links=128
*.open_links_per_instance=128
*.optimizer_features_enable='10.2.0.3'
*.parallel_max_servers=5# SMALL
*.pga_aggregate_target=500M
*.processes=512# SMALL
*.query_rewrite_enabled='TRUE'
*.query_rewrite_integrity='STALE_TOLERATED'
*.remote_login_passwordfile='EXCLUSIVE'
*.resource_limit=TRUE
*.service_names='EAMS01.pfizer.com'
*.sga_max_size=2G
*.shared_pool_size=500000000# SMALL
*.streams_pool_size=33554432
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.user_dump_dest='/u03/oracle/admin/EAMS01/udump'
now what the parameters i am missing or need to edit sga_target so that oralce will use empirically over
time. Thank you.
-- Raman.

Hi..
>
# symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
# cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
>
For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
which quotes
>
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
*Buffer cache (DB_CACHE_SIZE)
* Shared pool (SHARED_POOL_SIZE)
* Large pool (LARGE_POOL_SIZE)
* Java pool (JAVA_POOL_SIZE)
* Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
>
So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
HTH
Anand

Similar Messages

SGA_MAX_SIZE and SGA_TARGET in Oracle 10G

We have the following H/W with Solaris 9
SPARC-IV 16 CPUs
32GB RAM
128GB swap
What is the optimal size of sga_target and sga_max_size that can be configured for a heavy batch processing oracle server. Nothing runs except oracle in the above server.
We have currently 3GB SGA size , however our heavy queries are very slow.
We have huge updates on tables with more than 200Millions rows.
Do we need to have JAVA_POOL if the java stored procedure are NOT used.
However we are connecting to this database using JDBC also.
Moreover ASM is enabled in this server.
You expert suggetions are always welcome.

That's not a question that can be answered easily. It depends very much on where the time is going. Three main targets:
Writing the log file - which is largely about use of disks, not memory.
Reading data - lots of single block reads suggest looking at a bigger cache
Reading and writing temp because of large sorts/hash joins - pga configuration
One difficulty with TEMP is that the I/Os are often asynchronous, so a session can do a lot of TEMP I/O without recording much time - which means it can cause a problem elsewhere without suffering a problem itself.
You didn't mention the pga_aggregate_size - which is an important consideration in 10g and can be more important than the sga sizing in DSS and batch-like processing. Between them, the SGA and PGA_aggregate_target should probably account for a very large fraction of your memory - but (since you are on Solaris) make sure you look into large memory pages and intimate shared memory, otherwise you may need to leave a lot of memory available for the O/S memory management mechanisms.
As far as the java pool is concerned, check v$sgastat for pools which constantly show free memory, and reclaim any large free volumes.
Bottom line - if you've got the memory in the box, you might as well use it in the best possible place; but at the moment we don't have enough information to tell us where it would be most useful.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

SGA_TARGET question

Oracle's 10.2 documentations states the following about SGA_TARGET.
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
Buffer cache (DB_CACHE_SIZE)
Shared pool (SHARED_POOL_SIZE)
Large pool (LARGE_POOL_SIZE)
Java pool (JAVA_POOL_SIZE)
Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
The following pools are manually sized components and are not affected by Automatic Shared Memory Management:
Log buffer
Other buffer caches, such as KEEP, RECYCLE, and other block sizes
Fixed SGA and other internal allocations
The memory allocated to these pools is deducted from the total available for SGA_TARGET when Automatic Shared Memory Management computes the values of the automatically tuned memory pools.
Under the area that illustrates what is not affected by ASMM it has "Fixed SGA and other internal allocations".
Can anyone tell me exactly what these are??

Find your answer in this metalink doc
How to determine SGA Size (7.x, 8.x, 9.x, 10g)
Doc ID: Note:1008866.6

Difference between SGA_MAX_SIZE and SGA_TARGET

Difference between SGA_MAX_SIZE and SGA_TARGET

user8645026 wrote:
Difference between SGA_MAX_SIZE and SGA_TARGETIs discussed in the database forum, not the forum for which the title is " Community Feedback and Suggestions (Do Not Post Product-Related Questions Here)".
Is also discussed in the documentation at http://tahiti.oracle.com

Log Buffer and SGA_target

Hello,
What should be the best sizing for an Oracle db 10g, windows server 2003, 4gb ram + 2 processors, process over 5 mills records a day, using sqlldr, many pls, etc.
Now it has 100m log_buffer and sga_target 612m, but it´s very low and per each second generates log files, till 2 -3 log files per second, the size of each file is 5m.
Please help, I would like it to generate log files per each hour. Please let me know the combination of parameters that I would have to change.
Thanks in advance,
Juan Angel

Mark,
I installed the DB, in fact, I am not a DBA, I am in charge of the revenue assurance department for a Telco company, I do not know that much about setting up a DB, I used to be an oracle analyst only.
How do I resize them?, the manual says about improving the checkpointing, there are two parameters of checkpointing: log_checkpoint_interval=0 seconds, and log_checkpoint_timeout=1800 seconds, 30 minutes, down some parameters of the spfile:
__db_cache_size = 343932928
__java_pool_size = 8388608
__large_pool_size = 20971520
__shared_pool_size = 134217728
background_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\BDUMP
compatible = 10.1.0.2.0
control_files = ('D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\CONTROLFILE\O1_MF_1K9O0R7F_.CTL', 'D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\CONTROLFILE\O1_MF_1K9O0R9V_.CTL')
core_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\CDUMP
db_block_size = 8192
db_create_file_dest = D:\oracle\product\10.1.0\ra\u01\oradata
db_create_online_log_dest_1 = D:\oracle\product\10.1.0\ra\u02\oradata
db_create_online_log_dest_2 = D:\oracle\product\10.1.0\ra\u03\oradata
db_domain = 'megatel.hn'
db_file_multiblock_read_count = 8
db_name = ra
db_recovery_file_dest = D:\oracle\product\10.1.0\ra\flash_recovery_area
db_recovery_file_dest_size = 30536091648
dispatchers = '(protocol=TCP)'
job_queue_processes = 10
log_archive_dest_1 = 'LOCATION=D:\oracle\product\10.1.0\ra\flash_recovery_area'
log_archive_format = 'ARC%S_%R.%T'
log_buffer = 100000256
open_cursors = 300
pga_aggregate_target = 203423744
processes = 150
remote_login_passwordfile = EXCLUSIVE
sga_target = 612368384
sort_area_size = 65536
undo_management = AUTO
undo_tablespace = UNDOTBS1
user_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\UDUMP
I appreciate your helping me.
Juan Angel

Sga_target vs sga_max_size

Hi,
I'm using ASMM and sga_target is set to 1000M.
the sga_max_size parameter should be have the same value as sga_target?
For example: what's happen if i set sga_max_size to 1200M ?
Thank's

Hi,
I think, that if you set sga_max_size to 1200M and you have SGA_target=1000M, then you could dynamicaly (without restarting instance) increase sga up to 1200M. SGA_MAX_SIZE is only about possibility to increase your sga and oracle DOESN'T allocate whole SGA_MAX_SIZE - it allocate only your sga_target.
You can test it by decreasing SGA_TARGET by command ALTER SYSTEM SET SGA_TARGET=800M SCOPE=MEMORY; and you can see that memory will be released. You can test it in other direction too - increase sga_target to 1200M and aditional memory will be allocated from free memory.
Pavel

Sga_max_size vs sga_target

Whats the difference between SGA_MAX_SIZE and SGA_TARGET? I am bit confused.
As per Oracle® Database Reference 10g Release 1 (10.1)
SGA_MAX_SIZE specifies the maximum size of the SGA for the lifetime of the instance
Then why SGA_TARGET is used.
I am missing something here. Kindly clarify.
Thanks in Advance
SID.

Max_size is what the SGA can grow to if it has to.
SGA_Target is what you'd like the SGA to be.
Then why SGA_TARGET is used.
Because you might want to dynamically grow your SGA, above the target. Suppose someone gives you a transportable tablespace and it comes from a 4K-blocksize database, and you're using 8K blocks. You have to 'alter system set db_4k_cache_size=something', but if you try that when your TARGET already equals your MAX_SIZE, you'll be told there's no room to grow the SGA, so the only way to achieve what you want is to shrink some other part of the SGA or to set the parameter in your init.ora and bounce. Either could be problematic on a production box. That's just one example: remember that 'SGA_TARGET' is indeed only a target: Oracle is allowed to exceed the target if thinks the workload makes it necessary to do so.
So the difference between MAX_SIZE and TARGET is 'slack space': memory that's not in use, but could be if you (or Oracle) determined a need for it.
On a lot of operating systems, this difference is paged out and thus doesn't mean you're wasting real, physical memory.
But on others (and I think this is true of Windows and Linux), you would indeed be 'consuming' that memory difference -which would thus amount to wasted physical memory.

SGA_MAX_SIZE & SGA_TARGET

If anyone can explain to me the relationship of these 2 parameters? Chapter 8 Database Concepts doesn't clearly define how and if they are used in tandem.
Matt

Let me simplify it a bit ...
From the links I provided:
SGA_MAX_SIZE has a default. Therefore it does not need to be set.
SGA_TARGET has a default. it does not need to be set. The default is 0, meaning NOTHING is automatically handled.
In the Reference manual description for SGA_TARGET, it provides a link to the Concepts manual. That link is there to provide more detailed information, so we follow it ...
The SGA_MAX_SIZE and SGA_TARGET are in the table of contents of the Concepts manual. Following that, we find
It is significant that SGA_TARGET includes the entire memory for the SGA, in contrast to earlier releases in which memory for the internal and fixed SGA was added to the sum of the configured SGA memory parameters. Thus, SGA_TARGET gives you precise control over the size of the shared memory region allocated by the database. If SGA_TARGET is set to a value greater than SGA_MAX_SIZE at startup, then the latter is bumped up to accommodate SGA_TARGET.
Note:
Do not dynamically set or unset the SGA_TARGET parameter. This should be set only at startup.
There is a lot of additional supporting information in the Concepts manual as well.
Message was edited by: Hans Forbrich
Corrected the interpretation of SGA_TARGET default.

SGA_MAX_SIZE != SGA_TARGET when?

Just curious... under what circumstances, when using ASMM, would I not want SGA_TARGET to equal SGA_MAX_TARGET?
Bob

Just to clarify things up,
Oracle will allocate SGA size equal to SGA_MAX_SIZE from system initially.
SGA_TARGE can be smaller than SGA_MAX_SIZE because they are buffer caches, such as KEEP, RECYCLE, and other block sizes, not affected by SGA_TARGET.
See the result below,
SYS@etest> show sga
Total System Global Area 264241152 bytes
Fixed Size                  1301408 bytes
Variable Size             216540256 bytes
Database Buffers           46137344 bytes
Redo Buffers                 262144 bytes
SYS@etest> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     TRUE
sga_max_size                         big integer 252M
sga_target                           big integer 200MOracle SGA size is 264241152/1024/1024=252M equal to SGA_MAX_SIZE while SGA_TARGET is 200M
Since I don't have other buffers set, Where the 50M goes ?
SYS@etest> select * from v$sgainfo
2 /
NAME                                  BYTES RES
Fixed SGA Size                      1301408 No
Redo Buffers                         262144 No
Buffer Cache Size                  46137344 Yes
Shared Pool Size                  150994944 Yes
Large Pool Size                     4194304 Yes
Java Pool Size                      4194304 Yes
Streams Pool Size                         0 Yes
Granule Size                        4194304 No
Maximum SGA Size                  264241152 No
Startup overhead in Shared Pool    37748736 No
Free SGA Memory Available 54525952
11 rows selected.It went to Free SGA Memory Available. Hence you can dynamically increase SGA_TARGET without reboot instance.

SGA_MAX_size, SGA_target, PROCESSES Parameters

hi
i have oracle 11g and i want to know what are the uses of these parameters
SGA_MAX_size
SGA_target
PROCESSesAnd how can i change its values ?
If any onne of u has any information about these things please help me
Regards ,

From charles Hooper;
Take a look at page 21 of the Platform Guide for 10g Release 2 (10.2) for Microsoft Windows (32-Bit):
http://download.oracle.com/docs/cd/B19306_01/win.102/b14304.pdf
Each dedicated session's connection to the database on the Windows platform requires at least 1MB of memory - just for the session to connect. With 250 sessions connected, 250MB of memory is required before the sessions even submit their first SQL statement to perform useful work. On 32 bit Windows, each process is limited by default to no more than 2GB of memory - once the 2GB memory limit is reached, the listener will no longer be able to hand off connection requests. It is possible to raise the 2GB limit to just short of 3GB through a change to the server's boot.ini file, but that still does not allow the server to use more than 4GB of memory (and each process cannot use more than roughly 3GB).
Note that you are using the SGA_TARGET. SGA_TARGET cannot be used when USE_INDIRECT_DATA_BUFFERS=TRUE, which will allow Oracle to relocate the database block buffers into the memory region above the 4GB memory mark.
Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Oracle Parameter (SGA_MAX_SIZE / SGA_TARGET)

Hello together,
since yesterday we have a new oracle database on X64 (64BIT on Windows) with SAP R/3 4.7.
The server have 24GB ram and 2x quad Core CPU.
How can give me a good value for this parameters (for oracle)
SGA_MAX_SIZE
SGA_TARGET
I don't know what is a good size for such a hugh physikal memory!
Thank you
Christian

Hello Christian,
the parameter SGA_TARGET is "not longer" supported by SAP.
Take a look at sapnote #828268
At the beginning of oracle 10g we have activated the ASMM ... but there is still a bug with oracle 10g which results in a hang situation (solved in 11g ... no backport planned)
For more information regarding to the bug... take a look at bugnotes on metalink 4466399/4472338
SGA_MAX_SIZE should be a little bit higher than the sum of all your memory pools (SGA), because of you can extend some areas dynamically on the fly (if you are using a spfile).
Regards
Stefan

Issue creating a database: SGA_MAX_SIZE and SGA_TARGET

Hello:
While creating a custom database, I am running into issues with the values I specify for SGA_MAX_SIZE and SGA_TARGET.
The install manual for the product I am creating the database for says that SGA_MAX_SIZE should be >= SGA_TARGET_SIZE. It also wants a minimum of 1Gig for SGA_Target
The Database Configuration Assistant defaulted to 0.64GB for SGA_TARGET and 0.168 for SGA_MAX_SIZE (This is clearly against the instruction in the installation manual).
Who is right? Me or the vendor?
I read some threads that indicate that the vendor may be wrong.
venki

Follow the vendor's instructions.
DBCA has never in its existence made a correct decision yet. It puts all control files and redo logs into one directory.
It doesn't create multiple members for the log file groups.
And its memory management is based on a simple algorithm that has nothing to do with any specific reality.
DBCA is intended for creating a generic database for generic purposes ... and that it does very very well.

Relative size of sga_max_size and sga_target to the physical memory

Dear Experts,
I have installed oracle 10.2.0.4 on AIX 5.3 with 32 GB of physical memory.
Let us say other applications on the server consume 10 GB of physical memory.
Now how should i plan the size of SGA_TARGET and SGA_MAX_SIZE on the same.

As per Oracle® Database Performance Tuning Guide 10g Release 2 (10.2):
You must then divide the resulting memory between the SGA and the PGA.
For OLTP systems, the PGA memory typically accounts for a small fraction of the total memory available (for example, 20%), leaving 80% for the SGA.
For DSS systems running large, memory-intensive queries, PGA memory can typically use up to 70% of that total (up to 2.2 GB in this example).
Good initial values for the parameter PGA_AGGREGATE_TARGET might be:
For OLTP: PGA_AGGREGATE_TARGET = (total_mem * 80%) * 20%
For DSS: PGA_AGGREGATE_TARGET = (total_mem * 80%) * 50%
where total_mem is the total amount of physical memory available on the system.
(http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14211/memory.htm#i49320)

Increase the SGA_MAX_SIZE and SGA_TARGET parameters

HI ,
I am using oracle 10g R2 and windows server 2003 .
My server is having 8 GB RAM .
I want to increase the SGA_MAX_SIZE and SGA_TARGET parameters .
I am using the below command , but getting the error
SQL> alter system set sga_max_size=2000M scope=spfile ;
alter system set sga_max_size=2000M scope=spfile
ERROR at line 1:
ORA-32001: write to SPFILE requested but no SPFILE specified at startup
Can someone please help ..

hi
connect as sys user and then try...
first make folder as backup and then copy the old SPFILEorcl to the same folder(backup)
now you can easily modify the files otherwise you will get error..
you will find here..
C:\ORACLE_HOME\database
SQL> alter system set sga_max_size=2000M scope=spfile ;
System altered.OR.
connect as sys user.
and do the following...
1).SQL>create pfile from spfile;
2).modify the pfile and decrease\increase the size of pools.
3).shutdown database.
4). Startup database using created pfile.
if it start ok then.
5.) Recreate the Spfile with the created Pfile.
SQL>create spfile from pfile;sarah

Increase SGA_MAX_SIZE and SGA_TARGET

Hi all,
I want to increase SGA_MAX_SIZE and SGA_TARGET in 10g. Currently we have
SQL> sho parameter sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 2384M
sga_target big integer 2384M
And we have 16GB RAM in redhat linux 4(32 bit).Oracle 10.2.0.3 DB.
Because of 32 bit OS, I was not able to increase shmmax more than 4GB.
In this situation how and how much SGA_MAX_SIZE and SGA_TARGET I can increase?
Thanks in Advance,
Sunil

Hi sunilgln,
Given the present state of things, you have to take a meassure of how many RAM is used with nothing running but the OS, that will give you the Linux footprint.
Take note of the amount of physical free memory (using top command)
Later you have to estimate how much swapping are you willing to accept, the SGA you define may be within the ranges of
FREE MEM*90% and FREE MEM*90+(OS FOOTPRINT*%SWAP MEMORY WILLING TO USE)
This is a proposal for setting this up, you need to tune and balance load depending on usage.
Another recommendation, SGA_TARGET is dynamic, SGA_MAX_SIZE is not...but you may set SGA_MAX_SIZE to a full allocation and set SGA_TARGET to a percentage that allocation and gradually use it.
What happens is: the OS will "allocate" a chunk(or chunks) the size given by SGA_MAX_SIZE, but the real usage by the database will be determined by SGA_TARGET.
Hope this helps you
Ignacio
Regards
http://oracledisect.blogspot.com

How can I change SGA_TARGET IN Oracle 10G.

Dear Experts,
Please tell me
How can I change SGA_MAX_SIZE IN Oracle 10G.
How can I change SGA_TARGET IN Oracle 10G.
How Can i recreate SPFILE IN Oracle 10G.

Dear Experts,
Please tell me
How can I change SGA_MAX_SIZE IN Oracle 10G.
How can I change SGA_TARGET IN Oracle 10G.
How Can i recreate SPFILE IN Oracle 10G.SGA_MAX_SIZE and SGA_TARGET are all to be changed by alter system statement.
The difference is, you can't make change to SGA_MAX_SIZE effective while instance is running. Need restart database to make change effective.
Your can change SGA_TARGET while instance is running, as long as it's smaller than SGA_MAX_SIZE
to recreate a spfile,
you can shutdown your database,
find a copy of valid pfile,
startup pfile=/directory/yourpfile
and
create spfile from pfile;

SGA_TARGET

Similar Messages

Maybe you are looking for