Memory on AIX

Hi,
can you help me to understand please ?
Does the following mean that I have 14Gb physical memory on my AIX server and that 26.1 percent of it is currently used by the file cache ?
myserver@oracle$prtconf | grep "Memory"
Memory Size: 14848 MB
Good Memory Size: 14848 MB
+ mem0                                                            Memory
myserver@oracle$ vmstat -v | grep "numperm percentage"
                 26.1 numperm percentage
myserver@oracle$svmon -G
               size       inuse        free         pin     virtual   mmode
memory      3801088     3781855       19233      505457     2809438     Ded
pg space     671744       13160
               work        pers        clnt       other
pin          386193           0           0      119264
in use      2809438           0      972417
PageSize   PoolSize       inuse        pgsp         pin     virtual
s    4 KB         -     2835055       13160      171521     1862638
m   64 KB         -       59175           0       20871       59175 Thank you.

Hi;
Does the following mean that I have 14Gb physical memory on my AIX server and that 26.1 percent of it is currently used by the file cache ? it tells you how many “file” pages you have in memory (in this case, it is: %26.1).
myserver@oracle$prtconf | grep "Memory"
Memory Size: 14848 MB
Good Memory Size: 14848 MB
+ mem0                                                            Memory
myserver@oracle$ vmstat -v | grep "numperm percentage"
26.1 numperm percentage
myserver@oracle$svmon -G
size       inuse        free         pin     virtual   mmode
memory      3801088     3781855       19233      505457     2809438     Ded
pg space     671744       13160
work        pers        clnt       other
pin          386193           0           0      119264
in use      2809438           0      972417
PageSize   PoolSize       inuse        pgsp         pin     virtual
s    4 KB         -     2835055       13160      171521     1862638
m   64 KB         -       59175           0       20871       59175 Please see:
http://intermediatesql.com/aix/how-oracle-uses-memory-on-aix-part-1-processes/
Regard
Helios

Similar Messages

SAP ECC6 memory and paging issues

Dear Experts
I have recently upgraded my 4.6C systems to an ECC 6 system (DB2 LUW 9.5 on AIX 5.3 TL9 64 Bit OS)
I have been running the LPAR with 14 GB of memory and we are around 100-200+ users using the system, I was monitoring using nmon and found that Physical Memory was around 99.8% Used   (14311.8MB and 22.6MB was free) also the paging space was around 37.2% in result causing the system at times to run slow which can have a very negative effect on the users.
After further investigation I found that after a system restart the Physical Memory would start around 50.9% and increased at a steady pace until it reached 99.8% that is when the system would start using the paging space which would steadily increase, I found that the only solution was a system restart at least once a week to reduce the memory consumption.
At first glance it looked like a database manger memory leak with the process db2sysc, so I searched the net with the search words u201Cdb2 memory leaku201D and found the following APARs and notes.
APAR JR30285 - Pervasive memory leak when compiling SQL statements that use SQL/XML functions
APAR IZ35230 - There is a pervasive unix-specific private memory leak in the security component
Note 1288341 - Memory leak in APPLHEAPSZ -> SQL0954C
Note 1352361 - Memory leak in shared memory area abrfci
Note 1147821 - DB6: Known Errors and available Fixes in DB2 9.5 LUW
After reading the notes and APARs I decided to updated DB2 to the latest fix pack (5SAP), but after the fix pack was implemented it did not solve the memory problem
I started look at different problems with SAP ECC6, db2 and AIX with paging/memory problems and I found the following notes to do with AIX memory and paging but none of them helped as all parameters and settings were set accordingly
789477 - Large extended memory on AIX (64-bit) as of Kernel 6.20
191801 - AIX 64-bit with very large amount of Extended Memory
973227 - AIX Virtual Memory Management: Tuning Recommendations
884393 - AIX saposcol consumes large amount of memory.
856848 u2013 AIX Extended Memory Disclaiming
1048686 u2013 Recommended AIX settings for SAP
1121904 u2013 SAP on AIX: Recommendations for Paging
1086130 u2013 DB6: DB2 Standard Parameter Settings
After even more investigation I found the following evidence suggesting AIX Virtual Memory Manager might have a problem

