Abstract
The most efficient way to approach a reproducible problem is to take advantage of one of the available tracing and profiling features to perform a controlled measurement while an application is experiencing the problem. At first, the aim is to categorize the problem into three major classes:
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Or when a patch including the fix for bug 8328200 is installed (for example 11.2.0.1.0 Bundle Patch 7 for Exadata).
- 2.
The service name is a logical name associated to a database. It’s configured through the service_names initialization parameter, or through the dbms_service package. One database may have multiple service names.
- 3.
See http://www.oracledba.ru/orasrp for information.
- 4.
See http://method-r.com for information.
- 5.
See Oracle Support note TRCANLZR (TRCA): SQL_TRACE/Event 10046 Trace File Analyzer - Tool for Interpreting Raw SQL Traces (224270.1) for additional information.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Christian Antognini
About this chapter
Cite this chapter
Antognini, C. (2014). Analysis of Reproducible Problems. In: Troubleshooting Oracle Performance. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5759-2_3
Download citation
DOI: https://doi.org/10.1007/978-1-4302-5759-2_3
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-5758-5
Online ISBN: 978-1-4302-5759-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books