ADDM Findings
hi
I get a finding 'Individual database segments responsible for significant
user I/O wait were found' when i run ADDM
Pls anybody help me to elaborate this.
Database 10g rel2
Windows 2003 EE 32 bit
sga_max_size=1.5 gb
db_cache=1gb
pga=3 gb
dedicated server
sga
Oracle instance parameters could be considered for tuning on this issue if memory advisors show constant low ratios, otherwise, the reason for poor segment performance could be explained depending if it is due to queries (multiple processes creating a bottle neck) or transactions (manually managed segments with an associated high cpu usage).
~ Madrid
Similar Messages
-
I don't see the last addm findings when I enter in Enterprise Manager
Hello:
I don't see the last addm findings when I enter in Enterprise Manager. The Snapshots are being taken periodically but when I enter the Home of Enterprise Manager I don't see the findings of ADDM. I can run manually ADDM but in fact the ADDM is run every hour. Any idea?
I use Oracle 10r2 Enterprise edition
Thanks
Jordi Martinhi,
looks like that you cannot upload the xml files from your agent
you can try to perform a clean restart of your agent :
1) emctl stop agent
2)Remove the following files:
$AGENT_HOME/sysman/emd/state/*
$AGENT_HOME/sysman/emd/collection/*
$AGENT_HOME/sysman/emd/upload/*
$AGENT_HOME/sysman/emd/lastupld.xml
$AGENT_HOME/sysman/emd/agntstmp.txt
$AGENT_HOME/sysman/emd/blackouts.xml
$AGENT_HOME/sysman/emd/protocol.ini
3) emctl start agent
4) emctl clearstate agent
5) emctl secure agent your_pwd
6) emctl upload agent
7)emctl status agent ->to check agent status
br,
mrak -
Pressing the ADDM Findings Value Results in Internal Error
My database page shows that I have 7 ADDM findings. When I press the value, it displays a page with the following message "Internal Error has occured. Check the log file for details.".
I have checked the log, but nothing really pops out. The database is 10g and Toad does the report with no configuration.
Anyone with any thoughts about this?
Thanks,
JohnSolved the problem. Reran Catproc. It re-created the proper synonyms, etc.
-
ADDM Findings Recommendation Language
Hello.
I have a question on how to change the language that the ADDM Findings Recommendation are displayed. At this link you have a print-screen with the message I refer to.
I want to see these messages in English (the ones highlighted with green arrows).
To give some more details regarding the configuration of the instance, I should mention that initially the database was configured with a NLS_LANG (I can't remember it exactly right now), and then after a while I've changed it to ENGLISH_AMERICA.WE8MSWIN1252 because the language of sqlplus was the old one and it solved the problem and now it is English, but only the messages from ADDM findings are still in the old NLS_LANG setting.
Please let me know if you have any idea where from or how I can change this setting.
Also if you need any other detail, just tell me.
Thanks.Every job has the NLS_ENV set on Romanian:
NLS_LANGUAGE='ROMANIAN' NLS_TERRITORY='ROMANIA' NLS_CURRENCY='LEI' NLS_ISO_CURRENCY='ROMANIA' NLS_NUMERIC_CHARACTERS=',.' NLS_CALENDAR='GREGORIAN' NLS_DATE_FORMAT='DD-MM-RRRR' NLS_DATE_LANGUAGE='ROMANIAN' NLS_SORT='ROMANIAN' NLS_TIME_FORMAT='HH24:MI:SSXFF' NLS_TIMESTAMP_FORMAT='DD-MM-RRRR HH24:MI:SSXFF' NLS_TIME_TZ_FORMAT='HH24:MI:SSXFF TZR' NLS_TIMESTAMP_TZ_FORMAT='DD-MM-RRRR HH24:MI:SSXFF TZR' NLS_DUAL_CURRENCY='LEI' NLS_COMP='BINARY' NLS_LENGTH_SEMANTICS='BYTE' NLS_NCHAR_CONV_EXCP='FALSE'
Where from can I change these settings. The instance nls is set like this:
SQL> show parameter nls
NAME TYPE VALUE
nls_calendar string
nls_comp string
nls_currency string
nls_date_format string
nls_date_language string
nls_dual_currency string
nls_iso_currency string
nls_language string AMERICAN
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
NAME TYPE VALUE
nls_sort string
nls_territory string AMERICA
nls_time_format string
nls_time_tz_format string
nls_timestamp_format string
nls_timestamp_tz_format string -
ADDM Findings Top SQL Statements
Hi,
I have run addmrpt.sql for 1 month of time using snapshots and every ADDM report says that sql statement having id **** listed under top sql statements findings and recommendation is to tune using sql tunning advisor. It has 2-4 seconds elapsed time.But when i go through AWR report instance efficiency report and all are normal.
Can anyone please confirm whether I should recommend to tune this SQL statement to my vendor ?
Thanks,
TKbelow is the sql I found in ADDM. As I understood it is an intername SQL not an application SQL. When i searched it in internet found that it is related with check_oracle_health plugin. can you please help me to understand this nagios concept and the relationship it has with oracle software. And also how should I identify which methods we are using to monitor database internally?
SELECT
a.tablespace_name "Tablespace",
b.status "Status",
b.contents "Type",
b.extent_management "Extent Mgmt",
a.bytes bytes,
a.maxbytes bytes_max,
c.bytes_free + NVL(d.bytes_expired,0) bytes_free
FROM
-- belegter und maximal verfuegbarer platz pro datafile
-- nach tablespacenamen zusammengefasst
-- => bytes
-- => maxbytes
SELECT
a.tablespace_name,
SUM(a.bytes) bytes,
SUM(DECODE(a.autoextensible, 'YES', a.maxbytes, 'NO', a.bytes))
maxbytes
FROM
dba_data_files a
GROUP BY
tablespace_name
) a,
sys.dba_tablespaces b,
-- freier platz pro tablespace
-- => bytes_free
SELECT
a.tablespace_name,
SUM(a.bytes) bytes_free
FROM
dba_free_space a
GROUP BY
tablespace_name
) c,
-- freier platz durch expired extents
-- speziell fuer undo tablespaces
-- => bytes_expired
SELECT
a.tablespace_name,
SUM(a.bytes) bytes_expired
FROM
dba_undo_extents a
WHERE
status = 'EXPIRED'
GROUP BY
tablespace_name
) d
WHERE
a.tablespace_name = c.tablespace_name
AND a.tablespace_name = b.tablespace_name@@@@@@@@
AND a.tablespace_name = d.tablespace_name
UNION ALL
SELECT
d.tablespace_name "Tablespace",
b.status "Status",
b.contents "Type",
b.extent_management "Extent Mgmt",
sum(a.bytes_free + a.bytes_used) bytes, -- allocated
SUM(DECODE(d.autoextensible, 'YES', d.maxbytes, 'NO', d.bytes))
bytes_max,
SUM(a.bytes_free + a.bytes_used - NVL(c.bytes_used, 0)) bytes_free
FROM
sys.v_$TEMP_SPACE_HEADER a,
sys.dba_tablespaces b,
sys.v_$Temp_extent_pool c,
dba_temp_files d
WHERE
c.file_id(+) = a.file_id
and c.tablespace_name(+) = a.tablespace_name
and d.file_id = a.file_id
and d.tablespace_name = a.tablespace_name
and b.tablespace_name = a.tablespace_name
GROUP BY
b.status,
b.contents,
b.extent_management,
d.tablespace_name
ORDER BY
1 -
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 -
All,
Recently we have faced extremely poor database performance.
There were some observations and configuration details about environment setup.
Configuration details
- OS = Windows server 2003 64bit, Server RAM 16 GB
- DB Ver = 10g 64 bit (10.2.0.1.0)
- RAM = 16 GB, SGA 11 GB
- Application is developed in java, and Compiere application server is used.
- In application code to communicate with database bind variables are not used.
- Database is ASM based, no raid configured.
- Database is in no archive log mode, as this is not production environment, we were doing parallel run of the application.
Observations
- when database is started its response is much better but gradually it slow down and just after 20-30 minutes db response becomes very poor. During this time around 20-40 users were using application and there were around 150 plus database sessions.
- during execution there are some stages when ADDM findings related to SGA size and the recommended size was around 22GB, other findings include hard parsing of queries
I have shared the awr and stats_pack report for the time server was loaded and not performing as desired.
for awr report visit http://asim.net84.net/awr.html
& for stats pack report visit http://asim.net84.net/stat_pack.lst
Any tip/guidance will be much appreciated.
Regards,
Asimright now SGA size is reduced to 4 GB, and no performance gain is observed even with less users connected with databases.
SGA_SIZE SGA_SIZE_FACTOR ESTD_DB_TIME ESTD_DB_TIME_FACTOR ESTD_PHYSICAL_READS
4096 1 3027 1 4519385
1024 0.25 3178 1.0499 4646380
2048 0.5 3037 1.0033 4528876
8192 2 3013 0.9954 4508087
5120 1.25 3025 0.9993 4518481
6144 1.5 3024 0.999 4518029
7168 1.75 3015 0.996 4508538
3072 0.75 3031 1.0013 4523904 -
Hi,
Oracle Version:- Oracle Database Enterprise Edition Release 10.2.0.1
OS- Microsoft Windows 64-Bit 2003R2
Whenever load on db is increased , my EM shows follwing to me: IX-Lock Contention Found, and Latch- Cache Buffer Chains.
Can someone please explain what does this mean ?. And what may be possible causes for it ?
VinitaDear Vinita,
Let me tell you the magical keyword in your expression;
Whenever load on db is increasedWhat sort of load? Oracle does not create the lock and latch contention by itself but the application can cripple the database so bad!
First observe your application and see what the sessions are doing. Run ASH to find out the queries. Run AWR and see the ADDM findings (if you have already purchased the diagnostic pack for your production system, if you are on a test environment just run).
You can also see the metalink for those events and their information.
At the end those are contentions and needs to be observed in my opinion.
Regards.
Ogan -
Run single, consolidated AWR report on 4 adjacent snapshots?
We typically collect snapshots in 60 minute periods for our instances. Recently, a customer ran a test for 3.5 hours. I created an ADDM report spanning the 4 snapshots (useful). However, being able to generate an AWR report for the same 3.5 hour duration would add additional insight.
Currently, I can generate 4 separate AWR reports, one for each hour. However, I'd like to be able to create a single, consolidated AWR report. This way, I don't have to manually sum useful numbers like Executions contained in 4 separate AWR reports for SQL ordered by Elapsed Time, etc.
Can I create one, aggregated AWR report? Or is my only other option to revise the snapshot collection duration before the next scheduled load test occurs (e.g. to 3.5 hours for a 3.5 hour load test)? Would prefer not to have to do this. But is it the only available option to accomplish what I need?
Thanks very much.Thanks Rob. I'm able to run an ADDM report for the 3.5 hour duration I need. No problem there. I want to run a consolidated "AWR report" on multiple snapshots, e.g:
Performance > Snapshots > Click a snapshot ID > Click Report tab (by default you are on the Details tab).
This AWR report gives a lot more information than an ADDM report.
Can I select multiple snapshots for the AWR report? I'm already doing so with ADDM reports.
The title for the "AWR" report I'm interested in is: "WORKLOAD REPOSITORY report for." It doesn't have ADDM findings in it because it's not making recommendations--just reporting a large amount of snapshot details.
I'm guessing now that the answer is "no" to what I'm asking. Hope this makes sense. -
Queries giving results to slowly
Hi DBAs,
Our Database is running on the 10.2.0.4 and the database(UAT DB) contain very less number of Records in the tables.
My application team facing problem with Queries output,the queries taking execution time very less and its showing out to user after 15min.
how to tune database for overcome this problem and as a DBA what I need monitor ,is there any memory parameter need to change .
Thanks!
tmadugulaDear tmadugula,
You can either use AWR reports and ADDM findings (if you have purchased the diagnostic pack) and / or statspack to analyze the bottleneck. You can also use some specific dynamic performance views like v$sysstat, v$sesstat, v$system_event for analyzing.
You can create an SQL Tuning Set and place your relevant SQL queries (v$sql) and run the SQL Tuning Advisor or SQL Access Advisor. Access advisor can be used to spot neccessary indexes, materialized views or materialized view logs.
Hope That Helps.
Ogan -
Performance issue in DB need help with analysing this ADDM report
Hi,
My environment:
Os: RHEL5U3 / 11.1.0.7 64 bit / R12.1.1 64 bit
Issue:
Few days are am facing serious of performance problem in our Production instance. Normally the issue will occur 5 to 10 minutes occasionally per day. At the time of issue we not able to access the EBS application its taking time to load. But backend all the oracle, listener and apps services are up and running. No locks at table and session level. Cpu and memory usage is normal.
We have monitored using "Enterprise Manager" for this issue and we found the wait session present more in Active session tab. At this time EBS application is not able access its loading too time. After some time the in Active session tab the wait session came normal and when we try to access the EBS application its working fine.
We try to find the cause of the issue by running addm report. But am not able to understand what its says. Kindly suggests me
ADDM Report for Task 'TASK_42656'
Analysis Period
AWR snapshot range from 14754 to 14755.
Time period starts at 17-APR-12 11.00.22 AM
Time period ends at 17-APR-12 12.00.33 PM
Analysis Target
Database 'PRD' with DB ID 1789440879.
Database version 11.1.0.7.0.
ADDM performed an analysis of instance PRD, numbered 1 and hosted at
advgrpdb.advgroup.ae.
Activity During the Analysis Period
Total database time was 18674 seconds.
The average number of active sessions was 5.17.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 Top SQL by DB Time 3.43 | 66.33 5
2 Buffer Busy 2.52 | 48.81 5
3 Buffer Busy 1.39 | 26.81 2
4 Log File Switches .91 | 17.56 1
5 Buffer Busy .56 | 10.87 2
6 Undersized SGA .38 | 7.37 1
7 Commits and Rollbacks .28 | 5.42 1
8 Undo I/O .18 | 3.53 0
9 CPU Usage .13 | 2.57 1
10 Top SQL By I/O .11 | 2.21 1
Findings and Recommendations
Finding 1: Top SQL by DB Time
Impact is 3.43 active sessions, 66.33% of total activity.
SQL statements consuming significant database time were found.
Recommendation 1: SQL Tuning
Estimated benefit is 1.59 active sessions, 30.8% of total activity.
Action
Investigate the SQL statement with SQL_ID "a49xsqhv0h31b" for possible
performance improvements.
Related Object
SQL statement with SQL_ID a49xsqhv0h31b.
SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
R.Priority, U.User_Name, O.Oracle_Username,
O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
X.Argument100, R.number_of_arguments, C.CD_Name,
NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
(R.OPS_INSTANCE =
decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
P.Application_Id(+) And R.Concurrent_Program_Id =
P.Concurrent_Program_Id(+) And R.Program_Application_Id =
A.Application_Id(+) And P.Executable_Application_Id =
E.Application_Id(+) And P.Executable_Id =
E.Executable_Id(+) And P.Executable_Application_Id =
A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
= C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
:q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
Q.Max_Processes And R.Rowid = :reqname And
((P.Execution_Method_Code != 'S' OR
(R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
R.status_code NoWait
Rationale
SQL statement with SQL_ID "a49xsqhv0h31b" was executed 4686 times and
had an average elapsed time of 1.2 seconds.
Rationale
Waiting for event "buffer busy waits" in wait class "Concurrency"
accounted for 85% of the database time spent in processing the SQL
statement with SQL_ID "a49xsqhv0h31b".
Rationale
Waiting for event "log file switch (checkpoint incomplete)" in wait
class "Configuration" accounted for 9% of the database time spent in
processing the SQL statement with SQL_ID "a49xsqhv0h31b".
Recommendation 3: SQL Tuning
Estimated benefit is .56 active sessions, 10.91% of total activity.
Action
Investigate the SQL statement with SQL_ID "5d7957yktf3nn" for possible
performance improvements.
Related Object
SQL statement with SQL_ID 5d7957yktf3nn.
UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
Rationale
SQL statement with SQL_ID "5d7957yktf3nn" was executed 266 times and had
an average elapsed time of 7.6 seconds.
Rationale
Waiting for event "buffer busy waits" in wait class "Concurrency"
accounted for 86% of the database time spent in processing the SQL
statement with SQL_ID "5d7957yktf3nn".
Rationale
Waiting for event "log file switch (checkpoint incomplete)" in wait
class "Configuration" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "5d7957yktf3nn".
Finding 2: Buffer Busy
Impact is 2.52 active sessions, 48.81% of total activity.
Read and write contention on database blocks was consuming significant
database time.
Recommendation 1: Application Analysis
Estimated benefit is 1.42 active sessions, 27.44% of total activity.
Action
Trace the cause of object contention due to SELECT statements in the
application using the information provided.
Related Object
Database object with ID 34562.
Rationale
The SELECT statement with SQL_ID "a49xsqhv0h31b" was significantly
affected by "buffer busy" waits.
Related Object
SQL statement with SQL_ID a49xsqhv0h31b.
SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
R.Priority, U.User_Name, O.Oracle_Username,
O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
X.Argument100, R.number_of_arguments, C.CD_Name,
NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
(R.OPS_INSTANCE =
decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
P.Application_Id(+) And R.Concurrent_Program_Id =
P.Concurrent_Program_Id(+) And R.Program_Application_Id =
A.Application_Id(+) And P.Executable_Application_Id =
E.Application_Id(+) And P.Executable_Id =
E.Executable_Id(+) And P.Executable_Application_Id =
A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
= C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
:q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
Q.Max_Processes And R.Rowid = :reqname And
((P.Execution_Method_Code != 'S' OR
(R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
R.status_code NoWait
UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
Recommendation 1: Schema Changes
Estimated benefit is .03 active sessions, .62% of total activity.
Action
Consider rebuilding the TABLE "APPLSYS.FND_LOGIN_RESP_FORMS" with object
ID 34651 using a higher value for PCTFREE.
Related Object
Database object with ID 34651.
Rationale
The UPDATE statement with SQL_ID "cqc5crhxxt36t" was significantly
affected by "buffer busy" waits.
Related Object
SQL statement with SQL_ID cqc5crhxxt36t.
UPDATE FND_LOGIN_RESP_FORMS FLRF SET END_TIME = SYSDATE WHERE
FLRF.LOGIN_ID = :B2 AND FLRF.LOGIN_RESP_ID = :B1 AND FLRF.END_TIME IS
NULL AND (FLRF.FORM_ID, FLRF.FORM_APPL_ID) = (SELECT F.FORM_ID,
F.APPLICATION_ID FROM FND_FORM F, FND_APPLICATION A WHERE F.FORM_NAME
= :B4 AND F.APPLICATION_ID = A.APPLICATION_ID AND
A.APPLICATION_SHORT_NAME = :B3 )
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 4: Log File Switches
Impact is .91 active sessions, 17.56% of total activity.
Log file switch operations were consuming significant database time while
waiting for checkpoint completion.
This problem can be caused by use of hot backup mode on tablespaces. DML to
tablespaces in hot backup mode causes generation of additional redo.
Recommendation 1: Database Configuration
Estimated benefit is .91 active sessions, 17.56% of total activity.
Action
Verify whether incremental shipping was used for standby databases.
Symptoms That Led to the Finding:
Wait class "Configuration" was consuming significant database time.
Impact is .91 active sessions, 17.63% of total activity.
Finding 5: Buffer Busy
Impact is .56 active sessions, 10.87% of total activity.
A hot data block with concurrent read and write activity was found. The block
belongs to segment "ICX.ICX_SESSIONS" and is block 243489 in file 36.
Recommendation 1: Application Analysis
Estimated benefit is .56 active sessions, 10.87% of total activity.
Action
Investigate application logic to find the cause of high concurrent read
and write activity to the data present in this block.
Related Object
Database block with object number 37562, file number 36 and block
number 243489.
Rationale
The SQL statement with SQL_ID "5d7957yktf3nn" spent significant time on
"buffer busy" waits for the hot block.
Related Object
SQL statement with SQL_ID 5d7957yktf3nn.
UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
Rationale
The SQL statement with SQL_ID "326up1aym56dd" spent significant time on
"buffer busy" waits for the hot block.
Related Object
SQL statement with SQL_ID 326up1aym56dd.
UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
Recommendation 2: Schema Changes
Estimated benefit is .56 active sessions, 10.87% of total activity.
Action
Consider rebuilding the TABLE "ICX.ICX_SESSIONS" with object ID 37562
using a higher value for PCTFREE.
Related Object
Database object with ID 37562.
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 6: Undersized SGA
Impact is .38 active sessions, 7.37% of total activity.
The SGA was inadequately sized, causing additional I/O or hard parses.
The value of parameter "sga_target" was "4096 M" during the analysis period.
Recommendation 1: Database Configuration
Estimated benefit is .12 active sessions, 2.33% of total activity.
Action
Increase the size of the SGA by setting the parameter "sga_target" to
4608 M.
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Hard parsing of SQL statements was consuming significant database time.
Impact is .13 active sessions, 2.51% of total activity.
Contention for latches related to the shared pool was consuming
significant database time.
Impact is 0 active sessions, .03% of total activity.
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 7: Commits and Rollbacks
Impact is .28 active sessions, 5.42% of total activity.
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
Recommendation 1: Host Configuration
Estimated benefit is .28 active sessions, 5.42% of total activity.
Action
Investigate the possibility of improving the performance of I/O to the
online redo log files.
Rationale
The average size of writes to the online redo log files was 163 K and
the average time per write was 68 milliseconds.
Symptoms That Led to the Finding:
Wait class "Commit" was consuming significant database time.
Impact is .28 active sessions, 5.42% of total activity.
Finding 8: Undo I/O
Impact is .18 active sessions, 3.53% of total activity.
Undo I/O was a significant portion (26%) of the total database I/O.
No recommendations are available.
Symptoms That Led to the Finding:
The throughput of the I/O subsystem was significantly lower than
expected.
Impact is .08 active sessions, 1.46% of total activity.
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Finding 9: CPU Usage
Impact is .13 active sessions, 2.57% of total activity.
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
Recommendation 1: SQL Tuning
Estimated benefit is .13 active sessions, 2.57% of total activity.
Finding 10: Top SQL By I/O
Impact is .11 active sessions, 2.21% of total activity.
Individual SQL statements responsible for significant user I/O wait were
found.
Recommendation 1: SQL Tuning
Estimated benefit is .11 active sessions, 2.22% of total activity.
Action
Run SQL Tuning Advisor on the SQL statement with SQL_ID "b3pnc5yctv2z5".
Related Object
SQL statement with SQL_ID b3pnc5yctv2z5.
INSERT INTO ZX_TRANSACTION_LINES_GT( APPLICATION_ID ,ENTITY_CODE
,EVENT_CLASS_CODE ,TRX_ID ,TRX_LEVEL_TYPE ,TRX_LINE_ID ,LINE_CLASS
,LINE_LEVEL_ACTION ,TRX_LINE_TYPE ,TRX_LINE_DATE
,LINE_AMT_INCLUDES_TAX_FLAG ,LINE_AMT ,TRX_LINE_QUANTITY ,UNIT_PRICE
,PRODUCT_ID ,PRODUCT_ORG_ID ,UOM_CODE ,PRODUCT_CODE ,SHIP_TO_PARTY_ID
,SHIP_FROM_PARTY_ID ,BILL_TO_PARTY_ID ,BILL_FROM_PARTY_ID
,SHIP_FROM_PARTY_SITE_ID ,BILL_FROM_PARTY_SITE_ID
,SHIP_TO_LOCATION_ID ,SHIP_FROM_LOCATION_ID ,BILL_TO_LOCATION_ID
,SHIP_THIRD_PTY_ACCT_ID ,SHIP_THIRD_PTY_ACCT_SITE_ID ,HISTORICAL_FLAG
,TRX_LINE_CURRENCY_CODE ,TRX_LINE_CURRENCY_CONV_DATE
,TRX_LINE_CURRENCY_CONV_RATE ,TRX_LINE_CURRENCY_CONV_TYPE
,TRX_LINE_MAU ,TRX_LINE_PRECISION ,HISTORICAL_TAX_CODE_ID
,TRX_BUSINESS_CATEGORY ,PRODUCT_CATEGORY ,PRODUCT_FISC_CLASSIFICATION
,LINE_INTENDED_USE ,PRODUCT_TYPE ,USER_DEFINED_FISC_CLASS
,ASSESSABLE_VALUE ,INPUT_TAX_CLASSIFICATION_CODE ,ACCOUNT_CCID
,BILL_THIRD_PTY_ACCT_ID ,BILL_THIRD_PTY_ACCT_SITE_ID ,TRX_LINE_NUMBER
,TRX_LINE_DESCRIPTION ,PRODUCT_DESCRIPTION ,USER_UPD_DET_FACTORS_FLAG
,DEFAULTING_ATTRIBUTE1 ) SELECT :B4 ,:B3 ,:B2
,PRL.REQUISITION_HEADER_ID ,:B1 ,PRL.REQUISITION_LINE_ID ,'INVOICE'
,NVL(PRL.TAX_ATTRIBUTE_UPDATE_CODE,'UPDATE') ,'ITEM'
,NVL(PRL.NEED_BY_DATE, SYSDATE) ,'N' ,NVL(PRL.AMOUNT,
PRL.UNIT_PRICE*PRL.QUANTITY) ,PRL.QUANTITY ,PRL.UNIT_PRICE
,PRL.ITEM_ID ,(SELECT FSP.INVENTORY_ORGANIZATION_ID FROM
FINANCIALS_SYSTEM_PARAMS_ALL FSP WHERE FSP.ORG_ID=PRL.ORG_ID)
,(SELECT MUM.UOM_CODE FROM MTL_UNITS_OF_MEASURE MUM WHERE
MUM.UNIT_OF_MEASURE=PRL.UNIT_MEAS_LOOKUP_CODE) ,MSIB.SEGMENT1
,PRL.DESTINATION_ORGANIZATION_ID ,PV.PARTY_ID ,PRH.ORG_ID
,PV.PARTY_ID ,PVS.PARTY_SITE_ID ,PVS.PARTY_SITE_ID
,PRL.DELIVER_TO_LOCATION_ID ,(SELECT HZPS.LOCATION_ID FROM
HZ_PARTY_SITES HZPS WHERE HZPS.PARTY_SITE_ID = PVS.PARTY_SITE_ID)
,(SELECT LOCATION_ID FROM HR_ALL_ORGANIZATION_UNITS WHERE
ORGANIZATION_ID=PRH.ORG_ID) ,PRL.VENDOR_ID ,PRL.VENDOR_SITE_ID ,NULL
,NVL(PRL.CURRENCY_CODE, :B9 ) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE_DATE,
SYSDATE) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE, :B8 )
,NVL2(PRL.CURRENCY_CODE, PRL.RATE_TYPE, :B7 )
,FC.MINIMUM_ACCOUNTABLE_UNIT ,NVL(FC.PRECISION, 2) ,NULL
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.TRX_BUSINESS_CATEGORY, NULL),
NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_CATEGORY, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_FISC_CLASSIFICATION,
NULL), NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.LINE_INTENDED_USE, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_TYPE, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.USER_DEFINED_FISC_CLASS, NULL),
NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.ASSESSABLE_VALUE, NULL), NULL )
,DECODE(:B6 , 'REQIMPORT', PRL.TAX_NAME,
DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.INPUT_TAX_CLASSIFICATION_CODE,
NULL), NULL ) ) ,NVL((SELECT PRD.CODE_COMBINATION_ID FROM
PO_REQ_DISTRIBUTIONS_ALL PRD WHERE PRD.REQUISITION_LINE_ID =
PRL.REQUISITION_LINE_ID AND ROWNUM = 1), MSIB.EXPENSE_ACCOUNT )
,PV.VENDOR_ID ,PVS.VENDOR_SITE_ID ,PRL.LINE_NUM ,PRL.ITEM_DESCRIPTION
,PRL.ITEM_DESCRIPTION ,(SELECT 'Y' FROM DUAL WHERE :B6 = 'REQIMPORT'
AND PRL.TAX_NAME IS NOT NULL) ,PRL.DESTINATION_ORGANIZATION_ID FROM
PO_REQUISITION_HEADERS_ALL PRH, PO_REQUISITION_LINES_ALL PRL,
ZX_LINES_DET_FACTORS ZXLDET, PO_VENDORS PV, PO_VENDOR_SITES_ALL PVS,
MTL_SYSTEM_ITEMS_B MSIB, FND_CURRENCIES FC WHERE
PRH.REQUISITION_HEADER_ID = :B5 AND PRH.REQUISITION_HEADER_ID =
PRL.REQUISITION_HEADER_ID AND ZXLDET.APPLICATION_ID(+) = :B4 AND
ZXLDET.ENTITY_CODE(+) = :B3 AND ZXLDET.EVENT_CLASS_CODE(+) = :B2 AND
ZXLDET.TRX_LEVEL_TYPE(+) = :B1 AND ZXLDET.TRX_LINE_ID(+) =
PRL.PARENT_REQ_LINE_ID AND PV.VENDOR_ID(+) = PRL.VENDOR_ID AND
PVS.VENDOR_SITE_ID(+) = PRL.VENDOR_SITE_ID AND
MSIB.INVENTORY_ITEM_ID(+) = PRL.ITEM_ID AND MSIB.ORGANIZATION_ID(+) =
PRL.ORG_ID AND FC.CURRENCY_CODE(+) = PRL.CURRENCY_CODE AND
NVL(PRL.MODIFIED_BY_AGENT_FLAG, 'N') = 'N' AND NVL(PRL.CANCEL_FLAG,
'N') = 'N' AND NVL(PRL.CLOSED_CODE, 'OPEN') <> 'FINALLY CLOSED' AND
PRL.LINE_LOCATION_ID IS NULL AND PRL.AT_SOURCING_FLAG IS NULL
Rationale
SQL statement with SQL_ID "b3pnc5yctv2z5" was executed 3 times and had
an average elapsed time of 138 seconds.
Rationale
Average time spent in User I/O wait events per execution was 137
seconds.
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
Regards
AthishFew days are am facing serious of performance problem in our Production instanceFor production issues, please log a SR.
Was this working before? If yes, any changes been done recently?
Do you have the statistics collected up to date?
Please see these docs.
AutoInvoice Performance Issue When Processing Tax [ID 1059275.1]
R12 : System Hangs When Attempting To Save Blanket Release After Applying Patch 11817843 [ID 1333336.1]
Thanks,
Hussein -
Need understanding on the ADDM
Hi,
Db version 11.2.0.3
EBS version 12.1.3
OS : Linux
I have 2 SEV-1 SR's going on with Oracle on which we are working with them. I ran a ADDM from yesterday Morning till today afternoon( Almost 25 Hours).
My understanding :
1. Update query 85ag5gkm9wzmb is taking maximum of time and resources ( One SR is for this - this is Autoinvoice Master Program).
2. SGA and PGA are undersized. Current SGA is 24Gb and PGA is 6Gb. Do I really need to increase SGA and PGA ? My previous has been that on increasing
SGA/PGA to suggested value , it will further prompt for increasing.
3. SYS.DBMS_SPACE.AUTO_SPACE_ADVISOR_JOB_PROC needs some action from my end, should I disable this job , what does it really do ? i am trying to figure that out ,
any help on this will be appreciated.
Please confirm if my understanding is correct and other suggestion/inputs you can provide. Also please suggest how to find if I/O is a bottleneck in the system ? I can see db file sequential read and db file scattered reads in the AWR but they are mostly by the update statement 85ag5gkm9wzmb.
Below is the ADDM for reference.
ADDM Report for Task 'TASK_10569'
Analysis Period
AWR snapshot range from 6708 to 6733.
Time period starts at 19-DEC-13 11.30.37 AM
Time period ends at 20-DEC-13 12.30.43 PM
Analysis Target
Database 'PROD' with DB ID 221722471.
Database version 11.2.0.3.0.
ADDM performed an analysis of instance PROD, numbered 1 and hosted at
hostname.domainname.in.
Activity During the Analysis Period
Total database time was 448593 seconds.
The average number of active sessions was 4.98.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 Top SQL Statements 3.44 | 69.1 6
2 Top Segments by "User I/O" and "Cluster" 2.64 | 53.06 5
3 Undersized SGA .94 | 18.91 1
4 Undersized PGA .28 | 5.66 0
5 PL/SQL Execution .19 | 3.9 5
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
Finding 1: Top SQL Statements
Impact is 3.44 active sessions, 69.1% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
Recommendation 1: SQL Tuning
Estimated benefit is 2.26 active sessions, 45.37% of total activity.
Action
Run SQL Tuning Advisor on the UPDATE statement with SQL_ID
"85ag5gkm9wzmb".
Related Object
SQL statement with SQL_ID 85ag5gkm9wzmb.
UPDATE RA_CUST_TRX_LINE_GL_DIST LGD SET (AMOUNT, ACCTD_AMOUNT) =
(SELECT /*+ index(rec1 RA_CUST_TRX_LINE_GL_DIST_N6) ordered */
NVL(LGD.AMOUNT, 0) - ( SUM(LGD2.AMOUNT) - ( DECODE(LGD.GL_DATE,
REC1.GL_DATE, 1, 0) * CTL.EXTENDED_AMOUNT ) ), NVL(LGD.ACCTD_AMOUNT,
0) - ( SUM(LGD2.ACCTD_AMOUNT) - ( DECODE(LGD.GL_DATE, REC1.GL_DATE,
1, 0) * DECODE(:B2 , NULL, ROUND( CTL.EXTENDED_AMOUNT *
NVL(CT.EXCHANGE_RATE,1), :B3 ), ROUND( ( CTL.EXTENDED_AMOUNT *
NVL(CT.EXCHANGE_RATE,1) ) / :B2 ) * :B2 ) ) ) FROM
RA_CUSTOMER_TRX_LINES CTL, RA_CUSTOMER_TRX CT,
RA_CUST_TRX_LINE_GL_DIST LGD2, RA_CUST_TRX_LINE_GL_DIST REC1 WHERE
CTL.CUSTOMER_TRX_LINE_ID = LGD2.CUSTOMER_TRX_LINE_ID AND
CTL.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID AND LGD.CUSTOMER_TRX_LINE_ID
= CTL.CUSTOMER_TRX_LINE_ID AND LGD2.ACCOUNT_SET_FLAG = 'N' AND
REC1.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID AND REC1.ACCOUNT_CLASS =
'REC' AND REC1.LATEST_REC_FLAG = 'Y' AND NVL(LGD.GL_DATE, TO_DATE(
2415021, 'J') ) = NVL(LGD2.GL_DATE, TO_DATE( 2415021, 'J') ) GROUP BY
CTL.CUSTOMER_TRX_LINE_ID, REC1.GL_DATE, CTL.EXTENDED_AMOUNT,
CTL.REVENUE_AMOUNT, CT.EXCHANGE_RATE ), PERCENT = (SELECT /*+
index(rec2 RA_CUST_TRX_LINE_GL_DIST_N6) */ DECODE(LGD.ACCOUNT_CLASS
|| LGD.ACCOUNT_SET_FLAG, 'SUSPENSEN', LGD.PERCENT, 'UNBILLN',
LGD.PERCENT, 'UNEARNN', LGD.PERCENT, NVL(LGD.PERCENT, 0) - (
SUM(NVL(LGD4.PERCENT, 0)) - DECODE(REC2.GL_DATE, NVL(LGD.GL_DATE,
REC2.GL_DATE), 100, 0) ) ) FROM RA_CUST_TRX_LINE_GL_DIST LGD4,
RA_CUST_TRX_LINE_GL_DIST REC2 WHERE LGD.CUSTOMER_TRX_LINE_ID =
LGD4.CUSTOMER_TRX_LINE_ID AND REC2.CUSTOMER_TRX_ID =
LGD.CUSTOMER_TRX_ID AND REC2.CUSTOMER_TRX_ID = LGD4.CUSTOMER_TRX_ID
AND REC2.ACCOUNT_CLASS = 'REC' AND REC2.LATEST_REC_FLAG = 'Y' AND
LGD4.ACCOUNT_SET_FLAG = LGD.ACCOUNT_SET_FLAG AND
DECODE(LGD4.ACCOUNT_SET_FLAG, 'Y', LGD4.ACCOUNT_CLASS,
LGD.ACCOUNT_CLASS) = LGD.ACCOUNT_CLASS AND NVL(LGD.GL_DATE, TO_DATE(
2415021, 'J') ) = NVL(LGD4.GL_DATE, TO_DATE( 2415021, 'J') ) GROUP BY
REC2.GL_DATE, LGD.GL_DATE ), LAST_UPDATED_BY = :B1 , LAST_UPDATE_DATE
= SYSDATE WHERE CUST_TRX_LINE_GL_DIST_ID IN (SELECT /*+ index(rec3
RA_CUST_TRX_LINE_GL_DIST_N6) */ MIN(DECODE(LGD3.GL_POSTED_DATE, NULL,
LGD3.CUST_TRX_LINE_GL_DIST_ID, NULL) ) FROM RA_CUSTOMER_TRX_LINES
CTL, RA_CUSTOMER_TRX T, RA_CUST_TRX_LINE_GL_DIST LGD3,
RA_CUST_TRX_LINE_GL_DIST REC3 WHERE T.REQUEST_ID = :B5 AND
T.CUSTOMER_TRX_ID = CTL.CUSTOMER_TRX_ID AND (CTL.LINE_TYPE IN (
'TAX','FREIGHT','CHARGES','SUSPENSE' ) OR (CTL.LINE_TYPE = 'LINE' AND
CTL.ACCOUNTING_RULE_ID IS NULL )) AND LGD3.CUSTOMER_TRX_LINE_ID =
CTL.CUSTOMER_TRX_LINE_ID AND LGD3.ACCOUNT_SET_FLAG = 'N' AND
REC3.CUSTOMER_TRX_ID = T.CUSTOMER_TRX_ID AND REC3.ACCOUNT_CLASS =
'REC' AND REC3.LATEST_REC_FLAG = 'Y' AND
NVL(T.PREVIOUS_CUSTOMER_TRX_ID, -1) = DECODE(:B4 , 'INV', -1,
'REGULAR_CM', T.PREVIOUS_CUSTOMER_TRX_ID,
NVL(T.PREVIOUS_CUSTOMER_TRX_ID, -1) ) GROUP BY
CTL.CUSTOMER_TRX_LINE_ID, LGD3.GL_DATE, REC3.GL_DATE,
CTL.EXTENDED_AMOUNT, CTL.REVENUE_AMOUNT, T.EXCHANGE_RATE HAVING (
SUM(NVL(LGD3.AMOUNT, 0)) <> CTL.EXTENDED_AMOUNT *
DECODE(LGD3.GL_DATE, REC3.GL_DATE, 1, 0) OR
SUM(NVL(LGD3.ACCTD_AMOUNT, 0)) <> DECODE(LGD3.GL_DATE, REC3.GL_DATE,
1, 0) * DECODE(:B2 , NULL, ROUND( CTL.EXTENDED_AMOUNT *
NVL(T.EXCHANGE_RATE,1), :B3 ), ROUND( ( CTL.EXTENDED_AMOUNT *
NVL(T.EXCHANGE_RATE,1) ) / :B2 ) * :B2 ) ) UNION SELECT /*+
index(rec5 RA_CUST_TRX_LINE_GL_DIST_N6) INDEX (lgd5
ra_cust_trx_line_gl_dist_n6) index(ctl2 ra_customer_trx_lines_u1) */
TO_NUMBER( MIN(DECODE(LGD5.GL_POSTED_DATE||LGD5.ACCOUNT_CLASS||
LGD5.ACCOUNT_SET_FLAG, 'REVN', LGD5.CUST_TRX_LINE_GL_DIST_ID, 'REVY',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'TAXN', LGD5.CUST_TRX_LINE_GL_DIST_ID,
'TAXY', LGD5.CUST_TRX_LINE_GL_DIST_ID, 'FREIGHTN',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'FREIGHTY',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'CHARGESN',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'CHARGESY',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'UNEARNY',
LGD5.CUST_TRX_LINE_GL_DIST_ID, 'UNBILLY',
LGD5.CUST_TRX_LINE_GL_DIST_ID, NULL ) ) ) FROM
RA_CUST_TRX_LINE_GL_DIST LGD5, RA_CUST_TRX_LINE_GL_DIST REC5,
RA_CUSTOMER_TRX_LINES CTL2, RA_CUSTOMER_TRX T WHERE T.REQUEST_ID =
:B5 AND T.CUSTOMER_TRX_ID = REC5.CUSTOMER_TRX_ID AND
CTL2.CUSTOMER_TRX_LINE_ID = LGD5.CUSTOMER_TRX_LINE_ID AND
REC5.CUSTOMER_TRX_ID = LGD5.CUSTOMER_TRX_ID AND REC5.ACCOUNT_CLASS =
'REC' AND REC5.LATEST_REC_FLAG = 'Y' AND (CTL2.LINE_TYPE IN (
'TAX','FREIGHT','CHARGES','SUSPENSE') OR (CTL2.LINE_TYPE = 'LINE' AND
(CTL2.ACCOUNTING_RULE_ID IS NULL OR LGD5.ACCOUNT_SET_FLAG = 'Y' )))
GROUP BY LGD5.CUSTOMER_TRX_LINE_ID, LGD5.GL_DATE, REC5.GL_DATE,
LGD5.ACCOUNT_SET_FLAG, DECODE(LGD5.ACCOUNT_SET_FLAG, 'N', NULL,
LGD5.ACCOUNT_CLASS) HAVING SUM(NVL(LGD5.PERCENT, 0)) <> DECODE(
NVL(LGD5.GL_DATE, REC5.GL_DATE), REC5.GL_DATE, 100, 0) )
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "85ag5gkm9wzmb" was executed 20 times and had
an average elapsed time of 9763 seconds.
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"gccbpwamzp78q" are responsible for 100% of the database time spent on
the UPDATE statement with SQL_ID "85ag5gkm9wzmb".
Related Object
SQL statement with SQL_ID gccbpwamzp78q.
declare l_header_rounding_flag VARCHAR2 ( 1 ) ; BEGIN select
trx_header_level_rounding into l_header_rounding_flag from
ar_system_parameters ; :return_value:i_return_value := arp_rounding .
correct_dist_rounding_errors ( :request_id , NULL , NULL ,
:rows_processed:i_rows_processed , :error_msg:i_error_msg , NULL ,
NULL , :trx_class , 'N' , :debug_mode , l_header_rounding_flag , 'N'
) ; END ;
Recommendation 2: SQL Tuning
Estimated benefit is .42 active sessions, 8.39% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"d9xccqfmfjvns".
Related Object
SQL statement with SQL_ID d9xccqfmfjvns.
SELECT RCT.CUSTOMER_TRX_ID K_TRX_ID, RCT.TRX_NUMBER, SUM
(APS.AMOUNT_DUE_REMAINING) CM_AMOUNT_APPLIED,RCT.TRX_DATE FROM
APPS.RA_CUSTOMER_TRX_ALL RCT, APPS.AR_PAYMENT_SCHEDULES_ALL APS,
APPS.RA_CUST_TRX_TYPES_ALL TCTTA, APPS.AR_CUSTOMERS AC,
APPS.HZ_CUSTOMER_PROFILES HCP, APPS.RA_TERMS RT WHERE
RCT.CUST_TRX_TYPE_ID = TCTTA.CUST_TRX_TYPE_ID AND AC.CUSTOMER_ID =
RCT.BILL_TO_CUSTOMER_ID AND RCT.CUSTOMER_TRX_ID=APS.CUSTOMER_TRX_ID
AND AC.CUSTOMER_ID = HCP.CUST_ACCOUNT_ID AND RCT.BILL_TO_SITE_USE_ID
= HCP.SITE_USE_ID AND RT.TERM_ID = HCP.STANDARD_TERMS AND TCTTA.TYPE
IN ('INV') AND UPPER(TCTTA.NAME) IN ( SELECT UPPER(MEANING) FROM
FND_LOOKUP_VALUES WHERE LOOKUP_TYPE = :B3 ) AND RCT.TRX_DATE <= NVL
(TO_DATE(:B2 , 'RRRR/MM/DD HH24:MI:SS'), RCT.TRX_DATE) AND
AC.CUSTOMER_ID = :B1 GROUP BY RCT.CUSTOMER_TRX_ID,
RCT.TRX_NUMBER,RCT.TRX_DATE HAVING SUM (APS.AMOUNT_DUE_REMAINING) > 0
ORDER BY RCT.TRX_DATE
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "d9xccqfmfjvns" was executed 123412 times and
had an average elapsed time of 0.29 seconds.
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"bcxz2s8wj5spc" are responsible for 100% of the database time spent on
the SELECT statement with SQL_ID "d9xccqfmfjvns".
Related Object
SQL statement with SQL_ID bcxz2s8wj5spc.
BEGIN XXSD_APPLY_CM_APPLY_TO_INV(:errbuf,:rc,:A0,:A1,:A2,:A3); END;
Recommendation 3: SQL Tuning
Estimated benefit is .3 active sessions, 6.04% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"2ujt2fg615ymk".
Related Object
SQL statement with SQL_ID 2ujt2fg615ymk.
SELECT HP.PARTY_NAME PARTY_NAME, RCT.TRX_NUMBER TRX_NUMBER,
RCT.TRX_DATE TRX_DATE, APS.AMOUNT_DUE_ORIGINAL AMOUNT_DUE_ORIGINAL,
APS.AMOUNT_DUE_REMAINING OUTSTANDING_AMOUNT, RCTT.NAME
TRANSACTION_TYPE FROM RA_CUSTOMER_TRX_ALL RCT,
AR_PAYMENT_SCHEDULES_ALL APS, RA_CUST_TRX_TYPES_ALL RCTT,
HZ_CUST_ACCOUNTS HCA, HZ_PARTIES HP, APPS.AR_CUSTOMERS AC,
APPS.HZ_CUSTOMER_PROFILES HCP, APPS.RA_TERMS RT, HZ_PARTY_SITES HPS,
HZ_CUST_ACCT_SITES_ALL HCASA, HZ_CUST_SITE_USES_ALL HCSUA WHERE 1 = 1
AND RCT.BILL_TO_CUSTOMER_ID = HCA.CUST_ACCOUNT_ID AND HCA.PARTY_ID =
HP.PARTY_ID AND APS.CUSTOMER_TRX_ID = RCT.CUSTOMER_TRX_ID AND
APS.ORG_ID = RCT.ORG_ID AND RCTT.CUST_TRX_TYPE_ID =
RCT.CUST_TRX_TYPE_ID AND RCTT.ORG_ID = RCT.ORG_ID AND AC.CUSTOMER_ID
= HCA.CUST_ACCOUNT_ID AND AC.CUSTOMER_ID = RCT.BILL_TO_CUSTOMER_ID
AND AC.CUSTOMER_ID = HCP.CUST_ACCOUNT_ID AND RCT.BILL_TO_SITE_USE_ID
= HCP.SITE_USE_ID AND RT.TERM_ID = HCP.STANDARD_TERMS AND
HPS.PARTY_SITE_ID = HCASA.PARTY_SITE_ID AND HCASA.CUST_ACCOUNT_ID =
AC.CUSTOMER_ID AND HCASA.CUST_ACCT_SITE_ID = HCSUA.CUST_ACCT_SITE_ID
AND HCSUA.SITE_USE_ID = RCT.BILL_TO_SITE_USE_ID AND RCT.TRX_DATE
BETWEEN NVL (TO_DATE (:B6 , 'RRRR/MM/DD HH24:MI:SS' ), '1-JAN-1900' )
AND NVL (TO_DATE (:B5 , 'RRRR/MM/DD HH24:MI:SS' ), '31-DEC-2100' )
AND RCTT.NAME = NVL (:B4 , RCTT.NAME) AND RT.TERM_ID = NVL (:B3 ,
RT.TERM_ID) AND HP.PARTY_NAME = NVL (:B2 , HP.PARTY_NAME) AND ( (CASE
WHEN :B1 = 'Open' THEN APS.AMOUNT_DUE_REMAINING END != 0 ) OR ((CASE
WHEN :B1 = 'Closed' THEN APS.AMOUNT_DUE_REMAINING END = 0 ) ) OR CASE
WHEN :B1 IS NULL THEN 1 END = 1 )
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "2ujt2fg615ymk" was executed 19 times and had
an average elapsed time of 1368 seconds.
Rationale
At least 2 distinct execution plans were utilized for this SQL statement
during the analysis period.
Rationale
Top level calls to execute the PL/SQL statement with SQL_ID
"g969dx1d0uucf" are responsible for 100% of the database time spent on
the SELECT statement with SQL_ID "2ujt2fg615ymk".
Related Object
SQL statement with SQL_ID g969dx1d0uucf.
BEGIN XXSD_TRX_DETAIL_REPORT(:errbuf,:rc,:A0,:A1,:A2,:A3,:A4,:A5);
END;
Recommendation 4: SQL Tuning
Estimated benefit is .2 active sessions, 4.04% of total activity.
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"gy02p15c6bf0w".
Related Object
SQL statement with SQL_ID gy02p15c6bf0w.
SELECT SUM (RECEIPTS) - SUM (PAYMENTS) FROM (SELECT
AIP.ACCOUNTING_DATE GL_DATE , DECODE(NVL(APC.VENDOR_NAME ,
APC.REMIT_TO_SUPPLIER_NAME ) , 'FD Investment' , 'FD' , 'Payment' )
TYPE , APC.DOC_SEQUENCE_VALUE VOUCHER_NO , APC.CREATION_DATE
VOUCHER_DATE , TO_CHAR (APC.CHECK_NUMBER ) CHECK_NUMBER , TO_CHAR
(NVL(APC.FUTURE_PAY_DUE_DATE , APC.CHECK_DATE ) , 'DD-MON-YYYY' )
CHECK_DATE , NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME )
VENDOR_NAME , API.ACCTS_PAY_CODE_COMBINATION_ID ACCOUNT_CODE ,
'Supplier Payment' DESCRIPTION , TO_CHAR (DECODE(SIGN(SUM
(AIP.AMOUNT) ) , -1 , SUM (AIP.AMOUNT * NVL(AIP.EXCHANGE_RATE , 1 )
) * -1 , SUM (0) ) ) RECEIPTS , TO_CHAR (DECODE(SIGN(SUM
(AIP.AMOUNT) ) , 1 , SUM (AIP.AMOUNT * NVL(AIP.EXCHANGE_RATE , 1 )
) , SUM (0) ) ) PAYMENTS , TO_NUMBER (SUM (AIP.AMOUNT *
NVL(AIP.EXCHANGE_RATE , 1 ) ) ) PAYMENTS1 , CBA.BANK_ACCOUNT_NAME
BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM BANK_ACCOUNT_NUM ,
BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME BRANCH_NAME FROM
APPS.AP_INVOICE_PAYMENTS_ALL AIP , APPS.AP_INVOICES_ALL API ,
APPS.AP_CHECKS_ALL APC , APPS.CE_BANK_ACCOUNTS CBA ,
APPS.CE_BANK_ACCT_USES_ALL CBU , HZ_PARTIES BANK , HZ_PARTIES BRANCH
WHERE API.INVOICE_ID = AIP.INVOICE_ID AND AIP.CHECK_ID =
APC.CHECK_ID AND APC.CE_BANK_ACCT_USE_ID = CBU.BANK_ACCT_USE_ID
AND CBA.BANK_ACCOUNT_ID = CBU.BANK_ACCOUNT_ID AND CBA.BANK_ID =
BANK.PARTY_ID AND CBA.BANK_BRANCH_ID = BRANCH.PARTY_ID AND ( (
APC.STATUS_LOOKUP_CODE IN ( 'NEGOTIABLE' , 'CLEARED' , 'VOIDED' ,
'RECONCILED UNACCOUNTED' , 'RECONCILED' , 'CLEARED BUT UNACCOUNTED' )
AND AIP.ACCOUNTING_DATE < :b1 AND APC.FUTURE_PAY_DUE_DATE IS NULL
) OR ( APC.STATUS_LOOKUP_CODE IN ( 'NEGOTIABLE' ) AND
APC.FUTURE_PAY_DUE_DATE < :b1 ) ) AND CBA.BANK_ACCOUNT_ID = :b2
AND AIP.INVOICE_PAYMENT_TYPE IS NULL AND ( API.ORG_ID IS NULL OR
API.ORG_ID = :b3 ) GROUP BY AIP.ACCOUNTING_DATE ,
DECODE(NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME ) , 'FD
Investment' , 'FD' , 'Payment' ) , APC.DOC_SEQUENCE_VALUE ,
APC.CREATION_DATE , TO_CHAR (APC.CHECK_NUMBER ) , TO_CHAR
(NVL(APC.FUTURE_PAY_DUE_DATE , APC.CHECK_DATE ) , 'DD-MON-YYYY' ) ,
NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME ) ,
API.ACCTS_PAY_CODE_COMBINATION_ID , 'Supplier Payment' ,
CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM , BANK.PARTY_NAME ,
BRANCH.PARTY_NAME UNION ALL SELECT APID.ACCOUNTING_DATE GL_DATE ,
DECODE(POV.VENDOR_NAME , 'FD Investment' , 'FD' , 'I' ) TYPE ,
API.DOC_SEQUENCE_VALUE VOUCHER_NO , API.CREATION_DATE VOUCHER_DATE ,
API.INVOICE_NUM CHECK_NUMBER , TO_CHAR (API.INVOICE_DATE ,
'DD-MON-YYYY' ) CHECK_DATE , POV.VENDOR_NAME VENDOR_NAME ,
API.ACCTS_PAY_CODE_COMBINATION_ID ACCOUNT_CODE , NVL(API.DESCRIPTION
, API.INVOICE_NUM ) DESCRIPTION , TO_CHAR (SUM (API.INVOICE_AMOUNT *
NVL(API.EXCHANGE_RATE , 1 ) ) ) RECEIPTS , TO_CHAR (SUM (0) ,
'fm999999999990.00' ) PAYMENTS , TO_NUMBER (SUM (0) ) PAYMENTS1 ,
CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM
BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
BRANCH_NAME FROM APPS.AP_INVOICE_DISTRIBUTIONS_ALL APID ,
APPS.AP_INVOICE_LINES_ALL APLA , APPS.AP_INVOICES_ALL API ,
APPS.PO_VENDORS POV , APPS.CE_BANK_ACCOUNTS CBA , HZ_PARTIES BANK ,
HZ_PARTIES BRANCH WHERE API.INVOICE_ID = APID.INVOICE_ID AND
APLA.INVOICE_ID = APID.INVOICE_ID AND APLA.LINE_NUMBER =
APID.INVOICE_LINE_NUMBER AND API.VENDOR_ID = POV.VENDOR_ID AND
CBA.BANK_ACCOUNT_ID = :b2 AND CBA.ASSET_CODE_COMBINATION_ID =
APID.DIST_CODE_COMBINATION_ID AND CBA.BANK_ID = BANK.PARTY_ID AND
CBA.BANK_BRANCH_ID = BRANCH.PARTY_ID AND APID.MATCH_STATUS_FLAG =
'A' AND NVL(API.PAYMENT_STATUS_FLAG , 'N' ) != 'N' AND
APID.ACCOUNTING_DATE < :b1 AND ( API.ORG_ID IS NULL OR API.ORG_ID
= :b3 ) GROUP BY APID.ACCOUNTING_DATE , DECODE(POV.VENDOR_NAME ,
'FD Investment' , 'FD' , 'I' ) , API.DOC_SEQUENCE_VALUE ,
API.CREATION_DATE , API.INVOICE_NUM , TO_CHAR (API.INVOICE_DATE ,
'DD-MON-YYYY' ) , POV.VENDOR_NAME ,
API.ACCTS_PAY_CODE_COMBINATION_ID , NVL(API.DESCRIPTION ,
API.INVOICE_NUM ) , CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM ,
BANK.PARTY_NAME , BRANCH.PARTY_NAME UNION ALL SELECT ACRH.GL_DATE
GL_DATE , DECODE(ACRH.STATUS , 'REVERSED' , 'REV' ,
DECODE(ACRH.CREATED_FROM , 'RATE ADJUSTMENT TRIGGER' , 'ERF' ,
'Receipt' ) ) TYPE , ACR.DOC_SEQUENCE_VALUE VOUCHER_NO ,
ACR.CREATION_DATE VOUCHER_DATE , ACR.RECEIPT_NUMBER CHECK_NUMBER ,
TO_CHAR (ACR.RECEIPT_DATE , 'DD-MON-YYYY' ) CHECK_DATE ,
NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 ) , 'Miscellaneous Activity' )
VENDOR_NAME , ACRH.ACCOUNT_CODE_COMBINATION_ID ACCOUNT_CODE ,
'Customer Receipt' DESCRIPTION , TO_CHAR (SUM (DECODE(ACRH.STATUS ,
'REVERSED' , NVL(ADA.ACCTD_AMOUNT_DR , 0 ) , 'CLEARED' ,
NVL(ADA.ACCTD_AMOUNT_DR , 0 ) , 'REMITTED' , NVL(ADA.ACCTD_AMOUNT_DR
, 0 ) , 'CONFIRMED' , NVL(ADA.ACCTD_AMOUNT_DR , 0 ) ) ) ,
'fm999999999990.00' ) RECEIPTS , TO_CHAR (SUM (DECODE(ACRH.STATUS ,
'REVERSED' , NVL(ADA.ACCTD_AMOUNT_CR , 0 ) , 'CLEARED' ,
NVL(ADA.ACCTD_AMOUNT_CR , 0 ) , 'REMITTED' , NVL(ADA.ACCTD_AMOUNT_CR
, 0 ) , 'CONFIRMED' , NVL(ADA.ACCTD_AMOUNT_CR , 0 ) ) ) ,
'fm999999999990.00' ) PAYMENTS , TO_NUMBER (TO_CHAR (SUM (0) ) )
PAYMENTS1 , CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME ,
CBA.BANK_ACCOUNT_NUM BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME ,
BRANCH.PARTY_NAME BRANCH_NAME FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL
ACRH , APPS.AR_CASH_RECEIPTS_ALL ACR , APPS.HZ_PARTIES HP ,
APPS.HZ_CUST_ACCOUNTS HCA , APPS.CE_BANK_ACCOUNTS CBA ,
APPS.CE_BANK_ACCT_USES_ALL CBAU , APPS.AR_DISTRIBUTIONS_ALL ADA ,
HZ_PARTIES BANK , HZ_PARTIES BRANCH WHERE ACRH.CASH_RECEIPT_ID =
ACR.CASH_RECEIPT_ID AND CBAU.BANK_ACCT_USE_ID =
ACR.REMIT_BANK_ACCT_USE_ID AND CBAU.BANK_ACCOUNT_ID =
CBA.BANK_ACCOUNT_ID AND HCA.PARTY_ID = HP.PARTY_ID AND
ACR.PAY_FROM_CUSTOMER = HCA.CUST_ACCOUNT_ID AND CBA.BANK_ID =
BANK.PARTY_ID AND CBA.BANK_BRANCH_ID = BRANCH.PARTY_ID AND
ACRH.STATUS IN ( 'CLEARED' , 'REMITTED' , 'CONFIRMED' , 'REVERSED' )
AND ACRH.CASH_RECEIPT_HISTORY_ID = ADA.SOURCE_ID AND
ADA.SOURCE_TABLE = 'CRH' AND ADA.SOURCE_TYPE != 'BANK_CHARGES'
AND CBA.BANK_ACCOUNT_ID = :b2 AND ACRH.GL_DATE < :b1 AND (
ACR.ORG_ID IS NULL OR ACR.ORG_ID = :b3 ) AND ( (
ACR.REVERSAL_DATE IS NOT NULL AND ACRH.STATUS = 'REVERSED' ) OR (
ACRH.CASH_RECEIPT_HISTORY_ID IN (SELECT INCRH.CASH_RECEIPT_HISTORY_ID
FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL INCRH WHERE
INCRH.CASH_RECEIPT_ID = ACR.CASH_RECEIPT_ID AND INCRH.STATUS !=
'REVERSED' )) ) GROUP BY ACRH.GL_DATE , DECODE(ACRH.STATUS ,
'REVERSED' , 'REV' , DECODE(ACRH.CREATED_FROM , 'RATE ADJUSTMENT
TRIGGER' , 'ERF' , 'Receipt' ) ) , ACR.DOC_SEQUENCE_VALUE ,
ACR.CREATION_DATE , ACR.RECEIPT_NUMBER , TO_CHAR (ACR.RECEIPT_DATE ,
'DD-MON-YYYY' ) , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 ) ,
'Miscellaneous Activity' ) , ACRH.ACCOUNT_CODE_COMBINATION_ID ,
'Customer Receipt' , CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM ,
BANK.PARTY_NAME , BRANCH.PARTY_NAME UNION ALL SELECT ACRH.GL_DATE
GL_DATE , DECODE(ADJ.REASON_CODE , NULL , 'ADJ' , ADJ.REASON_CODE
|| ' - ADJ' ) TYPE , ACR.DOC_SEQUENCE_VALUE VOUCHER_NO ,
ACR.CREATION_DATE VOUCHER_DATE , NULL CHECK_NUMBER , NULL
CHECK_DATE , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 ) , 'Miscellaneous
Activity' ) VENDOR_NAME , ACRH.ACCOUNT_CODE_COMBINATION_ID
ACCOUNT_CODE , NVL(ACR.COMMENTS , ACR.RECEIPT_NUMBER ) DESCRIPTION ,
TO_CHAR (SUM (-1 * ADJ.AMOUNT ) , 'fm999999999990.00' ) RECEIPTS ,
NULL PAYMENTS , TO_NUMBER (TO_CHAR (SUM (0) ) ) PAYMENTS1 ,
CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM
BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
BRANCH_NAME FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL ACRH ,
APPS.AR_CASH_RECEIPTS_ALL ACR , APPS.HZ_PARTIES HP ,
APPS.HZ_CUST_ACCOUNTS HCA , APPS.CE_BANK_ACCOUNTS CBA ,
APPS.CE_BANK_ACCT_USES_ALL CBAU , APPS.AR_RECEIVABLE_APPLICATIONS_ALL
APP , APPS.AR_ADJUSTMENTS_ALL ADJ , HZ_PARTIES BANK , HZ_PARTIES
BRANCH WHERE ACRH.CASH_RECEIPT_ID = ACR.CASH_RECEIPT_ID AND
APP.CASH_RECEIPT_ID = ACRH.CASH_RECEIPT_ID AND APP.DISPLAY = 'Y'
AND APP.STATUS = 'APP' AND APP.APPLICATION_TYPE = 'CASH' AND
ADJ.CUSTOMER_TRX_ID = APP.APPLIED_CUSTOMER_TRX_ID AND
ADJ.CHARGEBACK_CUSTOMER_TRX_ID IS NULL AND ADJ.TYPE = 'CHARGES'
AND CBAU.BANK_ACCT_USE_ID = ACR.REMIT_BANK_ACCT_USE_ID AND
CBAU.BANK_ACCOUNT_ID = CBA.BANK_ACCOUNT_ID AND ACRH.CASH_RECEIPT_ID
= ACR.CASH_RECEIPT_ID AND HCA.PARTY_ID = HP.PARTY_ID AND
ACR.PAY_FROM_CUSTOMER = HCA.CUST_ACCOUNT_ID AND CBA.BANK_ID =
BANK.PARTY_ID AND CBA.BANK_BRANCH_ID = BRANCH.PARTY_ID AND
ACRH.STATUS IN ( 'CLEARED' , 'REMITTED' , 'CONFIRMED' , 'REVERSED' )
AND CBA.BANK_ACCOUNT_ID = :b2 AND ACRH.GL_DATE < :b1 AND (
ACR.ORG_ID IS NULL OR ACR.ORG_ID = :b3 ) AND ( (
ACR.REVERSAL_DATE IS NOT NULL AND ACRH.STATUS = 'REVERSED' ) OR (
ACRH.CASH_RECEIPT_HISTORY_ID IN (SELECT MIN
(INCRH.CASH_RECEIPT_HISTORY_ID) FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL
INCRH WHERE INCRH.CASH_RECEIPT_ID = ACR.CASH_RECEIPT_ID AND
INCRH.STATUS != 'REVERSED' )) ) GROUP BY ACRH.GL_DATE ,
DECODE(ADJ.REASON_CODE , NULL , 'ADJ' , ADJ.REASON_CODE || ' -
ADJ' ) , ACR.DOC_SEQUENCE_VALUE , ACR.CREATION_DATE , NULL ,
NULL , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 ) , 'Miscellaneous
Activity' ) , ACRH.ACCOUNT_CODE_COMBINATION_ID , NVL(ACR.COMMENTS ,
ACR.RECEIPT_NUMBER ) , NULL , CBA.BANK_ACCOUNT_NAME ,
CBA.BANK_ACCOUNT_NUM , BANK.PARTY_NAME , BRANCH.PARTY_NAME UNION ALL
SELECT PT.TRANSACTION_DATE GL_DATE , DECODE(PT.CREATED_FROM_DIR ,
'PAYMENT' , 'Payment' ) TYPE , PT.TRXN_REFERENCE_NUMBER VOUCHER_NO ,
TRUNC (PT.CREATION_DATE ) VOUCHER_DATE , PT.BANK_TRXN_NUMBER
CHECK_NUMBER , TO_CHAR (PT.TRANSACTION_DATE , 'DD-MON-YYYY' )
CHECK_DATE , DESTBA.BANK_ACCOUNT_NAME VENDOR_NAME ,
GCC.CODE_COMBINATION_ID ACCOUNT_CODE , 'Inter Bank Transfer' ACC_DESC
, '0' RECEIPTS , TO_CHAR (SUM (PT.PAYMENT_AMOUNT) ) PAYMENTS ,
TO_NUMBER (SUM (PT.PAYMENT_AMOUNT) ) PAYMENTS1 ,
SRCBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , SRCBA.BANK_ACCOUNT_NUM
BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
BRANCH_NAME FROM APPS.HZ_ORGANIZATION_PROFILES SBANKORGPROFILE ,
APPS.HZ_CODE_ASSIGNMENTS SBANKCA , APPS.HZ_PARTIES SBRANCHPARTY ,
APPS.HZ_ORGANIZATION_PROFILES SBRANCHORGPROFILE ,
APPS.HZ_CODE_ASSIGNMENTS SBRANCHCA , APPS.HZ_RELATIONSHIPS SBRREL ,
APPS.HZ_CODE_ASSIGNMENTS SBRANCHTYPECA , APPS.HZ_CONTACT_POINTS
SBRANCHCP , APPS.HZ_CONTACT_POINTS SEDICP ,
APPS.HZ_ORGANIZATION_PROFILES DBANKORGPROFILE ,
APPS.HZ_CODE_ASSIGNMENTS DBANKCA , APPS.HZ_PARTIES DBRANCHPARTY ,
APPS.HZ_ORGANIZATION_PROFILES DBRANCHORGPROFILE ,
APPS.HZ_CODE_ASSIGNMENTS DBRANCHCA , APPS.HZ_RELATIONSHIPS DBRREL ,
APPS.HZ_CODE_ASSIGNMENTS DBRANCHTYPECA , APPS.HZ_CONTACT_POINTS
DBRANCHCP , APPS.HZ_CONTACT_POINTS DEDICP ,
APPS.CE_PAYMENT_TRANSACTIONS PT , APPS.CE_BANK_ACCOUNTS SRCBA ,
APPS.CE_BANK_ACCOUNTS DESTBA , APPS.XLE_ENTITY_PROFILES SRCLE ,
APPS.XLE_ENTITY_PROFILES DESTLE , APPS.GL_CODE_COMBINATIONS GCC ,
APPS.HZ_PARTIES HZP , HZ_PARTIES BANK , HZ_PARTIES BRANCH WHERE
SYSDATE BETWEEN TRUNC (SBANKORGPROFILE.EFFECTIVE_START_DATE ) AND
NVL(TRUNC (SBANKORGPROFILE.EFFECTIVE_END_DATE ) , SYSDATE + 1 )
AND SBANKCA.CLASS_CATEGORY = 'BANK_INSTITUTION_TYPE' AND
SBANKCA.CLASS_CODE IN ( 'BANK' , 'CLEARINGHOUSE' ) AND
SBANKCA.OWNER_TABLE_NAME = 'HZ_PARTIES' AND ( SBANKCA.STATUS = 'A'
OR SBANKCA.STATUS IS NULL ) AND SBANKCA.OWNER_TABLE_ID =
SBANKORGPROFILE.PARTY_ID AND SBRANCHPARTY.PARTY_TYPE =
'ORGANIZATION' AND SBRANCHPARTY.STATUS = 'A' AND
SBRANCHORGPROFILE.PARTY_ID = SBRANCHPARTY.PARTY_ID AND SYSDATE
BETWEEN TRUNC (SBRANCHORGPROFILE.EFFECTIVE_START_DATE ) AND
NVL(TRUNC (SBRANCHORGPROFILE.EFFECTIVE_END_DATE ) , SYSDATE + 1 )
AND SBRANCHCA.CLASS_CATEGORY = 'BANK_INSTITUTION_TYPE' AND
SBRANCHCA.CLASS_CODE IN ( 'BANK_BRANCH' , 'CLEARINGHOUSE_BRANCH' )
AND SBRANCHCA.OWNER_TABLE_NAME = 'HZ_PARTIES' AND (
SBRANCHCA.STATUS = 'A' OR SBRANCHCA.STATUS IS NULL ) AND
SBRANCHCA.OWNER_TABLE_ID = SBRANCHPARTY.PARTY_ID AND
SBANKORGPROFILE.PARTY_ID = SBRREL.OBJECT_ID AND
SBRREL.RELATIONSHIP_TYPE = 'BANK_AND_BRANCH' AND
SBRREL.RELATIONSHIP_CODE = 'BRANCH_OF' AND SBRREL.STATUS = 'A'
AND SBRREL.SUBJECT_TABLE_NAME = 'HZ_PARTIES' AND
SBRREL.SUBJECT_TYPE = 'ORGANIZATION' AND SBRREL.OBJECT_TABLE_NAME =
'HZ_PARTIES' AND SBRREL.OBJECT_TYPE = 'ORGANIZATION' AND
SBRREL.SUBJECT_ID = SBRANCHPARTY.PARTY_ID AND
SBRANCHTYPECA.CLASS_CATEGORY = 'BANK_BRANCH_TYPE' AND
SBRANCHTYPECA.PRIMARY_FLAG = 'Y' AND
SBRANCHTYPECA.OWNER_TABLE_NAME = 'HZ_PARTIES' AND
SBRANCHTYPECA.OWNER_TABLE_ID = SBRANCHPARTY.PARTY_ID ANDHi Karan,
If your DB node has 48 GB and there are no other applications/program running on the server than I believe you still have for room for SGA/PGA resize.
GSS was scheduled to run at 20% till last week ( runs every week) while i just made it to run for auto_sample_size by giving the percent as 0. I have checked and found that most of the tables had good stats , though one of the programs has started to take too much time after that. So for now i have reverted it back to 20%.
10% - 20% is the percentage which I usually go with and this works well for me. Anyways that being said 10% default would do the trick in most cases.
The update statement which is causing the trouble is a seeded oracle program so we have checking that with oracle. ( Auto_invoice_master).
Yes as recommended, Please get confirmation from SR as well.
Please also see note:
How To Setup AutoInvoice For Optimal Performance (Doc ID 1083467.1)
Troubleshooting AutoInvoice Performance Issues (Doc ID 1089196.1)
Thanks &
Best Regards -
Hi,
I have a small 'orcl' database on my local machine, and I did not perform heavy activity on it. Today and yesterday I performed just some simple queries, like:
SELECT COUNT(*)
FROM products p, (SELECT prod_id, AVG(unit_cost) ac FROM costs GROUP BY prod_id) c
WHERE p.prod_id = c.prod_id AND
p.prod_list_price < 1.15 * c.ac;
or
select * from products;
from the 'sh' schema. Today I run a ADDM report, and this is the result:
ADDM Report for Task 'TASK_557'
Analysis Period
AWR snapshot range from 490 to 494.
Time period starts at 17-JUL-13 11.00.34 PM
Time period ends at 18-JUL-13 05.31.00 PM
Analysis Target
Database 'ORCL' with DB ID 1346555844.
Database version 11.2.0.3.0.
ADDM performed an analysis of instance orcl, numbered 1 and hosted at ROGER.
Activity During the Analysis Period
Total database time was 499 seconds.
The average number of active sessions was .01.
Summary of Findings
Description
Active Sessions
Recommendations
Percent of Activity
1 I/O Throughput
.01 | 100
2
2 Hard Parse
0 | 29.47
0
3 Hard Parse Due to Sharing Criteria 0 | 8.89
1
4 Row Lock Waits
0 | 7.37
0
5 PL/SQL Compilation
0 | 4.04
1
6 Unusual "User I/O" Wait Event
0 | 4.02
1
7 Commits and Rollbacks
0 | 3.08
1
8 Shared Pool Latches
0 | 2.78
0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
Finding 1: I/O Throughput
Impact is .01 active sessions, 100% of total activity.
The throughput of the I/O subsystem was significantly lower than expected.
Recommendation 1: Host Configuration
Estimated benefit is .01 active sessions, 100% of total activity.
Action
Consider increasing the throughput of the I/O subsystem. Oracle's
recommended solution is to stripe all data files using the SAME
methodology. You might also need to increase the number of disks for
better performance.
Rationale
During the analysis period, the average data files' I/O throughput was
1.4 K per second for reads and 1 K per second for writes. The average
response time for single block reads was 18 milliseconds.
Recommendation 2: Host Configuration
Estimated benefit is 0 active sessions, 17.55% of total activity.
Action
The performance of some data and temp files was significantly worse than
others. If striping all files using the SAME methodology is not
possible, consider striping these file over multiple disks.
Rationale
For file D:\ORACLE\APP\ORADATA\ORCL\SYSTEM01.DBF, the average response
time for single block reads was 168 milliseconds, and the total excess
I/O wait was 70 seconds.
Related Object
Database file
"D:\ORACLE\APP\ORADATA\ORCL\SYSTEM01.DBF"
Rationale
For file D:\ORACLE\APP\ORADATA\ORCL\SYSAUX01.DBF, the average response
time for single block reads was 16 milliseconds, and the total excess
I/O wait was 16 seconds.
Related Object
Database file
"D:\ORACLE\APP\ORADATA\ORCL\SYSAUX01.DBF"
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is 0 active sessions, 30.87% of total activity.
Finding 2: Hard Parse
Impact is 0 active sessions, 29.47% of total activity.
Hard parsing of SQL statements was consuming significant database time.
Hard parsing SQL statements that encountered parse errors was not consuming
significant database time.
Hard parses due to literal usage and cursor invalidation were not consuming
significant database time.
The Oracle instance memory (SGA and PGA) was adequately sized.
No recommendations are available.
Finding 3: Hard Parse Due to Sharing Criteria
Impact is 0 active sessions, 8.89% of total activity.
SQL statements with the same text were not shared because of cursor
environment mismatch. This resulted in additional hard parses which were
consuming significant database time.
Common causes of environment mismatch are session NLS settings, SQL trace
settings and optimizer parameters.
Recommendation 1: Application Analysis
Estimated benefit is 0 active sessions, 8.89% of total activity.
Action
Look for top reason for cursor environment mismatch in
V$SQL_SHARED_CURSOR.
Symptoms That Led to the Finding:
Hard parsing of SQL statements was consuming significant database time.
Impact is 0 active sessions, 29.47% of total activity.
Finding 4: Row Lock Waits
Impact is 0 active sessions, 7.37% of total activity.
SQL statements were found waiting for row lock waits.
No recommendations are available.
Symptoms That Led to the Finding:
Wait class "Application" was consuming significant database time.
Impact is 0 active sessions, 7.78% of total activity.
Finding 5: PL/SQL Compilation
Impact is 0 active sessions, 4.04% of total activity.
PL/SQL compilation consumed significant database time.
Recommendation 1: Application Analysis
Estimated benefit is 0 active sessions, 4.04% of total activity.
Action
Investigate the appropriateness of PL/SQL compilation. PL/SQL
compilation can be caused by DDL on dependent objects.
Finding 6: Unusual "User I/O" Wait Event
Impact is 0 active sessions, 4.02% of total activity.
Wait event "Disk file operations I/O" in wait class "User I/O" was consuming
significant database time.
Recommendation 1: Application Analysis
Estimated benefit is 0 active sessions, 4.02% of total activity.
Action
Investigate the cause for high "Disk file operations I/O" waits. Refer
to Oracle's "Database Reference" for the description of this wait event.
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is 0 active sessions, 30.87% of total activity.
Finding 7: Commits and Rollbacks
Impact is 0 active sessions, 3.08% of total activity.
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
Recommendation 1: Host Configuration
Estimated benefit is 0 active sessions, 3.08% of total activity.
Action
Investigate the possibility of improving the performance of I/O to the
online redo log files.
Rationale
The average size of writes to the online redo log files was 21 K and the
average time per write was 7 milliseconds.
Rationale
The total I/O throughput on redo log files was 0 K per second for reads
and 0.7 K per second for writes.
Rationale
The redo log I/O throughput was divided as follows: 0% by RMAN and
recovery, 100% by Log Writer, 0% by Archiver, 0% by Streams AQ and 0% by
all other activity.
Symptoms That Led to the Finding:
Wait class "Commit" was consuming significant database time.
Impact is 0 active sessions, 3.08% of total activity.
Finding 8: Shared Pool Latches
Impact is 0 active sessions, 2.78% of total activity.
Contention for latches related to the shared pool was consuming significant
database time.
Waits for "library cache load lock" amounted to 1% of database time.
Waits for "latch: shared pool" amounted to 1% of database time.
No recommendations are available.
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is 0 active sessions, 3.12% of total activity.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional Information
Miscellaneous Information
Wait class "Configuration" was not consuming significant database time.
CPU was not a bottleneck for the instance.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 94% of the analysis
period.
Being a small local database, my question is: do I really need to do something? For example at Finding 5: PL/SQL Compilation, what I really need to do? Or ar Finding 1: I/O Throughput
Thanks.Hi,
Mainly in ADDM you can consider
Recommendation
Estimated benefit
You have generated the report for ~18 hr time interval.
for test/local you can ignore this. -
ADDM Report is not produced by SQL DEV 4.0 if logged in user does not have SYSDBA privilege
Hello -
In SQLDEV 4.0 (Early Adapter), I logged in as user with no SYSDBA privilege granted. But ADVISOR granted and execute on DBMS_ADDM granted and "select any dictionary" granted, etc.
Then i go to the menu View --> DBA --> Performance --> Automatic Database Diagnostic Monitor
Select ADDM report from the available choices.
Out of 3 menu options: Summary, Findings and ADDM Report, I can see the first two, but I am getting a grey screen for ADDM Report.
^^^^^^^^^^^^^^^^^^^^^
If i do exactly the same but login as SYSDBA, then ADDM Report can be produced and can be seen. So the issue is in the missing grants and privileges.
^^^^^^^^^^^^^^^^^^^^^^
The goal that we are pursuing in our shop is to empower developers to work with ADDM reports by having them login as non-SYSDBA user.
^^^^^^^^^^^^^^^^^^^^^^^^
Please advise what privilege should be granted to get this working for non-SYSDBA login
The same user can successfully execute $ORACLE_HOME/rdbms/admin/addmrpt.sql and produce file with complete ADDM report. But not able to get the ADDM from SQL DEV 4.0
Thank you,
vrThank you, Phil.
This worked for me in my quick test case.
Great help, as DBA group wants to allow NON-privileged users (like Developers and QA) to execute ADDM on demand.
Here is my observation for RAC database with two instances.
I have followed your instructions:
"Performance / Automatic Database Diagnostic Monitor -> Run ADDM"
Then
- Uncheck box "By Creating New Snapshot" (this box was checked by default)
- Provide new "Task Name" (let's say "vr1")
- Select "Start Snapshot" (this is where my first confusion is: each screen shot # is shown twice, may be because i have two instances of RAC)
- Select "End Snapshot" (the same way: each SNAP_ID is shown twice)
- and finally APPLY button is pressed
This creates 3 reports:
vr1
vr1$1 (for instance_id=1)
vr1$2 (for instance_id=2_
So, my question is: this expected and normal behavior of the tool?
What if my RAC database has 8 instances? Then I would generate 9 separate ADDM reports?
Is this correct observation?
Thank you,
vr -
Just curious to know what is the difference between running *{color:#808000}awrrpt.sql{color}* and *{color:#808000}addmrpt.sql{color}*?
I could not get right information googling out.
Thanks for your time!1)addmrpt.sql -- Generates "DETAILED ADDM REPORT" which reports findings and gives recommendations about activities impacting the db most. It generates a text file.
2)awrrpt.sql -- Generates a "WORKLOAD REPOSITORY REPORT" which is like a statspack report. You can generate a html file from this script
Kev
Maybe you are looking for
-
Satellite P300-1AN - Touchpad issue with AC adapter
I've a Satellite P300-1AN notebook and since the beginning (two weeks) I have a touchpad issue: it is not immediately responsive and the pointer trembles when touching the pad. Very often it freezes for just one or two seconds. This is VERY annoying.
-
Document Type for Consignment-related invoice
hi , I i've changed the document type in OMR4 for consignment invoice ,but when MRKO generates the document show a error message that this document is not allow. What is wrong ?? Thaks Tatiana
-
Strange case of airport not detecting network
The airport menu often fails to show networks that are definitely being detected by the airport card - they show up strong and clear with stumblers - but I can't join the network either with the menu or the join network dialog. This can happen on net
-
Using 1.3.1 plug-in if 1.4 is installed
I want to make sure that the end user is going to run an applet using the Java 1.3.1 plug-in, even if a 1.4 plug-in is installed. However, the client machine uses the 1.4 if it is installed. How can I "force" the browser to use the 1.3.1 plug-in even
-
I have a tiny problem that is driving me mad. When I am playing an album in iTunes using cover flow view (with the playlist beneath the artwork picture) the picture is exactly above the album title. All is symmetrical. When I switch to full screen d