Shared memories inside of pool 40
Key:       42 Size:    17792992 ( 17.0 MB) DB TTAB buffer
Key:       43 Size:    53606392 ( 51.1 MB) DB FTAB buffer
Key:       44 Size:     8550392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     7014392 (   6.7 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    10241024 (   9.8 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     2769392 (   2.6 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        4 Size:      523048 (   0.5 MB) statistic area
Key:        6 Size:   692224000 ( 660.2 MB) ABAP program buffer
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:   134217828 ( 128.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       18 Size:     1835108 (   1.7 MB) Paging adminitration
Key:       19 Size:   119850000 ( 114.3 MB) Table-buffer
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900114 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 16
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....:         16
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 692224000 ( 660.2 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 1654.8 MB
..in pool 10 328.6 MB,   58% used
..in pool 40 143.3 MB,   30% used
..not in pool: 1174.1 MB
Processes........................: 413.4 MB
Extended Memory .................: 6144.0 MB
Total, minimum requirement.......: 8212.2 MB
Process local heaps, worst case..: 3814.7 MB
Total, worst case requirement....: 21882.9 MB
Errors detected..................:    0
Warnings detected................:    3

Help:oraprd user used too much memory

we have a ecc6 abap system which used 13.5GB memory.
in AIX:
svmon -U oraprd 2642791*4KB=10GB
===============================================================================
User Inuse Pin Pgsp Virtual
oraprd 2642791 69044 364678 2942062
svmon -U prdadm 491989 * 4KB=2GB
===============================================================================
User Inuse Pin Pgsp Virtual
prdadm 491989 66813 45580 516309
what puzzled me is the oraprd user used 10GB memory while the sga_targe and sga_max_size are both 5GB.
why the oraprd user used 10GB memory? Could you give me some advices. thanks very very much.
oracle 10.2.0.4 parameter:
NAME TYPE VALUE
sga_max_size big integer 5G
sga_target big integer 5G
pga_aggregate_target big integer 400M
db_cache_advice string OFF
db_cache_size big integer 16M
shared_pool_reserved_size big integer 57982058
shared_pool_size big integer 1G
large_pool_size big integer 16M
java_pool_size big integer 160M

thanks very much
all parameter:
O7_DICTIONARY_ACCESSIBILITY          boolean     FALSE
optimizerbetter_inlist_costing     string      OFF
aq_tm_processes                      integer     0
archive_lag_target                   integer     0
asm_power_limit                      integer     1
audit_file_dest                      string      /oracle/PRD/102_64/rdbms/audit
audit_sys_operations                 boolean     FALSE
audit_trail                          string      NONE
background_core_dump                 string      partial
background_dump_dest                 string      /oracle/PRD/saptrace/backgroun
backup_tape_io_slaves                boolean     FALSE
bitmap_merge_area_size               integer     1048576
blank_trimming                       boolean     FALSE
buffer_pool_keep                     string
buffer_pool_recycle                  string
circuits                             integer
cluster_database                     boolean     FALSE
cluster_database_instances           integer     1
cluster_interconnects                string
commit_point_strength                integer     1
commit_write                         string
compatible                           string      10.2.0
control_file_record_keep_time        integer     30
control_files                        string      /oracle/PRD/origlogA/cntrl/cnt
                                                 rlPRD.dbf, /oracle/PRD/sapdata
                                                 1/cntrl/cntrlPRD.dbf, /oracle/
                                                 PRD/saparch/cntrl/cntrlPRD.dbf
core_dump_dest                       string      /oracle/PRD/saptrace/backgroun
cpu_count                            integer     8
create_bitmap_area_size              integer     8388608
cursor_sharing                       string      EXACT
cursor_space_for_time                boolean     FALSE
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     0
db_block_checking                    string      FALSE
db_block_checksum                    string      TRUE
db_block_size                        integer     8192
db_cache_advice                      string      OFF
db_cache_size                        big integer 16M
db_create_file_dest                  string
db_file_multiblock_read_count        integer     128
db_files                             integer     254
db_flashback_retention_target        integer     1440
db_keep_cache_size                   big integer 0
db_name                              string      PRD
db_recovery_file_dest                string
db_recovery_file_dest_size           big integer 0
db_recycle_cache_size                big integer 0
db_unique_name                       string      PRD
db_writer_processes                  integer     1
dbwr_io_slaves                       integer     0
ddl_wait_for_locks                   boolean     FALSE
dg_broker_config_file1               string      /oracle/PRD/102_64/dbs/dr1PRD.
dg_broker_config_file2               string      /oracle/PRD/102_64/dbs/dr2PRD.
dg_broker_start                      boolean     FALSE
disk_asynch_io                       boolean     TRUE
dispatchers                          string
distributed_lock_timeout             integer     60
dml_locks                            integer     4000
drs_start                            boolean     FALSE
event                                string      10027 trace name context forev
                                                 er, level 1, 10028 trace name
                                                 context forever, level 1, 1014
                                                 2 trace name context forever,
                                                 level 1, 10183 trace name cont
                                                 ext forever, level 1, 10191 tr
                                                 ace name context forever, leve
                                                 l 1, 10753 trace name context
                                                 forever, level 2, 10891 trace
                                                 name context forever, level 1,
                                                  14532 trace name context fore
                                                 ver, level 1, 38068 trace name
                                                  context forever, level 100, 3
                                                 8085 trace name context foreve
                                                 r, level 1, 38087 trace name c
                                                 ontext forever, level 1, 44951
                                                  trace name context forever, l
                                                 ev
fast_start_io_target                 integer     0
fast_start_mttr_target               integer     900
fast_start_parallel_rollback         string      LOW
file_mapping                         boolean     FALSE
fileio_network_adapters              string
filesystemio_options                 string      SETALL
fixed_date                           string
gc_files_to_locks                    string
gcs_server_processes                 integer     0
global_context_pool_size             string
global_names                         boolean     FALSE
hash_area_size                       integer     4194304
hi_shared_memory_address             integer     0
hs_autoregister                      boolean     TRUE
java_max_sessionspace_size           integer     0
java_pool_size                       big integer 160M
java_soft_sessionspace_limit         integer     0
job_queue_processes                  integer     0
large_pool_size                      big integer 16M
ldap_directory_access                string      NONE
license_max_sessions                 integer     0
license_max_users                    integer     0
license_sessions_warning             integer     0
local_listener                       string      LISTENER_PRD
lock_name_space                      string
lock_sga                             boolean     FALSE
max_commit_propagation_delay         integer     0
max_dispatchers                      integer
max_dump_file_size                   string      UNLIMITED
max_enabled_roles                    integer     150
max_shared_servers                   integer
object_cache_max_size_percent        integer     10
object_cache_optimal_size            integer     102400
olap_page_pool_size                  big integer 0
open_cursors                         integer     800
optimizer_dynamic_sampling           integer     2
optimizer_features_enable            string      10.2.0.4
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     10
optimizer_mode                       string      ALL_ROWS
optimizer_secure_view_merging        boolean     TRUE
parallel_adaptive_multi_user         boolean     TRUE
parallel_automatic_tuning            boolean     FALSE
parallel_execution_message_size      integer     16384
parallel_instance_group              string
parallel_max_servers                 integer     80
parallel_min_percent                 integer     0
parallel_min_servers                 integer     0
parallel_server                      boolean     FALSE
parallel_server_instances            integer     1
parallel_threads_per_cpu             integer     1
pga_aggregate_target                 big integer 400M
plsql_optimize_level                 integer     2
plsql_v2_compatibility               boolean     FALSE
plsql_warnings                       string      DISABLE:ALL
pre_11g_enable_capture               boolean     FALSE
pre_page_sga                         boolean     FALSE
processes                            integer     100
query_rewrite_enabled                string      TRUE
query_rewrite_integrity              string      enforced
read_only_open_delayed               boolean     FALSE
recovery_parallelism                 integer     0
recyclebin                           string      off
replication_dependency_tracking      boolean     FALSE
resource_limit                       boolean     FALSE
resumable_timeout                    integer     0
serial_reuse                         string      disable
service_names                        string      PRD
session_cached_cursors               integer     20
session_max_open_files               integer     40
sessions                             integer     120
sga_max_size                         big integer 5G
sga_target                           big integer 5G
shadow_core_dump                     string      partial
shared_memory_address                integer     0
shared_pool_reserved_size            big integer 57982058
shared_pool_size                     big integer 1G
shared_server_sessions               integer
shared_servers                       integer     0
skip_unusable_indexes                boolean     TRUE
smtp_out_server                      string
sort_area_retained_size              integer     0
sort_area_size                       integer     2097152
spfile                               string      /oracle/PRD/102_64/dbs/spfileP
                                                 RD.ora
star_transformation_enabled          string      TRUE
statistics_level                     string      typical
streams_pool_size                    big integer 48M
tape_asynch_io                       boolean     TRUE
thread                               integer     0
timed_os_statistics                  integer     0
timed_statistics                     boolean     TRUE
trace_enabled                        boolean     TRUE
tracefile_identifier                 string
transactions                         integer     132
transactions_per_rollback_segment    integer     5
undo_management                      string      AUTO
undo_retention                       integer     43200
undo_tablespace                      string      PSAPUNDO
use_indirect_data_buffers            boolean     FALSE
use_sigio                            boolean     TRUE
user_dump_dest                       string      /oracle/PRD/saptrace/usertrace
utl_file_dir                         string
workarea_size_policy                 string      AUTO

AIX related Parameter settings...

This is related to BW 3.1C on AIX 5.2 (pSeries 690) and Oracle.
We are at 64-bit 6.40 kernel patch 66 and SAP_Basis and SAP_ABAP is patch level 47.
My question is specific to AIX related parameters as I am not able to find a very good information from notes.
I am reviewing a Earlly Watch report and not able to understand the AIX specific parameter.
Following parameters are my concern.
EM/TOTAL_SIZE_MB - 262144 MB (recommended 26301 MB)
ES/SHM_MAX_PRIV_SEGS - 64 (recommended 8)
ES/SHM_PROC_SEG_COUNT - 63 (recommended 7)
ES/SHM_SEG_COUNT - 4096 (no recommendation)
ES/SHM_USER_COUNT - 4096 (no recommendation)
ES/TABLE - SHM_SEGS (no recommendation and I understood the purpose of this parameter.)
ES/SHM_SEG_SIZE - 256 (recommendation 2048)
Our Physical memory is 32Gb and OS Swap is 26GB. As this is AIX, do I have to worry about the parameter em/initial_size_MB. it is set to 4Gb and we are planning to increase to 8GB. No recommendation SAP. but when you multiply ES/SHM_SEG_SIZE * ES/SHM_MAX_PRIV_SEGS, it comes to 16GB. So should I have to extended memory em/initial_size_MB to 16Gb or the EM/TOTAL_SIZE_MB will take care of it. I have read the IBM redBook that ES model ignores the em/initial_size_MB (Do not knwo what do they mean by this). Our model is IBM eServer pSeries 690.
I am just trying to find out the calculation/relation among these parameters to justify the team so that they are not off the limit.
Please help me and I will be really grateful to your advice.
Please let me know if you need more information.
I will appreciate your help.
Thank you.
SC.

Hello SC,
To clarify further.
The relevant notes in one place for 64-bit AIX memory management
in one place are as follows for you kernel version:
#146289 Parameter Recommendations for 64-Bit SAP Kernel
#789477 Lots of Extended Memory on AIX (64-Bit) as of Kernel 6.20
#425207 SAP memory management, current parameter ranges
#153641 Swap space requirement for R/3 64-bit kernel
When settings mentioned in the attached notes are used for AIX
64-bit systems as recommended then only EM/TOTAL_SIZE_MB is used
for the total instance extended memory, em/initial_size_MB is
ingored and the only reason to set this to the new value of
note #95454 is for the SAPPFPAR information to be more accurate as
it is looking at value em/initial_size_MB as for other Unix platforms
that don't use ES/TABLE = SHM_SEGS. The value em/initial_size_MB
will be ignored for all memory management settings purposes.
Because I suspect that ztta/roll_extension is set to 2GB then
the current values of ES/SHM_MAX_PRIV_SEGS and ES/SHM_PROC_SEG_COUNT
are not reached. The note #789477 goes into more details about
these parameters.
If RAM resources are 32GB and no other instances is on the
server then the recommendation for EM/TOTAL_SIZE_MB is made
for 26301 MB so that this is the new pool for total EM for this
instance. According to note #789477 this can be higher in some cases
and even surpass the RAM but the Early Watch team have determined
that this is the correct value. Other recommendations should
be reviewed contained in note #789477 also.
In case of any errors similar to those of note #352604, I would
suggest you review the parameters mentioned there and in note
#789477 also about these potential errors that may occur in the
future for a heavily used instance.
The references to em/initial_size_MB for SAPPFPAR are related to the
segment count in total for AIX. This was very important for 32-bit
AIX systems as there was such a shortage of available segments
for pool 10, 40, SAPOSCOL and other keys. It was important to
get the sappfpar segments as close as possible to the real value
so that you could optimize the pools etc. I many cases the
recommendation was still to ignore the segment cound in sappfpar
and manually count the used segments but all this information is
redundant for you and doesn't apply.
There are no such shortages for 64-bit and so the value is of
little importance in this case. You should therefore set
em/initial_size_MB to the same value as EM/TOTAL_SIZE_MB just
so they match. The actual SAPPFPAR output for the pool 10 and 40
sizes will not be affected by this and therefore you can use
the recommendation here for the sizing of the parameters of each the pools.
Regards, Mark

Weblogic 4.5.1, AIX 4.3, and hardware recommendations?

I have been asked to spec the hardware for the application server. We are
expecting the load to initially be very small but could grow up to 3000
concurrent users. We are thinking about initially going with an IBM H50, dual
processor (332Mhz 604E Power PC chip), 1 Gig of memory, running AIX 4.3.
We have concerns about web logic's support on AIX, it states that it is only
certified on JDK 1.1.6. Does anyone know if JDK 1.2 is supported? I believe
their is a JDK for 1.2 on AIX. We are uncomfortable about moving back to 1.1.6
just to run on an AIX box. Should we be thinking about using a Sun or NT box
instead?
Are there any other gotchas that we need to be looking for when specifying our
hardware? Does anyone have a matrix to help spec the expected memory, disk I/O,
and CPU power required for an EJB based application. I understand that this is
largely dependent on the design of the beans, but there has got to be something
out there that defines a "typical" setup.
Thanks for you help.
Tyler Van Gorder
[email protected]
Landacorp.

We have a Capacity Planning Guide that should help you in sizing your hardware
setup. It will soon be available off our website (with the rest of the docs) ...
but in the meanwhile, pl contact your sales rep for a copy.
Srikant.
Tyler Van Gorder wrote:
I have been asked to spec the hardware for the application server. We are
expecting the load to initially be very small but could grow up to 3000
concurrent users. We are thinking about initially going with an IBM H50, dual
processor (332Mhz 604E Power PC chip), 1 Gig of memory, running AIX 4.3.
We have concerns about web logic's support on AIX, it states that it is only
certified on JDK 1.1.6. Does anyone know if JDK 1.2 is supported? I believe
their is a JDK for 1.2 on AIX. We are uncomfortable about moving back to 1.1.6
just to run on an AIX box. Should we be thinking about using a Sun or NT box
instead?
Are there any other gotchas that we need to be looking for when specifying our
hardware? Does anyone have a matrix to help spec the expected memory, disk I/O,
and CPU power required for an EJB based application. I understand that this is
largely dependent on the design of the beans, but there has got to be something
out there that defines a "typical" setup.
Thanks for you help.
Tyler Van Gorder
[email protected]
Landacorp.

Web Logic 4.5.1, AIX 4.3, & hardware recommendations?

I have been asked to spec the hardware for the application server. We are
expecting the load to initially be very small but could grow up to 3000
concurrent users. We are thinking about initially going with an IBM H50, dual
processor (332Mhz 604E Power PC chip), 1 Gig of memory, running AIX 4.3.
We have concerns about web logic's support on AIX, it states that it is only
certified on JDK 1.1.6. Does anyone know if JDK 1.2 is supported? I believe
their is a JDK for 1.2 on AIX. We are uncomfortable about moving back to 1.1.6
just to run on an AIX box. Should we be thinking about using a Sun or NT box
instead?
Are there any other gotchas that we need to be looking for when specifying our
hardware? Does anyone have a matrix to help spec the expected memory, disk I/O,
and CPU power required for an EJB based application. I understand that this is
largely dependent on the design of the beans, but there has got to be something
out there that defines a "typical" setup.
Thanks for you help.
Tyler Van Gorder
[email protected]
Landacorp.

We have a Capacity Planning Guide that should help you in sizing your hardware
setup. It will soon be available off our website (with the rest of the docs) ...
but in the meanwhile, pl contact your sales rep for a copy.
Srikant.
Tyler Van Gorder wrote:
I have been asked to spec the hardware for the application server. We are
expecting the load to initially be very small but could grow up to 3000
concurrent users. We are thinking about initially going with an IBM H50, dual
processor (332Mhz 604E Power PC chip), 1 Gig of memory, running AIX 4.3.
We have concerns about web logic's support on AIX, it states that it is only
certified on JDK 1.1.6. Does anyone know if JDK 1.2 is supported? I believe
their is a JDK for 1.2 on AIX. We are uncomfortable about moving back to 1.1.6
just to run on an AIX box. Should we be thinking about using a Sun or NT box
instead?
Are there any other gotchas that we need to be looking for when specifying our
hardware? Does anyone have a matrix to help spec the expected memory, disk I/O,
and CPU power required for an EJB based application. I understand that this is
largely dependent on the design of the beans, but there has got to be something
out there that defines a "typical" setup.
Thanks for you help.
Tyler Van Gorder
[email protected]
Landacorp.

Can large page improve timesten performance on aix??

hello, chris:
Can large page imporove timesten performance on aix? we havenot test it yet, I just want to know whether it is ok?? thank you.

Enabling large page support on AIX may help performance under some circumstances (typically with large datastores). TimesTen does support use of large pages on AIX and no special action is needed on the TimesTen side to utilise large pages. Here is some information on this which should eventually appear in the TimesTen documentation.
The TimesTen shared memory segment for AIX has been created with the flags
( SHM_PIN | SHM_LGPAGE) necessary for large page support for many releases.
It used to be the case that special kernel flags needed to be enabled so it
was never documented as being supported. Subsequent AIX releases have made
enabling large pages a matter of system administration.
1) Enable capabilities (chuser)
2) Configure page pool (vmo -r)
3) Enable memory pining (vmo -p)
4) [restart timesten daemons]
The documentation is quoted below.
AIX maintains separate 4 KB and 16 MB physical memory pools. You can
specify the amount of physical memory in the 16 MB memory pool using the vmo
command. Starting with AIX 5.3, the large page pool is dynamic, so the amount
of physical memory that you specify takes effect immediately and does not
require a system reboot. The remaining physical memory backs the 4 KB virtual
pages.
AIX treats large pages as pinned memory. AIX does not provide paging
support for large pages. The data of an application that is backed by large
pages remains in physical memory until the application completes. A security
access control mechanism prevents unauthorized applications from using large
pages or large page physical memory. The security access control mechanism
also prevents unauthorized users from using large pages for their
applications. For non-root user ids, you must enable the CAP_BYPASS_RAC_VMM
capability with the chuser command in order to use large pages. The following
example demonstrates how to grant the CAP_BYPASS_RAC_VMM capability as the
superuser:
# chuser capabilities=CAP_BYPASS_RAC_VMM,CAP_PROPAGATE <user id>
The system default is to not have any memory allocated to the large page
physical memory pool. You can use the vmo command to configure the size of
the large page physical memory pool. The following example allocates 4 GB to
the large page physical memory pool:
# vmo -r -o lgpg_regions=64 -o lgpg_size=16777216
To use large pages for shared memory, you must enable the SHM_PIN shmget()
system call with the following command, which persists across system reboots:
# vmo -p -o v_pinshm=1
To see how many large pages are in use on your system, use the vmstat -l
command as in the following example:
# vmstat -l
kthr memory page faults cpu large-page
r b avm fre re pi po fr sr cy in sy cs us sy id wa alp flp
2 1 52238 124523 0 0 0 0 0 0 142 41 73 0 3 97 0 16 16
From the above example, you can see that there are 16 active large pages, alp, and
16 free large pages, flp.
Documentation is at:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibmaix.prftungd/doc/prftungd/large_page_ovw.htm
Chris

Sun JVM Performance Issue in Sun Solaris 10 (SPARC)

Hi,
Issue : Performance issue after the migration of a Java application from IBM-AIX 5 to Sun Solaris 10 (SPARC)
I am facing performance issue after the migration of a Java application from IBM-AIX 5.3 to Sun Solaris 10 (SPARC).
Normally the application takes less than 1 hour to complete the process in AIX, but after migration in Solaris the application is taking 4+ hours.
The Java version of IBM AIX is ,
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pap32dev-20051104)
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20051103 (JIT enabled)
The Java version of Solaris 10 is,
Java(TM) Platform, Standard Edition for Business (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)
Description of Application
The application merges 2 XML files of size 300 MB each using DOM Parser and generates flat file according to certain business logic.No remote files are using for the file generation. There are two folders and around 200 XML file in each folders of similar names. The application loads 2 similar XML file at a time from each folder and Processes. Same way, the application processes all the 200 XML file pairs using loop.
The JVM Parameters are given below.
/usr/java5/bin/java -cp $CLASSPATH -Xms3072m -Xmx3072M com.db.mcc.creditderiv.GCDXMLTransProc
Here the extended swap memory in AIX is 3072 (3GB). After copying the same tode to Solaris, the
application started throwing java.lang.OutofMemoryError. So that we have increased the swap memory up to 12 GB.
Since 32bit Java allows maximum 4 GB extended memory we started using 64 Bit Java in Solaris using -d64 argument.
The Current JVM Parameter in Solaris is given below.
java -d64 -cp $CLASSPATH -Xms8192m -Xmx12288m com.db.mcc.creditderiv.GCDXMLTransProc ( 64 GB Swap Memory is available in the System)
We have tried the following options
1.       Extended heap size up to 12 GB using -xms and -xmx parameters and tried multiple -XX options. Earlier the application was working fine in AIX with 3.5 GB extended heap size. ( 64 GB Swap Memory is available in the System)
2.       Downloaded and installed the Solaris SPARC Patches from the website,
     http://java.sun.com/javase/downloads/index_jdk5.jsp
