When I was reading about statement restarts, I thought it usually happens in a multi-user system or in the presence of triggers. However, last week one of our developers asked me to help him to figure out why a simple update statement was reading far more data than it was in the table. That blog post is published to share my findings about that.
I encountered that issue originally when I migrated one of my databases to 12.2.0.1.190416.
A question about optimizing access to V$DB_PIPES just came up recently on the SQL.RU Oracle database forum.
The Topic Starter wanted to find out if there is a way to speed up the query against V$DB_PIPES, or there are any other options to see if a named pipe exists.
A developer came to me the other day to ask me about an ORA-04036 error he encountered.
The goal of this blog post is to provide steps to troubleshoot the ORA-04036 error without modifying the source code.
That is another optimizer issue I came across this week while working with developers on tuning application queries.
I have recently investigated why there are some databases in my environment which are shown with empty OSDBA or OSOPER groups.
I was migrating several databases from AWS EC2 non-Nitro based instances to Nitro-based ones when I came across one issue with Oracle Recovery Manager (RMAN). This blog post is about it.
ORA-01031 select V$RESTORE_POINT in PL/SQLThis blog post is about an issue with V$RESTORE_POINT and ORA-01031 that I encountered after upgrading one database to 12.2.
After applying the 12.2.0.1.190416 Release Update (RU) patch, I noticed that the target version had not been updated.
While investigating a poor query performance issue, I came across the following Real-Time SQL Monitoring report from a 12.1 database.