I saw somebody using the GRANT ALL ON command recently and decided to see what I could do with it in an Oracle 11.2.0.2.7 database. First I logged in as OPS$ORACLE:
SQL> conn /
Connected.
SQL> show user
USER is "OPS$ORACLE"
SQL>
I noticed this in an Oracle 11.2.0.1.0 database. DBMS_STATS failed with an ORA-00600 and the first argument was [15851]. On investigation, it seemed to have something to do with the fact that the table had a function based index:
SQL> SELECT COUNT(*) FROM DBA_INDEXES
This was run on an Oracle 11.1 database. The v$reserved_words view lists Oracle's reserved words:
SQL> desc v$reserved_words
Name Null? Type
-------------------------- -------- ------------------
KEYWORD VARCHAR2(30)
LENGTH NUMBER
RESERVED VARCHAR2(1)
RES_TYPE VARCHAR2(1)
RES_ATTR VARCHAR2(1)
RES_SEMI VARCHAR2(1)
DUPLICATE VARCHAR2(1)
SQL>
It has 1733 rows:
This happened on Oracle 11.1.0.6.0. A colleague was debugging a package in a test database and his debug session fell over. Subsequent attempts to compile the package timed out as shown below:
SQL> alter package srce.pk_deemed_offer compile;
alter package srce.pk_deemed_offer compile
*
ERROR at line 1:
ORA-04021: timeout occurred while waiting to lock object
SQL>
The DBA_BLOCKERS view produced no output while this request was waiting:
SQL> select * from dba_blockers;
no rows selected
SQL>
… and there was nothing in V$LOCK either: