Abstract
How many times did DBAs have to open priority one service requests with Oracle support for critical errors faced while supporting their production environments? Errors are bound to happen, and as much as we would all like to see it, there is no such thing as the perfect application that is bug free. Critical errors can be caused by a misconfiguration or uncontrolled environments or due to human error; but when it occurs, they interrupt production, cause downtime, and slow performance that affects the credibility of the DBA, the system administrators, or the application in general. So it’s important that when problems do arise there is an immediate remedy, the database is operational immediately, and that the error has fixes in the form of patches or code, operational procedures, or configuration changes that ensure the errors do not happen again.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Source: Oracle Corporation.
- 2.
Source: Oracle Corporation.
- 3.
Troubleshoot on ORA-600 or ORA-7445 error using lookup tool—Metalink Note: 153788.1.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Murali Vallath
About this chapter
Cite this chapter
Vallath, M. (2014). Problem Diagnosis. In: Expert Oracle RAC Performance Diagnostics and Tuning. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-6710-2_18
Download citation
DOI: https://doi.org/10.1007/978-1-4302-6710-2_18
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-6709-6
Online ISBN: 978-1-4302-6710-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books