Reading the “new features” topic “Case insensitive database” for Oracle 12.2 it sounds as if you are back in the last century where data was stored case insensitive. But guess we are all on one page: that’s not what we want to have. In reality this feature is not to store data indepentent but to search and sort data independent of upper or lower case or accents. That’s what “collation” stands for.
Oracle 12.2 Collation Blogbeitrag lesen »
With Version 12.2.02 the release policy for Oracle database will change drastically. During his keynote at DOAG 2017 Datenbank Andy Mendelsohn (Executive Vice President for Database Server Technologies at Oracle) said, that there will be no Version 12.2.0.2 but instead Oracle will release a new database version every year and the version number will be the year. Now we got the announcement: The next database release will be 18 (due to the “Release Schedule of Current Database Releases (Doc ID 742060.1)”
New Oracle Release Policy Blogbeitrag lesen »
About problems with Oracle 12c Multitenant Database Back in the days everything was easier, wasn’t it? Thus far you connect to your database and in doubt you send a query to v$instance or v$database to check you’re actually connected to the right place. But since 12c the world is no more that clear. Meanwhile we’ve got the Multitenant Option and by connecting to a Pluggable Database, maybe you won’t get the desired result. But for what reason it is such a problem?
Help, where am I? CDB or PDB … and which DB anyway? Blogbeitrag lesen »
Flashback Pluggable Database Oracle 12.2 will be general available within the next few weeks including several new fetaures for Flashback Pluggable Database. But it will take some more month before customers will adopt 12.2 for their production database and we need some more experience with the PDB Undo management. Because thats the requirement for Flashback Pluggable Database. But you can use this feature alread with 12.1.0.2 if your environment relies on Data Guard.This configuration might be an interesting alternative because it ends up with two individual PDBs – the original and the flashback version.
Flashback PDB with Version 12.1.0.2 Blogbeitrag lesen »
The Challenge There are some anomalies when using Multitenant Database with Data Guard. In the following example I will describe how to clone a pluggable database and synchronize Data Guard. The base is Oracle 12 Release 1 (12.1.0.2) and Data Guard without Real Time Query (Active Data Guard).
PDB Cloning with Data Guard Blogbeitrag lesen »
Few weeks ago I had issues with naming conventions: In one of my projects a cloning software should be used. The installation went fine but the integration of the first database failed. The error message stated that the service is not available – but to my knowledge all entries are fine …
Servicename or not? Blogbeitrag lesen »
Many people shared their favorite Oracle feature as blog post. Currently Oracle 12.1 is the most actual version but 12.x is on it’s way. So my not posting something on the newest and greatest features – like my favorite: “Multitenant Database”? There is one single feature in the Oracle database which is outstanding since the first release with Oracle 8: RMAN!!! So my OTN Appreciation Day blog post is: “It’s so easy to use RMAN for Backups“. I wrote the blog in 2012 but guess it’s still valid.
OTN Appreciation Day – Thanks OTN Blogbeitrag lesen »
Actually I have a project where we are going to set up a high availability infrastructure with RAC and Dataguard. Due to the requirements from several applications (e.g. Flashback) we decided to implement the Multitenant database option. Even though it is not yet supported to flashback a single PDB we are able to use Snapshot Standby to flashback the standby database and unplug / create a PDB at a specific point in time.
Multitenant in a Dataguard Environment Blogbeitrag lesen »
Hugepages and Large Pages If you run a Oracle Database on a Linux Server with more than 16 GB physical memory and your System Global Area (SGA) is greater than 8 GB, you should configure HugePages. Oracle promises more performance by doing this. A HugePages configuration means, that the linux kernel can handle „large pages“, like Oracle generally calls them. Instead of standardly 4 KB on x86 and x86_64 or 16 KB on IA64 systems – 4 MB on x86, 2 MB on x86_64 and 256 MB on IA64 system. Bigger pages means, that the system uses less page tables,
7 easy steps to configure HugePages for your Oracle Database Server Blogbeitrag lesen »
In my last blog about Flashback Query “Flashback Query – Part 2” I had to admit that with Oracle Database Standard Edition it did not work as expected. So what if we are using Enterprise Edition? This is a similar example with the same Flashback Data Archive and the same tables but with Oracle Enterprise Edition 12.1.0.2 with PSU160419 from April 2016.
Flashback Query – Part 3 Blogbeitrag lesen »
