Changing an expired database account password using SQL Developer is very easy. Just follow these simple steps.
A simple tip on how to retrieve a history of all Patch Set Update applied to a database via SQL.
After applying the October 2015 Critical Patchset Update to our databases, we discovered a number of invalid objects within the XDB and GSMADMIN_INTERNAL schemas. This article provides the steps needed to ensure these objects compile successfully.
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.
This guide is intended to aid in establishing the origin of failed database login attempts. Most of the time these failed attempts are due to typos or outdated application configurations and are therefore not malicious, however due to default password management policies setting a limit on failed login attempts this often causes accounts to become... Continue Reading →
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.
Whilst developing some administrative functions within PL/SQL I needed to know whether the database that the code was being run in was part of an Oracle DataGuard setup, which you would think would be a trivial exercise. My first thought was that we could determine this via v$database. If the DATABASE_ROLE column in v$database contains STANDBY then we know... Continue Reading →
Users were complaining of ORA-12514: TNS:listener does not currently know of service requested in connect descriptor errors whilst connecting to a database on a RAC cluster. The cause was elusive, but was eventually tracked down to an unpublished bug relating to SCAN listener re-registration.