Changing PGA / SGA

We have had an error with unable to begin new thread. All connections to the db were denied. Requests were falling down. We flushed the shared pool and restarted the cc managers and users could then connect.
We are using Windows 2003 server enterprise edition platform with the /3 gb switch.
PGA_AGGREGATE_TARGET and SGA_AGGREGATE_TARGET are both set to 1G.
Is it worth trying to reduce these two memory settings?
Thanks.

Dan,
I think the answer would depend on the number of concurrent users you have. If you are on 11i, pl see MOS Doc 216205.1 (Database Initialization Parameters for Oracle Applications Release 11i) - scroll down to the bottom and you will see some recommendations for the various init.ora parameters depending on the number of users you have.
HTH
Srini

Similar Messages

PGA/SGA

Hi All,
My current oltp db is having a sga target set to 2gb and pga target set to 100mb. I see on a peak load all the sorting is done in memory what are the things to look and determine if these settings are optimal i have 32 gb host memory available. And one the DB running on the server. And if my Db occupies approximately 3gb of memory what is the fate of the remaining memory will it be used by the server process or cpu in read write operation etc....please advice
Thanks for your help

What is the problem are try to solve? Free memory is a not big problem. For example linux can use it for filesystem cache.
I see on a peak load all the sorting is done in memory If it true than you need not change PGA settings. But you can remember that 100mb pga it for all session of your DB.
Remain memory can not be used by DB. OS can use it for other purpose.

SOA-- Invoking OSB Service Getting Error :ORA-00084: global area must be PGA, SGA, or UGA

Hello Friends,
Really appreciate your help/inputs on the below Error Message encountered while running a Concurrent Program--using SOA:Same encountered in recently refreshed DEV instance, Can it be related to some Developement Instance Configuration related to SOA, as same working as expected in PROD.PLEASE ASSIST
Need your inputs on the Error Message we are getting which Invoking OSB Service.
"Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA "
Can you please review and confirm if the same encountered before or assist on the same:
XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-- Define the SOAP request according the the definition of the web service being called
l_soap_request :=
            '<?xml version = "1.0" encoding = "UTF-8"?>'
        || '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prox="http://OmnicareFinance/ProxyInput/">'
         ||   '<soapenv:Header/>'
         ||     '<soapenv:Body>'
         ||       '<prox:InboundProcess>'
         ||     '<Source_system>'||g_source_instance||'</Source_system>'
         ||     '<Run_mode>'||g_run_mode||'</Run_mode>'
         ||     '<Batch_key>'||g_batch_key||'</Batch_key>'
         ||     '<Request_id>'||g_request_id||'</Request_id>'
         ||     '<Invoice_Header_File_name>'||g_file_name||'</Invoice_Header_File_name>'
         ||     '<Invoice_Line_File_name>'||NULL||'</Invoice_Line_File_name>'
         ||     '<File_location>'||g_file_location||'</File_location>'
         ||       '</prox:InboundProcess>'
         ||     '</soapenv:Body>'
         ||   '</soapenv:Envelope>';
Oracle Apps Log File
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Response> status_code: "200"
-->Response> reason_phrase: "OK"
-->Response> http_version: "HTTP/1.1"
-->Response From OSB: <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:prox="http://OmnicareFinance/ProxyInput/"/><soapenv:Body xmlns:prox="http://OmnicareFinance/ProxyInput/"><prox:InboundProcessResponse><status>E</status></prox:InboundProcessResponse></soapenv:Body></soapenv:Envelope>
-->OSB Response: E
-->Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.capture_error_info
THANKS
ANKUR

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

Change PGA for session?

Hi there,
we are developing an OLTP application on 11gR2. As a consequence of having a lot of small transactions, we have configured a relatively small PGA and a lot of SGA memory and have configured the optimizer relevant parameters for choosing b-tree index paths.
Still we are going to have some batch Jobs, running during the non-office hours. Now my problem is, how to change the DB configuration session-wise, to be more DWH-like. While I can change the optimizer settings session wise, I have problems changing the PGA for a session.
How would you solve the problem? One solution could be to change from automatic PGA memory management to manual, that is to setting the %_AREA_SIZE parameters. These parameters can be changed session wise. But this would very much affect the behaviour of the overall system.
Any idea? What is the standard solution for such issues?
Many thanks in advance.

