Oracle 10gReport POOL Size/Cache

Could anybody tell me how to increase the Report server pool/cache size.
I am getting cache error.

Hi,
You have not mentioned the Application Server version. Assuming it is 10.1.2.0.2, you can find extensive information about Tuning Oracle Reports in the Oracle Application Server Reports Services Publishing Reports to the Web
10g Release 2 (10.1.2) ( B14048-01 ) - Chapter 20 :-
http://download-west.oracle.com/docs/cd/B14099_18/bi.1012/b14048/pbr_tune.htm#i1006609
Regards,
Sandeep

Similar Messages

Issue with shared pool size while upgrading from 10.2.0.4 to 11.2.0.2

Hi Team,
Below is my issue
I am running dbua as part of the upgrade from 10.2.0.4 to 11.2.0.2. Its almost 59% and nothing is happening on the instance. The logs directory contian the below
-bash-3.00$ ls -ltr
total 280
-rw-r----- 1 ora8014 ems8014 3662 Oct 16 08:58 upgrade.xml
-rw-r----- 1 ora8014 ems8014 1127 Oct 16 09:00 Upgrade_Directive.log
-rw-r----- 1 ora8014 ems8014 7452 Oct 16 09:00 mapfile.txt
-rw-r----- 1 ora8014 ems8014 297 Oct 16 09:04 SpaceUsage.txt
-rw-r----- 1 ora8014 ems8014 9803 Oct 16 09:04 PreUpgradeResults.html
-rw-r----- 1 ora8014 ems8014 1572 Oct 16 09:06 PreUpgrade.log
-rw-r----- 1 ora8014 ems8014 2850 Oct 16 09:06 Oracle_Text.log
-rw-r----- 1 ora8014 ems8014 157816 Oct 16 09:09 trace.log
-rw-r----- 1 ora8014 ems8014 71368 Oct 16 09:09 sqls.log
-rw-r----- 1 ora8014 ems8014 339 Oct 16 09:09 Oracle_Server.log
-bash-3.00$ date
Sat Oct 16 22:54:27 PDT 2010
-bash-3.00$ pwd
/slot/ems8014/oracle/app/ora8014/cfgtoollogs/dbua/ebs11i10/upgrade1
It seems its almost more 12 hrs nothing has happened. When I check the oracle_server.log it has the error
-bash-3.00$ tail Oracle_Server.log
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
select count(*) from v$instance
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
ORA-00371: not enough shared pool memory, should be atleast 424463564 bytes
Hence I started the Db in 10g oracle home to check and below is the details.
SQL> select * from V$SGAINFO;
NAME BYTES RES
Fixed SGA Size 1267908 No
Redo Buffers 11313152 No
Buffer Cache Size 614400000 Yes
Shared Pool Size 301989888 Yes
Large Pool Size 8388608 Yes
Java Pool Size 67108864 Yes
Streams Pool Size 50331648 Yes
Granule Size 4194304 No
Maximum SGA Size 1056964608 No
Startup overhead in Shared Pool 188743680 No
Free SGA Memory Available 0
11 rows selected.
I tried to increase the space of shared pool as below
SQL> ALTER SYSTEM SET shared_pool_size ='301M' SCOPE=MEMORY SID='ebs11i10';
ALTER SYSTEM SET shared_pool_size ='301M' SCOPE=MEMORY SID='ebs11i10'
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-04033: Insufficient memory to grow pool
I am stuck and cant proceed further. Could you please help me on this issue so that I overcome this and proceed further.
Thanks
Shyam.

These are the logs. Could you please let me know which one you want.
-bash-3.00$ pwd
/slot/ems8014/oracle/app/ora8014/cfgtoollogs/dbua/ebs11i10/upgrade1
-bash-3.00$ ls -ltr
total 280
-rw-r----- 1 ora8014 ems8014 3662 Oct 16 08:58 upgrade.xml
-rw-r----- 1 ora8014 ems8014 1127 Oct 16 09:00 Upgrade_Directive.log
-rw-r----- 1 ora8014 ems8014 7452 Oct 16 09:00 mapfile.txt
-rw-r----- 1 ora8014 ems8014 297 Oct 16 09:04 SpaceUsage.txt
-rw-r----- 1 ora8014 ems8014 9803 Oct 16 09:04 PreUpgradeResults.html
-rw-r----- 1 ora8014 ems8014 1572 Oct 16 09:06 PreUpgrade.log
-rw-r----- 1 ora8014 ems8014 2850 Oct 16 09:06 Oracle_Text.log
-rw-r----- 1 ora8014 ems8014 157816 Oct 16 09:09 trace.log
-rw-r----- 1 ora8014 ems8014 71368 Oct 16 09:09 sqls.log
-rw-r----- 1 ora8014 ems8014 339 Oct 16 09:09 Oracle_Server.log

How to set the correct shared pool size and db_buffer_cache using awr

Hi All,
I want to how to set the correct size for shared_pool_size and db_cache_size using shared pool advisory and buffer pool advisory of awr report. I have paste the shared and buffer pool advisory of awr report.
Shared Pool Advisory
* SP: Shared Pool Est LC: Estimated Library Cache Factr: Factor
* Note there is often a 1:Many correlation between a single logical object in the Library Cache, and the physical number of memory objects associated with it. Therefore comparing the number of Lib Cache objects (e.g. in v$librarycache), with the number of Lib Cache Memory Objects is invalid.
Shared Pool Size(M)     SP Size Factr     Est LC Size (M)     Est LC Mem Obj     Est LC Time Saved (s)     Est LC Time Saved Factr     Est LC Load Time (s)     Est LC Load Time Factr     Est LC Mem Obj Hits (K)
4,096     1.00     471     25,153     184,206     1.00     149     1.00     9,069
4,736     1.16     511     27,328     184,206     1.00     149     1.00     9,766
5,248     1.28     511     27,346     184,206     1.00     149     1.00     9,766
5,760     1.41     511     27,346     184,206     1.00     149     1.00     9,766
6,272     1.53     511     27,346     184,206     1.00     149     1.00     9,766
6,784     1.66     511     27,346     184,206     1.00     149     1.00     9,766
7,296     1.78     511     27,346     184,206     1.00     149     1.00     9,766
7,808     1.91     511     27,346     184,206     1.00     149     1.00     9,766
8,320     2.03     511     27,346     184,206     1.00     149     1.00     9,766
Buffer Pool Advisory
* Only rows with estimated physical reads >0 are displayed
* ordered by Block Size, Buffers For Estimate
P     Size for Est (M)     Size Factor     Buffers (thousands)     Est Phys Read Factor     Estimated Phys Reads (thousands)     Est Phys Read Time     Est %DBtime for Rds
D     4,096     0.10     485     1.02     1,002     1     0.00
D     8,192     0.20     970     1.00     987     1     0.00
D     12,288     0.30     1,454     1.00     987     1     0.00
D     16,384     0.40     1,939     1.00     987     1     0.00
D     20,480     0.50     2,424     1.00     987     1     0.00
D     24,576     0.60     2,909     1.00     987     1     0.00
D     28,672     0.70     3,394     1.00     987     1     0.00
D     32,768     0.80     3,878     1.00     987     1     0.00
D     36,864     0.90     4,363     1.00     987     1     0.00
D     40,960     1.00     4,848     1.00     987     1     0.00
D     45,056     1.10     5,333     1.00     987     1     0.00
D     49,152     1.20     5,818     1.00     987     1     0.00
D     53,248     1.30     6,302     1.00     987     1     0.00
D     57,344     1.40     6,787     1.00     987     1     0.00
D     61,440     1.50     7,272     1.00     987     1     0.00
D     65,536     1.60     7,757     1.00     987     1     0.00
D     69,632     1.70     8,242     1.00     987     1     0.00
D     73,728     1.80     8,726     1.00     987     1     0.00
D     77,824     1.90     9,211     1.00     987     1     0.00
D     81,920     2.00     9,696     1.00     987     1     0.00
My shared pool size is 4gb and db_cache_size is 40Gb.
Please help me in configuring the correct size for this.
Thanks and Regards,

