After you have issued the FLASHBACK DATABASE command how can you monitor the progress of the command, and more importantly, how can you predict when it will complete?
The behaviour of the pullup dependency as described in the Oracle documentation for CRS resources is counter-intuitive and so I decided to do some testing around it to see the results and reassure myself that the documentation was correct.
Before Oracle 11g, it was only possible to wrap PL/SQL code using the command line "wrap" utility. However, it is now possible to wrap code programatically after it has been loaded into the database using a simple PL/SQL procedure.
While refreshing a standby Database (11gR2) using “duplicate target database for standby” I recently encountered an error which one would normally associate with password files and/or the fact that the SYS password is not the same on the source and target databases. It was neither
I recently came across a scenario whereby we had created our ACFS filesystems as General Purpose filesystems using asmca, but then discovered that we needed these filesytems to be available prior to the database starting up and that we should have registered them as Oracle Home filesystems. This post details how we went about converting the filesystem without any loss of data.
During an installation of Oracle 11gR2 Real Application Clusters we encountered a warning during cluster verification that the NTP daemon did not have slewing enabled.