Centinul wrote:
user8768362 wrote:
Thanks but I mentioned this before in my own posting. I would somehow want to keep the automatic worksize area management.You can use manual PGA management at the SESSION level as Dom said, by changing the WORKAREA_SIZE_POLICY parameters, and subsequently setting the AREASIZE parameters.
user8768362 wrote:
and have configured the optimizer relevant parameters for choosing b-tree index paths.Would you be able to elaborate more on this? This sounds like a questionable change to me.
>
>Thanks but I mentioned this before in my own posting. I would somehow want to keep the automatic worksize area management.
You can use manual PGA management at the SESSION level as Dom said, by changing the WORKAREA_SIZE_POLICY parameters, and subsequently setting the AREASIZE parameters.
user8768362 wrote:
and have configured the optimizer relevant parameters for choosing b-tree index paths.Would you be able to elaborate more on this? This sounds like a questionable change to me.
>
>
Thanks but I mentioned this before in my own posting. I would somehow want to keep the automatic worksize area management.
You can use manual PGA management at the SESSION level as Dom said, by changing the WORKAREA_SIZE_POLICY parameters, and subsequently setting the AREASIZE parameters.
Thank you, that's it I think. My misunderstanding was that I had only looked at the PGA_AGGREGATE_TARGET parameter. Setting this parameter to 0, automatically sets the workarea_size to manual. Only difference is: pga_aggregate_target can only be changed on the system and not on the session level. So my solution is to change the workarea_size parameter to manual in the session and to set the xxx_area_size parameters as necessary. Thanks for the help. Sometimes the solution is there, but you just don't see it. :-)
>
user8768362 wrote:
and have configured the optimizer relevant parameters for choosing b-tree index paths.Would you be able to elaborate more on this? This sounds like a questionable change to me.Don't worry about that. I have made very good experience with these settings. I actually got the idea some years back from the book of Tom Kyte "Effective Oracle by Design". The default values
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     100are good for DWH environments. For OLTP apps the following setting can be better:
optimizer_index_caching              integer     90
optimizer_index_cost_adj             integer     25As you know the cost estimations of the optimizer are relative. So these parameters influence the decisions of the optimizer to rather choose index-paths or rather full table scans. The OLTP settings have been proved in my projects as recommendable.
Thanks.

Can oracle use more memory than pga+sga

Hi Experts,
If I have set pga 1GB and SGA 2GB then Could oracle use more than 3GB RAM from OS.
Thanks,
Please Ignore if seems to be very basic question..

Yes.
The PGA_AGGREGATE_TARGET is only a target. On a busy system, a system with frequently changing SQL patterns , Oracle may sometimes attempt to allocate a higher value.
I presume that you are on 32-bit Windows. You will hit ORA-4030 errors occassionally because Oracle on Windows is a single process (multi-threaded) and Windows limits the memory the process can address.
I suggest that you reduce your P_A_T.
Hemant K Chitale

How do I change the SGA settings?

I have Oracle 9i EE R2 installed on SuSE 8.2 Pro and my SGA settings seem incorrect. For example the Large Pool is only 16 Meg but I cannot increase it in the Enterprise Manager Console (logged in as SYS with SYSDBA rights in the manager). What text file can I change so that when I restart Oracle my Large Pool will be 32 Meg? From what I can tell, the setting I'm looking for is not in the init.ora file.

OK, I just got it working through the OEM but I had to use the OEM on my client side in Windows! Go figure that one out. :rolleyes: On the Linux SuSE side it did not even want to write to the file but on the Windows side it took the changes and bounced the server. Strange way to do it but at least it worked.

Constant change in SGA components up-down

hello,
we are developement database oracle 10gR2 on windows plateform
ASMM is on.
i am surprised to know that our smart oracle is doing a lot of shrink and grow on SGA components specially shared pool and db buffer cache
is it ok or some thing wrong?
i checked another development DB and found that it should be infrequent..
do i need to turn of the ASMM?
the out put from a query shown this
WHEN            COMPONENT                                                        OPER_TYPE     INITIAL_SIZE/1024      FINAL_SIZE/1024
May-16:19:53:17 DEFAULT buffer cache                                             STATIC        3031040                3014656
May-16:19:53:17 large pool                                                       GROW          0                      16384
May-16:19:53:17 DEFAULT buffer cache                                             INITIALIZING 3031040                3014656
May-16:19:53:17 ASM Buffer Cache                                                 STATIC        0                      0
May-16:19:53:17 DEFAULT 32K buffer cache                                         STATIC        0                      0
May-16:19:53:17 DEFAULT 16K buffer cache                                         STATIC        0                      0
May-16:19:53:17 DEFAULT 8K buffer cache                                          STATIC        0                      0
May-16:19:53:17 DEFAULT 4K buffer cache                                          STATIC        0                      0
May-16:19:53:17 DEFAULT 2K buffer cache                                          STATIC        0                      0
May-16:19:53:17 RECYCLE buffer cache                                             STATIC        0                      0
May-16:19:53:17 KEEP buffer cache                                                STATIC        0                      0
May-16:19:53:17 DEFAULT buffer cache                                             STATIC        0                      3014656
May-16:19:53:17 streams pool                                                     STATIC        0                      0
May-16:19:53:17 java pool                                                        STATIC        0                      16384
May-16:19:53:17 large pool                                                       STATIC        0                      16384
May-16:19:53:17 shared pool                                                      STATIC        0                      688128
May-16:20:30:59 shared pool                                                      GROW          688128                 704512
May-16:20:30:59 DEFAULT buffer cache                                             SHRINK        3014656                2998272
May-17:10:50:40 DEFAULT buffer cache                                             SHRINK        2998272                2981888
May-17:10:50:40 streams pool                                                     GROW          0                      16384
May-17:10:50:42 DEFAULT buffer cache                                             SHRINK        2981888                2965504
May-17:10:50:42 streams pool                                                     GROW          16384                  32768
May-17:11:04:38 shared pool                                                      GROW          704512                 737280
May-17:11:04:38 DEFAULT buffer cache                                             SHRINK        2965504                2932736
May-17:11:05:08 shared pool                                                      GROW          737280                 770048
May-17:11:05:08 DEFAULT buffer cache                                             SHRINK        2932736                2899968
May-17:11:06:01 DEFAULT buffer cache                                             SHRINK        2899968                2883584
May-17:11:06:01 shared pool                                                      GROW          770048                 786432
May-17:11:20:38 DEFAULT buffer cache                                             SHRINK        2883584                2850816
May-17:11:20:38 shared pool                                                      GROW          786432                 819200
May-28:15:24:06 DEFAULT buffer cache                                             SHRINK        2850816                2818048
May-28:15:24:06 shared pool any suggations/advice/help??
thank you

I saw this a lot on an highly OLTP system once at 10gR2. My SGA was thrashing wildly between buffer cache and shared pool due to a bug in AMM and it was causing performance impact (cursor S pin on X) for no apparent reason. This was particularly prevalent when I moved from a two to a three node cluster.
If you check out v$sga_resize_ops and see if you see a lot of thrashing (sometimes once every three seconds on one instance for 3 hours, then it'd switch to another instance), then my solution was to hardcode the various settings and disable AMM. However, in your case, you're resizing fairly irregularly - probably due to either an undersized component or workload changes. AMM is meant to do what you're describing - is it causing you any issue or is it something that you've noticed and are curious about?

Cannot change sga or pga value

Hello,
i've got a problem with changing the sga or pga values on oracle xe installed on windows xp.
When i log on to the administration page, set a new sga target, restart xe and go to the page where i can set the sga target size i still see the old values. My new values are not set.
What can i do to change the sga target value?
Thanks for help in advance,
Dirk

You don't need to restart instance when you set new value.
If you want to have that value permanently (I wouldn't) then you must change initialization parameter.
E.g.:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/start.htm#sthref512
HTH

Manually allocate SGA and PGA to a Instance?

1) Can we Manually allocate SGA and PGA to a Instance after . startup
sql>show user
connected to idle instance
2) In which type of memory user is stored in oracle mem or windows memory.
Thanx

If you are using 10g, you can modify PGA size after instance startup by alter system to change PGA_AGGREGATE_TARGET
You can't increase SGA_MAX_SIZE while instance is running. However you can change effective SGA size by alter SGA_TARGET if you are using ASMM
to find out what's current logon user,
select user from dual;
Don't quite understand your second question.

SGA/PGA best practice

With an XE limitation of 1GB for the PGA and SGA, how would one best preserve this limitation?
In other words, how would one minimise the PGA and SGA usage via ones interface with Oracle?
For instance, in a SQL query I was building I could either (The query has multiple aggregates on multiple tables in a 'one to many' join relationship):
1) Use WITH clauses
2) Use inline views
3) Use standard views
4) Use temporary tables
5) Maybe more possibilities
Without much of an insite into how Oracle 'works' it's difficult to gauge which of these is less 'resource hungry'.
Possibly there is a reference on how to use the PGA & SGA efficiently?
Or possibly a more definitive explanation on what's actually stored in these memory areas (rather than just 'prorgam' and 'system' data).
Regards all,

