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 »
In my last blog “Flashback Functions – One Name, different Techniques“, I wrote about Flashback Functions. In this blog I will again write about Flashback Query. Flashback query is actually the ability to read the past content of a table. Oracle Database uses two techniques to accomplish this: Rollback/Undo Segments Flashback Data Archive
Flashback Query – Part 2 Blogbeitrag lesen »
Since version 9i there is the term “Flashback” in the Oracle Technology. However it is often hard to harmonize the different terms and corresponding technologies. Let’s start with the definitions: Flashback means, at least in the Oracle terminology, that a past state shall be restored. Might be you want to see the state of a data set one hour ago, the table before it was deleted or the change from last month. And here we are at the actual question: What have I got to do to meet requirements like these?
Flashback Functions – One Name, different Techniques Blogbeitrag lesen »
Why you should not set the DBTIMEZONE to a “Location Time Zone” format in Oracle. First of all, the DBTIMEZONE does not control at what time scheduler jobs exactly starts. When I have been taking care of my scheduler jobs recently I was wondering how do I now configure these, I came across a very simple question. After what time zone will “by hour 23” executed which I have planned here? In addition to the well known SYSDATE, I came across the DBTIMZONE parameter. What would make more sense that the database time zone controls when my >database!< scheduler jobs
Be careful when setting the DBTIMEZONE! Blogbeitrag lesen »
Since Oracle 12c you create and use a second (or even more) SCAN-Listener for Load-Balancing, Failover, etc. This can be useful to separate Network traffic e.g. for Dataguard or Shareplex replication. Like the ordinary SCAN-Listener you need two additional VIP- and three additional SCAN-Addresses. In the following example I want to separate the Dataguard traffic between a RAC Database with two nodes (morrison and manzarek) and a single node (daltrey) RAC Database as standby.
Second SCAN-Listener Blogbeitrag lesen »
How do I prevent the creation of a second PDB in a Single Tenant environment? At last Oracle introduced a number of new features with 12c, but Multi Tenant is still the one outstanding innovation. But when switching to the new version my customers have one question: Do I really need this feature? Beside the not really low licensing costs for the Multi Tenant Option, there are practical use cases. But when I use one productive environment with one test environment or a consolidation into a Multi Tenant environment makes simply no sense, I still can use the Non-CDB alternative.
Prevent PDB creation in a Single Tenant environment Blogbeitrag lesen »