4. Downloaded and installed XML and XSLT patch from sun website
5.       Tried to run the Java in server mode using -server option.

A 64 bit VM is not necessarily faster than a 32 bit one. I remember at least on suggestion that it could be slower.
Make sure you use the -server option.
As a guess IBM isn't necessarily a slouch when it comes to Java. It might simply be that their VM was faster. Could have used a different dom library as well.
Could be an environment problem of course.
Profiling the application and the machine as well might provide information.

Creating user -- STORAGE_PARAMETER_WRONG_SET

Hello!
We made a new installation of our ERP 6.0. And now i should create the users.
SU01--> I created a username and chose "create".
First I got a problem that the company address is not created yet. I skipped it because the country ID was unknown/not defined.
so i wanted to saved my user.....THEN it happend! it took some time and then there was this nice error message:
STORAGE_PARAMETER_WRONG_SET
Short dump has not been completely stored (too big).
Short text:
The system is configured incorrectly.
What happened?
The current program had to be terminated because of an error when installing the R/3 System.
The program had already requested 235346480 bytes from the operating system with 'malloc' when the operating system reported after a further memory request that there was no more memory space available.
It´s a Windows Server 2003, with 3GB Ram. DB is MS SQL Server 2005.
Thanks for your suggestions.!
Edited by: Geraldine Pastor Guzman on Jun 30, 2008 4:41 PM

