(Richard Foote) In the coming weeks, I’ll be blogging about quite a number of new indexing features/capabilities/improvements that have been introduced in Oracle Database 12c Release 2. These include:

(Carlos Sierra) eDB360 provides a lot of insight about an Oracle database. It executes thousands of SQL statements querying GV$ and DBA views from the Oracle’s data dictionary. It was designed to impose very little load on the system where it executes, thus it consumes only one session and avoids pa

(raysmithace) There are no circumstances where manually changing the passwords for the SYSMAN-named database accounts will end happily.

(Jeff Smith) I said there were 8 ways to avoid using SELECT * FROM queries in SQL Developer – but I didn’t actually count them. So let’s do that now.

(Ben) In this article, I’ll explain what the Oracle CORR function does and show you some examples.

(connormcdonald) One of the nice facilities in 12c is the ability to instruct the database to co-locate data during loading in order to facilitate reduced resource consumption for subsequent queries.

(Gokhan Atil) I noticed an interesting security problem (exploit?) on Oracle Enterprise Manager Cloud Control 13cR2 (I tested on EM13cR1 and it also exists on there). When you create an Enterprise Manager administrator, you need to grant some special privileges to that administrator if you want them

(David Fitzjarrell) In one of the Oracle forums a question was asked regarding revoking selected privileges from the DBA role. Unfortunately for the person posting the question the answer is a resounding “No”; granting a role grants all privileges assigned to that role and there is no “picking and c

(Ben) The DELETE SQL statement allows you to delete records from a table. I’ll explain more about the Oracle DELETE SQL statement in this article.

(Jeff Smith) We by default don’t store certain things in your SQLcl HISTORY list – like CONNECTs. For obvious reasons, it’s best not to store certain things, either for convenience or for security.