Hi ,
Actually batch load is taking too much time.
Please find below the 1 hr awr report
     Snap Id     Snap Time     Sessions     Cursors/Session
Begin Snap:     6557     27-Nov-11 16:00:06     126     1.3
End Snap:     6558     27-Nov-11 17:00:17     130     1.6
Elapsed:          60.17 (mins)
DB Time:          34.00 (mins)
Report Summary
Cache Sizes
     Begin     End
Buffer Cache:     40,960M     40,960M     Std Block Size:     8K
Shared Pool Size:     4,096M     4,096M     Log Buffer:     25,908K
Load Profile
     Per Second     Per Transaction     Per Exec     Per Call
DB Time(s):     0.6     1.4     0.00     0.07
DB CPU(s):     0.5     1.2     0.00     0.06
Redo size:     281,296.9     698,483.4
Logical reads:     20,545.6     51,016.4
Block changes:     1,879.5     4,667.0
Physical reads:     123.7     307.2
Physical writes:     66.4     164.8
User calls:     8.2     20.4
Parses:     309.4     768.4
Hard parses:     8.5     21.2
W/A MB processed:     1.7     4.3
Logons:     0.7     1.6
Executes:     1,235.9     3,068.7
Rollbacks:     0.0     0.0
Transactions:     0.4
Instance Efficiency Percentages (Target 100%)
Buffer Nowait %:     100.00     Redo NoWait %:     100.00
Buffer Hit %:     99.66     In-memory Sort %:     100.00
Library Hit %:     99.19     Soft Parse %:     97.25
Execute to Parse %:     74.96     Latch Hit %:     99.97
Parse CPU to Parse Elapsd %:     92.41     % Non-Parse CPU:     98.65
Shared Pool Statistics
     Begin     End
Memory Usage %:     80.33     82.01
% SQL with executions>1:     90.90     86.48
% Memory for SQL w/exec>1:     90.10     86.89
Top 5 Timed Foreground Events
Event     Waits     Time(s)     Avg wait (ms)     % DB time     Wait Class
DB CPU          1,789          87.72
db file sequential read     27,531     50     2     2.45     User I/O
db file scattered read     26,322     30     1     1.47     User I/O
row cache lock     1,798     20     11     0.96     Concurrency
OJVM: Generic     36     15     421     0.74     Other
Host CPU (CPUs: 24 Cores: 12 Sockets: )
Load Average Begin     Load Average End     %User     %System     %WIO     %Idle
0.58     1.50     2.8     0.7     0.1     96.6
Instance CPU
%Total CPU     %Busy CPU     %DB time waiting for CPU (Resource Manager)
2.2     63.6     0.0
Memory Statistics
     Begin     End
Host Mem (MB):     131,072.0     131,072.0
SGA use (MB):     50,971.4     50,971.4
PGA use (MB):     545.5     1,066.3
% Host Mem used for SGA+PGA:     39.30     39.70
RAC Statistics
     Begin     End
Number of Instances:     2     2
Global Cache Load Profile
     Per Second     Per Transaction
Global Cache blocks received:     3.09     7.68
Global Cache blocks served:     1.86     4.62
GCS/GES messages received:     78.64     195.27
GCS/GES messages sent:     53.82     133.65
DBWR Fusion writes:     0.52     1.30
Estd Interconnect traffic (KB)     65.50
Global Cache Efficiency Percentages (Target local+remote 100%)
Buffer access - local cache %:     99.65
Buffer access - remote cache %:     0.02
Buffer access - disk %:     0.34
Global Cache and Enqueue Services - Workload Characteristics
Avg global enqueue get time (ms):     0.0
Avg global cache cr block receive time (ms):     1.7
Avg global cache current block receive time (ms):     1.0
Avg global cache cr block build time (ms):     0.0
Avg global cache cr block send time (ms):     0.0
Global cache log flushes for cr blocks served %:     1.4
Avg global cache cr block flush time (ms):     0.9
Avg global cache current block pin time (ms):     0.0
Avg global cache current block send time (ms):     0.0
Global cache log flushes for current blocks served %:     0.1
Avg global cache current block flush time (ms):     0.0
Global Cache and Enqueue Services - Messaging Statistics
Avg message sent queue time (ms):     0.0
Avg message sent queue time on ksxp (ms):     0.4
Avg message received queue time (ms):     0.5
Avg GCS message process time (ms):     0.0
Avg GES message process time (ms):     0.0
% of direct sent messages:     79.13
% of indirect sent messages:     17.10
% of flow controlled messages:     3.77
Cluster Interconnect
     Begin      End