SGA is used in 2 main areas: parsing the SQL and avoiding disk reads by having stuff in memory. There is one SGA for all of XE instance.
PGA is used heavily for sorting, hash joining and 'working stuff'. The PGA is created for each Dedicated Server process. Much of the PGA is inside the SGA for Shared Server processes
SGA: (There are exceptions to each of these 'Rules Of Thumb' or 'ROT' statements)
Good coding technique will allow reuse of SQL and avoid as much as possible reparsing;
Use bind variables;
Do not create SQL on the fly;
Avoid dynamic SQL (concat strings to create SQL on the fly);
Forget about tweakiing the buffer cache as it is mainly a performance thing that you can't do much about in XE;
WITH clause is nice as it may reduce the count of subqueries;
Leave it with 'automatic memory management' (again a perf hit, but it will attempt to optimize mem availability);
Don't reinvent - Use the features that are loaded as they will likely get statements out faster, releasing memory faster;
Stored Views may (often do) grab unneeded table data. When joining to stored views, see whether they can be replaced by cleaner code;
Do not create SQL on the fly.
PGA:
Use shared server when feasible (at risk of performance hit);
Global Temp Tables go into PGA, watch the use;
Maximize reuabale SQL, minimze all other languages (remote or in DB) including PL/SQL;
Watch for PGA wasters such as UNION vs the better UNION ALL, and unneeded sorts;
PGA is 'swapped out' to Temporary tablespace. Make sure temp tablespace big enough ... it's not counted in the 4GB disk;
Avoid using COMMIT except at end of transaction. Avoid COMMIT in loops. Make sure undo tablespace is big enough ... it's not counted in the 4GB disk ;
Did I mention it's not a good idea to create SQL on the fly?

SGA & PGA target

Hi all,
My questions is regarding how to set up SGA & PGA target values giving DB server is MS 2003 Enterprise 64 edition sever with 63 GB of RAM. Our DB’s version is 10.2.0.3 and RACed with 2 instances.
Currently our setting for SGA is 23 GB and PGA is 4 GB. I ran the memory advisor it display different optimal values for those two instances (35 GB and 23 GB for SGA, 5 GB and 4 GB for PGA). Guess our db is not well balance loaded.
I would like to know if there is any rule(s) that SGA can’t be more than certain percentage of total RAM for the server.
Thanks a lot in advance.
Have a great weekend!!
Shirley

Hi
Here is my approach:
1) consider free physical memory (meassure must be taken with Oracle down)
2) substract a 10% of that amount as a margin
3) if the box is exclusive for Oracle, the remaining amount may be your SGA+PGA limit
4) if not is exclusive, then substract memory required for other services, then you'll get the SGA+PGA limit.
5) Substract your PGA size, giving the SGA figure
For instance
59 Gb - 6 Gb = 53 Gb - 4 Gb = 49 Gb
(63 Gb -4 Gb [estimated OS footprint + IO cache]) = 59 Gb free physical memory
Setting PGA+SGA beyond the free physical memory figure, may lead to swaping and degraded system performance.
Regards
http://oracledisect.blogspot.com

Database creation - SGA size

Hi all,
When I try to create a database using DBCA, My default SGA Size : 128. PGA:794. When I click Next button, I receive the following caution...
Following parameters do not meet the recommended minimum size requirements:
An SGA size of atleast 160MB is recommended
Do you want Database configuration Assistant to Change the Parameter? I gave ignore and I changed the SGA size to: 160, I received the bellow caution
SGA Size can not be greater than maxmimum shared memory segment size (1342177728). Refer to oracle installation guide to configrue your operation system kernel parameters.
Please suggest me on the same....
Thanks
Gir

