Oracle Processes parameter

Hi,
What does "Processes" parameter mean in Oracle 10g R2. By what I understand I understood that it is the maximum number of OS processes that can be connected to Oracle. Please correct me if I am wrong. How do we determine the number of processes that we need to decide? Also What if we give the number very high i.e say 1000 or 2000. I am asking this because, I was told that for every user connected to database a process is taken away. What if I specify my processes as 200 and 5000 concurrent users try to connect to database. What is the work around for this option? If possible what please explain me what kind of errors do we get when we give processes very less? What is the maximum possible number that can be given in any environment? How does it work in RAC 10g R2? Like, are the processes distributed to each instance exactly or it changes it number dynamically? Is there any way we can find how many processes each instance in RAC is using?

PROCESSES is a static parameter.
It can only be change by restarting the DB.
It is essentially the maximum number of concurrent users (sessions within the DB).
But each additional user slot consumes RAM/shared memory

Similar Messages

  • ORA-32003: error occured processing parameter 'distributed_transactions'

    Hi,
    We are having oracle 10g database on AIX platform.As of now,Our database is running on pfile and We wanted the database to run on spfile.I tried to create the spfile and It is throwing the below error.Could somebody help me out on this issue...
    SQL> create spfile from pfile;
    create spfile from pfile
    ERROR at line 1:
    ORA-01078: failure in processing system parameters
    ORA-32003: error occured processing parameter 'distributed_transactions'
    LRM-00101: unknown parameter name 'distributed_transactions'
    I read the following old thread in this discussion forum related to this error , but I could not find a solution in that thread.
    error occured processing parameter

    Hi Satish,
    I'm not sure.I have taken up this project recently and seeing lot of issues with the databases,might be lack of proper administration.
    For some other database also I'm getting the same error for the parameter 'job_queue_interval'
    SQL> create spfile from pfile;
    create spfile from pfile
    ERROR at line 1:
    ORA-01078: failure in processing system parameters
    ORA-32003: error occured processing parameter 'job_queue_interval'
    LRM-00101: unknown parameter name 'job_queue_interval'
    If these are the parameters from oracle 8.1.7,can I comment these out.
    or How can I resolve these issues related to the parameters.

  • Setting processes parameter

    hi guys...
    i'm using db rel 10.2.0.1 enterprise edition, windows server 2003 (32-bit) , on an average work day, about 150 users are connected through the application server to the database.
    how does one know the appropriate value to set the "processes" parameter? what exactly does it depend on?
    oracle documentaion doesn't help much, so if anybody can help, it would be really appreciated.

    The Process parameter depends sort of on Sessions parameter. So if the number of sessions are 150 than settings Processes parameter to about 300 should be okay. There is no guidelines as such available which mentions how many to set. This is sort of a test-try kind of thing.
    You can check a view though, V$RESOURCE_LIMIT to check that if you set Processes to N number, how many of them are actually being used by your db?
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2050.htm#REFRN30206
    HTH
    Aman....
    Edited by: Aman.... on Dec 14, 2008 6:14 PM
    Added a bit more

  • ORACLE PROCESS의 DISK I/O PERFORMANCE CHECK

    제품 : ORACLE SERVER
    작성날짜 : 2003-06-27
    ORACLE PROCESS 가 I/O 를 과도하게 사용할 경우 조치 방법
    =======================================================
    I/O 가 heavy 하여 database 의 performance 가 떨어질 경우,
    원인을 확인하는 방법은 다음과 같습니다.
    먼저, i/o 를 빠르게 하기 위한 async I/O 가 setting 되어 있는지 확인합니다.
    async I/O 란 사용하는 H/W level 에서 제공하는 것으로, 동시에 하나 이상의
    I/O 를 할 수 있도록 해 줍니다.
    SVRMGRL 또는 SQLDBA> show parameter asyn
    NAME TYPE VALUE
    async_read boolean TRUE
    async_write boolean TRUE
    위의 값이 false 이면, H/W 가 Async I/O 를 제공하는지 확인한 후에,
    $ORACLE_HOME/dbs/initSID.ora 에 위 값을 True 로 setting 하고
    restartup 해 줍니다.
    (Async I/O 가 제공되지 않을 경우, OS channel 한개 당 하나의
    dbwr process 가 기동되도록 할 수 있습니다. db_writers 를 늘려주는 방법
    을 고려할 수도 있습니다.)
    두 번째 방법은 각 데이타 화일의 I/O를 확인해서, I/O 가 빈번한 데이타 화일을
    찾아 disk 를 옮겨 주거나 table을 다른 데이타 화일로 move해줍니다.
    다음 결과에 의해 각 datafile 의 access가 다른 datafile의 수치와 비슷할 때,
    데이타들이 잘 분산되어 I/O 병목 현상이 없는 것입니다.
    다음은 datafile 6, 7번에 read 가 집중되어 있습니다.
    만약, I/O 속도의 향상을 원한다면, 자주 read 되는 table 을 찾아서 다른 disk의
    datafile 로 옮겨 주는 것이 좋은 경우입니다.
    SQL> select file#, phyrds, phywrts from v$filestat;
    FILE# PHYRDS PHYWRTS
                  1              61667             26946
                  2              2194               58882
                  3              1972                189
                  4              804                   2
                  5              7306               13575
                  6              431859            21137
                  7              431245            3965
                  8              307                  19
    마지막으로, I/O 가 빈번한 session 을 찾아 내어 어떤 작업을 하는지
    확인하는 방법입니다.
    Session ID를 알 수 있으므로, 이 session 의 SQL 문을 확인한 후에
    I/O 를 줄일 수 있는 SQL 문으로 조정하십시오.
    (tkprof 를 이용하여 plan 과 소요 시간을 확인할 수 있습니다.)
    SQL> select sid, physical_reads, block_changes from v$sess_io
    SID PHYSICAL_READS BLOCK_CHANGES
                  1                0                0
                  2                0                0
                  3                0                0
                  4               15468          379
                  5                67               0
                  6                0                6
                  7                1               105
                  8               2487          2366
                  9               61               14
                  11             311              47

    I have seen slow iSCSI performance but in all cases it is slow on OS level already. You measurements indicate however that this is not the case but that the performance is slow just from within the guests when iSCSI disks are used.
    Two thoughts:
    - try to disable Jumbo frames. They are not standardized. While incompatible Jumbo frames typically result in a total loss of communication there might be an issue with the block sizes. Your dd tests could have been fast because of the 4K block sizes you use but the iSCSI initiator of VB may use a different block size which does not work well with Jumbo frames.
    - test the iSCSI with dd a little bit more. Use a file created from /dev/random (you can't use /dev/random directly as this is dead slow) instead of /dev/zero to avoid any interference from possible optimizations along the way. Test with different block sizes with and without Jumbo frames. What I typically get (w/ Jumbo frames) is:
    bs OSOL AR
    512 14:43 9:13
    4096 1:57 1:44
    8192 1:18 1:09
    16384 1:14 1:06
    32768 1:08 1:04 <--- sweet spot
    65536 1:08 1:08
    131072 1:14 1:11
    1048576 1:38 1:32
    Good luck,
    ~Thomas

  • Oracle Process

    Dear Gurus
    We are working in Online Application, and certain peak time our database activity increases and more than 1100 users login. ( checked in view v$session and v$parameter )
    Process parameter value = 1100
    sessions paramter value = 1215
    OS : Windows 2003 server
    Oracle : 10.2.0
    RAM : 20 GB
    SGA_TARGET : 7GB
    Server : Intel Xeon (R) 8 cpu
    Issues : DB server usage went 100% for few seconds, and then back to around 50%. Some users get DB server errors, because the process parameter is limited to 1100.
    Can you guide me ? should I increase the process parameter to 2000 ??
    or should I replace the existing server with heavy server and then increase the process parameter to 2000.
    Kind Regards.

    Umesh Gupta wrote:
    oracleRaj wrote:
    Dear Gurus
    We are working in Online Application, and certain peak time our database activity increases and more than 1100 users login. ( checked in view v$session and v$parameter )
    Process parameter value = 1100
    sessions paramter value = 1215
    OS : Windows 2003 server
    Oracle : 10.2.0
    RAM : 20 GB
    SGA_TARGET : 7GB
    Server : Intel Xeon (R) 8 cpu
    Issues : DB server usage went 100% for few seconds, and then back to around 50%. Some users get DB server errors, because the process parameter is limited to 1100.
    Can you guide me ? should I increase the process parameter to 2000 ??
    or should I replace the existing server with heavy server and then increase the process parameter to 2000.
    Kind Regards.HI,
    You can check v$resource_limit
    select * from v$resource_limit where resource_name in ('processes','sessions');
    RESOURCE_NAME   CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_AL     LIMIT_VALU     
    processes     32               150            150            150
    sessions     37               155            170            170If MAX_UTILIZATION is equal to Initial value of parameter and you are getting error regarding the same.
    You can think of increasing the values of the parameters
    Regards
    UmeshSQL> select * from v$resource_limit;
    RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_AL LIMIT_VALU
    processes 98 1100 1100 1100
    sessions 102 1215 1215 1215
    enqueue_locks 17 329 14890 14890

  • Error occured processing parameter

    Hi,
    I need to set new value for log_buffer. so what I did was i issued the following command at sql command prompt
    alter system set log_buffer=50M scope=spfile;
    it throws
    ORA-012095: specified initialization paramer cannot be modified
    so i brought the DB down and I made an entry(log_buffer=50m) in the initfile
    and saved. Then, when I try to create spfile from pfile;
    it throws error
    ORA-91978:failure in processing system parameters
    ORA-32003:error occured processing parameter 'log_buffer'
    Due to this I couldn't resize the log buffer.
    can anyone help me in how to set log_buffer
    Please help in this..... I will e grateful to you
    OS:AIX
    oracle:10.2.0.2.0
    Thanks in advance
    With Regards
    Boo

    What are you trying to resolve or trying to accomplish?
    Setting log_buffer to 50M doesn't make any sense at all,
    as the log_buffer will be written when 1M is dirty or when it's one third full, whichever occurs first.
    You are likely wasting some 45M of memory.
    Sybrand Bakker
    Senior Oracle DBA

  • MTS problem, excessive oracle processes in the OS part.

    Hi,
    yesterday I changed internet banking connections to MTS (shared server)
    So, I changed the system to mix architecture (dedicated & shared both)
    DB version is 10.2.0.3
    OS version is AIX 5.3.5
    Number of dispatchers are 2, each with 250 connections.
    Shared_Servers=10
    Max_Shared_Servers=40
    After 3 hours, I take the following error, no oracle process can be forked after in the OS.
    At the time of problem, # of oracle processes in the OS was about 4000,
    which is the OS limit for max processes a user can create.
    But the number of sessions in the v$session was about 2000.
    I also observed that SMON process turned to ZOMBIE (defunct) process.
    It seems that MTS opens more oracle processes in the OS or turned some oracle processes to zombie.
    But how can it be, since MTS does not create any new oracle processes except shared server process
    in the OS.
    When I turned back to dedicated server, everything works fine, that is, database sessions and OS oracle prosesses are almost the same.
    Thanks,
    ORA-27300: OS system dependent operation:fork failed with status: 11
    ORA-27301: OS failure message: Resource temporarily unavailable
    ORA-27302: failure occurred at: skgpspawn3

    Buffer Cache: 1,200M 1,200M Std Block Size: 8K
    Shared Pool Size: 2,960M 2,960M Log Buffer: 14,352K
    Load Profile
    Per Second Per Transaction
    Redo size: 258,968.61 6,558.43
    Logical reads: 104,557.19 2,647.93
    Block changes: 2,360.58 59.78
    Physical reads: 7,752.76 196.34
    Physical writes: 120.65 3.06
    User calls: 1,534.90 38.87
    Parses: 374.77 9.49
    Hard parses: 13.12 0.33
    Sorts: 54.16 1.37
    Logons: 0.87 0.02
    Executes: 2,867.82 72.63
    Transactions: 39.49
    % Blocks changed per Read: 2.26 Recursive Call %: 73.94
    Rollback per transaction %: 14.15 Rows per Sort: 381.28
    Instance Efficiency Percentages (Target 100%)
    Buffer Nowait %: 99.96 Redo NoWait %: 100.00
    Buffer Hit %: 92.63 In-memory Sort %: 100.00
    Library Hit %: 99.01 Soft Parse %: 96.50
    Execute to Parse %: 86.93 Latch Hit %: 99.91
    Parse CPU to Parse Elapsd %: 38.25 % Non-Parse CPU: 99.11
    Shared Pool Statistics
    Begin End
    Memory Usage %: 90.66 89.40
    % SQL with executions>1: 72.50 56.30
    % Memory for SQL w/exec>1: 74.85 60.27
    Top 5 Timed Events
    Event Waits Time(s) Avg Wait(ms) % Total Call Time Wait Class
    CPU time 9,924 43.7
    db file sequential read 10,113,395 8,454 1 37.2 User I/O
    db file scattered read 1,660,502 1,848 1 8.1 User I/O
    SQL*Net more data from client 18,186 316 17 1.4 Network
    enq: TX - row lock contention 80 221 2,766 1.0 Application
    Wait Class
    s - second
    cs - centisecond - 100th of a second
    ms - millisecond - 1000th of a second
    us - microsecond - 1000000th of a second
    ordered by wait time desc, waits desc
    Wait Class Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn
    User I/O 11,955,810 0.00 10,465 1 83.97
    Network 4,053,277 0.00 390 0 28.47
    Application 6,355 1.15 225 35 0.04
    System I/O 795,447 0.00 213 0 5.59
    Commit 100,846 0.00 140 1 0.71
    Concurrency 2,770 0.36 11 4 0.02
    Configuration 46 19.57 0 8 0.00
    Other 1,491 0.07 0 0 0.01
    Wait Events
    s - second
    cs - centisecond - 100th of a second
    ms - millisecond - 1000th of a second
    us - microsecond - 1000000th of a second
    ordered by wait time desc, waits desc (idle events last)
    Event Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn
    db file sequential read 10,113,395 0.00 8,454 1 71.03
    db file scattered read 1,660,502 0.00 1,848 1 11.66
    SQL*Net more data from client 18,186 0.00 316 17 0.13
    enq: TX - row lock contention 80 91.25 221 2766 0.00
    read by other session 157,454 0.00 142 1 1.11
    log file sync 100,846 0.00 140 1 0.71
    log file parallel write 128,249 0.00 137 1 0.90
    TCP Socket (KGAS) 2,429 0.00 64 26 0.02
    db file parallel write 10,158 0.00 55 5 0.07
    direct path write temp 6,721 0.00 13 2 0.05
    log file sequential read 981 0.00 8 9 0.01
    SQL*Net more data to client 156,908 0.00 6 0 1.10
    control file sequential read 651,338 0.00 5 0 4.57
    Log archive I/O 1,990 0.00 5 2 0.01
    latch: library cache 667 0.00 4 7 0.00
    db file parallel read 769 0.00 4 6 0.01
    os thread startup 127 0.00 4 33 0.00
    SQL*Net message to client 3,850,305 0.00 4 0 27.04
    SQL*Net break/reset to client 6,182 0.00 3 0 0.04
    control file parallel write 2,691 0.00 2 1 0.02
    latch: shared pool 145 0.00 2 12 0.00
    direct path read temp 13,714 0.00 1 0 0.10
    enq: RO - fast object reuse 93 0.00 1 9 0.00
    local write wait 300 0.00 0 1 0.00
    log file switch completion 29 0.00 0 12 0.00
    direct path read 1,806 0.00 0 0 0.01
    latch free 35 0.00 0 4 0.00
    direct path write 1,149 0.00 0 0 0.01
    SQL*Net more data to dblink 7,126 0.00 0 0 0.05
    log file single write 40 0.00 0 3 0.00
    cursor: pin S wait on X 12 83.33 0 8 0.00
    latch: cache buffers chains 1,666 0.00 0 0 0.01
    SQL*Net message to dblink 18,120 0.00 0 0 0.13
    reliable message 87 0.00 0 1 0.00
    LGWR wait for redo copy 1,209 0.00 0 0 0.01
    latch: messages 16 0.00 0 2 0.00
    latch: redo writing 7 0.00 0 5 0.00
    enq: TX - index contention 4 0.00 0 7 0.00
    rdbms ipc reply 95 0.00 0 0 0.00
    buffer busy waits 143 0.00 0 0 0.00
    latch: object queue header operation 18 0.00 0 1 0.00
    latch: checkpoint queue latch 2 0.00 0 5 0.00
    latch: cache buffers lru chain 2 0.00 0 3 0.00
    SQL*Net more data from dblink 203 0.00 0 0 0.00
    library cache load lock 1 0.00 0 4 0.00
    row cache lock 2 0.00 0 0 0.00
    latch: library cache pin 1 0.00 0 0 0.00
    undo segment extension 10 90.00 0 0 0.00
    cursor: pin S 26 0.00 0 0 0.00
    cursor: mutex S 2 0.00 0 0 0.00
    buffer deadlock 1 100.00 0 0 0.00
    SQL*Net message from client 3,850,087 0.00 2,879,903 748 27.04
    virtual circuit status 95,480 0.66 30,974 324 0.67
    jobq slave wait 6,672 87.16 18,382 2755 0.05
    wait for unread message on broadcast channel 3,611 100.00 3,521 975 0.03
    Streams AQ: waiting for messages in the queue 732 100.00 3,517 4805 0.01
    Streams AQ: qmn slave idle wait 129 0.00 3,506 27182 0.00
    Streams AQ: qmn coordinator idle wait 370 34.86 3,506 9477 0.00
    Streams AQ: waiting for time management or cleanup tasks 3 100.00 953 317683 0.00
    SQL*Net message from dblink 18,120 0.00 679 37 0.13
    HS message to agent 16,986 0.00 89 5 0.12
    single-task message 170 0.00 9 50 0.00
    pipe get 28 0.00 3 114 0.00
    class slave wait 2 0.00 0 0 0.00
    Background Wait Events
    ordered by wait time desc, waits desc (idle events last)
    Event Waits %Time -outs Total Wait Time (s) Avg wait (ms) Waits /txn
    log file parallel write 128,212 0.00 137 1 0.90
    db file parallel write 10,158 0.00 55 5 0.07
    db file sequential read 8,822 0.00 11 1 0.06
    log file sequential read 981 0.00 8 9 0.01
    Log archive I/O 1,990 0.00 5 2 0.01
    os thread startup 127 0.00 4 33 0.00
    control file parallel write 2,091 0.00 1 1 0.01
    db file scattered read 172 0.00 1 3 0.00
    control file sequential read 12,106 0.00 1 0 0.09
    events in waitclass Other 1,351 0.00 0 0 0.01
    direct path read 1,800 0.00 0 0 0.01
    log file single write 40 0.00 0 3 0.00
    direct path write 900 0.00 0 0 0.01
    latch: redo writing 7 0.00 0 5 0.00
    latch: cache buffers chains 15 0.00 0 1 0.00
    log file sync 2 0.00 0 1 0.00
    buffer busy waits 6 0.00 0 0 0.00
    rdbms ipc message 246,802 7.02 60,773 246 1.73
    pmon timer 2,015 97.37 3,515 1744 0.01
    Streams AQ: qmn slave idle wait 129 0.00 3,506 27182 0.00
    Streams AQ: qmn coordinator idle wait 370 34.86 3,506 9477 0.00
    smon timer 519 0.00 3,505 6753 0.00
    Streams AQ: waiting for time management or cleanup tasks 3 100.00 953 317683 0.00
    Operating System Statistics
    Statistic Total
    NUM_LCPUS 0
    NUM_VCPUS 0
    AVG_BUSY_TIME 78,988
    AVG_IDLE_TIME 281,508
    AVG_IOWAIT_TIME 55,083
    AVG_SYS_TIME 17,835
    AVG_USER_TIME 61,046
    BUSY_TIME 1,265,704
    IDLE_TIME 4,506,088
    IOWAIT_TIME 883,071
    SYS_TIME 287,149
    USER_TIME 978,555
    LOAD 0
    OS_CPU_WAIT_TIME 1,232,300
    RSRC_MGR_CPU_WAIT_TIME 0
    PHYSICAL_MEMORY_BYTES 33,285,996,544
    NUM_CPUS 16
    NUM_CPU_CORES 8
    Service Statistics
    ordered by DB Time
    Service Name DB Time (s) DB CPU (s) Physical Reads Logical Reads
    andlp2 13,795.70 5,680.50 23,785,158 266,206,268
    SYS$USERS 5,146.80 2,456.20 3,079,496 60,895,888
    shared_andlp2 3,777.40 1,795.40 1,063,806 49,135,813
    SYS$BACKGROUND 0.00 0.00 12,840 1,021,071
    andlp2XDB 0.00 0.00 0 0
    Service Wait Class Stats
    Wait Class info for services in the Service Statistics section.
    Total Waits and Time Waited displayed for the following wait classes: User I/O, Concurrency, Administrative, Network
    Time Waited (Wt Time) in centisecond (100th of a second)
    Service Name User I/O Total Wts User I/O Wt Time Concurcy Total Wts Concurcy Wt Time Admin Total Wts Admin Wt Time Network Total Wts Network Wt Time
    andlp2 9575680 700718 2099 466 0 0 3945537 6997
    SYS$USERS 1415659 141165 151 25 0 0 20355 17
    shared_andlp2 951411 203079 364 144 0 0 81260 31984
    SYS$BACKGROUND 12818 1478 148 422 0 0 0 0
    SQL ordered by Elapsed Time
    Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
    % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100
    Elapsed Time (s) CPU Time (s) Executions Elap per Exec (s) % Total DB Time SQL Id SQL Module SQL Text
    1,443 104 273 5.29 6.35 9xvr07cvm5md0 httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    1,304 640 29 44.95 5.74 91wxrh27r5g8n DECLARE job BINARY_INTEGER := ...
    936 453 424 2.21 4.12 abkgjr63dv6u8 frmweb.exe SELECT MUS_K_ISIM , HESAP_NO ...
    859 335 30 28.63 3.78 c406h8xcvfn4s DECLARE job BINARY_INTEGER := ...
    703 272 30 23.45 3.10 g0y0bsusuagjt INSERT INTO MARDATA.M_D_HESAP_...
    701 139 1,613 0.43 3.09 g5636apbsuu6m Apache.exe declare rc__ number; simple_...
    664 589 16 41.50 2.92 gu3j96aktwv05 Apache.exe declare rc__ number; simple_...
    626 13 250 2.50 2.76 gn6w1hb4paw56 frmweb.exe SELECT TUTAR , B_A , ACIK_RE...
    517 94 754 0.69 2.28 3cawwq59capz2 frmweb.exe select mus_k_isim, hesap_no fr...
    515 463 16 32.19 2.27 chz9021ufnzyn Apache.exe SELECT SIR.SIRKET_ADI, P.SUBE...
    508 156 30 16.92 2.23 3ax52z7dpz9mc SELECT H.HESAP_NO, SUM(NVL(H....
    496 18 1,134 0.44 2.18 fydgv84cqwmxn frmweb.exe SELECT /*+ INDEX(M1 M_MHAREKET...
    419 124 53 7.90 1.84 7pxhq3kjq89c4 Apache.exe declare rc__ number; simple_...
    407 115 52 7.83 1.79 7q13983tc3z7j Apache.exe SELECT SUM(ORTALAMA_TUTAR_TL *...
    386 104 366 1.05 1.70 4pcsmrfq05c3t httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    382 311 598 0.64 1.68 53tzqfs73d0n4 httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    351 44 30 11.71 1.55 729cpbmdgb7xg frmweb.exe SELECT A.ISUBE , A.CEK_NO , ...
    322 238 131 2.46 1.42 gxkktn00ntrc7 frmweb.exe SELECT A.SUBE_KOD , A.HESAP_N...
    319 21 387 0.83 1.41 8rnb53wzsnjyz httpd@karabatak (TNS V1-V3) SELECT TO_CHAR(MAX(CIKIS), 'DD...
    312 29 269 1.16 1.37 6nmu8qrsffk0p frmweb.exe SELECT E.KULLANICIKODU , E.IP...
    296 194 126 2.35 1.30 3vtwpw06rp7q9 frmweb.exe SELECT A.SUBE_KOD , A.HESAP_N...
    SQL ordered by CPU Time
    Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
    % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100
    CPU Time (s) Elapsed Time (s) Executions CPU per Exec (s) % Total DB Time SQL Id SQL Module SQL Text
    640 1,304 29 22.06 5.74 91wxrh27r5g8n DECLARE job BINARY_INTEGER := ...
    589 664 16 36.79 2.92 gu3j96aktwv05 Apache.exe declare rc__ number; simple_...
    463 515 16 28.92 2.27 chz9021ufnzyn Apache.exe SELECT SIR.SIRKET_ADI, P.SUBE...
    453 936 424 1.07 4.12 abkgjr63dv6u8 frmweb.exe SELECT MUS_K_ISIM , HESAP_NO ...
    335 859 30 11.17 3.78 c406h8xcvfn4s DECLARE job BINARY_INTEGER := ...
    311 382 598 0.52 1.68 53tzqfs73d0n4 httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    272 703 30 9.07 3.10 g0y0bsusuagjt INSERT INTO MARDATA.M_D_HESAP_...
    238 322 131 1.82 1.42 gxkktn00ntrc7 frmweb.exe SELECT A.SUBE_KOD , A.HESAP_N...
    194 296 126 1.54 1.30 3vtwpw06rp7q9 frmweb.exe SELECT A.SUBE_KOD , A.HESAP_N...
    159 195 479 0.33 0.86 cc0nhrvkmuy8r httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    156 508 30 5.21 2.23 3ax52z7dpz9mc SELECT H.HESAP_NO, SUM(NVL(H....
    139 701 1,613 0.09 3.09 g5636apbsuu6m Apache.exe declare rc__ number; simple_...
    124 419 53 2.35 1.84 7pxhq3kjq89c4 Apache.exe declare rc__ number; simple_...
    115 407 52 2.21 1.79 7q13983tc3z7j Apache.exe SELECT SUM(ORTALAMA_TUTAR_TL *...
    104 386 366 0.28 1.70 4pcsmrfq05c3t httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    104 1,443 273 0.38 6.35 9xvr07cvm5md0 httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    94 517 754 0.12 2.28 3cawwq59capz2 frmweb.exe select mus_k_isim, hesap_no fr...
    44 351 30 1.46 1.55 729cpbmdgb7xg frmweb.exe SELECT A.ISUBE , A.CEK_NO , ...
    29 312 269 0.11 1.37 6nmu8qrsffk0p frmweb.exe SELECT E.KULLANICIKODU , E.IP...
    21 319 387 0.05 1.41 8rnb53wzsnjyz httpd@karabatak (TNS V1-V3) SELECT TO_CHAR(MAX(CIKIS), 'DD...
    18 496 1,134 0.02 2.18 fydgv84cqwmxn frmweb.exe SELECT /*+ INDEX(M1 M_MHAREKET...
    13 626 250 0.05 2.76 gn6w1hb4paw56 frmweb.exe SELECT TUTAR , B_A , ACIK_RE...
    SQL ordered by Gets
    Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
    Total Buffer Gets: 377,028,313
    Captured SQL account for 36.7% of Total
    Buffer Gets Executions Gets per Exec %Total CPU Time (s) Elapsed Time (s) SQL Id SQL Module SQL Text
    36,098,836 30 1,203,294.53 9.57 335.17 858.88 c406h8xcvfn4s DECLARE job BINARY_INTEGER := ...
    25,797,967 30 859,932.23 6.84 156.31 507.52 3ax52z7dpz9mc SELECT H.HESAP_NO, SUM(NVL(H....
    21,427,570 598 35,832.06 5.68 310.83 382.37 53tzqfs73d0n4 httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    18,504,944 30 616,831.47 4.91 79.74 84.82 274s1h17p0j36 Reutersdevdb.exe (SELECT /*+ RULE */ '', T.own...
    18,132,811 29 625,269.34 4.81 639.68 1303.64 91wxrh27r5g8n DECLARE job BINARY_INTEGER := ...
    17,912,396 30 597,079.87 4.75 77.26 82.67 5cnac71x8744k Reutersdevdb.exe (SELECT /*+ RULE */ '', T.own...
    15,416,026 1,785 8,636.43 4.09 149.52 160.50 7u1rxxk2anfm1 httpd@karabatak (TNS V1-V3) SELECT /*+RULE*/ DISTINCT MD.S...
    11,188,695 16 699,293.44 2.97 588.69 664.07 gu3j96aktwv05 Apache.exe declare rc__ number; simple_...
    9,348,310 16 584,269.38 2.48 462.77 515.02 chz9021ufnzyn Apache.exe SELECT SIR.SIRKET_ADI, P.SUBE...
    8,674,950 424 20,459.79 2.30 452.70 935.96 abkgjr63dv6u8 frmweb.exe SELECT MUS_K_ISIM , HESAP_NO ...
    6,987,779 479 14,588.27 1.85 158.99 195.29 cc0nhrvkmuy8r httpd@karabatak (TNS V1-V3) declare rc__ number; simple_...
    6,545,269 53 123,495.64 1.74 124.31 418.90 7pxhq3kjq89c4 Apache.exe declare rc__ number; simple_...
    6,373,078 52 122,559.19 1.69 115.18 407.03 7q13983tc3z7j Apache.exe SELECT SUM(ORTALAMA_TUTAR_TL *...
    5,977,931 30 199,264.37 1.59 272.13 703.48 g0y0bsusuagjt INSERT INTO MARDATA.M_D_HESAP_...
    5,820,172 106 54,907.28 1.54 145.09 152.34 7nh29bk1sg42r frmweb.exe select distinct grup_kod, hes...
    Instance Activity Stats
    Statistic Total per Second per Trans
    CPU used by this session 820,065 227.42 5.76
    CPU used when call started 677,803 187.97 4.76
    CR blocks created 16,866 4.68 0.12
    Cached Commit SCN referenced 890,130 246.85 6.25
    Commit SCN cached 198 0.05 0.00
    DB time 3,363,185,519 932,675.92 23,620.20
    DBWR checkpoint buffers written 9,520 2.64 0.07
    DBWR checkpoints 100 0.03 0.00
    DBWR object drop buffers written 1,921 0.53 0.01
    DBWR parallel query checkpoint buffers written 0 0.00 0.00
    DBWR revisited being-written buffer 25 0.01 0.00
    DBWR tablespace checkpoint buffers written 0 0.00 0.00
    DBWR thread checkpoint buffers written 2,589 0.72 0.02
    DBWR transaction table writes 1,062 0.29 0.01
    DBWR undo block writes 75,368 20.90 0.53
    DDL statements parallelized 0 0.00 0.00
    DFO trees parallelized 0 0.00 0.00
    Misses for writing mapping 0 0.00 0.00
    PX local messages recv'd 0 0.00 0.00
    PX local messages sent 0 0.00 0.00
    Parallel operations downgraded 1 to 25 pct 0 0.00 0.00
    Parallel operations downgraded 50 to 75 pct 0 0.00 0.00
    Parallel operations not downgraded 0 0.00 0.00
    SMON posted for dropping temp segment 0 0.00 0.00
    SMON posted for undo segment recovery 0 0.00 0.00
    SMON posted for undo segment shrink 15 0.00 0.00
    SQL*Net roundtrips to/from client 3,859,275 1,070.25 27.10
    SQL*Net roundtrips to/from dblink 31,149 8.64 0.22
    active txn count during cleanout 115,814 32.12 0.81
    application wait time 22,502 6.24 0.16
    auto extends on undo tablespace 0 0.00 0.00
    background checkpoints completed 10 0.00 0.00
    background checkpoints started 10 0.00 0.00
    background timeouts 17,610 4.88 0.12
    branch node splits 7 0.00 0.00
    buffer is not pinned count 203,367,173 56,397.62 1,428.28
    buffer is pinned count 423,534,399 117,454.22 2,974.55
    bytes received via SQL*Net from client 875,387,626 242,761.80 6,147.99
    bytes received via SQL*Net from dblink 12,992,864 3,603.17 91.25
    bytes sent via SQL*Net to client ############### 1,369,289,664.01 34,677,525.68
    bytes sent via SQL*Net to dblink 52,952,034,748 14,684,615.90 371,890.74
    calls to get snapshot scn: kcmgss 15,353,638 4,257.86 107.83
    calls to kcmgas 732,189 203.05 5.14
    calls to kcmgcs 89,721 24.88 0.63
    change write time 3,250 0.90 0.02
    cleanout - number of ktugct calls 130,405 36.16 0.92
    cleanouts and rollbacks - consistent read gets 11,180 3.10 0.08
    cleanouts only - consistent read gets 2,244 0.62 0.02
    cluster key scan block gets 383,816 106.44 2.70
    cluster key scans 306,047 84.87 2.15
    commit batch performed 344 0.10 0.00
    commit batch requested 344 0.10 0.00
    commit batch/immediate performed 1,111 0.31 0.01
    commit batch/immediate requested 1,111 0.31 0.01
    commit cleanout failures: block lost 54,881 15.22 0.39
    commit cleanout failures: buffer being written 11 0.00 0.00
    commit cleanout failures: callback failure 1,410 0.39 0.01
    commit cleanout failures: cannot pin 77 0.02 0.00
    commit cleanout failures: hot backup in progress 0 0.00 0.00
    commit cleanouts 349,392 96.89 2.45
    commit cleanouts successfully completed 293,014 81.26 2.06
    commit immediate performed 767 0.21 0.01
    commit immediate requested 767 0.21 0.01
    commit txn count during cleanout 68,019 18.86 0.48
    concurrency wait time 1,058 0.29 0.01
    consistent changes 3,439,859 953.94 24.16
    consistent gets 366,680,318 101,687.49 2,575.26
    consistent gets - examination 121,966,420 33,823.63 856.59
    consistent gets direct 7,642 2.12 0.05
    consistent gets from cache 366,672,556 101,685.34 2,575.20
    current blocks converted for CR 55 0.02 0.00
    cursor authentications 14,703 4.08 0.10
    data blocks consistent reads - undo records applied 70,817 19.64 0.50
    db block changes 8,512,132 2,360.58 59.78
    db block gets 10,345,635 2,869.04 72.66
    db block gets direct 2,604 0.72 0.02
    db block gets from cache 10,343,017 2,868.32 72.64
    deferred (CURRENT) block cleanout applications 164,540 45.63 1.16
    dirty buffers inspected 201,591 55.91 1.42
    enqueue conversions 684,245 189.75 4.81
    enqueue deadlocks 0 0.00 0.00
    enqueue releases 2,493,773 691.57 17.51
    enqueue requests 2,493,903 691.61 17.52
    enqueue timeouts 68 0.02 0.00
    enqueue waits 101 0.03 0.00
    exchange deadlocks 1 0.00 0.00
    execute count 10,341,226 2,867.82 72.63
    failed probes on index block reclamation 0 0.00 0.00
    frame signature mismatch 0 0.00 0.00
    free buffer inspected 28,677,695 7,952.88 201.41
    free buffer requested 28,684,393 7,954.73 201.46
    global undo segment hints helped 0 0.00 0.00
    heap block compress 87,275 24.20 0.61
    hot buffers moved to head of LRU 3,506,139 972.32 24.62
    immediate (CR) block cleanout applications 13,424 3.72 0.09
    immediate (CURRENT) block cleanout applications 55,019 15.26 0.39
    index crx upgrade (found) 133 0.04 0.00
    index crx upgrade (positioned) 190,756 52.90 1.34
    index fast full scans (direct read) 0 0.00 0.00
    index fast full scans (full) 4,521 1.25 0.03
    index fast full scans (rowid ranges) 0 0.00 0.00
    index fetch by key 63,569,968 17,629.17 446.46
    index scans kdiixs1 47,264,964 13,107.48 331.95
    java call heap collected bytes 146,595,424 40,653.73 1,029.56
    java call heap collected count 2,109,118 584.90 14.81
    java call heap gc count 2,036 0.56 0.01
    java call heap live object count 53,667 14.88 0.38
    java call heap live object count max 163,629 45.38 1.15
    java call heap live size 4,897,136 1,358.07 34.39
    java call heap live size max 15,033,192 4,168.99 105.58
    java call heap object count 135,994 37.71 0.96
    java call heap object count max 194,386 53.91 1.37
    java call heap total size 8,131,840 2,255.12 57.11
    java call heap total size max 22,874,112 6,343.43 160.65
    java call heap used size 10,414,544 2,888.15 73.14
    java call heap used size max 17,090,000 4,739.39 120.03
    java session heap collected bytes 299,008 82.92 2.10
    java session heap collected count 223 0.06 0.00
    java session heap gc count 2 0.00 0.00
    java session heap live object count 62,042 17.21 0.44
    java session heap live object count max 62,204 17.25 0.44
    java session heap live size 6,119,424 1,697.03 42.98
    java session heap live size max 6,307,840 1,749.29 44.30
    java session heap object count 62,204 17.25 0.44
    java session heap object count max 62,204 17.25 0.44
    java session heap used size 6,307,840 1,749.29 44.30
    java session heap used size max 6,307,840 1,749.29 44.30
    leaf node 90-10 splits 590 0.16 0.00
    leaf node splits 12,720 3.53 0.09
    lob reads 18,068 5.01 0.13
    lob writes 378,857 105.06 2.66
    lob writes unaligned 378,854 105.06 2.66
    logons cumulative 3,128 0.87 0.02
    messages received 320,519 88.89 2.25
    messages sent 320,519 88.89 2.25
    no buffer to keep pinned count 0 0.00 0.00
    no work - consistent read gets 240,593,829 66,721.29 1,689.73
    opened cursors cumulative 1,230,004 341.10 8.64
    parse count (failures) 1,216 0.34 0.01
    parse count (hard) 47,313 13.12 0.33
    parse count (total) 1,351,392 374.77 9.49
    parse time cpu 8,806 2.44 0.06
    parse time elapsed 23,022 6.38 0.16
    physical read IO requests 11,798,391 3,271.92 82.86
    physical read bytes ############### 63,510,595.88 1,608,418.13
    physical read total IO requests 12,450,298 3,452.71 87.44
    physical read total bytes ############### 65,250,489.97 1,652,481.28
    physical read total multi block requests 1,668,164 462.61 11.72
    physical reads 27,956,086 7,752.76 196.34
    physical reads cache 27,790,026 7,706.71 195.17
    physical reads cache prefetch 16,014,666 4,441.17 112.47
    physical reads direct 166,060 46.05 1.17
    physical reads direct (lob) 7,635 2.12 0.05
    physical reads direct temporary tablespace 164,248 45.55 1.15
    physical reads prefetch warmup 0 0.00 0.00
    physical write IO requests 144,520 40.08 1.01
    physical write bytes 3,563,954,176 988,352.92 25,030.23
    physical write total IO requests 415,411 115.20 2.92
    physical write total bytes 7,501,977,600 2,080,442.42 52,687.61
    physical write total multi block requests 277,345 76.91 1.95
    physical writes 435,053 120.65 3.06
    physical writes direct 179,591 49.80 1.26
    physical writes direct (lob) 7 0.00 0.00
    physical writes direct temporary tablespace 176,122 48.84 1.24
    physical writes from cache 255,462 70.84 1.79
    physical writes non checkpoint 421,691 116.94 2.96
    pinned buffers inspected 1,685 0.47 0.01
    prefetch clients - default 1 0.00 0.00
    prefetch clients - keep 0 0.00 0.00
    prefetch warmup blocks aged out before use 0 0.00 0.00
    prefetched blocks aged out before use 2,672 0.74 0.02
    process last non-idle time 3,608 1.00 0.03
    queries parallelized 0 0.00 0.00
    recursive aborts on index block reclamation 0 0.00 0.00
    recursive calls 15,701,925 4,354.45 110.28
    recursive cpu usage 332,230 92.13 2.33
    redo blocks written 1,942,511 538.70 13.64
    redo buffer allocation retries 32 0.01 0.00
    redo entries 3,543,077 982.56 24.88
    redo log space requests 36 0.01 0.00
    redo log space wait time 32 0.01 0.00
    redo ordering marks 70,040 19.42 0.49
    redo size 933,828,628 258,968.61 6,558.43
    redo subscn max counts 92,765 25.73 0.65
    redo synch time 14,438 4.00 0.10
    redo synch writes 122,752 34.04 0.86
    redo wastage 28,240,164 7,831.54 198.34
    redo write time 14,659 4.07 0.10
    redo writer latching time 9 0.00 0.00
    redo writes 127,955 35.48 0.90
    rollback changes - undo records applied 10,431 2.89 0.07
    rollbacks only - consistent read gets 5,824 1.62 0.04
    rows fetched via callback 29,956,870 8,307.62 210.39
    session connect time 0 0.00 0.00
    session cursor cache hits 912,331 253.01 6.41
    session logical reads 377,028,313 104,557.19 2,647.93
    session pga memory 5,535,258,240 1,535,033.39 38,875.02
    session pga memory max ############### 35,280,612.09 893,488.33
    session uga memory ############### 1,112,659,489.56 28,178,316.86
    session uga memory max 6,581,957,632 1,825,303.22 46,226.16
    shared hash latch upgrades - no wait 662,685 183.78 4.65
    shared hash latch upgrades - wait 173 0.05 0.00
    sorts (disk) 0 0.00 0.00
    sorts (memory) 195,297 54.16 1.37
    sorts (rows) 74,462,048 20,649.76 522.96
    sql area evicted 29,407 8.16 0.21
    sql area purged 1,282 0.36 0.01
    summed dirty queue length 164,234 45.55 1.15
    switch current to new buffer 496,872 137.79 3.49
    table fetch by rowid 250,959,297 69,595.83 1,762.53
    table fetch continued row 634,272 175.90 4.45
    table scan blocks gotten 61,069,211 16,935.66 428.90
    table scan rows gotten 5,007,057,760 1,388,553.25 35,165.38
    table scans (cache partitions) 0 0.00 0.00
    table scans (direct read) 0 0.00 0.00
    table scans (long tables) 1,590 0.44 0.01
    table scans (rowid ranges) 0 0.00 0.00
    table scans (short tables) 1,455,250 403.57 10.22
    total number of times SMON posted 519 0.14 0.00
    transaction rollbacks 1,111 0.31 0.01
    transaction tables consistent read rollbacks 4 0.00 0.00
    transaction tables consistent reads - undo records applied 182 0.05 0.00
    undo change vector size 464,337,752 128,769.77 3,261.12
    user I/O wait time 1,046,881 290.32 7.35
    user calls 5,534,784 1,534.90 38.87
    user commits 122,239 33.90 0.86
    user rollbacks 20,147 5.59 0.14
    workarea executions - multipass 0 0.00 0.00
    workarea executions - onepass 19 0.01 0.00
    workarea executions - optimal 155,732 43.19 1.09
    write clones created in background 300 0.08 0.00
    write clones created in foreground 114 0.03 0.00
    Buffer Pool Statistics
    Standard block size Pools D: default, K: keep, R: recycle
    Default Pools for other block sizes: 2k, 4k, 8k, 16k, 32k
    P Number of Buffers Pool Hit% Buffer Gets Physical Reads Physical Writes Free Buff Wait Writ Comp Wait Buffer Busy Waits
    D 148,425 96 343,814,932 13,754,200 250,967 0 0 87,158
    K 7,916 58 33,054,317 14,034,039 4,373 0 0 70,577
    Enqueue Activity
    only enqueues with waits are shown
    Enqueue stats gathered prior to 10g should not be compared with 10g data
    ordered by Wait Time desc, Waits desc
    Enqueue Type (Request Reason) Requests Succ Gets Failed Gets Waits Wt Time (s) Av Wt Time(ms)
    TX-Transaction (row lock contention) 60 7 53 7 227 32,372.43
    RO-Multiple Object Reuse (fast object reuse) 810 810 0 90 1 9.60
    TX-Transaction (index contention) 4 4 0 4 0 7.00
    Resource Limit Stats
    only rows with Current or Maximum Utilization > 80% of Limit are shown
    ordered by resource name
    Resource Name Current Utilization Maximum Utilization Initial Allocation Limit
    processes 1,195 1,750 1750 1750
    sessions 1,230 1,930 1930 1930
    init.ora Parameters
    Parameter Name Begin value End value (if different)
    O7_DICTIONARY_ACCESSIBILITY TRUE
    aq_tm_processes 1
    archive_lag_target 1800
    audit_trail DB, EXTENDED
    background_dump_dest /oracle/orahome10/admin/andlp2/bdump
    compatible 10.2.0.3.0
    control_files /datac5/oradata/andlp2/control01.ctl, /datac6/oradata/andlp2/control02.ctl, /datac7/oradata/andlp2/control03.ctl
    core_dump_dest /oracle/orahome10/admin/andlp2/cdump
    cursor_sharing EXACT
    db_block_checksum FALSE
    db_block_size 8192
    db_cache_advice ON
    db_cache_size 1258291200
    db_domain
    db_file_multiblock_read_count 16
    db_keep_cache_size 67108864
    db_name andlp2
    db_recycle_cache_size 0
    db_writer_processes 6
    dispatchers (PROTOCOL=TCP)(SERVICE=shared_andlp2)(CONNECTIONS=250)(DISPATCHERS=2)
    fast_start_mttr_target 300
    filesystemio_options ASYNCH
    instance_name andlp2
    java_pool_size 100663296
    job_queue_processes 74
    large_pool_size 637534208
    local_listener LISTENER_ANDLP2
    log_archive_dest_1 LOCATION=/onliner0/andlp2/archive/
    log_archive_dest_2 LOCATION=/datac5/archive/
    log_archive_dest_3 SERVICE=ANDLP3
    log_archive_dest_state_3 DEFER
    log_archive_format %t_%s_%r.dbf
    log_archive_max_processes 4
    log_archive_min_succeed_dest 1
    log_buffer 14251008
    log_checkpoint_interval 200000
    log_checkpoint_timeout 27000
    max_dispatchers 2
    max_dump_file_size 1500M
    max_shared_servers 40
    open_cursors 500
    pga_aggregate_target 2621440000
    processes 1750
    query_rewrite_enabled TRUE
    remote_dependencies_mode SIGNATURE
    remote_login_passwordfile EXCLUSIVE
    remote_os_authent FALSE
    resource_limit TRUE
    session_cached_cursors 250
    session_max_open_files 20
    sga_max_size 5251268608
    shared_pool_size 3103784960
    shared_servers 10
    sort_area_retained_size 131072
    sort_area_size 1048576
    star_transformation_enabled FALSE
    streams_pool_size 50331648
    timed_statistics TRUE
    trace_enabled FALSE
    undo_management AUTO
    undo_retention 36000
    undo_tablespace UNDOTBS1
    user_dump_dest /oracle/orahome10/admin/andlp2/udump

  • Optimal value of processes parameter in AMS instance

    Hi
    If we have several database instances on single server which are accessing ASM instance. How can we calculate optimal value of PROCESSES parameter for ASM instance
    Here, I would like to mention that we are using Goldengate also for replication and for this our ARCHIVE DG is on ASM
    Rgds
    Harvindr

    I have seen systems with multiple database instances (4-6) and running very well with just the defaults. That being said, follow the recommendations. GG, IIRC, talks to the database which does all of the reads/writes for GG. Therefore, 50+50*n RDBMS INSTANCES.
    http://docs.oracle.com/cd/E11882_01/server.112/e10803/config_gg.htm
    "Oracle GoldenGate 11g introduces a new optimized method of reading log files stored in Oracle ASM. *This new method uses the database server to access the redo and archived redo log files, instead of connecting directly to the Oracle ASM instance*. The database must contain the libraries with the API modules. The libraries are currently included with Oracle Database release 10.2.0.5 and 11.2.0.2. For information for accessing the API modules for other releases, see "Optimized Access for Oracle GoldenGate to Redo Log Files in ASM - for Oracle Database Releases other than 10.2.0.5 and 11.2.0.2" in My Oracle Support Note 1333171.1 at https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1333171.1 "

  • Processes Parameter in 11g

    Hello,
    Oracle offers licencing by the number of processes parameter. I want to increase Processes value to 300. let me know oracle recomends any licence aggrement? or we can increase
    the processes parameter any value depends on the no of CPU's ? Is there any effect if we increase processes parameter to 300? FOR INCREASING THE PROCESSES PARAMETER ORACLE RECOMENDS LICENCE AGGREMENT?
    NAME VALUE
    processes 150
    sessions 264
    transactions 290
    SESSIONS_MAX USERS_MAX CPU_COUNT_CURRENT
    0 0 24
    Above is the total cpu count.
    Regards,
    Edited by: Hari Ravipati on 24 Jun, 2012 4:36 AM

    Oracle licensing options vary - pl check with your friendly Oracle salesperson regarding your license options. Any licensing advice offered in these forums in not legally binding in a court of law :-)
    HTH
    Srini

  • Changes on Oracle Database Parameter when you increase your WP

    Hi,
    I need to know what oracle parameter do I need to change when I increase the number of WP.
    I know from note 124361, you need to increase the following:
    - PROCESS   -->  #SAP Work processes * 2 + 20
    - SESSIONS  --> >=PROCESS
    My question:
    1. Is there any other parameter? what do I miss?
    2. What is good number for session. Should it be 1 more or 10 more than the number of PROCESS?
    Thanks in advance.

    Hi,
    If you are using oracle 9i then in this case the parameter have following value corresponds to sap workprocess  number ( this values is not applied to SAP BW based system)
    PROCESSES  ->     (Total number of SAP WP * 2 ) + 20
    SESSIONS ->       >=  PROCESSES
    In case of Oracle 10g
    PROCESSES  ->   (Total number of SAP WP * 2 ) + (J2EE Server  processes *
    MAX_CONNECTIONS) +    PARALLEL_MAX_SERVERS + 40
    Where
    PROCESSES
    - Defines the maximum number of Oracle processes that exist in parallel
    - The component relating to ABAP work processes is only relevant in systems with ABAP stacks. The component relating to J2EE server processes is only relevant in systems with Java stacks.
    MAX_CONNECTIONS
    - indicates the maximum number of connections (also called pool size) of the J2EE system DataSource
    PARALLEL_MAX_SERVERS
    - Defines the maximum number of parallel query processes
    - Based on the number of CPU Cores of the database server
    - The number of CPU Cores generally corresponds to the default value for the Oracle parameter CPU_COUNT. Therefore, if you are unsure in individual cases, you can use the value of the parameter CPU_COUNT (for example, in transaction DB26).
    - If the database shares the server with other software (for example, SAP central instance, other Oracle instances), only the part of the CPU Cores that is mathematically available to the database should be considered in the calculation (for example, 8 CPU Cores, the SAP central instance and the Oracle database are to share resources 50:50 -> PARALLEL_MAX_SERVERS = 8 * 0.5 * 10 = 40).
    Reference Note :  830576 - Parameter recommendations for Oracle 10g
    If you are not using JAVA Stack then you can omit the Java stack related parameter.
    regards,
    kaushal

  • Processes parameter

    I have an Oracle 9i database.
    Currently the processes parameter has been set to 500. In future the number of concurrent user processes will be around 2500.
    How can I say whether my database will support those many processes based on x GB of physical memory or pga or sga size.
    Thanks in advance.

    I don't think there is any way, other than "testing", to certify whether your configuration will support those many number of users.
    If you would like to verify how your system (configuration) would behave under load, try HammerOra. I love that tool.
    http://hammerora.sourceforge.net/

  • OWB10gR2 process parameter error

    Hi,
    I have OWB 10gR2 with 2.6.4 Workflow on a 10gR2 database. I create a process flow in owb with a process parameter. The process contains a mapping with an input parameter. I bind the process parameter to the mapping parameter.
    When I deploy the mapping to workflow I see that the mapping and process parameters are not deployed to workflow (wf_activity_attributes). And when I run the process from the control center manager and give a value to the process parameter this value does not appear in the runtime either (all_rt_audit_execution_params).
    It works fine with OWB 9.2 and 10.1.0.4 as well.
    Does anybody have an idea about this problem? What have been changed in R2 OWB in this territory? And how this problem can be solved?
    Thanks,
    Gabor

    could you elaborate a little bit on that?
    I have some issues with all my Process flows, after migrating from 10.1.0.4 to OWB10gR2.
    When I try to generate the PF packages it fails with internal error:
    oracle.wh.service.sdk.runtime.QueryException: null
    - Internal Error Unknown System Parameter PARAM0 for executionAdapterId= 5 executionOperatorId= 1080
    I can not delete this parameter from the process flow (the delete option is disabled when I click on in), and it doesn't complain about another parameter, PARAM, that I created after the migration.

  • Should i increase PGA when PROCESS parameter is increased?

    DB version:10gR2
    Currently our PROCESSes parameter is set to 500 and PGA_AGGREGATE_TARGET set to 700mb. We are going to increase init.ora parameter PROCESSES to 1000. Should i be increasing PGA_GGREGATE_TARGET as well?

    user659394 wrote:
    DB version:10gR2
    Currently our PROCESSes parameter is set to 500 and PGA_AGGREGATE_TARGET set to 700mb. We are going to increase init.ora parameter PROCESSES to 1000. Should i be increasing PGA_GGREGATE_TARGET as well?
    Probably - but where are you going to get that memory from ?
    When you set pga_aggregate_target, you are saying two things to Oracle. One viewpoint is that you are saying to that on average each process needs about N MB of memory (in your case about 1.4MB, which is a reasonable type of figure for an OLTP system). The alternative viewpoint is that you are saying to Oracle - ater startup and all other activity, this is the amount of memory available for Oracle processes so please ration it carefully.
    If your viewpoint is the former, you need to set your pga_aggregate_target to something getting on for twice your current value. If your viewpoint is the latter, you can't change the pga_aggregate_target unless you get some more memory from somewhere else (e.g. the db_cache_size, or shared_pool_size).
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    "The temptation to form premature theories upon insufficient data is the bane of our profession."
    Sherlock Holmes (Sir Arthur Conan Doyle) in "The Valley of Fear".

  • Error while creating a new action in Oracle Process Builder 10gR3.

    Hi,
    After creating a process in Oracle Process Builder 10gR3 when I am creating a
    new action then the following exception is occuring :
    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an
    object.
    at Stellent.IBPM.Actions.ActionsToolbox.Load()
    at Stellent.IBPM.Actions.SelectActionForm.ActionModuleSelectForm_Load(Object
    sender, EventArgs e)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.ContainerControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmShowWindow(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
    wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1891 (QFEN-1.050727-1800)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ActionLoader
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/ActionLoader/1.0.0.0__3fc10cde1afe6713/Acti\
    onLoader.dll
    BomInterop
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase: file:///D:/Program%20Files/Stellent/IBPM/BomInterop.DLL
    Stellent.IBPM.Builder
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Stellent.IBPM.Builder/1.0.0.0__3fc10cde1afe\
    6713/Stellent.IBPM.Builder.dll
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy\
    stem.Drawing.dll
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Stellent.IBPM.Actions
    Assembly Version: 1.0.0.0
    Win32 Version: 8.0.0.382
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Stellent.IBPM.Actions/1.0.0.0__3fc10cde1afe\
    6713/Stellent.IBPM.Actions.dll
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1891 (QFEN-1.050727-1800)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e\
    089/System.Windows.Forms.dll
    Infragistics2.Win.UltraWinTabControl.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.UltraWinTabControl.v6.2/6\
    .2.20062.34__7dd5c3163f2cd0cb/Infragistics2.Win.UltraWinTabControl.v6.2.dll
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50\
    a3a/System.Configuration.dll
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System\
    .Xml.dll
    Infragistics2.Win.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.v6.2/6.2.20062.34__7dd5c3\
    163f2cd0cb/Infragistics2.Win.v6.2.dll
    Infragistics2.Shared.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Shared.v6.2/6.2.20062.34__7dd\
    5c3163f2cd0cb/Infragistics2.Shared.v6.2.dll
    Infragistics2.Win.Misc.v6.2
    Assembly Version: 6.2.20062.34
    Win32 Version: 6.2.20062.34
    CodeBase:
    file:///C:/WINDOWS/assembly/GAC_MSIL/Infragistics2.Win.Misc.v6.2/6.2.20062.34__7\
    dd5c3163f2cd0cb/Infragistics2.Win.Misc.v6.2.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Hi Deena,
    This error:
    "[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
    javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
    is known issue
    Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
    You need to apply that patch.
    I hope this helps,
    Thiago Leoncio.

  • How to fetch oracle process id from a stored procedure.

    Hi,
    I want to fetch the oracle process id from within a stored procedure.
    I know that the one way to do this is using the v$process view. But, a grant has to be given to the user on this table. Due to the strict policies at my workplace, I do not have the permission to do this, nor can i ask anyone to give the grant. But, i need the oracle pid very much.
    Is there an alternate way to get the oracle process id from within the stored procedure (without using the v$process view, like we have sys_context() to fetch session id without using v$session) ?
    Any help would be appreciated.
    Thanks,
    AP

    Hi,
    The point is i do not want to use v$process ( or v_$process) ,because i can not give the select grant to the user on this view. ( As i need to fetch it from a stored procedure, not from the SQL prompt).
    Rahul , your query is correct. It fetches the values ( though i needed oracle process id not unix pid ; i would get it through p.pid), but i need an alternate approach to this.
    Is there an alternate approach which would enable me to fetch the oracle process id ( without using any of the V$ - system views) ? Does Oracle has such a feature /approach ?
    -AP

Maybe you are looking for