Hi,
According to the note 326949,Parameters that are recommend in the instance profile:
Also please go through the SAP NOTE 326949 for more information.
ztta/roll_first = 1       : Allocation unit for the early
                          : allocation of the roll area.
ztta/roll_area = 6500000 : Maximum roll area per work process.
ztta/roll_extension = 2000000000 : Size of a user context in the
                          : extended memory for AIX. Default: 250000000
                          : The parameter value should be higher than
                          : the value of em/address_space_MB since the
                          : lower value of the user
                          : context has a limiting effect. Setting the
                          : ztta/roll_extension to 2GB ensures that
                          : only the parameter
                          : em/address_space_MB defines the size of the
                          : user context in the extended memory.
abap/heap_area_dia        : Limiting the heap area for
                          : dialog work processes. Set the value
                          : according to the calculation instructions in
                          : Note 387370.
abap/heap_area_nondia     : Limiting the heap area for
                          : non-dialog work processes. Set the value
                          : according to the calculation instructions in
                          : Note 387370.
abap/heap_area_total = 2000000000 : Limiting the heap area
                        : altogether. You can extend the area if
                        : necessary.
rdisp/ROLL_SHM = 4096    : Size of the roll buffer in the shared memory.
rdisp/ROLL_MAXFS = 4096 : Maximum size of the roll file. Setting the
                        : parameter to the same value as rdisp/ROLL_SHM
                        : has the effect that, after reaching the user quota
                        : in the extended memory,
                        : files are sent straight to the heap rather than the file system.
rdisp/PG_SHM = 4096      : Size of the ABAP paging buffer in the shared
                        : memory.
rdisp/PG_MAXFS = 32768   : Maximum size of the ABAP paging file.
em/global_area_MB = 24   : Size of the global extended memory.
Hope this helps you
Thanks
Rama

Hot deploy on web logic 4.5.1

Hi,
I'm following the steps for hot deployment given at
http://www.weblogic.com/docs45/techdeploy/hotdeploy.html using
weblogic.deploy
I'm trying to redeploy an EJB with the same jar filename.
It gives the following error - NullPointerException
at
weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
at
weblogic.ejb.common.EJBManager_WLStub.deploy(EJBManager_WLStub.java:174)
at
weblogic.deploy.deploy(deploy.java:132).................
Please help. Any suggestions would be very helpful.
Rgds
Varma

We have a Capacity Planning Guide that should help you in sizing your hardware
setup. It will soon be available off our website (with the rest of the docs) ...
but in the meanwhile, pl contact your sales rep for a copy.
Srikant.
Tyler Van Gorder wrote:
I have been asked to spec the hardware for the application server. We are
expecting the load to initially be very small but could grow up to 3000
concurrent users. We are thinking about initially going with an IBM H50, dual
processor (332Mhz 604E Power PC chip), 1 Gig of memory, running AIX 4.3.
We have concerns about web logic's support on AIX, it states that it is only
certified on JDK 1.1.6. Does anyone know if JDK 1.2 is supported? I believe
their is a JDK for 1.2 on AIX. We are uncomfortable about moving back to 1.1.6
just to run on an AIX box. Should we be thinking about using a Sun or NT box
instead?
Are there any other gotchas that we need to be looking for when specifying our
hardware? Does anyone have a matrix to help spec the expected memory, disk I/O,
and CPU power required for an EJB based application. I understand that this is
largely dependent on the design of the beans, but there has got to be something
out there that defines a "typical" setup.
Thanks for you help.
Tyler Van Gorder
[email protected]
Landacorp.

Initial_size_MB

memlimits output
Posted: Apr 21, 2006 8:46 PM Reply
Hi,
When i give memlimits command from the sidadm id, i am getting the following output:
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Restart, set early swap allocation (PSALLOC=early)
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Check the maximum data size per process (malloc)
Check the available swap space (malloc in several processes)
Process 1859680 allocating ... Size = 4096MB Total: 4096MB
Upper size limit 4096 reached. Finish checking
Total available swap space = 4096MBCheck the maximum size of mapped file (mmap anonymous,dev/zero)
Check protection operations on this area (protect)
Trying to mmap 512MB ... successfull
Trying to mmap 768MB ... successfull
Trying to mmap 1024MB ... successfull
Trying to mmap 1280MB ... successfull
Trying to mmap 1536MB ... successfull
Trying to mmap 1792MB ... successfull
Trying to mmap 2048MB ... successfull
Trying to mmap 2304MB ... successfull
Trying to mmap 2560MB ... successfull
Trying to mmap 2816MB ... successfull
Trying to mmap 3072MB ... successfull
Trying to mmap 3328MB ... successfull
Trying to mmap 3584MB ... successfull
Trying to mmap 3840MB ... successfull
Trying to mmap 4096MB ... successfull
Upper size limit 4096 reached. Finish checking
Trying to mprotect 4096MB ... successfull
Maximum mapped file size: 4096MB
Maximum mprotect size: 4096MB
R/3 parameter em/initial_size_MB up to 4096 permitted
Check the maximum address space per process usable
both by process local memory and mapped file
Maximum address space ( mmap(4096 MB)+ malloc(1676MB) ): 5772MB
Result
Maximum heap size per process........: 4096 MB
measurement limited to 4096 MB
this value is probably limited by swap space
Maximum mapped file size (mmap)......: 4096 MB
measurement limited to 4096 MB
Maximum protectable size (mprotect)..: 4096 MB
measurement limited to 4096 MB
em/initial_size_MB > 4096 MB will not work
Maximum address space per process....: 5772 MB
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
Check the ones in bold, the swap space in our system is 20GB, the inital size_MB value is 8192 and the blocksize_kb is also 8192. Still the message seems to be like that, what is reason behind this ?
Ours is AIX 64bit and NW04 (R/3 is ECC 5.0)
Thanks

