Patching Oracle Grid Infrastructure Standalone Environment Using opatchauto Out of Place (OOP) Patching
A practical demonstration of performing unattended Grid Infrastructure Out of Place patching using opatchauto and property files.
2019¶
SQL92_SECURITY and ORA-01031
SQL92_SECURITY has changed its default value to TRUE starting from 12.2.0.1: Upgrade Guide.
That might lead to ORA-01031: insufficient privileges errors being thrown in runtime as this post demonstrates.
Temporary LOBs
I have recently optimized one of processes working with LOBs and decided to write a blog post about it.
APEX WWV_FLOW_SECURITY.GET_OWNER_OF_CALLING_CODE and 12.2
Our developers were using WWV_FLOW_API.SET_SECURITY_GROUP_ID and were surprised to find that that procedure behaves differently in 12.2 than in 12.1.
Unwrapping PL/SQL: Using Custom Wrap Tables
A practical demonstration of how to use custom wrap tables to affect Oracle wrap behavior.
Unwrapping PL/SQL: a Systematic Approach
In this blog post, I will show how I discovered the Oracle Wrap substitution table by reverse engineering Oracle binaries.
Bug 26588069 - Wrong Result (Duplicate Rows Produced) Using Group By After Upgrading To 12.2.0.1
I have stumbled upon this bug after upgrading one of my databases to 12.2.0.1 when one of application queries started returning extra rows.
Starting Oracle Database on Demand Using Socket Activation
I remember watching a video about Amazon Aurora Serverless where it was demonstrated that your database can be started on demand when the first connection comes. Although it is not something that you might want for your 24x7 OLTP database, it can come in handy for Development environments that have the intermittent usage pattern. I decided to write a blog post about how that can be done for an Oracle Database server working on a systemd-based Linux Operating System.
That Old Restart Problem Strikes Back: Triggers to the Rescue
Database triggers are notoriously known for slowing down DML operations. Yet, they lead to a remarkable consequence while applying to the first post of this series in which I demonstrated statement restarts within a single user session updating a non-partitioned table.
That Old Restart Problem Strikes Back: Getting What You Pay for
During my previous research, I was also testing the same UPDATE statement against a partitioned table.
I was slightly puzzled that I did not observe any statement restarts in the performance statistics, even after I updated tens of millions of rows in the partitioned table.
It turns out that there are still statement restarts there, however, they do not lead to such dreadful ramifications when a table is being read three times.