user10737570 wrote:
My other database SGA_MAX_SIZE is 1G.
Now I'm trying to create database using DBCA. By default my sga size allocated is 128MB. It recommends SGA size should be 160MB. I'm not able to extend SGA size. Please refere my previous post...
Could you please tell me why my default screen is showing as 128MB.
ThanksThe oracle installer determines the available sga_size bij calculating free "shared memory"
This is the setting of the maximum shared memory as posted in the first message minus the memory used by your first database, minus some other shared memory stuff.
To overcome this, you have to increase the mamimum shared memory size in your kernel and if needed reboot the system.
If your system happens to be a Redhat Enterprise system, then lookup the variable called
kernel.shmmax = <a certain size>
in /etc/sysctl.conf
Increase that value, and save the file ( as root )
Next run /sbin/sysctl -p to activate the new config

Error changing value of memory_target in 11g

Hello -
I am getting this error:
SQL> alter system set memory_target=250M sid='m433d1';
alter system set memory_target=250M sid='m433d1'
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00846: could not shrink MEMORY_TARGET to specified value
Here are the current memory values:
m433d1.__db_cache_size=96468992 = 92M
m433d1.__java_pool_size=4194304 = 4M
m433d1.__large_pool_size=8388608 = 8M
m433d1.__shared_pool_size=184549376 = 176
pga = 108
SQL> show parameter pga_aggregate_target;
NAME TYPE VALUE
pga_aggregate_target big integer 12M
SQL> show parameter sga_target
NAME TYPE VALUE
sga_target big integer 200M
Why would I not be able to set to 250M, if the pga + sga = 212M? The individual componts of SGA + PGA = 284M. Therefore, it allows me to resize to resize with 275M, but not 272M:
SQL> alter system set memory_target=275M sid='m433d1';
System altered.
SQL> alter system set memory_target=272M sid='m433d1';
alter system set memory_target=272M sid='m433d1'
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00846: could not shrink MEMORY_TARGET to specified value
Any ideas are greatly appreciated!
Thanks,
mike

m433d1.__db_cache_size=96468992 = 92M
m433d1.__java_pool_size=4194304 = 4M
m433d1.__large_pool_size=8388608 = 8M
m433d1.__shared_pool_size=184549376 = 176
pga = 108
==========
I understand that these values were set explicitly.
You can see the values of db_cache_size and shared_pool itself totals to 268M
Since these values are set explicitly, then you cannot give the value for memory_target to a lower value.
OR
set all other component values to 0 and set memory_target.
Mahesh

Problem with RAM 1GB and SGA

I have RedHat 6.1 and Oracle 8.0.5 on Dell with 2xPII and 1.5GB RAM, kernel 2.2.14. When I set in kernel option 2GB RAM, make it, I can set max 70MB shared memory pool in init.ora. With 1GB RAM in kernel, I can set 419MB shared memory pool (its max from standard shmparam.h).
Question: How I can set > 419MB shared memory pool with 1.5GB RAM?
Thanks for all answers.
Jirka

The problem is the default address for mmap, you can solve the problem changing the SGA address, a good choice is 0x40000000, the procedure is:
Shutdown all your instances
cd $ORACLE_HOME/rdbms/lib
genksms -b 0x40000000 > ksms.s
make -f ins_rdbms.mk ksms.o
make -f ins_rdbms.mk ioracle
I can get up to 1 GB SGA in my 2GB machine

Tuning of SGA on Oracle 8.0.5 and AIX 4.3.3

Hi folks,
I have an AIX box running AIX 4.3.3 and Oracle 8.0.5.2.0. The original SGA settings are as follows:
shared_pool_size = 150000000
sort_area_size = 1024876
db_block_buffer = 126102
The SGA size then is:
Total System Global Area 1838467232 bytes
Fixed Size 47264 bytes
Variable Size 803287040 bytes
Database Buffers 1033027584 bytes
Redo Buffers 2105344 bytes
I changed the SGA settings to the following:
shared_pool_size = 768000000
sort_area_size = 512000000
The SGA size is now:
Total System Global Area 2227943584 bytes
Fixed Size 47264 bytes
Variable Size 214097920 bytes
Database Buffers 2013265920 bytes
Redo Buffers 532480 bytes
After this change was done, the system ran but the users had some problems running reports in JDEOneWorld.
I then downsize the SGA settings and altered the db_block_buffer to improve buffer cache hits with these settings:
db_block_buffers = 245760
shared_pool_size = 200000000
sort_area_size = 1048576
On restarting the database with the new values, I noted that the SGA size remained unchanged as below:
Total System Global Area 2278475936 bytes
Fixed Size 47264 bytes
Variable Size 264105984 bytes
Database Buffers 2013265920 bytes
Redo Buffers 1056768 bytes
I tried to increase the size of db_block_buffers to 327680 but encountered ORA-27123 when trying to startup the database. I did some searches in metalink and found an article saying that the SGA size cannot exceed 2GB on AIX platforms. (Doc ID: 114934.1). Therefore I resize the db_block_buffers back to 245760.
What puzzles me is why the SGA size does not reflect my latest init.ora settings? Does anyone have any idea on how I can get the SGA to reflect the updated values in the init.ora file?

