Below you will find a script which I created for a customer, due to the fact we needed to have an overview of the flash cache usage after enable write back mode. In a table the storage cell, allocated flash cache, used and dirty is provide. Very useful to see in one run the current
When it is required to resize the online redo logfiles in a Data Guard configuration you need to perform the resize for both the online redo logfiles as well as the standby redo logfiles. In this blog post an example how to accomplish this task. In another post will explain an issue which can occur
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
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