Interface     IP Address     Pub     Source     IP     Pub     Src
en9     10.51.10.61     N     Oracle Cluster Repository
Main Report
* Report Summary
* Wait Events Statistics
* SQL Statistics
* Instance Activity Statistics
* IO Stats
* Buffer Pool Statistics
* Advisory Statistics
* Wait Statistics
* Undo Statistics
* Latch Statistics
* Segment Statistics
* Dictionary Cache Statistics
* Library Cache Statistics
* Memory Statistics
* Streams Statistics
* Resource Limit Statistics
* Shared Server Statistics
* init.ora Parameters
More RAC Statistics
* RAC Report Summary
* Global Messaging Statistics
* Global CR Served Stats
* Global CURRENT Served Stats
* Global Cache Transfer Stats
* Interconnect Stats
* Dynamic Remastering Statistics
Back to Top
Statistic Name     Time (s)     % of DB Time
sql execute elapsed time     1,925.20     94.38
DB CPU     1,789.38     87.72
connection management call elapsed time     99.65     4.89
PL/SQL execution elapsed time     89.81     4.40
parse time elapsed     46.32     2.27
hard parse elapsed time     25.01     1.23
Java execution elapsed time     21.24     1.04
PL/SQL compilation elapsed time     11.92     0.58
failed parse elapsed time     9.37     0.46
hard parse (sharing criteria) elapsed time     8.71     0.43
sequence load elapsed time     0.06     0.00
repeated bind elapsed time     0.02     0.00
hard parse (bind mismatch) elapsed time     0.01     0.00
DB time     2,039.77
background elapsed time     122.00
background cpu time     113.42
Statistic     Value     End Value
NUM_LCPUS     0
NUM_VCPUS     0
AVG_BUSY_TIME     12,339
AVG_IDLE_TIME     348,838
AVG_IOWAIT_TIME     221
AVG_SYS_TIME     2,274
AVG_USER_TIME     9,944
BUSY_TIME     299,090
IDLE_TIME     8,375,051
IOWAIT_TIME     6,820
SYS_TIME     57,512
USER_TIME     241,578
LOAD     1     2
OS_CPU_WAIT_TIME     312,200
PHYSICAL_MEMORY_BYTES     137,438,953,472
NUM_CPUS     24
NUM_CPU_CORES     12
GLOBAL_RECEIVE_SIZE_MAX     1,310,720
GLOBAL_SEND_SIZE_MAX     1,310,720
TCP_RECEIVE_SIZE_DEFAULT     16,384
TCP_RECEIVE_SIZE_MAX     9,223,372,036,854,775,807
TCP_RECEIVE_SIZE_MIN     4,096
TCP_SEND_SIZE_DEFAULT     16,384
TCP_SEND_SIZE_MAX     9,223,372,036,854,775,807
TCP_SEND_SIZE_MIN     4,096
Back to Wait Events Statistics
Back to Top
Operating System Statistics - Detail
Snap Time     Load     %busy     %user     %sys     %idle     %iowait
27-Nov 16:00:06     0.58
27-Nov 17:00:17     1.50     3.45     2.79     0.66     96.55     0.08
Back to Wait Events Statistics
Back to Top
Foreground Wait Class
* s - second, ms - millisecond - 1000th of a second
* ordered by wait time desc, waits desc
* %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
* Captured Time accounts for 95.7% of Total DB time 2,039.77 (s)
* Total FG Wait Time: 163.14 (s) DB CPU time: 1,789.38 (s)
Wait Class     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     %DB time
DB CPU               1,789          87.72
User I/O     61,229     0     92     1     4.49
Other     102,743     40     31     0     1.50
Concurrency     3,169     10     24     7     1.16
Cluster     58,920     0     11     0     0.52
System I/O     45,407     0     6     0     0.29
Configuration     107     7     1     5     0.03
Commit     383     0     0     1     0.01
Network     15,275     0     0     0     0.00
Application     52     8     0     0     0.00
Back to Wait Events Statistics
Back to Top
Foreground Wait Events
* s - second, ms - millisecond - 1000th of a second
* Only events with Total Wait Time (s) >= .001 are shown
* ordered by wait time desc, waits desc (idle events last)
* %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     Waits /txn     % DB time
db file sequential read     27,531     0     50     2     18.93     2.45
db file scattered read     26,322     0     30     1     18.10     1.47
row cache lock     1,798     0     20     11     1.24     0.96
OJVM: Generic     36     42     15     421     0.02     0.74
db file parallel read     394     0     7     19     0.27     0.36
control file sequential read     22,248     0     6     0     15.30     0.28
reliable message     4,439     0     4     1     3.05     0.18
gc current grant busy     7,597     0     3     0     5.22     0.16
PX Deq: Slave Session Stats     2,661     0     3     1     1.83     0.16
DFS lock handle     3,208     0     3     1     2.21     0.16
direct path write temp     4,842     0     3     1     3.33     0.15
library cache load lock     39     0     3     72     0.03     0.14
gc cr multi block request     37,008     0     3     0     25.45     0.14
IPC send completion sync     5,451     0     2     0     3.75     0.10
gc cr block 2-way     4,669     0     2     0     3.21     0.09
enq: PS - contention     3,183     33     1     0     2.19     0.06
gc cr grant 2-way     5,151     0     1     0     3.54     0.06
direct path read temp     1,722     0     1     1     1.18     0.05
gc current block 2-way     1,807     0     1     0     1.24     0.03
os thread startup     6     0     1     108     0.00     0.03
name-service call wait     12     0     1     47     0.01     0.03
PX Deq: Signal ACK RSG     2,046     50     0     0     1.41     0.02
log file switch completion     3     0     0     149     0.00     0.02
rdbms ipc reply     3,610     0     0     0     2.48     0.02
gc current grant 2-way     1,432     0     0     0     0.98     0.02
library cache pin     903     32     0     0     0.62     0.02
PX Deq: reap credit     35,815     100     0     0     24.63     0.01
log file sync     383     0     0     1     0.26     0.01
Disk file operations I/O     405     0     0     0     0.28     0.01
library cache lock     418     3     0     0     0.29     0.01
kfk: async disk IO     23,159     0     0     0     15.93     0.01
gc current block busy     4     0     0     35     0.00     0.01
gc current multi block request     1,206     0     0     0     0.83     0.01
ges message buffer allocation     38,526     0     0     0     26.50     0.00
enq: FB - contention     131     0     0     0     0.09     0.00
undo segment extension     8     100     0     6     0.01     0.00
CSS initialization     8     0     0     6     0.01     0.00
SQL*Net message to client     14,600     0     0     0     10.04     0.00
enq: HW - contention     96     0     0     0     0.07     0.00
CSS operation: action     8     0     0     4     0.01     0.00
gc cr block busy     33     0     0     1     0.02     0.00
latch free     30     0     0     1     0.02     0.00
enq: TM - contention     49     6     0     0     0.03     0.00
enq: JQ - contention     19     100     0     1     0.01     0.00
SQL*Net more data to client     666     0     0     0     0.46     0.00
asynch descriptor resize     3,179     100     0     0     2.19     0.00
latch: shared pool     3     0     0     3     0.00     0.00
CSS operation: query     24     0     0     0     0.02     0.00
PX Deq: Signal ACK EXT     72     0     0     0     0.05     0.00
KJC: Wait for msg sends to complete     269     0     0     0     0.19     0.00
latch: object queue header operation     4     0     0     1     0.00     0.00
gc cr block congested     5     0     0     0     0.00     0.00
utl_file I/O     11     0     0     0     0.01     0.00
enq: TO - contention     3     33     0     0     0.00     0.00
SQL*Net message from client     14,600     0     219,478     15033     10.04
jobq slave wait     7,726     100     3,856     499     5.31
PX Deq: Execution Msg     10,556     19     50     5     7.26
PX Deq: Execute Reply     2,946     31     27     9     2.03
PX Deq: Parse Reply     3,157     35     3     1     2.17
PX Deq: Join ACK     2,976     28     2     1     2.05
PX Deq Credit: send blkd     7     14     0     4     0.00
Back to Wait Events Statistics
Back to Top
Background Wait Events
* ordered by wait time desc, waits desc (idle events last)
* Only events with Total Wait Time (s) >= .001 are shown
* %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     Waits /txn     % bg time
os thread startup     140     0     13     90     0.10     10.35
db file parallel write     8,233     0     6     1     5.66     5.08
log file parallel write     3,906     0     6     1     2.69     4.62
log file sequential read     350     0     5     16     0.24     4.49
control file sequential read     13,737     0     5     0     9.45     3.72
DFS lock handle     2,990     27     2     1     2.06     1.43
db file sequential read     921     0     2     2     0.63     1.39
SQL*Net break/reset to client     18     0     1     81     0.01     1.19
control file parallel write     2,455     0     1     1     1.69     1.12
ges lms sync during dynamic remastering and reconfig     24     100     1     50     0.02     0.98
library cache load lock     35     0     1     24     0.02     0.68
ASM file metadata operation     3,483     0     1     0     2.40     0.65
enq: CO - master slave det     1,203     100     1     0     0.83     0.46
kjbdrmcvtq lmon drm quiesce: ping completion     9     0     1     62     0.01     0.46
enq: WF - contention     11     0     0     35     0.01     0.31
CGS wait for IPC msg     32,702     100     0     0     22.49     0.19
gc object scan     28,788     100     0     0     19.80     0.15
row cache lock     535     0     0     0     0.37     0.14
library cache pin     370     55     0     0     0.25     0.12
ksxr poll remote instances     19,119     100     0     0     13.15     0.11
name-service call wait     6     0     0     19     0.00     0.10
gc current block 2-way     304     0     0     0     0.21     0.09
gc cr block 2-way     267     0     0     0     0.18     0.08
gc cr grant 2-way     355     0     0     0     0.24     0.08
ges LMON to get to FTDONE     3     100     0     24     0.00     0.06
enq: CF - contention     145     76     0     0     0.10     0.05
PX Deq: reap credit     8,842     100     0     0     6.08     0.05
reliable message     126     0     0     0     0.09     0.05
db file scattered read     19     0     0     3     0.01     0.05
library cache lock     162     1     0     0     0.11     0.04
latch: shared pool     2     0     0     27     0.00     0.04
Disk file operations I/O     504     0     0     0     0.35     0.04
gc current grant busy     148     0     0     0     0.10     0.04
gcs log flush sync     84     0     0     1     0.06     0.04
ges message buffer allocation     24,934     0     0     0     17.15     0.02
enq: CR - block range reuse ckpt     83     0     0     0     0.06     0.02
latch free     22     0     0     1     0.02     0.02
CSS operation: action     13     0     0     2     0.01     0.02
CSS initialization     4     0     0     6     0.00     0.02
direct path read     1     0     0     21     0.00     0.02
rdbms ipc reply     153     0     0     0     0.11     0.01
db file parallel read     2     0     0     8     0.00     0.01
direct path write     5     0     0     3     0.00     0.01
gc current multi block request     49     0     0     0     0.03     0.01
gc current block busy     5     0     0     2     0.00     0.01
enq: PS - contention     24     50     0     0     0.02     0.01
gc cr multi block request     54     0     0     0     0.04     0.01
ges generic event     1     100     0     10     0.00     0.01
gc current grant 2-way     35     0     0     0     0.02     0.01
kfk: async disk IO     183     0     0     0     0.13     0.01
Log archive I/O     3     0     0     2     0.00     0.01
gc buffer busy acquire     2     0     0     3     0.00     0.00
LGWR wait for redo copy     123     0     0     0     0.08     0.00
IPC send completion sync     18     0     0     0     0.01     0.00
enq: TA - contention     11     0     0     0     0.01     0.00
read by other session     2     0     0     2     0.00     0.00
enq: TM - contention     9     89     0     0     0.01     0.00
latch: ges resource hash list     135     0     0     0     0.09     0.00
PX Deq: Slave Session Stats     12     0     0     0     0.01     0.00
KJC: Wait for msg sends to complete     89     0     0     0     0.06     0.00
enq: TD - KTF dump entries     8     0     0     0     0.01     0.00
enq: US - contention     7     0     0     0     0.00     0.00
CSS operation: query     12     0     0     0     0.01     0.00
enq: TK - Auto Task Serialization     6     100     0     0     0.00     0.00
PX Deq: Signal ACK RSG     24     50     0     0     0.02     0.00
log file single write     6     0     0     0     0.00     0.00
enq: WL - contention     2     100     0     1     0.00     0.00
ADR block file read     13     0     0     0     0.01     0.00
ADR block file write     5     0     0     0     0.00     0.00
latch: object queue header operation     1     0     0     1     0.00     0.00
gc cr block busy     1     0     0     1     0.00     0.00
rdbms ipc message     103,276     67     126,259     1223     71.03
PX Idle Wait     6,467     67     12,719     1967     4.45
wait for unread message on broadcast channel     7,240     100     7,221     997     4.98
gcs remote message     218,809     84     7,213     33     150.49
DIAG idle wait     203,228     95     7,185     35     139.77
shared server idle wait     121     100     3,630     30000     0.08
ASM background timer     3,343     0     3,611     1080     2.30
Space Manager: slave idle wait     723     100     3,610     4993     0.50
heartbeat monitor sleep     722     100     3,610     5000     0.50
ges remote message     73,089     52     3,609     49     50.27
dispatcher timer     66     88     3,608     54660     0.05
pmon timer     1,474     82     3,607     2447     1.01
PING     1,487     19     3,607     2426     1.02
Streams AQ: qmn slave idle wait     125     0     3,594     28754     0.09
Streams AQ: qmn coordinator idle wait     250     50     3,594     14377     0.17
smon timer     18     50     3,505     194740     0.01
JOX Jit Process Sleep     73     100     976     13370     0.05
class slave wait     56     0     605     10806     0.04
KSV master wait     2,215     98     1     0     1.52
SQL*Net message from client     109     0     0     2     0.07
PX Deq: Parse Reply     27     44     0     1     0.02
PX Deq: Join ACK     30     40     0     1     0.02
PX Deq: Execute Reply     20     30     0     0     0.01
Streams AQ: RAC qmn coordinator idle wait     259     100     0     0     0.18
Back to Wait Events Statistics
Back to Top
Wait Event Histogram
* Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
* % of Waits: value of .0 indicates value was <.05%; value of null is truly 0
* % of Waits: column heading of <=1s is truly <1024ms, >1s is truly >=1024ms
* Ordered by Event (idle events last)
          % of Waits
