Tuning: Memory Abusers

Hello,
I'm working through the book Oracle Database 10g Performance Tuning Tips & Techniques from R. Niemiec. In chapter 15 is the topic - Top 10 "Memory Abusers" as a percent of all Statements - which I do not understand correct.
Maybe someone has this book and can help me on this?
I executed the sql-statement given in this book and it gives me about 66 percent for the top ten statements. The example has 44 percent.
I don't understand the ranking given for the example, for the example the result is 60 points. Why?
I don't know if I'm allowed to paste the rate-part here.
Greets,
Hannibal

I customized the query on 10g a little;
SELECT *
  FROM (SELECT rank() over(ORDER BY buffer_gets DESC) AS rank_bufgets,
               (100 * ratio_to_report(buffer_gets) over()) pct_bufgets,
               sql_text,
               executions,
               disk_reads,
               cpu_time,
               elapsed_time
          FROM v$sqlarea)
WHERE rank_bufgets < 11;In my opinion above query helps to find and prioritize the problematic queries which are run from the last database startup, so the magic number and the conditions are not so important :)
If you are on 10g and have the cost option AWR report of a problematic period or before 10g STATSPACK report will assist you for this purpose. Also after 10gR2 v$sqlstats is very useful, search and check them according to your version here; http://tahiti.oracle.com