Hi Aravind S,
Note #332591 (memlimits output irritating) contains related information about memlimits and extended memory. The file dev_disp and ST02 transaction are better indications of the amount of memory being allocated to extended memory.
If as recommended according to note #789477 (Lots of Extended Memory on AIX (64-Bit) as of Kernel 6.20) the parameter ES/TABLE = SHM_SEGS, then em/initial_size_MB is not used to set the total extended memory of that instance but instead EM/TOTAL_SIZE_MB.
Notes #835474 (More than 32GB extended memory) and the note #835474 for older releases contain some more related information about relationship between em/blocksize_KB and em/initial_size_MB (or EM/TOTAL_SIZE_MB).
I hope this helps, after setting parameters according to notes above and #146289 (Parameter Recommendations for 64-Bit SAP Kernel), then you can ignore this return from memlimits.
Regards, Mark

Memory usage problem on AIX 7.1

Hi,
We are running Oracle 11GR2 EE on AIX 7.1 and keep getting alerts on the pgchecks (memory paging).
The alerts are coming from another system monitoring tool (Hobbit), but our sys admins are telling us it is because we are overallocating memory.
In our case, we have an 8G SGA for the only database.
Then, we are running grid and ASM.
How can I check the actual (real) memory usage by individual processes of our Oracle database, our emagent (OMS agent), and for our ASM. In our case, we have 32G of Real Memory installed, and we should not be having a memory paging issue.
For the Oracle database, it is set for 8G.
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pga_aggregate_target                 big integer 0
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 8480M
sga_target                           big integer 0For our ASM instance, it is set for 270M
SQL> sho sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pga_aggregate_target                 big integer 0
sga_max_size                         big integer 272M
sga_target                           big integer 0

do as below (vmstat takes 2 minutes to complete)
bcm@bcm-laptop:~$ vmstat 6 20
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b   swpd   free   buff cache   si   so    bi    bo   in   cs us sy id wa
0 0      0 1347636 81396 1592120    0    0   264    22 382 651 8 3 84 5
0 0      0 1347664 81404 1592144    0    0     0    13 515 1028 4 1 95 0
0 0      0 1353136 81412 1592144    0    0     0    14 507 1021 3 1 95 0
0 0      0 1353012 81420 1592144    0    0     0    23 523 1033 3 1 95 0
0 0      0 1353044 81428 1592144    0    0     0    13 513 1026 3 1 96 0
0 0      0 1353044 81436 1592144    0    0     0    15 517 1045 3 2 95 0
0 0      0 1352920 81444 1592144    0    0     0    15 505 1012 3 1 96 0
1 0      0 1347448 81452 1592156    0    0     1    21 521 1038 4 2 94 0
0 0      0 1347448 81460 1592156    0    0     0    28 513 1030 3 2 95 0
0 0      0 1347448 81468 1592180    0    0     1    21 529 1053 4 1 95 0
0 0      0 1347200 81484 1592176    0    0     0    39 530 1067 3 2 95 0
1 0      0 1347200 81492 1592172    0    0     0    14 530 1058 3 1 96 0
0 0      0 1352796 81500 1592172    0    0     0    17 514 1034 3 2 95 0
0 0      0 1352796 81508 1592180    0    0     0    21 516 1049 6 1 92 0
0 0      0 1352764 81516 1592180    0    0     0    15 506 1024 2 1 95 1
0 0      0 1352252 81524 1592180    0    0     0    15 563 1090 3 2 95 0
0 0      0 1351836 81532 1592180    0    0     0    15 550 1066 4 1 94 0
0 0      0 1346768 81540 1592200    0    0     1    18 547 1111 4 2 94 0
1 0      0 1346152 81548 1592204    0    0     0    69 524 1059 3 2 94 0
0 0      0 1346472 81556 1592244    0    0     1    17 498 1012 2 1 96 0

Issue with Memory in SAP(R/3 3.1I )/OS (AIX 5.2)

Hi

We have problem with the memory settings in SAP(R/3 3.1I )/OS (AIX 5.2). One of the customizing ABAP program failing at background but works fine when we run with same variant in forgeground.


Below are the current parameters values in system

em/initial_size_MB 1024 
ztta/roll_first 1024 
ztta/roll_area 7000064 
rdisp/ROLL_SHM 6528 
rdisp/ROLL_MAXFS 23040 
rdisp/PG_SHM 5120 
rdisp/PG_MAXFS 34560 
abap/heap_area_dia 188743680 
abap/heap_area_nondia 400556032 
abap/heap_area_total 838860800 
abap/heaplimit 52428800 
abap/swap_reserve 20971520 
ztta/roll_extension 200068300 
em/blocksize_KB 1024 
em/stat_log_size_MB 40 
em/stat_log_timeout 600 
ipc/shm_psize_01 -10 
ipc/shm_psize_02 -40 
ipc/shm_psize_03 -10 
ipc/shm_psize_04 -10 
ipc/shm_psize_06 -40 
ipc/shm_psize_07 -10 
ipc/shm_psize_08 -10 
ipc/shm_psize_09 -10 
ipc/shm_psize_10 276000000 
ipc/shm_psize_31 -10 
ipc/shm_psize_33 -10 
ipc/shm_psize_34 -10 
ipc/shm_psize_40 688000000 
ipc/shm_psize_51 -10 
ipc/shm_psize_52 -10 
ipc/shm_psize_54 -10 

I have checked at os level with below command, Its shows there is problem at ipc/shm_psize_10 :276000000
ipc/shm_psize_40 : 688000000 but the current values are higher then what the below recomands. Can you plz suggest me the correct values for the above parameters. If any problems with above parameters.


witco-12:ncpadm 1> sappfpar check pf=NCP_DVEBMGS00_WITCO-12

sapparam(2): fopen("NCP_DVEBMGS00_WITCO-12","r"): No such file or directory
No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
================================================================================
== Checking profile:
================================================================================

***ERROR: Size of shared memory pool 10 too small
================================================================================
SOLUTION: Increase size of shared memory pool 10 
 with parameter: ipc/shm_psize_10 =36000000 
***ERROR: Size of shared memory pool 40 too small
================================================================================
SOLUTION: Increase size of shared memory pool 40 
 with parameter: ipc/shm_psize_40 =50000000 
Shared memory disposition overview 
================================================================================
Shared memory pools 
Key: 10 Pool 
 Size configured.....: 12000000 ( 11.4 MB) 
 Size min. estimated.: 31988070 ( 30.5 MB) 
 Advised Size........: 36000000 ( 34.3 MB) 
Key: 40 Pool for database buffers 
 Size configured.....: 14250000 ( 13.6 MB) 
 Size min. estimated.: 47166184 ( 45.0 MB) 
 Advised Size........: 50000000 ( 47.7 MB) 
Shared memories inside of pool 10 
Key: 1 Size: 2000 ( 0.0 MB) System administration 
Key: 3 Size: 13100000 ( 12.5 MB) Disp. communication areas 
Key: 4 Size: 100000 ( 0.1 MB) statistic area 
Key: 7 Size: 14838 ( 0.0 MB) Update task administration 
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer 
Key: 12 Size: 120000 ( 0.1 MB) TemSe Char-Code convert Buf. 
Key: 13 Size: 500000 ( 0.5 MB) Alert Area 
Key: 14 Size: 4400000 ( 4.2 MB) Presentation buffer 
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring 
Key: 17 Size: 65636 ( 0.1 MB) Roll administration 
Key: 18 Size: 65636 ( 0.1 MB) Paging adminitration 
Key: 19 Size: 6000000 ( 5.7 MB) Table-buffer 
Key: 31 Size: 1806000 ( 1.7 MB) Dispatcher request queue 
Key: 33 Size: 2048000 ( 2.0 MB) Table buffer, part.buffering 
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin. 
Key: 52 Size: 20000 ( 0.0 MB) Message Server buffer 
Key: 54 Size: 16384 ( 0.0 MB) Export/Import buffer 
 
Shared memories inside of pool 40 
Key: 2 Size: 961296 ( 0.9 MB) Disp. administration tables 
Key: 6 Size: 26112000 ( 24.9 MB) ABAP program buffer 
Key: 41 Size: 6010000 ( 5.7 MB) DB statistics buffer 
Key: 42 Size: 596968 ( 0.6 MB) DB TTAB buffer 
Key: 43 Size: 3898344 ( 3.7 MB) DB FTAB buffer 
Key: 44 Size: 1850344 ( 1.8 MB) DB IREC buffer 
Key: 45 Size: 1338344 ( 1.3 MB) DB short nametab buffer 
Key: 46 Size: 20480 ( 0.0 MB) DB sync table 
Key: 47 Size: 3072000 ( 2.9 MB) DB CUA buffer 
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer 
Key: 49 Size: 3000000 ( 2.9 MB) Spool admin (SpoolWP+DiaWP) 
 