Event     Total Waits     <1ms     <2ms     <4ms     <8ms     <16ms     <32ms     <=1s     >1s
ADR block file read     13     100.0
ADR block file write     5     100.0
ADR file lock     6     100.0
ARCH wait for archivelog lock     3     100.0
ASM file metadata operation     3483     99.6     .1     .1                    .2
CGS wait for IPC msg     32.7K     100.0
CSS initialization     12     50.0                    50.0
CSS operation: action     21     28.6     9.5          61.9
CSS operation: query     36     86.1     5.6     8.3
DFS lock handle     6198     98.6     1.2     .1                    .1
Disk file operations I/O     909     95.7     3.6     .7
IPC send completion sync     5469     99.9     .1     .0     .0
KJC: Wait for msg sends to complete     313     100.0
LGWR wait for redo copy     122     100.0
Log archive I/O     3     66.7               33.3
OJVM: Generic     36     55.6                              44.4
PX Deq: Signal ACK EXT     72     98.6     1.4
PX Deq: Signal ACK RSG     2070     99.7               .0     .1     .0     .1
PX Deq: Slave Session Stats     2673     99.7     .2                         .1     .0
PX Deq: reap credit     44.7K     100.0
SQL*Net break/reset to client     20     95.0                                   5.0
SQL*Net message to client     14.7K     100.0
SQL*Net more data from client     32     100.0
SQL*Net more data to client     689     100.0
asynch descriptor resize     3387     100.0
buffer busy waits     2     100.0
control file parallel write     2455     96.6     2.2     .6     .6          .1
control file sequential read     36K     99.4     .3     .1     .1     .1     .1     .0
db file parallel read     397     8.8     .8     5.5     12.6     17.4     46.3     8.6
db file parallel write     8233     85.4     10.3     2.3     1.4     .4     .1
db file scattered read     26.3K     79.2     1.5     8.2     10.5     .6     .1     .0
db file sequential read     28.4K     60.2     3.3     18.0     18.1     .3     .1     .0
db file single write     2     100.0
direct path read     2     50.0                         50.0
direct path read temp     1722     95.8     2.8     .1     .5     .8     .1
direct path write     6     83.3                    16.7
direct path write temp     4842     96.3     2.7     .5     .2     .0     .0     .2
enq: AF - task serialization     1     100.0
enq: CF - contention     145     99.3     .7
enq: CO - master slave det     1203     98.9     .8     .2
enq: CR - block range reuse ckpt     83     100.0
enq: DR - contention     2     100.0
enq: FB - contention     131     100.0
enq: HW - contention     97     100.0
enq: JQ - contention     19     89.5     10.5
enq: JS - job run lock - synchronize     3     100.0
enq: MD - contention     1     100.0
enq: MW - contention     2     100.0
enq: PS - contention     3207     99.5     .4     .1
enq: TA - contention     11     100.0
enq: TD - KTF dump entries     8     100.0
enq: TK - Auto Task Serialization     6     100.0
enq: TM - contention     58     100.0
enq: TO - contention     3     100.0
enq: TQ - DDL contention     1     100.0
enq: TS - contention     1     100.0
enq: UL - contention     1     100.0
enq: US - contention     7     100.0
enq: WF - contention     11     81.8                              18.2
enq: WL - contention     2     50.0     50.0
gc buffer busy acquire     2     50.0               50.0
gc cr block 2-way     4934     99.9     .1                    .0     .0
gc cr block busy     35     68.6     31.4
gc cr block congested     6     100.0
gc cr disk read     2     100.0
gc cr grant 2-way     4824     100.0     .0
gc cr grant congested     2     100.0
gc cr multi block request     37.1K     99.8     .2     .0     .0     .0     .0     .0
gc current block 2-way     2134     99.9     .0                         .0
gc current block busy     7     14.3     14.3          14.3          28.6     28.6
gc current block congested     2     100.0
gc current grant 2-way     1337     99.9     .1
gc current grant busy     7123     99.2     .2     .2     .0     .0     .3     .1
gc current grant congested     2     100.0
gc current multi block request     1260     99.8     .2
gc object scan     28.8K     100.0
gcs log flush sync     65     95.4          3.1     1.5
ges LMON to get to FTDONE     3                              100.0
ges generic event     1                         100.0
ges inquiry response     2     100.0
ges lms sync during dynamic remastering and reconfig     24                         16.7     29.2     54.2
ges message buffer allocation     63.1K     100.0
kfk: async disk IO     23.3K     100.0     .0     .0
kjbdrmcvtq lmon drm quiesce: ping completion     9     11.1                              88.9
ksxr poll remote instances     19.1K     100.0
latch free     52     59.6     40.4
latch: call allocation     2     100.0
latch: gc element     1     100.0
latch: gcs resource hash     1     100.0
latch: ges resource hash list     135     100.0
latch: object queue header operation     5     40.0     40.0     20.0
latch: shared pool     5     40.0                    20.0     20.0     20.0
library cache load lock     74     9.5     5.4     8.1     17.6     10.8     13.5     35.1
library cache lock     493     99.2     .4     .4
library cache pin     1186     98.4     .3     1.2     .1
library cache: mutex X     6     100.0
log file parallel write     3897     72.9     1.5     17.1     7.5     .6     .3     .1
log file sequential read     350     4.6               3.1     59.4     30.0     2.9
log file single write     6     100.0
log file switch completion     3                         33.3          66.7
log file sync     385     90.4     3.6     4.7     .8     .5
name-service call wait     18          5.6     5.6     5.6     16.7     44.4     22.2
os thread startup     146                                   100.0
rdbms ipc reply     3763     99.7     .3
read by other session     2     50.0          50.0
reliable message     4565     99.7     .2     .0               .0     .1
row cache lock     2334     99.3     .2     .1                    .1     .3
undo segment extension     8     50.0                    37.5     12.5
utl_file I/O     11     100.0
ASM background timer     3343     57.0     .3     .1     .1     .1          21.1     21.4
DIAG idle wait     203.2K     3.4     .2     .4     18.0     41.4     14.8     21.8
JOX Jit Process Sleep     73                                   2.7     97.3
KSV master wait     2213     99.4     .1     .2                    .3
PING     1487     81.0                                   19.0
PX Deq Credit: send blkd     7     57.1          14.3     14.3          14.3
PX Deq: Execute Reply     2966     59.8     .8     9.5     5.6     10.2     2.6     11.4
PX Deq: Execution Msg     10.6K     72.4     12.1     2.6     2.5     .1     5.6     4.6     .0
PX Deq: Join ACK     3006     77.9     22.1     .1
PX Deq: Parse Reply     3184     67.1     31.1     1.6     .2
PX Idle Wait     6466     .2     8.7     4.3     4.8     .3     .1     5.0     76.6
SQL*Net message from client     14.7K     72.4     2.8     .8     .5     .9     .4     2.8     19.3
Space Manager: slave idle wait     722                                        100.0
Streams AQ: RAC qmn coordinator idle wait     259     100.0
Streams AQ: qmn coordinator idle wait     250     50.0                                   50.0
Streams AQ: qmn slave idle wait     125                                        100.0
class slave wait     55     67.3          7.3     1.8     5.5     1.8     7.3     9.1
dispatcher timer     66     6.1                                   93.9
gcs remote message     218.6K     7.7     1.8     1.2     1.6     1.7     15.7     70.3
ges remote message     72.9K     29.7     5.1     2.7     2.2     1.5     4.0     54.7
heartbeat monitor sleep     722                                        100.0
jobq slave wait     7725                    .1          .0     99.9
pmon timer     1474     18.4                                   81.6
rdbms ipc message     103.3K     20.7     2.7     1.5     1.3     .9     .7     40.7     31.6
shared server idle wait     121                                        100.0
smon timer     18                                        100.0
wait for unread message on broadcast channel     7238                         .3          99.7
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (64 msec to 2 sec)
* Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
* Units for % of Total Waits: ms is milliseconds s is 1024 milliseconds (approximately 1 second)
* % of Total Waits: total waits for all wait classes, including Idle
* % of Total Waits: value of .0 indicates value was <.05%; value of null is truly 0
* Ordered by Event (only non-idle events are displayed)
          % of Total Waits
