10g redo buffer
What sets up the size of the redo buffer ?
I think you are speaking of LOG_BUFFER, which is an initialization parameter you can set
in the initSID.ora file, or by :
SQL> alter system set LOG_BUFFER = <LOG_BUFFER size> scope = spfile;
then you have to restart your DB. See
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10755/initparams109.htm#sthref450
Similar Messages
-
Svrmgrl problem. illegal redo buffer size
Hello experts,
I installed oracle 8.1.5 in Linux 6.1 successfully.
And I rebooted the computer and got into the svrmgrl to start the db.
I can connect using "connect internal"
But I cannot start the db using "startup;"
I get this error message,
ORA-07304: ksmcsg: illegal redo buffer size.
I had no idea what to do now.
Please help me out.
And many many thanks in advance !!!
nullCheck log_buffer parameter in init.ora.
If the OS block size is 512, a value of 10*512 or 5120 will be valid.
Rounding off to 5100 would generate this error. -
10G redo log switchs with no activity
We have been testing 8i to 10G migrations and two things I have noticed that are different bwteeen the 2 databases are:
1) redo log switching occurring even though the database has no users and just sitting there. This is not happeniong in our 8i databases.
2) trace files of format instance_m001_ and instance_m000_ in ../bdump. Our 8i bdump's normally do not have trc files unless a problem occurs.
Is it normal for 10G to automatically switch redo logs with no activity and are these .trc files also normal? In general I get nervous with trc files. -quinnStill haven't figured out the redo log switches, they seem to be slowing down, but the excess trace files are apparently cuased by a bug and can be fixed with Patch 3432729.
-
Redo Log Buffer sizing problem
My pc has 512mb RAM and i was trying to increase the redo log buffer size. Initially the log_buffer size was 2899456 bytes. So i tried to increase it to 3099456 by issuing the command:
ALTER SYSTEM SET LOG_BUFFER=3099456 SCOPE=SPFILE;
And i issued SHUTDOWN IMMEDIATE. Upon restarting my database, when i queried SHOW PARAMETERS LOG_BUFFER . The value has been changed to 7029248 bytes not 3099456 which i wanted. How did this happen?1.) We are all volunteers.
2.) It was only 5 hours between posts and you're complaining that there are no answers?
3.) You didn't bother to mention platform or Oracle version, even after being specifically asked for it? Which part of "What is your Oracle version?" do you not understand? And yes, the platform may be useful too....
From memory, there could a couple of things going on. First off, starting in 9i, Oracle allocates memory in granules, so, allocating chunks smaller than granule size can result in being rounded up to granule size. Second, on some platforms, Oracle protects the redo buffer with "guard pages", i.e., extra memory that serves simply to try to prevent accidental memory overflows from corrupting the redo buffer.
If you want a specific answer, or at least a shot at one, post:
1.) Oracle version (specific version: 8.1.7.4, 9.2.0.8, 10.2.0.3, etc).
2.) Platform
3.) O/S and version
4.) Current SGA size
Reposting the same question, or threatening to do so, will get you nowhere.
-Mark -
Redo Log Buffer 32.8M, Seems to Big?
I just took over a database (Mainly used for OLTP on 11gR1) and I am looking at the log_buffer parameter it is set to 34412032 (32.8M). Not sure why it is so high.
select
NAME,
VALUE
from
SYS.V_$SYSSTAT
where
NAME in ('redo buffer allocation retries', 'redo log space wait time');
redo buffer allocation retries 185
redo log space wait time 5180(database has been up for 7.5 days)
Any opinions on this? I Normally keep try to stay below 3M and have not really seen it above 10M.Sky13 wrote:
I just took over a database (Mainly used for OLTP on 11gR1) and I am looking at the log_buffer parameter it is set to 34412032 (32.8M). Not sure why it is so high.
In 11g you shouldn't set the log_buffer parameter - let Oracle set the default.
The value is derived from the setting for the CPU count and the transactions parameter, which may be derived from sessions, which may be derived from processes. Moreover, Oracle is going to allocate at least a granule (which may be 4MB, 8MB, 16MB, 64MB or 256MB depending on the size of the SGA, so you are unlikely to save memory by reducing the log buffer size.
Here's a link to a discussion which shows you how to find out what's really behind that figure.
Re: Archived redo log size more less than online redo logs
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
Author: <b><em>Oracle Core</em></b> -
Hi,
i'm trying to size redolog and the buffer size in the best way.
I already adjusted the size of the redo to let them switch 1/2 times per hour.
The next step is to modify the redo buffer to avoid waits.
Actually this query gives me 896 as result.
SELECT NAME, VALUE
FROM V$SYSSTAT
WHERE NAME = 'redo buffer allocation retries';
I suppose this should be near to 0.
Log_buffer is setted to 1m.
And i read "sizing the log buffer larger than 1M does not provide any performance benefit" so what can i do to reduce that wait time?
Any ideas or suggestions?
Thanks
AcrACR80,
Every time you create a redo entry, you have to allocate space to copy it into the redo buffer. You've had 588 allocation retries in 46M entries. That's "close to zero"..
redo entries 46,901,591
redo buffer allocation retries 588The 1MB limit was based around the idea that a large buffer could allow a lot of log to accumulate between writes with the result that a process could execute a small transaction and commit - and have to wait a "long" time for the log writer to do a big write.
If in doubt, check the two wait events:
"log file sync"
"log buffer space".
As a guideline, you may reduce waits for "log buffer space" by increasing the size of the log buffer - but this introduces the risk of longer waits for "log file sync". Conversely, reducing the log buffer size may reduce the impact of "log file sync" waits but runs the risk of increasing "log buffer space" waits.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk -
Tuning of Redo logs in data warehouses (dwh)
Hi everybody,
I'm looking for some guidance to configure redo logs in data warehouse environments.
Of course we are running in noarchive log mode and use direct path inserts (nologging) whereever possible.
Nevertheless every etl process (one process per day) produces 150 GB of redo logs. That seems quite a lot compared to the overall data volume (1 TB tables + indexes).
Actually im not sure if there is a tuning problem, but because of the large amount of redo I'm interested in examining it.
Here are the facts:
- Oracle 10g, 32 GB RAM
- 6 GB SGA, 20 GB PGA
- 5 log groups each with 1 Gb log file
- 4 MB Log buffer
- every day ca 150 logswitches (with peaks: some logswitches after 10 seconds)
- some sysstat metrics after one etl load:
Select name, to_char(value, '9G999G999G999G999G999G999') from v$sysstat Where name like 'redo %';
"NAME" "TO_CHAR(VALUE,'9G999G999G999G999G999G999')"
"redo synch writes" " 300.636"
"redo synch time" " 61.421"
"redo blocks read for recovery"" 0"
"redo entries" " 327.090.445"
"redo size" " 159.588.263.420"
"redo buffer allocation retries"" 95.901"
"redo wastage" " 212.996.316"
"redo writer latching time" " 1.101"
"redo writes" " 807.594"
"redo blocks written" " 321.102.116"
"redo write time" " 183.010"
"redo log space requests" " 10.903"
"redo log space wait time" " 28.501"
"redo log switch interrupts" " 0"
"redo ordering marks" " 2.253.328"
"redo subscn max counts" " 4.685.754"
So the questions:
Does anybody can see tuning needs? Should the Redo logs be increased or incremented? What about placing redo logs on Solid state disks?
kind regards,
Mirkouser5341252 wrote:
I'm looking for some guidance to configure redo logs in data warehouse environments.
Of course we are running in noarchive log mode and use direct path inserts (nologging) whereever possible.Why "of course" ? What's your recovery strategy if you wreck the database ?
Nevertheless every etl process (one process per day) produces 150 GB of redo logs. That seems quite a lot compared to the overall data volume (1 TB tables + indexes).This may be an indication that you need to do something to reduce index maintenance during data loading
>
Actually im not sure if there is a tuning problem, but because of the large amount of redo I'm interested in examining it.
For a quick check you might be better off running statspack (or AWR) snapshots across the start and end of batch to get an idea of what work goes on and where the most time goes. A better strategy would be to examine specific jobs in detail, though).
"redo synch time" " 61.421"
"redo log space wait time" " 28.501" Rough guideline - if the redo is slowing you down, then you've lost less than 15 minutes across the board to the log writer. Given the number of processes loading and the elapsed time to load, is this significant ?
"redo buffer allocation retries"" 95.901" This figure tells us how OFTEN we couldn't get space in the log buffer - but not how much time we lost as a result. We also need to see your 'log buffer space' wait time.
Does anybody can see tuning needs? Should the Redo logs be increased or incremented? What about placing redo logs on Solid state disks?Based on the information you've given so far, I don't think anyone should be giving you concrete recommendations on what to do; only suggestions on where to look or what to tell us.
Regards
Jonathan Lewis -
Could someone please explain me why do I see different values for log_buffer in v$spparameter / v$parameter and v$sgastat
SYS> select value from v$spparameter where name ='log_buffer' ;
VALUE
2703937
SYS> select value from v$parameter where name ='log_buffer' ;
VALUE
2703360
SYS> select * from v$sgastat where name = 'log_buffer';
POOL NAME BYTES
log_buffer 5259264Thank you in advance and sorry for newbee questions :)In 10G R2, Oracle combines fixed SGA area and redo buffer [log buffer] together. If there is a free space after Oracle puts the combined buffers into a granule, that space is added to the redo buffer. Thus you see redo buffer has more space than expected. This is an expected behavior.
In 10.2 the log buffer is rounded up to use the rest of the granule.
The Log_buffer Default Size Cannot Be Reduced In 10g R2 [ID 351857.1] -
Hi,
Version : Oracle 9i
I am getting buffer busy waits on some tables. Will increase in inittrans & pctfree of those tables reduce buffer busy waits?
Tablespace is having segment space mgmt auto & extent management local.
cursor_sharing is similar.
Users are not experiencing any problem.Is there any problem other than this in statspack report?
STATSPACK report for
DB Name DB Id Instance Inst Num Release Cluster Host
AHD 3712247982 ahd 1 9.2.0.1.0 NO SBGSDPRI
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 20 13-Feb-07 14:48:35 33 9.9
End Snap: 21 13-Feb-07 15:12:19 34 10.4
Elapsed: 23.73 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 656M Std Block Size: 8K
Shared Pool Size: 152M Log Buffer: 768K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 5,960.83 2,761.29
Logical reads: 2,376.85 1,101.05
Block changes: 35.48 16.44
Physical reads: 97.56 45.20
Physical writes: 1.15 0.53
User calls: 92.63 42.91
Parses: 20.00 9.27
Hard parses: 0.29 0.13
Sorts: 4.80 2.22
Logons: 0.01 0.00
Executes: 23.14 10.72
Transactions: 2.16
% Blocks changed per Read: 1.49 Recursive Call %: 14.69
Rollback per transaction %: 0.00 Rows per Sort: 472.64
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.65 Redo NoWait %: 100.00
Buffer Hit %: 95.90 In-memory Sort %: 100.00
Library Hit %: 99.15 Soft Parse %: 98.55
Execute to Parse %: 13.57 Latch Hit %: 99.70
Parse CPU to Parse Elapsd %: 90.83 % Non-Parse CPU: 96.58
Shared Pool Statistics Begin End
Memory Usage %: 84.68 84.76
% SQL with executions>1: 77.32 79.22
% Memory for SQL w/exec>1: 90.74 92.81
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
CPU time 125 54.23
db file sequential read 83,110 69 30.14
db file scattered read 23,196 27 11.75
buffer busy waits 11,760 6 2.42
log file sync 3,078 1 .45
Wait Events for DB: AHD Instance: ahd Snaps: 20 -21
-> 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)
Avg
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
db file sequential read 83,110 0 69 1 27.0
db file scattered read 23,196 0 27 1 7.5
buffer busy waits 11,760 0 6 0 3.8
log file sync 3,078 0 1 0 1.0
log file parallel write 5,216 4,841 1 0 1.7
control file sequential read 1,390 0 1 1 0.5
control file parallel write 462 0 0 1 0.2
db file parallel write 672 336 0 0 0.2
latch free 54 24 0 2 0.0
SQL*Net more data to client 1,026 0 0 0 0.3
LGWR wait for redo copy 12 0 0 0 0.0
SQL*Net message from client 131,863 0 22,857 173 42.9
virtual circuit status 48 48 1,497 31188 0.0
wakeup time manager 45 45 1,446 32123 0.0
SQL*Net message to client 131,864 0 0 0 42.9
SQL*Net more data from clien 27 0 0 0 0.0
Background Wait Events for DB: AHD Instance: ahd Snaps: 20 -21
-> ordered by wait time desc, waits desc (idle events last)
Avg
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
log file parallel write 5,216 4,841 1 0 1.7
control file parallel write 462 0 0 1 0.2
control file sequential read 184 0 0 2 0.1
db file parallel write 672 336 0 0 0.2
log file sync 24 0 0 0 0.0
db file sequential read 1 0 0 8 0.0
LGWR wait for redo copy 12 0 0 0 0.0
rdbms ipc message 12,386 7,345 10,752 868 4.0
SQL*Net message from client 384 0 1,498 3901 0.1
smon timer 4 4 1,229 ###### 0.0
SQL*Net message to client 384 0 0 0 0.1
SQL ordered by Gets for DB: AHD Instance: ahd Snaps: 20 -21
-> End Buffer Gets Threshold: 10000
-> Note that resources reported for PL/SQL includes the resources used by
all SQL statements called within the PL/SQL code. As individual SQL
statements are also reported, it is possible and valid for the summed
total % to exceed 100
CPU Elapsd
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
1,269,773 52 24,418.7 37.5 27.03 76.26 3370382957
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1" ) AND ( (
381,394 44 8,668.0 11.3 21.30 22.94 3653016280
SELECT count(*) FROM call_req, ctct, loc, site, z_zo, z_lho WHER
E ( call_req.customer = ctct.id AND ctct.c_l_id = loc.id AND l
oc.l_si_id = site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo
lhoid = z_lho.id AND z_lho.lho_name LIKE :"SYS_B_0" AND cal
l_req.active_flag = :"SYS_B_1" ) AND ( ( call_req.group_id != :"
239,582 10 23,958.2 7.1 5.95 17.44 1650906216
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_0" ) AND ( ( call_req.group_id != :"SYS_B_1" ) and
146,016 9 16,224.0 4.3 2.58 12.01 977739309
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.group_id IN ( SELECT id FROM ctct WHERE id = :"SYS_B_00" O
R id = :"SYS_B_01" OR id = :"SYS_B_02" OR id = :"SYS_B_03" OR id
= :"SYS_B_04" OR id = :"SYS_B_05" OR id = :"SYS_B_06" OR id = :
"SYS_B_07" OR id = :"SYS_B_08" OR id = :"SYS_B_09" OR id = :"SYS
117,569 7 16,795.6 3.5 0.52 0.52 1972089848
SELECT call_req.open_date, call_req.id FROM call_req, ctct WHERE
( call_req.status = :"SYS_B_00" AND call_req.group_id = ctct.id
AND ctct.c_last_name LIKE :"SYS_B_01" AND ( call_req.assigne
e IS NULL ) ) AND ( call_req.group_id IN ( SELECT id FROM ctct W
HERE id = :"SYS_B_02" OR id = :"SYS_B_03" OR id = :"SYS_B_04" OR
100,276 4 25,069.0 3.0 2.77 6.95 771782876
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho, ctct cn01 WHERE ( call_req.customer = ctct.i
d AND ctct.c_l_id = loc.id AND loc.l_si_id = site.id AND site
.z_si_zo_id = z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.
lho_name LIKE :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1"
95,832 4 23,958.0 2.8 2.13 3.80 1755292198
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_00" AND call_req.active_flag = :"SYS_B_01" AND ( ca
86,680 10 8,668.0 2.6 7.69 8.21 3407388950
SQL ordered by Gets for DB: AHD Instance: ahd Snaps: 20 -21
-> End Buffer Gets Threshold: 10000
-> Note that resources reported for PL/SQL includes the resources used by
all SQL statements called within the PL/SQL code. As individual SQL
statements are also reported, it is possible and valid for the summed
total % to exceed 100
CPU Elapsd
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
SELECT count(*) FROM call_req, ctct, loc, site, z_zo, z_lho WHER
E ( call_req.customer = ctct.id AND ctct.c_l_id = loc.id AND l
oc.l_si_id = site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo
lhoid = z_lho.id AND z_lho.lho_name LIKE :"SYS_B_0" ) AND (
( call_req.group_id != :"SYS_B_1" ) and ( call_req.group_id !=
71,839 3 23,946.3 2.1 2.73 6.07 1599404397
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo WHERE ( call_req.active_flag = :"SYS_B_0" AND call_r
eq.customer = ctct.id AND ctct.c_l_id = loc.id AND loc.l_si_id
= site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo_name LIK
E :"SYS_B_1" ) AND ( ( call_req.group_id != :"SYS_B_2" ) and (
60,507 9 6,723.0 1.8 1.47 1.49 632450130
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho, ctct cn01 WHERE ( call_req.customer = ctct.i
d AND ctct.c_l_id = loc.id AND loc.l_si_id = site.id AND site
.z_si_zo_id = z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.
lho_name LIKE :"SYS_B_0" AND call_req.status = :"SYS_B_1" AND
57,682 191 302.0 1.7 3.48 3.52 484128938
SELECT cnote.posted_date, cnote.text FROM cnote WHERE ( ( cnote.
loc_id = :"SYS_B_0" ) OR cnote.loc_id IS NULL ) AND ( cnote.inte
rnal IS NULL OR cnote.internal != :"SYS_B_1" ) ORDER BY cnote.p
osted_date DESC
52,146 3 17,382.0 1.5 1.22 3.60 930247717
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.group_id IN ( SELECT id FROM ctct WHERE id = :"SYS_B_00" O
R id = :"SYS_B_01" OR id = :"SYS_B_02" OR id = :"SYS_B_03" OR id
= :"SYS_B_04" OR id = :"SYS_B_05" OR id = :"SYS_B_06" OR id = :
"SYS_B_07" OR id = :"SYS_B_08" OR id = :"SYS_B_09" OR id = :"SYS
43,534 4 10,883.5 1.3 2.05 2.10 2363733805
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho, prob_ctg, ctct cn01 WHERE ( call_req.custome
r = ctct.id AND ctct.c_l_id = loc.id AND loc.l_si_id = site.id
AND site.z_si_zo_id = z_zo.id AND z_zo.zo_lho_id = z_lho.id A
ND z_lho.lho_name LIKE :"SYS_B_00" AND call_req.active_flag =
SQL ordered by Reads for DB: AHD Instance: ahd Snaps: 20 -21
-> End Disk Reads Threshold: 1000
CPU Elapsd
Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
81,653 52 1,570.3 58.8 27.03 76.26 3370382957
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1" ) AND ( (
15,402 10 1,540.2 11.1 5.95 17.44 1650906216
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_0" ) AND ( ( call_req.group_id != :"SYS_B_1" ) and
13,371 9 1,485.7 9.6 2.58 12.01 977739309
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.group_id IN ( SELECT id FROM ctct WHERE id = :"SYS_B_00" O
R id = :"SYS_B_01" OR id = :"SYS_B_02" OR id = :"SYS_B_03" OR id
= :"SYS_B_04" OR id = :"SYS_B_05" OR id = :"SYS_B_06" OR id = :
"SYS_B_07" OR id = :"SYS_B_08" OR id = :"SYS_B_09" OR id = :"SYS
6,157 4 1,539.3 4.4 2.77 6.95 771782876
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho, ctct cn01 WHERE ( call_req.customer = ctct.i
d AND ctct.c_l_id = loc.id AND loc.l_si_id = site.id AND site
.z_si_zo_id = z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.
lho_name LIKE :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1"
6,152 4 1,538.0 4.4 2.13 3.80 1755292198
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_00" AND call_req.active_flag = :"SYS_B_01" AND ( ca
4,622 3 1,540.7 3.3 2.73 6.07 1599404397
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo WHERE ( call_req.active_flag = :"SYS_B_0" AND call_r
eq.customer = ctct.id AND ctct.c_l_id = loc.id AND loc.l_si_id
= site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo_name LIK
E :"SYS_B_1" ) AND ( ( call_req.group_id != :"SYS_B_2" ) and (
2,982 3 994.0 2.1 1.22 3.60 930247717
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.group_id IN ( SELECT id FROM ctct WHERE id = :"SYS_B_00" O
R id = :"SYS_B_01" OR id = :"SYS_B_02" OR id = :"SYS_B_03" OR id
= :"SYS_B_04" OR id = :"SYS_B_05" OR id = :"SYS_B_06" OR id = :
"SYS_B_07" OR id = :"SYS_B_08" OR id = :"SYS_B_09" OR id = :"SYS
1,566 44 35.6 1.1 21.30 22.94 3653016280
SELECT count(*) FROM call_req, ctct, loc, site, z_zo, z_lho WHER
E ( call_req.customer = ctct.id AND ctct.c_l_id = loc.id AND l
oc.l_si_id = site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo
_lho_id = z_lho.id AND z_lho.lho_name LIKE :"SYS_B_0" AND cal
SQL ordered by Reads for DB: AHD Instance: ahd Snaps: 20 -21
-> End Disk Reads Threshold: 1000
CPU Elapsd
Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
l_req.active_flag = :"SYS_B_1" ) AND ( ( call_req.group_id != :"
1,540 1 1,540.0 1.1 0.56 1.64 2582352638
SELECT call_req.open_date, call_req.id FROM call_req, ctct, loc,
site, z_zo, z_lho WHERE ( call_req.customer = ctct.id AND ctct
.c_l_id = loc.id AND loc.l_si_id = site.id AND site.z_si_zo_id
= z_zo.id AND z_zo.zo_lho_id = z_lho.id AND z_lho.lho_name L
IKE :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1" AND ( call
1,106 2 553.0 0.8 1.25 3.01 548248759
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( ( c
all_req.assignee IS NOT NULL OR call_req.group_id IS NOT NULL )
AND ( call_req.type = :"SYS_B_00" OR call_req.type = :"SYS_B_01"
OR call_req.type IS NULL ) AND call_req.active_flag = :"SYS_B_0
2" ) AND ( call_req.group_id IN ( SELECT id FROM ctct WHERE id =
875 2 437.5 0.6 0.94 2.95 1195215130
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( ( c
all_req.assignee IS NULL AND call_req.group_id IS NULL ) AND ( c
all_req.type = :"SYS_B_00" OR call_req.type = :"SYS_B_01" OR cal
l_req.type IS NULL ) AND call_req.active_flag = :"SYS_B_02" ) AN
D ( call_req.group_id IN ( SELECT id FROM ctct WHERE id = :"SYS_
473 1 473.0 0.3 1.80 5.57 3376831664
BEGIN statspack.snap; END;
357 10 35.7 0.3 7.69 8.21 3407388950
SELECT count(*) FROM call_req, ctct, loc, site, z_zo, z_lho WHER
E ( call_req.customer = ctct.id AND ctct.c_l_id = loc.id AND l
oc.l_si_id = site.id AND site.z_si_zo_id = z_zo.id AND z_zo.zo
_lho_id = z_lho.id AND z_lho.lho_name LIKE :"SYS_B_0" ) AND (
( call_req.group_id != :"SYS_B_1" ) and ( call_req.group_id !=
177 5 35.4 0.1 1.81 2.08 920690862
SELECT ctct.c_last_name, ctct.c_first_name, ctct.c_middle_name,
ctct.c_public_phone, ctct.c_contact_num, ctct.c_org_id, ctct.c_l
_id, ctct.id FROM ctct, ct_ty WHERE ( ctct.c_ctp_id = ct_ty.id A
SQL ordered by Executions for DB: AHD Instance: ahd Snaps: 20 -21
-> End Executions Threshold: 100
CPU per Elap per
Executions Rows Processed Rows per Exec Exec (s) Exec (s) Hash Value
7,741 7,738 1.0 0.00 0.00 1060224445
SELECT grpmem.group_id , grpmem.manager_flag , grpmem.member , g
rpmem.notify_flag FROM grpmem WHERE grpmem.id = :"SYS_B_0"
2,459 2,459 1.0 0.00 0.00 3026674282
SELECT act_log.action_desc , act_log.analyst , act_log.call_req_
id , act_log.description , act_log.internal , act_log.knowledge_
session , act_log.knowledge_tool , act_log.last_mod_dt , act_log
.persid , act_log.system_time , act_log.time_spent , act_log.tim
e_stamp , act_log.type FROM act_log WHERE act_log.id = :"SYS_B_0
1,449 1,449 1.0 0.00 0.00 3299996875
SELECT att_evt.cancel_time , att_evt.event_tmpl , att_evt.fire_t
ime , att_evt.first_fire_time , att_evt.group_name , att_evt.las
t_mod_dt , att_evt.num_fire , att_evt.obj_id , att_evt.persid ,
att_evt.start_time , att_evt.status_flag , att_evt.user_smag , a
tt_evt.wait_time FROM att_evt WHERE att_evt.id = :"SYS_B_0"
1,336 1,336 1.0 0.00 0.00 3034229510
SELECT cr_prp.description , cr_prp.label , cr_prp.last_mod_by ,
cr_prp.last_mod_dt , cr_prp.owning_cr , cr_prp.persid , cr_prp.r
equired , cr_prp.sample , cr_prp.sequence , cr_prp.value FROM cr
prp WHERE crprp.id = :"SYS_B_0"
968 968 1.0 0.00 0.00 3460529092
select t.name, (select owner_instance from sys.aq$_queue_table_
affinities where table_objno = t.objno) from system.aq$_queue
_tables t where t.name = :1 and t.schema = :2 for update skip lo
cked
808 808 1.0 0.00 0.00 3346182257
SELECT call_req.active_flag , call_req.affected_rc , call_req.as
signee , call_req.call_back_date , call_req.call_back_flag , cal
l_req.category , call_req.change , call_req.charge_back_id , cal
l_req.close_date , call_req.created_via , call_req.customer , ca
ll_req.description , call_req.event_token , call_req.extern_ref
720 720 1.0 0.00 0.00 140137628
Module: Spotlight On Oracle, classic
SELECT DECODE(:b1,'BL','Buffer hash table instance lock','CF','C
ontrol file schema global enqueue lock','CI','Cross-instance fun
ction invocation instance lock','CS','Control file schema global
enqueue lock','CU','Cursor bind lock','DF','Data file instance
lock','DL','Direct loader parallel index create','DM','Mount/sta
718 718 1.0 0.00 0.00 4078915446
SELECT options.app_name, options.sym, options.id FROM options WH
ERE ( options.sym = :"SYS_B_0" ) AND ( options.del = :"SYS_B_1"
) ORDER BY options.app_name
634 634 1.0 0.00 0.00 1199698393
SELECT loc.alias , loc.del , loc.l_addr1 , loc.l_addr2 , loc.l_a
ddr3 , loc.l_addr4 , loc.l_addr5 , loc.l_addr6 , loc.l_details ,
loc.l_name , loc.l_si_id , loc.last_mod , loc.persid , loc.z_cb
SQL ordered by Executions for DB: AHD Instance: ahd Snaps: 20 -21
-> End Executions Threshold: 100
CPU per Elap per
Executions Rows Processed Rows per Exec Exec (s) Exec (s) Hash Value
l1 , loc.zcb_l2 , loc.z_cb_l3 , loc.z_l_code , loc.z_ro_code ,
loc.z_zo_code FROM loc WHERE loc.id = :"SYS_B_0"
531 208 0.4 0.00 0.00 800192270
SELECT lrel.l_persid, lrel.l_attr, lrel.l_sql, lrel.r_persid, lr
el.r_attr, lrel.r_sql, lrel.id FROM lrel WHERE lrel.l_persid = :
"SYS_B_0" and lrel.l_attr = :"SYS_B_1" ORDER BY lrel.l_persid ,
lrel.l_attr , lrel.l_sql
438 438 1.0 0.00 0.00 1317334374
Select PROPERTY_NAME,PROPERTY_VALUE,PROPERTY_TYPE from CI_PROPER
TIES where PROPERTY_NAME=:"SYS_B_0"
429 8,151 19.0 0.00 0.00 1976028604
SELECT cr_stat.sym, cr_stat.code FROM cr_stat WHERE cr_stat.del
= :"SYS_B_0" ORDER BY cr_stat.sym
383 383 1.0 0.00 0.00 2599265718
DELETE FROM anima WHERE id = :"SYS_B_0"
359 359 1.0 0.00 0.00 1719939797
DELETE FROM att_evt WHERE id = :"SYS_B_0"
337 337 1.0 0.00 0.00 3069423312
SELECT anima.a_act , anima.a_delta , anima.a_lock , anima.a_name
, anima.a_org , anima.a_string , anima.a_time , anima.t_method
, anima.t_persid , anima.t_type FROM anima WHERE anima.id = :"SY
S_B_0"
332 331 1.0 0.00 0.00 1549656119
SELECT crsq.id FROM crsq WHERE crsq.code = :"SYS_B_0"
315 315 1.0 0.00 0.00 1734736338
UPDATE cr_prp SET last_mod_by = :"SYS_B_0" , last_mod_dt = :"SYS
_B_1" WHERE id = :"SYS_B_2"
308 1,580 5.1 0.00 0.00 618252548
SELECT cr_prp.sequence, cr_prp.id FROM cr_prp WHERE cr_prp.ownin
g_cr = :"SYS_B_0" ORDER BY cr_prp.sequence
279 1,716 6.2 0.00 0.00 749386807
SELECT call_req.open_date, call_req.id FROM call_req WHERE call_
req.customer = :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1"
ORDER BY call_req.open_date DESC
277 277 1.0 0.00 0.00 321149819
INSERT INTO anima ( a_act, a_delta, a_lock, a_name, a_org, a_str
ing, a_time, t_method, t_persid, t_type, id ) VALUES ( :"SYS_B_
0" , :"SYS_B_1" , :"SYS_B_2" , :"SYS_B_3" , :"SYS_B_4" , nu
ll , :"SYS_B_5" , :"SYS_B_6" , :"SYS_B_7" , :"SYS_B_8" , :"
SQL ordered by Parse Calls for DB: AHD Instance: ahd Snaps: 20 -21
-> End Parse Calls Threshold: 1000
% Total
Parse Calls Executions Parses Hash Value
7,733 7,741 27.15 1060224445
SELECT grpmem.group_id , grpmem.manager_flag , grpmem.member , g
rpmem.notify_flag FROM grpmem WHERE grpmem.id = :"SYS_B_0"
2,459 2,459 8.63 3026674282
SELECT act_log.action_desc , act_log.analyst , act_log.call_req_
id , act_log.description , act_log.internal , act_log.knowledge_
session , act_log.knowledge_tool , act_log.last_mod_dt , act_log
.persid , act_log.system_time , act_log.time_spent , act_log.tim
e_stamp , act_log.type FROM act_log WHERE act_log.id = :"SYS_B_0
1,449 1,449 5.09 3299996875
SELECT att_evt.cancel_time , att_evt.event_tmpl , att_evt.fire_t
ime , att_evt.first_fire_time , att_evt.group_name , att_evt.las
t_mod_dt , att_evt.num_fire , att_evt.obj_id , att_evt.persid ,
att_evt.start_time , att_evt.status_flag , att_evt.user_smag , a
tt_evt.wait_time FROM att_evt WHERE att_evt.id = :"SYS_B_0"
1,336 1,336 4.69 3034229510
SELECT cr_prp.description , cr_prp.label , cr_prp.last_mod_by ,
cr_prp.last_mod_dt , cr_prp.owning_cr , cr_prp.persid , cr_prp.r
equired , cr_prp.sample , cr_prp.sequence , cr_prp.value FROM cr
prp WHERE crprp.id = :"SYS_B_0"
808 808 2.84 3346182257
SELECT call_req.active_flag , call_req.affected_rc , call_req.as
signee , call_req.call_back_date , call_req.call_back_flag , cal
l_req.category , call_req.change , call_req.charge_back_id , cal
l_req.close_date , call_req.created_via , call_req.customer , ca
ll_req.description , call_req.event_token , call_req.extern_ref
718 718 2.52 4078915446
SELECT options.app_name, options.sym, options.id FROM options WH
ERE ( options.sym = :"SYS_B_0" ) AND ( options.del = :"SYS_B_1"
) ORDER BY options.app_name
634 634 2.23 1199698393
SELECT loc.alias , loc.del , loc.l_addr1 , loc.l_addr2 , loc.l_a
ddr3 , loc.l_addr4 , loc.l_addr5 , loc.l_addr6 , loc.l_details ,
loc.l_name , loc.l_si_id , loc.last_mod , loc.persid , loc.z_cb
l1 , loc.zcb_l2 , loc.z_cb_l3 , loc.z_l_code , loc.z_ro_code ,
loc.z_zo_code FROM loc WHERE loc.id = :"SYS_B_0"
531 531 1.86 800192270
SELECT lrel.l_persid, lrel.l_attr, lrel.l_sql, lrel.r_persid, lr
el.r_attr, lrel.r_sql, lrel.id FROM lrel WHERE lrel.l_persid = :
"SYS_B_0" and lrel.l_attr = :"SYS_B_1" ORDER BY lrel.l_persid ,
lrel.l_attr , lrel.l_sql
438 438 1.54 1317334374
Select PROPERTY_NAME,PROPERTY_VALUE,PROPERTY_TYPE from CI_PROPER
TIES where PROPERTY_NAME=:"SYS_B_0"
429 429 1.51 1976028604
SQL ordered by Parse Calls for DB: AHD Instance: ahd Snaps: 20 -21
-> End Parse Calls Threshold: 1000
% Total
Parse Calls Executions Parses Hash Value
SELECT cr_stat.sym, cr_stat.code FROM cr_stat WHERE cr_stat.del
= :"SYS_B_0" ORDER BY cr_stat.sym
383 383 1.34 2599265718
DELETE FROM anima WHERE id = :"SYS_B_0"
359 359 1.26 1719939797
DELETE FROM att_evt WHERE id = :"SYS_B_0"
337 337 1.18 3069423312
SELECT anima.a_act , anima.a_delta , anima.a_lock , anima.a_name
, anima.a_org , anima.a_string , anima.a_time , anima.t_method
, anima.t_persid , anima.t_type FROM anima WHERE anima.id = :"SY
S_B_0"
330 332 1.16 1549656119
SELECT crsq.id FROM crsq WHERE crsq.code = :"SYS_B_0"
315 315 1.11 1734736338
UPDATE cr_prp SET last_mod_by = :"SYS_B_0" , last_mod_dt = :"SYS
_B_1" WHERE id = :"SYS_B_2"
308 308 1.08 618252548
SELECT cr_prp.sequence, cr_prp.id FROM cr_prp WHERE cr_prp.ownin
g_cr = :"SYS_B_0" ORDER BY cr_prp.sequence
277 277 0.97 321149819
INSERT INTO anima ( a_act, a_delta, a_lock, a_name, a_org, a_str
ing, a_time, t_method, t_persid, t_type, id ) VALUES ( :"SYS_B_
0" , :"SYS_B_1" , :"SYS_B_2" , :"SYS_B_3" , :"SYS_B_4" , nu
ll , :"SYS_B_5" , :"SYS_B_6" , :"SYS_B_7" , :"SYS_B_8" , :"
SYS_B_9" )
277 279 0.97 749386807
SELECT call_req.open_date, call_req.id FROM call_req WHERE call_
req.customer = :"SYS_B_0" AND call_req.active_flag = :"SYS_B_1"
ORDER BY call_req.open_date DESC
275 275 0.97 2816620377
INSERT INTO att_evt ( cancel_time, event_tmpl, fire_time, first_
fire_time, group_name, last_mod_dt, num_fire, obj_id, persid, st
art_time, status_flag, user_smag, wait_time, id ) VALUES ( null
, :"SYS_B_00" , :"SYS_B_01" , :"SYS_B_02" , :"SYS_B_03" ,
:"SYS_B_04" , :"SYS_B_05" , :"SYS_B_06" , :"SYS_B_07" , :"SY
269 269 0.94 3605948696
SELECT slatpl.del , slatpl.elapsed , slatpl.event , slatpl.last_
mod_by , slatpl.last_mod_dt , slatpl.object_type , slatpl.persid
, slatpl.service_type , slatpl.sym FROM slatpl WHERE slatpl.id
SQL ordered by Sharable Memory for DB: AHD Instance: ahd Snaps: 20 -21
-> End Sharable Memory Threshold: 1048576
Sharable Mem (b) Executions % Total Hash Value
23,912,520 231 13.6 139964375
SELECT anima.a_name, anima.t_persid, anima.t_method, anima.id FR
OM anima WHERE anima.t_persid LIKE :"SYS_B_0" ORDER BY anima.
a_name
18,314,292 26 10.4 380755726
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.ref_num LIKE :"SYS_B_00" ) AND ( call_req.group_id IN (
SELECT id FROM ctct WHERE id = :"SYS_B_01" OR id = :"SYS_B_02" O
R id = :"SYS_B_03" OR id = :"SYS_B_04" OR id = :"SYS_B_05" OR id
= :"SYS_B_06" OR id = :"SYS_B_07" OR id = :"SYS_B_08" OR id = :
12,365,844 107 7.0 1877135209
SELECT chg.open_date, chg.chg_ref_num, chg.id FROM chg WHERE ( c
hg.affected_contact = :"SYS_B_0" and chg.active_flag = :"SYS_B_1
" ) AND ( chg.affected_contact = :"SYS_B_2" ) ORDER BY chg.open
_date DESC
2,692,852 17 1.5 4181730075
SELECT ctct.c_last_name, ctct.c_first_name, ctct.c_middle_name,
ctct.c_public_phone, ctct.c_contact_num, ctct.c_org_id, ctct.c_l
_id, ctct.id FROM ctct, ct_ty WHERE ( ctct.c_last_name LIKE :"
SYS_B_0" AND ctct.c_ctp_id = ct_ty.id AND ct_ty.id = :"SYS_B_1"
AND ctct.del = :"SYS_B_2" AND ctct.id IN ( SELECT member FROM g
2,048,083 10 1.2 153455816
SELECT ctct.c_last_name, ctct.c_first_name, ctct.c_middle_name,
ctct.c_public_phone, ctct.c_contact_num, ctct.c_org_id, ctct.c_l
_id, ctct.id FROM ctct WHERE ( ctct.c_last_name LIKE :"SYS_B_0
" ) AND ( ( ctct.del = :"SYS_B_1" ) AND ( ctct.c_ctp_id = :"SYS_
B_2" AND ctct.alias = -:"SYS_B_3" ) ) ORDER BY ctct.c_last_name
1,653,628 3 0.9 1096419296
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.ref_num LIKE :"SYS_B_0" ) AND ( ( call_req.group_id IN (
SELECT group_id FROM grpmem WHERE member = :"SYS_B_1" ) ) or ca
ll_req.assignee = :"SYS_B_2" or call_req.customer = :"SYS_B_3" )
ORDER BY call_req.open_date DESC
SQL ordered by Version Count for DB: AHD Instance: ahd Snaps: 20 -21
-> End Version Count Threshold: 20
Version
Count Executions Hash Value
349 231 139964375
SELECT anima.a_name, anima.t_persid, anima.t_method, anima.id FR
OM anima WHERE anima.t_persid LIKE :"SYS_B_0" ORDER BY anima.
a_name
196 107 1877135209
SELECT chg.open_date, chg.chg_ref_num, chg.id FROM chg WHERE ( c
hg.affected_contact = :"SYS_B_0" and chg.active_flag = :"SYS_B_1
" ) AND ( chg.affected_contact = :"SYS_B_2" ) ORDER BY chg.open
_date DESC
127 26 380755726
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.ref_num LIKE :"SYS_B_00" ) AND ( call_req.group_id IN (
SELECT id FROM ctct WHERE id = :"SYS_B_01" OR id = :"SYS_B_02" O
R id = :"SYS_B_03" OR id = :"SYS_B_04" OR id = :"SYS_B_05" OR id
= :"SYS_B_06" OR id = :"SYS_B_07" OR id = :"SYS_B_08" OR id = :
36 17 4181730075
SELECT ctct.c_last_name, ctct.c_first_name, ctct.c_middle_name,
ctct.c_public_phone, ctct.c_contact_num, ctct.c_org_id, ctct.c_l
_id, ctct.id FROM ctct, ct_ty WHERE ( ctct.c_last_name LIKE :"
SYS_B_0" AND ctct.c_ctp_id = ct_ty.id AND ct_ty.id = :"SYS_B_1"
AND ctct.del = :"SYS_B_2" AND ctct.id IN ( SELECT member FROM g
33 10 153455816
SELECT ctct.c_last_name, ctct.c_first_name, ctct.c_middle_name,
ctct.c_public_phone, ctct.c_contact_num, ctct.c_org_id, ctct.c_l
_id, ctct.id FROM ctct WHERE ( ctct.c_last_name LIKE :"SYS_B_0
" ) AND ( ( ctct.del = :"SYS_B_1" ) AND ( ctct.c_ctp_id = :"SYS_
B_2" AND ctct.alias = -:"SYS_B_3" ) ) ORDER BY ctct.c_last_name
26 3 1096419296
SELECT call_req.open_date, call_req.id FROM call_req WHERE ( cal
l_req.ref_num LIKE :"SYS_B_0" ) AND ( ( call_req.group_id IN (
SELECT group_id FROM grpmem WHERE member = :"SYS_B_1" ) ) or ca
ll_req.assignee = :"SYS_B_2" or call_req.customer = :"SYS_B_3" )
ORDER BY call_req.open_date DESC
Instance Activity Stats for DB: AHD Instance: ahd Snaps: 20 -21
Statistic Total per Second per Trans
CPU used by this session 12,450 8.7 4.1
CPU used when call started 12,515 8.8 4.1
CR blocks created 53 0.0 0.0
DBWR buffers scanned 0 0.0 0.0
DBWR checkpoint buffers written 1,644 1.2 0.5
DBWR checkpoints 0 0.0 0.0
DBWR free buffers found 0 0.0 0.0
DBWR lru scans 0 0.0 0.0
DBWR make free requests 0 0.0 0.0
DBWR summed scan depth 0 0.0 0.0
DBWR transaction table writes 10 0.0 0.0
DBWR undo block writes 238 0.2 0.1
SQL*Net roundtrips to/from client 131,833 92.6 42.9
active txn count during cleanout 130 0.1 0.0
background checkpoints completed 0 0.0 0.0
background checkpoints started 0 0.0 0.0
background timeouts 2,161 1.5 0.7
branch node splits 0 0.0 0.0
buffer is not pinned count 3,147,925 2,210.6 1,024.1
buffer is pinned count 638,155 448.1 207.6
bytes received via SQL*Net from c 20,116,711 14,126.9 6,544.2
bytes sent via SQL*Net to client 33,961,169 23,849.1 11,047.9
calls to get snapshot scn: kcmgss 76,324 53.6 24.8
calls to kcmgas 6,266 4.4 2.0
calls to kcmgcs 110 0.1 0.0
change write time 25 0.0 0.0
cleanout - number of ktugct calls 145 0.1 0.1
cleanouts and rollbacks - consist 0 0.0 0.0
cleanouts only - consistent read 0 0.0 0.0
cluster key scan block gets 1,361 1.0 0.4
cluster key scans 1,146 0.8 0.4
commit cleanout failures: buffer 0 0.0 0.0
commit cleanout failures: callbac 3 0.0 0.0
commit cleanout failures: cannot 0 0.0 0.0
commit cleanouts 14,837 10.4 4.8
commit cleanouts successfully com 14,834 10.4 4.8
commit txn count during cleanout 106 0.1 0.0
consistent changes 2,123 1.5 0.7
consistent gets 3,336,864 2,343.3 1,085.5
consistent gets - examination 197,061 138.4 64.1
cursor authentications 71 0.1 0.0
data blocks consistent reads - un 2,123 1.5 0.7
db block changes 50,525 35.5 16.4
db block gets 47,774 33.6 15.5
deferred (CURRENT) block cleanout 7,940 5.6 2.6
dirty buffers inspected 0 0.0 0.0
enqueue conversions 29 0.0 0.0
enqueue releases 14,210 10.0 4.6
enqueue requests 14,210 10.0 4.6
enqueue waits 0 0.0 0.0
execute count 32,955 23.1 10.7
free buffer inspected 16 0.0 0.0
free buffer requested 140,283 98.5 45.6
hot buffers moved to head of LRU 950 0.7 0.3
immediate (CR) block cleanout app 0 0.0 0.0
immediate (CURRENT) block cleanou 2,804 2.0 0.9
Instance Activity Stats for DB: AHD Instance: ahd Snaps: 20 -21
Statistic Total per Second per Trans
index fast full scans (full) 157 0.1 0.1
index fetch by key 70,378 49.4 22.9
index scans kdiixs1 28,181 19.8 9.2
leaf node 90-10 splits 10 0.0 0.0
leaf node splits 76 0.1 0.0
logons cumulative 11 0.0 0.0
messages received 5,452 3.8 1.8
messages sent 5,452 3.8 1.8
no buffer to keep pinned count 0 0.0 0.0
no work - consistent read gets 3,085,481 2,166.8 1,003.7
opened cursors cumulative 4,561 3.2 1.5
parse count (failures) 0 0.0 0.0
parse count (hard) 412 0.3 0.1
parse count (total) 28,484 20.0 9.3
parse time cpu 426 0.3 0.1
parse time elapsed 469 0.3 0.2
physical reads 138,930 97.6 45.2
physical reads direct 0 0.0 0.0
physical writes 1,644 1.2 0.5
physical writes direct 0 0.0 0.0
physical writes non checkpoint 232 0.2 0.1
pinned buffers inspected 7 0.0 0.0
prefetched blocks 32,732 23.0 10.7
process last non-idle time 12,884,949,552 9,048,419.6 4,191,590.6
recursive calls 22,718 16.0 7.4
recursive cpu usage 226 0.2 0.1
redo blocks written 19,178 13.5 6.2
redo buffer allocation retries 0 0.0 0.0
redo entries 27,265 19.2 8.9
redo log space requests 0 0.0 0.0
redo log space wait time 0 0.0 0.0
redo size 8,488,216 5,960.8 2,761.3
redo synch time 74 0.1 0.0
redo synch writes 3,078 2.2 1.0
redo wastage 1,040,788 730.9 338.6
redo write time 75 0.1 0.0
redo writer latching time 0 0.0 0.0
redo writes 5,216 3.7 1.7
rollback changes - undo records a 6 0.0 0.0
rollbacks only - consistent read 233 0.2 0.1
rows fetched via callback 54,581 38.3 17.8
session connect time 12,884,949,552 9,048,419.6 4,191,590.6
session logical reads 3,384,638 2,376.9 1,101.1
session pga memory max 6,168,536 4,331.8 2,006.7
session uga memory 599,984 421.3 195.2
session uga memory max 9,592,864 6,736.6 3,120.7
shared hash latch upgrades - no w 27,737 19.5 9.0
shared hash latch upgrades - wait 84 0.1 0.0
sorts (disk) 0 0.0 0.0
sorts (memory) 6,834 4.8 2.2
sorts (rows) 3,229,994 2,268.3 1,050.8
summed dirty queue length 0 0.0 0.0
switch current to new buffer 990 0.7 0.3
table fetch by rowid 474,673 333.3 154.4
table fetch continued row 8 0.0 0.0
table scan blocks gotten 2,751,375 1,932.2 895.1
Instance Activity Stats for DB: AHD Instance: ahd Snaps: 20 -21
Statistic Total per Second per Trans
table scan rows gotten 55,928,200 39,275.4 18,194.0
table scans (long tables) 245 0.2 0.1
table scans (short tables) 3,383 2.4 1.1
transaction rollbacks 3 0.0 0.0
transaction tables consistent rea 0 0.0 0.0
transaction tables consistent rea 0 0.0 0.0
user calls 131,904 92.6 42.9
user commits 3,074 2.2 1.0
user rollbacks 0 0.0 0.0
workarea executions - onepass 0 0.0 0.0
workarea executions - optimal 8,438 5.9 2.7
write clones created in backgroun 0 0.0 0.0
write clones created in foregroun 0 0.0 0.0
Tablespace IO Stats for DB: AHD Instance: ahd Snaps: 20 -21
->ordered by IOs (Reads + Writes) desc
Tablespace
Av Av Av Av Buffer Av Buf
Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
AHD1_DATA
105,869 74 0.9 1.3 828 1 11,740 0.5
AHD1_IDX
38 0 7.4 1.0 563 0 0 0.0
PERFSTAT
372 0 3.6 1.0 0 0 0 0.0
UNDOTBS1
0 0 0.0 248 0 0 0.0
SYSTEM
6 0 6.7 1.0 5 0 0 0.0
File IO Stats for DB: AHD Instance: ahd Snaps: 20 -21
->ordered by Tablespace, File
Tablespace Filename
Av Av Av Av Buffer Av Buf
Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
AHD1_DATA E:\ORACLE\ORADATA\AHD\AHD1_DATA.ORA
53,454 38 0.9 1.3 432 0 5,949 0.5
E:\ORACLE\ORADATA\AHD\AHD2_DATA.ORA
52,415 37 0.9 1.3 396 0 5,791 0.5
AHD1_IDX E:\ORACLE\ORADATA\AHD\AHD1_IDX.ORA
38 0 7.4 1.0 563 0 0
PERFSTAT E:\ORACLE\ORADATA\AHD\PERFSTAT.ORA
372 0 3.6 1.0 0 0 0
SYSTEM E:\ORACLE\ORADATA\AHD\SYSTEM01.DBF
6 0 6.7 1.0 5 0 0
UNDOTBS1 E:\ORACLE\ORADATA\AHD\UNDOTBS01.DBF
0 0 248 0 0
Buffer Pool Statistics for DB: AHD Instance: ahd Snaps: 20 -21
-> Standard block size Pools D: default, K: keep, R: recycle
-> Default Pools for other block sizes: 2k, 4k, 8k, 16k, 32k
Free Write Buffer
Number of Cache Buffer Physical Physical Buffer Complete Busy
P Buffers Hit % Gets Reads Writes Waits Waits Waits
D 82,082 97.8 6,327,007 138,971 1,644 0 0 11,760
Instance Recovery Stats for DB: AHD Instance: ahd Snaps: 20 -21
-> B: Begin snapshot, E: End snapshot
Targt Estd Log File Log Ckpt Log Ckpt
MTTR MTTR Recovery Actual Target Size Timeout Interval
(s) (s) Estd IOs Redo Blks Redo Blks Redo Blks Redo Blks Redo Blks
B 75 26 2354 18057 17632 184320 17632
E 75 27 2967 23569 22952 184320 22952
Buffer Pool Advisory for DB: AHD Instance: ahd End Snap: 21
-> Only rows with estimated physical reads >0 are displayed
-> ordered by Block Size, Buffers For Estimate
Size for Size Buffers for Est Physical Estimated
P Estimate (M) Factr Estimate Read Factor Physical Reads
D 64 .1 8,008 261.38 4,357,231,706
D 128 .2 16,016 207.44 3,458,029,385
D 192 .3 24,024 143.22 2,387,570,894
D 256 .4 32,032 2.29 38,243,018
D 320 .5 40,040 1.89 31,541,321
D 384 .6 48,048 1.74 29,023,767
D 448 .7 56,056 1.69 28,232,064
D 512 .8 64,064 1.20 19,951,481
D 576 .9 72,072 1.11 18,529,925
D 640 1.0 80,080 1.04 17,367,752
D 656 1.0 82,082 1.00 16,670,129
D 704 1.1 88,088 0.97 16,124,256
D 768 1.2 96,096 0.91 15,155,822
D 832 1.3 104,104 0.90 15,055,099
D 896 1.4 112,112 0.89 14,839,567
D 960 1.5 120,120 0.88 14,668,682
D 1,024 1.6 128,128 0.87 14,479,726
D 1,088 1.7 136,136 0.84 13,988,866
D 1,152 1.8 144,144 0.70 11,723,518
D 1,216 1.9 152,152 0.61 10,156,857
D 1,280 2.0 160,160 0.20 3,281,883
Buffer wait Statistics for DB: AHD Instance: ahd Snaps: 20 -21
-> ordered by wait time desc, waits desc
Tot Wait Avg
Class Waits Time (s) Time (ms)
data block 11,754 6 0
PGA Aggr Target Stats for DB: AHD Instance: ahd Snaps: 20 -21
-> B: Begin snap E: End snap (rows dentified with B or E contain data
which is absolute i.e. not diffed over the interval)
-> PGA cache hit % - percentage of W/A (WorkArea) data processed only in-memory
-> Auto PGA Target - actual workarea memory target
-> W/A PGA Used - amount of memory used for all Workareas (manual + auto)
-> %PGA W/A Mem - percentage of PGA memory allocated to workareas
-> %Auto W/A Mem - percentage of workarea memory controlled by Auto Mem Mgmt
-> %Man W/A Mem - percentage of workarea memory under manual control
PGA Cache Hit % W/A MB Processed Extra W/A MB Read/Written
100.0 1,169 0
%PGA %Auto %Man
PGA Aggr Auto PGA PGA Mem W/A PGA W/A W/A W/A Global Mem
Target(M) Target(M) Alloc(M) Used(M) Mem Mem Mem Bound(K)
B 350 293 37.6 0.0 .0 .0 .0 17,920
E 350 293 37.5 0.2 .6 100.0 .0 17,920
PGA Aggr Target Histogram for DB: AHD Instance: ahd Snaps: 20 -21
-> Optimal Executions are purely in-memory operations
Low High
Optimal Optimal Total Execs Optimal Execs 1-Pass Execs M-Pass Execs
8K 16K 6,809 6,809 0 0
16K 32K 148 148 0 0
32K 64K 90 90 0 0
64K 128K 154 154 0 0
128K 256K 73 73 0 0
256K 512K 308 308 0 0
512K 1024K 374 374 0 0
1M 2M 171 171 0 0
2M 4M 217 217 0 0
4M 8M 10 10 0 0
PGA Memory Advisory for DB: AHD Instance: ahd End Snap: 21
-> When using Auto Memory Mgmt, minimally choose a pga_aggregate_target value
where Estd PGA Overalloc Count is 0
Estd Extra Estd PGA Estd PGA
PGA Target Size W/A MB W/A MB Read/ Cache Overalloc
Est (MB) Factr Processed Written to Disk Hit % Count
44 0.1 180,060.5 42,218.7 81.0 4
88 0.3 180,060.5 23,194.7 89.0 0
175 0.5 180,060.5 9,436.8 95.0 0
263 0.8 180,060.5 9,356.7 95.0 0
350 1.0 180,060.5 9,274.8 95.0 0
420 1.2 180,060.5 9,169.9 95.0 0
490 1.4 180,060.5 9,148.0 95.0 0
560 1.6 180,060.5 9,148.0 95.0 0
630 1.8 180,060.5 9,148.0 95.0 0
700 2.0 180,060.5 9,148.0 95.0 0
1,050 3.0 180,060.5 9,148.0 95.0 0
1,400 4.0 180,060.5 9,148.0 95.0 0
2,100 6.0 180,060.5 3,983.3 98.0 0
2,800 8.0 180,060.5 3,983.3 98.0 0
Rollback Segment Stats for DB: AHD Instance: ahd Snaps: 20 -21
->A high value for "Pct Waits" suggests more rollback segments may be required
->RBS stats may not be accurate between begin and end snaps when using Auto Undo
managment, as RBS may be dynamically created and dropped as needed
Trans Table Pct Undo Bytes
RBS No Gets Waits Written Wraps Shrinks Extends
0 29.0 0.00 0 0 0 0
1 975.0 0.00 122,796 0 0 0
2 1,244.0 0.00 1,094,706 10 0 5
3 816.0 0.00 118,596 0 0 0
4 1,430.0 0.00 212,754 2 0 0
5 1,716.0 0.00 291,940 2 0 0
6 1,287.0 0.00 197,900 0 0 0
7 1,674.0 0.00 279,160 0 0 0
8 1,031.0 0.00 148,216 0 0 0
9 947.0 0.00 141,870 0 0 0
10 834.0 0.00 117,422 0 0 0
Rollback Segment Storage for DB: AHD Instance: ahd Snaps: 20 -21
->Optimal Size should be larger than Avg Active
RBS No Segment Size Avg Active Optimal Size Maximum Size
0 385,024 0 385,024
1 2,220,032 455,412 2,220,032
2 2,088,960 333,026 2,220,032
3 2,220,032 456,101 2,220,032
4 2,220,032 474,584 3,268,608
5 2,220,032 480,865 3,268,608
6 2,220,032 513,967 3,268,608
7 2,220,032 480,785 2,220,032
8 2,220,032 496,182 2,220,032
9 2,220,032 486,763 2,220,032
10 2,220,032 430,016 6,414,336
Undo Segment Summary for DB: AHD Instance: ahd Snaps: 20 -21
-> Undo segment block stats:
-> uS - unexpired Stolen, uR - unexpired Released, uU - unexpired reUsed
-> eS - expired Stolen, eR - expired Released, eU - expired reUsed
Undo Undo Num Max Qry Max Tx Snapshot Out of uS/uR/uU/
TS# Blocks Trans Len (s) Concurcy Too Old Space eS/eR/eU
1 395 2,900,725 5 1 0 0 0/0/0/0/0/0
Undo Segment Stats for DB: AHD Instance: ahd Snaps: 20 -21
-> ordered by Time desc
Undo Num Max Qry Max Tx Snap Out of uS/uR/uU/
End Time Blocks Trans Len (s) Concy Too Old Space eS/eR/eU
13-Feb 15:04 96 ######## 4 1 0 0 0/0/0/0/0/0
13-Feb 14:54 299 ######## 5 1 0 0 0/0/0/0/0/0
Latch Activity for DB: AHD Instance: ahd Snaps: 20 -21
->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
willing-to-wait latch get requests
->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
->"Pct Misses" for both should be very close to 0.0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
Consistent RBA 5,216 0.0 0 0
FOB s.o list latch 34 0.0 0 0
SQL memory manager latch 1 0.0 0 462 0.0
SQL memory manager worka 40,347 0.0 0 0
active checkpoint queue 1,261 0.0 0 0
archive control 163 0.0 0 0
archive process latch 29 0.0 0 0
cache buffer handles 378 0.0 0 0
cache buffers chains 6,836,244 0.4 0.0 0 266,617 0.0
cache buffers lru chain 244,157 0.0 0.0 0 140,432 0.0
channel handle pool latc 21 0.0 0 0
channel operations paren 960 0.0 0 0
checkpoint queue latch 86,982 0.0 0 2,337 0.0
child cursor hash table 6,464 0.0 0.0 0 0
dml lock allocation 15,005 0.0 0 0
dummy allocation 21 0.0 0 0
enqueue hash chains 28,447 0.0 0 0
enqueues 8,689 0.0 0 0
event group latch 11 0.0 0 0
file number translation 4,079 0.0 0 0
hash table column usage 38 0.0 0 187,596 0.0
hash table modification 1 0.0 0 0
job_queue_processes para 23 0.0 0 0
ktm global data 4 0.0 0 0
kwqit: protect wakeup ti 45 0.0 0 0
lgwr LWN SCN 5,328 0.4 0.0 0 0
library cache 342,865 0.2 0.0 0 342 0.6
library cache load lock 452 0.0 0 0
library cache pin 197,662 0.0 0.0 0 0
library cache pin alloca 124,035 0.0 0.0 0 0
list of block allocation 55 0.0 0 0
messages 30,779 0.0 0.0 0 0
mostly latch-free SCN 5,459 1.8 0.0 0 0
multiblock read objects 194,822 0.0 0.0 0 0
ncodef allocation latch 23 0.0 0 0
object stats modificatio 618 0.0 0 0
post/wait queue 10,441 0.0 0 3,078 0.0
process allocation 11 0.0 0 11 0.0
process group creation 21 0.0 0 0
redo allocation 37,773 0.0 0.0 0 0
redo copy 0 0 27,274 0.0
redo writing 17,880 0.0 0 0
row cache enqueue latch 169,423 0.0 0.0 0 0
row cache objects 169,795 0.0 0 3 0.0
sequence cache 38 0.0 0 0
session allocation 15,580 0.0 0 0
session idle bit 269,419 0.0 0.0 0 0
session switching 23 0.0 0 0
session timer 478 0.0 0 0
shared pool 104,427 0.1 0.0 0 0
Latch Activity for DB: AHD Instance: ahd Snaps: 20 -21
->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
willing-to-wait latch get requests
->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
->"Pct Misses" for both should be very close to 0.0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
sim partition latch 0 0 32 0.0
simulator hash latch 217,119 0.0 0.0 0 0
simulator lru latch 16,247 0.0 0 902 0.4
sort extent pool 29 0.0 0 0
transaction allocation 36 0.0 0 0
transaction branch alloc 23 0.0 0 0
undo global data 19,973 0.0 0 0
user lock 42 0.0 0 0
Latch Sleep breakdown for DB: AHD Instance: ahd Snaps: 20 -21
-> ordered by misses desc
Get Spin &
Latch Name Requests Misses Sleeps Sleeps 1->4
cache buffers chains 6,836,244 26,201 46 0/0/0/0/0
library cache 342,865 778 5 773/5/0/0/0
shared pool 104,427 125 3 122/3/0/0/0
Latch Miss Sources for DB: AHD Instance: ahd Snaps: 20 -21
-> only latches with sleeps are shown
-> ordered by name, sleeps desc
NoWait Waiter
Latch Name Where Misses Sleeps Sleeps
cache buffers chains kcbgtcr: kslbegin excl 0 32 30
cache buffers chains kcbrls: kslbegin 0 7 13
cache buffers chains kcbzwb 0 4 3
cache buffers chains kcbgtcr: fast path 0 3 0
library cache kglic 0 2 0
library cache kglobpn: child: 0 2 0
library cache kgllkdl: child: cleanup 0 1 0
shared pool kghalo 0 2 0
shared pool kghalp 0 1 0
Child Latch Statistics DB: AHD Instance: ahd Snaps: 20 -21
-> only latches with sleeps/gets > 1/100000 are shown
-> ordered by name, gets desc
Child Get Spin &
Latch Name Num Requests Misses Sleeps Sleeps 1->4
cache buffers chains 439 28,269 1,276 1 0/0/0/0/0
cache buffers chains 269 26,297 842 1 0/0/0/0/0
cache buffers chains 1010 17,482 49 2 0/0/0/0/0
cache buffers chains 260 11,141 20 1 0/0/0/0/0
cache buffers chains 324 9,454 29 1 0/0/0/0/0
cache buffers chains 840 7,235 20 1 0/0/0/0/0
cache buffers chains 46 6,868 25 1 0/0/0/0/0
cache buffers chains 835 6,799 26 2 0/0/0/0/0
cache buffers chains 202 6,768 17 1 0/0/0/0/0
cache buffers chains 740 6,573 38 2 0/0/0/0/0
cache buffers chains 592 6,508 30 1 0/0/0/0/0
cache buffers chains 436 6,485 25 2 0/0/0/0/0
cache buffers chains 513 6,443 16 1 0/0/0/0/0
cache buffers chains 844 6,436 28 1 0/0/0/0/0
cache buffers chains 117 6,423 25 1 0/0/0/0/0
cache buffers chains 389 6,381 25 1 0/0/0/0/0
cache buffers chains 116 6,349 29 1 0/0/0/0/0
cache buffers chains 51 6,340 34 1 0/0/0/0/0
cache buffers chains 914 6,259 31 1 0/0/0/0/0
cache buffers chains 713 6,249 24 1 0/0/0/0/0
cache buffers chains 465 6,198 27 2 0/0/0/0/0
cache buffers chains 416 6,193 27 1 0/0/0/0/0
cache buffers chains 432 6,155 34 1 0/0/0/0/0
cache buffers chains 583 6,152 23 2 0/0/0/0/0
cache buffers chains 126 6,147 35 1 0/0/0/0/0
cache buffers chains 879 6,043 21 1 0/0/0/0/0
cache buffers chains 110 6,010 25 1 0/0/0/0/0
cache buffers chains 138 6,010 25 1 0/0/0/0/0
cache buffers chains 472 6,002 31 1 0/0/0/0/0
cache buffers chains 908 5,964 20 1 0/0/0/0/0
cache buffers chains 860 5,950 23 1 0/0/0/0/0
cache buffers chains 71 5,945 29 3 0/0/0/0/0
cache buffers chains 20 5,780 28 1 0/0/0/0/0
cache buffers chains 932 5,759 25 1 0/0/0/0/0
cache buffers chains 866 5,610 22 1 0/0/0/0/0
cache buffers chains 989 5,454 34 2 0/0/0/0/0
cache buffers chains 1005 5,434 40 1 0/0/0/0/0
library cache 6 47,067 52 3 49/3/0/0/0
shared pool 1 99,771 124 3 121/3/0/0/0
Top 5 Logical Reads per Segment for DB: AHD Instance: ahd Snaps: 20 -21
-> End Segment Logical Reads Threshold: 10000
Subobject Obj. Logical
Owner Tablespace Object Name Name Type Reads %Total
AHD AHD1_DATA CALL_REQ TABLE 1,714,928 51.19
AHD AHD1_DATA CTCT TABLE 1,169,360 34.90
AHD AHD1_IDX SYS_C003707 INDEX 89,152 2.66
AHD AHD1_DATA CNOTE TABLE 66,272 1.98
AHD AHD1_IDX CALL_REQ_X5 INDEX 61,360 1.83
Top 5 Physical Reads per Segment for DB: AHD Instance: ahd Snaps: 20 -21
-> End Segment Physical Reads Threshold: 1000
Subobject Obj. Physical
Owner Tablespace Object Name Name Type Reads %Total
AHD AHD1_DATA CALL_REQ TABLE 132,989 95.95
AHD AHD1_DATA CTCT TABLE 5,325 3.84
AHD AHD1_DATA CI_AUDIT_TRAILS_GU_I INDEX 43 .03
AHD AHD1_DATA ACT_LOG TABLE 38 .03
AHD AHD1_DATA CI_EXT_CALLS_GUID INDEX 36 .03
Top 5 Buf. Busy Waits per Segment for DB: AHD Instance: ahd Snaps: 20 -21
-> End Segment Buffer Busy Waits Threshold: 100
Buffer
Subobject Obj. Busy
Owner Tablespace Object Name Name Type Waits %Total
AHD AHD1_DATA CALL_REQ TABLE 11,751 99.95
AHD AHD1_DATA CTCT TABLE 6 .05
Dictionary Cache Stats for DB: AHD Instance: ahd Snaps: 20 -21
->"Pct Misses" should be very low (< 2% in most cases)
->"Cache Usage" is the number of cache entries being used
->"Pct SGA" is the ratio of usage to allocated size for that cache
Get Pct Scan Pct Mod Final
Cache Requests Miss Reqs Miss Reqs Usage
dc_files 30 0.0 0 0 15
dc_histogram_defs 3,022 3.9 0 0 1,919
dc_object_ids 22,961 0.1 0 0 1,181
dc_objects 1,092 9.2 0 0 1,026
dc_profiles 11 0.0 0 0 1
dc_rollback_segments 168 0.0 0 0 22
dc_segments 5,519 0.1 0 0 1,334
dc_sequences 1 0.0 0 1 2
dc_tablespace_quotas 3 0.0 0 3 2
dc_tablespaces 25,902 0.0 0 0 16
dc_user_grants 127 0.0 0 0 22
dc_usernames 110 0.0 0 0 18
dc_users 26,077 0.0 0 0 30
Library Cache Activity for DB: AHD Instance: ahd Snaps: 20 -21
->"Pct Misses" should be very low
Get Pct Pin Pct Invali-
Namespace Requests Miss Requests Miss Reloads dations
CLUSTER 19 0.0 16 0.0 0 0
INDEX 315 0.0 315 0.0 0 0
SQL AREA 27,908 0.0 94,300 0.5 38 0
TABLE/PROCEDURE 3,793 2.6 6,017 6.5 55 0
TRIGGER 20 0.0 20 0.0 0 0
Shared Pool Advisory for DB: AHD Instance: ahd End Snap: 21
-> 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
Estd
Shared Pool SP Estd Estd Estd Lib LC Time
Size for Size Lib Cache Lib Cache Cache Time Saved Estd Lib Cache
Estim (M) Factr Size (M) Mem Obj Saved (s) Factr Mem Obj Hits
88 .6 81 11,169 59,229 1.0 6,202,663
104 .7 96 13,308 59,237 1.0 6,207,373
120 .8 112 15,603 59,277 1.0 6,228,405
136 .9 127 18,086 59,348 1.0 6,265,370
152 1.0 142 19,501 59,379 1.0 6,295,279
168 1.1 157 21,035 59,426 1.0 6,314,861
184 1.2 172 22,038 59,455 1.0 6,325,903
200 1.3 187 23,807 59,459 1.0 6,328,446
216 1.4 202 25,911 59,460 1.0 6,329,386
232 1.5 217 28,194 59,461 1.0 6,330,245
248 1.6 232 29,884 59,462 1.0 6,330,914
264 1.7 248 31,127 59,462 1.0 6,331,222
280 1.8 263 32,878 59,463 1.0 6,331,563
296 1.9 278 34,121 59,463 1.0 6,331,898
312 2.1 295 36,139 59,463 1.0 6,332,102
SGA Memory Summary for DB: AHD Instance: ahd Snaps: 20 -21
SGA regions Size in Bytes
Database Buffers 687,865,856
Fixed Size 455,196
Redo Buffers 929,792
Variable Size 293,601,280
sum 982,852,124
SGA breakdown difference for DB: AHD Instance: ahd Snaps: 20 -21
Pool Name Begin value End value % Diff
java free memory 75,497,472 75,497,472 0.00
large free memory 41,943,040 41,943,040 0.00
shared 1M buffer 2,098,176 2,098,176 0.00
shared Checkpoint queue 846,912 846,912 0.00
shared FileOpenBlock 695,504 695,504 0.00
shared KGK heap 3,756 3,756 0.00
shared KGLS heap 1,230,944 1,438,740 16.88
shared KQR L PO 2,064 2,064 0.00
shared KQR M PO 2,480,924 2,514,220 1.34
shared KQR S PO 383,036 383,036 0.00
shared KQR S SO 5,636 5,636 0.00
shared KSXR pending messages que 841,036 841,036 0.00
shared KSXR receive buffers 1,033,000 1,033,000 0.00
shared MTTR advisory 97,412 97,412 0.00
shared PL/SQL DIANA 624,112 624,112 0.00
shared PL/SQL MPCODE 422,640 422,640 0.00
shared PLS non-lib hp 2,068 2,068 0.00
shared character set object 323,724 323,724 0.00
shared dictionary cache 1,610,880 1,610,880 0.00
shared errors 35,964 35,964 0.00
shared event statistics per sess 1,718,360 1,718,360 0.00
shared fixed allocation callback 300 300 0.00
shared free memory 26,982,004 26,841,956 -0.52
shared joxs heap init 4,220 4,220 0.00
shared kgl simulator 3,980,240 3,996,976 0.42
shared library cache 54,425,164 53,999,624 -0.78
shared message pool freequeue 834,752 834,752 0.00
shared miscellaneous 8,126,704 8,177,516 0.63
shared parameters 1,632 1,632 0.00
shared sessions 410,720 410,720 0.00
shared sim memory hea 377,656 377,656 0.00
shared sql area 66,513,080 66,768,476 0.38
shared subheap 45,216 45,216 0.00
shared table definiti 1,200 2,752 129.33
shared trigger defini 340 340 0.00
shared trigger inform 1,292 1,292 0.00
shared trigger source 100 100 0.00
buffer_cache 687,865,856 687,865,856 0.00
fixed_sga 455,196 455,196 0.00
log_buffer 918,528 918,528 0.00
init.ora Parameters for DB: AHD Instance: ahd Snaps: 20 -21
End value
Parameter Name Begin value (if different)
aq_tm_processes 1
background_dump_dest E:\oracle\admin\ahd\bdump
compatible 9.2.0.0.0
control_files E:\oracle\oradata\ahd\CONTROL01.C
core_dump_dest E:\oracle\admin\ahd\cdump
cursor_sharing SIMILAR
db_block_size 8192
db_cache_size 687865856
db_domain
db_file_multiblock_read_count 8
db_name ahd
db_writer_processes 2
dispatchers (PROTOCOL=TCP) (SERVICE=ahdXDB)
fast_start_mttr_target 300
hash_join_enabled TRUE
instance_name ahd
java_pool_size 75497472
job_queue_processes 10
large_pool_size 41943040
log_archive_dest_1 location=c:\archive
log_archive_format arc%d_%t_%s.arc
log_archive_start TRUE
open_cursors 300
pga_aggregate_target 367001600
processes 150
query_rewrite_enabled FALSE
remote_login_passwordfile EXCLUSIVE
shared_pool_size 159383552
sort_area_size 10485760
star_transformation_enabled FALSE
timed_statistics TRUE
undo_management AUTO
undo_retention 3600
undo_tablespace UNDOTBS1
user_dump_dest E:\oracle\admin\ahd\udump
End of ReportI am getting buffer busy waits on some tables.
Users are not experiencing any problem.Looks like you got bit by the CTD troll while sleeping.
Note also that (if I'm reading the report alright) out of 23 mins you have 6 seconds accounted to buffer busy waits.
Read the sample chapter here. -
Statspack interpreting help - buffer busy waits
Hi,
I've got statspack report from 9.2.0.8 DB, cpu_count = 12 , there is 'buffer busy waits' in top 5 .
Is there a problem ?
DB Name DB Id Instance Inst Num Release Cluster Host
XXXX 138180125 XXXX 1 9.2.0.8.0 NO X1
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 35980 14-Jul-10 01:00:02 17 8.8
End Snap: 35984 14-Jul-10 05:00:01 17 8.8
Elapsed: 239.98 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 3,072M Std Block Size: 8K
Shared Pool Size: 512M Log Buffer: 4,096K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 317,746.23 4,498.59
Logical reads: 11,150.77 157.87
Block changes: 2,134.89 30.23
Physical reads: 466.05 6.60
Physical writes: 133.62 1.89
User calls: 82.42 1.17
Parses: 67.92 0.96
Hard parses: 0.02 0.00
Sorts: 106.77 1.51
Logons: 0.03 0.00
Executes: 516.58 7.31
Transactions: 70.63
% Blocks changed per Read: 19.15 Recursive Call %: 95.00
Rollback per transaction %: 0.00 Rows per Sort: 4.34
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.03 Redo NoWait %: 100.00
Buffer Hit %: 95.91 In-memory Sort %: 100.00
Library Hit %: 100.00 Soft Parse %: 99.98
Execute to Parse %: 86.85 Latch Hit %: 99.65
Parse CPU to Parse Elapsd %: 7.82 % Non-Parse CPU: 99.91
Shared Pool Statistics Begin End
Memory Usage %: 43.53 43.92
% SQL with executions>1: 64.89 70.00
% Memory for SQL w/exec>1: 55.95 61.64
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
SQL*Net message from dblink 797,760 44,575 41.69
PL/SQL lock timer 1,207 34,992 32.73
db file sequential read 3,297,249 17,047 15.94
buffer busy waits 1,558,995 3,987 3.73
CPU time 3,204 3.00
Statistic Total per Second per Trans
enqueue timeouts 299 0.0 0.0
enqueue waits 425 0.0 0.0
exchange deadlocks 41 0.0 0.0
execute count 7,438,297 516.6 7.3
failed probes on index block recl 13 0.0 0.0
free buffer inspected 107,385 7.5 0.1
free buffer requested 7,344,870 510.1 7.2
hot buffers moved to head of LRU 2,332,802 162.0 2.3
immediate (CR) block cleanout app 356,492 24.8 0.4
immediate (CURRENT) block cleanou 1,751,731 121.7 1.7
index crx upgrade (found) 7 0.0 0.0
index crx upgrade (positioned) 25,604 1.8 0.0
index fast full scans (full) 888 0.1 0.0
index fetch by key 6,008,269 417.3 5.9
index scans kdiixs1 2,343,163 162.7 2.3
leaf node 90-10 splits 330 0.0 0.0
leaf node splits 13,681 1.0 0.0
logons cumulative 447 0.0 0.0
messages received 2,760,503 191.7 2.7
messages sent 2,760,503 191.7 2.7
no buffer to keep pinned count 0 0.0 0.0
no work - consistent read gets 89,143,249 6,190.9 87.7
opened cursors cumulative 978,462 68.0 1.0
parse count (failures) 0 0.0 0.0
parse count (hard) 243 0.0 0.0
parse count (total) 977,939 67.9 1.0
parse time cpu 276 0.0 0.0
parse time elapsed 3,531 0.3 0.0
physical reads 6,710,684 466.1 6.6
physical reads direct 140,520 9.8 0.1
physical writes 1,924,011 133.6 1.9
physical writes direct 149,434 10.4 0.2
physical writes non checkpoint 1,160,293 80.6 1.1
pinned buffers inspected 88,165 6.1 0.1
prefetched blocks 2,965,135 205.9 2.9
prefetched blocks aged out before 1,485 0.1 0.0
process last non-idle time 14,401 1.0 0.0
recovery blocks read 0 0.0 0.0
recursive calls 22,566,381 1,567.2 22.2
recursive cpu usage 314,662 21.9 0.3
redo blocks written 9,712,190 674.5 9.6
redo buffer allocation retries 483 0.0 0.0
redo entries 17,147,344 1,190.9 16.9
redo log space requests 760 0.1 0.0
redo log space wait time 1,255 0.1 0.0
redo ordering marks 21 0.0 0.0
redo size 4,575,228,028 317,746.2 4,498.6
redo synch time 73,190 5.1 0.1
redo synch writes 333,440 23.2 0.3
redo wastage 240,517,096 16,703.7 236.5
redo write time 136,628 9.5 0.1
redo writer latching time 56 0.0 0.0
redo writes 865,653 60.1 0.9
rollback changes - undo records a 60,510 4.2 0.1
rows fetched via callback 3,948,006 274.2 3.9
session connect time 0 0.0 0.0
Statistic Total per Second per Trans
session logical reads 160,559,938 11,150.8 157.9
session pga memory 223,020,424 15,488.6 219.3
session pga memory max 841,058,240 58,410.9 827.0
session uga memory 682,912,005,944 47,427,738.5 671,472.1
session uga memory max 505,627,192 35,115.4 497.2
shared hash latch upgrades - no w 1,661,152 115.4 1.6
shared hash latch upgrades - wait 101 0.0 0.0
sorts (disk) 2 0.0 0.0
sorts (memory) 1,537,403 106.8 1.5
sorts (rows) 6,669,072 463.2 6.6
summed dirty queue length 71,613 5.0 0.1
switch current to new buffer 80,971 5.6 0.1
table fetch by rowid 79,047,167 5,489.8 77.7
table fetch continued row 5,013,545 348.2 4.9
table scan blocks gotten 10,328,271 717.3 10.2
table scan rows gotten 381,848,913 26,519.1 375.5
table scans (long tables) 82 0.0 0.0
table scans (short tables) 1,117,114 77.6 1.1
transaction rollbacks 32,437 2.3 0.0
transaction tables consistent rea 39 0.0 0.0
transaction tables consistent rea 82,904 5.8 0.1
user calls 1,186,828 82.4 1.2
user commits 1,017,037 70.6 1.0
user rollbacks 0 0.0 0.0
workarea executions - onepass 7 0.0 0.0
workarea executions - optimal 2,291,005 159.1 2.3
write clones created in backgroun 3 0.0 0.0
write clones created in foregroun 711 0.1 0.0
Class Waits Time (s) Time (ms)
data block 1,549,301 4,015 3
segment header 253 1 2
undo block 2,574 0 0
undo header 2,209 0 0
extent map 2 0 5
Eq Requests Succ Gets Failed Gets Waits Time (ms) Time (s)
TX 1,749,961 1,749,961 0 202 6.47 1
HW 20,789 20,789 0 223 .40 0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
Consistent RBA 866,126 0.0 0.0 0 0
FIB s.o chain latch 594 0.0 0 0
FOB s.o list latch 2,891 0.0 0.0 0 0
SQL memory manager latch 4 0.0 0 4,793 0.0
SQL memory manager worka 3,266,221 0.0 0.0 0 0
active checkpoint queue 1,905,423 0.5 0.0 0 0
archive control 28 0.0 0 0
cache buffer handles 12,070 0.0 0 0
cache buffers chains 387,508,854 0.6 0.0 134 11,212,815 0.1
cache buffers lru chain 1,946,036 0.0 0.0 0 14,681,284 0.2
channel handle pool latc 668 0.0 0 0
channel operations paren 12,460 0.0 0.0 0 0
checkpoint queue latch 209,244,852 0.0 0.0 0 1,775,314 0.0
child cursor hash table 3,240 0.7 0.0 0 0
commit callback allocati 16 0.0 0 0
dictionary lookup 13 0.0 0 0
dml lock allocation 5,900,238 0.3 0.0 0 0
dummy allocation 894 0.2 0.0 0 0
enqueue hash chains 19,444,854 0.1 0.0 0 0
enqueues 9,380,299 0.7 0.0 0 0
event group latch 288 0.0 0 0
event range base latch 3 0.0 0 0
global tx hash mapping 4,988,645 0.0 0.0 0 0
hash table column usage 82 0.0 0 1,783 0.0
job workq parent latch 1 100.0 0.0 0 242 15.3
job_queue_processes para 287 0.0 0 0
ktm global data 265 0.0 0 0
lgwr LWN SCN 868,053 0.1 0.0 0 0
library cache 29,540,874 0.1 0.0 0 37 0.0
library cache load lock 102 0.0 0 0
library cache pin 24,145,848 0.0 0.0 0 0
library cache pin alloca 3,988,997 0.0 0.0 0 0
list of block allocation 363,684 0.0 0.0 0 0
loader state object free 912 0.0 0 0
longop free list parent 479 0.0 0 60 1.7
message pool operations 100 1.0 0.0 0 0
messages 8,036,523 0.3 0.0 0 0
mostly latch-free SCN 878,016 1.0 0.0 0 0
multiblock read objects 922,048 0.1 0.0 0 0
ncodef allocation latch 230 0.0 0 0
object stats modificatio 2,100 0.0 0 0
post/wait queue 709,603 0.0 0.0 0 334,338 0.0
process allocation 576 0.0 0 288 0.0
process group creation 576 0.2 0.0 0 0
redo allocation 18,881,467 0.7 0.0 0 0
redo copy 0 0 17,155,579 0.1
redo writing 4,513,716 0.2 0.0 0 0
resumable state object 48 0.0 0 0
row cache enqueue latch 3,556,148 0.1 0.0 0 0
row cache objects 6,671,783 0.1 0.0 0 0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
sequence cache 1,533,482 0.0 0.0 0 0
session allocation 15,194,281 0.1 0.0 0 0
session idle bit 3,005,477 0.0 0.0 0 0
session switching 230 0.0 0 0
session timer 4,825 0.0 0 0
shared pool 2,114,153 0.0 0.0 0 0
sim partition latch 0 0 10,243 0.6
simulator hash latch 8,460,492 0.0 0.0 0 0
simulator lru latch 223,868 0.0 0.3 0 470,589 0.1
sort extent pool 1,823 0.5 0.0 0 0
temporary table state ob 16 0.0 0 0
transaction allocation 533,964 0.0 0 0
transaction branch alloc 1,259,723 0.1 0.0 0 0
undo global data 17,460,173 0.0 0.0 0 14,976 0.0
user lock 906 0.1 0.0 0 0
Get Spin &
Latch Name Requests Misses Sleeps Sleeps 1->4
cache buffers chains 387,508,854 2,447,832 12,701 2435135/1269
3/4/0/0
redo allocation 18,881,467 131,460 343 131118/341/1
/0/0
enqueues 9,380,299 62,436 122 62314/122/0/
0/0
library cache 29,540,874 38,344 80 38264/80/0/0
/0
messages 8,036,523 25,266 28 25238/28/0/0
/0
dml lock allocation 5,900,238 19,220 25 19195/25/0/0
/0
enqueue hash chains 19,444,854 10,510 27 10483/27/0/0
/0
active checkpoint queue la 1,905,423 9,896 36 9860/36/0/0/
0
library cache pin 24,145,848 8,451 17 8434/17/0/0/
0
mostly latch-free SCN 878,016 8,423 17 8406/17/0/0/
0
session allocation 15,194,281 8,290 33 8257/33/0/0/
0
redo writing 4,513,716 7,235 13 7222/13/0/0/
0
undo global data 17,460,173 4,113 8 4105/8/0/0/0
row cache objects 6,671,783 3,680 4 3676/4/0/0/0
row cache enqueue latch 3,556,148 2,015 1 2014/1/0/0/0
checkpoint queue latch 209,244,852 1,756 6 1750/6/0/0/0
transaction branch allocat 1,259,723 1,236 7 1229/7/0/0/0
shared pool 2,114,153 808 2 806/2/0/0/0
library cache pin allocati 3,988,997 649 1 648/1/0/0/0
cache buffers lru chain 1,946,036 588 13 575/13/0/0/0
multiblock read objects 922,048 469 8 461/8/0/0/0
sequence cache 1,533,482 333 1 332/1/0/0/0
session idle bit 3,005,477 97 1 96/1/0/0/0
Consistent RBA 866,126 55 1 54/1/0/0/0
simulator lru latch 223,868 33 9 24/9/0/0/0
post/wait queue 709,603 27 1 26/1/0/0/0
NoWait Waiter
Latch Name Where Misses Sleeps Sleeps
active checkpoint queue kcbbacq: scan active check 0 36 36
cache buffers chains kcbgtcr: kslbegin excl 0 10,706 10,084
cache buffers chains kcbrls: kslbegin 0 937 1,577
cache buffers chains kcbzwb 0 371 388
cache buffers chains kcbgtcr: fast path 0 223 174
cache buffers chains kcbgcur: kslbegin 0 86 114
cache buffers chains kcbget: pin buffer 0 57 47
cache buffers chains kcbzib: finish free bufs 0 54 27
cache buffers chains kcbchg: kslbegin: bufs not 0 52 89
cache buffers chains kcbnlc 0 46 37
cache buffers chains kcbzgb: scan from tail. no 0 42 0
cache buffers chains kcbzib: multi-block read: 0 25 0
cache buffers chains kcbget: exchange rls 0 12 3
cache buffers chains kcbchg: kslbegin: call CR 0 12 80
cache buffers chains kcbget: exchange 0 10 8
cache buffers chains kcbnew 0 9 0
cache buffers chains kcbcge 0 1 0
cache buffers chains kcbgtcr 0 1 0
cache buffers chains kcbbxsv 0 1 16
cache buffers chains kcbkzs 0 1 3
cache buffers chains kcbbic2 0 1 2
cache buffers chains kcbbic1 0 1 5
cache buffers lru chain kcbzgb: multiple sets nowa 10,344 10 0
cache buffers lru chain kcbbiop: lru scan 112 3 0
checkpoint queue latch kcbklbc: Link buffer into 0 6 0
dml lock allocation ktaiam 0 15 16
dml lock allocation ktaidm 0 10 9
enqueue hash chains ksqgtl3 0 17 11
enqueue hash chains ksqrcl 0 9 15
enqueue hash chains ksqcnl 0 1 1
enqueues ksqdel 0 60 50
enqueues ksqgel: create enqueue 0 60 56
enqueues ksqies 0 2 16
lgwr LWN SCN kcs023 0 9 0
library cache kglpnc: child 0 29 29
library cache kglupc: child 0 25 22
library cache kgllkdl: child: cleanup 0 11 2
library cache kglpndl: child: before pro 0 5 4
library cache kglhdgn: child: 0 3 13
library cache kglhdgc: child: 0 2 1
library cache kglpndl: child: after proc 0 2 0
library cache kgldte: child 0 0 1 2
library cache kglpin: child: heap proces 0 1 0
library cache kglobpn: child: 0 1 5
library cache pin kglpndl 0 6 1
library cache pin kglpnc: child 0 6 8
library cache pin kglupc 0 5 4
library cache pin alloca kglpnal 0 1 1
messages ksarcv 0 12 5
messages ksarcv: after wait 0 8 19
messages ksaamb: after wakeup 0 8 4
mostly latch-free SCN kcslcu3 0 8 17
mostly latch-free SCN kcsnew_scn_rba 0 1 0
Latch Name Where Misses Sleeps Sleeps
multiblock read objects kcbzib: mbr get 0 4 4
multiblock read objects kcbzib: normal mbr free 0 4 4
post/wait queue ksliwat:add:nowait 0 1 0
redo allocation kcrfwr 0 322 248
redo allocation kcrfwi: more space 0 14 88
redo allocation kcrfwi: before write 0 7 7
redo writing kcrfwcr 0 9 12
redo writing kcrfwint: rba scn pair 0 2 0
redo writing kcrfwint: after write 0 2 6
row cache enqueue latch kqreqa 0 1 1
row cache objects kqrpre: find obj 0 3 1
row cache objects kqrpfl: not dirty 0 1 1
sequence cache kdnss 0 1 1
session allocation ksuprc 0 14 5
session allocation ksudlc 0 10 7
session allocation ksucri 0 6 14
session allocation ksuxds: not user session 0 3 7
session idle bit ksupuc: clear busy 0 1 0
shared pool kghalo 0 1 0
shared pool kghupr1 0 1 2
simulator lru latch kcbs_simulate: simulate se 0 8 9
simulator lru latch kcbs_lookup_setid 0 1 0
transaction branch alloc ktcbba 0 4 2
transaction branch alloc ktcbod 0 2 3
transaction branch alloc ksupuc 0 1 2
undo global data ktudba: KSLBEGIN 0 8 7
Top 5 Logical Reads per Segment for DB: XXXXX Instance: XXXXX Snaps: 35980
-> End Segment Logical Reads Threshold: 10000
Subobject Obj. Logical
Owner Tablespace Object Name Name Type Reads %Total
xxxxxxxx XXXXXDATA TAB1TABLE TABLE 39,838,592 37.65
Top 5 Physical Reads per Segment for DB: XXXXX Instance: XXXXX Snaps: 3598
-> End Segment Physical Reads Threshold: 1000
Subobject Obj. Physical
Owner Tablespace Object Name Name Type Reads %Total
xxxxxxxx XXXXXDATA TAB1TABLE TABLE 3,568,038 58.64
Top 5 Buf. Busy Waits per Segment for DB: XXXXX Instance: XXXXX Snaps: 359
-> End Segment Buffer Busy Waits Threshold: 100
Buffer
Subobject Obj. Busy
Owner Tablespace Object Name Name Type Waits %Total
xxxxxxxx XXXXXDATA TAB1TABLE 1,421,043 91.65
xxxxxxxx XXXXXDATA IDX_SOMEIDX INDEX 62,638 4.04
xxxxxxxx XXXXXTABLE TABLE 26,914 1.74
----------So, for me It looks like :
TAB1TABLE is buffer busy deliver but there are no inserts reported for that table,
I've checked that TAB1TABLE tablespace is NO ASSM and extent management is local with uniform size 1M .
So this is not obvious free list problem . Kind of strange for me .
Any ideas greatly appreciated :).
Regards.
Greguser10388717 wrote:
Hi,
I've got statspack report from 9.2.0.8 DB, cpu_count = 12 , there is 'buffer busy waits' in top 5 .
Is there a problem ?
DB Name DB Id Instance Inst Num Release Cluster Host
XXXX 138180125 XXXX 1 9.2.0.8.0 NO X1
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 35980 14-Jul-10 01:00:02 17 8.8
End Snap: 35984 14-Jul-10 05:00:01 17 8.8
Elapsed: 239.98 (mins)
----------So, for me It looks like :
TAB1TABLE is buffer busy deliver but there are no inserts reported for that table,
I've checked that TAB1TABLE tablespace is NO ASSM and extent management is local with uniform size 1M .
So this is not obvious free list problem . Kind of strange for me .
Any ideas greatly appreciated :).We can't tell if you have a problem - only you (or your users) can know.
But you've shown us a statspack snapshot covering 4 hours and in that time you've reported about 30 hours of database time (sum foreground "in-database" waits and CPU), with a fairly small number of sessions which (allowing for background sessions) means most of your foreground sessions seem to be working pretty much non-stop for the entire period. I could take a guess and say that you would like some of the work that they're doing completed sooner.
The largest fraction of your time goes into waiting for messages from db link, with an average time of 55ms - maybe you have a network problem, maybe you have a query that has a bad choice of execution path that is doing lots of unnecessary trips to the remote db, maybe the queries that get to the remote db could be made much more efficient. (Look for 'sql ordered by executions' in a statspack from the remote db for clues).
pl/sql lock timer is the next big chunk of time - but this is deliberately coded waits in pl/sql (dbms_lock.sleep) maybe that's supposed to be happening, but you could check the logic to see if some "slow" processes are actually coded to sleep much longer than necessary.
Your db file sequential reads (single block reads) are, on average taking 5.5 ms - which is reasonable, so you have to ask if the number (and we know which table a lot of them are hitting) is reasonable. This brings us to your buffer busy waits: these can be caused by updates and deletes as well as inserts, but in 9i they are also caused by "read by other session" - so the buffer busy wait may simple be one session waiting for another session to complete a db file sequential read.
I'd look at your "SQL ordered by Reads" to see if you have some inefficient execution plans (or poorly defined indexes) that result in large amounts of the critical table being constantly re-read. It's possible that you can eliminate redundant visits to this table and reduce your I/O, BBW, and CPU in one shot.
Regards
Jonathan Lewis -
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)
2) Where buffer contents in this case are dumped ?
Thanks and best regards,
Pavel
Edited by: Pavel on Jul 19, 2012 9:49 PMPavel wrote:
Hello dear gurus!
After shutting database with option "abort"
we have unconsisten state of datafiles.That's expected as checkpoint didn't happen. Issue a startup and instance recovery should take care of everything.
I ask to explain :
1) - does the ARCH background processes flash whole redo buffer into redolog ?ARCH process or LGWR? How does this relates to your current question?
(In other words how reached consistency if all redo log groups was in active state before shutting down ?)As I said, issue a startup of the instance and it should take care of the things.
2) Where buffer contents in this case are dumped ?Which case? Your questions are a bit fuzzy you see. Let's stick to one question at one time and follow it shall we?
Aman.... -
As written in Oracle documents.
oracle records each and every tranjaction in redo buffer and as soon as writes to redo file.
As redo file is full it switches to another redo file.
While switching redo file it archives the the current redo file and the new redo file will be the current redo
if it is in archive log mode and the archival process is started.
And also written that in the event failure the redo file is needed to recover database when the
database starts. Now I want to know I have a transaction which is not fit in a redo file and it goes to another redo file.
What will happen if again failuer occured and I have restarted the database.Does it recovere from both of the redo files?
If Yes: What will happen if my transaction doesn't fit in all of the redofiles?
if no: How does it rollback up to last commited transaction if it is not in current redo logfile?
thank You very much.Perhaps you should try to learn by both reading and doing (testing!), since this a quite vital "concept".
I think Oracle9i Backup and Recovery Concepts A96519-01, Chapter 1 - the basic concepts adn explanation of the involved structures, is a good place to start. -
Hi all,
does the LGWR only write transactions that are COMMITED from the redo buffer to the redo logs? or they will write uncommited transactions to the redo log as well?
please advise.
thanksOk now lets clarify some things...
The redlog groups can containt some uncomitted statements... but they will be come permanent only if they are commited... you can read that from the link above:
http://www.dbasupport.com/oracle/ora9i/background_process01.shtml
or here: http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm
Sometimes, if more buffer space is needed, LGWR writes redo log entries before a transaction is committed. These entries become permanent only if the transaction is later committed.
and now to your questions:
not the manipulated value itself but the old value from the undo management (which self was comitted by oracle)...Ok a little example:
You modify a value from 0 to 1. But you don't commit this transaction. An undo entry is generated in the undo tablespace (if you are using automatic undo) for that modification. Then a checkpoint occur in your database (for example, you made this by hand). So the DBWR will write down the modified value "1" to the table in the datafiles, but you have not commited the statement.
So now your instance crashes... how should oracle know what the old value was?
Yes oracle have to rollback the uncomitted statement from the undo record to "0".
Lets make the situation even worst... maybe while the crash you lost some datafiles from the undo tablespace... so your undo management is not consistent.
And now? Yes oracle have all the uncomitted statements from the undo tablespace also "commited" in the redo log files... to rebuild the undo managment. So the old value 0 is a commited transaction in the redo log files for the undo tablespace...
how does oracle knows which records in the redo logs are not commited and which are the one which are commited? which recoreds to rollback and not roll foward perhaps during recovery.hmm i think you should read some documentation about that phases first... all commited statements are assigned by a SCN...
Regards
Stefan -
REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서
제품 : ORACLE SERVER
작성날짜 : 2000-08-28
REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서
========================================================================
redo log buffer 사용 시 wait 비율이 높은 경우 log buffer의 크기 조정 외에도
redo에 관한 latch를 조정함으로써 성능을 향상시킬 수 있다.
여기에서는 redo allocation latch와 redo copy latch의 작동 원리와, tuning
방법 등을 설명한다. 그리고 8i에서의 변경 사항도 포함하였다.
1. redo entry를 redo log buffer에 할당하는 방법
database에 변경 작업을 수행하는 server process는 PGA 부분에 변경 작업에 대한
redo entry를 만든다. 그리고 이것을 redo log buffer에 옮기는데, 이 때 먼저
할당될 redo log buffer의 부분을 allocation하고, 그 이후에 allocation 된
redo log buffer 공간에, PGA 상에 만들어 둔 redo entry를 copy한다.
Oracle은 SGA 내에서 발생하는 source code의 action의 serialization을 위해서
latch를 사용한다. 즉, log buffer에서 redo entry를 save시킬 공간을 할당하는
작업 절차도 먼저 latch를 부여받은 process가 작업하는 것이고, 할당받은
공간에 redo entry를 copy시키는 작업 절차도 latch를 획득한 다음에만 수행
가능하다.
2. redo allocation latch
모든 redo entry는 db에 수행된 작업 순서대로 redo log file에 기록되어야 한다.
그러므로 redo log buffer에 redo entry를 할당하는 작업은 항상 serialization을
유지하여야 하고, 그런 이유로 인해서 redo allocation latch는 instance마다
하나만이 가능하다.
server process는 이 redo allocation latch를 잡고, redo buffer 내에 redo
entry를 저장시킬 위치를 확보한다.
다음에 설명할 redo copy latch를 사용할 수 없는 환경에서는, redo buffer 내의
확보한 공간 내에 redo entry를 copy하는 작업도 이 redo allocation latch를
잡은 후 진행한다.
3. redo copy latch (LOG_SIMULTANEOUS_COPIES)
redo allocation latch 하나를 이용하여 redo buffer 내의 공간을 할당하고,
redo entry를 copy하는 것은, redo buffer에 대한 작업을 모두 serialize시켜
performance에 지장을 줄 수 있다.
redo entry가 위치할 공간을 확보하는 작업은 반드시 시간 순서대로 위치해야
하기 때문에 모두 순서가 유지되어야 하는 작업이지만, 일단 확보한 log
buffer의 공간에 redo entry를 copy하는 작업은 동시에 수행되어도 지장이
없다. 이것을 위해 복수 개의 redo copy latch를 지정하여, redo entry를 확보된
영역에 동시에 copy가 가능하도록 하였다. 단 이러한 copy 작업은 CPU의
작업이므로 CPU가 한장이면, 동시 작업이 불가능하여 이 redo copy latch를
사용하는 것이 의미가 없어 사용이 불가능하다.
즉, redo buffer에 대한 작업이 redo copy latch를 사용하면, 다음과 같은
절차로 수행된다.
(1) A server process가 redo allocation latch를 잡고 redo buffer 내의 공간을
할당한 후 redo allocation latch는 푼다.
(2) B server process가 redo allocation latch를 잡고 redo buffer의 새로운
공간을 할당받은 다음 redo allocation latch를 푼다.
(3) A process가 redo copy latch를 잡고 A process가 만든 PGA 내의 redo
entry를 (1)번 단계에서 확보한 공간에 copy한다.
이와 동시에 B process도 또 다른 redo copy latch를 잡고, (2)번 단계에서
확보한 공간에 redo entry를 copy한다.
redo copy latch의 갯수는 log_simultaneous_copies parameter에 의해 지정된다.
CPU가 하나이면 이 값은 0가 되어, redo allocation latch를 이용해 redo
allocation과 redo copy 작업을 한번에 수행하게 되며, default는 CPU_COUNT 값이
된다. CPU_COUNT는 operating system layer에 의해 자동으로 결정되며, init.ora
file에 명시적으로 지정하지 않는 parameter이다.
즉, multi CPU 환경에서는 자동으로 redo copy latch를 사용하게 되는 것이다.
default 외의 값을 사용하고자 한다면, $ORACLE_HOME/dbs/initSID.ora file 내에
다음과 같이 지정하면 된다. 최대값의 제한은 없다.
log_simultaneous_copies=n
redo copy latch의 장점을 정리하면, redo buffer의 공간 할당을 위해 선행된
작업이 redo entry를 copy할 때까지 기다리지 않아도 되며, redo copy 작업 자체도
병렬도 수행이 가능하다는 것이다.
4. LOG_SMALL_ENTRY_MAX_SIZE
CPU를 복수개를 사용하는 경우 redo copy latch를 사용하는 것이 redo log buffer
내의 작업에 대한 wait는 줄일 수 있음은 위에서 살펴보았다. 그런데 매우 작은
redo entry의 경우 redo entry를 copy하는 데 시간이 거의 걸리지 않은 상황에서
굳이 redo allocation과 redo copy를 별도의 latch를 이용하여 두 단계로 나누어
작업하는 것이 성능 향상에 도움이 되지 않을 수도 있다. 오히려 copy하는 데 시간이
거의 안 걸린다면 redo allocation latch 하나를 잡고서 redo allocation과 redo
copy를 모두 수행하는 것이 나을 수도 있다.
그렇다면 redo copy latch를 사용하는 상황에서 이 latch를 사용하지 않아도 되는,
작은 redo entry의 기준을 설정할 필요가 있다.
이것을 결정하는 parameter가 log_small_entry_max_size이다.
즉, log_small_entry_max_size보다 큰 redo entry는 redo copy를 위해 redo copy
latch를 사용하지만, 이보다 작은 크기의 redo entry에 대해서는 redo allocation
latch를 이용하여 redo allocation과 copy를 모두 수행하게 되는 것이다.
아무리 작은 redo entry라도 redo copy latch를 사용하게 하고 싶다면 이 값을
0으로 지정하면 된다.
5. tuning point
multi-CPU 환경에서 redo copy latch의 갯수를 늘리거나, log_small_entry_max_size
값을 줄여야 할때는 redo buffer에 contention이 발생하는 경우이다.
redo buffer에 contention이 발생하는지 확인하는 방법은 다음과 같다.
SQL>select name, gets, misses from v$latch where name = 'redo allocation';
이 값의 결과에서 gets에 대한 misses의 비율이 1%를 넘는다면 이것은 contention
이 존재한다고 판단될 수 있다. 물론 이것은 절대적인 기준은 아니어서, 1% 미만
이라 하더라도 miss 율을 더 줄이고자 할 수도 있다.
contention이 발생하면 log_simultaneous_copies의 값을 CPU의 약 두배 정도까지
증가시키는 것이 권고할 만하고, log_small_entry_max_size의 값도 0에 가까운
값으로 줄여서 contention의 상황을 지속적으로 살펴보아야 한다.
6. 8i 에서의 변경 사항
Oracle 8.1 에서는 위에서 설명한 두 parameter가 모두 나타나지 않는다.
log_small_entry_max_size parameter는 완전히 없어졌으며,
log_simultaneous_copies 값은 CPU_COUNT의 두배로 무조건 설정이 된다.
이 CPU_COUNT는 앞에서 설명한 것과 같이 operating system layer에 의해
자동으로 결정되는 parameter로 CPU의 갯수를 나타낸다.
log_simultaneous_copies가 자동으로 CPU 갯수의 2배로 지정되는 것은 모든
환경에서 대부분 최적이라고 볼 수 있으므로, user가 변경하지 않도록 하기 위해
parameter 부분에 display가 안 되도록 하였다.제품 : ORACLE SERVER
작성날짜 : 2000-08-28
REDO ALLOCATION LATCH와 REDO COPY LATCH에 대해서
========================================================================
redo log buffer 사용 시 wait 비율이 높은 경우 log buffer의 크기 조정 외에도
redo에 관한 latch를 조정함으로써 성능을 향상시킬 수 있다.
여기에서는 redo allocation latch와 redo copy latch의 작동 원리와, tuning
방법 등을 설명한다. 그리고 8i에서의 변경 사항도 포함하였다.
1. redo entry를 redo log buffer에 할당하는 방법
database에 변경 작업을 수행하는 server process는 PGA 부분에 변경 작업에 대한
redo entry를 만든다. 그리고 이것을 redo log buffer에 옮기는데, 이 때 먼저
할당될 redo log buffer의 부분을 allocation하고, 그 이후에 allocation 된
redo log buffer 공간에, PGA 상에 만들어 둔 redo entry를 copy한다.
Oracle은 SGA 내에서 발생하는 source code의 action의 serialization을 위해서
latch를 사용한다. 즉, log buffer에서 redo entry를 save시킬 공간을 할당하는
작업 절차도 먼저 latch를 부여받은 process가 작업하는 것이고, 할당받은
공간에 redo entry를 copy시키는 작업 절차도 latch를 획득한 다음에만 수행
가능하다.
2. redo allocation latch
모든 redo entry는 db에 수행된 작업 순서대로 redo log file에 기록되어야 한다.
그러므로 redo log buffer에 redo entry를 할당하는 작업은 항상 serialization을
유지하여야 하고, 그런 이유로 인해서 redo allocation latch는 instance마다
하나만이 가능하다.
server process는 이 redo allocation latch를 잡고, redo buffer 내에 redo
entry를 저장시킬 위치를 확보한다.
다음에 설명할 redo copy latch를 사용할 수 없는 환경에서는, redo buffer 내의
확보한 공간 내에 redo entry를 copy하는 작업도 이 redo allocation latch를
잡은 후 진행한다.
3. redo copy latch (LOG_SIMULTANEOUS_COPIES)
redo allocation latch 하나를 이용하여 redo buffer 내의 공간을 할당하고,
redo entry를 copy하는 것은, redo buffer에 대한 작업을 모두 serialize시켜
performance에 지장을 줄 수 있다.
redo entry가 위치할 공간을 확보하는 작업은 반드시 시간 순서대로 위치해야
하기 때문에 모두 순서가 유지되어야 하는 작업이지만, 일단 확보한 log
buffer의 공간에 redo entry를 copy하는 작업은 동시에 수행되어도 지장이
없다. 이것을 위해 복수 개의 redo copy latch를 지정하여, redo entry를 확보된
영역에 동시에 copy가 가능하도록 하였다. 단 이러한 copy 작업은 CPU의
작업이므로 CPU가 한장이면, 동시 작업이 불가능하여 이 redo copy latch를
사용하는 것이 의미가 없어 사용이 불가능하다.
즉, redo buffer에 대한 작업이 redo copy latch를 사용하면, 다음과 같은
절차로 수행된다.
(1) A server process가 redo allocation latch를 잡고 redo buffer 내의 공간을
할당한 후 redo allocation latch는 푼다.
(2) B server process가 redo allocation latch를 잡고 redo buffer의 새로운
공간을 할당받은 다음 redo allocation latch를 푼다.
(3) A process가 redo copy latch를 잡고 A process가 만든 PGA 내의 redo
entry를 (1)번 단계에서 확보한 공간에 copy한다.
이와 동시에 B process도 또 다른 redo copy latch를 잡고, (2)번 단계에서
확보한 공간에 redo entry를 copy한다.
redo copy latch의 갯수는 log_simultaneous_copies parameter에 의해 지정된다.
CPU가 하나이면 이 값은 0가 되어, redo allocation latch를 이용해 redo
allocation과 redo copy 작업을 한번에 수행하게 되며, default는 CPU_COUNT 값이
된다. CPU_COUNT는 operating system layer에 의해 자동으로 결정되며, init.ora
file에 명시적으로 지정하지 않는 parameter이다.
즉, multi CPU 환경에서는 자동으로 redo copy latch를 사용하게 되는 것이다.
default 외의 값을 사용하고자 한다면, $ORACLE_HOME/dbs/initSID.ora file 내에
다음과 같이 지정하면 된다. 최대값의 제한은 없다.
log_simultaneous_copies=n
redo copy latch의 장점을 정리하면, redo buffer의 공간 할당을 위해 선행된
작업이 redo entry를 copy할 때까지 기다리지 않아도 되며, redo copy 작업 자체도
병렬도 수행이 가능하다는 것이다.
4. LOG_SMALL_ENTRY_MAX_SIZE
CPU를 복수개를 사용하는 경우 redo copy latch를 사용하는 것이 redo log buffer
내의 작업에 대한 wait는 줄일 수 있음은 위에서 살펴보았다. 그런데 매우 작은
redo entry의 경우 redo entry를 copy하는 데 시간이 거의 걸리지 않은 상황에서
굳이 redo allocation과 redo copy를 별도의 latch를 이용하여 두 단계로 나누어
작업하는 것이 성능 향상에 도움이 되지 않을 수도 있다. 오히려 copy하는 데 시간이
거의 안 걸린다면 redo allocation latch 하나를 잡고서 redo allocation과 redo
copy를 모두 수행하는 것이 나을 수도 있다.
그렇다면 redo copy latch를 사용하는 상황에서 이 latch를 사용하지 않아도 되는,
작은 redo entry의 기준을 설정할 필요가 있다.
이것을 결정하는 parameter가 log_small_entry_max_size이다.
즉, log_small_entry_max_size보다 큰 redo entry는 redo copy를 위해 redo copy
latch를 사용하지만, 이보다 작은 크기의 redo entry에 대해서는 redo allocation
latch를 이용하여 redo allocation과 copy를 모두 수행하게 되는 것이다.
아무리 작은 redo entry라도 redo copy latch를 사용하게 하고 싶다면 이 값을
0으로 지정하면 된다.
5. tuning point
multi-CPU 환경에서 redo copy latch의 갯수를 늘리거나, log_small_entry_max_size
값을 줄여야 할때는 redo buffer에 contention이 발생하는 경우이다.
redo buffer에 contention이 발생하는지 확인하는 방법은 다음과 같다.
SQL>select name, gets, misses from v$latch where name = 'redo allocation';
이 값의 결과에서 gets에 대한 misses의 비율이 1%를 넘는다면 이것은 contention
이 존재한다고 판단될 수 있다. 물론 이것은 절대적인 기준은 아니어서, 1% 미만
이라 하더라도 miss 율을 더 줄이고자 할 수도 있다.
contention이 발생하면 log_simultaneous_copies의 값을 CPU의 약 두배 정도까지
증가시키는 것이 권고할 만하고, log_small_entry_max_size의 값도 0에 가까운
값으로 줄여서 contention의 상황을 지속적으로 살펴보아야 한다.
6. 8i 에서의 변경 사항
Oracle 8.1 에서는 위에서 설명한 두 parameter가 모두 나타나지 않는다.
log_small_entry_max_size parameter는 완전히 없어졌으며,
log_simultaneous_copies 값은 CPU_COUNT의 두배로 무조건 설정이 된다.
이 CPU_COUNT는 앞에서 설명한 것과 같이 operating system layer에 의해
자동으로 결정되는 parameter로 CPU의 갯수를 나타낸다.
log_simultaneous_copies가 자동으로 CPU 갯수의 2배로 지정되는 것은 모든
환경에서 대부분 최적이라고 볼 수 있으므로, user가 변경하지 않도록 하기 위해
parameter 부분에 display가 안 되도록 하였다. -
oracle : 9i
os : linux
log : archive
dg : primary
Production : Yes
The instance is up. the performace is poor due to redospace wait.
I checked the following.
1. select (sw.value)*100/lw.valuefrom v$sysstat sw, v$sysstat lwwhere sw.name='redo log space requests' and lw.name='redo writes';
24.9544131
2. Parameters
log_checkpoint_interval integer 0
log_checkpoint_timeout integer 1800
log_checkpoints_to_alert boolean TRUE
log_buffer integer 524288
3. SELECT name, value
FROM SYS.v_$sysstat
WHERE NAME in ('redo buffer allocation retries',
'redo log space wait time');
redo buffer allocation retries 5216940
redo log space wait time 40519121
4. Select name, value from v$sysstat
Where name in ('redo log space requests', 'redo entries'); 2
redo entries 785620472
redo log space requests 1295431
Other than restarting the server, Any action can be taken ?1. Make sure your archiving destination isn't getting
full. If ARCH can't archive, LGWR can't switch, the
log buffer fills up and users then have to wait until
it unclogs.
space is enough . File is getting generated and able to transport also.
2. Make sure you have sufficient ARCH processes. As a
rough rule of thumb, LGWR can fill a log about three
times faster than ARCH can copy it. Therefore, there
is always a risk of ARCH getting bogged down with a
backlog of unarchived logs. If that happens, LGWR
will eventually get to a point where it can't
switch... and the log buffer fills up etc etc. ARCH
is supposed to be self-tuning (that is, extra ARCH
processes are spawned automatically). But you may
want to set log_archive_max_processes to provide a
minimum number of processes to start with (yeah, the
name of the parameter and its job are very confusing!
MAX_PROCESSES actually specifies a minimum (and
initial) number of processes!)
log_archive_max_processes integer 2
need to increase further?
3. Make sure you have sufficient log groups.If you've
only the minimum two, for example, LGWR will likely
be unable to switch back to log 1 when it's finished
in log 2, because log 1 is still being archived and
checkpointed. If LGWR waits, the log buffer fills up,
users have to wait until space becomes free once
more... With lots of log groups, however, LGWR can
switch into group 3, group 4, group 5 and so on
before having to switch back to attempt to re-use
group 1. I'd generally recommend a minimum of 4
groups.
SQL> select group#, (bytes)/(1024* 1024) from v$log;
GROUP# (BYTES)/(1024*1024)
1 5
2 5
3 5
I wll add 1 more group as per your suggestion
4. Make sure your logs are sufficiently large. Small
logs switch quicker, and hence LGWR can catch up with
itself more readily. If the logs are big, the rate of
switching slows down, but incremental checkpointing
means you don't build up a huge backlog of checkpoint
work to perform when the switch finally happens. Few
switches that don't have to do much will help keep
LGWR able to work, and if LGWR can keep clearing the
log buffer, users won't experience redo space waits.
5. Put your redo logs on your best hardware. If
you've got a mix of very fast disks and very ordinary
disks, put your online logs on the good stuff. If
you've got RAID 5 for the data files, don't put your
redo logs on it. Use RAID1+0 ideally, or RAID0 with
multiplexing. Keep the redo subsystem fast, in other
words.
running on RAID0 and archive logs are on san device
6. Related: keep the IO done to redo logs away from
the IO done to data files and anything else. Anything
which disrupts LGWR's ability to clear the log buffer
efficiently will increase your risk of redo space
waits.
Maybe you are looking for
-
Request for developers to include the Dell Quadro FX 3450 in their beta linux flashplayer for 10.1
request for developers to include the Dell Quadro FX 3450 in their beta linux flashplayer for 10.1. i'm guessing it wouldn't be hard to do. its the same chip that is used in the Nvidia Geforce 6800. It has NV42GL core processor. please don't leav
-
Arctic Cooling VGA Silencer + Zalman CNPS7000 = Fit?
I'm thinking about getting an Arctic Cooling VGA Silencer for my Hercules 9800 Pro, but I was wondering if the back piece really fits between the AGP card and the Zalman CNPS7000. Right now my gfx has the special stock cooling on, a.k.a Hercules-styl
-
Function Module for finding all the users in an org unit?
Hi, is there a function module or a table by which we can find all the users within a purchasing group of purchasing organisatiopn unit. Looking for a quick response. Regards, Neha
-
Where to find how to use JSF and database operation(eg. JDBC) together?
Thanks very much!
-
Suggest to better design the view?
Hello Experts, we are in the process of designing a huge User Interface using WDJ for our client. And this would contain many views which has to render few UI Elements based on the End Users action. For eg., in a view there will be a few default elem