Shared memories outside of pools 
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0 
Key: 58900100 Size: 4096 ( 0.0 MB) SCSA area 
Nr of operating system shared memory segments: 4 
Shared memory resource requirements estimated 
================================================================ 
Nr of shared memory descriptors required for 
Extended Memory Management (unnamed mapped file).: 1 
 
Total Nr of shared segments required.....: 5 
System-imposed number of shared memories.: 11 
Shared memory segment size required min..: 36000000 ( 34.3 MB) 
System-imposed maximum segment size......: 3489660928 (3328.0 MB) 
R/3-imposed maximum segment size.........: 2147483647 (2048.0 MB) 
 
Swap space requirements estimated 
================================================ 
Shared memory....................: 86.2 MB 
..in pool 10 11.4 MB, 266% used !! 
..in pool 40 13.6 MB, 330% used !! 
..not in pool 0.4 MB 
Processes........................: 30.9 MB 
Extended Memory .................: 128.0 MB 
 
Total, minimum requirement.......: 245.1 MB 
Process local heaps, worst case..: 762.9 MB 
Total, worst case requirement....: 1008.1 MB 
 
Errors detected..................: 2 
Warnings detected................: 0 

Edited by: Sambireddy Authu on Jan 19, 2011 1:47 PM
Edited by: Sambireddy Authu on Jan 19, 2011 1:49 PM

Hi APR, 
I have checked sm21, St22 and dev_wp<no> file at OS level but I am not finding the exact error . 
Tue Jan 18 15:15:29 2011 
A WP has reached abap/heaplimit = 52428800 bytes 
Tue Jan 18 15:15:37 2011 
M -
C-STACK -
 
NONAME at 0x103804cc 
NONAME at 0x103806e4 
NONAME at 0x1046a02c 
Signal 0 in M -
 
M ***LOG Q0E=> DpSigGenHandler, signal ( 4) [dpuxtool 0501] 
M ThSigHandler: signal (step 4) 
M Modeinfo for User T17/M0 
M tm state = 2 
M uid = 18 
M term type = 0x0 
M display = 0x0 
M cpic_no = 0 
M cpic_idx = -1 
M usr = >GONUGRA < 
M terminal = > < 
M client = >088< 
M convid = > < 
M appc_tm_conv_idx = -1 
M imode = 2 
M mode state = 0x42 
M th_errno = 0 
M async_receives = 0 
M cpic_receive = 0 
M em handle = 4 
M roll state = 2 
M abap state = 2 
M em state = 3 
M eg state = 1 
M spa state = 3 
M enq state = 0 
M next hook = T-1/U-1/M255 
M master hook = T-1/U-1/M255 
M slave hook = T-1/U-1/M255 
M debug_tid = -1 
M mode type = 0x1 
M debug = 0 
M tcode = > < 
M client convid = > < 
M server convid = > < 
M lock = 0 
M max enq infos = 0 
M act enq infos = 0 
M
M ***************************************************************************** 
M * 
M * LOCATION SAP-Server witco-10_NCQ_00 on host witco-10 (wp 17) 
M * ERROR ThSigHandler: signal 
M *
M * TIME Tue Jan 18 15:15:37 2011 
M * RELEASE 31I 
M * COMPONENT Taskhandler 
M * VERSION 1 
M * RC 11 
M * MODULE thxxhead.c 
M * LINE 7209 
M * COUNTER 103 
M *
M ***************************************************************************** 
M
M ***LOG R68=> ThIRollBack, roll back () [thxxhead 9123] 
M ***LOG R68=> ThIRollBack, roll back () [thxxhead 9123] 
X <ES> RecoverAll 
X <ES> RecoverFreeList 
X <ES> RecoverAll 
X <ES> RecoverFreeList 
A 
A ** RABAX: could not save part LEV_SN_DATA_ENV of dump. 
A 
A Tue Jan 18 15:15:38 2011 
A 
A ** RABAX: could not save part LEV_SN_ITABS of dump. 
M ***LOG Q02=> wp_halt, WPStop (Workproc17 60272) [dpuxtool 0773] 
 
trc file: "dev_w17", trc level: 1, release: "31I" 
 
* 
ACTIVE TRACE LEVEL 1 
ACTIVE TRACE COMPONENTS all, M 
* 
M ***LOG Q01=> tskh_init, WPStart (Workproc17 2 19746) [thxxhead 0898] 
M calling db_connect ... 
B Try to connect as default user 
B Using SQL-Net V2 with tnsname = 'NCQ' 
B No TNS_ADMIN in environment 
B Setting TNS_ADMIN to '/usr/sap/trans' (profile-parameter DIR_TRANS) 
B Got 'NCQ' for SID from profile-parameter 'rsdb/oracle_sid' 
B Connecting via TNS_ADMIN=/usr/sap/trans, tnsname=NCQ 
B Got NLS_LANG=AMERICAN_AMERICA.US7ASCII from environment 
B 
B Tue Jan 18 15:15:40 2011 
B Now I'm connected to ORACLE 
B Database instance NCQ is running on witco-10 with ORACLE version 8.1.7.4.0 
M db_connect o.k. 
X <ES> client 17 initializing .... 
X ES initialized. 
A Attached to PXA (address 63026e00, size 621972496) 
S frontend print server enabled 
S Form-Textpool enabled (TSP06T has 4 fields) 
S OMS support enabled (TSPLOMS has 13 fields, TSPROMS has 8 field) 
M ThCheckPrevUser: clean previous user T17/U18/M0 
M Modeinfo for User T17/M0 
M tm state = 2 
M uid = 18 
M term type = 0x0 
M display = 0x0 
M cpic_no = 0 
M cpic_idx = -1 
M usr = >GONUGRA < 
M terminal = > < 
M client = >088< 
M convid = > < 
M appc_tm_conv_idx = -1 
M imode = 2 
M mode state = 0x42 
M th_errno = 11 
M async_receives = 0 
M cpic_receive = 0 
M em handle = 4 
M roll state = 2 
M abap state = 2 
M em state = 3 
M eg state = 1 
M spa state = 3 
M enq state = 0 
M next hook = T-1/U-1/M255 
M master hook = T-1/U-1/M255 
M slave hook = T-1/U-1/M255 
M debug_tid = -1 
M mode type = 0x1 
M debug = 0 
M tcode = > < 
M client convid = > < 
M server convid = > < 
M lock = 0 
M max enq infos = 0 
M act enq infos = 0 
M ***LOG R47=> ThResFree, delete (001023) [thxxmode 0780] 
B
B Tue Jan 18 15:22:09 2011 
B dbtran INFO (initialize_tran): 
B maxblocking_factor = 25, 
B minblocking_factor = 10, 
B maxin_blocking_factor = 254, 
B minin_blocking_factor = 10, 
B preferunion_all = 0, 
B preferunion_for_views = 0, 
B preferin_itab_opt = 0, 
B preferfix_blocking = 0, 
B usehints = 0, 
B optgele_to_between = 0, 
B convafter_aggregat = 0, 
B allowNULL_for_agg = 0, 
B rownumfor_count = 1

ORA-27101: shared memory realm does not exist AIX 5.3 Oracle 10.2 g