Event     Waits 64ms to 2s     <32ms     <64ms     <1/8s     <1/4s     <1/2s     <1s     <2s     >=2s
ASM file metadata operation     6     99.8          .1     .1
DFS lock handle     6     99.9               .1     .0
OJVM: Generic     16     55.6               2.8          41.7
PX Deq: Signal ACK RSG     3     99.9     .0     .1
PX Deq: Slave Session Stats     3     99.9          .0               .0     .0
SQL*Net break/reset to client     1     95.0                              5.0
control file sequential read     1     100.0          .0
db file parallel read     34     91.4     8.6
db file scattered read     4     100.0     .0          .0
db file sequential read     6     100.0     .0     .0     .0
direct path write temp     11     99.8     .1     .1     .0
enq: WF - contention     2     81.8               18.2
gc cr block 2-way     1     100.0          .0
gc cr multi block request     1     100.0          .0
gc current block 2-way     1     100.0     .0
gc current block busy     2     71.4     28.6
gc current grant busy     8     99.9     .0     .1
ges lms sync during dynamic remastering and reconfig     13     45.8     20.8     33.3
kjbdrmcvtq lmon drm quiesce: ping completion     8     11.1     11.1     77.8
latch: shared pool     1     80.0     20.0
library cache load lock     26     64.9     14.9     12.2     4.1     4.1
log file parallel write     2     99.9     .0               .0
log file sequential read     10     97.1     2.0     .6     .3
log file switch completion     2     33.3               66.7
name-service call wait     4     77.8          22.2
os thread startup     146               100.0
reliable message     4     99.9          .0               .1
row cache lock     2     99.7                    .0     .0          .3
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (4 sec to 2 min)
* Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
* Units for % of Total Waits: s is 1024 milliseconds (approximately 1 second) m is 64*1024 milliseconds (approximately 67 seconds or 1.1 minutes)
* % of Total Waits: total waits for all wait classes, including Idle
* % of Total Waits: value of .0 indicates value was <.05%; value of null is truly 0
* Ordered by Event (only non-idle events are displayed)
          % of Total Waits
Event     Waits 4s to 2m     <2s     <4s     <8s     <16s     <32s     < 1m     < 2m     >=2m
row cache lock     6     99.7     .3
Back to Wait Events Statistics
Back to Top
Wait Event Histogram Detail (4 min to 1 hr)
No data exists for this section of the report.
Back to Wait Events Statistics
Back to Top
Service Statistics
* ordered by DB Time
Service Name     DB Time (s)     DB CPU (s)     Physical Reads (K)     Logical Reads (K)
ubshost     1,934     1,744     445     73,633
SYS$USERS     105     45     1     404
SYS$BACKGROUND     0     0     1     128
ubshostXDB     0     0     0     0
Back to Wait Events Statistics
Back to Top
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 seconds
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
ubshost      60232     90     2644     4     0     0     13302     0
SYS$USERS      997     2     525     19     0     0     1973     0
SYS$BACKGROUND      1456     2     1258     14     0     0     0     0
I am not able to paste the whole awr report. I have paste some of the sections of awr report.
Please help.
Thanks and Regards,

How to calculate the shared pool size ..........

Does anyone know if there is a decent algorithm/method to calculate the shared pool size in Oracle 8.1.7.

look my answer on your thread about db cache size
How to Calculate the DB Block Buffer value.

ORA-04031 on 10g - should I just adjust my SGA POOL SIZE?

Has anyone gotten this message frequently:
ORA-04031: unable to allocate 37536 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","session parame")
We are a business intelligence application that issues lots of large queries. We just migrated to 10g and we are seeing this every 2-3 days on our testing machine.
In particular, I am not sure about "sga heap"... I would just set my Shared Pool Size higher - currently 144 MB but will this help here? Thoughts?

In Oracle 10g a new feature called "automatic memory management" allows the dba to reserve a pool of shared memory that is used to allocate the shared pool, the buffer cache, the java pool and the large pool.
In general, when the database needs to allocate a large object into the shared pool and cannot find contiguous space available, it will automatically increase the shared pool size using free space from other SGA structure.
Since the space allocation is automatically managed by Oracle, the probability of getting ora-4031 errors may be greatly reduced. Automatic Memory Management is enabled when the parameter SGA_TARGET is greater than zero and the current setting can be obtained quering the v$sga_dynamic_components view.
Please refer to the 10g Administration Manual for further reference
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14231/toc.htm

Oracle shared pool fragmentation