I did a find and here are the files I got:
278529 12 -rw-r--r-- 1 oracle dba 8332 May 12 1998 /u01/app/oracle/product/805/dbs/init.ora
278531 0 lrwxrwxrwx 1 oracle dba 43 Apr 14 2001 /u01/app/oracle/product/805/dbs/initklb.ora -> /u01/app/oracle/admin/klb/pfile/initklb.ora
278532 0 lrwxrwxrwx 1 oracle dba 45 Apr 14 2001 /u01/app/oracle/product/805/dbs/initklb_0.ora -> /u01/app/oracle/admin/klb/pfile/initklb_0.ora
49154 8 -rw-r--r-- 1 oracle dba 4657 Sep 7 2000 /u01/app/oracle/product/orig_db/initklb.ora
49155 8 -rw-r--r-- 1 oracle dba 4657 Jul 27 2000 /u01/app/oracle/product/orig_db/initklb_0.ora
151553 4 -rw-r--r-- 1 oracle dba 2985 Aug 4 2006 /u01/app/oracle/product/luz/pfile/initklb.ora
49161 8 -rw-r--r-- 1 oracle dba 4118 Oct 11 11:22 /u01/app/oracle/admin/klb/pfile/initklb.ora
135169 4 -rw-r--r-- 1 oracle dba 2896 Aug 4 2006 /u01/app/oracle/admin/klb/pfile/backup/initklb.ora
49168 8 -rw-r--r-- 1 root dba 4687 Jul 21 2001 /u01/app/oracle/admin/klb/pfile/archive/initklb1.ora
49162 8 -rw-r--r-- 1 oracle dba 4657 Dec 23 1999 /u01/app/oracle/admin/klb/pfile/archive/initklb_0.ora
The instance name is KLB so the applicable files are:
278531 0 lrwxrwxrwx 1 oracle dba 43 Apr 14 2001 /u01/app/oracle/product/805/dbs/initklb.ora -> /u01/app/oracle/admin/klb/pfile/initklb.ora
278532 0 lrwxrwxrwx 1 oracle dba 45 Apr 14 2001 /u01/app/oracle/product/805/dbs/initklb_0.ora -> /u01/app/oracle/admin/klb/pfile/initklb_0.ora
49154 8 -rw-r--r-- 1 oracle dba 4657 Sep 7 2000 /u01/app/oracle/product/orig_db/initklb.ora
49155 8 -rw-r--r-- 1 oracle dba 4657 Jul 27 2000 /u01/app/oracle/product/orig_db/initklb_0.ora
151553 4 -rw-r--r-- 1 oracle dba 2985 Aug 4 2006 /u01/app/oracle/product/luz/pfile/initklb.ora
49161 8 -rw-r--r-- 1 oracle dba 4118 Oct 11 11:22 /u01/app/oracle/admin/klb/pfile/initklb.ora
135169 4 -rw-r--r-- 1 oracle dba 2896 Aug 4 2006 /u01/app/oracle/admin/klb/pfile/backup/initklb.ora
49168 8 -rw-r--r-- 1 root dba 4687 Jul 21 2001 /u01/app/oracle/admin/klb/pfile/archive/initklb1.ora
49162 8 -rw-r--r-- 1 oracle dba 4657 Dec 23 1999 /u01/app/oracle/admin/klb/pfile/archive/initklb_0.ora
Now, exclude the files in the product, backup and archive directories (the pfile should be in the pfile directory), and that leaves us with:
49161 8 -rw-r--r-- 1 oracle dba 4118 Oct 11 11:22 /u01/app/oracle/admin/klb/pfile/initklb.ora
(Which is the file that I edited)
As I mentioned previously, my client is not prepared to perform an upgrade on both Oracle and AIX. As much as I would like to have them upgrade to the latest versions, it is just not possible.
Oracle 8.0.5 does not have spfiles, so there is no way for me to edit a spfile unless this is one of those undocumented tricks floating around.

Changing PGA / SGA

Similar Messages

Maybe you are looking for