Messaging memory settings can block filetransfer

Question

I have as probebly most businessmen/woman do, save (some)of my SMS-messages to my memorycard for safety. Therefor I.ve ajusted the memory settings of messaging.
This causes an error when I want to use direct filetransfer. THis error block fore instance a lot of software installations. And I don't feel like changing the settings twice if I want to use filetransfer.
is this another bug, or is there a solution?

Answer 1

Hi,
In general a good starting point for allocating memory is as follows
OLTP system
20% memory for OS, 80% for Oracle
DSS
30% memory for OS, 70% for Oracle
so at a rough guess I would estimate that you will have available between 22 to 26 GB ram available for oracle. The next thing to think about is the split between SGA and PGA. another rule of thumb is as follows
- For OLTP systems
PGA_AGGREGATE_TARGET = (<Total Physical Memory > * 80%) * 20%
- For DSS systems
PGA_AGGREGATE_TARGET = (<Total Physical Memory > * 80%) * 50%
so this arrives at figures of PGA between 5GB and 13GB.
this then leaves the rest of the memory for SGA_MAX_SIZE and then you can start your database with an SGA_TARGET of something less than SGA_MAX_SIZE. these figures are a guide only.
for tuning the PGA you can look at the following view for a quick estimate of what the system thinks is the best value.
The following select statement can be used to find this information
SELECT round(PGA_TARGET_FOR_ESTIMATE/1024/1024) target_mb,
ESTD_PGA_CACHE_HIT_PERCENTAGE cache_hit_perc,
ESTD_OVERALLOC_COUNT
FROM v$pga_target_advice;
The output of this query might look like the following:
TARGET_MB CACHE_HIT_PERC ESTD_OVERALLOC_COUNT
63 23 367
125 24 30
250 30 3
375 39 0
where the over_allocation is 0 is the figure that the PGA should be set to.
rgds
alan