We are running Identity Manager 7.0 using an Oracle database repository. We've been seeing shared pool fragmentation in the database resulting in various java.io.IOException: ORA-00600: internal error code messages when using bulk actions to create and remove accounts. Flushing the oracle shared pool is the only way we've found to clear these errors. Has anyone run into similar problems and found any solution other than increasing the size of the shared pool and issuing an 'alter system flush shared_pool' command periodically?

Scott Heaton wrote:
We have an application running WebLogic 5.1 against an Oracle 8.1.7.4 database
and are seeing very rapid fragmentation of the Oracle database shared pool, ultimately
resulting in an ORA-04031 error (unable to allocate xxxx bytes of shared memory).
I'm curious if there are are known issues with WebLogic 5.1 regarding the database
shared pool, retaining a handle to SQL statements issues (so that they cannot
be released), or anything similar? Thanks.What sp level of 5.1? We are caching prepared statements in the later versions,
so for every pooled connection there will be up to 10 (or whatever cache size
you set) prepared statements cached for re-use, and each of these will retain
a DBMS-side cursor. I am not an oracle DBA so I don't know if this relates directly
to the shared pool fragmentation...
Joe

Oracle Connection Pool failure in COM+

I am having some trouble trying to get a specific database to work with an application that makes use of a COM+ Application. When we point the application at the UAT database everything seems fine, but when we point it to the production database after a few successful calls it ends up failing at the COM+ application recycles. The event viewer provides the following information:
Event Type:     Error
Event Source:     COM+
Event Category:     Unknown
Event ID:     4786
Date:          8/5/2007
Time:          12:54:46 PM
User:          N/A
Computer:     APPL_SERVER
Description:
The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID: Oracle Connection Pool - tnsnames_alias
Method Name: IDispenserDriver::CreateResource
Server Application ID: {30A93CB3-25EB-4258-8C88-5AE103B7B86F}
Server Application Instance ID:
{A57C513E-519F-45BD-B46D-DC54B285F534}
Server Application Name: COM+ Application Name
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x7C8327F9
Call Stack:
+ 0x7c8327f9
ntdll!RtlFindActivationContextSectionGuid + 0x7d2
ntdll!RtlInitializeSListHead + 0x175
ntdll!RtlFindActivationContextSectionGuid + 0x1b7
msvcrt!malloc + 0x6c
oracommon9!sktsfMalloc + 0x14
orageneric9!kpummapg + 0x58
orageneric9!kghalo + 0xabb
orageneric9!kghalf + 0x102
orageneric9!kopo2cpc + 0x61
orageneric9!kopeini + 0x1d
orageneric9!kopo2cpc + 0xd2
orageneric9!kopopgi + 0x117
OraClient9!koudpnp + 0x712
OraClient9!koudpnp + 0x101
OraClient9!kpuinit0 + 0xb19
OraClient9!kpuinit + 0x38
OraClient9!OCIEnvInit + 0x1c
oramts!kpntsrvr::kpntsrvr(class kpntdbid *) + 0x80
oramts!kpntdbid::allocNewSrvr(struct SIDAND_ATTRIBUTES *) + 0x138
oramts!kpntdbid::GetSrvr(class kpntsvrl * *,unsigned long) + 0x7df
oramts!kpntdisp::getNet8conn(class kpntsvrl * *,unsigned long) + 0x41
oramts!kpntsess::initOCI(void) + 0xec
oramts!kpntsess::sessionBegin(void) + 0x17b
oramts!kpntdisp::CreateResource(unsigned long,unsigned long *,long *) + 0xc4
COMSVCS!DispManGetContext + 0xa3d
COMSVCS!DispManGetContext + 0x1fee
oramts!kpntdisp::allocateConnection(class kpntsess * *,unsigned long,class kpntrtyp *) + 0x3c4
oramts!_kpntsvcgetex + 0x183
oramts!_kpntsvcget + 0x25
oramts!kpntctra::getConnectionAndHandles(class kpntrtyp *,struct OCISvcCtx * *,struct OCITrans * *,struct OCIError * *) + 0x87
oramts!kpntctra::abortBranch(struct xid_t &,class kpntbrnch *,struct BOID *,int,struct BOID *) + 0x15a
oramts!kpntctra::doAbort(struct BOID *,int,struct BOID *) + 0x454
oramts!kpntajob::doJob(void) + 0x27
oramts!kpntjobq::serviceRequest(class kpntjob *) + 0x3e
oramts!workerThread(void *) + 0xd0
msvcrt!_endthreadex + 0xa3
kernel32!GetModuleFileNameA + 0xeb
Not being an expert in Oracle, I have been able to dig up a little bit of information that might be of use ...
a) Our tnsnames.ora indicates that the connections are to be DEDICATED and running Toad bares this out -- dllhost ends up with a single connection.
b) most of the database initial set of parameters seem to be very similar. The only difference I noticed was that the archive log mode and db_cache_advice are ON for production.
c) We have little control over how the connection strings are being created internally in this COM+ application, but however they are created it works for UAT and doesn't for PROD.
d) When we go into our web application and hit a page that makes use of the COM+ component to render, it will work the first time but when I do a simple browser refresh it will usually fail on the 2nd or 3rd time. Almost like it is trying to expand the connection pool size and the oracle server is throwing up.
If I didn't mention earlier the two database instances run on different servers but the application server is exactly the same. We only change the alias we are using for the database (both are defined in tnsnames) and the password used to make its connection.
Does anyone have any clues on this one? I am really spinning my wheels trying to figure out what could cause this type of situation. Anything at all would be very helpful.

It appeared to us that the problem was with the Oracle server and that it might have been failing when we were trying to expand our application connection pool size or basically obtain more connections.
The biggest indicator of this is that we run the same application code against two different databases and one works and one does not work. Having said this, I suppose the problem could be rooted in a data error instead of an oracle server error ...
Is there a specific trace file on the oracle server that would help me point to any error that is truly an oracle server error? Sorry I am very new to Oracle.

Bug in Oracle JDBC Pooling Classes - Deadlock

