Oracle Trace is one of my favorite tools when working with performance. It’s not my only tool, but it’s a tool which have given me great success when working on performance related issues. In this small article I’ll try to explain why? I’ll start by telling a small story.
Personal info
My tweets:
Fetch Tweets: Could not authenticate you. Code: 32Java
Oracle
Oracle Blogs
-
Recent Posts
- Testing solution to MERGE with sequence NEXTVAL
- Strange behavior in MERGE with sequence NEXTVAL
- Use default parameter/setting (row) if not set specific for entity
- SQL Developer, Database Copy and TRUNCATING unwanted tables
- Copy schema with data pump when using editions
- The NUMBER datatype without precision
- Redundant NOT NULLs in DDL
- Java and JDBC for Oracle DBAs – Part 6: Spring-boot, JPA and Hibernate
- PLSQL: Nice little overview of the PL/SQL language
- MacOS: Finally a text editor competing with Notepad++
Disclaimer
For the avoidance of any doubt, all views expressed here are my own and not those of past or current employers, clients, friends, Oracle Corporation, EVRY, my Mum or, indeed, my mother in law. If you want to sue someone, I suggest you pick on Tigger, but I hope you have a good lawyer. Frankly, I doubt any of the former agree with my views or would want to be associated with them in any way.
