A few years ago I wrote the post All You Need to Know about Oracle Database Patching, and I also presented a presentation about this topic a few time. But
A few years ago I wrote the post All You Need to Know about Oracle Database Patching, and I also presented a presentation about this topic a few time. But
Lately I’m in the process of upgrading a few clients to 18c and 19c, so I expected to hit a few issues. In this post I’ll discuss a specific issue
These days I’m in the progress of patching all databases for a specific client to 18.10 (from 18.9 as we need to be up to date). However, we realized that
When I worked on Oracle Cloud 20c for my Data Dictionary Changes post, I ran into a problem with DST difference. Oracle 20c (20.2) is coming with DST V34 while
I wrote lately a couple of post about upgrading to 18c (why research is important and OCR and Voting disks on 18c and 19c). These posts were the result of
This is a topic I wrote about in the past (understanding Oracle patching and new version numbering). But now, after the new patching concept (since 12.2) and numbering change (since
One of my client is on 12.1 and since the support for 12.1 has ended we started planning the upgrade of this database. During the research I did before the
Oracle Open World was interesting like every year. This year, Oracle started talking about features that will probably be in Oracle 19c (which is the last 12.2 release). The rumor
Different software components (operating systems, databases, etc.) are updating our clocks automatically when our country changes the clock (when daylight saving starts or ends). In order to do that, the
I’ve installed quite a few PSUs in my professional life, but this time, it was something else. I’m talking about a RAC environment with 2 nodes and a database containing