One of the great new features is unified auditing in Oracle 12c, with this feature you can start to define your own auditing, or use one of the built in policies. We don’t look into this blog about the general unified auditing. But what will happen when you use Unified Auditing and the database is
Last week I needed to validate an issue with an archive backup on a standby database. And I run into a “problem” which seems to be a change of behavior starting from 11.2.0.4. which I wasn’t aware of. First lets me show the error message before I explain the change in behavior. When I connect
When you plugin/clone a pluggable from a source container into a target container it is possible you have a mismatch in parameters or patches installed. In this blog post I list an example what you will notice when you perform a pluggable cloning action, into a new container with newer installed patches. I always advise
In a previous post I talked about the Force Full DB Caching feature introduced in Oracle RDBMS release 12.1.0.2. This feature is available in two flavours. – Database Caching (when possible) – Database Caching with force option. In this blog we look at the database caching when possible. And this one is simple,
With the introduction of Oracle 12c, 12.1.0.2 a few new features are introduced. One of those features is FULL Database Caching. No additional licensing is required when using this feature This feature is available in two flavours. - Database Caching (when possible) - Database Caching with force option. In this blog we look at the
One of the new features of 12.1 is the automatic stats collection when performing a Create table as Select action. But be aware of the site effects when using this feature, one a index is created it is also maintained but only for the first time, when an append is performed or a turncate table
In the old days, trace information of the broker command was automatically written in the logfiles for Data Guard broker. One of het nice things about this default logging, is the logging of the SQL statements the broker is executing. Starting from 11.2.0.3 this behavior is changed, and a tracelevel property is introduced. When you check the broker