Sql performance tunning user guides
Hi
Any One Have sql performence usere guids and best optimal how to use explain plan satement .
thank's
Maybe you should also have a look to Cost-Based Oracle Fundamentals, from Jonathan Lewis (at Apress), which is a bit more complex but really great on SQL tuning.
Similar Messages
-
How to improve my pls/sql performance tunning skills
Hi All , I would like to learn more about pl/sql performance tunning , where or how can i get more knowledge in this area ?
Is there any tutorials which can help me to understand the Explain plan, Dbms_Profiler, Dbms_Advisor more etc ........Thanks . BcjExplain plan
http://www.psoug.org/reference/explain_plan.html
DBMS_PROFILER (10g)
http://www.psoug.org/reference/dbms_profiler.html
DBMS_HPROF (11g)
http://www.psoug.org/reference/dbms_hprof.html
DBMS_ADVISOR
http://www.psoug.org/reference/dbms_advisor.html
DBMS_MONITOR
http://www.psoug.org/reference/dbms_monitor.html
DBMS_SUPPORT
http://www.psoug.org/reference/dbms_support.html
DBMS_TRACE
http://www.psoug.org/reference/dbms_trace.html
DBMS_SQLTUNE
http://www.psoug.org/reference/dbms_sqltune.html -
Hi
Can any body tell me how to tune pl/sql code
tnr
nageshBook 'Oracle PL/SQL Tips and Techniques' by TUSC guys is good one.
First thing is to use proving coding stretagies, which is key to gain performance even without tuning; then using proper tuning techniques. Tuning is no more than a polishing, if it is a dent, polishing will not solve it. -
SQL Performance tunning on RAC environment
Hi,
I am working on oracle 11.2.0.2.0 with 2 node RAC.
We have a batch process with runs everday and comsumes most of the time in cluster waits. Could someone please suggest what SQL / PL SQL changes / Hints are available to tune this cluster waits..
Also, if possible please provide link where can find more information on this.
ThanksIs your batch process multi-threaded or single-threaded?
If multi-threaded, and each thread is doing similar work, running the same code, and if your connections are load balanced across both nodes, it won't take long to end up waiting on cluster interconnect activity. You might try having the connections related to this batch job all go to one node.
In general, utilizing both nodes at the same time shouldn't be a problem, unless you have code that accesses the same segments on both nodes at the same time. That's when you'll see the worst problems in terms of cluster-related waits.
-Mark -
Hi I am using Oracle 9i, i am having SQL Query like this which is taking mote time to execute , is there any alternate way to modify the same query with Rank and Partition by concepts? The tables(dw_csc_site_mappings smo, dw_csc_companies cco) having 14 million rows approx.
SELECT /*+ RULE */
smo.company_target_id, smo.customer_id
FROM dw_csc_site_mappings smo, dw_csc_companies cco
WHERE cco.company_target_id = smo.company_target_id
AND cco.global_target_id IS NOT NULL
GROUP BY smo.company_target_id, smo.customer_id
HAVING COUNT (*) =
(SELECT MAX (COUNT (*))
FROM dw_csc_site_mappings smi, dw_csc_companies cci
WHERE smo.customer_id = smi.customer_id
AND cci.company_target_id = smi.company_target_id
AND cci.global_target_id IS NOT NULL
GROUP BY smi.company_target_id, smi.customer_id)
ORDER BY 1 ASCAnalytics might help.
You should try to find a way to access those big tables only once instead of twice.
untested try
select company_target_id, customer_id, cnt
from (
SELECT smo.company_target_id, smo.customer_id,
count(*) cnt, max(count(*)) over (partition by smo.company_target_id, smo.customer_id order by count(*)) max_cnt
FROM dw_csc_site_mappings smo, dw_csc_companies cco
WHERE cco.company_target_id = smo.company_target_id
AND cco.global_target_id IS NOT NULL
GROUP BY smo.company_target_id, smo.customer_id
) v
WHERE v.cnt = v.max_cnt
ORDER BY 1 ASC -
How will do the SQL PERFORMANCE TUNNING.
hi to all:
i have a query like example: select col1,col2,col3,col4,col5,col6,col7,col8,
col9,col0,col11,col12,col13,col14,col15 from table_name where col1=100 like that but data contain more like some lack wise reords.this query it's taking so much of time .i want to do the performance kindly give me solution to me...
anbarasan.select dai.GSI_PARTY_ID ,dai.GSI_PARTY_NUM ,dai.CERTIFICATION_LVL,dai.NAME ,dai.DUNS_NUM ,dai.CITY ,dai.STATE ,dai.ZIPCODE ,dai.COUNTRY,dai.ROW_WID,dai.GEO_WID,dai.ACCNT_GEOSTATE_WID,dai.W_CUSTOMER_CLASS,dai.MGR_NAME,dai.MAIN_PH_NUM,dai.ST_ADDRESS ,dai.ACCNT_FLG ,dai.ACCNT_LOC,dai.ACCNT_REVN,dai.ACTIVE_FLG,dai.ACCNT_STATUS,dai.ACCNT_STATUS_I,dai.ACCNT_TYPE_CD,dai.ACCNT_TYPE_CD_I,dai.CUST_TYPE_CODE,dai.CUST_TYPE_NAME,dai.ANNUAL_REVN_CAT,dai.ANNUAL_REVN_CAT_I,dai.BASE_CURCY_CD,dai.BU_NAME,dai.CHANNEL_FLG,dai.CHNL_ANNL_SALES,dai.CHNL_SALES_GRWTH,dai.CHNL_SALES_GRWTH_I,dai.COMPETITOR_FLG,dai.CREATED_DT,dai.DIVN_FLG,dai.DIVN_TYPE_CD,dai.DIVN_TYPE_CD_I,dai.DOMESTIC_ULTIMATE_DUNS_NUM,dai.EMP_COUNT,dai.EXPERTISE,dai.EXPERTISE_I,dai.FORMED_DT,dai.FREQUENCY_CAT,dai.FREQUENCY_CAT_I,dai.FRGHT_TERMS_CD,dai.FRGHT_TERMS_CD_I,dai.GLOBAL_DUNS_NUM,dai.HIST_SLS_VOL,dai.LINE_OF_BUSINESS,dai.MONETARY_CAT,dai.MONETARY_CAT_I,dai.NUM_EMPLOY_CAT,dai.NUM_EMPLOY_CAT_I,dai.ORG_NAME,dai.ORG_MGR_NAME,dai.ORG_MAIN_PH_NUM,dai.ORG_ST_ADDRESS,dai.ORG_CITY,dai.ORG_STATE,dai.ORG_ZIPCODE,dai.ORG_TERR_NAME,dai.ORG_COUNTRY,dai.ORG_FLG,dai.ORG_PRTNR_FLG,dai.ORG_PRTNR_TIER,dai.ORG_PRTNR_TIER_I,dai.ORG_PRTNR_TYPE,dai.ORG_PRTNR_TYPE_I,dai.PARENT_DUNS_NUM,dai.PAR_INTEGRATION_ID,dai.PAR_ORG_NAME,dai.PRI_LST_NAME,dai.PROSPECT_FLG,dai.PRTNRSHP_START_DT,dai.PRTNR_FLG,dai.PRTNR_NAME,dai.PRTNR_SALES_RANK,dai.PR_COMPETITOR,dai.PR_INDUST_NAME,dai.PR_ORG_TRGT_MKT,dai.PR_PTSHP_MKTSEG,dai.PTNTL_SLS_VOL,dai.PTSHP_END_DT,dai.PTSHP_FEE_PAID_FLG,dai.PTSHP_PRTNR_ACCNT,dai.PTSHP_RENEWAL_DT,dai.PTSHP_SAT_INDEX,dai.PTSHP_STAGE,dai.PTSHP_STAGE_I,dai.PUBLIC_LISTING_FLG,dai.RECENCY_CAT,dai.RECENCY_CAT_I,dai.REGION,dai.REGION_I,dai.REVN_GROWTH_CAT,dai.REVN_GROWTH_CAT_I,dai.SALES_EMP_CNT,dai.SERVICE_EMP_CNT,dai.U_ACCNT_RVN,dai.U_ACNTRVN_CURCY_CD,dai.U_ACNTRVN_EXCH_DT,dai.U_CHNL_ANNL_SLS,dai.U_CH_ASLS_CURCY_CD,dai.U_CH_ASLS_EXCH_DT,dai.U_HIST_SLS_VOL,dai.U_HST_SLS_CURCY_CD,dai.U_HST_SLS_EXCH_DT,dai.U_PTL_SLS_CURCY_CD,dai.U_PTL_SLS_EXCH_DT,dai.U_PTL_SLS_VOL,dai.VIS_PR_BU_ID,dai.VIS_PR_POS_ID,dai.VIS_PR_POSTN_DH_WID,dai.ACCNT_AHA_NUM,dai.ACCNT_CLASS,dai.ACCNT_CLASS_I,dai.ACCNT_HIN_NUM,dai.ACCNT_REGION,dai.ACCNT_VALUE,dai.ACCNT_VALUE_I,dai.AGENCY_FLG,dai.AGNC_CONTRACT_DT,dai.ANNUAL_REVENUE,dai.BOOK_VALUE,dai.BRANCH_FLG,dai.CALL_FREQUENCY,dai.CLIENT_FLG,dai.CREDIT_SCORE,dai.CRIME_TYPE_CD,dai.CRIME_TYPE_CD_I,dai.CURR_ASSET,dai.CURR_LIAB,dai.CUST_END_DT,dai.CUST_SINCE_DT,dai.CUST_STATUS_CODE,dai.DIVIDEND,dai.EXCHANGE_LOC,dai.FACILITY_FLG,dai.FACILITY_TYPE,dai.FACILITY_TYPE_I,dai.FIFTYTWO_HIGH,dai.FIFTYTWO_LOW,dai.FIN_METHOD,dai.FIN_METHOD_I,dai.GROSS_PROFIT,dai.GROWTH_HORIZ,dai.GROWTH_HORIZ_I,dai.GROWTH_OBJ,dai.GROWTH_OBJ_I,dai.GROWTH_PERCNTG,dai.IDENTIFIED_DT,dai.INVESTOR_FLG,dai.KEY_COMPETITOR,dai.LEADER_NAME,dai.LEGAL_FORM,dai.LEGAL_FORM_I,dai.LOYAL_SCORE1,dai.LOYAL_SCORE2,dai.LOYAL_SCORE3,dai.LOYAL_SCORE4,dai.LOYAL_SCORE5,dai.LOYAL_SCORE6,dai.LOYAL_SCORE7,dai.MARGIN_VS_INDUST,dai.MARGIN_VS_INDUST_I,dai.MARKET_CLASS,dai.MARKET_CLASS_I,dai.MARKET_TYPE,dai.MARKET_TYPE_I,dai.MED_PROC,dai.MEMBER_NUM,dai.MKT_POTENTIAL,dai.MRKT_CAP_PREF,dai.MRKT_CAP_PREF_I,dai.NET_INCOME,dai.NON_CASH_EXP,dai.NUMB_OF_BEDS,dai.NUM_PROD,dai.NUM_PROD_EFF_DT,dai.OBJECTIVE,dai.OBJECTIVE_I,dai.OPER_INCOME,dai.PERSIST_RATIO,dai.PRIM_MARKET,dai.PRIM_MARKET_I,dai.PROJ_EPS,dai.PR_SPEC_NAME,dai.PR_SYN_ID,dai.QUICK_RATIO,dai.SHARE_OUTST,dai.SRV_PROVDR_FLG,dai.STAT_REASON_CD,dai.STAT_REASON_CD_I,dai.TICKER,dai.TOTAL_DEBT,dai.TOTAL_NET_WORTH,dai.TOT_ASSET,dai.TOT_LIABILITY,dai.TRAIL_EPS,dai.U_EXCH_DT,dai.U_LOYAL_SCORE5,dai.VOLUME_TR,dai.X_NUM_PROD,dai.BIRTH_DT_WID,dai.NO_OF_CHILDREN,dai.LEGAL_NAME,dai.FAMILY_NAME,dai.OTHER_NAME,dai.PREFERRED_NAME,dai.INDV_TITLE,dai.INDV_MARITAL_STATE,dai.INDV_GENDER,dai.EMAIL_ADDRESS,dai.FAX_NUM,dai.PAGER_NUM,dai.MOBILE_NUM,dai.CUST_CAT_CODE,dai.CUST_CAT_NAME,dai.SIC_CODE,dai.SIC_NAME,dai.GOVT_ID_TYPE,dai.GOVT_ID_VALUE,dai.DUNNS_SITE_NAME,dai.DUNNS_GLOBAL_NAME,dai.DUNNS_LEGAL_NAME,dai.CUSTOMER_NUM,dai.ALT_CUSTOMER_NUM,dai.ALT_PHONE_NUM,dai.INTERNET_HOME_PAGE,dai.LEGAL_STRUCT_CODE,dai.LEGAL_STRUCT_NAME,dai.DIRECT_MKTG_FLG,dai.SOLICITATION_FLG,dai.CREATED_BY_WID,dai.CHANGED_BY_WID,dai.CREATED_ON_DT,dai.CHANGED_ON_DT,dai.AUX1_CHANGED_ON_DT,dai.AUX2_CHANGED_ON_DT,dai.AUX3_CHANGED_ON_DT,dai.AUX4_CHANGED_ON_DT,dai.SRC_EFF_FROM_DT,dai.SRC_EFF_TO_DT,dai.EFFECTIVE_FROM_DT,dai.EFFECTIVE_TO_DT,dai.DELETE_FLG,dai.CURRENT_FLG,dai.W_INSERT_DT,dai.W_UPDATE_DT,dai.DATASOURCE_NUM_ID,dai.ETL_PROC_WID,dai.INTEGRATION_ID,dai.TENANT_ID,dai.X_CUSTOM,dai.X_ADDR_CLEANSE_RESULT,dai.X_PR_INDUSTRY_ID,dai.X_PTNR_ACC_LVL_CD,dai.OPN_PIN_NUM,dai.X_ALIAS_NAME,dai.X_URL,dai.X_ACCNT_NAME_LOCAL,dai.X_ADDR_LINE_2,dai.X_ADDR_LINE_3,dai.X_COUNTY,dai.X_FAX_PH_NUM,dai.X_CONTRACT_VIS_FLG,dai.INDUSTRY_ONEVOICE,dai.X_ANNUAL_REVENUE,dai.X_NUM_EMPLOYEES,dai.INDUSTRY_ONEVOICE_SEGMENT,dai.X_GCD_ORG_ID,dai.X_MKTG_CREATED_FLG,dai.X_PR_ASGN_TYPE,dai.X_ADDR_DUNS,dai.X_ADDR_STATUS_CD,dai.X_MKTG_REGION,dai.X_MKTG_SUBREGION,dai.X_TRNSLT_CITY,dai.X_TRNSLT_STATE,dai.X_TRNSLT_POSTALCODE,dai.X_TRNSLT_LANG,dai.X_TRNSLT_ADDR1,dai.X_TRNSLT_ADDR2,dai.X_TRNSLT_ADDR3,dai.X_QUALITYSCORE,dai.X_SOURCE_TYPE_CD,dai.X_SIC_CODE,dai.X_PROVINCE,dai.X_GOVT_TYPE from dimple.gcm_account dai where 1=1 and dai.gsi_party_id=1017247578
this is my compleate quary ..pls give me solution.. -
SQL Performance issue: Using user defined function with group by
Hi Everyone,
im new here and I really could need some help on a weird performance issue. I hope this is the right topic for SQL performance issues.
Well ok, i create a function for converting a date from timezone GMT to a specified timzeone.
CREATE OR REPLACE FUNCTION I3S_REP_1.fnc_user_rep_date_to_local (date_in IN date, tz_name_in IN VARCHAR2) RETURN date
IS
tz_name VARCHAR2(100);
date_out date;
BEGIN
SELECT
to_date(to_char(cast(from_tz(cast( date_in AS TIMESTAMP),'GMT')AT
TIME ZONE (tz_name_in) AS DATE),'dd-mm-yyyy hh24:mi:ss'),'dd-mm-yyyy hh24:mi:ss')
INTO date_out
FROM dual;
RETURN date_out;
END fnc_user_rep_date_to_local;The following statement is just an example, the real statement is much more complex. So I select some date values from a table and aggregate a little.
select
stp_end_stamp,
count(*) noi
from step
where
stp_end_stamp
BETWEEN
to_date('23-05-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
AND
to_date('23-07-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
group by
stp_end_stampThis statement selects ~70000 rows and needs ~ 70ms
If i use the function it selects the same number of rows ;-) and takes ~ 4 sec ...
select
fnc_user_rep_date_to_local(stp_end_stamp,'Europe/Berlin'),
count(*) noi
from step
where
stp_end_stamp
BETWEEN
to_date('23-05-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
AND
to_date('23-07-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
group by
fnc_user_rep_date_to_local(stp_end_stamp,'Europe/Berlin')I understand that the DB has to execute the function for each row.
But if I execute the following statement, it takes only ~90ms ...
select
fnc_user_rep_date_to_gmt(stp_end_stamp,'Europe/Berlin','ny21654'),
noi
from
select
stp_end_stamp,
count(*) noi
from step
where
stp_end_stamp
BETWEEN
to_date('23-05-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
AND
to_date('23-07-2009 00:00:00','dd-mm-yyyy hh24:mi:ss')
group by
stp_end_stamp
)The execution plan for all three statements is EXACTLY the same!!!
Usually i would say, that I use the third statement and the world is in order. BUT I'm working on a BI project with a tool called Business Objects and it generates SQL, so my hands are bound and I can't make this tool to generate the SQL as a subselect.
My questions are:
Why is the second statement sooo much slower than the third?
and
Howcan I force the optimizer to do whatever he is doing to make the third statement so fast?
I would really appreciate some help on this really weird issue.
Thanks in advance,
AndiHi,
The execution plan for all three statements is EXACTLY the same!!!Not exactly. Plans are the same - true. They uses slightly different approach to call function. See:
drop table t cascade constraints purge;
create table t as select mod(rownum,10) id, cast('x' as char(500)) pad from dual connect by level <= 10000;
exec dbms_stats.gather_table_stats(user, 't');
create or replace function test_fnc(p_int number) return number is
begin
return trunc(p_int);
end;
explain plan for select id from t group by id;
select * from table(dbms_xplan.display(null,null,'advanced'));
explain plan for select test_fnc(id) from t group by test_fnc(id);
select * from table(dbms_xplan.display(null,null,'advanced'));
explain plan for select test_fnc(id) from (select id from t group by id);
select * from table(dbms_xplan.display(null,null,'advanced'));Output:
PLAN_TABLE_OUTPUT
Plan hash value: 47235625
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 10 | 30 | 162 (3)| 00:00:02 |
| 1 | HASH GROUP BY | | 10 | 30 | 162 (3)| 00:00:02 |
| 2 | TABLE ACCESS FULL| T | 10000 | 30000 | 159 (1)| 00:00:02 |
Query Block Name / Object Alias (identified by operation id):
1 - SEL$1
2 - SEL$1 / T@SEL$1
Outline Data
/*+
BEGIN_OUTLINE_DATA
FULL(@"SEL$1" "T"@"SEL$1")
OUTLINE_LEAF(@"SEL$1")
ALL_ROWS
OPTIMIZER_FEATURES_ENABLE('10.2.0.4')
IGNORE_OPTIM_EMBEDDED_HINTS
END_OUTLINE_DATA
Column Projection Information (identified by operation id):
1 - (#keys=1) "ID"[NUMBER,22]
2 - "ID"[NUMBER,22]
34 rows selected.
SQL>
Explained.
SQL>
PLAN_TABLE_OUTPUT
Plan hash value: 47235625
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 10 | 30 | 162 (3)| 00:00:02 |
| 1 | HASH GROUP BY | | 10 | 30 | 162 (3)| 00:00:02 |
| 2 | TABLE ACCESS FULL| T | 10000 | 30000 | 159 (1)| 00:00:02 |
Query Block Name / Object Alias (identified by operation id):
1 - SEL$1
2 - SEL$1 / T@SEL$1
Outline Data
/*+
BEGIN_OUTLINE_DATA
FULL(@"SEL$1" "T"@"SEL$1")
OUTLINE_LEAF(@"SEL$1")
ALL_ROWS
OPTIMIZER_FEATURES_ENABLE('10.2.0.4')
IGNORE_OPTIM_EMBEDDED_HINTS
END_OUTLINE_DATA
Column Projection Information (identified by operation id):
1 - (#keys=1) "TEST_FNC"("ID")[22]
2 - "ID"[NUMBER,22]
34 rows selected.
SQL>
Explained.
SQL> select * from table(dbms_xplan.display(null,null,'advanced'));
PLAN_TABLE_OUTPUT
Plan hash value: 47235625
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 10 | 30 | 162 (3)| 00:00:02 |
| 1 | HASH GROUP BY | | 10 | 30 | 162 (3)| 00:00:02 |
| 2 | TABLE ACCESS FULL| T | 10000 | 30000 | 159 (1)| 00:00:02 |
Query Block Name / Object Alias (identified by operation id):
1 - SEL$F5BB74E1
2 - SEL$F5BB74E1 / T@SEL$2
Outline Data
/*+
BEGIN_OUTLINE_DATA
FULL(@"SEL$F5BB74E1" "T"@"SEL$2")
OUTLINE(@"SEL$2")
OUTLINE(@"SEL$1")
MERGE(@"SEL$2")
OUTLINE_LEAF(@"SEL$F5BB74E1")
ALL_ROWS
OPTIMIZER_FEATURES_ENABLE('10.2.0.4')
IGNORE_OPTIM_EMBEDDED_HINTS
END_OUTLINE_DATA
Column Projection Information (identified by operation id):
1 - (#keys=1) "ID"[NUMBER,22]
2 - "ID"[NUMBER,22]
37 rows selected. -
EP Performance Tunning and concurrent user login problems
Hi all.
We have a EP , integrated with Windows AD and SAP R3.
In real situation, there will be 1000 users login in EP in 0.5 hours. And their operation time will be 6-8 hours, connect to R3 or other applications.
Is EP can support such concurrent user login scenario ?
if EP fails, is there some performance monitor tool or performance tunning issue ?Hi
EP supports this logon load, however it all depends on sizing and architecture! Also the content of the STARTPAGE can be critical (make it "light").
If the portal fails, then often it is only one J2EE server process, which fails - so by having more server-processes will be an easy/minimum form of high availability. A "real" HA solution must be considered if your business will not work without the portal og SAPGUI connections can be used as workaround/fallback in such situations.
BR
Tom Bo -
Oracle Performance tunning genral question
Hi,
Below is the list of Areas of Oracle db for which tunning activities are done. You are invited to comment to it weather this is complete list or need some addition or deletion. As I'm learning PT for Oracle now a days, therefore I want to expand my knowledge by sharing what I'm learning and what I need to learn.
So comment with Open hearts on it. Espically from experts and Gurus.
Here is the List
1-Planning for Performance, include Storage consideration( Weather it is SAN, NAS, DAS), Network planning and host OS planning with proper configuration for running Oracle.
2-Database desining (Not under-Normalized and not Over-Normalized with proper usage of Indexes, views and Stored Procedures)
3- Instance tunning (Memory structure + B.g Processes)
4- Session tunning.
5- Segment Space tunning.
6- SQL tunning.
This is what uptill what I've learned. If it needs addition kindly tell me what are these. Please also provide me links(good and precise one) for PT tutorials on web.Also note that I'm discussing this w.r.t Single instance non-rac db.
Looking for Good sugessions
Regards,
AbbasiHello,
This is the oracle course contents:
Contents
Preface
1 Introduction
Course Objectives 1-2
Organization 1-3
Agenda 1-4
What Is Not Included 1-6
Who Tunes? 1-7
What Does the DBA Tune? 1-8
How to Tune 1-10
Tuning Methodology 1-11
Effective Tuning Goals 1-13
General Tuning Session 1-15
Summary 1-17
2 Basic Tuning Tools
Objectives 2-2
Performance Tuning Diagnostics 2-3
Performance Tuning Tools 2-4
Tuning Objectives 2-5
Top Wait Events 2-6
DB Time 2-7
CPU and Wait Time Tuning Dimensions 2-8
Time Model: Overview 2-9
Time Model Statistics Hierarchy 2-10
Time Model Example 2-12
Dynamic Performance Views 2-13
Dynamic Performance Views: Usage Examples 2-14
Dynamic Performance Views: Considerations 2-15
Statistic Levels 2-16
Statistics and Wait Events 2-18
System Statistic Classes 2-19
Displaying Statistics 2-20
Displaying SGA Statistics 2-22
Wait Events 2-23
Using the V$EVENT_NAME View 2-24
Wait Classes 2-25
Displaying Wait Event Statistics 2-26
Oracle Internal & Oracle Academy Use Only
iv
Commonly Observed Wait Events 2-28
Using the V$SESSION_WAIT View 2-29
Precision of System Statistics 2-31
Using Features of the Packs 2-32
Accessing the Database Home Page 2-34
Enterprise Manager Performance Pages 2-35
Viewing the Alert Log 2-37
Using Alert Log Information as an Aid in Tuning 2-38
User Trace Files 2-40
Background Processes Trace Files 2-41
Summary 2-42
Practice 2 Overview: Using Basic Tools 2-43
3 Using Automatic Workload Repository
Objectives 3-2
Automatic Workload Repository: Overview 3-3
Automatic Workload Repository Data 3-4
Workload Repository 3-5
Database Control and AWR 3-6
AWR Snapshot Purging Policy 3-7
AWR Snapshot Settings 3-8
Manual AWR Snapshots 3-9
Managing Snapshots with PL/SQL 3-10
Generating AWR Reports in EM 3-11
Generating AWR Reports in SQL*Plus 3-12
Reading the AWR Report 3-13
Snapshots and Periods Comparisons 3-14
Compare Periods: Benefits 3-15
Compare Periods: Results 3-16
Compare Periods: Report 3-17
Compare Periods: Load Profile 3-18
Compare Periods: Top Events 3-19
Summary 3-20
Practice 3 Overview: Using AWR-Based Tools 3-21
4 Defining Problems
Objectives 4-2
Defining the Problem 4-3
Limit the Scope 4-4
Setting the Priority 4-5
Top Wait Events 4-6
Oracle Internal & Oracle Academy Use Only
v
Setting the Priority: Example 4-7
Top SQL Reports 4-8
Common Tuning Problems 4-9
Tuning Life Cycle Phases 4-11
Tuning During the Life Cycle 4-12
Application Design and Development 4-13
Testing: Database Configuration 4-14
Deployment 4-15
Production 4-16
Migration, Upgrade, and Environment Changes 4-17
ADDM Tuning Session 4-18
Performance Versus Business Requirements 4-19
Performance Tuning Resources 4-20
Filing a Performance Service Request 4-21
RDA Report 4-22
Monitoring and Tuning Tool: Overview 4-23
Summary 4-25
Practice 4 Overview: Identifying the Problem 4-26
5 Using Metrics and Alerts
Objectives 5-2
Metrics, Alerts, and Baselines 5-3
Limitation of Base Statistics 5-4
Typical Delta Tools 5-5
Oracle Database 11g Solution: Metrics 5-6
Benefits of Metrics 5-7
Viewing Metric History Information 5-8
Using EM to View Metric Details 5-9
Statistic Histograms 5-10
Histogram Views 5-11
Server-Generated Alerts 5-12
Database Control Usage Model 5-13
Setting Thresholds 5-14
Creating and Testing an Alert 5-15
Metric and Alert Views 5-16
View User-Defined SQL Metrics 5-17
Create User-Defined SQL Metrics 5-18
View User-Defined Host Metrics 5-19
Create User-Defined Host Metrics 5-20
Summary 5-21
Practice Overview 5: Working with Metrics 5-22
Oracle Internal & Oracle Academy Use Only
vi
6 Baselines
Objectives 6-2
Comparative Performance Analysis with AWR Baselines 6-3
Automatic Workload Repository Baselines 6-4
Moving Window Baseline 6-5
Baselines in Performance Page Settings 6-6
Baseline Templates 6-7
AWR Baselines 6-8
Creating AWR Baselines 6-9
Single AWR Baseline 6-10
Creating a Repeating Baseline Template 6-11
Managing Baselines with PL/SQL 6-12
Generating a Baseline Template for a Single Time Period 6-13
Creating a Repeating Baseline Template 6-14
Baseline Views 6-15
Performance Monitoring and Baselines 6-17
Defining Alert Thresholds Using a Static Baseline 6-19
Using EM to Quickly Configure Adaptive Thresholds 6-20
Changing Adaptive Threshold Settings 6-22
Summary 6-23
Practice 6: Overview Using AWR Baselines 6-24
7 Using AWR-Based Tools
Objectives 7-2
Automatic Maintenance Tasks 7-3
Maintenance Windows 7-4
Default Maintenance Plan 7-5
Automated Maintenance Task Priorities 7-6
Tuning Automatic Maintenance Tasks 7-7
ADDM Performance Monitoring 7-8
ADDM and Database Time 7-9
DBTime-Graph and ADDM Methodology 7-10
Top Performance Issues Detected 7-12
Database Control and ADDM Findings 7-13
ADDM Analysis Results 7-14
ADDM Recommendations 7-15
Database Control and ADDM Task 7-16
Changing ADDM Attributes 7-17
Retrieving ADDM Reports by Using SQL 7-18
Active Session History: Overview 7-19
Active Session History: Mechanics 7-20
Oracle Internal & Oracle Academy Use Only
vii
ASH Sampling: Example 7-21
Accessing ASH Data 7-22
Dump ASH to File 7-23
Analyzing the ASH Data 7-24
Generating ASH Reports 7-25
ASH Report Script 7-26
ASH Report: General Section 7-27
ASH Report Structure 7-28
ASH Report: Activity Over Time 7-29
Summary 7-30
Practice 7 Overview: Using AWR-Based Tools 7-31
8 Monitoring an Application
Objectives 8-2
What Is a Service? 8-3
Service Attributes 8-4
Service Types 8-5
Creating Services 8-6
Managing Services in a Single-Instance Environment 8-7
Everything Switches to Services 8-8
Using Services with Client Applications 8-9
Using Services with the Resource Manager 8-10
Services and Resource Manager with EM 8-11
Services and the Resource Manager: Example 8-12
Using Services with the Scheduler 8-13
Services and the Scheduler with EM 8-14
Services and the Scheduler: Example 8-16
Using Services with Parallel Operations 8-17
Using Services with Metric Thresholds 8-18
Changing Service Thresholds by Using EM 8-19
Services and Metric Thresholds: Example 8-20
Service Aggregation and Tracing 8-21
Top Services Performance Page 8-22
Service Aggregation Configuration 8-23
Service Aggregation: Example 8-24
Client Identifier Aggregation and Tracing 8-25
trcsess Utility 8-26
Service Performance Views 8-27
Summary 8-29
Practice 8 Overview: Using Services 8-30
Oracle Internal & Oracle Academy Use Only
viii
9 Identifying Problem SQL Statements
Objectives 9-2
SQL Statement Processing Phases 9-3
Parse Phase 9-4
SQL Storage 9-5
Cursor Usage and Parsing 9-6
SQL Statement Processing Phases: Bind 9-8
SQL Statement Processing Phases: Execute and Fetch 9-9
Processing a DML Statement 9-10
COMMIT Processing 9-12
Role of the Oracle Optimizer 9-13
Identifying Bad SQL 9-15
TOP SQL Reports 9-16
What Is an Execution Plan? 9-17
Methods for Viewing Execution Plans 9-18
Uses of Execution Plans 9-19
DBMS_XPLAN Package: Overview 9-20
EXPLAIN PLAN Command 9-22
EXPLAIN PLAN Command: Example 9-23
EXPLAIN PLAN Command: Output 9-24
Reading an Execution Plan 9-25
Using the V$SQL_PLAN View 9-26
V$SQL_PLAN Columns 9-27
Querying V$SQL_PLAN 9-28
V$SQL_PLAN_STATISTICS View 9-29
Querying the AWR 9-30
SQL*Plus AUTOTRACE 9-32
Using SQL*Plus AUTOTRACE 9-33
SQL*Plus AUTOTRACE: Statistics 9-34
SQL Trace Facility 9-35
How to Use the SQL Trace Facility 9-37
Initialization Parameters 9-38
Enabling SQL Trace 9-40
Disabling SQL Trace 9-41
Formatting Your Trace Files 9-42
TKPROF Command Options 9-43
Output of the TKPROF Command 9-45
TKPROF Output with No Index: Example 9-50
TKPROF Output with Index: Example 9-51
Generate an Optimizer Trace 9-52
Oracle Internal & Oracle Academy Use Only
ix
Summary 9-53
Practice Overview 9: Using Execution Plan Utilities 9-54
10 Influencing the Optimizer
Objectives 10-2
Functions of the Query Optimizer 10-3
Selectivity 10-5
Cardinality and Cost 10-6
Changing Optimizer Behavior 10-7
Using Hints 10-8
Optimizer Statistics 10-9
Extended Statistics 10-10
Controlling the Behavior of the Optimizer with Parameters 10-11
Enabling Query Optimizer Features 10-13
Influencing the Optimizer Approach 10-14
Optimizing SQL Statements 10-15
Access Paths 10-16
Choosing an Access Path 10-17
Full Table Scans 10-18
Row ID Scans 10-20
Index Operations 10-21
B*Tree Index Operations 10-22
Bitmap Indexes 10-23
Bitmap Index Access 10-24
Combining Bitmaps 10-25
Bitmap Operations 10-26
Join Operations 10-27
Join Methods 10-28
Nested Loop Joins 10-29
Hash Joins 10-31
Sort-Merge Joins 10-32
Join Performance 10-34
How the Query Optimizer Chooses Execution Plans for Joins 10-35
Sort Operations 10-37
Tuning Sort Performance 10-38
Reducing the Cost 10-39
Index Maintenance 10-40
Dropping Indexes 10-42
Creating Indexes 10-43
SQL Access Advisor 10-44
Table Maintenance for Performance 10-45
Oracle Internal & Oracle Academy Use Only
x
Table Reorganization Methods 10-46
Summary 10-47
Practice 10 Overview: Influencing the Optimizer 10-48
11 Using SQL Performance Analyzer
Objectives 11-2
Real Application Testing: Overview 11-3
Real Application Testing: Use Cases 11-4
SQL Performance Analyzer: Process 11-5
Capturing the SQL Workload 11-7
Creating a SQL Performance Analyzer Task 11-8
SQL Performance Analyzer: Tasks 11-9
Optimizer Upgrade Simulation 11-10
SQL Performance Analyzer Task Page 11-11
Comparison Report 11-12
Comparison Report SQL Detail 11-13
Tuning Regressing Statements 11-14
Preventing Regressions 11-16
Parameter Change Analysis 11-17
Guided Workflow Analysis 11-18
SQL Performance Analyzer: PL/SQL Example 11-19
SQL Performance Analyzer: Data Dictionary Views 11-21
Summary 11-22
Practice 11: Overview 11-23
12 SQL Performance Management
Objectives 12-2
Maintaining SQL Performance 12-3
Maintaining Optimizer Statistics 12-4
Automated Maintenance Tasks 12-5
Statistic Gathering Options 12-6
Setting Statistic Preferences 12-7
Restore Statistics 12-9
Deferred Statistics Publishing: Overview 12-10
Deferred Statistics Publishing: Example 12-12
Automatic SQL Tuning: Overview 12-13
SQL Statement Profiling 12-14
Plan Tuning Flow and SQL Profile Creation 12-15
SQL Tuning Loop 12-16
Using SQL Profiles 12-17
SQL Tuning Advisor: Overview 12-18
Oracle Internal & Oracle Academy Use Only
xi
Using the SQL Tuning Advisor 12-19
SQL Tuning Advisor Options 12-20
SQL Tuning Advisor Recommendations 12-21
Using the SQL Tuning Advisor: Example 12-22
Using the SQL Access Advisor 12-23
View Recommendations 12-25
View Recommendation Details 12-26
SQL Plan Management: Overview 12-27
SQL Plan Baseline: Architecture 12-28
Loading SQL Plan Baselines 12-30
Evolving SQL Plan Baselines 12-31
Important Baseline SQL Plan Attributes 12-32
SQL Plan Selection 12-34
Possible SQL Plan Manageability Scenarios 12-36
SQL Performance Analyzer and SQL Plan Baseline Scenario 12-37
Loading a SQL Plan Baseline Automatically 12-38
Purging SQL Management Base Policy 12-39
Enterprise Manager and SQL Plan Baselines 12-40
Summary 12-41
Practice 12: Overview Using SQL Plan Management 12-42
13 Using Database Replay
Objectives 13-2
Using Database Replay 13-3
The Big Picture 13-4
System Architecture: Capture 13-5
System Architecture: Processing the Workload 13-7
System Architecture: Replay 13-8
Capture Considerations 13-9
Replay Considerations: Preparation 13-10
Replay Considerations 13-11
Replay Options 13-12
Replay Analysis 13-13
Database Replay Workflow in Enterprise Manager 13-15
Capturing Workload with Enterprise Manager 13-16
Capture Wizard: Plan Environment 13-17
Capture Wizard: Options 13-18
Capture Wizard: Parameters 13-19
Viewing Capture Progress 13-20
Viewing Capture Report 13-21
Export Capture AWR Data 13-22
Oracle Internal & Oracle Academy Use Only
xii
Viewing Workload Capture History 13-23
Processing Captured Workload 13-24
Using the Preprocess Captured Workload Wizard 13-25
Using the Replay Workload Wizard 13-26
Replay Workload: Prerequisites 13-27
Replay Workload: Choose Initial Options 13-28
Replay Workload: Customize Options 13-29
Replay Workload: Prepare Replay Clients 13-30
Replay Workload: Client Connections 13-31
Replay Workload: Replay Started 13-32
Viewing Workload Replay Progress 13-33
Viewing Workload Replay Statistics 13-34
Packages and Procedures 13-36
Data Dictionary Views: Database Replay 13-37
Database Replay: PL/SQL Example 13-38
Calibrating Replay Clients 13-40
Summary 13-41
Practice 13: Overview 13-42
14 Tuning the Shared Pool
Objectives 14-2
Shared Pool Architecture 14-3
Shared Pool Operation 14-4
The Library Cache 14-5
Latch and Mutex 14-7
Latch and Mutex: Views and Statistics 14-9
Diagnostic Tools for Tuning the Shared Pool 14-11
AWR/Statspack Indicators 14-13
Load Profile 14-14
Instance Efficiencies 14-15
Top Waits 14-16
Time Model 14-17
Library Cache Activity 14-19
Avoid Hard Parses 14-20
Are Cursors Being Shared? 14-21
Sharing Cursors 14-23
Adaptive Cursor Sharing: Example 14-25
Adaptive Cursor Sharing Views 14-27
Interacting with Adaptive Cursor Sharing 14-28
Avoiding Soft Parses 14-29
Sizing the Shared Pool 14-30
Oracle Internal & Oracle Academy Use Only
xiii
Shared Pool Advisory 14-31
Shared Pool Advisor 14-33
Avoiding Fragmentation 14-34
Large Memory Requirements 14-35
Tuning the Shared Pool Reserved Space 14-37
Keeping Large Objects 14-39
Data Dictionary Cache 14-41
Dictionary Cache Misses 14-42
SQL Query Result Cache: Overview 14-43
Managing the SQL Query Result Cache 14-44
Using the RESULT_CACHE Hint 14-46
Using the DBMS_RESULT_CACHE Package 14-47
Viewing SQL Result Cache Dictionary Information 14-48
SQL Query Result Cache: Considerations 14-49
UGA and Oracle Shared Server 14-50
Large Pool 14-51
Tuning the Large Pool 14-52
Summary 14-53
Practice Overview 14: Tuning the Shared Pool 14-54
15 Tuning the Buffer Cache
Objectives 15-2
Oracle Database Architecture 15-3
Buffer Cache: Highlights 15-4
Database Buffers 15-5
Buffer Hash Table for Lookups 15-6
Working Sets 15-7
Tuning Goals and Techniques 15-9
Symptoms 15-11
Cache Buffer Chains Latch Contention 15-12
Finding Hot Segments 15-13
Buffer Busy Waits 15-14
Calculating the Buffer Cache Hit Ratio 15-15
Buffer Cache Hit Ratio Is Not Everything 15-16
Interpreting Buffer Cache Hit Ratio 15-17
Read Waits 15-19
Free Buffer Waits 15-21
Solutions 15-22
Sizing the Buffer Cache 15-23
Buffer Cache Size Parameters 15-24
Dynamic Buffer Cache Advisory Parameter 15-25
Oracle Internal & Oracle Academy Use Only
xiv
Buffer Cache Advisory View 15-26
Using the V$DB_CACHE_ADVICE View 15-27
Using the Buffer Cache Advisory with EM 15-28
Caching Tables 15-29
Multiple Buffer Pools 15-30
Enabling Multiple Buffer Pools 15-32
Calculating the Hit Ratio for Multiple Pools 15-33
Multiple Block Sizes 15-35
Multiple Database Writers 15-36
Multiple I/O Slaves 15-37
Use Multiple Writers or I/O Slaves 15-38
Private Pool for I/O Intensive Operations 15-39
Automatically Tuned Multiblock Reads 15-40
Flushing the Buffer Cache (for Testing Only) 15-41
Summary 15-42
Practice 15: Overview Tuning the Buffer Cache 15-43
16 Tuning PGA and Temporary Space
Objectives 16-2
SQL Memory Usage 16-3
Performance Impact 16-4
Automatic PGA Memory 16-5
SQL Memory Manager 16-6
Configuring Automatic PGA Memory 16-8
Setting PGA_AGGREGATE_TARGET Initially 16-9
Monitoring SQL Memory Usage 16-10
Monitoring SQL Memory Usage: Examples 16-12
Tuning SQL Memory Usage 16-13
PGA Target Advice Statistics 16-14
PGA Target Advice Histograms 16-15
Automatic PGA and Enterprise Manager 16-16
Automatic PGA and AWR Reports 16-17
Temporary Tablespace Management: Overview 16-18
Temporary Tablespace: Best Practice 16-19
Configuring Temporary Tablespace 16-20
Temporary Tablespace Group: Overview 16-22
Temporary Tablespace Group: Benefits 16-23
Creating Temporary Tablespace Groups 16-24
Maintaining Temporary Tablespace Groups 16-25
View Tablespace Groups 16-26
Monitoring Temporary Tablespace 16-27
Oracle Internal & Oracle Academy Use Only
xv
Temporary Tablespace Shrink 16-28
Tablespace Option for Creating Temporary Table 16-29
Summary 16-30
Practice Overview 16: Tuning PGA Memory 16-31
17 Automatic Memory Management
Objectives 17-2
Oracle Database Architecture 17-3
Dynamic SGA 17-4
Granule 17-5
Memory Advisories 17-6
Manually Adding Granules to Components 17-7
Increasing the Size of an SGA Component 17-8
Automatic Shared Memory Management: Overview 17-9
SGA Sizing Parameters: Overview 17-10
Dynamic SGA Transfer Modes 17-11
Memory Broker Architecture 17-12
Manually Resizing Dynamic SGA Parameters 17-13
Behavior of Auto-Tuned SGA Parameters 17-14
Behavior of Manually Tuned SGA Parameters 17-15
Using the V$PARAMETER View 17-16
Resizing SGA_TARGET 17-17
Disabling Automatic Shared Memory Management 17-18
Configuring ASMM 17-19
SGA Advisor 17-20
Monitoring ASMM 17-21
Automatic Memory Management: Overview 17-22
Oracle Database Memory Parameters 17-24
Automatic Memory Parameter Dependency 17-25
Enabling Automatic Memory Management 17-26
Monitoring Automatic Memory Management 17-27
DBCA and Automatic Memory Management 17-29
Summary 17-30
Practice 17: Overview Using Automatic Memory Tuning 17-31
Oracle Internal & Oracle Academy Use Only
xvi
18 Tuning Segment Space Usage
Objectives 18-2
Space Management 18-3
Extent Management 18-4
Locally Managed Extents 18-5
Large Extents: Considerations 18-6
How Table Data Is Stored 18-8
Anatomy of a Database Block 18-9
Minimize Block Visits 18-10
The DB_BLOCK_SIZE Parameter 18-11
Small Block Size: Considerations 18-12
Large Block Size: Considerations 18-13
Block Allocation 18-14
Free Lists 18-15
Block Space Management 18-16
Block Space Management with Free Lists 18-17
Automatic Segment Space Management 18-19
Automatic Segment Space Management at Work 18-20
Block Space Management with ASSM 18-22
Creating an Automatic Segment Space Management Segment 18-23
Migration and Chaining 18-24
Guidelines for PCTFREE and PCTUSED 18-26
Detecting Migration and Chaining 18-27
Selecting Migrated Rows 18-28
Eliminating Migrated Rows 18-29
Shrinking Segments: Overview 18-31
Shrinking Segments: Considerations 18-32
Shrinking Segments by Using SQL 18-33
Segment Shrink: Basic Execution 18-34
Segment Shrink: Execution Considerations 18-35
Using EM to Shrink Segments 18-36
Table Compression: Overview 18-37
Table Compression Concepts 18-38
Using Table Compression 18-39
Summary 18-40
19 Tuning I/O
Objectives 19-2
I/O Architecture 19-3
File System Characteristics 19-4
I/O Modes 19-5
Oracle Internal & Oracle Academy Use Only
xvii
Direct I/O 19-6
Bandwidth Versus Size 19-7
Important I/O Metrics for Oracle Databases 19-8
I/O Calibration and Enterprise Manager 19-10
I/O Calibration and the PL/SQL Interface 19-11
I/O Statistics: Overview 19-13
I/O Statistics and Enterprise Manager 19-14
Stripe and Mirror Everything 19-16
Using RAID 19-17
RAID Cost Versus Benefits 19-18
Should I Use RAID 1 or RAID 5? 19-20
Diagnostics 19-21
Database I/O Tuning 19-22
What Is Automatic Storage Management? 19-23
Tuning ASM 19-24
How Many Disk Groups per Database 19-25
Which RAID Configuration for Best Availability? 19-26
ASM Mirroring Guidelines 19-27
ASM Striping Granularity 19-28
What Type of Striping Works Best? 19-29
ASM Striping Only 19-30
Hardware RAID Striped LUNs 19-31
ASM Guidelines 19-32
ASM Instance Initialization Parameters 19-33
Dynamic Performance Views 19-34
Monitoring Long-Running Operations by Using V$ASM_OPERATION 19-36
ASM Instance Performance Diagnostics 19-37
ASM Performance Page 19-38
Database Instance Parameter Changes 19-39
ASM Scalability 19-40
Summary 19-41
20 Performance Tuning Summary
Objectives 20-2
Necessary Initialization Parameters with Little Performance Impact 20-3
Important Initialization Parameters with Performance Impact 20-4
Sizing Memory Initially 20-6
Database High Availability: Best Practices 20-7
Undo Tablespace: Best Practices 20-8
Temporary Tablespace: Best Practices 20-9
General Tablespace: Best Practices 20-11
Internal Fragmentation Considerations 20-12
Oracle Internal & Oracle Academy Use Only
xviii
Block Size: Advantages and Disadvantages 20-13
Automatic Checkpoint Tuning 20-14
Sizing the Redo Log Buffer 20-15
Sizing Redo Log Files 20-16
Increasing the Performance of Archiving 20-17
Automatic Statistics Gathering 20-19
Automatic Statistics Collection: Considerations 20-20
Commonly Observed Wait Events 20-21
Additional Statistics 20-22
Top 10 Mistakes Found in Customer Systems 20-23
Summary 20-25
Appendix A: Practices and Solutions
Appendix B: Using Statspack
Index -
Hi friends,
I am himansu, i am facing a problem during performance tunning of query in oracle , please guide me how to tune a query which will give better performance.907977 wrote:
Hi friends,
I am himansu, i am facing a problem during performance tunning of query in oracle , please guide me how to tune a query which will give better performance.Welcome to OTN
Please post your thread at SQL, PL/SQL. PL/SQL
and provide your sql query.
Hope this will help you. -
Need help for performance tunning
Hello,
I have 16K records return by query, it takes long time to proceed for 7K it takes 7.5 sec.
Note: I used all seeded tables only.
If possible please help me to tune it.
SELECT msi.inventory_item_id,msi.segment1,msi.rimary_uom_code , msi.primary_unit_of_measure
FROM mtl_system_items_b msi, qp_list_lines qpll,qp_pricing_attributes qppr,
mtl_category_sets_tl mcs,mtl_category_sets_b mcsb,
mtl_categories_b mc, mtl_item_categories mcb
WHERE msi.enabled_flag = 'Y'
AND qpll.list_line_id = qppr.list_line_id
AND qppr.product_attr_value = TO_CHAR (msi.inventory_item_id(+))
AND qppr.product_uom_code = msi.primary_uom_code
AND mc.category_id = mcb.category_id
AND msi.inventory_item_id = mcb.inventory_item_id
AND msi.organization_id = mcb.organization_id
AND TRUNC (SYSDATE) BETWEEN NVL (qpll.start_date_active,TRUNC (SYSDATE)) AND NVL (qpll.end_date_active,TRUNC (SYSDATE))
AND mcs.category_set_name = 'LSS SALES CATEGORY'
AND mcs.language = 'US'
AND mcs.category_set_id = mcsb.category_set_id
AND mcsb.structure_id = mc.structure_id
AND msi.organization_id = :p_organization_id
AND qpll.list_header_id = :p_price_list_id
AND mcb.category_id = :p_category_id;
Thanks and regards
Akil.Thanks Helios ,
here is answers
Databse version
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
PL/SQL Release 11.1.0.7.0
explain plan
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)|
|
0 | SELECT STATEMENT
| |
1 | 149 | 9439
(1)|
|
1 | NESTED LOOPS | | 1 |
149 | 9439 (1)|
|*
2 | HASH JOIN OUTER | | 1 |
135 | 9437 (1)|
|*
3 | HASH JOIN | | 1 |
71 | 9432 (1)|
|
4 | NESTED LOOPS | | 2 |
76 | 53 (0)|
|*
5 | TABLE ACCESS BY INDEX
ROWID| QP_LIST_LINES | 2 |
44 | 49 (0)|
|*
6 | INDEX SKIP SCAN | QP_LIST_LINES_N2 |
702 | | 20
(0)|
|*
7 | INDEX RANGE SCAN | QP_PRICING_ATTRIBUTES_N3 | 1 |
16 | 2 (0)|
|*
8 | TABLE ACCESS BY INDEX
ROWID | MTL_SYSTEM_ITEMS_B | 46254
| 1490K|
9378 (1)|
|*
9 | INDEX RANGE SCAN | MTL_SYSTEM_ITEMS_B_N9 | 46254 | |
174 (1)|
|
10 | TABLE ACCESS FULL | XX_WEB_ITEM_IMAGE_TBL |
277 | 17728 | 5 (0)|
|* 11 | INDEX RANGE SCAN | MTL_ITEM_CATEGORIES_U1 |
1 | 14 | 2
(0)|
Predicate Information (identified
by operation id):
2 -
access("XWIIT"."IMAGE_CODE"(+)="MSI"."SEGMENT1")
3 -
access("QPPR"."PRODUCT_ATTR_VALUE"=TO_CHAR("MSI"."INVENTORY_ITEM_ID")
AND
"QPPR"."PRODUCT_UOM_CODE"="MSI"."PRIMARY_UOM_CODE")
5 - filter(NVL("QPLL"."START_DATE_ACTIVE",TRUNC(SYSDATE@!))<=TRUNC(SYSDATE@!)
AND
NVL("QPLL"."END_DATE_ACTIVE",TRUNC(SYSDATE@!))>=TRUNC(SYSDATE@!))
6 -
access("QPLL"."LIST_HEADER_ID"=TO_NUMBER(:P_PRICE_LIST_ID))
filter("QPLL"."LIST_HEADER_ID"=TO_NUMBER(:P_PRICE_LIST_ID))
7 -
access("QPLL"."LIST_LINE_ID"="QPPR"."LIST_LINE_ID")
filter("QPPR"."PRODUCT_UOM_CODE" IS NOT NULL)
8 - filter("MSI"."ENABLED_FLAG"='Y')
9 - access("MSI"."ORGANIZATION_ID"=TO_NUMBER(:P_ORGANIZATION_ID))
11 -
access("MCB"."ORGANIZATION_ID"=TO_NUMBER(:P_ORGANIZATION_ID)
AND
"MSI"."INVENTORY_ITEM_ID"="MCB"."INVENTORY_ITEM_ID"
AND
"MCB"."CATEGORY_ID"=TO_NUMBER(:P_CATEGORY_ID))
filter("MCB"."CATEGORY_ID"=TO_NUMBER(:P_CATEGORY_ID))
Note
- 'PLAN_TABLE' is old version
TKprof Plan
TKPROF: Release 11.1.0.7.0 - Production on Fri Nov 15 06:12:26 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Trace file: LSSD_ora_19760.trc
Sort options: default
count = number of times OCI procedure was executed
cpu = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk = number of physical reads of buffers from disk
query = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows = number of rows processed by the fetch or execute call
SELECT msi.inventory_item_id,
msi.segment1,
primary_uom_code,
primary_unit_of_measure,
xwiit.image_url
FROM mtl_system_items_b msi,
qp_list_lines qpll,
qp_pricing_attributes qppr,
mtl_item_categories mcb,
xx_web_item_image_tbl xwiit
WHERE msi.enabled_flag = 'Y'
AND qpll.list_line_id = qppr.list_line_id
AND qppr.product_attr_value = TO_CHAR (msi.inventory_item_id)
AND qppr.product_uom_code = msi.primary_uom_code
AND msi.inventory_item_id = mcb.inventory_item_id
AND msi.organization_id = mcb.organization_id
AND TRUNC (SYSDATE) BETWEEN NVL (qpll.start_date_active,
TRUNC (SYSDATE))
AND NVL (qpll.end_date_active,
TRUNC (SYSDATE))
AND xwiit.image_code(+) = msi.segment1
AND msi.organization_id = :p_organization_id
AND qpll.list_header_id = :p_price_list_id
AND mcb.category_id = :p_category_id
call count cpu elapsed disk query current rows
Parse 2 0.00 0.00 0 0 0 0
Execute 2 0.00 0.00 0 0 0 0
Fetch 2 3.84 3.85 0 432560 0 1002
total 6 3.84 3.85 0 432560 0 1002
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 173
Rows Row Source Operation
501 NESTED LOOPS (cr=216280 pr=0 pw=0 time=115 us cost=9439 size=149 card=1)
2616 HASH JOIN OUTER (cr=211012 pr=0 pw=0 time=39 us cost=9437 size=135 card=1)
78568 HASH JOIN (cr=210997 pr=0 pw=0 time=3786 us cost=9432 size=71 card=1)
78571 NESTED LOOPS (cr=29229 pr=0 pw=0 time=35533 us cost=53 size=76 card=2)
78571 TABLE ACCESS BY INDEX ROWID QP_LIST_LINES (cr=9943 pr=0 pw=0 time=27533 us cost=49 size=44 card=2)
226733 INDEX SKIP SCAN QP_LIST_LINES_N2 (cr=865 pr=0 pw=0 time=4122 us cost=20 size=0 card=702)(object id 99730)
78571 INDEX RANGE SCAN QP_PRICING_ATTRIBUTES_N3 (cr=19286 pr=0 pw=0 time=0 us cost=2 size=16 card=1)(object id 99733)
128857 TABLE ACCESS BY INDEX ROWID MTL_SYSTEM_ITEMS_B (cr=181768 pr=0 pw=0 time=9580 us cost=9378 size=1526382 card=46254)
128857 INDEX RANGE SCAN MTL_SYSTEM_ITEMS_B_N9 (cr=450 pr=0 pw=0 time=1657 us cost=174 size=0 card=46254)(object id 199728)
277 TABLE ACCESS FULL XX_WEB_ITEM_IMAGE_TBL (cr=15 pr=0 pw=0 time=22 us cost=5 size=17728 card=277)
501 INDEX RANGE SCAN MTL_ITEM_CATEGORIES_U1 (cr=5268 pr=0 pw=0 time=0 us cost=2 size=14 card=1)(object id 99557)
Note: I modified query and it gives good result, now it takes 3 to 4 sec for 16000 records.
If possible can you plz explain what we have to take care while doing performance tunning
I am a fresher so don't have that much idea.
and also Thanks Hussein for your replay -
What are the tools in performance Tunning in ABAP/4
Thanks Regards,
KumarHi kumar,
Tools provided for Performance Analysis
Following are the different tools provided by SAP for performance analysis of an ABAP object
Run time analysis transaction SE30
This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
SQL Trace transaction ST05
The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
how to perform sql trace:
Poorly written SQL statements have the greatest impact on application performance. An SQL
statement using which an Oracle database system reads and/or sorts thousands or even millions of
rows of data can bring the database to a standstill. Indexes should be used properly to prevent such
situations from occurring. To analyze such problems you should use the SQL Trace (TCode ST05) to
with database access operations.
CAUTION
Only one person can perform an SQL trace at a time. Remember to turn off the
trace when you are finished. SQL trace slows the system down.
1. Using SQL Trace
1. Open a program that you want to analyze, in the editor, so that it is ready and waiting to be
executed.
2. Open a new session using the menu path System Create session.
3. Run transaction ST05 (enter /nst05-zero-five, not oh-five in the Command field, or choose
the menu path System Utilities Performance Trace).
4. Then the initial screen of the test tool appears.
The status of the Performance Trace is displayed in the lower part of the screen. This status tells you
three things namely
Whether any of the Performance Traces are switched on
The users for whom Performance Trace is enabled
The user that switched the Performance Trace on
If the trace is switched on you must switch it off before you can proceed. There are two cases in
which the trace needs to be switched off. They are
If the trace was started within the past hour, it is possible that it is still being used. Contact the
indicated user or try again later
If the trace was started hours or days ago, the user probably left it on by mistake and it can be
safely turned off
To turn off the trace, press the Trace Off pushbutton.
5. The initial screen has various trace functions such as SQL Trace, Enqueue Trace, RFC
Trace
6. Select SQL Trace.
7. There are various options under which trace can be switched on. They are
If you want to switch on the trace under your user name, choose Trace on.
If you want to switch on the trace for another user or user group, choose Trace on for user.
To enter a single user, specify the user name.
To enter a user group, specify a search pattern (you can use the normal wildcards).
If you want to change the user or user group, switch off the Performance Trace and then restart it,
entering the new users or user group.
8. Now switch back to the window containing your editor session (the one with your program
waiting to be executed).
9. Press F8 to run your program.
Note Just press F8 and do nothing. Do not even press the Back button.
10. When your program has run and the hourglass is no longer displayed, switch back to the trace
window.
11. Press the Trace Off pushbutton.
12. Once Performance Trace is switched off, you can analyze the data
Using Runtime Analysis Tool (SE30)
1. You can open the Runtime Analysis tool as follows:
To start from Choose
Any screen System Utilities Runtime Analysis Execute
Initial screen of ABAP
Workbench
Test Runtime Analysis
Initial screen of ABAP Editor Program Execute Runtime Analysis
ABAP Editor Utilities More utilities Runtime Analysis
2. In the simplest case, you would enter a short description and a measurement object
(transaction, program, or function module) to run the analysis in the current session.
3. In the Measurement restrictions group box, you can make more specific restrictions for the
measurement. For example, you may want to include only certain statements or time periods.
(For further information refer section 3. 0).
4. To start the measurement, choose Measure runtime. From the initial screen, you can
specify whether the analysis should run in the same session or in a parallel session using the
Enable/Disable button in the In parallel session group box.
5. Run the transaction, program, or function module as normal.
6. Return to the initial screen of the Runtime Analysis transaction. To do so, either leave
transaction, program, or function module as normal, or start the runtime analysis again.
7. The name of the performance data file that has just been created is displayed at the bottom of
the initial screen. The file created by the system is added to the list of performance data files.
You can now analyze, print, or delete the file, or save it locally. The Performance file group
box contains options for analyzing performance files. (For further information refer sections 4.
0 and 5. 0)
regards,
keerthi -
How to do Performance tunning in OBIEE
Hi All,
We are using OBIEE 10.3.4 version on windows envorinment .In our OBIEE project we are using 9 reports my requriment is we need to do performance tunning for OBIEE side.For eace report accessing its taking around 80 sec.We need to decrease these accessing time,is there any possibility to access all the reports with less response time in OBIEE side.
Could you anyone suggest how to do performance tunning in OBIEE side.
Thanks,
Vijay.Vijay,
Plz refer
http://www.business-intelligence-quotient.com/?p=119
http://prolynxuk.com/blog/?p=173
http://businessdecisionsystems.com/blog/?p=486
Here is the section from the BIEE admin guide:
=======================
Usage Examples
This section provides a few examples of how to use Oracle hints in conjunction with the Oracle BI Server. For more information about Oracle hints, refer to the Oracle SQL Reference documentation for the version of the Oracle server that you use.
Index Hint
The Index hint instructs the optimizer to scan a specified index rather than a table. The following hypothetical example explains how you would use the Index hint. You find queries against the ORDER_ITEMS table to be slow. You review the query optimizer's execution plan and find the FAST_INDEX index is not being used. You create an Index hint to force the optimizer to scan the FAST_INDEX index rather than the ORDER_ITEMS table. The syntax for the Index hint is index(table_name, index_name). To add this hint to the repository, navigate to the Administration Tool's Physical Table dialog box and type the following text in the Hint field:
index(ORDER_ITEMS, FAST_INDEX)
Leading Hint
The Leading hint forces the optimizer to build the join order of a query with a specified table. The syntax for the Leading hint is leading(table_name). If you were creating a foreign key join between the Products table and the Sales Fact table and wanted to force the optimizer to begin the join with the Products table, you would navigate to the Administration Tool's Physical Foreign Key dialog box and type the following text in the Hint field:
leading(Products)
So, the table names "order_items" and "products" in the above documentation will not be the same after BIEE puts aliases on them.
============
Hope this is useful..
Edited by: Deepak Gupta on Aug 1, 2011 7:18 AM -
Real Application Testing/Sql Performance Analyzer Docs in 10g....
I believed that both the tools mentioned in the subject are a part of 11g and so are in the 11g docs.
http://download.oracle.com/docs/cd/B28359_01/server.111/e12253/toc.htm
But I was just looking at 10g book listing and I saw the same book in 10g documentation as well.
http://download.oracle.com/docs/cd/B19306_01/server.102/e12024/toc.htm
Now my best guess is that this is due to the backporting of 11g tools for the previous releases. Means that we can do RAT or use SPA in pre 11g databases as well so this doc book is added. Is it correct or there is some other reason?
Cheers
Aman....Real Application Testing was introduced as a new feature in Oracle Database 11g. The documentation for Real Application Testing was released in 4 phases.
In the initial phase, the usage of Real Application Testing was documented in the Performance Tuning Guide for release 11.1.
In the second phase, the Real Application Testing User's Guide was released for release 10.2 to document certain backported functionalities. For Database Replay, the capability to capture a database workload was backported. For SQL Performance Analyzer, the capability to capture a SQL workload into a SQL tuning set was backported. These functionalities were backported to Oracle Database 10g Release 2 (version 10.2.0.4 or higher) to support customers who want to use Real Application Testing to test database upgrades from a previous version of Oracle Database to Oracle Database 11g.
In the third phase, the Real Application Testing Addendum was released for release 11.1 to document the added functionality to read SQL trace files from Oracle Database 9i to construct a SQL tuning set that can be used as an input source for SQL Performance Analyzer in release 11.1.0.7.
In the final phase, all available documentation for Real Application Testing contained in the above documents were consolidated into the Real Application Testing User's Guide for release 11.1. Going forward, this guide will contain all documentation of Real Application Testing and be updated for each release.
Regards,
Immanuel -
User guide: MSI HQ USB BIOS Flash Tool
Guide based on USB tool v1.17c
HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation. It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation. (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
Symptoms that your USB key need a fix after booting from the USB key:
* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.
Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
Read the three notes that follow first before you move on:
1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
Contents of the Guide:
0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
3.2. Method 2: Processing a BIOS File Directly
3.3. Method 3: SureHands Live Update
3.4. Method 4: Geometry Change
4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
5.1. BIOS Settings to Check
5.2. Booting from USB Flash Drive
5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
6. FAQ: Common Problems & Solutions
7. Version History
0. Preconditions & System Requirements
The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash. The Tool is designed to work with MSI Retail Boards & Laptops only.
Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32). NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
1. Basic Description of Functionality
The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure. Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
* Excluding the Geometry Change method which will destroy all data on the USB storage device.
2. Installing/Starting the tool
Treat the forum's USB Flashing Tool like a regular application. Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing. Both, the installer version and the stand-alone version, do precisely the same job. Which of the two versions you use, is solely up to you and your preferences. The stand-alone version can be started directly by clicking on the executable file. The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
When you start the tool a DOS box should open up to provide you with status messages and prompts. Do not close that box unless you want to abort the preparation procedure!
Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
3. Choosing a Preparation Method
If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes. The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board). If you have downloaded such an archive, you should choose the first method from the option box.
You do not need to extract the files from the BIOS archive. The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive. You don't have to worry about anything else. All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
3.2. Method 2: Processing a BIOS File Directly
If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box. In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility. If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used. All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
3.3. Method 3: SureHands Live Update
"SureHands Live Update" is the third operation method you can choose from the option box. It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well. If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
Not all MSI Retail Boards are currently supported. With every update of the USB Flashing Tool more boards will be added. At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)
Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)
After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard. It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash. SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist. If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment. That message is part of a prediction feature that tries to determine future BIOS Releases. If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
3.4 Geometry Change
If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
Select your drive then let the tool do it's business.
Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.
4. Selecting the USB Flash Drive for preparation
When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it. This can happen in rare cases, but it is usually no problem.
The tool will check the selected drive and will provide you with status messages. If everything is okay, the message should look like this:
The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing. If the procedure was successful, you will get the following message in the DOS box:
5. BIOS-Settings, Booting & Flashing
If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
5.1. BIOS Settings to Check
Check USB-related Options in BIOS:
- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.
Not all of these options may be found in BIOS and the precise name may vary as well. Just make sure you checked for such options and that they are enabled (if present).
Another option you should check for is "Boot Sector Protection". If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
5.2. Booting from USB Flash Drive
To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu. From here, you can select you drive directly without having to adjust the boot sequence in BIOS. Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
5.3. Flashing Procedure/Running MemTest86+
As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
The flashing procedure will automatically be initiated from there. You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash. A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts. You do not need to enter any commands in DOS. All you have to do is acknowledge the information on the screen by pressing a key.
The flash itself will only take a couple of seconds (20-30s at the most). If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU. Read the >>Clear CMOS Guide<< for further information.
After clearing CMOS you have completed the BIOS-Flash.
Guide created by Jack The Newbie and the forum teamVersion updated to 1.18x:
* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0
* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.
Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
How i can roll back to my old BIOS version?
The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
How i can re-flash to my original BIOS version and from where can i get it?
A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.3
BIOS Date: 05/08/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.6
BIOS Date: 11/30/2009
Then choose your old BIOS version from the list:
The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:
It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:
The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:
"K9A2 CF wont flash to Bios v. 1.A !!!"
Quote from: Fingon on 25-October-09, 16:53:15
Hi MSI,
I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
My questions are:
1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
Thank you for any help!!
EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?
Thx for replies!
Quote from: Jack t.N. on 25-October-09, 17:16:16
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear. The fact that this message appears, shows, that there was actually something programmed to the chip.
If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
The BIOS Version should be shown on the POST Status Screen and there should be a date behind it. Please check the BIOS Date and write it down:
Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"? Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten). The hexadecimal notation is only used in the BIOS File Ending. Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
Here is a piece of well-meant advice for now and the future: MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version. Why? Because this tool is stupid and one of there most risky applications for performing a BIOS Flash. Please uninstall it completely.
Why do I call it stupid? I call it stupid because it does not differentiate between hexadecimal notation and decimal notation. It will show you that "v1.A0" is available. The it will flash it, if you allow it to do so. Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten). When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you. The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Quote from: Fingon on 25-October-09, 18:03:44
Thank you for the quick reply!!
Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
So thank you! Problem is solved.
Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
Quote from: Lostsoul777 on 14-August-09, 05:46:25
I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
Quote from: LinuxGuy on 29-December-09, 01:17:45
My computer does not have a floppy drive. How do I update the BIOS? (I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults. So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around). So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated. Either way, I would like to manually flash it in DOS. Is it safe to burn the setup files to CD and boot from CD into DOS?
That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
Quote
I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
What's going on?
Just run the MSIHQ USB Flash Tool and will show you all that you need to know
Examples[with real/accurate info]:
MSI Eclipse:
BIOS version 1.9:
BIOS version 1.10:[Tool now shows both BIOS versions alias]
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:30:55,34
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.9
BIOS Date: 09/22/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:37:25,66
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date: 10/27/2009
More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
More examples =>945GCM5-F V2 (FSB 1333) :
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:47:34,35
Mainboard: MS-7267
PCB Version: 4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date: 11/20/2008
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:52:46,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date: 06/02/2009
More examples =>780GT-E63 [N/A at MSI web yet] :
For MSI Notebooks such decoding isn't need, examples:
* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
- In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
- This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:00:53,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.DX2
Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:12:23,95
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.KV7
Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:18:34,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V3.9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.390
Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:22:24,04
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V8.1B9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.819
Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:25:38,51
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.4E0
Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:28:16,62
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.1B1
Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:31:57,78
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.IF5
Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:36:02,40
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.7O0
Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:39:11,84
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.C86
Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:49:38,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.GP6
Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:53:17,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.UH0
Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
Maybe you are looking for
-
Error application path: C: \ Windows \ explorer.exe
Signature problem Problem Event Name: BEX Application Name: Explorer.EXE Application Version: 6.1.7601.17567 Application Timestamp: 4d6727a7 Name faulty module: StackHash_0a9e Fault module version: 0.0.0.0 Faulty module timestamp: 00000000 Aw
-
1 payment methods, 3 DME files
Hi gurus, Within 1 payment methods (outgoing payments in local currency via bank transfer) I have 3 different house banks, each of them have its own custom DME file format. How to set up the payment program so that it generates 3 different DME files
-
ALV Report to KSB1 Report-- KSB1 Report outputs in Non-ALV Format
Hi Gurus, I am calling KSB1 from report ALV output. After execution of KSB1, Report outputs in Classical report format. While I execute KSB1 manually it shows in ALV Report. From my report how to retain output of KSB1 in ALV Format. Thanks in advance
-
Hi, There are discount conditions, like RL01-Vendor Discount % in which access sequence 006 (vendor discount) is assigned. RA01-Discount % on Gross in which access sequence KB01 (Header Discount) is assigned along with Pricing procedure RM0001. R000-
-
-43 error when import Imovie into Imovie
Hello, I want to import an imovie into another Imovie but I get a -43 error : saying impossible to import the file. Quicktime could not analyse it : -43. I removed plug ins from library/Imovie What I did : open a Imovie project. Dragged a project fro