Performance of Database
Hi all ,
I a, having 9.2.0.6.0. database.
when developers executes some batch job(running around 1 hour).They are saying it is responding very slow.Which view i need to check what wait events are there and caluse of slowness .Like where i need to find the cause .
V$waitstat
V$session_wait
V$system_event
which view (column) i need to go for...steps
can u put some light on it .
Thanks
Rohit Mathur
first look at which sqls are active and running on database:
set lines 233
select /*+ ordered */ to_char(s.sid,'99999'),
substr(username,1,8),
substr(t.sql_text,1,60),
nvl(last_call_et,0) TIME_sec,
t.hash_value,
substr(w.event,1,30) WAIT_EV,
substr(machine,1,10) MACHINE
from v$session s,v$sqltext t,v$session_wait w
where s.sql_address=t.address
and s.sql_HASH_VALUE=t.HASH_VALUE
and w.sid=s.sid
and username between 'AAAAAAAAA' and 'ZZZZZZZZZ'
and s.status='ACTIVE'
and t.piece=0
--and upper(sql_text) not like 'BEGIN%'
order by TIME_SEC
For the ones with high TIME_SEC value, run following script put its HASH_VALUE as input to see execution plan:
UNDEFINE H_VALUE
select
to_char(ID,'999') ID,substr(LPAD(' ',depth,' ')||OPERATION||' '||OPTIONS,1,40) Operation,
substr(OBJECT_NAME,1,25) Name,
substr(OPTIMIZER,1,10) OPTIMIZER,
CARDINALITY ,
Bytes,
Cost
from
v$sql_plan
where
HASH_VALUE=&&H_VALUE
--and child_number=0
order by
child_number,ID
select
to_char(ID,'999')||'- Filter: '||FILTER_PREDICATES ACCESS_FILTER
from
v$sql_plan
where
HASH_VALUE=&&H_VALUE and FILTER_PREDICATES is not null and FILTER_PREDICATES <> ' '
union
select
to_char(ID,'999')||'- Access: '||ACCESS_PREDICATES ACCESS_FILTER
from
v$sql_plan
where
HASH_VALUE=&H_VALUE and ACCESS_PREDICATES is not null --and ACCESS_PREDICATES <> ' '
order by ACCESS_FILTER
however, if batch job runs thousands of short TIME_sec sqls, then this method is useless. In this case you should check executions column of v$sqlarea view in order to see if there is a huge increase in execution number of any sql. Then you should focus on those sqls.
regards,
erkan
Similar Messages
-
Hello,
I am working on Oracle10.2.0.4 and HP-UX .
The requerement is to prepare a presantation on health of database on daily basis like when the load was low , I/O etc... in Graphs ..
How we can track performance of database?
Need to use any 3rd party tools or Oracle inbuilt tools , if any ?
Any Idea...
Edited by: oradba11 on Dec 15, 2010 7:40 PMDear oradba11,
You can preserve the AWR snapshots and also if you go the the EM Performance tab and at the upper right corner you will see "View Data". Select the historical one slide the periods. Take a screen shot of that graph and add it to your presentation.
If you also want to see the events in details, click on the event (USER I/O, CPU Used etc) and see the top SQLs and sessions there.
I have written those because you need graphs. If you want to have the numbers, you need to use AWR or statspack.
Regards.
Ogan -
[open] Performance of Database
Hello Gurus
I have around 5 databases Dev01,Dev02,Dev03,Dev04,Dev05 in my server
To increase the performance of one Dev04 DB i decrease the resources(sga_max_size,shared_pool_size,db_cache_size) for other DBs and increase the resources of Dev04 DB upto maximun extended
But i am observered the performance of Dev04 DB is poor
Is there any suggestion/tricks to increase or decraese resources for DB to perform better
Thanks in advanceIt would be a little tough to say what to do with the information that you have provided. The first most important missing part is the database version(4 digits). Alot has changed with the versions so what and why can be different based on it.
It would be required for you to see that what's happening on the Dev 4 db that its slow. The parameters , even though given generously doesn't gurantee that there would be a performance boost all the time. If there is a hard parse issue in the statements itself than it won't matter how much shared pool you allocate,it will eventually get filled up. Changing the parameter and expecting performance gain is called instance tuning and its highly unlikely that it would be of much use.
You have mentioned high resource utilization in the db. Did you check that in the system itself is not choked up due to resource crunch? There are commands like sar, top, vmstat which can help you in doing this. The objective is to remove anything over the o/s itself which is causing it.
Once you are done with this, you should come to the db and check which are the areas that may have beocme the contention point,for example, due to heavy parsing of the statemen aka hard parsing of the statements, cpu would be used veyr heavily. This may cause the resource crunch also. The best way to check this would be to generate STatspack or AWR report, depending on the version of your db. Generate that and post it here than it would be a little accurate to advice you over the performance gain.
HTH
Aman.... -
Performance of Database Objects
Hi,
Curious as to if anyone has any tricks involving
improving performance of updating database objects
in the database? For instance passing a list of changes?
I am mimicking java objects.
Thanks so much!Mike,
Check out the JDBC online doc for Oracle's performance enhancements at http://otn.oracle.com/docs/products/oracle9i/doc_library/901_doc/java.901/a90211/oraperf.htm#1056233.
Regards,
Geoff
Hi,
Curious as to if anyone has any tricks involving
improving performance of updating database objects
in the database? For instance passing a list of changes?
I am mimicking java objects.
Thanks so much! -
"Perform whole database Recovery" Host Credentials problem
Hello,
I have minimal knowledge of the Oracle database system but currently I need to recover a Oracle 10G database on a Windows Server 2003 Standard edition.
Im trying to use the Oracle Enterprise Manager. Im logged into the instance with SYS as SYSDBA. On the Perform Recovery page there are fields for "Host Credentials" Could someone explain to me what credentials EM is asking for. Whatever account I try to use EM gives a Validation Error stating
Error - Connection to host as user test failed: ERROR: Wrong password for user
Ive tried both local and Active Directory accounts that have full admin rights on the Host machine. With the AD account I tried using just the user name and allso domain\username. The page asks for "To perform recovery, supply operating system login credentials to access the target database." which sounds like the account has to have both access to the host and the database. Does that mean I have to create an external account in the instance? I even tried that but im not sure I configured it properly.Well found the solution. Atleast to this problem. Had to give the account "Log on as batch job" rights under Local Policy -> User Rights Assignment
-
Performance chart -- Database Error Io exception: The Network Adapter
Hi all,
I migrate my grid control repository to a new HOST and a new OMS.
Everything went right but on two of our databases if I click on the performance chart the database login screen appears.
After I insert he right parameter system try to log on and throw following error.
Database Error
Io exception: The Network Adapter could not establish the connectionSearching the web / metalink I find something like some wrong parameter but on the same hosts are multiple instances there do not have this problem.
Does anyone have an idea ?.
Thanks
*THey Rob.
there was a search domain missing in the resolf.conf.
Well done.
*T -
How to improve the performance of Database
Hi all,
Reporting Database backup from OLTP database daily morning,from reporting DB users are spooling the report.But Reporting DB is always slow (Death).User can't spool any reports.
Here details:-
DB size:120GB(mdf),20GB(ldf) seperate drive
Max degree of Parallelism -0
Cost threshold of parallelism-25
Any important settings i need to check or how can i improve my database performance.
Thanks
cost threshold for parallelism
cost threshold for parallelism
Thanks - SelvaKumarSubramaniam.Please MARK AS ANSWER, if my answer is useful to U.If you run the query that generates report in SSMS query window, does it also run slowly? Try recompile the stored procedure and re-run the report.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
Performance Problem Database Server on Solaris 10 5/08 (Update 5) v890 Box
Hello,
I am having performance problems on Solaris 10 5/08 (Update 5) Production server below I have mentioned the details information about the system and some command iostat and vmstat reports:
Sun Fire V890
Ram 32 GB
Physical CPU 8 (Logical 16)
Application Oracle 10G
Raid 1
1) iostat report
extended device statistics tty
device r/s w/s kr/s kw/s wait actv svc_t %w %b tin tout
md100 0.3 7.0 2.4 7.0 0.0 0.2 38.5 3 4 0 0
2/md3100 205.0 27.4 23099.6 472.2 0.0 2.5 10.9 0 79
2/md3200 225.3 27.3 24993.8 577.3 0.0 2.6 10.5 0 81
2/md3300 295.8 25.5 31538.0 412.5 0.0 3.1 9.8 0 84
2/md3400 198.3 25.6 21032.9 423.7 0.0 2.2 9.8 0 65
2/md3500 55.0 313.0 2397.5 2425.9 0.0 1.2 3.2 0 93
2/md3600 0.1 19.2 0.8 1440.0 0.0 0.1 5.4 0 10
2/md3700 3.1 0.8 48.8 35.7 0.0 0.0 9.3 0 4
2/md3800 300.4 0.7 30651.9 69.4 0.0 2.6 8.7 0 92
2/md3900 359.9 0.7 35876.8 56.6 0.0 3.3 9.1 0 95
2/md4100 0.6 512.1 9.6 1815.8 0.0 1.2 2.4 0 70
2/md4200 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0
2) vmstat report
kthr memory page disk faults cpu
r b w swap free re mf pi po fr de sr 2m 2m 2m 2m in sy cs us sy id
1 20 0 39126264 11482648 2570 5039 16336 14 14 0 1 41 38 47 61 71072 41785 30463 51 14 35
0 16 0 40580912 9157288 273 2366 0 8 7 0 0 198 310 251 192 49207 47702 29823 39 8 53
0 16 0 40588992 9163784 187 1392 0 8 8 0 0 251 278 212 163 47310 44840 27821 31 7 62
0 12 0 40597208 9171640 624 3168 0 2 2 0 0 298 329 209 245 49150 44768 26264 29 8 62
0 13 0 40577400 9158032 425 4452 0 9 8 0 0 177 181 331 292 49149 42545 25544 31 8 61
0 14 0 40576680 9156328 868 6027 0 8 7 0 0 161 234 259 327 48726 41187 26184 26 9 65
0 13 0 40567952 9151360 1067 7302 0 3 3 0 0 254 386 256 160 50388 45422 26596 31 10 60
0 13 0 40565160 9150880 838 6582 0 9 8 0 0 257 289 236 281 49697 45190 26925 31 10 60
0 12 0 40568616 9153128 640 4880 0 11 10 0 0 334 206 214 214 48738 43552 26431 27 9 65
0 12 0 40581696 9163248 799 5895 0 2 2 0 0 426 273 138 226 47831 41873 26301 30 9 61
0 11 0 40572096 9157896 1087 7138 1 10 9 0 0 337 163 220 305 53124 55371 27933 45 11 44
0 18 0 40520032 9123424 868 5946 0 10 9 0 0 222 218 170 249 51322 49556 27867 40 10 50
0 17 0 40528544 9130112 481 3257 0 1 1 0 0 276 269 145 316 56103 44359 27645 39 9 51
0 15 0 40521776 9126208 490 3174 0 10 8 0 0 240 305 226 222 55839 43464 27003 42 10 48
0 15 0 40491176 9101072 769 4149 0 8 8 0 0 297 362 150 317 59718 55624 34333 43 11 46
0 17 0 40603696 9183224 785 4364 0 2 2 0 0 314 234 281 238 62990 67554 39122 43 12 45
0 19 0 40622592 9215816 711 5308 1 12 12 0 0 390 167 252 283 65340 60514 30525 45 12 44
0 17 0 40662248 9276136 767 5113 0 10 8 0 0 218 280 298 221 63734 53314 31029 43 11 45
3) SAR CPU Utilization report
12:30:51 %usr %sys %wio %idle
12:31:01 41 9 0 50
12:31:11 43 11 0 46
12:31:21 42 11 0 47
12:31:31 44 12 0 44
12:31:41 42 11 0 47
Average 42 11 0 47
Anybody have any comment regarding the reports ?
Thanks for your help,
Srikanta SanpuiA suggestion: if you use the code tags with your output it will be a great deal easier to read.
extended device statistics tty
device r/s w/s kr/s kw/s wait actv svc_t %w %b tin tout
md100 0.3 7.0 2.4 7.0 0.0 0.2 38.5 3 4 0 0
2/md3100 205.0 27.4 23099.6 472.2 0.0 2.5 10.9 0 79
2/md3200 225.3 27.3 24993.8 577.3 0.0 2.6 10.5 0 81
2/md3300 295.8 25.5 31538.0 412.5 0.0 3.1 9.8 0 84
2/md3400 198.3 25.6 21032.9 423.7 0.0 2.2 9.8 0 65
2/md3500 55.0 313.0 2397.5 2425.9 0.0 1.2 3.2 0 93
2/md3600 0.1 19.2 0.8 1440.0 0.0 0.1 5.4 0 10
2/md3700 3.1 0.8 48.8 35.7 0.0 0.0 9.3 0 4
2/md3800 300.4 0.7 30651.9 69.4 0.0 2.6 8.7 0 92
2/md3900 359.9 0.7 35876.8 56.6 0.0 3.3 9.1 0 95
2/md4100 0.6 512.1 9.6 1815.8 0.0 1.2 2.4 0 70
2/md4200 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 -
Why arhivelogs are required for performing FLASHBACK database
Please explain. Thanks.
Documentation says :
It is similar to conventional point in time recovery in its effects, allowing you to return a database to its state at a time in the recent past.
Flashback Database is, however, much faster than point-in-time recovery, because it does not require restoring datafiles from backup and it requires applying fewer changes from the archived redo logs.
It is reason of Flashback require archivelog mode on database.
Regards
Mahir M. Quluzade -
Problem in performing multiple Point-In-Time Database Recovery using RMAN
Hello Experts,
I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
Environment:
Oracle 11g, ASM,
Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
Snapshot DiskGroups :
Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
Steps performed for point in time recovery:
1. Restore control file from snapshot 2.
RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
3. Catalog data files from snapshot 1.
4. Catalog archive logs from snapshot 2.
5. Perform point in time recovery till given time.
STARTUP MOUNT;
RUN {
SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
SET UNTIL TIME "06-mar-2013 09:30:00";
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
Results:
Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
Starting recover at 28-FEB-13
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/06/2013 11:10:57
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until time 'MAR 06 2013 09:45:00'
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
Doubts:
1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
However for this to work, I always need to keep the AutoBackup feature enabled.
How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
Please help me out in this issue.
Thanks.992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks. -
Database Performance (Tablespaces and Datafiles)
Hi guys!
What's the best for performance in database, tablespace with various datafiles distribuited in diferents filesystems or tablespaces with various datafiles in only one filesystem?
Thanks,
AugustoIt depends on contents of the tablespaces, tablespace level LOGGING/NOLOGGING and env such as either OLTP or OLAP and LUN presentation to the server with RAID or without RAID and SAN Read per second and write per second.
In general, tablespace with various datafiles distribuited in diferents filesystems/LUN's is in practice for non dev/system test databases.
Moreover using ASM is better then standard filesystems.
Regards,
Kamalesh -
Database performance is poor after upgrading to 9i
hi Guys
My system was upgraded to 9i by the third party after that I took over from that and I am getting the continuous complaints regarding performance of Database.
there are 150 Users who connects using citrix , from different locations and DB size is 20 GB.
this is my Init Ora file
# Cache and I/O
db_block_size = 4096
db_cache_size=591396864
db_file_multiblock_read_count=16
# Cursors and Library cache
open_cursors=3000
# Database Identification
db_domain=""
db_name=db_live
# Diagnostics and Statistics
background_dump_dest=D:\oracle\admin\db_live\bdump
core_dump_dest=D:\oracle\admin\db_live\cdump
timed_statistics=TRUE
user_dump_dest=D:\oracle\admin\db_live\udump
# File Configuration
control_files=("D:\oracle\oradata\db_live\control01.ctl","D:\oracle\oradata\db_live\control02.ctl","D:\oracle\oradata\db_live\control03.ctl")
# Instance Identification
instance_name = live
# Job Queues
job_queue_processes=10
# MTS
dispatchers = "(PROTOCOL=TCP)"
# Miscellaneous
aq_tm_processes = 1
compatible=9.2.0.0.0
# Optimizer
hash_join_enabled=TRUE
query_rewrite_enabled=FALSE
star_transfformation_enabled=FALSE
# Pools
java_pool_size=0
large_pool_size=145752064
shared_pool_size=197132288
# Processes and Sessions
processes=400
# Redo Log and Recovery
fast_start_mttr_target=300
# Security and Auditing
remote_login_passwordfile=EXCLUSIVE
# SORT, HASH Joins, Bitmap Indexes
pga_aggregate_target=525336576
sort_area_size=524288
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=UNDOTBS1
I feel SGA size and Sort area size are not correct if we increase the value of both will it solve some my problem
AbhiI have run the some scripts to check the performance
Here is the ouput :
Hit Ratio Section
=========================
BUFFER HIT RATIO
=========================
(should be > 70, else increase db_block_buffers in init.ora)
Buffer Hit Ratio
77
logical_reads phys_reads phy_writes BUFFER HIT RATIO
89,127,477 20,013,061 1,556,989 78
=========================
DATA DICT HIT RATIO
=========================
(should be higher than 90 else increase shared_pool_size in init.ora)
Data Dict. Gets Data Dict. cache misses DATA DICT CACHE HIT RATIO
11,785,386 40,955 99
=========================
LIBRARY CACHE MISS RATIO
=========================
(If > .1, i.e., more than 1% of the pins resulted in reloads, then
increase the shared_pool_size in init.ora)
executions Cache misses while executing LIBRARY CACHE MISS RATIO
9,845,481 11,831 .0012
=========================
Library Cache Section
=========================
hit ratio should be > 70, and pin ratio > 70 ...
NAMESPACE Hit ratio pin hit ratio reloads
SQL AREA 70 94 7,293
TABLE/PROCEDURE 99 98 4,529
BODY 87 68 9
TRIGGER 99 99 0
INDEX 98 98 0
CLUSTER 98 98 0
OBJECT 100 100 0
PIPE 100 100 0
JAVA SOURCE 100 100 0
JAVA RESOURCE 100 100 0
JAVA DATA 100 100 0
=========================
REDO LOG BUFFER
=========================
redo log space requests 37
Pool's Free Memory
POOL NAME BYTES
shared pool free memory 8,075,760
large pool free memory 127,547,048
SQL Summary Section
Tot SQL run since startup SQL executing now
4,727,276 3,833
Lock Section
=========================
SYSTEM-WIDE LOCKS - all requests for locks or latches
=========================
Processing Locks and Latches, please standby...
User Lock Type Mode Held
XR Null
Temp Segment Row-X (SX)
SYNTECH Transaction Exclusive
SYNTECH DML Row-S (SS)
SYNTECH Transaction Exclusive
SYNTECH DML Row-X (SX)
SYNTECH DML Row-X (SX)
SYNTECH DML Row-X (SX)
SYNTECH Transaction Exclusive
SYNTECH DML Row-S (SS)
=========================
DDL LOCKS - These are usually triggers or other DDL
=========================
User Owner Name Type Mode held
SYNTECH SYS DBMS_TRANSACTIO Table/Procedure/Type Null
SYNTECH SYS DBMS_TRANSACTIO Table/Procedure/Type Null
SYNTECH SYNTECH SW_LUC_SEQ Table/Procedure/Type Null
SYNTECH SYS DBMS_UTILITY Body Null
SYNTECH SYS DBMS_UTILITY Body Null
SYSTEM SYSTEM SYSTEM 18 Null
SYNTECH SYS DBMS_UTILITY Table/Procedure/Type Null
SYNTECH SYS DBMS_UTILITY Table/Procedure/Type Null
SYSTEM SYS DBMS_OUTPUT Body Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
User Owner Name Type Mode held
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SUMMIT SUMMIT SUMMIT 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
User Owner Name Type Mode held
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYNTECH SYNTECH 18 Null
SYNTECH SYS DBMS_TRANSACTIO Body Null
User Owner Name Type Mode held
SYNTECH SYS DBMS_TRANSACTIO Body Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SUMMIT SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYSTEM SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SUMMIT SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
User Owner Name Type Mode held
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYNTECH SYS DATABASE 18 Null
SYSTEM SYS DBMS_OUTPUT Table/Procedure/Type Null
SYNTECH SYS DBMS_APPLICATIO Table/Procedure/Type Null
SYNTECH SYS DBMS_APPLICATIO Table/Procedure/Type Null
SYSTEM SYS DBMS_APPLICATIO Table/Procedure/Type Null
SYNTECH SYS DBMS_APPLICATIO Body Null
SYNTECH SYS DBMS_APPLICATIO Body Null
SYSTEM SYS DBMS_APPLICATIO Body Null
=========================
DML LOCKS - These are table and row locks...
=========================
User Owner Name Mode held
SYNTECH SYNTECH SYJOBTRN Row-S (SS)
SYNTECH SYNTECH JCINVTRN Row-X (SX)
SYNTECH SYNTECH JCBATCH Row-S (SS)
SYNTECH SYNTECH JCIVBK Row-X (SX)
SYNTECH SYNTECH JCWSTG Row-S (SS)
SYNTECH SYNTECH JCINVC Row-X (SX)
Latch Section
if miss_ratio or immediate_miss_ratio > 1 then latch
contention exists, decrease LOG_SMALL_ENTRY_MAX_SIZE in init.ora
NAME miss_ratio immediate_miss_ratio
library cache .04 .24
virtual circuit queues .42 .00
Rollback Segment Section
if any count below is > 1% of the total number of requests for data
then more rollback segments are needed
CLASS COUNT
free list 0
undo block 1
undo header 201
system undo block 0
system undo header 0
Tot # of Requests for Data
89,163,600
=========================
ROLLBACK SEGMENT CONTENTION
=========================
If any ratio is > .01 then more rollback segments are needed
NAME WAITS GETS Ratio
SYSTEM 0 625 .00000
_SYSSMU1$ 31 67196 .00046
_SYSSMU2$ 0 30118 .00000
_SYSSMU3$ 18 75372 .00024
_SYSSMU4$ 9 36534 .00025
_SYSSMU5$ 28 173253 .00016
_SYSSMU6$ 0 31350 .00000
_SYSSMU7$ 0 28957 .00000
_SYSSMU8$ 10 62721 .00016
_SYSSMU9$ 3 44480 .00007
_SYSSMU10$ 37 42719 .00087
NAME WAITS GETS Ratio
_SYSSMU11$ 0 20228 .00000
_SYSSMU12$ 1 19168 .00005
Session Event Section
if average-wait > 20 then contention might exists
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
latch free 5 1 1
latch free 2 0 1
buffer busy waits 362 0 1
buffer busy waits 1 0 25
buffer busy waits 217 0 1
log buffer space 4 0 5
log file switch completion 4 0 3
log file switch completion 7 0 3
log file sync 253 0 1
log file sync 12 1 11
log file sync 307 1 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file sequential read 776 0 1
db file sequential read 53 0 3
db file sequential read 2,791 0 1
db file sequential read 2,125 0 1
db file sequential read 728 0 1
db file sequential read 12 0 1
db file sequential read 1,710 0 1
db file sequential read 237 0 1
db file sequential read 1 0 1
db file sequential read 404 0 1
db file sequential read 731 0 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file sequential read 1 0 1
db file sequential read 18 0 1
db file sequential read 11 0 3
db file sequential read 4 0 1
db file sequential read 64 0 4
db file sequential read 119 0 1
db file sequential read 1 0 1
db file sequential read 3 0 2
db file sequential read 511 0 2
db file sequential read 608 0 1
db file sequential read 2 0 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file sequential read 6 0 1
db file sequential read 5 0 1
db file sequential read 80 0 1
db file sequential read 74 0 2
db file sequential read 40 0 3
db file sequential read 876 0 1
db file sequential read 2,791 0 1
db file sequential read 5 0 1
db file sequential read 2 0 1
db file sequential read 315 0 1
db file scattered read 7 0 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file scattered read 15 0 1
db file scattered read 5 0 4
db file scattered read 8 0 1
db file scattered read 2 0 1
db file scattered read 1 0 1
db file scattered read 8 0 1
db file scattered read 129 0 1
db file scattered read 7 0 5
db file scattered read 1 0 1
db file scattered read 6 0 1
db file scattered read 4 0 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file scattered read 2 0 1
db file scattered read 5 0 4
db file scattered read 4 0 3
db file scattered read 4 0 1
db file scattered read 10,487 0 1
db file scattered read 2 0 1
db file scattered read 3 0 1
db file scattered read 2 0 1
db file scattered read 3 0 1
db file scattered read 13 0 2
db file scattered read 17 0 1
EVENT TOTAL_WAITS TOTAL_TIMEOUTS AVERAGE_WAIT
db file scattered read 2 0 1
db file scattered read 3 0 1
db file parallel read 32 0 1
db file parallel read 1 0 2
db file parallel read 29 0 2
db file parallel read 38 0 1
db file parallel read 24 0 2
db file parallel read 52 0 1
db file parallel read 33 0 1
undo segment extension 9 9 2
76 rows selected.
Queue Section
average wait for queues should be near zero ...
PADDR Queue type # queued WAIT TOTALQ AVG WAIT
00 COMMON 0 3195556 10,273,816 .311038858
1DCB67CC DISPATCHER 0 14654 10,649,458 .001376032
2 rows selected.
Multi-threaded Server Section
If the following number is > 1
then increase MTS_MAX_SERVERS parm in init.ora
Avg wait per request queue
.311037586853935493365783330857794608413 hundredths of seconds
1 row selected.
If the following number increases, consider adding dispatcher processes
Avg wait per response queue
.001376211356617059142626710087687462551 hundredths of seconds
=========================
DISPATCHER USAGE
=========================
(If Time Busy > 50, then change
MTS_MAX_DISPATCHERS in init.ora)
NAME STATUS IDLE BUSY Time Busy
D000 WAIT 3,506,156 89,948 2.501
Shared Server Processes
0
high-water mark for the multi-threaded server
MAXIMUM_CONNECTIONS MAXIMUM_SESSIONS SERVERS_STARTED SERVERS_TERMINATED
SERVERS_HIGHWATER
157 157 1721 1721
17
file i/o should be evenly distributed across drives.
# Name STATUS BYTES PHYRDS PHYWRTS
1 F:\ORACLE\ORADATA\DB_LIVE\SYST SYSTEM 262,144,000 16239 735
2 F:\ORACLE\ORADATA\DB_LIVE\UNDO ONLINE 2,222,981,120 1962 191422
3 F:\ORACLE\ORADATA\DB_LIVE\CONQ ONLINE 17,179,860,992 2361254 111110
4 F:\ORACLE\ORADATA\DB_LIVE\INDX ONLINE 26,214,400 20 18
5 F:\ORACLE\ORADATA\DB_LIVE\SUMM ONLINE 162,529,280 303 60
6 F:\ORACLE\ORADATA\DB_LIVE\TOOL ONLINE 10,485,760 20 18
7 F:\ORACLE\ORADATA\DB_LIVE\USER ONLINE 26,214,400 20 18
8 F:\ORACLE\ORADATA\DB_LIVE\CONQ ONLINE 1,263,534,080 2254864 123356
SYSTEM_STATISTIC VALUE
CPU used by this session 639,861
CPU used when call started 639,807
CR blocks created 27,293
Cached Commit SCN referenced 0
Commit SCN cached 0
DBWR buffers scanned 1,494,581
DBWR checkpoint buffers written 240,048
DBWR checkpoints 18
DBWR cross instance writes 0
DBWR free buffers found 1,319,309
DBWR fusion writes 0
SYSTEM_STATISTIC VALUE
DBWR lru scans 1,210
DBWR make free requests 1,210
DBWR revisited being-written buffer 0
DBWR summed scan depth 1,494,581
DBWR transaction table writes 271
DBWR undo block writes 191,098
DDL statements parallelized 0
DFO trees parallelized 0
DML statements parallelized 0
OTC commit optimization attempts 0
OTC commit optimization failure - setup 0
SYSTEM_STATISTIC VALUE
OTC commit optimization hits 0
PX local messages recv'd 0
PX local messages sent 0
PX remote messages recv'd 0
PX remote messages sent 0
Parallel operations downgraded 1 to 25 pct 0
Parallel operations downgraded 25 to 50 pct 0
Parallel operations downgraded 50 to 75 pct 0
Parallel operations downgraded 75 to 99 pct 0
Parallel operations downgraded to serial 0
Parallel operations not downgraded 0
SYSTEM_STATISTIC VALUE
RowCR - row contention 0
RowCR attempts 0
RowCR hits 0
SQL*Net roundtrips to/from client 20,533,267
SQL*Net roundtrips to/from dblink 0
Unnecesary process cleanup for SCN batching 0
active txn count during cleanout 82,931
background checkpoints completed 17
background checkpoints started 18
background timeouts 42,216
branch node splits 222
SYSTEM_STATISTIC VALUE
buffer is not pinned count 58,473,081
buffer is pinned count 58,622,335
bytes received via SQL*Net from client 690,006,487
bytes received via SQL*Net from dblink 0
bytes sent via SQL*Net to client 102,210,355,400
bytes sent via SQL*Net to dblink 0
calls to get snapshot scn: kcmgss 8,092,887
calls to kcmgas 130,839
calls to kcmgcs 87,223
calls to kcmgrs 0
change write time 16,834
SYSTEM_STATISTIC VALUE
cleanout - number of ktugct calls 91,022
cleanouts and rollbacks - consistent read gets 15,130
cleanouts only - consistent read gets 16,490
cluster key scan block gets 126,689
cluster key scans 74,722
cold recycle reads 0
commit cleanout failures: block lost 708
commit cleanout failures: buffer being written 59
commit cleanout failures: callback failure 49
commit cleanout failures: cannot pin 0
commit cleanout failures: hot backup in progress 0
SYSTEM_STATISTIC VALUE
commit cleanout failures: write disabled 0
commit cleanouts 488,120
commit cleanouts successfully completed 487,304
commit txn count during cleanout 36,303
consistent changes 155,131
consistent gets 74,645,555
consistent gets - examination 16,776,826
current blocks converted for CR 4
cursor authentications 55,278
data blocks consistent reads - undo records applied 154,868
db block changes 12,976,485
SYSTEM_STATISTIC VALUE
db block gets 14,531,153
deferred (CURRENT) block cleanout applications 137,895
deferred CUR cleanouts (index blocks) 0
dirty buffers inspected 9,671
enqueue conversions 11,684
enqueue deadlocks 0
enqueue releases 184,564
enqueue requests 184,686
enqueue timeouts 94
enqueue waits 1
exchange deadlocks 0
SYSTEM_STATISTIC VALUE
execute count 7,319,198
free buffer inspected 10,181
free buffer requested 19,253,045
gcs messages sent 0
ges messages sent 0
global cache blocks corrupt 0
global cache blocks lost 0
global cache claim blocks lost 0
global cache convert time 0
global cache convert timeouts 0
global cache converts 0
SYSTEM_STATISTIC VALUE
global cache cr block build time 0
global cache cr block flush time 0
global cache cr block receive time 0
global cache cr block send time 0
global cache cr blocks received 0
global cache cr blocks served 0
global cache current block flush time 0
global cache current block pin time 0
global cache current block receive time 0
global cache current block send time 0
global cache current blocks received 0
SYSTEM_STATISTIC VALUE
global cache current blocks served 0
global cache defers 0
global cache freelist waits 0
global cache get time 0
global cache gets 0
global cache prepare failures 0
global cache skip prepare failures 0
global lock async converts 0
global lock async gets 0
global lock convert time 0
global lock get time 0
SYSTEM_STATISTIC VALUE
global lock releases 0
global lock sync converts 0
global lock sync gets 0
hot buffers moved to head of LRU 1,334,001
immediate (CR) block cleanout applications 31,620
immediate (CURRENT) block cleanout applications 256,895
immediate CR cleanouts (index blocks) 0
index fast full scans (direct read) 0
index fast full scans (full) 6,363
index fast full scans (rowid ranges) 0
index fetch by key 7,199,288
SYSTEM_STATISTIC VALUE
index scans kdiixs1 2,173,768
instance recovery database freeze count 0
kcmccs called get current scn 0
kcmgss read scn without going to GES 0
kcmgss waited for batching 0
leaf node 90-10 splits 137
leaf node splits 20,302
logons cumulative 2,347
logons current 86
messages received 60,379
messages sent 60,378
SYSTEM_STATISTIC VALUE
native hash arithmetic execute 0
native hash arithmetic fail 0
next scns gotten without going to GES 0
no buffer to keep pinned count 5
no work - consistent read gets 55,487,127
number of map misses 0
number of map operations 0
opened cursors cumulative 692,633
opened cursors current 11,134
opens of replaced files 0
opens requiring cache replacement 0
SYSTEM_STATISTIC VALUE
parse count (failures) 35
parse count (hard) 222,131
parse count (total) 740,269
parse time cpu 71,868
parse time elapsed 79,481
physical reads 20,026,636
physical reads direct 1,052,614
physical reads direct (lob) 0
physical writes 1,557,017
physical writes direct 1,130,421
physical writes direct (lob) 0
SYSTEM_STATISTIC VALUE
physical writes non checkpoint 1,477,234
pinned buffers inspected 344
prefetch clients - 16k 0
prefetch clients - 2k 0
prefetch clients - 32k 0
prefetch clients - 4k 0
prefetch clients - 8k 0
prefetch clients - default 223
prefetch clients - keep 0
prefetch clients - recycle 0
prefetched blocks 14,445,041
SYSTEM_STATISTIC VALUE
prefetched blocks aged out before use 2,636
process last non-idle time ################
queries parallelized 0
recovery array read time 0
recovery array reads 0
recovery blocks read 0
recursive calls 1,911,332
recursive cpu usage 4,012
redo blocks written 3,597,536
redo buffer allocation retries 337
redo entries 6,634,895
SYSTEM_STATISTIC VALUE
redo log space requests 37
redo log space wait time 284
redo log switch interrupts 0
redo ordering marks 3
redo size 1,772,883,980
redo synch time 6,781
redo synch writes 27,527
redo wastage 11,115,384
redo write time 16,597
redo writer latching time 5
redo writes 51,171
SYSTEM_STATISTIC VALUE
remote instance undo block writes 0
remote instance undo header writes 0
rollback changes - undo records applied 88,835
rollbacks only - consistent read gets 12,179
rows fetched via callback 3,423,058
serializable aborts 0
session connect time ################
session cursor cache count 0
session cursor cache hits 0
session logical reads 89,176,705
session pga memory 35,556,660
SYSTEM_STATISTIC VALUE
session pga memory max 132,532,528
session stored procedure space 0
session uga memory 50,817,520
session uga memory max 497,741,936
shared hash latch upgrades - no wait 2,566,917
shared hash latch upgrades - wait 32
sorts (disk) 130
sorts (memory) 196,268
sorts (rows) 18,962,940
summed dirty queue length 376,151
switch current to new buffer 33,449
SYSTEM_STATISTIC VALUE
table fetch by rowid 39,128,298
table fetch continued row 556,214
table lookup prefetch client count 0
table scan blocks gotten 32,208,464
table scan rows gotten 2,455,389,745
table scans (cache partitions) 0
table scans (direct read) 0
table scans (long tables) 3,754
table scans (rowid ranges) 0
table scans (short tables) 124,879
total file opens 0
SYSTEM_STATISTIC VALUE
total number of slots 0
transaction lock background get time 0
transaction lock background gets 0
transaction lock foreground requests 0
transaction lock foreground wait time 0
transaction rollbacks 366
transaction tables consistent read rollbacks 1
transaction tables consistent reads - undo records appl 260
user calls 10,869,191
user commits 27,014
user rollbacks 411
SYSTEM_STATISTIC VALUE
workarea executions - multipass 36
workarea executions - onepass 218
workarea executions - optimal 131,726
workarea memory allocated 888
write clones created in background 1
write clones created in foreground 48 -
8.1.7 database performance issue
Hi Guys,
I have one issue raised by customer about performance of database. The platform is HP-UX 11i and Oracle 8.1.7
There is 3-tier architecture with D2k as front-end , One application or file server ( Novell based ) and Database server ( 8.1.7 with HP-UX 11i )
I don't see any probelms from hardware and OS perspective. Oracle is using raw devices in HP StorageWorks EVA 5000 ( 2 nos )with 3 HBAs for for each EVA from the HP rp7410 server ( 4x875Mhz CPU , 8GB RAM , HP-UX 11i OS ) through SAN switches.
The systems shows users around 400. As per DBA's feedback
SGA is 1.8GB with with total data files size around 135GB
( In terms of object is 90GB )
How UNIX kernel paramter dbc_max_pct parameter would affect the oracle operation?
Can anyone there, guide me on how to trace the cause of system slowness?
SamThe DBA can apply this query to know the I/O activity of read/writes regarding the datafiles and you must check that those datafiles has a good distribution. In case of not you have to apply a good striping of them.
SQL> r
1 select phyrds, phywrts, ceil(phyrds*100/(phyrds+phywrts)) ||
2 '%' "%reads", ceil(phywrts*100/(phyrds+phywrts)) || '%'
3 "%writes", d.name
4 from v$datafile d, v$filestat f
5* where d.file#=f.file# order by d.name
PHYRDS PHYWRTS %reads %writes NAME
1214231 190474 87% 14% /oracle/SIGEP/BANDEJA1/BANDEJA_2.dbf
39854 32963 55% 46% /oracle/SIGEP/BANDEJA1/BANDEJA_8.dbf
2426805 279412 90% 11% /oracle/SIGEP/BANDEJA2/BANDEJA_1.dbf
178777 35009 84% 17% /oracle/SIGEP/BANDEJA2/BANDEJA_3.dbf
22530 16284 59% 42% /oracle/SIGEP/BANDEJA2/BANDEJA_4.dbf
48571 24085 67% 34% /oracle/SIGEP/BANDEJA2/BANDEJA_5.dbf
37902 35409 52% 49% /oracle/SIGEP/BANDEJA2/BANDEJA_6.dbf
52154 39680 57% 44% /oracle/SIGEP/BANDEJA2/BANDEJA_7.dbf
2858606 76561 98% 3% /oracle/SIGEP/DATOS1/DATOS01.dbf
2599916 70456 98% 3% /oracle/SIGEP/DATOS1/DATOS02.dbf
1294 1223 52% 49% /oracle/SIGEP/DATOS1/MEDICION1.dbf
PHYRDS PHYWRTS %reads %writes NAME
4873 1223 80% 21% /oracle/SIGEP/DATOS1/PUNTOS1.dbf
7115316 121538 99% 2% /oracle/SIGEP/DATOS2/DATOS03.dbf
1855688 51318 98% 3% /oracle/SIGEP/DATOS2/DATOS04.dbf
1440753 52197 97% 4% /oracle/SIGEP/DATOS2/DATOS05.dbf
1162709 39525 97% 4% /oracle/SIGEP/DATOS2/DATOS06.dbf
1160547 42985 97% 4% /oracle/SIGEP/DATOS2/DATOS07.dbf
19944 1223 95% 6% /oracle/SIGEP/DATOS2/XDB1.dbf
1042353 125964 90% 11% /oracle/SIGEP/INDICES1/INDICES1.dbf
1017340 116972 90% 11% /oracle/SIGEP/INDICES1/INDICES2.dbf
1126702 128896 90% 11% /oracle/SIGEP/INDICES1/INDICES3.dbf
493673 52913 91% 10% /oracle/SIGEP/INDICES1/INDICES4.dbf
PHYRDS PHYWRTS %reads %writes NAME
63487 28007 70% 31% /oracle/SIGEP/INDICES1/INDICES5.dbf
62568 29283 69% 32% /oracle/SIGEP/INDICES1/INDICES6.dbf
54510 25509 69% 32% /oracle/SIGEP/INDICES1/INDICES7.dbf
46607 27442 63% 38% /oracle/SIGEP/INDICES1/INDICES8.dbf
20409 13729 60% 41% /oracle/SIGEP/INDICES1/MONITOR.dbf
260582 255290 51% 50% /oracle/SIGEP/MIC1/MIC1.dbf
305669 765111 29% 72% /oracle/SIGEP/MIC_IDX1/MIC_IDX1.dbf
9136 34232 22% 79% /oracle/SIGEP/SYSTEM1/DRSYS1.dbf
95652 27735 78% 23% /oracle/SIGEP/SYSTEM1/SYSTEM1.dbf
2787738 21627 100% 1% /oracle/SIGEP/SYSTEM1/USERS9_1.dbf
24815 736947 4% 97% /oracle/SIGEP/UNDO1/UNDO1.dbf
PHYRDS PHYWRTS %reads %writes NAME
33128 678687 5% 96% /oracle/SIGEP/UNDO1/UNDO2.dbf
38029 859205 5% 96% /oracle/SIGEP/UNDO1/UNDO3.dbf
30881 796939 4% 97% /oracle/SIGEP/UNDO1/UNDO4.dbf
29158 710228 4% 97% /oracle/SIGEP/UNDO1/UNDO5.dbf
26750 674284 4% 97% /oracle/SIGEP/UNDO1/UNDO6.dbf
28553 703524 4% 97% /oracle/SIGEP/UNDO1/UNDO7.dbf
24657 664093 4% 97% /oracle/SIGEP/UNDO1/UNDO8.dbf
40 rows selected.
Elapsed: 00:00:00.57
SQL>Joel Pérez
http://www.oracle.com/technology/experts -
Restored database, can't perform 'System Restore'
We've just performed a system reset of a system by performing a database restore to a version from a few months back. I now need to reapply the SC's that have been modified since the initial database snapshot.
However, when I try to perform a restore, the DI gives me a message indicating that the system already has the up-to-date version. Checking the SystemInfo page, it's quite clearly shown that the SC is the old version; checking in the SLD also shows the old build version. However, running the SDM tool shows the new version as being deployed...
Inspecting the file system, you can see all the originally deployed SCs in the folder /usr/sap/SID/JC00/SDM/root/origin, organized by domain and DC. The SC I need to redeploy is indeed in these directories, and I think I can probably fix my problem by removing the file, but I'm not sure of the side effects of doing this.
It's almost as if SAP expects you to perform a full system restore, rather than a database restore when recovering a system, since data is contained in both the database, and the file system.
Opinions?Just used SDM to force/sync the system.
-
Autogrowth, shrink and database performance
I have already asked some questions about Autogrowth and shrink. But I have some doubts related to it.
1)I have a database which grows about 300 MB every month. So is it best to set Autogrowth of 300 MB to it? Now 10 MB is set.
2)I have so many small databases which really have data of about 50 MB. But it's physical size is about 900 MB.(So 850 is free space). I have not shrinked this database. As if i shrink it then again when data gets added autogrowth occurs. But adding data to
this database is rare. So I think it will not gro more than 200 mb for next one year. So should i shrink the database? If I keep it as it is Should that cause any performance problem? Or having more free space(more than 90%) in database will cause any problem.
I think most of the people think having large physical size will cause performance problem. So is it true or not?
3) SQL Server 2008 R2 Express Database Size Limit is 10 GB. So is it physical size of both mdf and ldf file together? because I need to consider this if i should shrink database at any point.1) If this is a database where you expect performance, the current auto growth setting gives the following disadvantages:
- It will affect performance. Database files grow too often and it's unnecessary work for SQL Server during normal operations. It takes time to grow database files and especially if you have not turned Instant File Initialization on, which is highly recommended
by the way. I would prefer to grow databases off peak hours and once a year.
- The database file(s) gets fragmented. If SQL keeps allocating small 10 MB chunks the file will eventually have hundreds of fragments instead of just a few. Fragmentation reduces IO performance.
I would set the database file sizes to what you expect it to grow to within a year, plus 10 % and set auto growth to perhaps 300 MB that will kick in if your calculations were off. Next year you manually grow the database again according to your new 1-year
prediction. That way you will hopefully get less fragmentation and very few operational disturbances due to auto growth in peak hours.
2)
Keeping the database as is will not cause anything else than that the database is consuming unnecessary disk space, a lot of free space does not affect performance negatively. SQL Server does not do more IO just because you have large file(s). Having to little
free space in a db can cause internal fragmentation and will affect performance negatively. However, you should not fill up the spindles to more than 80% (some say 85%) since your storage will be noticeable slower.
You can shrink the database but that usually causes performance problems due to the shrink operation creates massive internal fragmentation in the database. But you can fix that by rebuilding all indexes and tables, starting with the clustered ones first.
So don't shrink the database so much that it must start with growing itself to accommodate for all index rebuilds.
Hope this helps!
Peter
Maybe you are looking for
-
ICloud documents not showing up in iCloud
Using Pages I have a number of documents that just don't show up on any of my iCloud devices (including iCloud from my Mac, when I click Open and go to iCloud they aren't there). I have tried duplicating the files and saving them to iCloud but they s
-
Java applet failures after updating to Java 6 Update 19
Hi, I'm currently experiencing a failure of unsigned Java applets after upgrading to JRE/Plugin 1.6.0_19. The problem with the update has been narrowed down to an interim fix for a TLS/SSL Man-in-the-Middle attack (see http://java.sun.com/javase/java
-
ABAP Certification -- Important
Hi Can any one tell me the procedure for ABAP certification. Where can i get documents to prepare myself for the examination? Where and how can i take this certification examination? What is the eligibility criteria and need information on fees struc
-
Why does macbook air go to sleep spontaneously?
My Macbook Air 13" goes to sleep spontaneoully while I'm working on it.
-
Workflow - Multiple dead line messages
I've got a PO ( BUS2012 ) workflow in which I want to have weekly notifications sent to the workflow initiator if the PO has not been released. I gone the route of setting up a fork, one fork looks for the PO release and the other fork does a loop an