We are utilizing Oracle's connection caching (drivers 10.2.0.1) and have found a deadlock situation. I reviewed the code for the (drivers 10.2.0.3) and I see the same problem could happen.
I searched and have not found this problem identified anywhere. Is this something I should post to Oracle in some way (i.e. Metalink?) or is there a better forum to get this resolved?
We are utilizing an OCI driver with the following setup in the server.xml
<ResourceParams name="cmf_toolbox">
<parameter>
<name>factory</name>
<value>oracle.jdbc.pool.OracleDataSourceFactory</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>user</name>
<value>hidden</value>
</parameter>
<parameter>
<name>password</name>
<value>hidden</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:oracle:oci:@PTB2</value>
</parameter>
<parameter>
<name>connectionCachingEnabled</name>
<value>true</value>
</parameter>
<parameter>
<name>connectionCacheProperties</name>
<value>(InitialLimit=5,MinLimit=15,MaxLimit=75,ConnectionWaitTimeout=30,InactivityTimeout=300,AbandonedConnectionTimeout=300,ValidateConnection=false)</value>
</parameter>
</ResourceParams>
We get a deadlock situation between two threads and the exact steps are this:
1) thread1 - The OracleImplicitConnectionClassThread class is executing the runAbandonedTimeout method which will lock the OracleImplicitConnectionCache class with a synchronized block. It will then go thru additional steps and finally try to call the LogicalConnection.close method which is already locked by thread2
2) thread2 - This thread is doing a standard .close() on the Logical Connection and when it does this it obtains a lock on the LogicalConnection class. This thread then goes through additional steps till it gets to a point in the OracleImplicitConnectionCache class where it executes the reusePooledConnection method. This method is synchronized.
Actual steps that cause deadlock:
1) thread1 locks OracleImplicitConnectionClass in runAbandonedTimeout method
2) thread2 locks LogicalConnection class in close function.
3) thread1 tries to lock the LogicalConnection and is unable to do this, waits for lock
4) thread2 tries to lock the OracleImplicitConnectionClass and waits for lock.
***DEADLOCK***
Thread Dumps from two threads listed above
thread1
Thread Name : Thread-1 State : Deadlock/Waiting on monitor Owns Monitor Lock on 0x30267fe8 Waiting for Monitor Lock on 0x509190d8 Java Stack at oracle.jdbc.driver.LogicalConnection.close(LogicalConnection.java:214) - waiting to lock 0x509190d8> (a oracle.jdbc.driver.LogicalConnection) at oracle.jdbc.pool.OracleImplicitConnectionCache.closeCheckedOutConnection(OracleImplicitConnectionCache.java:1330) at oracle.jdbc.pool.OracleImplicitConnectionCacheThread.runAbandonedTimeout(OracleImplicitConnectionCacheThread.java:261) - locked 0x30267fe8> (a oracle.jdbc.pool.OracleImplicitConnectionCache) at oracle.jdbc.pool.OracleImplicitConnectionCacheThread.run(OracleImplicitConnectionCacheThread.java:81)
thread2
Thread Name : http-7320-Processor83 State : Deadlock/Waiting on monitor Owns Monitor Lock on 0x509190d8 Waiting for Monitor Lock on 0x30267fe8 Java Stack at oracle.jdbc.pool.OracleImplicitConnectionCache.reusePooledConnection(OracleImplicitConnectionCache.java:1608) - waiting to lock 0x30267fe8> (a oracle.jdbc.pool.OracleImplicitConnectionCache) at oracle.jdbc.pool.OracleConnectionCacheEventListener.connectionClosed(OracleConnectionCacheEventListener.java:71) - locked 0x34d514f8> (a oracle.jdbc.pool.OracleConnectionCacheEventListener) at oracle.jdbc.pool.OraclePooledConnection.callImplicitCacheListener(OraclePooledConnection.java:544) at oracle.jdbc.pool.OraclePooledConnection.logicalCloseForImplicitConnectionCache(OraclePooledConnection.java:459) at oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:475) at oracle.jdbc.driver.LogicalConnection.closeInternal(LogicalConnection.java:243) at oracle.jdbc.driver.LogicalConnection.close(LogicalConnection.java:214) - locked 0x509190d8> (a oracle.jdbc.driver.LogicalConnection) at com.schoolspecialty.cmf.yantra.OrderDB.updateOrder(OrderDB.java:2022) at com.schoolspecialty.cmf.yantra.OrderFactoryImpl.saveOrder(OrderFactoryImpl.java:119) at com.schoolspecialty.cmf.yantra.OrderFactoryImpl.saveOrder(OrderFactoryImpl.java:67) at com.schoolspecialty.ecommerce.beans.ECommerceUtil.saveOrder(Unknown Source) at com.schoolspecialty.ecommerce.beans.ECommerceUtil.saveOrder(Unknown Source) at com.schoolspecialty.ecommerce.beans.UpdateCartAction.perform(Unknown Source) at com.schoolspecialty.mvc2.ActionServlet.doPost(ActionServlet.java:112) at com.schoolspecialty.ecommerce.servlets.ECServlet.doPostOrGet(Unknown Source) at com.schoolspecialty.ecommerce.servlets.ECServlet.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at com.schoolspecialty.ecommerce.servlets.filters.EcommerceURLFilter.doFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534)

We used a documented option to abandon connects in the case of an unforeseen error. The consequence of using this option was not a graceful degradation in performance but a complete lockup of the application. The scenario in which we created a moderate number of abandoned connections was a rare error scenario but a valid test.
How could this not be a bug in the Oracle driver? Is dead-lock a desireable outcome of using an option? Is dead-lock ever an acceptable consequence of using a feature as documented?
Turns out other Oracle options to recover from an unexpected error also incur a similar deadlock (TimeToLiveTimeout).
I did a code review of the decompiled drivers and it clearly shows the issue, confirming the original report of this issue. Perhaps you have evidence to the contrary or better evidence to support your statement "not a bug in Oracle"?
Perhaps you are one of the very few people who have not experience problems with Oracle drivers? I've been using Oracle since 7.3.4 and it seems that I have always been working around Oracle JDBC driver problems.
We are using Tomcat with the OracleDataSourceFactory.

How to change the field size cache/buffer in a query

I query a field from sql developer, the field is cases_history, it resides in a data mart in the global network of our company.
this field is big in size, it stores logs in a sequential way, so field size increases a lot.
when i query it and try a "single record view" the field is cut off and can´t see all of its content..
WHAT I THOUGHT AND IT DOESN´T APPLY
1. maybe in database connections in the system tab, I go to the oracle data mart that i am interested in and change buffer and cache
but it doesn´t work, sql developer keeps showing part of the field
2. maybe it was then the buffer size in sql developer, so I change it, but no luck
WHAT IS THE PROBLEM HERE?
MANY THANKS IN ADVANCE

many thanks in advance for your help,
1.the data type in the remote oracle data mart is VARCHAR2(4000)
2.editing with the pencil cuts off at somepoint (which is the same line and last word)
3.this is the query I write
||select case_history from wfm_case where case_id='xxxx'||
this is to test if I can get a long case_history, which we know it is because it is fully accessible through a web solution to revise cases.
PLS note. I have a tns connection which is of the following type :
(in data sources (odbc) -- system dsn -- oracle odbc driver configuration ...oracle .. buffer size =9000 , cache buffer size =4000 and FORCE SQL_WCHAR SUPPORT is enabled
many thanks,
Jordi.

Change of Min Pool Size has no effect?

Hi, we are still using odp 9.2.0.4 on windows server 2003 webserver and oracle database 9i on Sun solaris. Recently we discovered a problem using Min Pool Size = 1, it seems that if new connections are required we sometimes get a connection timeout. So we decided to set Min Pool Size = 30, and on the testserver this works fine. In the odp tracefile (tracelevel=2) you see the 30 connections building up immediately. But on the production server we see no difference, it looks like the (new installed, application pool reset) application still uses the Min Pool Size = 1 setting.
The connection string is build up in application code. On the testserver it was sufficient to stop and start the website and its application pool, on the production server this has no effect.
Does anyone have an idea what the problem is??? We also tried restarting the IIS server, that did not help either. In production there are more applications using ODP.
Regards, Paul.

What problem are you trying to solve at this point? Simply "why is odp not tracing?" The only suggestions I really have there are
1) make sure you restart the app after enabling tracing parameters
2) make sure the directory you've set tracing to is open as far as permissions
3) make sure you've set tracing in the right registry setting if you have multiple versions of ODP installed
4) if you're trying to write to c:\ root, try creating and pointing to a different (c:\odptrace for example) directory instead.
Hope it helps,
Greg

Setting max bean pool size in MDB