Hi everybody, please help!!!!!
I have a problem on my ERP, whe the users run reports called ZSD01, ZSD07 these programs exeed the lifetime period of 600 seconds and cause an ABAP - runtime error by time out.
using the TX ST22 I get a report indicating the folow:
C Attaching to DB Server R3P (con_hdl=0,svchp=0x114e60fa8,srvhp=0x1144295e8)
C     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12537:
C     ORA-12537: TNS:connection closed
C *** ERROR => CONNECT failed with sql error '12537'
[dbsloci.c    11239
C     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1034:
C     ORA-01034: ORACLE not available
C ORA-27101: shared memory realm does not exist
C IBM AIX RISC System/6000 Error: 2: No such file or directory
C Detaching from DB Server (con_hdl=0,svchp=0x114e60fa8,srvhp=0x1144295e8)
C *** ERROR => CONNECT failed with sql error '1034'
[dbsloci.c    11239]
My Oracle and SAP instances are runnig and this error occurs when on the report select a several sales offices and was oerating 'til last moth ago...
Thanks!!!!!!!!!!!!!!!
Regards,
Oscar D'Lima

Hi,
C ORA-12537: TNS:connection closed
C *** ERROR => CONNECT failed with sql error '12537'
[dbsloci.c 11239
C OCISessionBegin(OCI_DEFAULT) failed with SQL error 1034:
C ORA-01034: ORACLE not available
C ORA-27101: shared memory realm does not exist
C IBM AIX RISC System/6000 Error: 2: No such file or directory
C Detaching from DB Server (con_hdl=0,svchp=0x114e60fa8,srvhp=0x1144295e8)
C *** ERROR => CONNECT failed with sql error '1034'
The ORA-27101 error is generated when the shared memory key generated by the client does not match any currently existing keys. This is to be expected if the ORACLE_HOME or ORACLE_SID used by the client is not the same as that used when starting up the database.
Perform the following:
1) Check these environment variables and if required set them appropriately.
2) Review the listener.ora currently used to startup the listener and verify the ORACLE_HOME value is correct for all listed Oracle databases. If the ORACLE_HOME points to a different Oracle version then what was used when the database was created, then this error can occur.
3) Likewise, review the listener.ora currently used to startup the listener and verify the SID_NAME value is correct and has the right value (the SID_NAME is case sensitive).
Also check Metalink Doc ID: 167252.1 (ORA-27101: Shared Memory Realm Does Not Exist).
regards,
Subhajit.

ORA 04030 Out of process memory error

Dear experts,
I know there are multiple discussions around this error and I have been reading through most of them in the past one week or so, but looks like we are running out of options or are missing the color altogether. Ok, we are getting ORA-04030 - out of process memory while allocating....while one of our batch process runs in the night. It simply tries to insert/update to a table. Our installation is 11.2.0.1.0 with no RAC configuration and on 64-bit AIX having 6 cores, 12 CPUs and 16 GB memory.
We have checked the Workarea_Size_Policy is set to be as Auto so Oracle decides how much memory to allocate to PGA automatically on run-time based on the demand. And based on the AWR report it doesnt look like we are anywhere near the country having a PGA-deficit!! I am attaching the AWR report in a word document here for your reference.
Also attached below are the configurations and the ulimit values.
IKBTRN1> show parameter workarea;
NAME TYPE VALUE
workarea_size_policy string AUTO
oraipeikbtrn1:/home/oracle-> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user) unlimited
Now, nothing seems to have contributed to the out of process memory issue from Oracle standpoint. I would be happy to be proved wrong here, if I am wrong.
So, whats going wrong here? A possible memory leak which we cannot zero down to, a OS memory limit or something else?
Seeking expert's advise on this, and also sincerely appreciate your time in looking at this.
Thanks.
P.S - I am pasting the whole AWR report since there is no 'upload file' option here that I can see.
WORKLOAD REPOSITORY report for
DB Name DB Id Instance Inst num Startup Time Release RAC
IKBTRN1 54659199 IKBTRN1 1 06-Jun-11 02:06 11.2.0.1.0 NO
Host Name Platform CPUs Cores Sockets Memory (GB)
oraipeikbtrn1.******.com AIX-Based Systems (64-bit) 12 6 16.00
 Snap Id Snap Time Sessions Cursors/Session
Begin Snap: 5952 26-Aug-11 03:00:48 34 2.0
End Snap: 5953 26-Aug-11 04:00:52 32 1.9
Elapsed: 60.07 (mins)
DB Time: 1.93 (mins)
Report Summary
Cache Sizes
 Begin End
Buffer Cache: 1,056M 704M Std Block Size: 8K
Shared Pool Size: 3,456M 3,456M Log Buffer: 7,184K
Load Profile
Load Profile
 Per Second Per Transaction Per Exec Per Call
DB Time(s): 0.0 2.0 0.02 0.02
DB CPU(s): 0.0 0.5 0.00 0.00
Redo size: 556.1 34,554.8
Logical reads: 151.4 9,407.6
Block changes: 1.9 119.8
Physical reads: 14.2 882.6
Physical writes: 9.5 590.4
User calls: 1.8 112.8
Parses: 1.5 93.7
Hard parses: 0.1 8.9
W/A MB processed: -0.1 -6.9
Logons: 0.0 1.6
Executes: 1.9 115.4
Rollbacks: 0.0 0.0
Transactions: 0.0
Instance Efficiency Percentages (Target 100%)
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 96.63 In-memory Sort %: 99.97
Library Hit %: 95.68 Soft Parse %: 90.49
Execute to Parse %: 18.74 Latch Hit %: 100.00
Parse CPU to Parse Elapsd %: 57.23 % Non-Parse CPU: 86.28
Shared Pool Statistics
 Begin End
Memory Usage %: 85.72 85.76
% SQL with executions>1: 93.91 96.66
% Memory for SQL w/exec>1: 89.07 87.04
Top 5 Timed Foreground Events
Event Waits Time(s) Avg wait (ms) % DB time Wait Class
DB CPU 29 24.66
db file scattered read 3,456 17 5 14.92 User I/O
db file sequential read 4,304 17 4 14.77 User I/O
direct path read temp 764 17 22 14.31 User I/O
direct path write temp 259 5 21 4.70 User I/O
Host CPU (CPUs: 12 Cores: 6 Sockets: )
Load Average Begin Load Average End %User %System %WIO %Idle
1.39 1.37 0.2 0.2 0.2 99.6
Instance CPU
%Total CPU %Busy CPU %DB time waiting for CPU (Resource Manager)
0.1 20.5 0.0
Memory Statistics
 Begin End
