| main - Oracle Database Diagnostics | |
This menu enables you to collect database diagnostics based
on a specific issue. Database components are organized
by categories for improved diagnostic collection and analysis.
Select one of the following options:
(1) Installation
(2) Upgrade
(3) Configuration
(4) General
(5) Patching
(6) Performance
(7) Backup and Recovery
(8) Network
(H)elp (E)xit
Showing Menu Help:
Oracle Diagnostic Assistant Database Target Main Menu Help
Explanation of available options:
(1) Installation
o Execute Health Check / Validation Engine HCVE
(2) Upgrade
o Execute Health Check / Validation Engine HCVE
o Database Status
(3) Configuration
o Run the RDA DB_Assessment collection
o Get configuration information
o Get archive destination information
o Get CPU count information
o Get NLS information
o Get DB block size information
o Get dumpdest information
o Health Check / Validation Engine HCVE
(4) General
o OSWatcher
o Core File Stack Trace
o Invalid Objects
o Dynamic Properties
o Tablespace
o Other
- Redo Generation Rate in KB/second
- Fast-Start Failover Occurred
- Deferred Transaction Count
- Feature Usage
- Owner's Invalid Object Count
- Database Job Status
(5) Patching
o List patches applied
o DB Component Versions
(6) Performance
o Get database and SQL performance information
o Process session hang
o Run RDA Exadata_DatabaseHang collection
(7) Backup and Recovery
o Run the RDA DB_BackupRecovery collection
(8) Network
o Listener
o Server
o Shared Server
o Configuration
o NET rda module
|
|
| Menu Option: 1 - [+] Show Menu Details | |
| Menu Option: 2 - [+] Show Menu Details | |
| Menu Option: 3 - [+] Show Menu Details | |
| Menu Option: 4 - [+] Show Menu Details | |
| Menu Option: 5 - [+] Show Menu Details | |
| Menu Option: 6 - [+] Show Menu Details | |
| Menu Option: 7 - [+] Show Menu Details | |
| Menu Option: 8 - [+] Show Menu Details | |
| Install - Database Installation Diagnostics | |
This menu enables you to collect database installation data.
Select one of the following options:
(1) HCVE For RAC 10g and OS Best Practises
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Database Target: Installation Main Menu Help
Explanation of available options:
(1) Executes the Health Check Validation Engine for RAC
10g DB and OS Best Practices (Linux)
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| Upgrade - Database: Upgrade Diagnostics | |
This menu enables you to collect database data both
before and after an upgrade.
Select one of the following options:
(1) HCVE For RAC 10g and OS Best Practises
(2) Database Status
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Demo Menu Help Title.
The Administration Menu enables you to perform limited
admin functions.
Explanation of available options:
(1) Runs OS command ls -l
This selection provides options for viewing and managing files
There 2 issues that need to be checked with this command:
o size of directory
o any missing files shown below:
Note: some extra details here ... to help the user understand
the purpose of running this command and using it to solve
a problem.
(2) Sub Menu yyy
This option provides access to yyy detailed information
of data collections performed
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| Config - Database: Configuration Diagnostics | |
This menu enables you to collect database configuration diagnostics
based on a specific issue. The configuration components are organized
into categories for improved diagnostic collection and analysis.
Select one of the following options:
(1) Database Assessment
(2) Configuration
(3) Archive Destination
(4) CPU Count
(5) NLS
(6) DB Block Size
(7) Dumpdest
(8) HCVE
(9) Memory Setup - TBD
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Database Target: Configuration Main Menu Help
Explanation of available options:
(1) Database Assessment
(2) Configuration
(3) Archive Destination
(4) CPU Count
(5) NLS
(6) DB Block Size
(7) Dumpdest
(8) HCVE
(9) Memory Setup - TBD
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: 6 - [+] Show Command Details | |
| Menu Option: 7 - [+] Show Command Details | |
| Menu Option: 8 - [+] Show Menu Details | |
| Menu Option: 9 - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| HCVE - Config: Health Check Assessments | |
Select your database to execute the correct HCVE
Database Assessment.
Select one of the following options:
(1) Oracle Database 10g - 10.1.x
(2) Oracle Database 10g - 10.2.x
(3) Oracle Database 11g - 11.1.x
(4) Oracle Database 11g - 11.2.x
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Preinstallation: Health Check Assessments Menu Help
Explanation of available options:
(1) Oracle Database 10g - 10.1.x
Select this option if you have a 10.1.x database environment
(2) Oracle Database 10g - 10.2.x
Select this option if you have a 10.2.x database environment
(3) Oracle Database 11g - 11.1.x
Select this option if you have a 11.1.x database environment
(4) Oracle Database 11g - 11.2.x
Select this option if you have a 11.2.x database environment
Please review Knowledge Article 250262.1: RDA 4 -Health Check /
Validation Engine Guide (https://support.oracle.com/CSP/main/
article?cmd=show&type=NOT&id=250262.1)
for detailed information on Health Check usage.
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| General - Database: General Diagnostics | |
This menu enables you to collect various database diagnostics
that are commonly used in troubleshooting database issues.
Select one of the following options:
(1) OSWatcher
(2) Core File Stack Trace
(3) Invalid Objects
(4) Dynamic Properties
(5) Tablespace
(6) Other
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
General Database Diagnostics Help
Explanation of available options:
(1) OSWatcher
(2) Core File Stack Trace
This command will get a stack trace from a core dump produced by
any of the Oracle products on Unix platforms. For more information
see "Getting a Stack Trace from a CORE file on Unix" (Note 1812.1).
Before you can use this command, you must download the stack
script from "STACKX Core / Stack Trace Extraction Toolnote (Note
362791.1). You will need to specify the location of this script.
(3) Invalid Objects
(4) Dynamic Properties
Displays dynamic property values from the database.
(5) Tablespace
Displays tablespace values from the database.
(6) Other
Displays other values from the database.
|
|
| Menu Option: 1 - [+] Show Menu Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Menu Details | |
| Menu Option: 5 - [+] Show Menu Details | |
| Menu Option: 6 - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| OSWatcher - OSWatcher | |
OSWatcher is an tool that reports CPU, RAM and Network stress.
Select one of the following options:
(1) OSWatcher - Limited by date
(2) OSWatcher - Limited by time
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: OSWatcher
Oracle OS watcher (OSWatcher) reports CPU, RAM and Network stress,
and is a new alternative for monitoring Oracle servers.
For more information on OSWatcher, see My Oracle Support
Knowledge Article 301137.1: OS Watcher Black Box User Guide
(https://support.oracle.com/CSP/main/article?cmd=show&type=
NOT&id=301137.1).
The following options will prompt for the directory path where
OSWatcher is installed. Once prompted, the value is stored in
config/user.properties: DA_OSWATCHER_DIR and you will not be
prompted again. They will also prompt for date or date and
time, depending on which option you choose.
Explanation of available options:
(1) OSWatcher - Limited by date
(2) OSWatcher - Limited by time
When providing date values, you must use YY.MM.DD format. For
example, May 31, 2011 would be 11.05.31. When providing time
values, you must use the 24 hour HHMM format. For example,
5 PM would be 1700. You may also use a time range; for example,
5 PM to 7 PM would be 1[7-9]00.
Oracle OS watcher is especially useful for Linux/UNIX-based RAC
systems where monitoring the OS is important for identifying CPU,
RAM or network stress. Oracle OS Watcher may invoke these popular
UNIX/Linux utilities, depending on the platform (Solaris, HP/UX,
Linux and Tru64):
* vmstat
* iostat
* top
* netstat
* traceroute
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| dyn_prop - Dynamic Properties | |
Diplays dynamic property values from the database.
Select one of the following options:
(1) Database version
(2) CPU Timing Enabled
(3) RAC Options
(4) Server Manageability
(5) Config
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Diplays dynamic property values from the database
Each option queries information from the database and returns the
appropriate value(s) to the screen.
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| ts_prop - Tablespace Properties | |
Diplays tablespace values from the database
Select one of the following options:
(1) Tablespace Space Used as a %
(2) Tablespace Free Space in MB
(3) Tablespace Allocation
(4) Recovery Area Free Space
(5) SYSTEM Tablespace Number
(6) SYSAUX Tablespace Number
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Diplays tablespace values from the database. Each option queries information from the database and returns the appropriate value(s) to the screen. |
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: 6 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| other_prop - Other Properties | |
Diplays other values from the database
Select one of the following options:
(1) Redo Generation Rate in KB/second
(2) Fast-Start Failover Occurred
(3) Deferred Transaction Count
(4) Feature Usage
(5) Owner's Invalid Object Count
(6) Database Job Status
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Diplays other values from the database. Each option queries information from the database and returns the appropriate value(s) to the screen. |
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: 6 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| Patching - Database: Patching Diagnostics | |
Select one of the following options:
(1) List patches applied
(2) DB Component Versions
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Database Target: Patchin Main Menu Help
Explanation of available options:
(1) Shows a list of patches applied to this ORACLE_HOME
(2) Shows a list of DB Component Versions
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| Perform - Database: Performance Diagnostics | |
Select one of the following options:
(1) Top SQL Statements
(2) Database is Running Slowly
(3) Slow Database Due to SQL Performance - TBD
(4) Database Appears to Hang
(5) Sql Statement Running Slowly
(6) Sql Issues
(7) Process/Session Appears to Hang
(8) Exadata Database Appears to Hang
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Database Target: Performance Main Menu Help
Explanation of available options:
(1) Top SQL Statements
o Used to identify SQL statements or SQL_ID values
(2) Database is Running Slowly
o AWR and ADDM
(3) Slow Database Due to SQL Performance - TBD
(4) Database Appears to Hang
o Includes tools like HangFG, LTOM, Procwatcher and OSWatcher
(5) Sql Statement Running Slowly
o Includes tools like SQLHC and SQLT
o For more information on SQLHC, see My Oracle Support
Knowledge Article 1366133.1: SQL Tuning Health-Check Script (SQLHC)
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1366133.1)
o For more information on SQLT, see My Oracle Support
Knowledge Article 215187.1: SQLT (SQLTXPLAIN)
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215187.1)
(6) Sql Issues
o Includes DBMS_SQLDIAG and DBMS_PROFILER
o For more information on DBMS_SQLDIAG, see My Oracle Support
Knowledge Article 1386802.1: How To Use DBMS_SQLDIAG To Diagnose
Query Performance and 727863.1: How to Create a SQL-testcase
Using the DBMS_SQLDIAG Package [Video]
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1386802.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=727863.1)
(7) Process/Session Appears to Hang
o Includes trace and errorstack commands
(8) Exadata Database Appears to Hang
|
|
| Menu Option: 1 - [+] Show Menu Details | |
| Menu Option: 2 - [+] Show Menu Details | |
| Menu Option: 3 - [+] Show Menu Details | |
| Menu Option: 4 - [+] Show Menu Details | |
| Menu Option: 5 - [+] Show Menu Details | |
| Menu Option: 6 - [+] Show Menu Details | |
| Menu Option: 7 - [+] Show Menu Details | |
| Menu Option: 8 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| dbSlow - Database Running Slowly | |
Select one of the following options:
(1) Display snapshots for AWR and ADDM
(2) Run AWR and ADDM
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
This menu runs the Workload Repository Report. The report takes a
starting snapshot ID and an ending snapshot ID as parameters. Run step
1 to identify the desired snapshots. Then run step 2 to produce the report.
(1) Display snapshots for AWR and ADDM
o Run this to identify the snapshots needed as parameters to the report
o Displays snapshots for the last 3 days
(2) Run AWR and ADDM
o Runs the Workload Repository Report for the given snapshot range
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| SQLStmts - Performance: Top Running SQL Statements | |
Select one of the following options:
(1) Top SQL Statements in Cache, order by elapsed time
(2) Top SQL Statements, order by Physical Disk Reads
(3) SQL Monitoring
(4) Find SQL_ID by query text
(5) Find SQL_ID by date
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: Top Running SQL Statements Help Menu
This menu provides multiple ways to capture/identify long running
sql statements.
Explanation of available options:
(1) Top SQL Statements stored in Cache, order by elapsed time
o Collects SQL statements that are currently stored in the
SQL cache
o results are ordered by Elapsed Time
(2) Top SQL Statements ordered by Physical Disk Reads
o Identifies SQL statements that are doing the most diskreads
o SQL Statements doing a lot of physical IO may well be using
Full Table Scans as their primary method of access where
indexes may be appropriate
o Use this output to investigate these Statements further
(3) SQL Monitoring
o The SQL statement must:
* be CURRENTLY running, or
* have executed long enough to get monitored, but recently
enough that the DB has not lost track of it
o Licenses are needed for 11g and higher. SQL Monitoring is a feature
of the Oracle Database Tuning Pack. In addition,
Oracle Diagnostics Pack is a prerequisite product to Oracle
Tuning Pack. Therefore, to use SQL Monitoring, licenses for both
Diagnostics and Tuning Pack are required.
(4) Find SQL_ID by query text
o Queries V$SQL and returns queries which match the given query text
(5) Find SQL_ID by date
o Queries V$SQL and returns queries which are newer than the given
date
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| dbHang - Performance: Database Hang | |
Select one of the following options:
(1) HangFG Report
(2) Configure/Run LTOM
(3) Process Spins/Hangs - Procwatcher
(4) OSWatcher Blackbox
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
DB: Performance DB Hang Help Menu
Explanation of available options:
(1) HangFG Report
HANGFG (Hang file generator) is a series of unix shell scripts
used to automate the generation and collection of hanganalyze
and systemstate trace files.
HANGFG generates and collects hang trace files based on the
impact of taking diagnostic traces on a system which is already
in a degraded state.
The overall decision on what level of impact the user can afford
is left up to the user when he runs HANGFG, as the level of impact
is passed in as an argument to the tool.
HANGFG is also capable of making this decision for the user if the
user selects light or medium impact (option 1 or 2) as an argument
to the tool.
HANGFG is RAC aware and can run in either a RAC or non RAC
environment.
For more details see:
o HANGFG User Guide (Doc ID 362094.1)
(2) Configure/Run LTOM
The Lite Onboard Monitor (LTOM) provides real-time automatic
problem detection and data collection.
LTOM runs on a target UNIX server, is tightly integrated with the
host operating system and provides an integrated solution for
detecting and collecting trace files for system performance issues
in real-time.
LTOM provides services for:
o Automatic Hang Detection
o System Profiling
o Automatic Session Tracing
For more details see:
o Document 352363.1 LTOM - The On-Board Monitor User Guide
(3) Process Spins/Hangs (using Procwatcher)
Procwatcher is a tool that examines and monitors Oracle database
and/or clusterware processes at a specific interval.
It can collect 'stack' information from processes which can help
debug the cause of issues where processes appear to "hang" or "spin"
For more details see:
o Document 459694.1 Procwatcher: Script to Monitor and Examine
Oracle DB and Clusterware Processes
(4) OSWatcher Blackbox
OS Watcher Black Box (OSWbb) is a collection of UNIX shell scripts
intended to collect and archive operating system and network
metrics to aid support in diagnosing performance issues.
OSWbb operates as a set of background processes on the server and
gathers OS data on a regular basis, invoking such Unix utilities
as vmstat, netstat and iostat.
For more details see:
o Document 301137.1 OS Watcher Black Box User Guide
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Menu Details | |
| Menu Option: 3 - [+] Show Menu Details | |
| Menu Option: 4 - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| SQLSlow - Perfomance: SQL Statement Running Slowly | |
Select one of the following options:
(1) Verify Common Issues using SQLHC
(2) Collect SQL Tuning Diagnostic Information using SQLT
(3) Collect Performance Information
(4) Create testcase using DBMS_SQLDIAG
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Perormance: SQL Stmt is Running Slow.
These options are helpful is targeting slow running sql statements.
(1) Verify Common Issues
o uses SQLHC
o For more information on SQLHC, see My Oracle Support
Knowledge Article 1366133.1: SQL Tuning Health-Check Script (SQLHC)
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1366133.1)
(2) Collect SQL Tuning Diagnostic Information using SQLT
o uses SQLTXPLAIN
o For more information on SQLT, see My Oracle Support
Knowledge Article 215187.1: SQLT (SQLTXPLAIN)
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215187.1)
(3) Run DBMS_SQLDIAG PERFORMANCE Task against a SQL_ID or SQL
o For more information on DBMS_SQLDIAG, see My Oracle Support
Knowledge Article 1386802.1: How To Use DBMS_SQLDIAG To Diagnose
Query Performance and 727863.1: How to Create a SQL-testcase
Using the DBMS_SQLDIAG Package [Video]
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1386802.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=727863.1)
(4) Create testcase using DBMS_SQLDIAG
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Menu Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| sqltxplain - Performance: SQLTXPLAIN | |
Select one of the following options:
(1) XTRACT
(2) XECUTE
(3) XTRXEC
(4) XTRSBY
(5) XPLAIN
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: SQLTXPLAIN
The SQLTXPLAIN utility has many options available.
Explanation of available options:
(1) XTRACT
o You will be prompted for the SQL_ID or HASH_VALUE
(2) XECUTE
o You will be prompted for the full path to the SQL script
(3) XTRXEC
o You will be prompted for the SQL_ID or HASH_VALUE
(4) XTRSXBY
o You will be prompted for the SQL_ID or HASH_VALUE and the
name of the DB link
(5) XPLAIN
o You will be prompted for the full path to the SQL script
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| SQLIssue - Performance: Sql Issues | |
Select one of the following options:
(1) SQL Getting Wrong Result
(2) Session Crash / Critical Error
(3) Enable DBMS_PROFILE to Analyze Processing Time
(4) Analyze Processing Time Using DBMS_PROFILER - See Help BEFORE selecting
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: Sql Issues Help
The Administration Menu enables you to perform limited
admin functions.
Explanation of available options:
(1) SQL Getting Wrong Result
o You will be prompted for the sql query causing the
incorrect results. Alternatively, you may provide the SQL_ID
instead, if you know it.
o Uses the DBMS_SQLDIAG utility
o When providing the SQL statement, be sure to replace
each single quote with TWO single quotes
- Example: select ''x'' from dual
(2) Session Crash / Critical Error
o You will be prompted for the sql query causing the
incorrect results. Alternatively, you may provide the SQL_ID
instead, if you know it.
o Uses the DBMS_SQLDIAG utility
o When providing the SQL statement, be sure to replace
each single quote with TWO single quotes
- Example: select ''x'' from dual
(3) Enable DBMS_PROFILE to Analyze Processing Time
o Runs proftab.sql script to build the tables needed for DBMS_PROFILER
o Runs profload.sql script to install the DBMS_PROFILER API
o only needs to be run ONE time in a given database
(4) Analyze Processing Time Using DBMS_PROFILER
o Generates the DBMS_PROFILER report
o *BEFORE* you run this command, some MANUAL steps are required:
- Start PL/SQL Profiler in your application:
EXEC DBMS_PROFILER.START_PROFILER('optional comment');
- Execute your transaction to be profiled.
- Calls to PL/SQL Libraries are expected.
- Stop PL/SQL Profiler: EXEC DBMS_PROFILER.STOP_PROFILER;
Once you have completed these three tasks, this command will
generate the report
o You will be prompted for a runid
o For more details about the PL/SQL Profiler DBMS_PROFILER
see Note 243755.1
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 9 - [+] Show Command Details | |
| Menu Option: 10 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| LTOM - LTOM | |
Select one of the following options:
(1) Start LTOM
(2) Stop LTOM
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: Process Spins/Hangs Help Menu
LTOM is a java program designed as a real-time diagnostic platform for
deployment to a customer site. LTOM differs from other support tools, as it
is proactive rather than reactive. LTOM provides real-time automatic problem
detection and data collection. LTOM runs on the customer's UNIX server, is
tightly integrated with the host operating system and provides an integrated
solution for detecting and collecting trace files for system performance
issues. The ability to detect problems and collect data in real-time will
hopefully reduce the amount of time it takes to solve problems and reduce
customer downtime.
You may perform the following actions for LTOM:
(1) Start LTOM
(2) Stop LTOM
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| Procwatcher - Procwatcher | |
Procwatcher is an external tool to examine and monitor Oracle
database and/or clusterware processes at an interval.
If you experience problems with Procwatcher, please contact the owner
of My Oracle Support Knowledge Article 459694.1: Script to Monitor and
Examine Oracle DB and Clusterware Processes (https://support.oracle.com/
CSP/main/article?cmd=show&type=NOT&id=459694.1) for assistance.
Select one of the following options:
(1) Procwatcher status
(2) Start Procwatcher
(3) Stop Procwatcher
(4) Package Procwatcher files
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: Procwatcher Help Menu
Procwatcher is an external tool to examine and monitor Oracle
database and/or clusterware processes at an interval.
If you experience problems with Procwatcher, please contact the owner
of My Oracle Support Knowledge Article 459694.1 - Procwatcher: Script
to Monitor and Examine Oracle DB and Clusterware Processes
(https://support.oracle.com/CSP/main/article?cmd=show&type=
NOT&id=1070954.1)for assistance.
The following options will prompt for the directory path where
Procwatcher is installed. Once prompted, the value is stored in
config/user.properties: DA_PROCWATCHER_DIR and you will not be
prompted again.
Explanation of available options:
(1) Procwatcher status
(2) Start Procwatcher
(3) Stop Procwatcher
(4) Package Procwatcher files
Additionally, if Procwatcher is deployed, all output will go to
GRID_HOME/log/procwatcher but it is possible to run prw.sh standalone
from any directory if it is not deployed.
If installed as standalone, and if prw finds clusterware active,
the output will go to GRID_HOME/log/procwatcher
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| OSWbb - OSWatcher Black Box | |
OSWatcher is an tool that reports CPU, RAM and Network stress.
Select one of the following options:
(1) Start OSWbb
(2) Stop OSWbb
(3) Package OSWbb Files
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: OSWatcher Black Box Help
OSWbb now provides an analysis tool OSWbba which analyzes the
log files produced by OSWbb. This tool allows OSWbb to be
self-analyzing. This tool also provides a graphing capability
to graph the data and to produce a html profile. See the
"Graphing the Output" section below.
OS Watcher Black Box (OSWbb) is a collection of UNIX shell scripts
intended to collect and archive operating system and network metrics
to aid support in diagnosing performance issues. OSWbb operates as a
set of background processes on the server and gathers OS data on a
regular basis, invoking such Unix utilities as vmstat, netstat and
iostat.
OSWbb is installed on each node where data is to be collected.
For more information on OSWatcher Black Box, see My Oracle Support
Knowledge Article 301137.1: OS Watcher Black Box User Guide
(https://support.oracle.com/CSP/main/article?cmd=show&type=
NOT&id=301137.1).
Explanation of available options:
(1) Start OSWbb
The main controlling executive (OSWatcher.sh) is started which
spawns individual shell processes to collect specific kinds of
data, using Unix operating system diagnostic utilities
(2) Stop OSWbb
stopOSWbb.sh will be invoked to terminate all processes
associated with OSWbb, and is the normal, graceful mechanism
for stopping the tool's operation
(3) Package OSWbb Files
Each data collector has its own file, created and named by
the File Manager process
This option will gather those files and package them into
a single file which can then be easily uploaded to support
if needed
To collect database metrics in addition to OS metrics consider
running LTOM.
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| processHang - Performance: Process Hang | |
When a process appears to hang, use one of the options below to gather
diagnostic data to help troubleshoot the issue.
*** Don't forget to turn trace OFF when done.
Select one of the following options:
(1) ErrorStack Using OS Process ID - may take > 1 min to run
(2) ErrorStack Using Oracle Process ID - may take > 1 min to run
(3) Stop Trace
(4) CPU Usage - valid for HPUX, Solaris and Windows only
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Performance: Process Hang Help
Trace files can be executed using OS process ID or Oracle process ID.
Explanation of available options:
(1) ErrorStack Using OS Process ID
o You will be prompted for OS Process ID
o Selecting this option will turn on sql_trace/10046
o Caution: collection may take more than a few seconds to execute
o Options 1 and 2 will return the same information - they only differ
in what input parameter is used to generate the error stack
(2) ErrorStack Using Oracle Process ID
o You will be prompted for Oracle Process ID
o Selecting this option will turn on sql_trace/10046
o Caution: collection may take more than a few seconds to execute
o Options 1 and 2 will return the same information - they only differ
in what input parameter is used to generate the error stack
(3) Stop Trace
o Selecting this option will disable everything, not just what
was turned on in option 1 and 2 above
o If you do NOT selecting this option after process trace
(option 1 or 2) has been captured, the trace will continue
to run indefinitely
(4) CPU Usage - valid on HPUX, Solaris, Windows only
o Only valid on HPUX, Solaris and Windows operating systems
o Provide the OS Process ID
o Runs OS specific commands to diagnose high CPU usage of the
given OS process
WARNING: The diagnostic for HPUX will run until the process ID
you provide has ended, which may be indefinitely if
that process is hung
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| Backup - Database:Backup and Recovery Diagnostics | |
Select one of the following options:
(1) Backup and Recovery Collection
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Database Target: Backup and Recovery Main Menu Help
Explanation of available options:
(1) Run RDA DB_BackupRecovery collection
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| Network - Database: Network | |
Select one of the following options:
(1) Listener - Hang/Performance
(2) Listener - Status and Services Registered
(3) Server - Find Service Name - needed for Load Balancing
(4) Server - Load Balancing
(5) Shared Server - Configuration
(6) Shared Server - Dispatchers Monitoring Performance
(7) Shared Server - Performance
(8) Configuration
(9) General
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
Demo Menu Help Title.
The Administration Menu enables you to perform limited
admin functions.
Explanation of available options:
(1) Listener: Hang/Performance
(2) Listener: Status and Services Registered
(4) Server: Find Service Name - needed for Load Balancing
(5) Server: Load Balancing
(3) Shared Server Configuration
(6) Shared Server: Dispatchers Monitoring Performance
(7) Shared Server: Performance
(8) Configuration
(9) General
|
|
| Menu Option: 1 - [+] Show Command Details | |
| Menu Option: 2 - [+] Show Command Details | |
| Menu Option: 3 - [+] Show Command Details | |
| Menu Option: 4 - [+] Show Command Details | |
| Menu Option: 5 - [+] Show Command Details | |
| Menu Option: 6 - [+] Show Command Details | |
| Menu Option: 7 - [+] Show Command Details | |
| Menu Option: 8 - [+] Show Command Details | |
| Menu Option: 9 - [+] Show Command Details | |
| Menu Option: B - [+] Show Menu Details | |
| Menu Option: M - [+] Show Menu Details | |
| tbd - TBD: Command not ready | |
TBD - Command not yet developed
Select from the menu below to continue:
(M)ain (B)ack (H)elp (E)xit
Showing Menu Help:
TBD - command not yet developed |
|
| Menu Option: M - [+] Show Menu Details | |
| Menu Option: B - [+] Show Menu Details | |
| COMMAND: PREREQ_os_230_lic | |
| COMMAND TYPE: | OS |
| COMMAND TITLE: | Valid values for lic field for command os_230 |
| COMMAND DESCRIPTION: | |
TODO |
|
| COMMAND ARGUMENT(S): | |
echo Tuning=T
echo Diagnostics=D
echo None=N
|
|
| COMMAND: PREREQ_sql_type | |
| COMMAND TYPE: | OS |
| COMMAND TITLE: | Valid values for sql_type |
| COMMAND DESCRIPTION: | |
TODO |
|
| COMMAND ARGUMENT(S): | |
echo sql_id
echo sql_text
|
|