Hi,
I need to set the max bean pool size for my MDB to 1. This MDB is a part of my application and is packaged in an ear.
I tried to set it with the following annotation -
import javax.ejb.*;
@MessageDriven
(mappedName = "MyQueue",
name = "MyMDB",
activationConfig = {
@ActivationConfigProperty(propertyName="maxBeansInFreePool",
propertyValue="1"),
@ActivationConfigProperty(propertyName="initialBeansInFreePool",
propertyValue="1"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
However, this does not seem to work since I see the Current pool count on the WLS console as 3 after processing is done.
After looking at various posts in this forum, I also tried it with weblogic ejbgen as follows-
import weblogic.ejbgen.*;
@MessageDriven(ejbName = "MyMDB",
destinationType = "javax.jms.Queue",
initialBeansInFreePool = "1",
maxBeansInFreePool = "1",
destinationJndiName = "MyQueue")
However, with this the MDB did not get deployed in WLS.
I am using Weblogic 10.3 / EJB 3.0.
Any help on this is greatly appreciated.
Thanks
Meera

As far as I know, it currently isn't possible to set max-beans-in-free-pool via annotations. You can use a deployment plan (configurable from console and/or follow the link supplied by atheek1).
I think you can also automatically generate descriptors based on javadoc text via ejb-gen, I'm not quite sure if this tooling can work in conjunction with EJB 3.0 annotations. See http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/EJBGen_reference.html
Tom

Oracle TimesTen In-Memory Database VS Oracle In-Memory Database Cache

Hi,
What is difference in Oracle TimesTen In-Memory Database VS Oracle In-Memory Database Cache.
For 32 bit on windows OS i am not able to insert data's more than 500k rows with 150 columns (with combinations of CHAR,BINARY_DOUBLE,BINARY_FLOAT, TT_BIGINT,REAL,DECIMAL,NUMERIC etc).
[TimesTen][TimesTen 11.2.2.2.0 ODBC Driver][TimesTen]TT0802: Database permanent space exhausted -- file "blk.c", lineno 3450, procedure "sbBlkAlloc"
I have set Perm size as 700 mb,Temp size as 100mb
What is the max size we can given for PermSize,TempSize,LogBufMB for 32 bit on windows OS.
What is the max size we can given for PermSize,TempSize,LogBufMB for 64 bit on windows OS.
What is the Max configuration of TT for 32 bit what i can set for Perm size Temp size.
Thanks!

They are the same product but they are licensed differently and the license limits what functionality you can use.
TimesTen In-Memory Database is a product in its own right allows you to use TimesTen as a standalone database and also allows replication.
IMDB Cache is an Oracle DB Enterprise Edition option (i.e. it can only be licensed as an option to an Oracle DB EE license). This includes all the functionality of TImesTen In-Memory Database but adds in cache functionality (cache groups, cache grid etc.).
32-bit O/S are in general a poor platform to try and create an in-memory database of any significant size (32-bit O/S are very limited in memory addressing capability) and 32-bit Windows is the worst example. The hard coded limit for total datastore size on 32-bit O/S is 2 GB but in reality you probably can;'t achieve that. On Windows the largest you can get is 1.1 GB and most often less than that. If you need something more than about 0.5 Gb on Windows then you really need to use 64-bit Windows and 64-bit TimesTen. There are no hard coded upper limit to database size on 64-bit TimesTen; the limit is the amount of free physical memory (not virtual memory) in the machine. I have easily created a 12 GB database on a Win64 machine with 16 GB RAM. On 64-bit Unix machines we have live database of over 1 TB...
Chris

Initial and Minimum Pool Size

in j2ee admin console, i set the parameter to 8. I go to oracle and from sql*plus i execute the following command
select * from v$session
However, when i run my sample program I only see a session from my computer. Is it right? or I am supposed to see 8 sessions

Well, that would depend on whether you set initial pool size to 8 or minimum pool size to 8, wouldn't it? All you said was that you set "the parameter" to 8.

Shared pool size

Hi All,
DB:oracle9iR2
os:solaris
how to get the shared_pool usage,free total size and hit ratio in oracle 9i R2?,can any one help to me....
POOL BYTES MB
shared pool used :
shared pool free :
shared pool (Total):
=================
Shared_pool hit ratio:
thanks.

Hi All,
thank you for all the responses..
Db:oracle 9iR2
os :solaris
Actually i am facing below problem..
prob: ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4224 bytes of shared memory ("shared pool","select obj#,type#,ctime,mtim...","sga heap(1,0)","library ca
che")
Wed Feb 8 19:33:43 2012
Errors in file /ora/admin/cddp/bdump/cddp_cjq0_2601.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4224 bytes of shared memory ("shared pool","select obj#,type#,ctime,mtim...","sga heap(1,0)","library ca
che")
Wed Feb 8 19:33:43 2012
Errors in file /ora/admin/cddp/bdump/cddp_cjq0_2601.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4224 bytes of shared memory ("shared pool","select obj#,type#,ctime,mtim...","sga heap(1,0)","library ca
che")
Wed Feb 8 19:33:48 2012
Errors in file /ora/admin/cddp/bdump/cddp_cjq0_2601.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4224 bytes of shared memory ("shared pool","select obj#,type#,ctime,mtim...","sga heap(1,0)","library ca
che")
========================================
i was running with 200MB size of share pool....couple of days back un expectdly i got above error....for temparory solution i did shared pool flush...
again nexday same error got repeated....for that i increased shared pool size to 420 MB....
while monitoring db it is using shared pool memory up to 400MB with avg shared pool hit ratio of 94.5 %..(database started recently)...
Earlier shared_pool size:200MB
Now:420 MB
Avg usage:up to 400MB
my question is :
1)if we have many different sql statements in shared pool ..won't
oracle flush share pool (ie aged out based on LRU or some alogorithm) if any program need memory in shared pool?
2) Any data Fragmentation will cause@above error?
3)can any one please explain..... how to check whats going on in Shared_pool(internally)...why it is using 400MB while compare to erlier avg usage 170MB .....any idea...(how to find root cause)..?
4)will plan table cause any issue ?
can any one explain to me...
thanks..
Edited by: kk001 on Feb 11, 2012 4:54 PM
Edited by: kk001 on Feb 11, 2012 4:56 PM

Resource_manager_plan and Reserved pool size parameter changing every time

Hello All,
In my production database (Oracle 11g RAC )Resource_manager_plan and Reserved pool size parameter changing every time .
Below is my question .
This parameter changed automatically or it require manual intervention .
In what case this parameter changed if it automatically changed.
I had checked dba_hist_parameter a, dba_Hist_snapshot b table for parameter changed history parameter changed .
This parameter linked with process and sql performances?.
Please help me . Thanks .
Regards
Ranjeet

When scheduler window opens, its resource plan becomes active. For example, MONDAY_WINDOW begins on monday at 22:00. At this time current plan is changed to DEFAULT_MAINTENANCE_PLAN. At 00:00 (Tuesday) plan that was active before monday 22:00, becomes active. DEFAULT_MAINTENANCE_PLAN is used for Autotask clients :
select client_name,WINDOW_GROUP from DBA_AUTOTASK_CLIENT ;
CLIENT_NAME                     WINDOW_GROUP
auto optimizer stats collection ORA$AT_WGRP_OS
auto space advisor              ORA$AT_WGRP_SA
sql tuning advisor              ORA$AT_WGRP_SQ
select * from DBA_SCHEDULER_WINGROUP_MEMBERS where WINDOW_GROUP_NAME in (select WINDOW_GROUP from DBA_AUTOTASK_CLIENT);
WINDOW_GROUP_NAME WINDOW_NAME
ORA$AT_WGRP_OS    MONDAY_WINDOW
ORA$AT_WGRP_OS    TUESDAY_WINDOW
ORA$AT_WGRP_OS    WEDNESDAY_WINDOW
ORA$AT_WGRP_OS    THURSDAY_WINDOW
ORA$AT_WGRP_OS    FRIDAY_WINDOW
ORA$AT_WGRP_OS    SATURDAY_WINDOW
ORA$AT_WGRP_OS    SUNDAY_WINDOW
ORA$AT_WGRP_SA    MONDAY_WINDOW
ORA$AT_WGRP_SA    TUESDAY_WINDOW
ORA$AT_WGRP_SA    WEDNESDAY_WINDOW
ORA$AT_WGRP_SA    THURSDAY_WINDOW
ORA$AT_WGRP_SA    FRIDAY_WINDOW
ORA$AT_WGRP_SA    SATURDAY_WINDOW
ORA$AT_WGRP_SA    SUNDAY_WINDOW
ORA$AT_WGRP_SQ    MONDAY_WINDOW
ORA$AT_WGRP_SQ    TUESDAY_WINDOW
ORA$AT_WGRP_SQ    WEDNESDAY_WINDOW
ORA$AT_WGRP_SQ    THURSDAY_WINDOW
ORA$AT_WGRP_SQ    FRIDAY_WINDOW
ORA$AT_WGRP_SQ    SATURDAY_WINDOW
ORA$AT_WGRP_SQ    SUNDAY_WINDOW

Oracle 10gReport POOL Size/Cache

Similar Messages

Maybe you are looking for