Similar Messages

  • How tuning memory in Logical database 10.2.0.2 in Unix server?

    Hi
    I need your help.
    I have a logical database ver, 10.2.0.2, in a unix itanium with 16G in Ram.
    Recently my database has issues because is not refresing the data that comes from the primary DB.
    I have to flush the SGA memory and shutdown the database.
    Also I decrese the max_servers from 27 to 18 and still fails.
    My sga memory is 9G
    How can I tuning the size of the SGA, shared pool etc for a better performance?
    Or what else I need to review in order to have a better performance?
    Thanks in advance for the help.
    Lorein

    Hello
    That's the issue I don't receive any error just take long time to apply the archive files from the primary database.
    This is a part of the alert file. Yesterday the file arch112366_1_652812906.arc start to be applied but for 5 hours didn't finish, but I didn't receive any error. The logical continued receiving the arch fiels from the primary but never finish loading this file. What I did was flush the SGA and shutdown the database , and decrease the max_servers. Then the database starts applying the files.
    LOGMINER: End mining logfile: /oracle/pexp/arch/sarchive/arch112365_1_652812906.arc
    Wed Feb 3 12:32:36 2010
    RFS[2]: No standby redo logfiles created
    RFS[2]: Archived Log: '/oracle/pexp/arch/sarchive/arch112366_1_652812906.arc'
    Wed Feb 3 12:32:38 2010
    RFS LogMiner: Registered logfile [oracle/pexp/arch/sarchive/arch112366_1_652812906.arc] to LogMiner session id [1]
    Wed Feb 3 12:32:38 2010
    LOGMINER: Begin mining logfile: /oracle/pexp/arch/sarchive/arch112366_1_652812906.arc
    Wed Feb 3 12:32:40 2010
    LSP0: rolling back apply server 4
    LSP0: apply server 4 rolled back
    Wed Feb 3 12:32:45 2010
    Thread 1 advanced to log sequence 1026
    Current log# 1 seq# 1026 mem# 0: /oradata/pexp/redoA/redo01.log
    Current log# 1 seq# 1026 mem# 1: /oradata/pexp/mirrorredoA/redo01b.log
    Wed Feb 3 12:32:46 2010
    LOGMINER: Log Auto Delete - deleting: /oracle/pexp/arch/sarchive/arch112352_1_652812906.arc
    Deleted file /oracle/pexp/arch/sarchive/arch112352_1_652812906.arc
    Wed Feb 3 12:32:46 2010
    LOGMINER: Log Auto Delete - deleting: /oracle/pexp/arch/sarchive/arch112353_1_652812906.arc
    Deleted file /oracle/pexp/arch/sarchive/arch112353_1_652812906.arc
    Wed Feb 3 12:32:46 2010
    Regards

  • Performance Tuning Memory

    I have an application where I expect to be pushing the bounds of the process memory limit on windows. I have done a lot of optimization to make sure that I am using as little memory as possible. I expect it to be around 650M given my current data set.
    When I run the application, I have to bump the heap up to almost twice that size so that I don't run out of memory. I believe that the virtual machine is allocating memory for the different generations in order to prepare to garbage collect all of these objects. The objects will never need to be garbage collected though because they will live for the life of the app. I've looked through the garbage colletion FAQs and documents and none of the VM parameters have enabled me to bring the size of the app down to the size I expect it to be.
    Any ideas?
    My last resort is to write it in C++ do I have complete control but I would much rather have this written in Java.
    Michael Connor

    Hi,
    don't have an answer to your problem, but a tip: Go and look for "jvmstat" - a gc and memory visualisation tool. It will help you to find out what's going on in your vm
    Then you can try to tweak your jvm with all those pretty -XX options,
    Documentation starting point: http://java.sun.com/docs/performance/
    Peter

  • Tuning Memory Structures

    Guys,
    My application runs on oracle Database, in order to improve the performance by reducing I/0 we haev spread
    the datafiles and redolog files across 4 different drives.
    Now when I try to tune application based on increasing the SGA, buffer cache (to improve buffer cache size hit
    ratio), shared pool does it use up the space on the default drive where it is installed which is C drive
    For example Oracle is installed on C
    I want to increase the SGA size from 600MB to 1GB so does it use the space on the C drive to incorporate the change
    Thanks

    SGA does not map to a file on a harddisk, but is allocated in the memory (should be RAM) of you your computer. It may indirectly you diskspace, if you don't have enough physical memory and paging happens. It makes no sense to increase your SGA, if it does not fit into pyhsical memory.

  • Db memory Vs abap memory

    I wanted to know in the Central Instance (crm/ BI/solman) how much memory should be allocated to the database and how much to ABAP.
    I remember from one of the class it is 30% to the database and 70% to abap. .. but I could not find this in any manual/link/note.
    Does any one send me a reference with this information.
    thank you and happy holidays.
    regards
    Laxmi

    This is just one "rule of thumb", not a general recommendation.
    Each system is different, has a different workload, different number of users, different requirements, that's why there is no official note.
    I would start with 50/50 and let the system run for a few days, then check ST02 for the maximum amount of memory for the SAP application needed and adapt the parameters according. Tuning memory is an iterative process.
    Just keep in mind that your system speed almost solely relies on the size of the database cache. Less I/O --> less time to wait --> more speed. So I would give the database as much memory as possible by not impacting the application and avoding the OS to start swapping/paging.
    Markus

  • QUESTION: Multi-instance memory requirements on Linux

    Hi, all.
    I've been out of the loop on Oracle technical details for awhile, and need to re-educate myself on a few things. I'm hoping someone can point me to a book in the online docs which discusses my question.
    Oracle db 10.2.0.2, on Redhat Linux 2.6.9-67.0.0.0.1. This server is a virtual machine, on a VMWare ESX server.
    My question concerns the utilization of memory resources in a multi-instance environment.
    I currently have 2 instances/dbs on this server. Each was configured with an SGA_TARGET of approximately 900MB. java_pool_size, large_pool_size and shared_pool_size are also assigned values in the pfile, which I believe supersedes SGA_TARGET.
    I am tasked with determining if the server can handle a third instance. It's unclear how much load the database will see, so I don't yet know how much memory I will want to allocate to the shared pool for the buffer cache, etc.
    I wanted to see how much memory was being used by the existing instances, so on the server I attempted to capture memory usage information both before, and after, the startup of the second instance.
    I used 'top' for this, and found that the server has a total of 3.12GB of physical memory. Currently there's about 100MB free physical memory.
    the information from 'top' also indicated that physical memory utilization had actually decreased after I started the second instance:
    Before second instance was started:
    Mem: 3115208k total, 3012172k used, 103036k free, 46664k buffers
    Swap: 2031608k total, 77328k used, 1954280k free, 2391148k cached
    After second instance was started:
    Mem: 3115208k total, 2989244k used, 125964k free, 47144k buffers
    Swap: 2031608k total, 89696k used, 1941912k free, 2320184k cached
    Logging into the instance, I ran a 'show SGA', and got an SGA size of about 900MB (as expected). But before I started the instance, there wasn't anywhere near than amount of physical memory available.
    The question I need to answer is whether this server can accomodate a third instance. I gather that the actual amount of memory listed in SGA_TARGET won't be allocated until needed, and I also understand that virtual memory will be used if needed.
    So rather than just asking for 'the answer', I'm hoping someone can point me to a resource which will help me better understand *NIX memory usage behavior in a multi-instance environment...
    Thanks!!
    DW

    Each was configured with an SGA_TARGET of approximately 900MB. java_pool_size, large_pool_size and shared_pool_size are also assigned values in the pfile, which I believe supersedes SGA_TARGET.
    Not quite. If you set non-zero values for those parameters as well as setting SGA_TARGET, then they act as minimum values that have to be maintained before extra free memory is distributed automatically amongst all auto-tuned memory pools. If you've set them as well as SGA_TARGET, you've possibly got a mish-mash of memory settings that aren't doing what you expected. If it was me, I'd stick either to the old settings, or to the new, and try not to mix them (unless your application is very strange and causes the auto-allocate mechanism to apportion memory in ways you know are wrong, in which case setting a floor below which memory allocations cannot go might be useful).
    3GB of physical memory is not much these days. The general rule is that your total SGAs should not make up more than about 50% of physical memory, because you probably need most of the other 50% for PGA use. But if your users aren't going to be doing strenuous sorting (for example), then you can shrink the PGA requirement and nudge the SGA allowance up in its place.
    At 900MB per SGA, you can have two SGAs and not much user activity. That's 1800MB SGA plus, say, 200MB each PGA = 2200MB, leaving about 800MB for contingencies and Linux itself. That's quite tight and I personally wouldn't try to squeeze another instance of the same size into that, not if you want performance to be meaningful.
    Your top figures seem to me to suggest you're paging physical memory out to RAM already, which can't be good!

  • 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

  • SGA_TARGET question

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

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

  • BW System crashed due to DB6_ADM_RUNSTATS, error -911, -1032, --1224

    Hi Friends,
    we are using AIX 5.2 with DB2 8.1 on BW 3.5/640 system.
    The below warning is also coming very frequently which is causing system crash sometimes:
    1.Function DB6_ADM_RUNSTATS failed for List of Tables . Reason: ADBC
    2. Error and Database error -911 at EXE
    3. BTC 029 061 SEMABL BYL Database error -1032
    4. DIA 003 061 SEJABE BYM SQL error -1224 occurred;
    work process in reconnect status
    18:58:59 DP Q04 Connection to user
    14871 (ITGARO ), terminal 125 (nbw20810 ) lost
    19:04:06 BTC 029 061 SEMABL BYL Database error -1032
    requires intervention from database administrator
    19:04:06 BTC 029 061 SEMABL BY4 Database error -1032 at PRE
    access to table SWT_LOGCAT
    19:04:06 BTC 029 061 SEMABL BY0 > SQL1032N No start database
    manager command was issued.
    19:04:06 DIA 012 061 USEDBA BY2 Database error -1032 at CON
    19:04:06 DIA 017 061 DEKASO BY2 Database error -1032 at CON
    19:04:06 DIA 014 R19 Initialization DB-
    Connect Failed, Return Code 000256
    19:04:06 DIA 019 061 CHPAPR BYL Database error -1032
    requires intervention from database administrator
    19:04:46 DIA 003 061 SEJABE BYM SQL error -1224 occurred;
    work process in reconnect status
    19:04:46 DIA 012 061 USEDBA BYM SQL error -1224 occurred;
    work process in reconnect status
    19:04:46 DIA 005 061 DKKILA BYM SQL error -1224 occurred;
    work process in reconnect status
    19:04:46 DIA 015 061 NLBAGR BYM SQL error -1224 occurred;
    work process in reconnect status
    19:04:46 BTC 030 000 SESYSTADMJOB BY2 Database error -1224 at OPC
    19:04:46 BTC 030 000 SESYSTADMJOB BY0 > SQL1224N The database
    manager is not able to accept new
    19:04:46 BTC 030 000 SESYSTADMJOB BY0 > requests, has terminated
    all requests in progress, or has
    19:04:46 BTC 030 000 SESYSTADMJOB BY0 > terminated your particular
    request due to a problem with you
    19:04:46 BTC 030 000 SESYSTADMJOB BY0 > request. SQLSTATE=55032
    19:04:46 DIA 017 061 DEKASO BYM SQL error -1224 occurred;
    work process in reconnect status
    19:04:46 DIA 017 061 DEKASO R38 Error at DB commit, return
    code 001024
    any idea what can be done to resolve this issue.
    Thanks and regards
    Regards - Munish

    tail -310 db2diag.log
              /db2/BWP/log_dir/NODE0000/.
    2010-01-14-10.32.03.583933+060 I15733311A444      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sheapthres_shr" From: "73056" <automatic>  To: "81793" <automatic>
    2010-01-14-10.32.03.593671+060 I15733756A436      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sortheap" From: "3653" <automatic>  To: "4089" <automatic>
    2010-01-14-10.42.55.641172+060 I15734193A271      LEVEL: Warning
    PID     : 3633166              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.42.55.753060+060 I15734465A271      LEVEL: Warning
    PID     : 3633168              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.42.56.076470+060 I15734737A271      LEVEL: Warning
    PID     : 3633170              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.42.57.940361+060 I15735009A271      LEVEL: Warning
    PID     : 3633172              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.42.57.984990+060 I15735281A271      LEVEL: Warning
    PID     : 3633172              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.42.58.227268+060 I15735553A271      LEVEL: Warning
    PID     : 3633174              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.51.33.683730+060 I15735825A462      LEVEL: Info
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "BP_STD_16K" From: "1348672" <automatic> To:
              "1356492" <automatic>
    2010-01-14-10.53.03.721301+060 I15736288A567      LEVEL: Warning
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmUpdateDBConfig, probe:285
    MESSAGE : ZRC=0x82AE00A6=-2102525786=STMM_DYNAMIC_UPDATE_FAILED
              "STMM dynamic update failed"
    DATA #1 : String, 76 bytes
    Dynamic update failed for parameter Locklist. Attempted update value is 5472
    2010-01-14-10.53.03.722593+060 I15736856A444      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sheapthres_shr" From: "81793" <automatic>  To: "78415" <automatic>
    2010-01-14-10.53.04.168179+060 I15737301A458      LEVEL: Info
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterBufferPoolAct, probe:90
    MESSAGE : Altering bufferpool "IBMDEFAULTBP" From: "6524" <automatic> To:
              "5244" <automatic>
    2010-01-14-10.53.04.182145+060 I15737760A436      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sortheap" From: "4089" <automatic>  To: "3920" <automatic>
    2010-01-14-10.57.13.883762+060 I15738197A271      LEVEL: Warning
    PID     : 3522744              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.14.048828+060 I15738469A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.14.216675+060 I15738741A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.14.285737+060 I15739013A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.14.917712+060 I15739285A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.14.980479+060 I15739557A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.15.254151+060 I15739829A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.15.308542+060 I15740101A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.15.586406+060 I15740373A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.15.650049+060 I15740645A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.15.934485+060 I15740917A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.16.023114+060 I15741189A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.16.289905+060 I15741461A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.16.345930+060 I15741733A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.16.627395+060 I15742005A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.16.701147+060 I15742277A271      LEVEL: Warning
    PID     : 3522746              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    2010-01-14-10.57.31.076427+060 I15742549A379      LEVEL: Severe
    PID     : 786644               TID  : 1           PROC : db2sysc 0
    INSTANCE: db2bwp               NODE : 000
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:910
    MESSAGE : marking fmp as unstable:
    DATA #1 : Hexdump, 4 bytes
    0x078000000041EF40 : 0036 3064                                  .60d
    2010-01-14-10.57.31.076634+060 I15742929A2815     LEVEL: Severe
    PID     : 786644               TID  : 1           PROC : db2sysc 0
    INSTANCE: db2bwp               NODE : 000
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerReturnFmpToPool, probe:911
    MESSAGE : marking fmp as unstable:
    DATA #1 : Hexdump, 488 bytes
    0x078000000041EF40 : 0036 3064 0000 0000 018A 0000 0000 0000    .60d............
    0x078000000041EF50 : 018B 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EF60 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EF70 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EF80 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EF90 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFA0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFB0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFC0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFD0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFE0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041EFF0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F000 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F010 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F020 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F030 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F040 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F050 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F060 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F070 : 0000 0000 0000 0000 0000 0001 111F 7720    ..............w
    0x078000000041F080 : 0780 0000 1007 0094 0780 0000 1008 0094    ................
    0x078000000041F090 : 0001 0000 0000 0000 0000 0000 0000 029A    ................
    0x078000000041F0A0 : 0000 00A3 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F0B0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F0C0 : 0780 0000 0023 AB20 0780 0000 0041 EF40    .....#. .....A.@
    0x078000000041F0D0 : 0780 0000 002C FF00 0000 0001 0000 0001    .....,..........
    0x078000000041F0E0 : 0000 0000 0000 0000 0000 0001 0000 0000    ................
    0x078000000041F0F0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x078000000041F100 : 0780 0000 001A FB60 0000 0000 0000 0000    .......`........
    0x078000000041F110 : 0000 0150 0000 0000 0000 0000 0000 0001    ...P............
    0x078000000041F120 : 0100 0000 0000 0000                        ........
    2010-01-14-10.57.31.076872+060 I15745745A426      LEVEL: Warning
    PID     : 548998               TID  : 1           PROC : db2agent (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-28                 APPID: *LOCAL.db2bwp.100111182348
    AUTHID  : SAPBWP 
    MESSAGE : Removing FMP from pool
    DATA #1 : Hexdump, 16 bytes
    0x0FFFFFFFFFFF0748 : 0780 0000 0041 EF58 0036 3064 0000 0000    .....A.X.60d....
    2010-01-14-10.57.34.238172+060 I15746172A444      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sheapthres_shr" From: "78415" <automatic>  To: "73992" <automatic>
    2010-01-14-10.57.34.241586+060 I15746617A436      LEVEL: Event
    PID     : 798956               TID  : 1           PROC : db2stmm (BWP) 0
    INSTANCE: db2bwp               NODE : 000         DB   : BWP
    APPHDL  : 0-52                 APPID: *LOCAL.db2bwp.100111182342
    AUTHID  : SAPBWP 
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : STMM CFG DB BWP: "Sortheap" From: "3920" <automatic>  To: "3699" <automatic>
    2010-01-14-10.57.40.592365+060 I15747054A271      LEVEL: Warning
    PID     : 3522628              TID : 1
    FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
    DATA #1 : String, 65 bytes
    Password validation for user bwpadm failed with rc = -2146500507
    ];bwpadm@nbcsaprtv016:/db2/BWP/db2dump

  • SGA_TARGET

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

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

  • J2EE Startup Issue - XI

    Hi,
    System hang occured while configuring JCO RFC Provider AI_RUNTIME_XI in Visual Admin. I had just completed the SP12 Application on NW04S Usage Type PI. I had also tried uninstalling the J2EE Schema and then installing back and redeploying SP11 instead but with same results as system hung while setting up JCO RFC destination in SP12. As i restart the cluster i get the following error in 'Starting Application' state. I have done the clean shut down , ipc cleanup still the issue persists. The Application was working fine before i configured AI_RUNTIME_XI, not sure whats causing this or is this a resource/memory contention.
    Also i have done the SP12 patches on other XI boxes without having to change the memory/heap parameter values.
    Below is the server.0.log.
    #1.5#000F202B62B500000000001700002E930004340883490E63#1183111073822#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###13
    services have timed out.#
    #1.5#000F202B62B500000000001900002E93000434088349100E#1183111073823#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000001B00002E9300043408834911AA#1183111073823#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000001D00002E930004340883491337#1183111073823#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.af.security.service has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000001F00002E9300043408834914D0#1183111073824#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.jms.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000002100002E93000434088349165C#1183111073824#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000002300002E9300043408834917E8#1183111073825#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.af.ispeak.svc has timed out > hard reference to service com.sap.aii.af.ms.svc.#
    #1.5#000F202B62B500000000002500002E930004340883491983#1183111073825#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000002700002E930004340883491B11#1183111073825#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
    #1.5#000F202B62B500000000002900002E930004340883491CAC#1183111073826#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
    #1.5#000F202B62B500000000002B00002E930004340883491E36#1183111073826#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.af.cpa.svc has timed out > service com.sap.aii.af.cpa.svc start method invoked.#
    #1.5#000F202B62B500000000002D00002E930004340883491FEC#1183111073827#/System/Server##com.sap.engine.core.service630.container.M
    emoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Ser
    vice com.sap.aii.adapter.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#

    Vinith,
    Issue got resolved through fine tuning Memory /Heap parameters and increasing no of dbpool connections. Though your note was a goot pointer and i am rewarding points for that.
    Thanks
    Rahul

  • PC intermittently gives blue screen crash under Firefox v9 but OK under V3

    Using V9 I encountered unpredictable BSOD events with message "A problem has been detected & windows has been shut down to prevent damage to your computer. etc (recommended checks)"
    No BIOS tuning; Memory integrity OK; no disk errors; no malware problems; no other software updates. Using XP Pro.
    Problem disappeared on reverting to Firefox V3.6.15;
    However now have lost FireFTP compatable with V3.6.15.
    One other observation may be relevant - upgrade to V3.6.25 failed to restart (The update could not be installed. Please make sure there are no other copies of Firefox running on your computer, and then restart Firefox to try again.) Task manager showed that no copies were running so couldn'y install update to V3.6.25. Upgrades have previously been OK.

    You may likely have the issue with Firefox 4.0, 5.0, 6.0, 7.0 and 8.0 also.
    Again Firefox does not cause BSOD but something is getting triggered whether it is a antivirus, software firewall, graphics driver or even a hardware issue like putting just the right load on power supply to trigger a power cut or such (been a long while since I have seen that being the cause for a Fx user though).
    Firefox can run completely off a usb flash drive for example.

  • Unexpected minimum value for SHEAPTHRES_SHR

    Hi Folks - We keep getting the following message every 30 seconds on our BI QA server.
    2009-08-24-07.26.17.263989-240 E78429A607         LEVEL: Warning
    PID     : 930014               TID  : 15425       PROC : db2sysc 0
    INSTANCE: db2bq1               NODE : 000         DB   : BQ1
    APPHDL  : 0-28423              APPID: *LOCAL.DB2.090808073504
    AUTHID  : DB2BQ1
    EDUID   : 15425                EDUNAME: db2stmm (BQ1) 0
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmComputeMinSHEAPTHRES, probe:836
    MESSAGE : Unexpected minimum value for SHEAPTHRES_SHR - value automatically
              corrected -  122423 -  2448 -  338887 -  9180 -  3 -  0 -  3.000000 -
               1 -  31 -  271110 -  630
    I am pretty sure this will have performance impact on the database as the database manager has to keep changing the SHEAPTHRES_SHR value every 30 seconds back to the correct value. Has any one seen this before? Turning off STMM is not an option. We do not want to hard code SHEAPTHRES_SHR value as the loads on BI are not-predictable in the environment.
    Pl advise.
    Thanks.

    The output of the SQL statement shows:
    MAX_PARTITION_MEM: Maximum allowed "instance_memory" (this will correspond with the current setting of instance_memory in bytes)
    CURRENT_PARTITION_MEM: Current total memory allocation (in bytes)
    PEAK_PARTITION_MEM: HWM total memory allocation (in bytes)
    The bug with the STMM memory calculation was first fixed with version 9.5 FP4 so you might have to upgrade your instances to FP4. In fact, if I am not mistaken, SAP withdrew FP3 due to a hiper apar which can potentially impact SAP systems.
    Also as far as the values in the output of the query and db2pd are concerned, they are not different. The output of the query is expressed in bytes whereas the output of pd is expressed in KB.
    $$ db2pd -dbptnmem
    Memory Limit:         36000000 KB (which is 36864000000 bytes)
    Current usage:        31746944 KB (which is 32508870656 bytes)
    HWM usage:            35704320 KB (which is 36561223680 bytes)
    Regards,
    Sameer

  • Directory log_dir full

    hello,
    The directory "log_dir" is full at 97%.
    We have in this directory redologs from January 2010.
    We have a backup every day successfully
    OS Linux Suse10
    DB6 09.01.0007
    My question is: How can I empty log_dir directory ??
    I suppose I cannot use the "rm" command
    Can you help me to solve this problem ?
    thanks a lot in advance
    Daniel

    Hello Bhavik,
    Log retain for recovery enabled             (LOGRETAIN) = OFF
    User exit for logging enabled                (USEREXIT) = OFF
    All config of my DB
    SETNICSAPAP1:db2ap1 58> db2 get db cfg for AP1
           Database Configuration for Database AP1
    Database configuration release level                    = 0x0b00
    Database release level                                  = 0x0b00
    Database territory                                      = en_US
    Database code page                                      = 1208
    Database code set                                       = UTF-8
    Database country/region code                            = 1
    Database collating sequence                             = IDENTITY_16BIT
    Alternate collating sequence              (ALT_COLLATE) =
    Database page size                                      = 16384
    Dynamic SQL Query management           (DYN_QUERY_MGMT) = DISABLE
    Discovery support for this database       (DISCOVER_DB) = ENABLE
    Restrict access                                         = NO
    Default query optimization class         (DFT_QUERYOPT) = 5
    Degree of parallelism                      (DFT_DEGREE) = 1
    Continue upon arithmetic exceptions   (DFT_SQLMATHWARN) = NO
    Default refresh age                   (DFT_REFRESH_AGE) = 0
    Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
    Number of frequent values retained     (NUM_FREQVALUES) = 10
    Number of quantiles retained            (NUM_QUANTILES) = 20
    Backup pending                                          = NO
    Database is consistent                                  = NO
    Rollforward pending                                     = NO
    Restore pending                                         = NO
    Multi-page file allocation enabled                      = YES
    Log retain for recovery status                          = NO
    User exit for logging status                            = YES
    Self tuning memory                    (SELF_TUNING_MEM) = ON
    Size of database shared memory (4KB)  (DATABASE_MEMORY) = 1369600
    Database memory threshold               (DB_MEM_THRESH) = 10
    Max storage for lock list (4KB)              (LOCKLIST) = AUTOMATIC
    Percent. of lock lists per application       (MAXLOCKS) = AUTOMATIC
    Package cache size (4KB)                   (PCKCACHESZ) = AUTOMATIC
    Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = AUTOMATIC
    Sort list heap (4KB)                         (SORTHEAP) = AUTOMATIC
    Database heap (4KB)                            (DBHEAP) = 25000
    Catalog cache size (4KB)              (CATALOGCACHE_SZ) = 2560
    Log buffer size (4KB)                        (LOGBUFSZ) = 1024
    Utilities heap size (4KB)                (UTIL_HEAP_SZ) = 10000
    Buffer pool size (pages)                     (BUFFPAGE) = 10000
    Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 128000
    Percent of mem for appl. group heap   (GROUPHEAP_RATIO) = 25
    Max appl. control heap size (4KB)     (APP_CTL_HEAP_SZ) = 1600
    SQL statement heap (4KB)                     (STMTHEAP) = 5120
    Default application heap (4KB)             (APPLHEAPSZ) = 4096
    Statistics heap size (4KB)               (STAT_HEAP_SZ) = 15000
    Interval for checking deadlock (ms)         (DLCHKTIME) = 10000
    Lock timeout (sec)                        (LOCKTIMEOUT) = 3600
    Changed pages threshold                (CHNGPGS_THRESH) = 40
    Number of asynchronous page cleaners   (NUM_IOCLEANERS) = AUTOMATIC
    Number of I/O servers                   (NUM_IOSERVERS) = AUTOMATIC
    Index sort flag                             (INDEXSORT) = YES
    Sequential detect flag                      (SEQDETECT) = YES
    Default prefetch size (pages)         (DFT_PREFETCH_SZ) = 32
    Track modified pages                         (TRACKMOD) = ON
    Default number of containers                            = 1
    Default tablespace extentsize (pages)   (DFT_EXTENT_SZ) = 2
    Max number of active applications            (MAXAPPLS) = AUTOMATIC
    Average number of active applications       (AVG_APPLS) = AUTOMATIC
    Max DB files open per application            (MAXFILOP) = 1950
    Log file size (4KB)                         (LOGFILSIZ) = 16380
    Number of primary log files                (LOGPRIMARY) = 20
    Number of secondary log files               (LOGSECOND) = 100
    Changed path to log files                  (NEWLOGPATH) =
    Path to log files                                       = /db2/AP1/log_dir/NODE0000/
    Overflow log path                     (OVERFLOWLOGPATH) =
    Mirror log path                         (MIRRORLOGPATH) =
    First active log file                                   = S0006408.LOG
    Block log on disk full                (BLK_LOG_DSK_FUL) = YES
    Percent max primary log space by transaction  (MAX_LOG) = 0
    Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
    Group commit count                          (MINCOMMIT) = 1
    Percent log file reclaimed before soft chckpt (SOFTMAX) = 300
    Log retain for recovery enabled             (LOGRETAIN) = OFF
    User exit for logging enabled                (USEREXIT) = OFF
    HADR database role                                      = STANDARD
    HADR local host name                  (HADR_LOCAL_HOST) =
    HADR local service name                (HADR_LOCAL_SVC) =
    HADR remote host name                (HADR_REMOTE_HOST) =
    HADR remote service name              (HADR_REMOTE_SVC) =
    HADR instance name of remote server  (HADR_REMOTE_INST) =
    HADR timeout value                       (HADR_TIMEOUT) = 120
    HADR log write synchronization mode     (HADR_SYNCMODE) = NEARSYNC
    First log archive method                 (LOGARCHMETH1) = DISK:/backup/PROD/log_archive/
    Options for logarchmeth1                  (LOGARCHOPT1) =
    Second log archive method                (LOGARCHMETH2) = OFF
    Options for logarchmeth2                  (LOGARCHOPT2) =
    Failover log archive path                (FAILARCHPATH) =
    Number of log archive retries on error   (NUMARCHRETRY) = 5
    Log archive retry Delay (secs)         (ARCHRETRYDELAY) = 20
    Vendor options                              (VENDOROPT) =
    Auto restart enabled                      (AUTORESTART) = ON
    Index re-creation time and redo index build  (INDEXREC) = SYSTEM (RESTART)
    Log pages during index build            (LOGINDEXBUILD) = OFF
    Default number of loadrec sessions    (DFT_LOADREC_SES) = 1
    Number of database backups to retain   (NUM_DB_BACKUPS) = 12
    Recovery history retention (days)     (REC_HIS_RETENTN) = 60
    TSM management class                    (TSM_MGMTCLASS) =
    TSM node name                            (TSM_NODENAME) =
    TSM owner                                   (TSM_OWNER) =
    TSM password                             (TSM_PASSWORD) =
    Automatic maintenance                      (AUTO_MAINT) = ON
       Automatic database backup            (AUTO_DB_BACKUP) = OFF
       Automatic table maintenance          (AUTO_TBL_MAINT) = ON
         Automatic runstats                  (AUTO_RUNSTATS) = ON
         Automatic statistics profiling    (AUTO_STATS_PROF) = OFF
           Automatic profile updates         (AUTO_PROF_UPD) = OFF
         Automatic reorganization               (AUTO_REORG) = OFF
    SETNICSAPAP1:db2ap1 59>

  • Error in DB rollback/SyFlush, return code  000256

    Hi friends
    I have a problem with new instalaction over windows 2008 R2 and database DB6, the system sometimes is hang with error " Error in DB rollback/SyFlush, return code  000256", when check me the service of DB2 is down.
    Thanks in advance.
    Jose

    Hi, it is db2diag.log, this error down service of DB2.
    2011-11-24-15.00.06.217000-270 I6859178F336       LEVEL: Event
    PID     : 7384                 TID  : 7056        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7056                 EDUNAME: db2pdbe 0
    FUNCTION: DB2 UDB, RAS/PD component, pdDumpTempTableStats, probe:3531
    START   : db2pd -temptable started
    2011-11-24-15.00.06.233000-270 I6859516F337       LEVEL: Event
    PID     : 7384                 TID  : 7056        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7056                 EDUNAME: db2pdbe 0
    FUNCTION: DB2 UDB, RAS/PD component, pdDumpTempTableStats, probe:3661
    START   : db2pd -temptable finished
    2011-11-24-15.02.02.282000-270 E6859855F563       LEVEL: Error
    PID     : 7280                 TID  : 1704        PROC : db2fmp64.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1704
    FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsTask::executeTask, probe:600
    MESSAGE : ZRC=0xFFFFFB38=-1224
    DATA #1 : <preformatted>
    [IBM][CLI Driver] SQL1224N  The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt.  SQLSTATE=55032
    2011-11-24-15.02.02.313000-270 E6860420F414       LEVEL: Error
    PID     : 7280                 TID  : 1704        PROC : db2fmp64.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1704
    FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsConnection::setApplName, probe:100
    MESSAGE : ZRC=0xFFFE7961=-99999
    DATA #1 : <preformatted>
    [IBM][CLI Driver] CLI0108E  Communication link failure. SQLSTATE=40003
    2011-11-24-15.02.02.313000-270 E6860836F412       LEVEL: Error
    PID     : 7280                 TID  : 1704        PROC : db2fmp64.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1704
    FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsConnection::rollback, probe:900
    MESSAGE : ECF=0x82BA00E2=-2101739294
    DATA #1 : String, 64 bytes
    [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
    2011-11-24-15.02.02.313000-270 I6861250F340       LEVEL: Error
    PID     : 7280                 TID  : 1704        PROC : db2fmp64.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1704
    FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsTask::run, probe:1200
    MESSAGE : ECF=0x82BA00E4=-2101739292
    DATA #1 : Codepath, 8 bytes
    4
    2011-11-24-15.05.10.669000-270 E6861592F888       LEVEL: Warning
    PID     : 7148                 TID  : 7624        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7624
    FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
    MESSAGE : ADM12007E  There are "13" day(s) left in the evaluation period for
              the product "DB2 Enterprise Server Edition". For evaluation license
              terms and conditions, refer to the IBM License Acceptance and License
              Information document located in the license directory in the
              installation path of this product. If you have licensed this product,
              ensure the license key is properly registered. You can register the
              license via the License Center or db2licm command line utility. The
              license file can be obtained from your licensed product CD.
    2011-11-24-15.05.10.700000-270 I6862482F857       LEVEL: Warning
    PID     : 7148                 TID  : 7624        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7624
    FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
    MESSAGE : SQL8007W  There are "13" day(s) left in the evaluation period for the
              product "DB2 Enterprise Server Edition". For evaluation license terms
              and conditions, refer to the License Agreement document located in
              the license directory in the installation path of this product. If
              you have licensed this product, ensure the license key is properly
              registered. You can register the license via the License Center or
              db2licm command line utility. The license key can be obtained from
              your licensed product CD.
    2011-11-24-15.05.11.246000-270 I6863341F544       LEVEL: Event
    PID     : 7148                 TID  : 1920        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1920                 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, fast comm manager, sqkfBufferManager::initBufferManager, probe:10
    START   : Starting FCM Buffer Manager
    1 resource group(s).
    128 buffers allocated.
    Maximum number of buffers supported is 8192.
    Total buffer manager memory required for 1 logical and 0 fail-over partition(s) is 925712 bytes.
    2011-11-24-15.05.11.262000-270 I6863887F551       LEVEL: Event
    PID     : 7148                 TID  : 1920        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1920                 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, fast comm manager, sqkfChannelManager::initChannelManager, probe:10
    START   : Starting FCM Channel Manager
    1 resource group(s).
    128 channels allocated.
    Maximum number of channels supported is 8192.
    Total channel manager memory required for 1 logical and 0 fail-over partitions(s) is 507928 bytes.
    2011-11-24-15.05.11.262000-270 I6864440F550       LEVEL: Event
    PID     : 7148                 TID  : 1920        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1920                 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, fast comm manager, sqkfSessionManager::initSessionManager, probe:10
    START   : Starting FCM Session Manager
    1 resource group(s).
    128 sessions allocated.
    Maximum number of sessions supported is 64000.
    Total session manager memory required for 1 logical and 0 fail-over partitions is 1683456 bytes.
    2011-11-24-15.05.11.262000-270 I6864992F428       LEVEL: Event
    PID     : 7148                 TID  : 1920        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1920                 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500
    START   : FCM infrastructure started
    FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv4
    2011-11-24-15.05.11.355000-270 E6865422F450       LEVEL: Warning
    PID     : 7148                 TID  : 1920        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 1920                 EDUNAME: db2sysc 0
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpTable, probe:30
    DATA #1 : String, 16 bytes
    agentCachingFmp:
    DATA #2 : String, 3 bytes
    OFF
    DATA #3 : String, 5 bytes
    Flag:
    DATA #4 : Boolean, 1 bytes
    false
    2011-11-24-15.05.12.447000-270 E6865874F328       LEVEL: Event
    PID     : 7148                 TID  : 7624        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7624
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W  Database manager has started.
    START   : DB2 DBM
    2011-11-24-15.05.23.632000-270 I6866204F327       LEVEL: Event
    PID     : 6324                 TID  : 7032        PROC : db2start.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7032
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
    DATA #1 : <preformatted>
    Single node instance [0] is starting
    2011-11-24-15.05.23.664000-270 I6866533F1686      LEVEL: Event
    PID     : 6324                 TID  : 7032        PROC : db2start.exe
    INSTANCE: DB2CAL               NODE : 000
    EDUID   : 7032
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
    DATA #1 : String, 44 bytes
    D:\db2\db2cal\db2_software
    bin\DB2STAR2.EXE
    DATA #2 : Hexdump, 256 bytes
    0x00000000001271E0 : 443A 5C64 6232 5C64 6232 6361 6C5C 6462    D:\db2\db2cal\db
    0x00000000001271F0 : 325F 736F 6674 7761 7265 5C5C 6269 6E5C    2_software
    bin\
    0x0000000000127200 : 4442 3253 5441 5232 2E45 5845 004E 4F4D    DB2STAR2.EXE.NOM
    0x0000000000127210 : 5347 0000 0000 0000 0000 0000 0000 0000    SG..............
    0x0000000000127220 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127230 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127240 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127250 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127260 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127270 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127280 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x0000000000127290 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000001272A0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000001272B0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000001272C0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00000000001272D0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    2011-11-24-15.05.25.052000-270 E6868221F480       LEVEL: Event
    PID     : 7148                 TID  : 1396        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000         DB   : CAL
    APPHDL  : 0-7                  APPID: *LOCAL.DB2CAL.111124193525
    AUTHID  : SAPSERVICECAL
    EDUID   : 1396                 EDUNAME: db2agent (CAL) 0
    FUNCTION: DB2 UDB, Self tuning memory manager, stmmLog, probe:1008
    DATA #1 : <preformatted>
    Starting STMM log from file number 30
    2011-11-24-15.05.25.177000-270 I6868703F516       LEVEL: Event
    PID     : 7148                 TID  : 1396        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000         DB   : CAL
    APPHDL  : 0-7                  APPID: *LOCAL.DB2CAL.111124193525
    AUTHID  : SAPSERVICECAL
    EDUID   : 1396                 EDUNAME: db2agent (CAL) 0
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
    CHANGE  : CFG DB CAL     : "Database_memory" From: "1120660" <automatic>  To: "1056608" <automatic>
    2011-11-24-15.05.25.489000-270 I6869221F445       LEVEL: Warning
    PID     : 7148                 TID  : 1396        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000         DB   : CAL
    APPHDL  : 0-7                  APPID: *LOCAL.DB2CAL.111124193525
    AUTHID  : SAPSERVICECAL
    EDUID   : 1396                 EDUNAME: db2agent (CAL) 0
    FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
    MESSAGE : Crash Recovery is needed.
    2011-11-24-15.05.27.969000-270 I6869668F453       LEVEL: Warning
    PID     : 7148                 TID  : 1396        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000         DB   : CAL
    APPHDL  : 0-7                  APPID: *LOCAL.DB2CAL.111124193525
    AUTHID  : SAPSERVICECAL
    EDUID   : 1396                 EDUNAME: db2agent (CAL) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_db_init, probe:700
    MESSAGE : DB2_IMPLICIT_UNICODE enabled
    2011-11-24-15.05.27.969000-270 E6870123F476       LEVEL: Event
    PID     : 7148                 TID  : 1396        PROC : db2syscs.exe
    INSTANCE: DB2CAL               NODE : 000         DB   : CAL
    APPHDL  : 0-7                  APPID: *LOCAL.DB2CAL.111124193525
    AUTHID  : SAPSERVICECAL
    EDUID   : 1396                 EDUNAME: db2agent (CAL) 0
    FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:1000
    START   : DATABASE: CAL      : ACTIVATED: YES
    thanks in advance
    JOse

Maybe you are looking for