Host Mem (MB): 16,384.0 16,384.0
SGA use (MB): 4,704.0 4,352.0
PGA use (MB): 196.1 188.4
% Host Mem used for SGA+PGA: 29.91 27.71
Main Report
• Report Summary
• Wait Events Statistics
• SQL Statistics
• Instance Activity Statistics
• IO Stats
• Buffer Pool Statistics
• Advisory Statistics
• Wait Statistics
• Undo Statistics
• Latch Statistics
• Segment Statistics
• Dictionary Cache Statistics
• Library Cache Statistics
• Memory Statistics
• Streams Statistics
• Resource Limit Statistics
• Shared Server Statistics
• init.ora Parameters
Back to Top
Wait Events Statistics
• Time Model Statistics
• Operating System Statistics
• Operating System Statistics - Detail
• Foreground Wait Class
• Foreground Wait Events
• Background Wait Events
• Wait Event Histogram
• Wait Event Histogram Detail (64 msec to 2 sec)
• Wait Event Histogram Detail (4 sec to 2 min)
• Wait Event Histogram Detail (4 min to 1 hr)
• Service Statistics
• Service Wait Class Stats
Back to Top
Time Model Statistics
• Total time in database user-calls (DB Time): 115.9s
• Statistics including the word "background" measure background process time, and so do not contribute to the DB time statistic
• Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 101.69 87.75
DB CPU 28.58 24.66
parse time elapsed 10.14 8.75
hard parse elapsed time 9.92 8.56
failed parse elapsed time 4.92 4.25
hard parse (sharing criteria) elapsed time 4.27 3.68
connection management call elapsed time 0.42 0.36
PL/SQL compilation elapsed time 0.34 0.30
PL/SQL execution elapsed time 0.18 0.15
sequence load elapsed time 0.00 0.00
repeated bind elapsed time 0.00 0.00
DB time 115.88
background elapsed time 86.01
background cpu time 5.06
Back to Wait Events Statistics
Back to Top
Operating System Statistics
• *TIME statistic values are diffed. All others display actual values. End Value is displayed if different
• ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
Statistic Value End Value
NUM_LCPUS 0
NUM_VCPUS 0
AVG_BUSY_TIME 1,260
AVG_IDLE_TIME 360,705
AVG_IOWAIT_TIME 534
AVG_SYS_TIME 483
AVG_USER_TIME 679
BUSY_TIME 16,405
IDLE_TIME 4,329,811
IOWAIT_TIME 7,284
SYS_TIME 7,092
USER_TIME 9,313
LOAD 1 1
OS_CPU_WAIT_TIME 503,900
PHYSICAL_MEMORY_BYTES 17,179,869,184
NUM_CPUS 12
NUM_CPU_CORES 6
GLOBAL_RECEIVE_SIZE_MAX 1,310,720
GLOBAL_SEND_SIZE_MAX 1,310,720
TCP_RECEIVE_SIZE_DEFAULT 16,384
TCP_RECEIVE_SIZE_MAX 9,223,372,036,854,775,807
TCP_RECEIVE_SIZE_MIN 4,096
TCP_SEND_SIZE_DEFAULT 16,384
TCP_SEND_SIZE_MAX 9,223,372,036,854,775,807
TCP_SEND_SIZE_MIN 4,096
Back to Wait Events Statistics
Back to Top
Operating System Statistics - Detail
Snap Time Load %busy %user %sys %idle %iowait
26-Aug 03:00:48 1.39
26-Aug 04:00:52 1.37 0.38 0.21 0.16 99.62 0.17
Back to Wait Events Statistics
Back to Top
Foreground Wait Class
• s - second, ms - millisecond - 1000th of a second
• ordered by wait time desc, waits desc
• %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
• Captured Time accounts for 78.2% of Total DB time 115.88 (s)
• Total FG Wait Time: 62.08 (s) DB CPU time: 28.58 (s)
Wait Class Waits %Time -outs Total Wait Time (s) Avg wait (ms) %DB time
User I/O 8,949 0 56 6 48.74
DB CPU 29 24.66
System I/O 1,916 0 3 1 2.18
Other 506 88 1 2 0.92
Configuration 2 50 1 500 0.86
Commit 37 0 1 18 0.56
Application 20 0 0 17 0.29
Network 4,792 0 0 0 0.01
Concurrency 1 0 0 0 0.00
Back to Wait Events Statistics
Back to Top
Foreground Wait Events
• s - second, ms - millisecond - 1000th of a second
• Only events with Total Wait Time (s) >= .001 are shown
• ordered by wait time desc, waits desc (idle events last)
• %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn % DB time
db file scattered read 3,456 0 17 5 59.59 14.92
db file sequential read 4,304 0 17 4 74.21 14.77
direct path read temp 764 0 17 22 13.17 14.31
direct path write temp 259 0 5 21 4.47 4.70
control file sequential read 1,916 0 3 1 33.03 2.18
ADR block file read 38 0 1 28 0.66 0.92
log buffer space 2 50 1 500 0.03 0.86
log file sync 37 0 1 18 0.64 0.56
enq: RO - fast object reuse 14 0 0 24 0.24 0.29
local write wait 44 0 0 1 0.76 0.03
SQL*Net message to client 4,772 0 0 0 82.28 0.01
Disk file operations I/O 110 0 0 0 1.90 0.00
ADR block file write 7 0 0 0 0.12 0.00
SQL*Net message from client 4,773 0 15,396 3226 82.29
Streams AQ: waiting for messages in the queue 720 100 3,600 5000 12.41
Back to Wait Events Statistics
Back to Top
Background Wait Events
• ordered by wait time desc, waits desc (idle events last)
• Only events with Total Wait Time (s) >= .001 are shown
• %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn % bg time
control file sequential read 4,950 0 35 7 85.34 40.74
control file parallel write 1,262 0 31 25 21.76 36.46
log file parallel write 383 0 4 10 6.60 4.37
db file parallel write 627 0 2 3 10.81 2.36
change tracking file synchronous read 56 0 2 34 0.97 2.21
os thread startup 17 0 1 88 0.29 1.74
ADR block file read 135 0 1 7 2.33 1.04
change tracking file synchronous write 56 0 1 15 0.97 0.98
SGA: allocation forcing component growth 8 100 1 100 0.14 0.93
db file sequential read 112 0 1 6 1.93 0.75
process diagnostic dump 94 0 0 1 1.62 0.09
ADR block file write 92 0 0 1 1.59 0.07
LGWR wait for redo copy 11 0 0 1 0.19 0.01
log file sync 2 0 0 3 0.03 0.01
ADR file lock 92 22 0 0 1.59 0.01
Parameter File I/O 24 0 0 0 0.41 0.01
direct path write 6 0 0 1 0.10 0.00
Disk file operations I/O 54 0 0 0 0.93 0.00
rdbms ipc message 17,637 97 61,836 3506 304.09
Streams AQ: waiting for time management or cleanup tasks 5 60 11,053 2210602 0.09
DIAG idle wait 7,203 100 7,203 1000 124.19
PX Idle Wait 1,802 100 3,604 2000 31.07
pmon timer 1,212 99 3,603 2973 20.90
Space Manager: slave idle wait 726 99 3,603 4963 12.52
smon timer 12 100 3,600 300004 0.21
Streams AQ: qmn slave idle wait 128 0 3,583 27993 2.21
Streams AQ: qmn coordinator idle wait 256 50 3,583 13996 4.41
SQL*Net message from client 293 0 2 5 5.05
Back to Wait Events Statistics
Back to Top
Wait Event Histogram
• Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
• % of Waits: value of .0 indicates value was <.05%; value of null is truly 0
• % of Waits: column heading of <=1s is truly <1024ms, >1s is truly >=1024ms
• Ordered by Event (idle events last)
 % of Waits
Event Total Waits <1ms <2ms <4ms <8ms <16ms <32ms <=1s >1s
ADR block file read 173 80.3 5.2 2.3 5.8 1.7 4.6
ADR block file write 99 96.0 3.0 1.0
ADR file lock 102 100.0
Disk file operations I/O 165 100.0
LGWR wait for redo copy 11 90.9 9.1
Parameter File I/O 24 100.0
SGA: allocation forcing component growth 8 100.0
SQL*Net break/reset to client 6 100.0
SQL*Net message to client 4992 100.0
SQL*Net more data from client 20 100.0
asynch descriptor resize 541 100.0
change tracking file synchronous read 56 83.9 1.8 14.3
change tracking file synchronous write 56 80.4 7.1 1.8 10.7
control file parallel write 1262 80.3 1.7 .6 .6 .8 1.3 14.7
control file sequential read 6866 94.1 .9 .7 .7 .3 .4 2.9
db file parallel write 628 94.3 2.1 1.0 .8 .3 .3 1.3
db file scattered read 3457 72.6 7.2 5.4 6.9 5.7 .5 1.6
db file sequential read 4525 78.7 2.7 1.8 9.6 5.3 .4 1.5
direct path read temp 764 40.2 18.6 9.4 6.2 11.0 5.8 8.9
direct path sync 1 100.0
direct path write 6 83.3 16.7
direct path write temp 259 .4 1.2 88.8 .4 9.3
enq: RO - fast object reuse 14 42.9 42.9 7.1 7.1
latch free 1 100.0
latch: cache buffers lru chain 2 100.0
latch: checkpoint queue latch 2 100.0
latch: messages 2 100.0
latch: object queue header operation 2 100.0
latch: redo allocation 1 100.0
latch: row cache objects 1 100.0
local write wait 44 100.0
log buffer space 2 50.0 50.0
log file parallel write 383 92.4 .8 1.0 5.7
log file sync 39 82.1 2.6 2.6 12.8
os thread startup 17 100.0
process diagnostic dump 94 34.0 63.8 2.1
reliable message 7 100.0
utl_file I/O 12 100.0
DIAG idle wait 7204 100.0
PX Idle Wait 1802 100.0
SQL*Net message from client 5067 87.1 6.6 1.0 .5 .5 .1 .5 3.7
Space Manager: slave idle wait 726 .6 99.4
Streams AQ: qmn coordinator idle wait 256 49.2 .8 50.0
Streams AQ: qmn slave idle wait 128 100.0
Streams AQ: waiting for messages in the queue 721 100.0
Streams AQ: waiting for time management or cleanup tasks 5 40.0 20.0 40.0
class slave wait 17 100.0
pmon timer 1212 .9 99.1
rdbms ipc message 17.6K 1.8 .4 .2 .2 .1 .1 21.0 76.2
smon timer 12 100.0
Back to Wait Events Statistics
Back to Top
I couldnt add the rest of the report here since it is telling me I have exceeded 30000 characters. If you want to see the full report, please email me at [email protected]

Unless your database is strictly a DSS-type of database, your AWR report exposes loads of issues with it. And I think none of the time during the AWR window was spent on database. Look at the DB time (with all those multi cores) compared with the elapsed time of the AWR.
As you are on 11g, why not make use of MEMORY_TARGET (a single parameter to manage both SGA and PGA)? If you are already on it, ignore this as I can't see it anywhere. If not, get rid of SGA_TARGET and PGA_AGGREGATE_TARGET and replace it with a single MEMORY_TARGET parameter. However you may have a minimum threshold set for different SGA pools so that they won't shrink beyond that point.
Having said that, setting MEMORY_TARGET is not a guarantee to avoid ORA-4030. Just a single bad PL/SQL code could go and exploit the untunable part of your process memory and even go and blow up the physical memory. If you are using FORALL and BULK load, see if you can cut it down into few chunks rather than running as a single process.
What does your V$PGASTAT say?

Memory on AIX

Similar Messages

Maybe you are looking for